Rajiv Gupta
August 13, 2026
How Marmon runs transformation across its autonomous businesses on Axiamatic, from a Dynamics 365 ERP program at Marmon Plumbing & Refrigeration to Marmon Rail's phased modernization, capturing what status decks miss.
Marmon's operating model gives each business genuine independence: its own systems, its own integrators and its own transformation calendar. That autonomy is why the portfolio performs. It is also why delivering ERP, CRM and shared-services programs across the portfolio is hard. Several transformations run at once, supported by lean central teams. Each program generates enormous effort without a shared mechanism to make that effort compound.
Inside the programs, the failure pattern was structural rather than dramatic:
The mandate Marmon's transformation leadership set for Axiamatic was blunt: don't add dashboards. Surface the exceptions, route each one to a named owner, and make every program cheaper and faster than the one before it.
Axiamatic operates inside Marmon's programs as both platform and embedded delivery partner. It connects to workshops, CRP sessions, plans, specifications and Azure DevOps. It works to one principle agreed with Marmon's transformation leadership: report exceptions with owners, not dashboards with everything.
What it does: During CRP execution, every blocked test, live fix and net-new requirement is captured from the room as it happens. Each is logged with its workaround and routed to named owners for closure in Azure DevOps. Daily exception digests replace end-of-week compilation.
Why it matters: The failure that used to resurface at go-live now has a paper trail and an owner within hours. Leadership reads a short exception list instead of a sprawling risk board.
What it does: It builds named-user training cohorts from actual proficiency and role impact. It converts task recordings into SOPs, generates multi-week training plans directly from CRP agendas, and tracks adoption and sentiment in the training environment to flag at-risk users.
Why it matters: Training hours go where they change the outcome. Strong performers aren't burned on content they already know. End users who first see the system before UAT get a concrete, dated plan.
What it does: It generates change-request analyses ahead of the final CRP, comparative schedule reviews across finance and supply chain, day-by-day cutover runbooks with dependencies, and communications plans. These come from program context in minutes. Self-serve deep research exports straight to Excel and PowerPoint.
Why it matters: Program leadership judged these analyses unambiguously worth the investment. They now arrive before decisions are made, not after, and leads run their own questions without queuing behind anyone.
What it does: At Marmon Rail, phase-zero value drivers were codified as the program's foundation. They sit alongside a deliberately conservative financial model grounded in how the business actually operates. Every later phase is judged against this reference.
Why it matters: When phases one through three force trade-offs, they are made against the original value case, not against the loudest voice in the room.
The operating principle, set jointly with Marmon's transformation leadership: leadership shouldn't consume dashboards, it should receive exceptions. Each one comes with an owner, a workaround and a closure path in the system of record.
Marmon Rail's CRM shipped in the first quarter of 2026. It moved through hypercare to a stable steady state within weeks, and the phased ERP program is now progressing across finance and supply chain on the same instrumented foundation.
At Marmon's shared services transformation, what the data teams once had to chase now arrives automatically. Weekly delivery digests drove roughly a threefold increase in engagement and are expanding from one group to five.
At Marmon Plumbing & Refrigeration, the program has advanced through its CRP cycles into final execution. Exception governance is live, a day-by-day cutover runbook is drafted, and a Q4 2026 go-live is in sight.
Every workshop, decision, exception, SOP and training asset is captured on one platform. Because of that, each Marmon business inherits what the last one learned. The first Marmon Plumbing & Refrigeration implementation is deliberately being run as the template for six divisions to follow.
PMO leaders replaced sprawling risk registers with short, owner-assigned exception lists and decision-point analyses. They shifted their time from compiling status to closing gaps, and every exception is traceable to its resolution in Azure DevOps.
OCM and training leads work from cohort-level plans generated off the real, configured system. They have SOPs built from task recordings and communications sequenced to cutover. They flag at-risk users from actual practice-environment behavior instead of intuition.
Signal, not volume. Governance is built around the small set of things that changed or broke, each with an owner and a closure path. It replaces boards that catalog everything and drive nothing.
Every program funds the next. The first division implementation becomes the template for six, Rail's phase-zero value case anchors every later phase, and each Marmon business inherits the portfolio's accumulated delivery memory.
Axiamatic is the agentic control plane for enterprise transformation. Its platform continuously monitors complex programs, surfaces risks early, and delivers the context and recommendations every stakeholder needs to act. This lets enterprises run transformations with a speed, visibility and predictability that human teams alone cannot achieve.
Backed by Greylock Partners and Bessemer Venture Partners, Axiamatic is trusted by leading Fortune 500 companies, large enterprises and leading system integrators to ensure the success of transformation programs.
To learn more about the platform, visit axiamatic.com or reach out at hello@axiamatic.com.
