Model and Simulate distances between locations

The transmission time attributes are not evaluated by the current simulation product.

In order to express that employees have to walk to other locations you could add actual walking activities at which you can set a processing time for the time it takes to walk to the location. This would also make it obvious for somebody who does not look at the object attributes that there is some time consumption between the value-adding activities.

Hello Mr. Angeli,

thought about that solution, too. But I didn't want to mix up the processing times of actual activities with the ones for walking between the locations.

My goal is to see a metric(distance,time or cost) at the end of simulation that only represents walking, so that I can make a comparison with different process chains.

Is there maybe a way to add an addtional attribute to the walking activites, so I can filter for example the processing times only for walking activites.

I know that you can for example filter KPIs for particular locations or time spans in PPM and MashZone.

Thank you so far

Best Regards

Simon

Hello Simon, I work at Lanner we provide the simulation software used by the ARIS Simulator. One approach you could try to keep the statistics separate for 'walking' and for 'processing' is to use the SETUP activity to represent the walking times to each activity. This will of course only work if the SETUP is not already in use. Hope this helps, Geoff

Hello Mr. Hook,

SETUPs for activites are news to me.

Could you give me a brief introduction what they are, what they are used for and how i define them?

Best Regards

Simon

 

Geoff refers to what is called orientation time in ARIS. At activities there is an attribute called 'Orientation time' which can be used to define a time period for the setup of the activity. This time period elapses before the period starts which is defined by the attribute 'Processing time'. On the result side of the simulation, orientation times are displayed in a separate column besides processing times.

If you set an orientation time this could be interpreted as the time the person or role who carries out the activity is required to walk to the location of the activity.

Ah okay. At the moment I used the static wait time, because It wasn't in use yet. But the orientation time seems to be the better solution.

Thank you both

Greets by

Simon

 

The orientation time is definitely better because it requires the resource to be present. For the static wait time no resource is needed.

Simon, just for information the Hochschule Darmstadt also has our WITNESS simulation software. You can check this out on Lanner.com.   If you are interested please contact me on my business email; ghook@lanner.com and I can give you the details of the professor.