Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Transcript of Progressive Simulation
12/13/2012 A Presentation on AQUE Continuing the Medical Building Simulations In class, we simulated an Oncology medical treatment center with various levels of process detail in each iteration. Step 1: Assign Triage Values After you have the basic infrastructure in place, such as we do in our oncology center model (entities created, process modules in place, etc.), we can implement the triage functionality. Of course, you could do this step in the beginning of modeling as well. Step 2: Removal Capacity Once we've created our entities (patients) and assigned triage values, we'll need to remove them from the infinite queue they are "stuck" in otherwise. IE 4510: Simulation Modeling Tons of material covered! But there is still so much more to learn... Create Dispose Assign Record Decide Route Animation PickStation Station Entity Resource With simulation, we can always take it a step further. One need of a medical center such as an urgent care center would be to have the capacity for a nurse to choose their next patient based on triage, instead of in order of arrival. If you follow the right steps, you can fairly easily incorporate this functionality using the AQUE function. The steps given here will all reference the triage application example. We first need to decide on our Triage values. For our example, lets say 1,2 and 3 in order of most to least urgent. Assign these to your arriving entities using whatever distribution you choose (we'll do random here) with an assign type and directly route them to an infinite hold module with FIFO priority within each triage value. Initiate a control entity using a create block (in a separate line of modules). Proceed to sequentially assign a triage value to that control entity using an assign block. During the simulation run, the control entity will start off by searching for the first patient entity with a "1" triage value and remove the entity from the holding queue. If there are no more "1" patients remaining, the control entity will move on to "2" then finally "3". This allows top priority patients to be treated first. Step 3: Implementing AQUE Functionality According to the Arena help files, AQUE "returns the value of a general-purpose attribute of the entity at the specified Rank in queue Queue ID."
As the text book puts it, AQUE essentially finds the value of a queued entity. In our example so far, this is exactly the functionality we need in order to search through the triage values of the entities in our holding queue to then be compared to the control entity. Let's take a look at the coding.... The J variable allows for a search through the entities in the queue. AQUE(Hold Patients In Queue.Queue,J,NSYM(Patient Triage Value))==Triage Value Starting Value: 1 Ending Value: NQ(Hold Patients In Queue.Queue) Our familiar "NQ" command will come in handy here... Step 5: Removing the Entity Using a Remove block, functionality needs to be implemented to actually remove the patient from the queue. In our example, the queue name is of course: Hold Patients In Queue.Queue
and from our AQUE expression, the rank is "J" Bringing it all together Although we didn't cover each individual module extensively in this presentation, the above is what the entire AQUE functionality looks like (linked from the control entity string to the first decide block) Integrated into a model with processes, etc. such as our oncology center, you have now successfully implemented AQUE and can queue entities based on additional attributes than just arrival time.