How AUCOTEC's agile engineering significantly accelerates processes

Up to now, mechanical and plant engineers have lost a lot of time and data quality due to the change pitfall that arises from trying to achieve the necessary parallelization of processes with toolchains that are actually only suitable for waterfall processes. However, "the" waterfall process is long gone. No designer can wait until the previous project step is completely finished. Thus, he starts without the results of the neighbouring discipline in his tool. The other departments do the same. This requires interdisciplinary comparisons repeatedly. There are also inevitable external corrections due to changing customer requirements or conditions, with an impact on all disciplines. This results in a lengthy, error-prone cycle of change transfers. It becomes even more complicated with parallel "waterfalls", where the new version of a released process step is edited, while other participants are still developing on the basis of an earlier release.

Thus, the waterfall model is not only a thing of the past because of excessively long waiting times, but also because water does not flow uphill, i.e. backwards – and toolchains only support a predefined sequence. This is why AUCOTEC developed the cooperation platform Engineering Base (EB). It combines all core disciplines of machine and plant design into one system. Its central data model ensures that every change in each discipline involved is immediately visible to everyone and can be further edited directly. To stick with the water image: the model is like a pond in which circles of ripples spread out as a result of each new drop of water. Likewise, each input into EB's single source of truth immediately reaches every discipline – an existential prerequisite for mastering complex scenarios.

With a number of innovations, AUCOTEC has now optimized EB to such an extent that the next step, agile engineering, is possible. In addition to the established data tracking with complete change history in which it is possible to individually configure whatever changes you want to see, there is attribute-level rights assignment, which enables you to define who may see and edit which status. This only works because EB focuses on data instead of documents. Restrictive rights in relation to objects are not effective here, as each object exists only once, but different disciplines work on it, even in parallel. A process engineer edits a pump just like an electrical expert, but with respect to other aspects. EB is all about simultaneity.

In addition, the data and the entire plant structure are protected against inadvertent changes. This applies below objects as well as above them ("glue to parent"). Agile work is only possible with this cross-disciplinary certainty, which does not require the "freezing" of data, but enables continuous visibility of progress in neighbouring disciplines and immediate usability of new data for one's own tasks. As a result, the much closer interlinking of the disciplines eliminates the need for waiting times and continuous changes back and forth between departments and contributes enormous gains in terms of efficiency. During the design stage, the modification of a plant engineering project is also possible at any time: what was envisaged a year or two ago does not necessarily have to be implemented. New insights can be implemented continuously and quickly, i.e. agilely, in the ongoing process. The result: the finished plant is state-of-the-art, and not from two years ago.