During the handover phase, the Smart 3D design model is converted to a fit-for-purpose operations model. This involves consolidating all the Smart 3D design data and any data from legacy systems such as PDS and PDMS to a common format that can be used for downstream operations and maintenance tasks.
Data conversion is a multi-step process that involves two separate tools. First, you must use Smart Interop Publisher to convert the design tool data to a Smart Model format. Then, you use the Smart 3D Generate Smart Interop Object utility to import the Smart Model data into the Smart 3D database as Smart Interop Objects.
You can also bring in laser-scanned point cloud data and reference it in the as-built model.
After the data is in operations mode, all changes in the facility are performed within the context of at project. This ensures that there is a clear start and end as well as a clearly defined project scope. After creating the Smart Interop project, you must then identify the Smart Interop Objects to be modified by claiming them into the active project. The Claim command assigns the selected objects exclusively to the active project and ensures that no other project can modify the object. The following example illustrates a portion of the operations model (1) being claimed to the project (2).
Claiming objects ensures that any changes that you make to existing Smart Interop Objects or any new Smart 3D design objects that you add to the as-built model are automatically within the scope of the project.
Within the context of the project, you can modify many of the existing Smart Interop Object properties and add native Smart 3D design objects. You can also make simple project changes such as assigning a different system parent and re-arranging the system hierarchy.
When design and project changes are complete, you can generate drawing deliverables using both Smart Interop Objects and native Smart 3D design objects. For example, you can generate drawings for Fabrication and Material Take-Off (MTO) to show what is being changed within the context of the project.
Finally, when all work associated with the active project is finished, you release the claim on the selected objects. The Release Claim command reassigns a claim from the active project back to the as-built model so that another project can claim it.