ow121912

I tried proceeding with the method suggested by deod, but when I checked the resource plan in the Planning tab, the naming did not appear correctly. I’m sorry to bother you, but would it be possible to take a look at a sample file if you have one available?

I also checked the OnEntityArrival Process of the Source, but since there is no Step related to entity naming, I could not find a solution.

Hello, I created a simple model where a Source generates an Entity that immediately goes to a Sink. When I checked the Trace, I noticed that in Source1.OnEntityArrival, the entity was created with the name DefaultEntity.7. Why does the numbering start from 7 instead of 0 or 1? I know that entity naming can be defined through a Table, but since my model generates more than 230,400 entities, it is very cumbersome to create names one by one. Without using a Table, is there a way to automatically name the entities as EntityName.0 or EntityName.1? Thank you. Trace On entity arrival Process

Example.spfxHere is the sample file

Hello. To address the issue you mentioned, I recommend the following approach: Create a state in the ModelEntity to store information about defects. In the Facility view, create one Source, one Server, and one Sink, then connect each object with Paths. Additionally, create a Path from the Server’s Output to its Input. Set the Path weight from the Server’s Output to the Sink to 90, and set the Path weight from the Server’s Output back to the Server’s Input to 10. Set the Server’s Output Outbound Link Rule to By Link Weight. Add a Process to the Path that goes from the Server’s Output back to the Input. Configure it so that when the entity enters the Path, the state you set earlier will be updated to 1. Set the Server’s Processing Time to vary depending on the state by using a Math.If expression: Math.If(ModelEntity.variable == 1, Random.Triangular(3,4,5), Random.Exponential(10))

It seems the approach I had in mind was much more complicated than necessary. Thanks to your suggestion, I was able to resolve the issue. After applying your method, it worked seamlessly in my model. Thank you very much for your help.

Thank you very much for your response, Vinicius. Thanks to your reply, I was able to confirm once again that my assumptions were correct. For now, I have designed my model’s logic to minimize pickups as much as possible, which allowed me to create a simulation that matches the expected values. However, this is only a temporary measure, and since it could cause problems later, I think it would be better to revise the model according to your suggestion. That said, in my current model, the vehicle’s travel speed has been implemented to match the real-world model, so changing the vehicle speed is not feasible. Therefore, I tried to implement the method you suggested using the Process approach. However, while doing so, I encountered a problem: in my model, according to the day pattern, the wage rate during certain hours should be 1.5 times higher than the regular wage. I realized that implementing this wage adjustment is not easy with your proposed process. Could I get your advice on how to address this part? Once again, thank you very much for your response.

Hello, I would like to pay workers a fixed wage regardless of their current state. In my model, each worker performs both Transporter and Resource roles, so I have set the Transport Cost Rate, Idle Cost Rate, and Usage Cost Rate all to USD 1 per minute. However, after running the simulation for 1 day (1,440 minutes), I found that some workers were not charged $1,440 as expected, but a different amount. After investigating the issue, I believe this is because the time a worker spends moving to a pickup location in response to a transport request from another server is not counted in any of the cost categories. In this situation, is there a way to configure the model so that the worker's wage is calculated based on their total presence time in the simulation, regardless of whether they are idle, transporting, or busy? Thank you in advance for your help.