Experiences of organization charts?

3 posts 0 new
Log in or register to post comments.

Experiences of organization charts?

We are looking into keeping the "master" orgchart in QPR EA, including individual persons. Has anyone done this, and what are the experiences? I'm especially interested in:

- the ease of keeping the orgchart up-to-date when people join, leave, switch to another unit, reorganization happens etc.

- splitting the chart into several layers, i.e. top-layer shows only a few boxes (org. units), and then user can (in portal) drill-down by clicking each box down to individual names

- searching for a person, function, title etc in the portal, i.e. the ease of finding to which unit a specific person belongs, who is his/her boss, who work under a certain person etc.

- the understandability of orgcharts to people who are not familiar with the specific notation

but also any other comments are valuable.

Hi Timo,

Organization charts can be utilized and configured in different ways, depending on customer needs. I'll give my comments on your questions below with the assumption that we are talking about QPR ODM-based models:

- Organization charts are made of "Business Actor" items that represent both organization units and persons. I would recommend that you use organization diagrams to show organization unit structures, e.g. hierarchies between business units and their managers, using the nested modeling approach (i.e. setting elements on top of each other, thus creating relations between them appropriately). As there can be a lot of personnel under business units and changes in personnel assignments, I would use a navigator view to show and place persons under appropriate organization units; navigator views are very convenient way of showing larger element hierarchies and they enable structural modeling in a "drag & drop" manner. 

- For enabling such a "drill-down" function where you can click on a organization unit to show the sub-unit hierarchy you can configure "Business Actor" elements to act as diagram elements. Probably you want also the substructure of an organization unit to be visible at the "top-level"; for enabling such behaviour you can configure the "Business Actor" element's graphical properties to show value of a special "Show diagram contents" field. Other possibility would be to use nested modeling at the top level to show a simplified contents of the sub-unit structure, and then at the diagram level represent, possibly more complete, design of the sub-unit organization.

- At the moment, QPR Portal has a basic keyword based search functionality; if more advanced search functionality (e.g. based on metadata fields as you described) is needed, you can contact our technical consulting team.

- Using the nested modeling approach, drill-down functionality and organization specific "landing pages" organization hierarchies can be communicated efficiently through the organization.

Best regards,


My 2 cents to share: I had some expierience with 3 different types of organizational hierarchies.  

  • Departmental is the most common one that endusers will recognize and is maintained by an HR department: when modeling this and to keep maintenance low only vizually model using departmental names, not person names.  Adding a manager attribute to that department object and vizualize the managers name in a smaller font within that 'department box' has always been sufficient. If you want to capture names of individual personel use another (cardinality N) attribute to capture all other staff within that department. You do not have to vizualize them as a search on a name will result in the related department. When using a top-down hierarchy chart you can add 'staff deparment' functions using horizontal connector. When doing that in a nested object hierarchie you can give 'staff' departments a different color.
  • Management reporting charts are only practicall for analysis. It vizualizes via connectors how the accountabilities and responsibilites are between individuals. In a process, project or matrix organization it is possible to see people with multiple parents. In this case a department can be an attribute of the person. Arrow connectors can have different colors to depict an accountability or responsibility.
  • Juridistic hierarchies overviews are especially used with larger companies who consist of multiple juridistic entities with shared ownership. These organizations are modeled with their legal names and their relationships can be modelled as connectors with a property (ie. name attribute) showing the 'percentage ownership' as an attribute.