A North American workforce engagement platform ran JD Edwards EnterpriseOne 9.0 on AS/400 against a tightening vendor-support window. Custom integrations and reports were tightly coupled to JDE 9.0 objects — a lift-and-shift approach carried real cutover risk. Allari executed the JDE 9.0 → 9.2 upgrade with ESU baseline installation, mock go-live rehearsal, production cutover, and post-go-live hypercare — then carried the same platform forward into steady-state production support and the next tools-release upgrade. Operating knowledge carried from the upgrade into ongoing support.
- Sector
- Workforce Engagement / HR Technology
- Platform
- JDE EnterpriseOne · AS/400
- Scope
- Upgrade → Mock Go-Live → Hypercare → Production Support
A support window closing, tightly coupled integrations, and no tolerance for a handoff at the moment of highest risk
The workforce engagement platform ran JD Edwards EnterpriseOne 9.0 on AS/400. The vendor support window was narrowing — ESU and CNC patch currency became harder to sustain on the old platform, and the vulnerability patch cadence was mounting with each quarter that passed without an upgrade path. Custom integrations and reports were tightly coupled to JDE 9.0 objects, which meant a standard upgrade carried real cutover risk for a platform where workforce and HR data integrity is non-negotiable. The missing piece was not just an upgrade partner — it was a partner who could execute the upgrade and own the runbook afterward, without a contractor handoff at the moment of highest risk.
PLATFORM SUPPORT EROSION
Vendor support window narrowing, patch cadence unsustainable on 9.0
JDE 9.0 was running against a closing vendor support window. ESU patches and CNC updates were accumulating without a supported upgrade path in place. Every quarter on the old platform added complexity and increased the risk of operating a workforce system outside the support envelope — a risk that compounds as tools releases move further ahead of the installed version.
INTEGRATION RETROFIT RISK
Custom integrations and reports tightly coupled to JDE 9.0 objects
The platform's custom integrations and reports were tightly coupled to JDE 9.0 objects. A standard lift-and-shift upgrade approach — without a deliberate retrofit and validation phase — would surface integration failures in production, at the moment when the platform team's capacity to absorb them is lowest. For a workforce engagement system, an integration failure at cutover is a business-continuity event.
HANDOFF RISK AT GO-LIVE
No tolerance for a knowledge reset at the moment of highest post-cutover risk
Post-go-live hypercare is the highest-risk phase of any upgrade: the production environment is new, the team's familiarity with the new platform is being stress-tested in real time, and issues surface without warning. A contractor handoff at this moment — a new team inheriting a platform they didn't build — resets institutional knowledge at precisely the wrong time. The engagement needed a partner who would be present through the cutover and into steady state.
A closing vendor support window, tightly coupled integrations with real cutover risk, and the structural danger of a contractor handoff at post-go-live hypercare — three compounding pressures that required a managed, phased upgrade with same-team continuity from cutover through steady-state run.
ESU baseline, mock go-live rehearsal, production cutover, and hypercare — delivered without a handoff
Allari executed the JDE 9.0 → 9.2 upgrade across three structured phases. Phase 01 established the technical baseline and upgrade environment — ESU installations, JDE 9.2 Update 8 (UN8) application, tools release update to 9.2.5.6, and backup/restore methodology proven on the new iSeries — the foundation that made the mock go-live rehearsal possible. Phase 02 rehearsed and executed the production cutover: documented mock go-live rehearsal, cutover prep, and production go-live. Phase 03 delivered post-go-live hypercare and then transitioned — without a handoff — into steady-state production support under the same delivery team that ran the cutover. This mid-market playbook is the same operating model Allari applies at large-enterprise scale; for the large-enterprise version, see the JDE 9.0 → 9.2 upgrade for a global advanced-materials manufacturer.
PHASE 01 · PLAN & BASELINE
ESU baselines, UN8 application, Tools Release update, Backup/Restore proven
Phase 01 established the technical foundation for the upgrade. ESU baselines were installed for JDE 9.2, JDE 9.2 Update 8 (UN8) was applied, and the tools release was updated to 9.2.5.6 to achieve V7R2 support on the iSeries. The backup and restore methodology for PRODDTA and PRODCTL environments was proven on the new AS/400 configuration — the validation step that made the mock go-live rehearsal a rehearsal of the actual production procedure, not a simulation. Every artifact produced in Phase 01 was a direct input to the cutover runbook.
PHASE 02 · MOCK GO-LIVE & CUTOVER
Documented mock go-live rehearsal, cutover prep, production go-live execution
Phase 02 executed the mock go-live rehearsal — a full end-to-end rehearsal of the production cutover sequence in a controlled environment, with documented outputs that governed the real go-live. Cutover preparation covered the sequencing, dependency validation, and the go/no-go criteria that the team would use on production day. The production go-live was executed against the proven runbook with the same team that had rehearsed the procedure. Issues surfaced in the mock go-live were resolved before production — not discovered at the moment the platform team's capacity to absorb them was lowest.
PHASE 03 · HYPERCARE → PRODUCTION SUPPORT
Post-go-live hypercare delivered by the same team — no handoff, no knowledge reset
Phase 03 delivered the post-go-live hypercare phase — the highest-risk window of any upgrade — with the same delivery team that executed the cutover. The delivery team retained the upgrade knowledge through hypercare. The institutional memory of the platform architecture, the upgrade decisions, and the cutover mechanics remained in the team. Hypercare transitioned directly into steady-state production support, which has been running for multiple years. The same team is now executing the next tools-release upgrade — continuity of knowledge, not just continuity of contract.
The team that executed the upgrade is the same team running steady-state production support and the next tools-release upgrade. Continuity is the asset — institutional knowledge of the platform persisted across every phase transition without a re-onboarding cycle.
DELIVERY COORDINATION — UPGRADE OPERATING STACK
What the upgrade + hypercare program produced
UPGRADE
Complete
JDE 9.0 → 9.2 in production, mock go-live rehearsal to cutover delivered against a committed window.
HYPERCARE
Same team
Post-go-live hypercare delivered by the same delivery team that ran the cutover — no handoff at the moment of highest risk.
CONTINUITY
Multi-year
Steady-state production support running for years post-upgrade, next tools-release upgrade now in flight with the same team.
PARALLEL STREAMS
Concurrent
LDAP/SSO, vulnerability cadence, and tools-release upgrades all running in parallel under one operating partner.
Mock go-live rehearsal executed in a controlled environment before the production switch, surfacing and resolving issues before they could become cutover-day incidents.
Production cutover executed against the committed window — the same team that rehearsed the procedure executed it in production.
Post-go-live hypercare delivered by the same delivery team that ran the cutover — no contractor handoff at the moment of highest post-upgrade risk.
Steady-state production support running for multiple years post-upgrade, with the same team that executed the upgrade maintaining platform operations.
Next tools-release upgrade currently in flight with the same delivery team — operating knowledge carried into the next cycle.
Adjacent sustainment workstreams — LDAP/SSO integration, quarterly vulnerability cadence, Weblogic patching — running concurrently under the same operating partner.
ESU and CNC patch currency restored; the platform now operating within vendor support with an active upgrade path for future tools releases.
Related work
Start with the work your team needs handled.
Bring the operating responsibility or change you need help with. Define the outcome, internal owners, required skills, access, coverage and budget together.
