How to use the correct object type?

Hi,

 

the first terms are used for concrete objects in real life, the second one four groups.

Let's say, Person is "Kah Jun Yap, the Person type is "Group member of 'We love BPM'".

 

About the persons: "internal person" could be a member of the company, whereas "extern person" could be a member from a partner company.

So, you are able to create hierarchies of real existing organizations, but also to describe the meta structure of organizations. In addition you can describe the membership of real existing objects to their type.

 

Does that help?

Bye,

Frank

Hi Kah,

There is a type-level which in the IT world is often referred to as logical level, and instance level known as physical. This can be applied to all aspects of an enterprise model. When applied to business processes if we talk about "processes" we refer to logical or conceptual level and when we talk about "process instances" that is happens in concrete circumstances. That's why for project management purposes the task is actually a function instance. The same applies to IT components. You have an application system type, say SAP (logical level), and the conrete installation of SAP in server X at address Y server room Z. Similar logic applies to the organisational aspect. For example VP  is a position type and VP Marketing is a position, Regional Sales Office is organisation Unit Type and Regional Sales Office EMEA is orgnizational unit. It is very important that the method is quite rigorous about it and logical and physical object types can participate in certain models and allow only the pertinent connection types.

Hope that helps a bit.

Regards

Ivo

Interesting discussion... Let me try to extend it a bit...

If an ARIS implementation uses only Positions for Organisation Chart and only Organisation Units as actors in EPCs (ie, Position Types and Organization Unit Types are not used), is there any drawback?

In other words, given the objective of leveraging ARIS to its potential, would the above introduce any handicap?

What are the Best Practices around the usage of these objects?

Thanks & Regards,

Shankar

Yes, there is a drawback. Basically you are not directly linking your organisational structure with your process models. It would be much better if you are using the same kind of object (types) in all models. Also, make sure to "reuse" objects. So if you have an organisational unit "sales" in your organisational chart, do not create another one in your EPC, but instead reuse the one from the organisational chart.

This creates many advantages. For example, you can now easily navigate from your org chart to all processes, where this org unit is used. You could also evaluate which org units are involved in many processes, etc.