Translate PDS source files - Intergraph Smart Interop Publisher - Help

Intergraph Smart Interop Publisher Help

Language
English
Product
Intergraph Smart Interop Publisher
Search by Category
Help
Smart Interop Publisher Version
17

Smart Interop Publisher can translate PDS legacy project files and PDS-published files so that each property label display is converted to a standard one for all target applications.

PDS legacy files are exported from all versions of PDS, however, only PDS v11.0 and earlier exports the published files (.zvf and .xml).

Requirements and Considerations

  • All PDS 3D source file types must be in the input location.

  • PDS-published source files (.zvf + .xml + .xrg) are translated to a Smart Model .zvf project containing .zvf, .mdb2, and .xrg files. The .xrg file must be provided for a Smart Model .zvf project that is going to be published to SmartPlant Foundation.

  • For referencing in Smart 3D, an .xrg file is not required.

  • Make sure your export does not contain duplicate linkages.

  • For Smart Models to be converted to Smart Interop Objects (SIOs) for import into Smart 3D, you can use only .zvf/.xml data files; not PDS legacy files.

PDS Legacy Files

Use the PDS DesignReview Integrator to generate control (.dri) files, graphics (.dgn) files, and any Frameworks Plus (.prp) files. The database or label (.drv) files can be created from PE-HVAC, Piping, Equipment, Structural, Raceway, and PLANTGEN models. See the Plant Design System (PDS) DesignReview Integrator User's Guide.

The delivered default translation settings define relationships between nozzles and their parent equipment, pipe parts and parent pipelines, and pipeline delimiters. Check this information in your .dgn or .drv source files before you translate so that you can enter any required settings at translation time.

PDS Published Files

The Material Data and SmartPlant Publisher utility (MDP) allows you to generate graphics (.zvf), database (.xml), and object range information (.xrg) files. An .xrg file is required for a translated Smart Model .zvf project that is going to be opened in SmartPlant Foundation. The Material Data and SmartPlant Publisher uses selection set files to determine what data to publish. The MDP interface allows you to select specific disciplines, model areas, and models within the project to publish, and to save different sets of models in separate selection set files. See Material Data Publishing Workflow in the Plant Design System (PDS) Material Data and SmartPlant Publisher User's Guide.

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 custom PDS mapping template files.

For translating PDS-published files (.zvf, .xml, and .xrg), use PDSToR3DMapping.xls and customPDSToR3DMapping.xls template files. For PDS legacy files (.dri, .dgn, and .drv), use PDSLegacyToR3DMapping.xls and customPDSLegacyToR3DMapping.xls template files.

  1. Review the PDSToR3DMapping.xls or PDSLegacyToR3DMapping.xls default mapping file to see the classes and properties that are currently mapped.

  2. Make a copy of the customPDSToR3DMapping.xls or customPDSLegacyToR3DMapping.xls file located in the CustomMappingFiles folder, and place the copy in another folder location.

  3. Edit the custom mapping 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.

  4. 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.

  5. For publishing custom codelist tables to SDx, you can map custom SPF codelist table numbers to Smart InterOp (SIO) codelist numbers. See Map Custom PDS Codelist Tables.

  6. For Smart Review display, edit the PDS_ASPECTS sheet in customPDSToR3DMapping.xls to define the level number of the PDS 3D graphics for Piping or Equipment disciplines under the Level Number column, and map it to the required aspect under the Aspects column. You can map more level numbers and change existing ones. Otherwise, Smart Interop Publisher, by default, maps graphics to the Simple Physical aspect.

    For example, you can assign piping objects at two different levels a different aspect. You can map piping objects at level 54 to the Insulation aspect. All other piping objects at different levels are mapped to the Simple Physical aspect. The example images below display an inner and outer pipe object in Smart Review. The outer pipe, per the mapping defined in the PDS_ASPECTS sheet, displays at level 54 and is mapped to the Insulation aspect. The inner pipe at level 22 displays with the Simple Physical aspect assignment.

    Outer pipe in Smart Review:

    Inner pipe in Smart Review:

Translation

  1. Click the Smart Interop Publisher icon on your desktop .
    -OR-
    Click Start > All Programs > Intergraph Smart Interop Publisher.

  2. If you are not in the Projects View, click Projects.

  3. Select or create a project to use in the grid.

  4. Right-click the project, and then select Settings Menu > Project Settings Command.

  5. Use the default settings, or make any required changes.

  6. 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.

    SHARED Tip Selecting only the target applications you require can produce a faster translation time. Smart Interop Publisher only generates files required for the selected target.

  7. Click Save to save your changes and close the Project Settings Dialog.

    Right-click the project, and then select the Translation Settings Command. Smart Interop Publisher displays the Translation Settings Dialog.

  8. Click New in the Select or Create Settings Group list, and type the name to use.
    -OR-
    Edit the Default translation settings group.

  9. For PDS published files, select the Schema file (PDSComponent.xml) and Relationship Mapping file (RelationshipMapping.txt) provided by PDS. You can edit these configuration files before translation, or use their default settings.

    For PDS legacy files, make sure the Nozzle Parent Identifier, Pipeline Number Identifier, and Pipeline Number Delimiter settings match the settings listed in the PDS source files being translated. Smart Interop Publisher provides the following default settings:

    You can create different translation settings groups to accommodate different settings for your PDS source files.

  10. (Optional) If you are having problems publishing your PDS legacy files because of duplicate linkages, select Resolve duplicate linkages. Otherwise, do not select the option. See PDS 3D options.

  11. Click Save when you have finished defining translation settings.

  12. Click Models to go back to the Models View.

  13. On the Source Files Grid, click Add , and then select either the PDS legacy source .dri files or published .zvf file.

    • For either PDS-generated file type, make sure all data and graphics files are in the same folder on your system.

    • For published PDS files, you must include the .xrg file in the same folder as the .zvf file if your target application is SmartPlant Foundation.

  14. Select each source file to use in creating the Smart Model, and then click Translate .

    SHARED Tip Use SHIFT+ or CTRL+ key combinations to select multiple source files.

  15. On the Translate Source File Dialog, type a name and location for the Smart Model.

  16. Select the Settings Group you defined earlier, or use the Default group.

  17. If you used custom mapping, set the Mapping Options to Custom and select the Mapping Files Location of the custom PDS mapping template file you edited.

  18. Click Translate.
    -OR-
    To schedule the translation for a later time, click Schedule to open the Schedule Translate Dialog.

  19. Open the Smart Models you created in the Intergraph target applications:

  20. 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.