Part 5 – The Birth of Tantum
When Ownership Became Unavoidable
The previous story ended with a realization that could not be ignored.
No matter how much value TPMS delivered, as long as the software belonged to someone else, the brand, the margins, and the future would too. Execution alone would never be enough. Survival through delivery had reached its limit.
If TPMS was to stand for anything enduring, it would have to own the product.
This story captures how that realization became Tantum.
The First Spark
An Unexpected Proving Ground
The first real opportunity did not come from a corporate boardroom, but from an operational pilot.
During a CCPM engagement with a large Indian multinational, TPMS was introduced to one of their customers: the Indian Naval Dockyard at Visakhapatnam. The dockyard selected TPMS for a pilot implementation.
Over four months, using a standalone CCPM planning tool and custom-built modules for managing cross-project priorities, the pilot delivered clear results.
The response from the dockyard was decisive. TPMS was asked to prepare a detailed project report, which was circulated across other dockyards and senior naval leadership. A procurement process for enterprise software was initiated.
That process collapsed when the quoted price from a U.S. vendor proved unaffordable.
The Question That Changed Everything
A Challenge, not a Request
Soon after, Naval Dockyard Mumbai invited TPMS to run a similar pilot. Once again, using a basic desktop planner, the results were replicated.
Then came the question that changed the trajectory of TPMS:
“Can TPMS develop enterprise-grade software within our budget?”
There was no funding behind the question. No safety net. No product team waiting in reserve.
TPMS said yes.
Building Tantum
From GEMS to DRMS
That commitment marked the birth of Tantum, what was initially called GEMS — the Good Execution Management System.
GEMS was designed to be configurable and intuitive, allowing each dockyard to see its own language and logic reflected in the system. Naval Dockyard Mumbai referred to its projects as “Refits,” and the system was renamed DRMS — the Dockyard Refit Management System.
In building the system, TPMS embedded everything it had learned the hard way.
Priority logic that could not be gamed.
Clear accountability across roles.
Built-in support for people development through role hierarchy and mentoring.
And the seamless integration of non-project work into execution priorities.
This was not software layered on top of thinking.
The software was the thinking.
Validation and Limits
Growth Without Compromise
In 2012, Naval Headquarters issued a directive to roll out DRMS across all dockyards.
TPMS declined.
The surrounding ecosystem and operating norms did not align with its values.
But the story did not stop there.
The DRMS experience travelled. It reached Alstom, a manufacturer of hydro plant components, and Godrej Precision Systems, known for its work on the BrahMos missile project.
Each engagement sharpened Tantum further. Alstom pushed the platform toward greater technological robustness. Godrej Precision Systems revealed the need for Tantum to support multiple planning strategies, not just CCPM.
If Naval Dockyard Mumbai marked Tantum’s birth, Godrej Precision Systems became its crucible.
Why This Story Matters
Part 4 revealed the limits of borrowed power.
Part 5 marks the moment TPMS chose ownership — of product, of thinking, and of responsibility.
Tantum was not built to scale consulting.
It was built to protect value.
What follows is the final chapter — where everything learned so far meets the present tense.