Search the Community
Showing results for tags 'worker'.
Hi all, In a warehouse the transporter needs to work in different logic based on part size condition. If the part is large, it should pickup only one type of part and drop to a single destination which is easy to model with the default vehicle object. However if the same vehicle picks up a "small" part, it should pick up all the other "small" items in other locations (output of server) which have the same destination and drop them to the destination (working like a supermarket cart or milkrun). We are struggling to model this picking process and having the transporter work in either way b
I'm having some trouble with worker actions and transfer steps. Below is a picture of my current model. I have also attached the simio file itself. What I want to happen: Worker1 carries both entities to their respective nodes and leaves them in their respective stations after worker(A/B) "checks them" (I used a delay to simulate this check) and then Worker1 moves on. The worker(A/B) only picks up the entity if needed. So if the worker was with another entity in process (like Srv(A/B)), he would go check the new entity so that worker1 can move on, but would return
Hi I am currently working on modeling a facility whose description I provide below and attach its simio file to this message: 1)There are Two entities each titled 'Small Package' and 'Large Package' that enter the system through a Server titled 'Shooter' 2) Four worker elements take the incoming packages to 16 Sinks titled as 'Carts' 3) I have set up a process at the Output@Server1 so that each worker element serves a specific set of Carts Worker 1 -> Cart1, Cart2, Cart 3, Cart 4 Worker 2 -> Cart 5, Cart 6, Cart 7, C
I've got multiple workers going to single server. As the title implies, I'd like these workers to mimic the real-life behaviour of randomly going on leave for a random amount of time. Ideally I'm looking for something that's shown in vehicles or servers, but for workers. Does anyone here know an easy workaround for this? I did think about adding in a add-on process after the worker releases an entity with a counter, and after a certain count the worker is seized for a random amount of time. I just thought there would be a better way. Another alternative would be creating a work sched