This case study is around the implementation of a "Cost Source Override" within our model. This is in effect a mapping file that can target any Cost Source transaction across any GL Period, and allow the TBM Office to "tell it" how to allocate. No configuration required!
With model designs, there are a large number of discussions with IT Finance on all of the transactions flowing into a Cost Transparency model. Decisions are made on how to code these transactions and allocate them out to the financial layer objects with specified logic. Finance may also update some of their processes to help automate and streamline this process. The model is built with the transform/allocation logic created to send costs up and the identified issues are all resolved.
Then the next month comes along. There are transactions that do not conform to what was agreed upon with the model design. There are outliers that hadn't been considered. There are those transactions that person X forgot to do process Y and so they are not allocating as intended.
The same thing happens the following month. And the one after. No matter how robust your model design is, outliers, human error and other factors will result in fallout or the incorrect allocation of transactions in the model.
This case study goes through the process we built to handle pretty much all of these scenarios, using an override process (or mapping file). Once implemented it removes the risk that changing configuration introduces, and it also dramatically reduces the time spend in correcting fallout. We are pushing our model to production far sooner than previously through this approach.
Please reach out to me for any questions or feedback.
@Debbie Hagen - apologies for taking some time in getting a Case Study together. Hope this one is a good starter.
------------------------------
Mark Johnson
Delivery Manager - TBM Office
Origin Energy
+61 467 863 134
mark.johnson1@origin.com.au------------------------------
#ApptioforAll