Interoperability Summary: Leveraging 3D Designs & Data White Paper
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Interoperability Summary: Leveraging 3D Designs & Data White Paper
2. Introduction
Process plant design and construction projects bring together data created by the:
O/O
Engineering teams
Joint venture partners
Procurement and construction contractor(s)
Subcontractors
Consultants
These stakeholders produce large volumes of 3D data using a variety of software solutions such as:
PDS
Smart 3D
CADWorx
CAESAR II®
PDMS
PlantSpace
MicroStation
AutoCAD®
SAT
IFC
XMpLant
i-model
And others
If software components change over time, data formats become incompatible and require conversion
before data can be reused for similar designs and construction. It has traditionally been a time-consuming
and costly process to map source model graphics and object property files into common formats that can
be viewed and modeled against.
Converting 3D models from one format to another before reuse dramatically increases the O/O’s cost
during the plant’s lifetime – when 3D data availability is most critical for maintenance, modification, and
eventually decommissioning.
This paper highlights Intergraph’s interoperability capabilities that eliminate the “big bite” of converting
legacy 3D models. Intergraph offers interoperability technology that incorporates valuable model data
from many sources. These technologies are designed for five scenarios to reuse 3D data throughout the
design, construction, handover, and operations and maintenance (O&M) phases of the plant life cycle.
4
Interoperability Summary: Leveraging 3D Designs & Data White Paper
This white paper is structured to cover each of these five scenarios, including:
1. (Design Phase) Reuse data for Smart 3D design (3D Interop)
2. (Design Phase) Full conversion to Smart 3D (Importers)
3. (Construction and O&M) Provide 3D data from multiple formats during construction and O&M
(3D Interop)
4. (O&M Design) Engineering in O&M (CAXperts)
5. (Handover) Conversion from Smart 3D to meet client handover requirements and specifications
(Exporters)
5
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Figure 2: SPIOP brings most data formats into the SmartPlant environment.
6
Interoperability Summary: Leveraging 3D Designs & Data White Paper
SmartPlant Interop Publisher, the heart of Intergraph’s interoperability solution, offers a significantly
more efficient path to reuse data rather than having to convert and validate an entire model. Avoiding
the “big bite” conversion enables incremental conversion of sections of the model as needed for design
reuse. Portions of the model can be referenced from a new Smart 3D model (see Figure 3). SPIOP
receives input from non-Smart 3D models in the form of sets of matching graphics and data files.
7
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Survey Data – Converted 3D models can be viewed when displaying laser data to ensure the
model reflects the “as-built” plant, not just the digital plant. Smart 3D capabilities (together with
Leica CloudWorx™) efficiently model intelligent objects on top of point clouds. Smart 3D uses
advanced geometry recognition tools for accurate determination and measurement of objects
such as pipe diameters and allows semi-automatic modeling of pipelines.
Mechanical CAD – Users can convert equipment files that were designed in mechanical CAD
(MCAD) packages into SmartPlant Enterprise. SPIOP reads MCAD formats (NX, SolidEdge,
SolidWorks, Pro/E, CATIA, and Inventor). SPIOP adds value by:
Reducing equipment file size and memory
Allowing object selection from assembly hierarchies
Maintaining accurate 3D connect point information
Offering selective de-featuring of graphics or unwanted detail
Providing clash-checking
Storing intelligence for automated routing
Preserving equipment integrity in Smart 3D
Allowing batch file updates
SPIOP also protects intellectual property of equipment designers by not exposing the fabrication
model. It includes unique equipment, subsystems, or modules, and supports design and reuse of
mechanical equipment in the plant.
Lowering Barriers to Joint Venture (JV) Projects – Joint venture projects typically involve a
number of contractors. Projects primarily executed in Smart 3D will receive models – process
units, design packages, skid units, etc. – produced by smaller contractors designed in other
systems having different model formats. The project team can work in multiple 3D formats and
eventually consolidate into a single environment and format. Live connections to original data
sources are not required. SPIOP does not require live connections to data sources, minimizing
concerns about security and IP protection risk. Only data that is required by partners is
authorized to be shared. Periodic updates enable disconnected workshare while promoting
ad hoc collaboration. SPIOP unifies multiple formats to allow joint venture partners to collaborate
more easily, share design work, consolidate efforts, and enjoy more efficient work processes –
even when using different software.
Smart Model References – Users can attach multiple Smart Model references to the Smart 3D
project to allow users to view the referenced model objects. The Smart Model filters objects
from referenced models based on their type and properties. It also extracts drawings using
graphic/label rules and shows object positioning from referenced models with limited annotation.
Design Reviews – With SPIOP and SmartPlant Review, users can review models during design
and construction, open and combine reference files for design reviews and “walk-throughs” to
see design or construction status, perform clash detection, and create queries across multiple
sources. This leverages the entire project’s data as a single source.
Publish 3D Model Graphics and Object Property Data – SPIOP provides OOTB mapping and
data formats to publish 3D model graphic and object properties within the plant data repository.
The SPF Schema Editor facilitates customizing properties in the translated model when the
requirement is to transfer property data to SmartPlant Foundation and subsequently SmartPlant
Construction. Users can query the 3D model and links to plant data. SmartPlant Construction
retrieves components from reference files to create work packages and construction sequencing.
8
Interoperability Summary: Leveraging 3D Designs & Data White Paper
9
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Figure 4: This CADWorx model shows DWG files referenced in AutoCAD to create a single view of the plant.
10
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Being an application built on top of AutoCAD, CADWorx models are saved in AutoCAD DWG format. In
addition to the information AutoCAD defines, DWGs created and saved by CADWorx include Extended
Data (Xdata) for piping, equipment, structure, etc. SPIOP can automatically detect whether it is translating
a native AutoCAD file, or an AutoCAD file containing CADWorx objects.
CADWorx DWGs are processed through SPIOP to produce input for SmartPlant Review (VUE), or
Smart 3D (ZVF). Using SPIOP, CADWorx models can also be published to SP Foundation. From
CADWorx version 2015 and up, CADWorx proves a direct translator to Smart 3D OOTB. In SPIOP,
the main window is split into two main sections containing source files, CADWorx DWGs in this case,
and Smart Models (SPR, S3D, or SPF outputs) (see Figure 5).
A template mapping file installed by SPIOP is used to map CADWorx properties to corresponding
Smart 3D classes and properties. SPIOP provides options for the user to fill in Smart Model output
locations, mapping options, target applications, etc. VUE and ZVF files produced by SPIOP are used
to visualize and reference the CADWorx model in the SmartPlant environment.
Figure 5: The SPIOP window shows CADWorx source files and corresponding translated Smart Model outputs.
For example, the CADWorx model in VUE format can be opened in SmartPlant Review, enabling the
model to be navigated and its properties and attributes to be queried. The same CADWorx model, this
time in ZVF format, can be referenced in Smart 3D via the Smart 3D Project Management application.
Once the CADWorx model is attached in Smart 3D, users can view and model and clash check against it.
11
Interoperability Summary: Leveraging 3D Designs & Data White Paper
The SmartPlant environment for CADWorx-referenced models includes several complementary functions,
such as:
In Smart 3D
Attach multiple Smart Models (reference files) to the Smart 3D model
Inspect/provide property views for referenced model objects
Filter objects from referenced models based on their type and properties
Use Surface Style Rules to change the referenced model to look the same as the native
Smart 3D model objects
Use graphic/label rules to extract drawings showing position of objects from referenced models
Connect Smart 3D pipe routes intelligently to nozzles on referenced models
Complete pipe routings and tie-in connections between Smart 3D models and referenced models,
enabling final isometrics and bills of materials to be generated
Check for potential interferences and clashes between referenced models and Smart 3D
model objects
In SmartPlant Review
Open and combine Smart Models for design reviews
Walk through 3D Smart Models to understand the design or construction status
Perform clash detection against objects in the Smart Models
Perform motion collision detection by moving Smart Model objects along a path
In SmartPlant Foundation
Register the Smart Models with the corresponding plant
Publish 3D model graphic/object properties using mapping/data formats, delivered OOTB in SPF
Map custom properties for the translated model using the Schema Editor in SPF
Query/view the 3D model with associated links to other non-graphic data stored for the plant
In SmartPlant Construction
Retrieve components from the Smart Model to create construction work packages.
Note: Add-on module is required to publish to SmartPlant Foundation and SmartPlant Construction.
12
Interoperability Summary: Leveraging 3D Designs & Data White Paper
When converting full or partial databases between any of these formats, two important components must
be addressed to accommodate the intelligence rules for Smart 3D. Reference data must be created or
reused from the Standard Database (SDB). Model data must be migrated via automated tools and/or
referencing graphic/property data via SPIOP. Each of these components is discussed in the following
sections from the perspective of the three migration scenarios involving Intergraph PDS, Intergraph
Smart 3D, and Aveva PDMS software. Import and export tools are highlighted in these sections.
In traditional migration projects for a fully intelligent model with full conversion of piping specs, PDS
users can undertake their own model translation using the Smart 3D PDS Project Translator software
and training. This is a separately-licensed Intergraph software product, enabling PDS customers to export
piping, HVAC, electrical, equipment, and structure model data (geometry and attributes) from PDS into
Smart 3D. The intent of this translator software is to protect and leverage the equity in existing reference
data and plant models to establish a comparable Smart 3D production-level design environment to
replace PDS. Current software tools and utilities are not designed to undertake a “big bang” migration
into Smart 3D at the end of a PDS project to meet data handover obligations specified by an owner.
13
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Design intent used in Smart 3D is captured and transforms same system hierarchy to PDS
Different levels of intelligence are transferred for specific disciplines
Equipment nozzles can be revised/edited in PDS, making them intelligent
100 percent intelligent transfer of piping to PDS
A PDS project can be automatically configured and populated without opening the PDS project
Users can export only data needed instead of the whole plant
OOTB mapping with properties; users select system hierarchy to export
Export wizard simplifies user experience in moving project data from Smart 3D to PDS
14
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Hangers & Smart 3D supports exported as logical hangers and supports written in APL file
Supports Supports are processed with piping; no special provisions required
HVAC Smart 3D HVAC exported to PDS as geometry (reviewable only) and properties written in DRV files
15
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Two alternatives are available for using PDMS data in Smart 3D, including:
Option 1: Smart 3D references PDMS Model using SPIOP
Option 2: PDMS Data is migrated into Smart 3D
Option 2.1: PDMS Reference Data is created
Option 2.2: PDMS Model Data is converted
Two important variables must be considered when converting PDMS data to Smart 3D: creating reference
data and migrating model data. Both situations are described in the following sections.
Intergraph recommends that SmartPlant Reference Data manage component dimensions, descriptions,
and connectivity in Smart 3D catalogs and specifications. Data within SPRD can be exported directly to
Smart 3D to support future additions and modifications.
16
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Some automated tools exist in PDMS DATAL format to create objects in Smart 3D Versions 2011 R1
and 2014 (see Figure 6); these tools are productized in Smart 3D Version 2014 R1. Other data will need
to be manually created or referenced in Smart 3D. Such automation tools are used by Intergraph services
teams working with the customer. Automated migration tools that can be used to read piping, HVAC,
electrical, equipment, and structure model data from PDMS include:
Structure – Intergraph’s model translator software will convert DATAL files into XML format and
import into Smart 3D as intelligent structural objects. A structural system such as StruCAD also
imports PDMS SDNF files (additional PDMS license required) and can export to CIS/2 format
and Smart 3D. Structural objects can be created/transferred to Smart 3D.
Equipment – Intergraph’s model translator software converts DATAL files into XML and imports
to Smart 3D as intelligent equipment objects. If the PDMS model uses any third-party formats like
3D MicroStation, AutoCAD, or SAT file as an equipment object, these should be imported by
native Smart 3D functionality.
Piping – Intergraph’s model translator software converts DATAL and ATT files extracted from
PDMS into XML format and imports into Smart 3D as intelligent piping objects. If an equipment
connection exists in PDMS when imported, the relationship is automatically generated in Smart
3D.
Electrical – Intergraph’s model translator software will convert the DATAL files into XML format
and import into Smart 3D as intelligent cable tray objects in Smart 3D. This functionality will be
available in Smart 3D version 2016.
HVAC – Intergraph’s model translator software will convert the DATAL files into XML format and
import into Smart 3D as intelligent duct objects in Smart 3D.
Figure 6: Smart 3D’s model translator converts PDMS designs into intelligent Smart 3D data.
17
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Smart 3D offers OOTB capabilities to reference a PDMS model. PDMS data is exported into PDMS
RVM and ATT files that are converted into a streamed Smart 3D format (zvf) using a standard Smart 3D
ConvertToZvf utility that utilizes the SPIOP technology. Streamed data is referenced from Smart 3D
because sample mapping files for PDMS data are supplied with Smart 3D. PDMS attributes can be added
to the mapping file to be available in Smart 3D. A user can reference any number of reference models
(in formats supported by SPIOP) at the same time. Individual models can be moved, rotated, and scaled.
Model display is controlled by the workspace definition filter in operation in the Smart 3D session.
Structure 1,528 primitives, 200 sections/connections, 27 panels, 5 floors 437 KB 619 seconds
18
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Once the configuration/mapping is done, the export process can be set up to run automatically on a
scheduled basis, exporting only objects that have been created or modified since the last export. This
is a unique feature as opposed to the "typical" one-off exports that other systems perform, and allows
incremental update of the PDMS model during the project. This is important for projects where the
PDMS model is participating in a "PDMS Global" configuration, and other parties might be interested
in seeing the progress day by day.
Figure 7: Smart 3D exports designs and catalog data for most disciplines used by PDMS.
19
Interoperability Summary: Leveraging 3D Designs & Data White Paper
In the initial construction and in follow-up projects during the life cycle of the plant, these stakeholders
produce large volumes of 3D data using a variety of software solutions. It has traditionally been a time-
consuming and costly process to map source model graphics and object property files into common
formats that can be viewed and modeled against for construction planning and execution.
Later during O&M, software components may change over time. Data formats become incompatible and
require conversion before data can be reused for similar designs and construction. Converting 3D models
from one format to another before reuse dramatically increases the owner’s cost during the plant’s lifetime
– when 3D data availability is most critical for maintenance, modification, and decommissioning.
Intergraph’s interoperability technology incorporates valuable model data from many sources and helps
eliminate the “big bite” of converting legacy 3D models for construction and O&M projects.
As a capability built into Smart 3D, 3D Interop gives users the ability to intelligently reference external 3D
model data in the Smart 3D environment. Such external data might have been created from other typical
sources:
Another Smart 3D model
Other Intergraph products such as PDS or CADWorx
Third-party model such as PDMS or Tekla
AutoCAD or MicroStation file
These files are converted for use with 3D Interop. The resulting converted files are then referenced,
positioned, rotated, and scaled in the Smart 3D Project Management application. Generic files can
have optionally generated schema and mapping files and, like other supported types, map their data to
3D Interop properties. Once referenced; the 3D Interop model data is available for use in the Smart 3D
model for interactive design, including connectivity, clash checking, drawings, and more. An important
aspect of the 3D Interop technology is the fact that the catalog and specification information from the
third-party system is NOT required. The data from external models is expected as a set of matching
graphic (.zvf) and data (.xml or .drv) files. This feature significantly augments the current global
workshare solution, because it does not require replicated model or catalog databases.
20
Interoperability Summary: Leveraging 3D Designs & Data White Paper
21
Interoperability Summary: Leveraging 3D Designs & Data White Paper
The following features and benefits in converting model data to Smart 3D show PlantReModeller
capabilities result in extremely fast project completion with a very high success rate. The solution:
Reads the 3D model data directly from the schema, so setup of source data is minimal and
straightforward.
Allows designer control of the import with minimal training. PlantReModeler presents a list of the
data available; end users can select items for import – from individual objects to an entire project.
Provides rapid conversion and delivery of results; this often reduces the migration time from
months to just days or weeks.
Achieves migration goals at a much lower cost and with less resources than manual migration
methods. Typically, the PlantReModeler process cost is 60-70 percent of manual remodelling
costs, based on low-cost center conversion services provided by CAXperts.
Helps owners (and EPCs) achieve conversion time savings through PlantReModeller’s
capabilities for generic component placement that require specs containing pipes only with no
components. Each component is placed separately as a generic component with the graphic
definition. Attribute information is transferred.
Helps align and validate specs from the source system and target system (Smart 3D).
Uses Smart 3D command environment to edit data from the source and develop as needed.
Technology such as PlantReModeller can help deliver an intelligent model that can be edited and further
developed within Smart 3D. Intergraph highly recommends using the CAXperts technology when the
conversion project meets the following criteria:
An exact replica of the model is not required
There is not sufficient time in the project schedule to allow for exact spec/component mapping
between the source and Smart 3D
The original model has outdated specs and/or components and requires rework
Only part of the model is required for reuse on a new project
Non-intelligent graphics must also be translated
The designer needs to retain control of the data being brought into Smart 3D
22
Interoperability Summary: Leveraging 3D Designs & Data White Paper
For example, in a situation where Smart 3D data is exported to Aveva’s PDMS, PDMS 12.x supports the
system hierarchy of plants. Its Lexicon module allows users to create user-defined types (UDETs) based
on ZONE type and map them to the Smart 3D system. Incremental export can occur as data is needed
from Smart 3D (see Figure 8).
Smart 3D designs exported to PDMS can have different intelligence levels that can be controlled through:
Mapping between Smart 3D and PDMS data
Initialization and customization for specific project needs
23
Interoperability Summary: Leveraging 3D Designs & Data White Paper
Smart 3D provides a number of built-in productivity tools to assist with the conversion to PDMS and boost
project team productivity. These include:
Receive warning for missed and many-to-many mapping through discipline-based mapping
Customize to fit project needs with Smart 3D filters
Eliminate export order dependencies thanks to object connections
Automate object naming/geometry grouping
Support plant and marine world objects of Smart 3D
Maintain intelligence of exported Smart 3D designs and data
Export-to-PDMS capability is an add-on tool to Smart 3D. Customers can manage their own configuration
and use of the export solution, but even advanced Smart 3D users typically request Intergraph assistance
to get started and deal with the specifications, catalog data, dynamic checking of mapping, and Smart 3D
reference data. The export to PDMS tool was designed with the following engineering characteristics:
Scalable for large-scale projects
Dual mode of export of graphics with properties or by mapping
Integration with SPRD and SDB drastically reduces catalog creation time
Less training time needed to start the implementation
100 percent Smart 3D .Net compliant
24
Interoperability Summary: Leveraging 3D Designs & Data White Paper
8. Conclusion
Intergraph offers interoperability technology that helps protect and leverage valuable model data from
many project sources and formats. This paper highlights Intergraph’s interoperability capabilities that
eliminate the “big bite” of converting legacy 3D models for process, power, and marine projects.
This white paper explores five scenarios (and relevant interoperability technology) to reuse 3D data
throughout the design, construction, handover, and operations and maintenance (O&M) phases of the
plant life cycle. These scenarios include:
1. (Design Phase) Reuse data for Smart 3D design (3D Interop)
2. (Design Phase) Full conversion to Smart 3D (Importers)
3. (Construction and O&M) Provide 3D data from multiple formats during construction and O&M
(3D Interop)
4. (O&M Design) Engineering in O&M (CAXperts)
5. (Handover) Conversion from Smart 3D to meet client handover requirements and specifications
(Exporters)
Each scenario was discussed in the context of leveraging data (through conversion and referencing)
between Intergraph’s Smart 3D, PDS, and CADWorx formats and Aveva’s PDMS environments.
25
Interoperability Summary: Leveraging 3D Designs & Data White Paper
9. Definitions
Table 4: This is a list of the definitions of the terms used in this white paper.
Term Definition
Conversion Changing one form of encoded software data to another form
Convert to ZVF utility Translates PDS and/or PDMS data to read-only Smart 3D data
DATAL Data exchange format of PDMS 3D designed data, for importing to PDMS software or
exporting from PDMS
Export to PDMS An export tool added-on to Smart 3D to convert data from Smart 3D to PDMS
Import from PDMS An import tool added-on to Smart 3D to convert data from Smart 3D to PDMS
JV Joint venture projects managed by multiple stakeholders
Mapping Process of identifying the suitable match of objects, properties between the source
(PDMS model) and destination (Smart 3D model) and their corresponding Reference
Data (parts, materials, cross sections, specifications, etc.) between the source (PDMS
catalog) and destination (Smart 3D catalog)
MCAD Mechanical Computer-aided Design
Migrate Transferring data between storage types, formats, or computer systems
Model Data The three-dimensional representation of geometric images
OOTB Out of the Box: refers to functionality, capabilities, configurations, utilities, and
automation routines that are standard to a software product
PDMS Plant Design Management System: 3D design solution for plant industries from Aveva
PDS Plant Design System: 3D design solution for plant industries from Intergraph
Reference Data Data associated with the 3D model used to create intelligent “rules” for design
Referencing Referring to designs and data in different formats from the current design file
Schema A data model of a specific domain expressed in terms of a particular data management
technology related to relational tables and columns, object-oriented classes, or XML tags
SDB Intergraph Standard Database
Smart 3D Intergraph’s Smart 3D which combines the former SmartPlant 3D and SmartMarine 3D
Smart 3D Convert Converts Smart 3D plant data mode to Marine or Material Handling mode
Database Mode
Utility
Smart 3D Database Converts Smart 3D data between database platforms (MS SQL Server to Oracle or
Conversion Wizard Oracle to MS SQL Server)
Smart 3D Translators Exports/imports PDS and/or PDMS data from or to native (editable) Smart 3D data
Module (which can be published to SPF)
SPC SmartPlant Construction from Intergraph
SPF SmartPlant Foundation from Intergraph
SPIOP SmartPlant Interop Publisher from Intergraph: translates PDS and/or PDMS data to
read-only SmartPlant Review and Smart 3D data (which can be published to SPF)
SPR SmartPlant Review from Intergraph
SPRD SmartPlant Reference Data from Intergraph
Translation Changing one form of encoded software data to another form
Upgrade Transferring data between versions of data formats
26
For more information about Intergraph, visit our website at
www.intergraph.com.