KY

hi,

I am still a newbie in modelling BPM process in ARIS. Please help to differentiate the object type in organization chart as stated below:

  1. Position vs Position Type
  2. Organization Unit vs Organization Unit Type
  3. System Organization Unit vs System Organization Unit Type
  4. Person vs Person Type
  5. External Person vs Internal Person

What is the condition to use the each of an object type in orgnization chart? Your assistance will be highly appreciated.

thank you.

best regards

by Frank Weyand
Posted on Mon, 06/29/2009 - 09:07

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

 

 

0
by Ivo Velitchkov
Posted on Mon, 06/29/2009 - 09:16















































































































































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

 

0
by Shankar Ganesh
Posted on Tue, 07/07/2009 - 15:54

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

0
by Sebastian Stein
Posted on Tue, 07/07/2009 - 16:39

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.

0

Featured achievement

Rookie
Say hello to the ARIS Community! Personalize your community experience by following forums or tags, liking a post or uploading a profile picture.
Recent Unlocks

Leaderboard

|
icon-arrow-down icon-arrow-cerulean-left icon-arrow-cerulean-right icon-arrow-down icon-arrow-left icon-arrow-right icon-arrow icon-back icon-close icon-comments icon-correct-answer icon-tick icon-download icon-facebook icon-flag icon-google-plus icon-hamburger icon-in icon-info icon-instagram icon-login-true icon-login icon-mail-notification icon-mail icon-mortarboard icon-newsletter icon-notification icon-pinterest icon-plus icon-rss icon-search icon-share icon-shield icon-snapchat icon-star icon-tutorials icon-twitter icon-universities icon-videos icon-views icon-whatsapp icon-xing icon-youtube icon-jobs icon-heart icon-heart2 aris-express bpm-glossary help-intro help-design Process_Mining_Icon help-publishing help-administration help-dashboarding help-archive help-risk icon-knowledge icon-question icon-events icon-message icon-more icon-pencil forum-icon icon-lock