TM1 is a very open and versatile platform… sometimes to a fault.

One of the biggest challenges many TM1 COE’s face is that of coordinating multiple developers within a single TM1 development and test environment. Unlike most relational databases, TM1 has no built-in namespaces or the concept of object ownership. As a result, TM1 developers must rely on ad-hoc manual communication and an “honor system” of design conventions (e.g. prefixing or suffixing object names) to avoid collisions.

But, such manual systems do not scale very well, and collisions and miscommunication inevitably occur. At best, the result is a few moments of frustration, at worst it can mean days or weeks of lost productivity and development effort, depending on how effective your server backup and restoration procedures are.

Cubewise Pulse for TM1 completely eliminates the challenges of multi-developer collaboration, and implements an unambiguous auditable path from Development through Test and Production. Here are a few ways Pulse accomplishes that:

Embedded inside Pulse is an instance of the very popular and robust “Git” source code control technology (incidentally, it is this Git engine that powers the open-source “GitHub” repository, as well as what is used to manage the Linux kernel). Pulse tracks every change to every TM1 object, by developer and time. And, unlike manual processes that are easily bypassed, Pulse captures every add/mod/delete event, regardless of how it occured (e.g. through TM1’s UI, TI or API).