GFurtado

Each ContainerEntity has its own ContainerEntity.DesiredSpeed. You can assign a new value to it whenever you like.

Check a SimBit named Choose Alternate Sequence. It creates a process containing the Set Row step to change the current sequence table.

Try using a similar logic to the model I attached. I created a chain of states where one updates the next one, and you can easily access their values. Change to the state you want to memorize and when/where you want to trigger it. Passing TimeStamps.spfx

I would suggest to expand this model I sent before by creating new states inside your ModelEntity. Two states when the entity leaves a station (one updates the station name and one updates the time it left). A state when the entity enters a station. Maybe another states registering how many rows in your sheet were written. The columns of your sheet would be ModelEnity.FromStation, ModelEntity.ToStation and (ModelEntity.TimeLeftStation - TimeNow). Let me know if you need help building this model.

Wait, actually this doesn't work. Check the attached model: Create a new ContainerEntity with a string state named whatever you like; Assign NewContainerEntity.NewStringState = Filler.Name when entering the filler. Use this expression any time you need the name of the last station that entity visited. Get Station Name.spfx

ModelEntity.CurrentStation.Name Be aware that this will return an error in the case the entity is not at a station.

ModelEntity.CurrentStation might help you. Alternatively: You could register the object in an ObjectReference state or its name in a string state, depending on what you want to do with this information.

Sure. It depends on your model logic/design. I would suggest using Server1.Failure.Active expression as a process time parameter. This expression return 1 when Server1 stops due a failure, otherwise it returns 0.

Open your ModelEntity and add a new Real State variable named TimeInServer1 or whatever; Set ModelEntity.TimeInServer1 = TimeNow when the entity enters Server1; Set ModelEntity.TimeInServer1 = TimeNow - ModelEntity.TimeInServer1 when the entity exits Server1; Set Server2 processing time to ModelEntity.TimeInServer1 * E + delay (hours). Check the attached model for some extra help. Register Server1 Processing Time.spfx

It is possible. There's several ways to solve this. It is just a matter of model designing. Some tips: 1. You can use expressions like TimeNow or ModelEntity.TimeInSystem to check how much time processing time has passed. 2. Interrupt step might help you remove the entity from the process. 3. A State inside the ModelEntity will help your entities to take the right path or take the right decisions. Open you entity model, create a boolean state named Failed (or whatever the name you like), set ModelEntity.Failed to True or False, and use this same expression to steer you entity to the right direction. 4. Be creative. Your solution heavily depends on your problem.

Ok, in this case, I tried to solve it using a regular Data Table. Maybe not the prettiest solution, but check the attached model. I used the TimeNow expression to check what day is it and assigned the Entities per Arrival property to that day's row of the data table. Arrival.spfx

Is there a reason you're using a Rate Table instead of the good ol' Interarrival Time?

I set ModelEntity.Priority = X at Output@SourceX State Assignments property, but it could be assigned anywhere before the server.

Entities are prioritized in server according to the server Ranking Rule. Check my attached model. I set Entity1 priority to 1, Entity2 priority to 2 and told the server to prioritize the ModelEntity with the highest priority value. You can play with that logic to prioritize everything the way you want. entity priority.spfx

I believe you can't create of vector of elements. Although, you can create a element reference state vector, which might be helpful. Your best bet would probably be modelling your process logic to trigger events through the Fire step, instead of using a timer. Or maybe adding a timer inside a object model, so every instance of that object has its own timer.