A new developer takes over an established TM1 system. He opens a rule file containing 800 lines of code with no comments. His predecessor is no longer with the company.
The TM1 Dokutool automatically analyzes processes and rules and generates a visual dependency diagram, rather than leaving system knowledge locked away in a single person’s code.
Why is TM1 code often undocumented?
TM1 processes and rules are often created under time pressure; documentation comes “afterward” – and in practice, often not at all. Existing documentation tools require complex code tags that are rarely maintained.
This is particularly true for systems that have been further developed over the years by a succession of external service providers, where documentation standards have varied from project to project.
What is the cost of missing process documentation?
When the person in charge leaves the company, a significant portion of the system’s knowledge disappears with them. Every new developer must painstakingly acquire this knowledge on their own.
Without the Dokutool, dependencies are only visible in the code itself; the onboarding process takes significantly longer, and knowledge transfer usually only works through a personal handoff. With the Dokutool, dependencies are visualized as a diagram, new developers get up to speed noticeably faster, and knowledge transfer succeeds even without a personal handoff.
In practice, the onboarding of new developers is shortened by about 2 days, and debugging dependencies takes about 50 percent less time.
Is your system knowledge only in the code?
We’ll check how well your TM1 processes are documented – honestly, even if the answer turns out to be “pretty good already.”
How does Dokutool generate documentation automatically?
The TM1 documentation tool automatically analyzes processes and rules – without requiring any special code tags – and generates a visual dependency diagram based on this analysis. This diagram shows which processes and cubes depend on one another.
Because the documentation is generated directly from the existing code, it is automatically kept up to date without anyone having to maintain it manually.
How can Dokutool be implemented?
In practice, the following order has proven effective:
- Select the relevant processes and rule files for the analysis.
- Run Dokutool on the existing system.
- Have experienced developers review the generated dependency diagram.
- Provide the diagram to new team members as a training aid.
- Repeat the analysis after major system changes.
The benefits are most evident when a new team member begins the onboarding process. That is precisely when the effort put into the analysis earlier pays off.
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.
FAQ
How long does it take to use the Dokutool?
Typically 1 to 3 person-days, depending on the size and complexity of the system.
Do developers have to include code tags?
No. Dokutool automatically analyzes existing code without requiring any special tags.
Will the documentation remain up to date after system changes?
Only if the analysis is run again after major changes. It does not generate itself automatically on an ongoing basis.
What is the Dokutool generally not best suited for?
For very small, straightforward systems with few dependencies, the effort is usually not necessary.
Does the Dokutool replace in-person training?
No. It significantly speeds up the onboarding process, but it does not replace professional discussions with experienced colleagues.
How does the effort compare to the benefits?
The ROI in the first year is approximately 380 percent, with 1 to 3 person-days of setup effort.
Why BI2run
BI2run develops modules like Dokutool based on actual TM1 systems, not from scratch. If an assessment shows that your system is already well documented, we’ll let you know. Feel free to contact us to discuss your situation.
Small Tools. Big Impact.
15 ready-to-use modules for your TM1 / Planning Analytics – with an ROI calculation per tool.
Get the playbook now →
