Synchronize PCR and iModel
The data synchronization works free of user interaction. There is no other manipulation to the resulting models or working layers possible than importing and aggregating data.
When users execute an import, depending on the import type, the imported data is saved in one of the data repositories.
In order to unify the data, there are two situations when the synchronization is triggered:
- When importing external 2D
and 3D data sources on the iModelHub side via iModel Bridges
The functional data coming from 3D imports is synchronized automatically with the PCR as soon as the import is completed.
- When saving
data in the Digital Twin during Data Aggregation
The functional data of each Digital Twin object is synchronized automatically with the iModel Hub
During synchronization, the instances are registered in the EIFS Service. The tags are registered in the ICS Service. As a result, the functional, schematic and physical data sets are linked with each other and the user can navigate between them.
- a mapping was created
You can find more information on this in the COMOS manual 'Generic Data Mapper", keyword 'Using the Generic Data Mapper'.
- the PlantSight environment is configured
- the BIS schema is properly configured
- the iModelHub Project is allocated to a COMOS database
- the iModel is dedicated to a COMOS Project
- the iModel is provisioned with the BIS configuration
- the data acquisition workflows and aggregation workflows are in place
Synchronization During Data Import
If by an iModel bridge functional data has been acquired, a synchronization to the PCR is required in order to use the information for the data aggregation process. Therefore, the dataset is imported into a working layer in the PCR.
At the same time an internal ID is being tracked to allow to the identification of the original import source The registration of the IDs make sure the corresponding functional, physical and schematic data are identifiable as belonging to the same technical instance. This enables navigation, data updates and other manipulations.
Synchronization During Data Aggregation
During the process of data aggregation the collected data is being reviewed and selectively aggregated in order to create a data set that represents the actual status in the plant based on all available information. This available information also includes functional data taken from the 3D bridges and is limited only to functional data in the PCR. So, for the creation of a Digital Twin, the aggregated functional data needs to be synchronized to the iModelHub in order to combine it with 2D and 3D model information. The previously created registration IDs, be it while importing data from the bridges or while aggregating in the PCR, are used to identify corresponding functional, physical and schematic occurrences in the iModelHub's digital twin models.
The data synchronization is intended to work without user interaction. Therefore, the functional model created is locked for any other manipulation that is not executed from the sync service itself.
Administrating the Synchronization
For reviewing or manipulating the mapping configuration of the data models BIS and PCR, the Generic Data Mapper in the PCR software (COMOS) is used. There the class definitions as well as the class properties of the two data models are assigned to each other.
This is an administrator task which needs to be carefully done - for further information please refer to the COMOS manual "Generic Data Mapper".
The mapping rules are saved in a .gmad-file and need to be referenced in the PCR project settings.
There is an example .gmad-file provided together with the the PCR software COMOS. In case the data models are changed, the mapping rules might also need to be changed. Therefore you need to access COMOS via a provided VM.