Management of change (MoC) process for agile engineering
Thomas Salitz
Digital Industry Advisor / 20K + Followers / Creative senior sales partner for the global process industry
Previous process engineering runs sequentially, i.e. first you start the concept, the simulation begins. The simulation results are used to evaluate different scenarios with regard, i.e. to their energy and mass balances. Once you have decided on a winning scenario, the process engineer then starts with the P&ID.
Only when the processes have been designed does the electrical measurement and control technology start, until it finally goes into automation. As time progresses, many individual objects change within the individual disciplines, which usually have a direct influence on the neighboring processes. This change process is usually manually documented parallel in Excel. In reality, the processes no longer run sequentially due to the time pressure, but more and more in parallel. The impact on the MoC is fatal, becoming more buggy the longer it lasts, resulting in valuable resources being unfortunately wasted.?
Engineering Base (EB) now enables the desired agile engineering, i.e. the complete parallelization of all process disciplines, and offers a unique management of change process, data tracking.
The data tracker is an individual container for each user, which automatically monitors and displays all data changes. This is not only innovative and simple, but also very sustainable. The quality increases, despite more parallelization of the processes. As a result, commissioning requires less energy and thus saves valuable resources.
AI Product Manager @ Novo Nordisk, dedicated to developing outstanding, user-centric AI solutions.
2 年Dear Thomas, thank you very much for this article! This is exactly what Engineering Base is designed for. Multiple disciplines are working with the exact same data. No synchronisation is needed between multiple data sources. Also from a software development point of view it is a huge benefit. Keeping data up to date in a multi-discipline and multi-user context is one of the biggest challenges. You nailed it!
Executive Board at AUCOTEC AG
2 年Hi Thomas Salitz, thanks for the article! I agree completely. You explain MoC (Management of Change) as important topic for the engineering departments. To improve the engineering process over the different disciplines a complete change of workflows and responsibilities is necessary. In the most cases different departments and different companies are involved (Owner/Operator, EPC, subcontractor, …). That’s the real challenge. Without a very strong vision and decision of the top management this change will not really happen. Unfortunately we don’t see such a clear commitment from top management in every digitalization project.
Passionate enabler of high-quality software engineering and IT operations
2 年MoC is crucial to increase efficiency and quality due to an agile transition. #AUCOTEC RnD and Operations is comitted to the #Agile approach and successes are clearly visible. Learn from Thomas Salitz how to apply the #Agile principles to Engineering!
Senior Sales Specialist - Digital Solutions for Process Industries | MES-SMOM | Production Efficiency | Energy Management | Operation & Maintenance
2 年Great article, Thomas. I think sequential engineering becomes "old style" and shows that a company is still far away from digitalisation and a digital twin. Many companies had to change for agile engineering to stay competitive.
Digital Industry Advisor / 20K + Followers / Creative senior sales partner for the global process industry
2 年More information under: https://www.aucotec.com/en/news-press/article/constant-dripping-instead-of-a-waterfall/ https://www.aucotec.com/en/plant-solutions/cooperative-platform/modern-plant-engineering/