Models

Hey Jitesh, 

I read your query and below are a few of my thoughts. If you need a detailed answer, feel free to reach out to me at deeptilad@gmail.com

• I'm not sure if you can use IT Architect for Simulation. You will need a Business Architect Application with Simulator add-on or an ARIS Simulator plus admin rights. Once you have this in place, you will notice the simulator icon on the left module tab.
• ARIS Business Simulator gives us a Dynamic evaluation method for our models and data. For example, taking into account transfer and wait times enables overall process execution time to be calculated: Parallel process flows are included, throughput times and time-referenced bottlenecks are identified
• You are right about the attributes...you can have as may attributes as you want which are relevant for your evaluation. You can capture attribute at mode level or o bject level. You can have time attributes (Static, orientation & processing), cost attributes (Total costs, material cost, personal cost, operating costs, energy cost etc.). In addition to these you can also have attributes on organizational elements (shift, no. of people, resource allocation) or Technical elements as well.
• It depends on what you want to achieve by Simulating the process. To define an objective is first and the foremost thing you should do before starting to simulate your process.
• Pick up one simple process at a time and try to simulate that and see if you get the results you desire. You can slice and dice the data as per your requirements. This is all about "what-if" scenarios you can create.

Hope this gives you some clarity. Feel free to reach out.

Regards,

D

Technically there are no mandatory attributes. That means the simulation will work even if you don't maintain any attributes. But then the usefulness is limited. While you can check if the model is syntactically correct, simulation will not provide you with information about throughput times or resource utilization. For results like these you need to maintain times at functions (processing time being probably the most common one) and -- as a limiting factor -- the amount of resources which are available and which are required for function execution. For decisions in the process flow it is also worthwhile to maintain the probabilities of the decision outcomes (connections or events after XOR and OR rules). To make a model even more realistic you can define process instantiation patterns for start events (which is more sophisticated than frequencies) and availability times for resources. Both of these are done by assigning schedule models to the respective start events or resource objects.

Whether you want to maintain all that data depends on your analysis goal and on the conditions in the reality represented by the model. As mentioned before, if you only need to check if the model is syntactically correct you do not have to maintain any attributes. If your resources are available 24/7 you don't need a shift calendar. And so on.

Regarding all the details you can find a lot of information in the ARIS Help. See "Help > Help topics" and then "Optimize and control processes/strategy > Simulate processes".

Hey Deepti, Thanks alot for the information,, I will start this experiment soon, Will need some more help in doing this right.. Catch you back soon..

Hey Deepti, Thanks alot for the information, I will start this experiment soon, Will need some more help in doing this right.. Catch you back soon.

Hi,

Thanks for your help and support