Defining your Org Modelling Project – Orgvue Knowledge Base

Using Orgvue’s org modelling solutions:

Your baseline dataset defines the ‘as-is’ organization.
The ‘to-be’ organization is modelled through position-level ‘Actions’: positions being added, flagged for removal, changed, or kept unchanged. ‘Modelling Properties’ are used to define positions. For example, the function it belongs to, its geographic location, and the cost associated with the position.
Impact analysis – differences between the ‘as-is’ organization and the ‘to-be’ organization – are automatically calculated and visualized.

There are two stages for defining your assignment and setting-up the solution to deliver against your requirements. By selecting the links below, you can understand each in more detail.

Establishing the baseline

Customizing the modelling solution

What is the scope of the project? *

Should a People Dataset or a Positions dataset be used?

What properties are needed in the baseline dataset?

How can the baseline data quality be checked?

Should we use a static, or a rolling baseline? *

Agreeing the baseline

How should modelling ‘actions’ be labelled? *

Is time tracking required; what increments and initiatives should be reported?

Should any values be added to my modelling properties?

Which change impacts should be reported? *

What ‘change reasons’ should be specified?

Which elements should be included the cost property?

How should position costs be entered?

Is time tracking required and what increments should be reported? *

Note: Items marked * are only relevant if the Advanced Org Modelling Solution is being used.

The Org Modelling Guided Experience provides a workflow for the practical steps involved. Where the Advanced solution is required, these requirements will be addressed through the set-up process with the involvement of the Orgvue Services team.