How QUBEdocs solves the top 5 challenges for analyst and developers
Here you have it - our top 5 challenges that QUBEdocs will solve if you use TM1 or Planning Analytics!
1: Understanding and learning a model
SITUATION: You have inherited a TM1 model and you have no idea of how it works. The model has been in use for several years and it is now up to you to support and develop it. SOLUTION: You use QUBEdoc’s model diagrams to explore and understand the data flows in the model. You drill-down to specific areas to answer your questions and use the keyword search to query terms that you have heard people use when talking about the solution. Before long you become the expert on the model. You also use the QUBEdocs framework to organize the models, centralize other documentation and maintain a glossary of terms so that what you have learnt can be easily communication to others.
2: Assessing the impact of model changes
SITUATION: Your boss has tasked you with making changes to the sales model, but the last changes did not go so well. You didn’t understand the full impact that these would have and you ended up working late into the night resolving the issues that arose. SOLUTION: You navigate to the Sales cube in QUBEdocs and look at the dependent cubes and processes. You instantly see in the diagrams that there is an additional flat file that gets loaded into the sales cube for one business unit and that the model is linked to a downstream KPIs cube used by the Exec team. Both considerations had not factored into your thinking. You will need to consider these when making changes so you are very pleased that you had this insight.
SITUATION: You are experiencing a new issue with the Capital Expenditure report in the production environment. Everything looked okay when you migrated some development work over but perhaps this report was overlooked in testing. You suspect it has something to do with the rules. Where do you start to find the problem?
SOLUTION: You run the change analysis report in QUBEdocs and you set it to compare today’s production model against what it looked like a week ago. You navigate to the Capex cube and notice differences in the dimension subsets used by the model. While the fix is easy you can’t help but think that it would have been difficult to pinpoint if you didn’t have QUBEdocs available.
4: Cleaning up and rationalising old models
SITUATION: A TM1 model has been in place for six years and over this time it has become very messy. There are 400+ TI processes and several models that nobody knows about. You are too scared to delete anything in case you break it. But you need to free up some of the memory that the model uses. SOLUTION: You launch QUBEdocs and navigate to the stats page to find out which cubes consume the most memory. You spot some large cubes that you have not come across before. You dive deeper and it becomes obvious that they are no longer in use. From here use the version repository report to identify old objects that haven’t been updated for a long time and then use the predefined search queries to perform a redundancy analysis.
5: Deploying the correct files
SITUATION: You worked on a Headcount model half a year ago and have forgotten many of the changes that you have made and what’s more, changes have occurred in other related areas. The Manager has given you the greenlight to take the model over to production but you can’t be sure of what to migrate across. SOLUTION: You navigate to the version repository in QUBEdocs. You compare what is on the development server to production. It identifies all the areas that have changed, making it a simple task to package the new files into a deployment plan to migrate to production. You also save the deployment plan in QUBEdocs for later reference, along with the backup of the source files.
Why don't you see for yourself if QUBEdocs can solve these problems and take it for a free two-week test drive: http://www.qubedocs.com/qubedocs-cloud