Delay: Difference between revisions

From Planimate Knowledge Base
Jump to navigation Jump to search
(initial)
 
No edit summary
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== M<span style="background-color: navy; color: white;" />ultiServer: Multiple servers in one object  ==
== &nbsp; Delay: One or more servers in one object  ==


The M<span style="background-color: navy; color: white;" />ultiServer object has the ability to delay one or more items at a time.  
<onlyinclude>[[Image:MultiServerIconLg.jpg]]


They can be classified as "Logical with Capacity and Process Delay".  
In simulation, objects that can hold an item and apply a process delay time before releasing the item are known as '''Servers'''.


M<span style="background-color: navy; color: white;" />ultiServers are used in situations where one or a number of items undergo a delay (representing some operation) in parallel or together.  
The Planimate '''Delay '''object has the ability to delay one <u>or more</u> items at a time.</onlyinclude>


Servers are objects that can hold items and apply a process delay time before releasing the items.  
Delays are used in situations where one or a number of items undergo a delay (representing some operation) in parallel or together. The process delay time can be zero, fixed, or made to vary from item to item, with a choice of distribution patterns.


The process delay time can be zero, fixed, or made to vary from item to item, with a choice of distribution patterns.
<br>


Process delays are edited in Interaction View.  
The number of items that may be held in the Delay can be varied in the model over time. This enables you to model situations such as workdays and weekends, lunch breaks, work shifts and regular down time.


The number of items that may be held in the Multi-Server can be varied in the model over time.  
The process delay is configured via the object's context menu and can be set per item class.


This enables you to model situations such as workdays and weekends, lunch breaks, work shifts and regular down time.  
During a model run (but not in User Mode) clicking on a Delay's icon (or its head in "road" mode)&nbsp; enables you to browse its items. You can see:


=== M<span style="background-color: navy; color: white;" />ultiServer States  ===
'''Item Entry Time;&nbsp; Item class;&nbsp; Item ID;&nbsp; Time-till-departure.'''


Idle No items are currently in the M<span style="background-color: navy; color: white;" />ultiServer.  
Clicking on a line in this list will show the item details for that item.<br>[[Image:Multiserver As Road with Data.jpg|center|500px]]


Busy At least one item is currently in the M<span style="background-color: navy; color: white;" />ultiServer.
=== States  ===


Blocked One or more items are blocked from leaving the M<span style="background-color: navy; color: white;" />ultiServer.
Delay Objects have these states:


Unavailable The M<span style="background-color: navy; color: white;" />ultiServer has entered a period of zero server availability.  
[[Image:MultiServer-Idle.jpg]]&nbsp; '''Idle&nbsp;&nbsp; '''No items are currently in the Delay.


Note: A M<span style="background-color: navy; color: white;" />ultiServer with a capacity set to 0 sets itself to "Unavailable" state, as long as there are no items present or blocked in which case the busy/blocked states take priority.  
[[Image:MultiServer-Busy.jpg]]&nbsp; '''Busy&nbsp;&nbsp; '''At least one item is currently in the Delay.


=== <br>Capacity  ===
[[Image:MultiServer-Blkd.jpg]]&nbsp; '''Blocked&nbsp;&nbsp; '''One or more items are blocked from leaving the Delay.


Enables the capacity of the M<span style="background-color: navy; color: white;" />ultiServer to be set. <br>The Capacity of a M<span style="background-color: navy; color: white;" />ultiServer may be determined in a range of ways:
[[Image:MultiServer-Unav.jpg]]&nbsp; '''Unavailable&nbsp;&nbsp; '''The Delay has entered a period of zero server availability.


As a constant value that does not change.  
'''Stopped'''&npsb;&nbsp; The Delay has been suspended/interrupted by the Control attribute being set to 0.
<br>


By reference to an Attribute which may change over time or change based on other conditions in the model during the model run.  
''Note: A MultiServer with a capacity set to 0 sets itself to "Unavailable" state, as long as there are no items present or blocked in which case the busy/blocked states take priority.''


Using an Attribute reference will enable the capacity to be changed during a model run.
== Delay Settings  ==


For example, when an item enters the M<span style="background-color: navy; color: white;" />ultiServer the Attribute it is carrying can determine the new M<span style="background-color: navy; color: white;" />ultiServer capacity.
=== Capacity  ===


=== <br>Server Limit  ===
Enables the capacity of the MultiServer to be set. <br>The Capacity of a MultiServer may be determined in a range of ways:


This setting enables Planimate® to allocate memory to accommodate the maximum number of servers you expect to be in the M<span style="background-color: navy; color: white;" />ultiServer during the run.  
*As a constant value that does not change.
*By reference to an Attribute which may change over time or change based on other conditions in the model during the model run.
*Using an Attribute reference will enable the capacity to be changed during a model run.


This sets a hard limit on how many items can undergo a delay at the M<span style="background-color: navy; color: white;" />ultiServer at the same time.  
For example, when an item enters the MultiServer the Attribute it is carrying can determine the new MultiServer capacity.


You then use the Capacity setting to vary the capacity dynamically over time, it you wish.
=== Control ===


You need to ensure that the maximum Capacity you expect to provide is less than or equal to the Server Limit value.  
An attribute can stop and resume a Delay. When the control attribute is set to zero, the delay is stopped and all items in the Delay are suspended and resume the delay they were performing when the control attribute becomes non zero.


If the Capacity value of the multi-server exceeds this Server Limit, the Server Limit is applied.
== Delay Options  ==


The maximum specifiable capacity limit of m<span style="background-color: navy; color: white;" />ultiServers is 9999.
=== Show as Road  ===


=== <br>Show as Road Option  ===
This option enables a Delay to animate [[Item]] process delays along a straight line.


M<span style="background-color: navy; color: white;" />ultiServers may be configured to Act as a Road and animate items overtaking each other and moving at different speeds.  
You can adjust the line using the [[Position Exit]] option of the [[Object Edit Menu]].


=== <br>Pausable 0 Delay Option  ===
Items with varying delay times are displayed overtaking each other and moving at different speeds.


Pauseable 0 Delay configures the m<span style="background-color: navy; color: white;" />ultiServer to enable a pause of the model, even at zero time.  
Adjust the model's [[Update Interval]] to adjust the smoothness of your animation.


This enables a modeller to specify "pauseable points" in a long processing sequence which runs in zero time in a very controlled manner.  
With this option set, you are also able to adjust the number, and spacing of "Lanes" the items can use as they travel along the line. (Lane Selection will be random during a model run).


More details on Pauseable 0 Delay  
=== Pausable 0 Delay ===


=== <br>No Blocking between Items Option  ===
{{Breakout|Pauseable Zero Delay Delays}}


M<span style="background-color: navy; color: white;" />ultiServers have an option to prevent a blocked item from blocking other finished items.
=== No Blocking between Items Option  ===


This makes it act more like a dispatcher when many items are finished and one is blocked.  
Delays have an option to prevent a blocked item from blocking other finished items.


No blocking between items option is on by default for new servers.  
This makes it act more like a dispatcher when many items are finished and one is blocked.


If you turn this option off, you create a single exit point for a Multi-Server.  
No blocking between items option is on by default for new servers.


Whenever an item is blocked from leaving a multi-server, ALL subsequent items in the m<span style="background-color: navy; color: white;" />ultiServer become blocked.  
''This option is on by default. ''


This single exit is sometimes useful because it maintains the exit order of the items, based on when they finished their delay.  
If you turn this option off, you create a single exit point for a Delay.


=== <br>Multi-server Interaction Editing  ===
Then, whenever an item is blocked from leaving a multi-server, ALL subsequent items in the Delay become blocked. This single exit is sometimes useful because it maintains the exit order of the items, based on when they finished their delay.


The delay an item undergoes is specific to its class and independent of any other activity in the Multi-Server.
== Delay Time  ==


The delay parameter needs to be set separately for each item class that will use it.  
The delay an item undergoes is specific to its item class. Hence if multiple item classes use a Delay, you need to configure them separately.


To set the delay time, shift to Interaction Edit View and click on the MultiServer.  
The context menu for the object lists all the classes using the object so they can be edited.


A Distribution Pattern Dialog appears enabling the time to be set.  
The delay is set using a Distribution Pattern Dialog.
<br>Refer to Editing Object Properties for information about editing properties common to all objects. <br>


The time you set pertains only to the item class displayed in the Item Edit Box, whose paths you can see on the screen.


<br>Refer to Editing Object Properties for information about editing properties common to all objects. <br><br>
== Delay Articles  ==


[[Category:Object/Multiserver]]
<dpl>
[[Category:Object]]
category=Object/Delay
notnamespace=Category
notcategory=FAQ
ordermethod=pagetouched
order=descending
</dpl>
 
<br> <br>
 
== Delay Object Frequently Asked Questions  ==
 
<dpl>
category=FAQ
titlematch=%Multiserver%|%multiserver%|%Multi-server%|%multi-server%
ordermethod=pagetouched
order=descending
</dpl>
 
<br> 
 
[[Category:Object/Multiserver]] [[Category:Object]]

Latest revision as of 12:49, 26 October 2020

  Delay: One or more servers in one object

MultiServerIconLg.jpg

In simulation, objects that can hold an item and apply a process delay time before releasing the item are known as Servers.

The Planimate Delay object has the ability to delay one or more items at a time.

Delays are used in situations where one or a number of items undergo a delay (representing some operation) in parallel or together. The process delay time can be zero, fixed, or made to vary from item to item, with a choice of distribution patterns.


The number of items that may be held in the Delay can be varied in the model over time. This enables you to model situations such as workdays and weekends, lunch breaks, work shifts and regular down time.

The process delay is configured via the object's context menu and can be set per item class.

During a model run (but not in User Mode) clicking on a Delay's icon (or its head in "road" mode)  enables you to browse its items. You can see:

Item Entry Time;  Item class;  Item ID;  Time-till-departure.

Clicking on a line in this list will show the item details for that item.

States

Delay Objects have these states:

MultiServer-Idle.jpg  Idle   No items are currently in the Delay.

MultiServer-Busy.jpg  Busy   At least one item is currently in the Delay.

MultiServer-Blkd.jpg  Blocked   One or more items are blocked from leaving the Delay.

MultiServer-Unav.jpg  Unavailable   The Delay has entered a period of zero server availability.

Stopped&npsb;  The Delay has been suspended/interrupted by the Control attribute being set to 0.

Note: A MultiServer with a capacity set to 0 sets itself to "Unavailable" state, as long as there are no items present or blocked in which case the busy/blocked states take priority.

Delay Settings

Capacity

Enables the capacity of the MultiServer to be set.
The Capacity of a MultiServer may be determined in a range of ways:

  • As a constant value that does not change.
  • By reference to an Attribute which may change over time or change based on other conditions in the model during the model run.
  • Using an Attribute reference will enable the capacity to be changed during a model run.

For example, when an item enters the MultiServer the Attribute it is carrying can determine the new MultiServer capacity.

Control

An attribute can stop and resume a Delay. When the control attribute is set to zero, the delay is stopped and all items in the Delay are suspended and resume the delay they were performing when the control attribute becomes non zero.

Delay Options

Show as Road

This option enables a Delay to animate Item process delays along a straight line.

You can adjust the line using the Position Exit option of the Object Edit Menu.

Items with varying delay times are displayed overtaking each other and moving at different speeds.

Adjust the model's Update Interval to adjust the smoothness of your animation.

With this option set, you are also able to adjust the number, and spacing of "Lanes" the items can use as they travel along the line. (Lane Selection will be random during a model run).

Pausable 0 Delay

Pauseable Zero Delay Delays

For full details refer to this page: Pauseable Zero Delay Delays

No Blocking between Items Option

Delays have an option to prevent a blocked item from blocking other finished items.

This makes it act more like a dispatcher when many items are finished and one is blocked.

No blocking between items option is on by default for new servers.

This option is on by default.

If you turn this option off, you create a single exit point for a Delay.

Then, whenever an item is blocked from leaving a multi-server, ALL subsequent items in the Delay become blocked. This single exit is sometimes useful because it maintains the exit order of the items, based on when they finished their delay.

Delay Time

The delay an item undergoes is specific to its item class. Hence if multiple item classes use a Delay, you need to configure them separately.

The context menu for the object lists all the classes using the object so they can be edited.

The delay is set using a Distribution Pattern Dialog.
Refer to Editing Object Properties for information about editing properties common to all objects.


Delay Articles




Delay Object Frequently Asked Questions