The starting point of any cross-company subcontracting process is the handover procedure. During the handover phase, the Smart 3D design model is converted to a fit-for-purpose operations model, commonly referred to as the As-Built model. This process involves using Intergraph Smart Interop Publisher and the Smart 3D Generate SIO Utility to consolidate all the Smart 3D design data, as well as any legacy PDS and PDMS data essential to operations and maintenance, to the Smart Interop format. The key phases for preparing the design model for handover are Translation, Conversion, and Validation. Successful completion of each phase plays a vital role in producing the standalone As-Built model.
-
In Smart 3D, the Smart Interop Object format provides a single platform for Smart 3D, PDS, and PDMS design tool data.
-
You can also bring in laser-scanned point cloud data and reference it in the As-Built model.
-
To share design data from a legacy Smart 3D model with SDx, you must first upgrade the model to the current version of the software. Only after the model is upgraded, can you begin the Translation, Conversion, and Validation phases. See Upgrade the model in the Project Management Help.
Translation
Converting design tool data to the Smart Interop Object format is a multi-step process. This process begins with using Intergraph Smart Interop Publisher to translate your 3D design data to Smart Models. A Smart Model contains graphics and data translated from Smart 3D, PDS, or PDMS. When you create a Smart Model, the data is translated to the file formats listed below:
-
.zvf
Contains a .zvf file and multiple .vue files. A .zvf file enables you to access a sub-set of your model data without loading the entire model. If the entire model data does not fit into memory, portions are still accessible.
-
.xml
Contains data and relationships translated from the source files. Formatting is based on the Smart Interop schema.
Conversion and validation
After you convert the design data source files to Smart Models, you use the Smart 3D Generate SIO Utility to convert the Smart Model data to the Smart Interop format, which is then imported into the Smart 3D model database as Smart Interop Objects.
Each time that you run the Generate SIO Utility, it is important to review the results of the output. The Generate SIO Utility generates data from files that are translated from different source types. Structure, attribution relationships, and design quality can vary between the source types. In some instances, object names or properties might not be sufficient for the intended purpose of the project; you might need to modify the organization of Smart Interop Objects in the system hierarchy, or assign Smart Interop Objects to permission groups.
PDS and PDMS source data
When generating Smart Interop Objects from PDS data and PDMS data, the Generate SIO Utility can sometimes create objects in the source model as basic geometry. These basic geometry types might not have the proper mapping needed for converting to Smart Interop Objects. To resolve this issue, the Convert Smart Interop Object custom command enables you to manually convert basic geometry objects to more intelligent Smart Interop Object types. For example, you can convert a collection of basic geometry that represents a slab to a slab. Running this command requires you to select the output object type and the parent system in which the output object is created. You can select and convert single or multiple objects. You can also select multiple Smart Interop Objects and merge them to a single object type.
If your SIO model contains walls and slabs, you must perform a report and repair process. PDS and PDMS applications do not support layers, which results in the generated wall and slab SIO properties not having associated layers. When you select an SIO slab or wall in the model and view the properties, there are no associated layers in Relationships. To correct this issue for Smart 3D, you can run two custom commands to report and then repair wall and slab SIOs to add layer associations and any missing property values. Both commands must be run from the Smart 3D Host.
Data imported from PDS or PDMS can also have disconnections between objects. The Route Smart Interop Diagnostic command detects and repairs the data and relationship inconsistency in the Smart Interop Object data.
Unmapped data
You can choose to include unmapped data on Smart Interop Objects. Open the Generate SIO configuration file using your default text editor, and locate the <appSettings> element. Make sure the value for the IncludeUnmappedData key and the LogUnmappedData key is set to True.
When you set LogUnmappedData to True, the utility generates the file UnMappedProperties.csv and saves it in the %TEMP% folder on the local machine. The .csv file contains all the unmapped data for the Smart Interop Objects.
-
The Generate SIO configuration file (GenerateSIO.exe.config) is in the [Product Folder]\ProjectMgmt\Tools\bin folder.
-
By default, the Generate SIO Utility includes unmapped data on Smart Interop Objects. However, the default setting for LogUnmappedData is False.
Unsupported source types
The Generate SIO Utility only processes files with the following source type values: S3D, PDMS, and PDS_XML. This ensures that the data generated has the proper object classification, is organized correctly in the system hierarchy, and supports workflows for pipe routing and isometric drawing generation. All other source file types are skipped during processing and an entry is written to the log file:
"Skipping processing of <path\filename.mdb2> with data from unsupported source type <source type value>."
If needed, you can generate Smart Interop Object data translated from an unsupported source type, such as structural data in IFC file format, Open the Generate SIO configuration file using your default text editor, and locate the <appSettings> element. Add IFC to the values listed for the AdditionalSourceTypes key.
<appSettings>
<add key="AdditionalSourceTypes" value="S3D,PDMS,PDS_XML,IFC" />
<appSettings>
Smart Interop Objects generated from an unsupported file format such as IFC might have limited functionality,
as well as issues with classification, system hierarchy, and port connectivity.
What do you want to do?