For those of you interested in how to manage the creation of a Common Date Environment (CDE) based on engineering information delivered by different companies using different engineering tools in a structured way, the article written by the USPI members Leo van Ruijven (Croonwolter&dros) and Jim Novack (Dynatec) provides a good starting point.
Although the target group for the article are people in the Nuclear industry, the content of the article provides a good basis for those looking into doing the same for any other regulated industry or industry in general.
The article is titled “Car wash for data”: Best practices for Information and Configuration Management applied at Pallas nuclear facility. It describes the Why, How and What for information from the engineering phase, the architecture of a Common Data Environment (CDE) that stores the information, and the process of making the information supplied by the different parties involved suitable for entry in the CDE in such a way that it meets the requirements of the CDE. As this information is provided in different data formats (because of the use of different tooling) and may not be modelled based on the common Integrated Information Model (IIM), the underlying data needs to be cleaned up like in a car wash to make it suitably cleaned to upload in the CDE.
Having the data in the CDE based on the IIM makes the CDE very suitable as the basis for a Digital Twin (DT) to support better operations and safety.
To download the article, please click here