Difference: EditingHoldModules (1 vs. 9)

Revision 92010-02-15 - KatTrevor

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

Editing Hold Modules

Line: 6 to 6
 

Wait for Signal

Changed:
<
<		This hold stores entities in a queue until a unique signal is recieved during the simulation. Each time the signal is received an entity leaves the Hold module queue.
>
>		This Hold module stores entities in a queue until a unique signal is recieved during the simulation. Each time the signal is received a specified number of entities (defined by Limit) will leave the Hold module queue.
 
Changed:
<
<		Consider the example of simulating cars queing at a parking building exit while waiting for their prepaid parking tickets to be approved. The cars ( entities) must wait for the signal 10 to be sent in the simulation. When this signal is sent, one car will proceed through the exit.
>
>		Consider the example of simulating cars queing at a parking building exit while waiting for their prepaid parking tickets to be approved. The cars ( entities) must wait for the signal 10 to be sent in the simulation. When this signal is sent, one car (as defined by Limit) will proceed through the exit.
  Hold_for_signal.PNG

Scan for Condition

Changed:
<
<		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.
>
>		This Hold module 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. As long as LoadingInnerCity is equal to one entities will leave the Hold module.
  Hold_Scan_for_Condition.PNG

Infinite Hold

Changed:
<
<		This hold stores entities in a queue infinitely while the simulation is running.
>
>		This Hold module stores entities in a queue for an infinite duration while the simulation is running.
 
Changed:
<
<		NB: An infinite hold is usually combined with a Search module and a Remove module (See Arena help for more details).
>
>		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. 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.
>
>		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 Hold module in queue until they are removed from the queue by an nurse (entity) at a Remove module.
  hold_infinite.PNG

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

Revision 72010-02-04 - KatTrevor

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

Editing Hold Modules

Line: 9 to 9
 This hold stores entities in a queue until a unique signal is recieved during the simulation. Each time the signal is received an entity leaves the Hold module queue.

Consider the example of simulating cars queing at a parking building exit while waiting for their prepaid parking tickets to be approved. The cars ( entities) must wait for the signal 10 to be sent in the simulation. When this signal is sent, one car will proceed through the exit.

Added:
>
>		 Hold_for_signal.PNG
 

Scan for Condition

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.

Line: 20 to 22
  This hold stores entities in a queue infinitely while the simulation is running.
Changed:
<
<		NB: An infinite hold is usually combined with a Search module and a Remove module (See Arena help for more details).
>
>		NB: An infinite hold is usually combined with a Search module and a Remove module (See Arena help for more details).
 
Changed:
<
<		-- MichaelOSullivan - 25 Aug 2009
>
>		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.
 
Changed:
<
<
  • Hold_for_signal.PNG:
    Hold_for_signal.PNG
>
>		hold_infinite.PNG

-- MichaelOSullivan - 25 Aug 2009

 
META FILEATTACHMENT attachment="Hold_Scan_for_Condition.PNG" attr="h" comment="" date="1265238748" name="Hold_Scan_for_Condition.PNG" path="U:\Summer Work\Printscreens\Hold Scan for Condition.PNG" size="10013" stream="U:\Summer Work\Printscreens\Hold Scan for Condition.PNG" tmpFilename="" user="KatTrevor" version="1"
META FILEATTACHMENT attachment="Hold_for_signal.PNG" attr="h" comment="" date="1265248904" name="Hold_for_signal.PNG" path="U:\Summer Work\Printscreens\Hold for signal.PNG" size="9848" stream="U:\Summer Work\Printscreens\Hold for signal.PNG" tmpFilename="" user="KatTrevor" version="1"
Added:
>
>
META FILEATTACHMENT attachment="hold_infinite.PNG" attr="h" comment="" date="1265249145" name="hold_infinite.PNG" path="U:\Summer Work\Printscreens\hold infinite.PNG" size="9248" stream="U:\Summer Work\Printscreens\hold infinite.PNG" tmpFilename="" user="KatTrevor" version="1"

Revision 62010-02-04 - KatTrevor

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

Editing Hold Modules

Line: 7 to 7
 

Wait for Signal

This hold stores entities in a queue until a unique signal is recieved during the simulation. Each time the signal is received an entity leaves the Hold module queue.

Added:
>
>		 Consider the example of simulating cars queing at a parking building exit while waiting for their prepaid parking tickets to be approved. The cars ( entities) must wait for the signal 10 to be sent in the simulation. When this signal is sent, one car will proceed through the exit.
 

Scan for Condition

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.

Line: 18 to 20
  This hold stores entities in a queue infinitely while the simulation is running.
Added:
>
>		NB: An infinite hold is usually combined with a Search module and a Remove module (See Arena help for more details).
 -- MichaelOSullivan - 25 Aug 2009
Added:
>
>
  • Hold_for_signal.PNG:
    Hold_for_signal.PNG
 
META FILEATTACHMENT attachment="Hold_Scan_for_Condition.PNG" attr="h" comment="" date="1265238748" name="Hold_Scan_for_Condition.PNG" path="U:\Summer Work\Printscreens\Hold Scan for Condition.PNG" size="10013" stream="U:\Summer Work\Printscreens\Hold Scan for Condition.PNG" tmpFilename="" user="KatTrevor" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Hold_for_signal.PNG" attr="h" comment="" date="1265248904" name="Hold_for_signal.PNG" path="U:\Summer Work\Printscreens\Hold for signal.PNG" size="9848" stream="U:\Summer Work\Printscreens\Hold for signal.PNG" tmpFilename="" user="KatTrevor" version="1"

Revision 52010-02-03 - KatTrevor

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

Editing Hold Modules

Line: 11 to 11
  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.
Added:
>
>		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

This hold stores entities in a queue infinitely while the simulation is running.

-- MichaelOSullivan - 25 Aug 2009

Deleted:
<
<
  • Hold_Scan_for_Condition.PNG:
    Hold_Scan_for_Condition.PNG
 
META FILEATTACHMENT attachment="Hold_Scan_for_Condition.PNG" attr="h" comment="" date="1265238748" name="Hold_Scan_for_Condition.PNG" path="U:\Summer Work\Printscreens\Hold Scan for Condition.PNG" size="10013" stream="U:\Summer Work\Printscreens\Hold Scan for Condition.PNG" tmpFilename="" user="KatTrevor" version="1"

Revision 42010-02-03 - KatTrevor

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

Editing Hold Modules

Line: 16 to 16
 This hold stores entities in a queue infinitely while the simulation is running.

-- MichaelOSullivan - 25 Aug 2009 \ No newline at end of file

Added:
>
>
  • Hold_Scan_for_Condition.PNG:
    Hold_Scan_for_Condition.PNG

META FILEATTACHMENT attachment="Hold_Scan_for_Condition.PNG" attr="h" comment="" date="1265238748" name="Hold_Scan_for_Condition.PNG" path="U:\Summer Work\Printscreens\Hold Scan for Condition.PNG" size="10013" stream="U:\Summer Work\Printscreens\Hold Scan for Condition.PNG" tmpFilename="" user="KatTrevor" version="1"

Revision 32010-02-03 - KatTrevor

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

Editing Hold Modules

Line: 6 to 6
 

Wait for Signal

Changed:
<
<		Coming soon!
>
>		This hold stores entities in a queue until a unique signal is recieved during the simulation. Each time the signal is received an entity leaves the Hold module queue.
 

Scan for Condition

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.

Infinite Hold

Changed:
<
<		Coming soon!
>
>		This hold stores entities in a queue infinitely while the simulation is running.
  -- MichaelOSullivan - 25 Aug 2009 \ No newline at end of file

Revision 22009-09-07 - TWikiAdminUser

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

Editing Hold Modules

Changed:
<
<		Hold modules belong to the Advanced Process template (if you cannot find this template you may need to attach it). After you have added a Hold module by dragging it onto the flowchart view, you can edit it by double clicking. You can change the Name of course, but the main functionality is determined by the Type. There are 3 types of Hold module and we will discuss each on of them separately.
>
>		Hold modules belong to the Advanced Process template (if you cannot find this template you may need to attach it). After you have added a Hold module by dragging it onto the flowchart view, you can edit it by double clicking. You can change the Name of course, but the main functionality is determined by the Type. There are 3 types of Hold module and we will discuss each one of them separately.
 

Wait for Signal

Line: 10 to 10
 

Scan for Condition

Changed:
<
<		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 and enity is feed from the Hold module queue.
>
>		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.
 

Infinite Hold

Revision 12009-08-25 - MichaelOSullivan

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

Editing Hold Modules

Hold modules belong to the Advanced Process template (if you cannot find this template you may need to attach it). After you have added a Hold module by dragging it onto the flowchart view, you can edit it by double clicking. You can change the Name of course, but the main functionality is determined by the Type. There are 3 types of Hold module and we will discuss each on of them separately.

Wait for Signal

Coming soon!

Scan for Condition

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 and enity is feed from the Hold module queue.

Infinite Hold

Coming soon!

-- MichaelOSullivan - 25 Aug 2009

View topic | History: r9 < r8 < r7 < r6 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback