PUBLIC TRANSIT · JDE ENTERPRISEONE 9.2 · TOOLS RELEASE + SQL SERVER MODERNIZATION

Zero-disruption Tools Release upgrade. Ahead of schedule.

A major US public transit authority — 2,000+ employees, JDE EnterpriseOne 9.2 on SQL Server — needed to advance both its Tools Release and its database platform in a single planned window. Allari®'s CNC team executed the upgrade from TR 9.2.6.3 to 9.2.8.1 and migrated SQL Server from 2016 to 2022. Zero-disruption cutover. Completed ahead of schedule. The consumption model returned the schedule gain directly to the authority's budget. See methodology.

SECTOR: Public Transit · PLATFORM: JDE EnterpriseOne 9.2 · TOOLS RELEASE: 9.2.6.3 → 9.2.8.1 · DATABASE: SQL Server 2016 → 2022

Major US public transit authority · 2,000+ employees · JDE EnterpriseOne 9.2 on SQL Server. The authority operates a multimodal network serving millions of passengers across a major metropolitan region. Public-agency governance standards require that all infrastructure changes execute within pre-approved maintenance windows with zero unplanned downtime.

§01 — Diagnosis

Version currency deferred — two stacks exposed

The authority's JDE environment carried two compounding version-currency gaps that could not be addressed independently. The Tools Release remained at 9.2.6.3 — multiple releases behind Oracle's current recommended posture — while the SQL Server database platform sat on 2016, a version beyond its mainstream support horizon. Neither gap was immediately operationally dangerous, but the combination created an accumulating risk surface: security exposure on the database layer, functional limitations from the older Tools Release, and a widening distance from Oracle's certified support configuration.

JDE Tools Release at 9.2.6.3 — multiple releases behind the current certified posture. New functionality, security hardening, and performance fixes introduced in 9.2.7.x and 9.2.8.x were unavailable.

SQL Server 2016 had passed its mainstream support window. Running the JDE database tier on an unsupported SQL Server version created compliance exposure and deferred access to SQL Server 2022 performance and security improvements.

The authority required the core application to remain on 9.2 update 6 throughout the upgrade — only the Tools Release and database platform were to advance. Custom objects, integrations, and business processes had to survive the transition unchanged.

Transit operations cannot absorb unplanned downtime. The entire upgrade — Tools Release and SQL Server — had to execute within a pre-approved maintenance window with a documented rollback path and zero unplanned impact to the authority's 2,000+ person workforce.

§02 — Intervention

Planned-window execution — both stacks advanced simultaneously

Allari's CNC team and Project Manager embedded directly with the authority's internal technical staff. The execution plan staged the Tools Release upgrade and SQL Server migration in non-production first, validated all custom objects and integrations, then executed cutover in a single planned maintenance window. The authority's team retained full visibility throughout.

TOOLS RELEASE MIGRATION

• → Upgraded TR from 9.2.6.3 to 9.2.8.1
• → Application held at 9.2 update 6 throughout
• → All custom objects and modifications validated
• → Integration compatibility confirmed pre-cutover

SQL SERVER 2022 MIGRATION

• → Database platform advanced from SQL Server 2016 to 2022
• → Performance optimization applied at migration
• → Security hardening and compliance alignment verified
• → Full testing and validation cycle completed

PLANNED-WINDOW EXECUTION

• → Non-production staging environment upgraded first
• → Documented rollback path maintained throughout
• → Cutover executed inside pre-approved maintenance window
• → Zero unplanned disruption to transit operations

POST-CUTOVER SUPPORT

• → Allari monitoring active through post-cutover stabilization
• → Emerging issues resolved on contact — minimal volume
• → Knowledge transfer to authority's internal team
• → Documentation of all changes delivered on completion

CONSUMPTION-DRIVEN COST DISCIPLINE

Allari's consumption-driven model aligns cost directly with scope consumed. The authority contracted for the upgrade scope; Allari executed ahead of schedule with fewer post-go-live issues than planned. The schedule gain translated automatically into cost compression — the authority paid for what was consumed, not for time originally allocated. For a public agency operating under budget governance constraints, this structure provides a defensible cost outcome without renegotiation.

§03 — Verified Outcomes

Version-currency posture achieved — zero disruption

Zero disruption

Tools Release and SQL Server migration executed inside a single planned window with no unplanned impact to transit operations.

Ahead of plan

Project completed earlier than the contracted window. Post-go-live support demand was far less than initially estimated.

9.2.8.1

Authority advanced from 9.2.6.3 to 9.2.8.1, reaching Oracle's current recommended Tools Release posture for JDE EnterpriseOne 9.2.

SQL Server 2022

Database platform advanced from end-of-mainstream-support SQL Server 2016 to SQL Server 2022 in the same planned window.

Minimal

Issues encountered post-go-live were fewer than anticipated. All were resolved promptly by the Allari CNC team with no escalation.

Consumption

Ahead-of-schedule delivery returned budget to the authority automatically — pay-for-consumption model, no renegotiation required.

Maintained

Core application held at 9.2 update 6 throughout. Custom objects, integrations, and business processes survived the upgrade unchanged.

Public-agency grade

Planned-window execution, documented rollback path, full knowledge transfer — consistent with the authority's public-sector accountability standards.

Beyond the upgrade window

What the authority keeps

VERSION-CURRENCY POSTURE

The authority now operates on Oracle's current recommended Tools Release configuration for JDE EnterpriseOne 9.2, with a SQL Server 2022 database platform that carries mainstream support through 2028 and extended support beyond. The version gap that accumulated over prior release cycles has been closed.

GOVERNANCE-GRADE DOCUMENTATION

Every change executed during the upgrade is documented and transferred to the authority's internal team. Public-sector accountability requires that infrastructure changes be auditable — the engagement produced a documented record of all modifications, validated configurations, and post-cutover test results.

CONSUMPTION COST DISCIPLINE

The consumption-driven model provides a repeatable cost structure for future Tools Release upgrades. When Allari executes efficiently, the authority spends less — automatically. No renegotiation, no change orders for scope that didn't materialize. Budget governance is built into the contract structure.

How these outcomes were measured

Methodology

Zero-disruption claim

Derived from Allari's project record and post-cutover support log. "Zero disruption" means no unplanned outage or service interruption occurred outside the pre-approved maintenance window. The authority's internal team confirmed this outcome in post-project review.

Ahead-of-schedule claim

The project completed prior to the contracted window end date. "Ahead of schedule" reflects the difference between the planned cutover window and the actual completion date as recorded in Allari's project management system.

Minimal post-go-live issues

Post-cutover issue volume was below the baseline estimated at project scoping. "Minimal" reflects the qualitative assessment in Allari's post-project review, not a specific ticket count. All issues raised were resolved by the Allari CNC team without escalation.

Consumption cost discipline

Under Allari's consumption-driven model, the authority was invoiced for hours actually consumed, not hours originally scoped. Because the project completed ahead of schedule with fewer post-go-live issues than estimated, the final invoice was below the original estimate. Specific cost savings figures are not published at client request.

Caveats

Single-engagement measurement at one public transit authority. Outcomes on Tools Release upgrades vary with environment complexity, custom object volume, integration scope, and organizational change-control requirements. Full project record available under NDA on request.

Source Control & Provenance

Client identity withheld at customer request. Engagement details, metrics, and outcomes verified against Allari's internal ticket database and customer-cleared reporting. Methodology and supporting evidence available under NDA on request. Published: 2026-03-01. Last updated: 2026-05-22.

Want what A major US public transit authority has?

Zero-disruption Tools Release upgrade and SQL Server migration — delivered ahead of schedule, under consumption. Version-currency posture achieved.

Book a 30-minute Working Session. Bring the recurring work your team runs each month — the builds, checks, patches, and refreshes. We’ll show you what the first 30 days of Build-Run Separation looks like for your operation.

Platform & Methodology

Related Case Studies

This is the engagement summary. The monthly statement is what arrives in your Power BI workspace.