Profile picture for user andrea.zarembova

Last time I´ve shown you how to create your start model using structuring model. Today I will show you how to create an Organizational chart. Organizational chart describes organizational structure within the company. It represents important roles of the organization visible and is used for internal and external communication. It consists of elements and relationships between them.

 Basic elements of an organizational chart are:

  • Organizational unit that is used to describe organizational departments and can be assigned to roles and persons.   Organizational unit
  • Position is used to describe position defined by job description and is assigned to persons.  Position
  • Role is similar to position but less formal and can be assigned to multiple persons.  Role
  • Internal person that refers to specific person/employee.   Internal person
  • Location describes local subsidiary (physical place).    Location

The most important relationships in organizational chart are:

   1. Position is organization manager for organizational unit (It answers the question who is responsible for whom?)

Organization manager

   2. Organizational unit is superior for another organizational unit (It answers the question who is superior or inferior?)

superior

   3. Internal person occupies the position (It answers the question what communication channels exist?)

occupies

 

Check the training video to see how to create the organizational chart. The organizational chart in training video might look like this:

Organizational chart

In addition to Organizational chart, ARIS Basic also supports other model types: process landscape, BPMN, Event-driven process, System diagram, Data model and Structuring model.

Model types

 

by Prabhu Chandrasekeran
Posted on Thu, 12/10/2020 - 20:30

I am working on an organizational chart for a large organization where they have a specific position say "Project Manager" or "Sr Project Manager". These two positions are one of the common positions within different departments and teams. What is the recommended approach for handling a common position type but used within different teams and departments?

1. Should I create an object called "Project Manager" and kept using the same in multiple departments. This would lead to 10s of reporting relationship to different Department Heads.

2. or Should I create several objects such as "Procurement Project Manager", "Finance Project Manager", Capital Project Manager".

Please help!

 

1

Featured achievement

Genius
You like to help others solve their problems by answering questions.
Recent Unlocks
  • KF
  • KH
  • RG
  • Profile picture for user Vee_ARIS
  • Profile picture for user smarty
  • PacMan

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