A report needs to be updated at the turn of the year. The colleague in charge does not have admin rights and has to wait three days for IT support. The report is published too late.
The TM1 View Generator organizes cube view names according to a clear convention and documents their purpose, rather than allowing views to be created ad hoc and without a recognizable structure.
Why Do Cube Views Become a Bottleneck in TM1?
Views are usually created on an ad hoc basis, for a specific analysis or department. Without a consistent naming convention, dozens or even hundreds of views accumulate over time, many of which were intended to be temporary but are never removed.
The more departments that need their own reports, the faster the number of views grows—often in parallel and without anyone taking charge of establishing a common structure.
What is the cost of a lack of structure in Cube Views?
Because no one except the IT department has the big picture and the necessary permissions, even the smallest adjustment depends on those same few people.
Without the View Generator, views are usually created without a recognizable structure or purpose; every modification requires an IT ticket; and temporary views often remain in place permanently. With the View Generator, however, views are named and documented in a structured manner, business users maintain them independently, and outdated entries are automatically cleaned up.
In practice, the view generator saves an average of 2 hours of IT work per month and makes system maintenance scalable and decentralized.
How does the View Generator structure Cube Views?
The View Generator specifies a clear naming convention for views and automatically documents their purpose. Outdated entries are identified and can be cleaned up without anyone having to guess whether a view is still needed.
Business users can then maintain their relevant views on their own, within clearly defined limits, but without having to go through a ticket system.
How can the view generator be implemented?
In practice, the following order has proven effective:
- Review existing views and categorize them by relevance and usage.
- Establish a naming convention for views.
- Require the use of the View Generator for new views.
- Gradually clean up outdated views.
- Enable business users to maintain their own views independently.
The final step has the greatest impact: Only when business users are truly allowed to perform maintenance on their own does the number of IT tickets drop noticeably.
Small Tools. Big Impact.
15 ready-to-use modules for your TM1 / Planning Analytics – with an ROI calculation per tool.
Get the playbook now →The key figures at a glance:
Basis: our playbook “Small Tools. Big Impact.” (2026), internal ROI formula: ROI = (Business Value − Implementation Cost) ÷ Implementation Cost × 100%, based on 1 person-day = 1,000 euros.
Glossary
A brief explanation of a few terms from this article:
FAQ
How long does it take to set up the ViewGenerator?
Typically 1 to 3 person-days, depending on the number of existing views.
Can business users then manage views without admin privileges?
Yes, within defined limits, business users can customize relevant views on their own.
What happens to old, unclear views?
They will be identified during the implementation process and gradually corrected or documented.
In what situations is the ViewGenerator not really worth it?
For very small systems with just a few clearly named views, the extra effort is usually unnecessary.
Does the view generator replace IT when it comes to complex customizations?
No. It handles routine adjustments, while complex structural changes remain the responsibility of the IT department.
Why BI2run
We build modules like the View Generator based on actual TM1 systems, not from scratch. If an assessment shows that your views are already well-structured, we’ll tell you so.
