pretty sure you don't need an answer two years in, but maybe it will help someone else. The trick is to abandon using the basic process and use process logic from the advanced processes tab. Instead of using a seize delay relase basic process you first put a seize module. You seize the resource of your station. right after that you add an assign and assign the resource state to setup (you have to create this setup state in the stateset module, as it is not a standard built-in state). After that you add a delay for the setup time. if you want to care about setup states you can add an assign after the setup delay that for example sets the setup state to entity type. in the setup delay you could put something along the lines of (setup_state entity.type) * 1 meaning that setup takes an hour if another entity type was processed before or that no setup is required if consecutive parts are of equal type. Also, you should assign the resource state to processing after the setup delay. After you have done that, add another delay with your processing time definition. Finally, you put a release module that releases the required machine, resource, etc. and allows the next part to enter the resource. If setup requires another resource, i.e. a setup operator you can just put another seize module in front of the setup logic within the resource logic that seizes the operator. after setup, you put a release that releases the operator. This way you can manage that only one machine can be set up at a time, as the operator cannot work on 2 machines at once. Hope my explanation helps some people, as you certainly have figured out how to do this by now.
Very well explained! Thanks for sharing!
Thank you for this video, Could you explain how does destination type by expression work?
Why did you put decide box after creating ?
does this mean the parts can go to part 2 without going to part 1, or vice-versa
Thanks a lot. Great example
Thank you for knowledge sharing! :)
Gm sir...
How do I use the machine set up times in Arena Simulation model?
pretty sure you don't need an answer two years in, but maybe it will help someone else. The trick is to abandon using the basic process and use process logic from the advanced processes tab.
Instead of using a seize delay relase basic process you first put a seize module. You seize the resource of your station. right after that you add an assign and assign the resource state to setup (you have to create this setup state in the stateset module, as it is not a standard built-in state).
After that you add a delay for the setup time. if you want to care about setup states you can add an assign after the setup delay that for example sets the setup state to entity type. in the setup delay you could put something along the lines of (setup_state entity.type) * 1 meaning that setup takes an hour if another entity type was processed before or that no setup is required if consecutive parts are of equal type.
Also, you should assign the resource state to processing after the setup delay. After you have done that, add another delay with your processing time definition.
Finally, you put a release module that releases the required machine, resource, etc. and allows the next part to enter the resource.
If setup requires another resource, i.e. a setup operator you can just put another seize module in front of the setup logic within the resource logic that seizes the operator. after setup, you put a release that releases the operator. This way you can manage that only one machine can be set up at a time, as the operator cannot work on 2 machines at once.
Hope my explanation helps some people, as you certainly have figured out how to do this by now.