Reporting on Fallout

Every TBMO has a need to analyse, understand and reduce, where possible, metric value fallout from their models.  This can sometimes be a time-consuming activity tied into the month end data load with a small window of opportunity to fix before publishing to production.

Building out a strategy to reduce fallout is a fundamental requirement for any TBMO and this article is designed to support that use case and help reduce time spent on month end by providing transparency on fallout.  A report that holistically looks at fallout by model object over time and a steer towards how to resolve.

How?

To report on fallout, you will first need to create four calculated metrics.  Each calculated metric will need to be repeated for each model metric you would like to report on fallout.  The following examples cater for reporting on Cost fallout.

Cost Absolute Allocated

Generates a view on total allocated Cost metric value as an absolute:

Cost Unallocated Absolute

Generates a view on total unallocated Cost metric value as an absolute:

Cost Unallocated

Generates a view on total unallocated Cost metric value:

Reporting

You are now ready to start reporting on fallout.  Suggest you start simple and evolve over time as once operational you will start to understand what’s needed to best support your needs.

I would start by creating one table, within this table you should pull into the…

• Rows, each field contained within the allocations out of the object your reporting fallout against, the
• Values would be the new “Cost Unallocated” and “Cost Unallocated Absolute” calculated metrics and
• Columns would be Months

You can then apply a total column and filter out zero values for your holistic view on fallout.

This table will give you the necessary information to analyse fallout and steer on root cause.  To cover your whole model, you will need to replicate this for each model object you intend reporting against.

This will give you a great base to start with, evolving with visual aids, KPI’s, trends over time etc can also be considered as you mature the use case.