Where We Started, Where We Are
A real account of the problems we've solved building Truss and Parivarta — not a feature list, a working log.
Where It Started
Truss didn't begin as a software idea. It began as Parivarta — a five-phase operating model methodology built the hard way, across nearly a decade of real enterprise engagements: decomposing Merck's Clinical Study Management service to the task level, architecting Cognizant's global SIAM framework, leading Medtronic's 400-application migration with zero service continuity breaches. The methodology worked. What didn't exist yet was a way to make it outlive the engagement that built it.
That's the actual origin of Truss: not "let's build ITSM software," but "the governance discipline we bring to a client shouldn't quietly decay the day the engagement ends."
The Problems We've Actually Solved
Structural decay, solved at the database level
Every enterprise CMDB we've ever worked inside eventually decays — orphaned records, stale ownership, data nobody trusts enough to act on. Truss's answer isn't a policy or a cleanup process; it's a real database constraint. Every Configuration Item is structurally required to trace to a real Business Process. There is no code path that creates an orphan. The CMDB cannot lie, because the schema itself won't allow it.
Replacing "Owner: [text field]" with something real
The Parivarta Accountability Model replaces the single, meaningless "Owner" field most ITSM tools default to with six real role types — Directorship, Ownership, Management, Coordination, Business/Financial Analysis, and Analyst — each scoped to something specific and real, never floating free. A title in Truss is never just a label; it's always a checkable triplet of role, seniority, and target.
WHO/WHAT/WHEN/WHERE/HOW, grounded in ITIL v2
Business Service and IT Service are modeled as parallel concepts, not artificially nested — matching how ServiceNow's own data model actually works, not how most tools pretend it should. Every IT Service carries a full WHO/WHAT/WHEN/WHERE/HOW definition, with a RACI chart generated automatically from real PAM role assignments, never re-typed by hand.
Staging, review, and a real commit gate
Nothing in Truss writes directly to live structure. Every piece of a new client's organization — Org Units, Business Units, Services, Processes, Process Steps — passes through a real Draft → Review → Approved → Commit workflow, with the final commit gated to OSCI's own setup administrators. Structure doesn't appear by accident.
Where Things Stand Right Now
Truss doesn't have a paying customer yet. What it has is a genuinely tested architecture, real engagement experience behind every design decision, and active interest from a real prospective client. We'd rather say that plainly than oversell where this stands.
The same discipline that keeps the CMDB from decaying is the discipline we're applying to this page itself: real status, not aspirational status.
What's Ahead
The next real milestone is a unified setup experience — one continuous build spanning Organization structure, IT Services, and People, instead of three separate tools run in sequence. Alongside it: Role-Based Access Control enforcement, turning the access model we've already designed into something actually gating every screen in the application, not just a schema waiting to be used.