7-year operating partnership. ERP operations continuously. 3,956 tickets resolved across the engagement.

A national services leader is the largest commercial landscape services company in the United States, with operations across hundreds of branch locations and a complex JD Edwards EnterpriseOne footprint supporting field operations, finance, HR, and supply chain. Allari has been their JD Edwards production support partner on a multi-year continuous engagement. Recorded in the Allari engagement ledger: 3,956 lifetime tickets and 6,852 hours delivered.

Scope of the engagement

• 24/7 JD Edwards EnterpriseOne production support — incident response, ticket triage, root-cause remediation, environment management.
• CNC and security work, configuration management, and ongoing JDE vulnerability management (scanning, remediation, ESU coordination).
• Outcome Team with senior Allari JDE engineers, held by the same team across the contract for continuity.
• OpenBook® transparency — the customer’s core team sees every ticket, every hour, and every root cause in the engagement ledger.
• Monthly compression review with senior-engineer sign-off on the recurring-work eliminations carried into the next month.

What the core team got back

Before Allari held the Run layer, routine JDE production support and vulnerability management were absorbing significant capacity from the customer’s core team. A flat-fee outsourcing model did not give them clear visibility into what was being done, and the volume of routine work was unpredictable. Under the current engagement, Allari holds incidents, environment work, and steady-state operations on the JDE estate; the customer’s core team holds strategy, transformation, and the next-generation roadmap. This is the Build-Run Separation in production form.

How we run it

The engagement is consumption-based with OpenBook® reporting and is held by an Outcome Team. Every ticket is categorized by root cause; recurring categories are taken into a permanent-fix backlog and retired across successive months. Coverage is 24/7 for tier-1 production incidents with a 15-minute response SLA, and the same senior Allari engineers carry the engagement across years — not a rotating queue.

Why it matters

The customer’s multi-year retention is the durability proof for the deflationary model at public-company scale: the same team structure that runs a mid-size JDE estate runs a public-company JDE estate with hundreds of branches without changing shape. The Build-Run Separation is the structural reason the customer’s core team can hold transformation while Allari holds the Run.

Book a working session · JD Edwards production support · All case studies

See what the monthly statement looks like →