Do you document your TM1 models?
Updated: Jul 19, 2019
Let's get straight to the point.
Are you documenting your Planning Analytics (TM1) models by hand?
If yes, you might be surprised to learn that you’re doing better than most. Even if you are just documenting a portion of your model by hand, at least you’re documenting some of it!
Most of the Planning Analytics (TM1) developers and consultants that we talk to do not have any documentation for their models at all, much less complete, up-to-date or usable documentation. They’re not capturing the most basic changes to their models from day to day, week to week or even year to year.
Why are they omitting this fundamental component of TM1 development work? Usually, it’s because it’s tedious and time-consuming and not considered a vital part of the process.
But, without comprehensive documentation, it becomes extremely hard to reverse-engineer or find errors or relationships between models – representing a big risk for both developers and their clients.
So, while manual documentation is better than nothing, automated documentation is so much better.
It saves time – no more laborious manual documenting.
It gets the job done – while you get on with your work.
It gives you power – to easily find and fix errors and generate reports.
In this series of posts, we will be sharing our view on the true costs of manual vs automated documentation of your Planning Analytics (TM1) models. We hope to expose some myths, get real on the costs and reinforce the fact that:
Documentation is good
Automation is better
And, regular analysis and model audits should be the standard that we aim for.
Read on to discover more.
We can help.
To document your model right now, Click here to book a 30 to 60-minute web demo.
Are you a consultant or consultancy? Do you want to deliver QUBEdocs as a service to your clients? Click here to start the conversation with us.