NZDT project methodology for SAP S/4HANA
The right approach, complemented by smart transformation tools
1. Initial downtime
The basic idea of NZDT is to perform as many activities as possible outside of the downtime window. With this goal in mind, a copy of the production system is created before any changes to system or data are being allowed. At this point in time, the copy freezes the database and forms the basis for the transformation or migration implementation. From then on, any changes to productive data during the transformation are being recorded, leveraging tools that have been installed when taking the system copy. This step of copying the system and activating tools requires an initial short downtime of the productive system.
2. Uptime
Following the first initial downtime, the user can work with the productive system as usual. During this uptime, the transformation team sets up the new SAP system on the data previously copied. Next, data is being transferred following the migration strategy, processes are defined, and the new system is then validated and tested. After the preparation work of the target system has concluded, all recorded data changes from the productive system are imported into the new system.
3. Final downtime
After most of the changes have been reapplied, the next phase includes the second and final downtime. In this step, which corresponds to the typical go-live downtime, only those activities are carried out that could not be prepared based on the copied database. The production system is shut down, the last changes that had been logged are transferred, and remaining implementation work is performed. Now is the time for final checks and preparation for go-live. Finally, the new system is activated for business.
The NZDT methodology manages the sequence of activities as it also spreads those across the transformation process. With its proprietary solution Natuvion DCS, Natuvion supports, complements, and executes NZDT activities. This specialty tool takes NZDT to another level with a particular focus on customer requirements. The software automates certain tasks during downtime, ultimately reducing the time systems are unavailable. Automation not only accelerates the project timeline, but also eliminates errors caused by manual work and thus increases quality. In addition, the tool frees up capacity and resources can now turn to more complex, problem-solving activities.
