Smart Interop Publisher can translate PlantSpace .dgn files so that each property label display is converted to a standard display for all target applications. Additionally, for any MicroStation-based .dgn files, you have settings that allow you to translate reference models and one or all design models that are in the .dgn file.
Requirements and Considerations
PlantSpace can have a mapping .xml file with the source .dgn file that contains all the property information. Any custom properties added to the PlantSpace .dgn file are placed in this corresponding .xml file.
To support custom properties, you must replace the default PlantSpace DGN V8 Attributes Mapping.xml file in Smart Interop Publisher with the PlantSpace .xml file corresponding to the .dgn file.
-
Make a copy of your PlantSpace mapping .xml file, and then rename it to PlantSpace DGN V8 Attributes Mapping.xml.
-
Go to [Drive]:\[Smart Interop Publisher Install Folder], locate the delivered default PlantSpace.xml file, and then replace it with your custom .xml file.
-
Make sure you have a Component Type property in the .xml file; otherwise, the software translates your property class as generic.
-
You can now either use the default PlantSpace mapping delivered with Smart Interop Publisher or use custom mapping spreadsheets to show additional properties in a target application.
Custom Mapping (Optional)
You can include new classes and properties, map any unmapped properties that you have
added, and define unit of measure strings for property values using the CustomPlantSpaceToR3DMapping.xls
mapping template files.
-OR-
Skip this section and use the default mapping provided with Smart Interop Publisher.
-
Review the PlantSpaceToR3DMapping.xls default mapping file to see the classes and properties that are currently mapped.
-
In the CustomMappingFiles folder, make a copy of the CustomPlantSpaceToR3DMapping.xls file, and place it in another location.
-
Edit the custom mapping spreadsheet file to either modify property labels or add classes and properties.
Smart Interop Publisher removes any colons placed inside a property name during translation. For example,
if you enter Net:Area for the property name, the resulting translation displays NetArea.
-
Save the edited mapping spreadsheet file in the Microsoft Excel 97-2003 Workbook (.xlsx) format. See Edit the custom mapping template file.
To display unit strings such as 'meters' or 'inches' with specific property values in the translated model, you can define the Units G column in the custom mapping file. See Set the units of measure (UoM) in custom mapping.
-
To set up custom mapping for a third-party format target such as Industry Foundation Classes (IFC), you must also create Hexagon schema (R3D)-to-IFC mapping. See Use custom mapping for third-party format targets.
Translation
-
Click the Smart Interop Publisher icon on your desktop
.
-OR-
Click Start > All Programs > Intergraph Smart Interop Publisher. -
If you are not in the Projects View, click Projects.
-
Select or create a project to use in the grid.
-
Right-click the project, and then select Settings Menu > Project Settings Command.
-
Use the default settings, or make any required changes.
-
For Target Applications, select the Hexagon Asset Lifecycle Intelligence applications and third-party format to use. If you select a third-party format, verify that you have the required license. For example, you must have an IFC license to use the Industry Foundation Classes target.
Selecting only the target applications you require can produce a faster translation
time. Smart Interop Publisher only generates files required for the selected target.
-
Click New in the Select or Create Settings Group list, and type the name to use.
-OR-
Edit the Default translation settings group.
-
Because PlantSpace is a MicroStation-based application, select MicroStation in the left pane.
-
For Model Options:
-
You can turn on or off the translation of a reference model in the .dgn file.
-
Set the option to translate either the active, selected, or all design models in the .dgn file. Smart Interop Publisher uses the naming convention [design model file name]_[Smart Model name] for each generated Smart Model.
If you are selecting multiple source files to translate, the Translate each design model separately option affects the number of Smart Models that are created. This option causes Smart Interop Publisher to create a separate Smart Model for each design model that is in the selected V8
.dgn source file. For example, if you have two .dgn source files with each containing
two design models, then Smart Interop Publisher generates four Smart Models.
-
-
Select any required Display Options. These options the way the model looks when opened by a target application.
-
Click Save when you have finished defining translation settings. See MicroStation options.
-
Click Models to go back to the Models View.
-
Select each source file to use in creating the Smart Model, and then click Translate
.
Use SHIFT+ or CTRL+ key combinations to select multiple source files.
-
On the Translate Source File Dialog, type a name and location for the Smart Model.
-
Select the Settings Group you defined earlier, or use the Default group.
-
If you used custom mapping, set the Mapping Options to Custom and select the Mapping Files Location of the CustomPlantSpaceToR3DMapping.xls you edited.
-
Click Translate.
-OR-
To schedule the translation for a later time, click Schedule to open the Schedule Translate Dialog. -
Open the Smart Models you created in the Intergraph target applications:
-
If you selected a non-Intergraph format target, open the model format file using your preferred third-party reader. For example, if you selected the Industry Foundation Classes (IFC) format target, use your own IFC reader to review the resulting Smart Model .ifc file.