This goal is achieved by implementing following:
- a common ontology describing the terms and concepts;
- data structures based on this ontology;
- a central server, serving as a common data environment and providing an API interface;
- PLEIADES connectors at the client side- for each software tool that wants to benefit from the PLEIADES platform.
The overall architecture of the platform is shown in the above figure.
The data managed by the platform are of the following kind:
- files, mostly 3D models in .ifc format;
- structured data following the ontology.
By using the API provided by the central server, a connected software is able to download relevant 3D models and related decommissioning planning data, use this downloaded data (either in an automated process, e.g. some mathematical simulation, or in interaction with the software user) and after the job is finished, upload the results back to the central database. The main building block of a structured data exchanged via the server’s API is the ‘record’. Records are classified using ontology classes and each class contains a specified set of properties.
This principle accomplishes the centralized data storage in all situations and independently from the software being used in the planning. That means that practically all software tools used during the decommissioning activities, independently from the technology they are built on, can use the same data set to support the decommissioning planning process.
Follow the project’s LinkedIn page and subscribe to our newsletter to keep up-to-date with the project’s progress!