Search the Community
Showing results for '"resource reservation"'.
-
Two options depending on whether you want the worker to be shown as idle during the move or busy during that entire sequence: One is to use the resource reservation feature on the Secondary Resource in Server. On Server1 and Server2, you would reserve the resource for the amount of time you expect it would take to get to the next Server. Then when you get there it would automatically prefer that resource and no other entity could seize it during the timeout period. The second is to use the Other Resource Seizes to seize the worker before starting on Server1 and use the Other Resource Releases to release the worker After Processing at Server 3.
-
Worker exiting a station and leaving entity
Kaylinn replied to Kaylinn's topic in SI General Discussions
Thank you for your quick reply! Yes, I am using workstations. Could you tell me more about this resource reservation? That's a new one for me. And I just had another question. I am modeling a wash station that takes 30 minutes for the first piece, and an additional 5 for each piece after that(so a batch of 3 would take 40 minutes, a batch of 6 would take 55 minutes, and so on) but I'm having some trouble putting this into a processing time. The added problem is that the number of entities changes. Currently I'm using a source that produces one "shipment" a day with "Entities per arrival" set as "random.triangular(3,13,19)" which is working fine for my quantity, but I don't know how to relate that into the processing time of the next workstation. -
Worker exiting a station and leaving entity
dsturrock replied to Kaylinn's topic in SI General Discussions
1) If you are not already using a Workstation (instead of a Server) you probably should because it has the 3 stage processing that you appear to need. Or use the new task features added to Server around sprint 120/121. 2) The problem you are having is because between the "work" phase and the "move" phase there is a delay. Even if this is a zero-time delay, the Worker momentarily goes idle, and it gives any other waiting entity a chance to seize the worker before this entity can get it back. One of our SimBits has a "hack" type solution to this, but a much better solution is available using the resource reservation features added to sprints 121/122. This new feature lets an entity release a resource, but prevents any other entity from seizing that resource for a specified time period. 3) There are often multiple ways of approaching a problem. The simple answer is to use the one you understand the best or the one that is clearest to explain to others. In general, I personally try to stay inside the object properties (no processes) as much as I can because it is easier for most users to understand (e.g. more self-documenting). But if I need to add process logic for any reason, then I am inclined to put everything in the processes so I can see all my logic together in one place. But that is just my personal preference.