<img height="1" width="1" style="display:none;" alt="" src="https://dc.ads.linkedin.com/collect/?pid=287945&amp;fmt=gif">

A successful execution of a Cut-over project using FlowWright

Posted by FlowWright on Jun 28, 2019, 7:49:00 AM

One of the largest OEM auto parts manufacturing companies in the world recently executed one of their scheduled SAP Cut-over projects using the FlowWrightPM Application (powered by FlowWright workflow automation.)  With our Project Management workflow application users are able to design a Cut-over plan and then execute it within the same application. To execute this particular SAP upgrade pertaining to multiple systems, production manufacturing needed to be halted across the board until the upgrade is complete.  They allotted an 8 hour window to execute the Cut-over. Here's how it works...

Designing and executing a complex project tends to be very task intensive, FlowWright solves for this organizational need and provides a high performance web-based graphical designer to help users visually bring these complex projects to life. Within any design, there’s decision making and tasks performing parallelly across systems. One of the most important steps to outline and consider when a user is in the design phase is around the synchronization of these tasks and systems. As a reminder, the next step that is slated to happen after the synchronization is not able to execute without all previous paths being completed. Below we highlight screenshots from the FlowWright PM application that outline the process they executed recently. 

Below is a graphical view of the Cut-over that was executed recently for our automotive client.
view of an actual cut-over execution using FlowWright

The next couple of graphs show what went on while the Cut-over was being executed:

user acknowledged tasks for the cut-over
There were 677 tasks based on the plan, according to the above graph, all 677 were acknowledged by the receivers of the tasks.


tasks by status
Based on the above task by the status graph, 677 tasks were completed. Since each task was routed to 3-5 users, a total of 3786 tasks were closed by the system automatically. FlowWright tasks can be routed to multiple users but require only 1 user to act on the task. That is a feature many FlowWright PM users find high value in. 


tasks completed by date
The above graph reflects when the tasks were completed. As you can see the plan started on May 20th with a small number of tasks being acted upon. On the day of the Cut-over, June 9th, where manufacturing production was stopped for upgrades across the company, the majority of the tasks were executed. On the last day of the Cut-over, FlowWright engines were busy launching Robotic process workers to process requests.  The graph below shows engine activity and history for the execution of the Cut-over.


FlowWright engine activity for the plan execution

plan execution history by date
In summary, the graphs show the completed Cut-over performed with minimal downtime, only taking about 3.5 hours, beating the projected 8 hour time allotment by more than half the hours allotted. FlowWright PM was able to route tasks to plants all over the globe and manage the response to these tasks with near real-time views into the execution of the plan, all because they used FlowWright PM to plan and execute the project. 

Companies that have a need for this type of real-time visibility into their complex project plan's report this application as imperative within the organization to de-risk, and improve efficiency for planning and execution. 

Learn more about how FlowWrightPM will help your company plan and execute projects today. 

Schedule A Project Management App Demo BOOK TIME HERE

Topics: cutover projects, erp upgrade