Search the Community

Hi LizMB, Without evaluating your model in detail, that error is due to a transfer not being completed (transfer request while entity is still being transferred previously). It is typically when you make use of a transfer step and either not end the transfer (using and "End Transfer" step), before transferring it again or when Simio attempts to transfer the entity (due to inherent worker/node/vehicle logic) before the end transfer is completed. It could also be if you interrupt something before a transfer action has completed. What also happens is when you have processes executing e.g. On-Entered and the same entity executes one or more such processes at the same time, resulting in a inherent transfer request before the previous has completed. It could be a matter of timing or the sequence of events, or a problem in your logic. When you are using a transfer step in your logic it is useful to have a process with an End Transfer step that is either subscribed to certain events or executed on an event triggered e.g. StationName.Entered. If you were to interrupt a process/action, you can either fire the trigger event or just use logic to test whether the entity has transferred. With an add-on process it is best to understand the sequence of events happening in the Simio logic and ensure certain logic gets completed first or that you don't have parallel requests at the same time. As you can see there are multiple ways to address something like this and your approach depends on your logic and the system being modeled. Good Luck. H

You can just use a process with a WAIT step. On entity arrival you will fire and event and the process will go on. I also belive that a worker is derived from entity so you can use workers instead of entities. Or the best fitting thing is to use consume step to consume a material (the tools). And have two inventories for it (one near the machine, one in the warehouse of tools). There are some simbits with the basic inventory concepts.

Hi, I am looking for an event which can be used in a Wait step in a process which is triggered by an entity finishing processing in a station. Also potentially an event which is triggered when an entity exits a station. Do I have to manually fire an event with an addon process from every station which I wish to do this?

Hi there - My entities are going into a wait step based on a condition. So at any point in time I may or may not have multiple entities in the wait step. When I fire an event to release entity from the wait step all the entities which are in the wait step at the time event is fired get released. I don't want that, I want wait to release only one entity every time release event is fired. Any ideas how I can achieve this? Thank you.

You asked for "a way to start/stop timers on a specific entity without creating a bunch of different events". As I understand it, Enable is just a switch that stops/starts the Timer clock. It has nothing to do with triggering events and does not require any events. So if you set a timer to fire in 60 minutes, then after 10 minutes disable the timer, the timer should fire its event 50 minutes after it is enabled.

For this particular scenario, you could have a Timer (see Definitions tab, Elements button on panel). The timer would define the time(s) that an event is triggered - for example if the simulation starts at 12 am, then you could have the first timer event at 5 hours (5 am) and then every 12 hours after that (5 pm, 5am, 5pm, etc.). The 'event' that the entity would wait for would then be TimerName.Event. You could use a Decide step before putting the entity into the Wait step, then the event would be automatically fired at a given time by the Timer element. (instead of by a Fire step).

Hello, In my model I’ve made entity arrival mode to be On event and I’ve created an event named CommandeEvent in the Definition ==>event section. In order to action the event, I’ve created a process called ProcessEvent in which I have a decide step followed by a fire step that fire the CommandeEvent if the condition in the Decide step is respected. But when I run the model, the entities are not created. Is there something I should do differently or add ? Thank you, Flora

If you mean that an entity should not advance to the next location unless it is available: Try using Node Lists when routing entities to the next location. Lists automatically block the entity from moving forward if the destination server is not available. 1. Create a node list in Definitions>Lists 2. Set the input and output buffers to 0 on your servers 3. On the output nodes, set Entity destination type to "Select From List" and choose the node list. If you mean you have a group entities that are processing at different servers and none in that group can advance until all are processed: Use a Wait step and event. After each entity finishes, trigger the wait step to wait for an event. After the last entity finishes, fire the Event. You will probably also use a Decide step to separate the non-last entities (wait for event) from the last entity (fire event).

Your logic is fully right. But, you have to send an entity (or any token) to the processevent to fire your event. Examine the sample model I attached. OnRunInitialized process I created an entity and by using this entity I activated the process1 to fire the event. You should apply this type of logic. sample model.spfx

Hi, I'm already assigning resources based on priority, but if I have a high-priority entity hit a certain point and there are no resources available (capacity ==0), I want to branch off and have a resource "stolen" from a lower priority entity so that my high-pri entity can get service. Does this imply a release-seize? Maybe I could fire an event and all my low-pri processes are listening to do a release? But how could I make it so that not everyone dumps their resource? Or is this a "Move"? Note that there isn't actual movement, so I'm not sure if this applies. Any tips gratefully received! I'm not sure even how to use "Candidate" well, in order to see if the "Candidate"s Owner is a low-pri entity or not.

The recommended approach might vary by what you are waiting for. For example if the plane is a Vehicle that will come to pick up the passengers, then the easiest approach is probably to have a Server with 0 processing time. Entities will flow through it with no delay, but then wait in the outbound transfer node for the Ride requested. If you want to wait on something more arbitrary you could direct the entity that enters an outbound transfer node to Wait for an event. Then you would have to add some logic to Fire that event (unless it is one that is already automatically fired). You should post your questions inside the Simio Insider forum where we can post screenshots and examples to provide a more complete answer.

I extended the previous model a little bit because i want to measure how often the servers are idle. I implemented that the following way: As soon as one server is idle it fires an event and all the other servers are idle too. Is one server idle, all servers have to stop working. Because you can consider it as an assembly line. And i count how often the event is fired. All servers fire the same failure event. But i don't know how to repair the servers as soon as the idle server gets a new entity again. Because as soon as the idle server has new material the assembly line (all servers) can start working again. But i can't handle that with an add on process and an event because its only allowed to fire an repair event when it was idle before. So i don't know how to do that. I hope you can help me with that too. In the example i let the servers be repaired after 3 minutes. And do you know if i can get a graph at the end of the simulation which shows at which time for how long the servers had a failure or were idle? Because under results i only see how often and how long they were idle but not when. Is that possible to get that information? Thanks a lot for your support! HeuristicTest3.spfx

You are correct that the automatic "Entered" event on a node fires whenever any entity enters that node. Unfortunately a Vehicle is a type of entity. So a vehicle delivering an entity causes the event to fire twice, once when the vehicle arrives and once when it delivers the entity and IT arrives. The solution involves: 1) Create a custom event on the Definitions>Events tab. 2) Trigger that event. Perhaps the easiest way is to add a process the the Sink Entered (Sink>AddOnProcessTriggers>Entered). This process can be a single Fire step that triggers that new Event. 3) Change the source to use that new event. Here is an example:EntityArrivalEventToSink.spfx