Project Steel Industry

Business Case: Upgrade from AX 2012 R3 to D365 for a Steel Industry Client

Executive Summary

The privately owned steel company currently operates on Microsoft Dynamics AX 2012 R3, a robust but outdated system. To maintain a competitive edge and capitalize on the latest technological advancements, the company has decided to upgrade to Microsoft Dynamics 365 (D365). This article outlines the solution provided, the analysis conducted, the upgrade process, and the successful Go-Live strategy.

Objective

The primary objective of this upgrade is to transition the client’s existing AX 2012 R3 environment to D365. This move is aimed at integrating advanced features, improving performance, and enhancing business capabilities to ensure the company remains at the forefront of the industry.

Solution Provided

Code Upgrade and Customizations

The solution involves a comprehensive code upgrade from AX 2012 R3 to D365, complemented by the implementation of new customizations that were not covered by the code upgrade alone. This dual approach ensures that all the client’s needs are met, both in terms of existing processes and future requirements.

Analysis

Requirements Gathering:

The project began with an initial analysis of the AX 2012 R3 environment. Multiple workshops were held with the client to gain a thorough understanding of their current processes and to identify the necessary customizations for the upgrade. This collaborative approach ensured that all critical areas were addressed.

Upgrade Analyser Tool

To outline the time and effort required for the upgrade, the team utilized the Upgrade Analyser Estimator tool. This tool was instrumental in exporting the AX 2012 R3 code as a model store, which was then used with the LCS Code Upgrade tool. This process generated an upgraded version and provided a report on conflicts, enabling the team to address potential issues early on.

Life Cycle Services (LCS)

Life Cycle Services (LCS) played a pivotal role in the upgrade process. A project plan was created, and onboarding documents were generated using the upgrade methodology. The detailed descriptions from the Upgrade Analyser Tool were incorporated into the project plan, ensuring that all aspects of the upgrade were thoroughly documented.

Implementation Process

Demo Environment & Code Upgrade

A demo environment was deployed to perform a basic fit-gap analysis of the standard processes used in AX 2012 that have changed in D365 Finance and Operations. This analysis highlighted multiple issues, all of which were mitigated during the code upgrade process.

Functional Design Document

Following the demo environment setup, the team had a call with the client to develop a Functional Design Document. This document outlined requirements that could not be moved as part of the code upgrade, necessitating development from scratch. This step ensured that all customizations were accounted for and that the client’s specific needs were met.

Development and Testing

Branches were created in Azure DevOps Repos for development, testing, and building. The demo environment was linked with the development branch, and the code was merged from Dev to Test, where regression testing was performed. After multiple rounds of testing, the code was merged into the Build branch, and a deployable package was generated and stored in the Asset Library of LCS.

The deployable package was then deployed to a Sandbox environment, named User Acceptance Testing (UAT). Further regression testing was conducted, and access was provided to the client for their review and use. This step ensured that the upgraded system met the client’s expectations before going live.

Go-Live Strategy

Planning and Microsoft Checklist

A meticulous Go-Live plan was developed, with all required documents filled out according to the Microsoft checklist. This checklist was validated by Microsoft, and a test run was conducted during a call, which was subsequently approved. Microsoft then deployed a Production environment and gave the go-ahead.

Production Deployment

With Microsoft’s approval, the deployable package was released as a release candidate, and a call was raised to Microsoft for the production deployment. During a planned downtime of four hours, the package was successfully deployed in the Production environment, marking the completion of the upgrade.

Hyper-Care

Following the Go-Live, a one-month Hyper-Care period was provided to ensure stability in the new D365 environment. During this time, any P1, P2, or P3 issues that arose were promptly rectified and resolved, ensuring a smooth transition for the client

Benefits

Enhanced Features

The upgrade to D365 provides the steel company with access to advanced features and functionalities that were not available in AX 2012 R3. These enhancements position the company to operate more efficiently and effectively.

Improved Efficiency

With the new system in place, the company can expect improved efficiency across all business processes, leading to better resource management and increased productivity.

Stability and Support

The transition to D365 ensures that the company benefits from enhanced system stability and support, reducing downtime and enabling smoother operations.

Client Satisfaction

The comprehensive approach to the upgrade, combined with thorough testing and a dedicated Hyper-Care period, has resulted in high client satisfaction. The company is now well-positioned to take full advantage of the capabilities offered by D365.

Conclusion

The successful upgrade from AX 2012 R3 to D365 has positioned the steel company to leverage advanced features, enhance operational efficiency, and achieve better performance. The structured approach to code upgrade, testing, and deployment ensured a smooth transition with effective client support and minimal disruptions. This upgrade not only modernizes the company’s IT infrastructure but also lays the foundation for future growth and innovation.