Difference: EditingHoldModules (7 vs. 8)

Revision 82010-02-04 - KatTrevor

Line: 1 to 1
 
META TOPICPARENT name="ArenaGuide"

Editing Hold Modules

Line: 15 to 15
  This hold stores entities in a queue until a condition is satisfied. However, the Hold module ONLY checks this condition WHEN A CALENDAR EVENT OCCURS. If the condition is true then the first entity in the queue may leave the Hold module. This generates a new event and the condition is checked again. Each time the condition is true an entity leaves the Hold module queue.
Changed:
<
<
Below is an example of a Scan for Condition Hold module from the Case Study: Courier Service Model.
>
>
Below is an example of a Scan for Condition Hold module from the case study: Courier Service Model.
  Hold_Scan_for_Condition.PNG

Infinite Hold

Line: 24 to 24
  NB: An infinite hold is usually combined with a Search module and a Remove module (See Arena help for more details).
Changed:
<
<
Consider the example of simulating an emergency waiting room. Incoming patients (entities) are placed into a queue based on their Patient Type. Patient Type is an attribute assigned to each entity earlier in the model. Entities will wait in the Emergency Room module in queue until they are removed from the queue by an nurse (entity) from a Remove module.
>
>
Consider the example of simulating an emergency waiting room. Incoming patients (entities) are placed into a queue based on their Patient Type. Patient Type is an attribute assigned to each entity earlier in the model. Patients will wait in the Emergency Room module in queue until they are removed from the queue by an nurse (entity) from a Remove module.
  hold_infinite.PNG
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback