KarsaOrlong

Thanks for the help. I came up with another solution, let me know what you think: The Entity has reached end of queue and is about to begin processing. In Server-Before Processing state assignments I recalculate .TimeTillDeath. At this time I will also give them a .TreatmentTime = random.exp(x). Actual server processing time is Min(ModelEntity.TimeTIllDeath, ModelEntity.TreatmentTime) Once they leave the station, my routing is based on if TimeTillDeath < Treatment Time. If that is true, then they had effectively died at end of service and are sent to a sink. I can see how this would fudge some of the Server stats in the results page, but I am not concerned about actual treatment times there. Let me know if i'm missing something.

How can I schedule a randomly distributed death event for each entity, and pull them out of the system (or perhaps route to a "mortality" sink) if it occurs before they have already left? Somewhat similar to reneging, but I need mortality to be possible during a service, not only in queues. If an entity is removed from service, I also need the seized resources to be released. What I have tried so far: When an entity is created, I provide them with a state variable for TimeTillDeath, lets say exponential(2) hours. This is a real number, not a datetime. As they enter each queue, I set the reneg trigger as ModelEntity.TimeTillDeath subtract any elapsed time since creation, min 0. This works to model mortality while they are waiting for service, but not during a service. Any help is appreciated, KO