Delta reporting is a way to capture net differences between two different datasets, typically between a given scenario and the baseline, and a standard delta report use case requires that property keys for properties upon which one wants to cut/report are identical across datasets.
While using the Cloning method you can compare different scenarios side by side and OrgVue Branching allows scenario modelling in live baseline and charts the net effect of changes, sometimes there is benefit in using the simpler approach of Deltas to visualise differences between datasets.
This is the goal to be achieved in running this delta report in this instance
I am working in an Organisation structure re-structuring scenario and I would like to show the As-Is and To-Be Status for the same metrics in one report but the assumption here is that As-Is and To-Be are separate datasets as I don’t want to use “Cloning”. The kind of reports I would like to create are e.g.
- As-Is and To-Be FTEs by Depth
- As-Is and To-Be Outgoing Count by Depth
In the right situation, delta reporting can have advantages over cloning in that:
- It is much simpler to compare as is with different To-Be datasets
- It is faster than cloning – no potential Excel involved to create an ‘As Is or To Be’ property
- Cloned nodes need to be updated manually to reflect changes in the ‘Other’ dataset i.e. you’re duplicating data, which needs to be upheld in two places.
Note again that it is a prerequisite of this method that property keys for properties upon which one wants to cut/report are identical across datasets.
The steps to take here are:
- Complete the work on the AsIs and ToBe datasets
- Within the scenario dataset, choose the baseline dataset from the Delta drop-down list
- The visible dataset title will update to reflect the Delta action (note keyword "vs.") and there will be a loading data message shown
- Run a recalculate after loading the second dataset.
When loading a dataset, you will see a message for loading the delta, but you still need an explicit recalculate - button inside dataset, top right, circular arrow - before differencing will appear e.g. in the chart tools.
- Navigate to Chart view and create charts showing net differences between the two datasets.
To answer the first question (As-Is and To-Be FTEs by Depth) we set the chart values to be CNT FTE by Depth. Choosing the Split by Dataset option will determine if relative differences are shown (Example One) or whether the explicit values are shown instead.
(Larger versions of the screenshots below are attachments to this article.)
Note in the explicit approach, OrgVue holds an internal flag node._records which is usually 1, for the imported dataset this is set as -1 so the comparison record will show as negative as this flag is applied to values in the imported (second) dataset.
A possible downside of the approach above is that the bars appear as positive and negative, rather than both positive, as you will have seen in the examples:
If this is a concern, it is easy enough to take the cloning route instead by:
1. Adding a property to both To Be an As Is datasets (call it e.g. Dataset Type)
2. Populate it with ‘To Be’ in the To Be and ‘As Is’ in the As Is
3. Paste one of the datasets into the other, taking only the properties that want to be compared (is the typical approach)
4. ... then Dataset Type is a property that can be used as a By/Split By in the chart controls.