The requirement
The work involved two connected technical layers: JD Edwards EnterpriseOne Tools and Microsoft SQL Server. The agency needed to keep the core application on EnterpriseOne 9.2 update 6 while changing those underlying components. The upgrade plan assigned responsibilities between the agency and Allari and included nonproduction testing, backup prerequisites, production work and post-go-live support.
The work
Allari’s historical project review records a Tools Release upgrade from 9.2.6.3 to 9.2.8.1 and a database migration from SQL Server 2016 to SQL Server 2022. The engagement brought together CNC delivery and a Client Solutions Manager acting in project coordination. Planning and the customer’s own responsibilities formed part of the work rather than treating the upgrade as an isolated technical installation.
What the project review records
The internal project review records the engagement as completed in 2024, with the application retained on 9.2 update 6. It reports lower installation and post-go-live support effort than estimated, and identifies lessons for more accurate estimation and clearer involvement of supporting team members.
What your team can take from this
A tools and database upgrade needs clear scope, assigned responsibilities, testing and post-release follow-through. Keep the application boundary explicit, coordinate the customer and delivery team, and use the actual work to improve the next estimate.
Read this example in context
Historical engagement completed in 2024. The separately planned November 2026 upgrade is a different initiative.
Coordinate the work around your priorities
Allari brings functional and technical skills together around your team’s priorities and agreed budget. A dedicated Client Solutions Manager connects people, work and decisions, with the cost included in the partnership. Start with the operating requirement, the responsibilities and the result your users need to verify.
