0%

Checklist of prerequisites for consolidation

In order to be consolidated, projects must respect some homogeneity conditions. If one of these conditions is not respected in one of the projects to be consolidated, the consolidation will not be made possible by Albert.

Here is a list of prerequisites for consolidation:

Characteristics of common segmentations

The segmentation dimensions of the projects to be consolidated must have common characteristics:

  • The same number of segmentation dimensions (it is not possible to consolidate a project that has 2 segmentation dimensions and a project that has 3)

  • The same nature of segmentation dimensions (it is not possible to consolidate a project that has GEO and JOB segmentations with another project that has JOB and ORGA segmentations)

Common projection dates

All consolidated projects must have at least two common projection dates. Only data and analyses between these two common projection dates will be visible in the conso project.

Common calculation method (FTE or Headcount)

The projects to be consolidated must all have at least one common calculation method.

This means that :

  • A project that is only in FTE cannot be consolidated with a project that is only in Headcount and vice versa

  • An FTE-only project can be consolidated with another project that has both FTE and Headcount and vice versa. The consolidated project will then be in FTE

  • A project only in Headcount can be consolidated with another project that has both FTE and Staff and vice versa. The consolidated project will then be in Staff

What the consolidation allows

If all the prerequisites are met, then consolidation can always be done. However, it will potentially be limited by some settings.

Here are the limitations of consolidation:

Common segmentation levels

It is possible to consolidate projects with a different number of levels within a segmentation. Only the first common levels will be taken into account in the consolidation.

Optional individual data

The following optional data: seniority, names, and cost, can be present in all the projects to be consolidated or only in some of them. However, if this data is not present in all projects, it will not appear in the consolidated project.

Competencies clusters in the competency framework

A project with clusters of competencies in the competency framework can be consolidated with a project without clusters of competencies. The consolidated project will then have no competency cluster in its framework.

Similar project parameters

It is also possible to consolidate projects with different parameters (see Project settings menu).

However, only similar settings will show the whole analysis.

  1. If the projects do not have the same granularity of analysis (year, quarter, month), then Albert will consolidate the analysis with the largest granularity

  2. As mentioned in the consolidation prerequisites, if one project uses both calculation methods (FTE and headcount) while the other project uses only one, then only the common calculation method will be used in the consolidated project

  3. If the business drivers are used in a project to evaluate the workforce requirements, and another project does not use the business drivers, then the consolidated project will not show the business drivers. In the consolidated project, only the staffing targets at each projection date will be visible

  4. Projects with different analysis settings (age groups and evolution of the proportion of an age category) can be consolidated. If this is the case, the corresponding graphs will not appear in the SWP report

  5. If the consolidated projects do not have the same proficiency scale, then the proficiency scale of the consolidating project will encompass the scales of all source projects.