SmartPlant® Enterprise Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
Version 1.11
July 2014
Copyright Copyright © 2011 - 2014 Intergraph ® Corporation. All Rights Reserved. Intergraph is part of Hexagon . Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.
U.S. U.S. Government Restricted Rights L egend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3. Unpublished - rights reserved under the copyright laws of the United States. Intergraph Corporation 305 Intergraph Way Madison, AL 35758
Documentation Documentation shall mean, whether in electronic or printed form, User's Guides, Installation Guides, Reference Guides, Administrator's Guides, Customization Guides, Programmer's Guides, Configuration Guides and Help Guides delivered with a particular software product.
Other Documentation Other Documentation shall mean, whether in electronic or printed form and delivered with software or on Intergraph Smart Support, SharePoint, or box.net, any documentation related to work processes, workflows, and best practices that is provided by Intergraph as guidance for using a software product.
Terms of Use a.
Use of a software product and Documentation is subject to the End User License Agreement ("EULA") delivered with the software product unless the Licensee has a valid signed license for this software product with Intergraph Corporation. If the Licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product and Documentation. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives Licensee permission to print a reasonable number of copies of the Documentation as defined in the applicable license agreement and delivered with the software product for Licensee's internal, non-commercial use. The Documentation may not be printed for resale or redistribution.
b.
For use of Documentation or Other Documentation where end user does not receive a EULA or does not have a valid license agreement with Intergraph, Intergraph grants the Licensee a non-exclusive license to use the Documentation or Other Documentation for Licensee’s internal non-commercial use. Intergraph Corporation gives Licensee permission to print a reasonable number of copies of Other Documentation for Licensee’s internal , non-commercial use. The Other Documentation may not be printed for resale or redistribut ion. This license contained in this subsection b) may be terminated at any time and for any reason by Intergraph Corporation by giving written notice to Licensee.
Disclaimer of Warranties Except for any express warranties as may be stated in the EULA or separate license or separate terms and conditions, Intergraph Corporation disclaims any and all express or implied warranties including, but not limited to the implied warranties of merchantability and fitness for a particular purpose and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such disclaimer. Intergraph believes the information in this publication is accurate as of its publication date. The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document. The software, Documentation and Other Documentation discussed in this document are furnished under a license and may be used or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT. Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work.
Limitation of Damages Damages IN NO EVENT WILL INTERGRAPH CORPORATION BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF REVENUE OR PROFIT, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF INTERGRAPH CORPORATION HAS BEEN ADVISED OF THE POSSIBILITY POSSIBILITY OF OF SUCH DAMAGES. DAMAGES. UNDER NO CIRCUMSTANCES SHALL INTERGRAPH CORPORATION’S LIABILITY EXCEED THE AMOUNT THAT INTERGRAPH CORPORATION HAS BEEN PAID BY LICENSEE UNDER THIS AGREEMENT AT THE TIME THE CLAIM IS MADE. EXCEPT WHERE PROHIBITED BY APPLICABLE LAW, NO CLAIM, REGARDLESS OF FORM, ARISING OUT OF OR IN CONNECTION WITH THE SUBJECT MATTER OF THIS DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2) YEARS AFTER THE EVENT GIVING RISE TO THE CAUSE OF ACTION HAS OCCURRED. IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, THEN INTERGRAPH LIMITS ITS LIABILITY TO THE MAXIMUM EXTENT ALLOWED BY SAID LAW.
Export Controls Intergraph Corporation’s software products and any third-party Software Products obtained from Intergraph Corporation, its subsidiaries, or distributors (including any Documentation, Other Documentation or technical data related to these products) are subject to the export control laws and regulations of the United States. Diversion contrary to U.S. law is prohibited. These Software Products, and the direct product thereof, must not be exported or re-exported, directly or indirectly (including via remote access) under the following circumstances: a.
To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries.
b.
To any person or entity listed on any U.S. government denial list, including but not limited to, the U.S. Department of Commerce Denied Persons, Entities, and Unverified Lists, http://www.bis.doc.gov/complianceandenforcement/liststocheck.htm, the U.S. Department of Treasury Specially Designated Nationals List, http://www.treas.gov/offices/enforcement/ofac/, and the U.S. Department of State Debarred List, http://www.pmddtc.state.gov/compliance/debar.html.
c.
To any entity when Licensee knows, or has reason to know, the end use of the Software Product is related to the design, development, producti on, or use of missiles, chemical , biological, or nuclear weapons, or other un-safeguarded or sensitive nuclear uses.
d.
To any entity when Licensee knows, or has reason to know, that an illegal reshipment will take place.
Any questions questions regarding regarding export or re-export re-export of these Software Software Products Products should be addressed to Intergraph Intergraph Corporation’s Corporation’s Export Export Compliance Departmen Department, t, Huntsville, Alabama Alabama 35894, 35894, USA. Intergraph, the Intergraph logo, Intergraph Smart, PDS, SmartPlant, SmartMarine, FrameWorks, I-Sketch, IntelliShip, ISOGEN, SmartSketch, SPOOLGEN, SupportManager, SupportModeler, Sapphire, and FreeView are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Hexagon and the Hexagon logo are registered trademarks of Hexagon AB or its subsidiaries. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product names are trademarks of their respective owners.
Intergraph Proprietary Information
Using Inst rum ent Dimension al Data Data to Drive 3D De Desig sig n This work process, primarily involving SmartPlant® SmartPlant® Instrumentation and Intergraph Smart™ 3D, can be driven with or without the P&IDs. The recommended process is to use the P&IDs.
Work Process Diagram 1: Using inst rument dimensional data to dr ive 3D design with P&IDs (Recommended process).
Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
4
Intergraph Proprietary Information without P&IDs P&I Ds . Work Process Diagram 2: Using inst rument dimensional data to dr ive 3D design without
1.
Any red/dashed process step in the the diagram has associated precautions precautions that should be carefully reviewed reviewed prior to implementation. These precautions precautions are italicized in the sections below, and the step number is referenced. Steps with rounded corners represent tasks that are automated by the software, with required configuration.
2.
Most engineering work processes processes are not sequential, but instead instead are parallel and iterative. The Start and Repeat boxes boxes in the diagram represent the boundaries of the work process associated with this capability statement, rather than the start and end of a purely sequential engineering work process.
3.
The step Review and approve for publish is a timing decision made by the project, depending on many factors. Some of these factors are discussed in the Publish and Retrieve Considerations section Considerations section below.
Short Description of Work Process In Smart 3D, you can place instruments using one of two d ifferent methods: stock instruments instruments defined in the Catalog, or non-stock (on-the-fly) instruments. DDP integration only applies to non-stock instruments. This work process enables the Instrument Engineer to have full control of all the instrument data required in the 3D model, including the dimensional group, physical dimensions, as well as weight and connection properties. The Instrument Engineer specifies the physical dimensions for types of instruments in SmartPlant Instrumentation. This is published to SmartPlant Foundation Foundation and retrieved to Smart 3D (in the design basis) where the item is available for Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
5
Intergraph Proprietary Information placement, either by selecting the instrument from the P&ID or, if the P&ID is not used, by selecting the tag number from a list of instruments in the design basis. The 3D instrument is created based on the data provided by the Instrument Engineer.
Business Value
Provides the ability ability to manage all instrumentation instrumentation data in in a single environment environment used by Instrument Instrument Engineers (SmartPlant (SmartPlant Instrumentation) for for re-use in the 3D model, eliminating duplicate entries, which improves efficiency and data quality. Improve project schedule schedule and data quality quality by automatically automatically identifying changes to instruments instruments (updates, additions, additions, deletions, and and renamed items) in one one engineering discipline, discipline, and by deciding how and when to apply these changes in another discipline later in the work process. Reduces the hours required by the 3D designer designer to locate locate and input input the physical physical dimensions for instruments.
General Requirements
Applications must be registered with with SmartPlant Foundation prior prior to performing performing publish publish and retrieval operations. operations. PBS structures must be be consistent across across the applications applications before integrating. When data in an application application has been created created in a non-integrated environment, it is possible the PBS structure may not be compatible with requirements for integration. When this situation arises, r estructuring of the PBS is required. For additional information, please review the Integration Capability Statement Defining a Plant Breakdown Structure for Integration. Integration.
Item Tagging must be consistent consistent across across the enterprise enterprise in order for correlation and retrieval to to function properly. properly.
SmartPlant Interop Interop Publisher Publisher uses only revisions revisions managed managed by SmartPlant SmartPlant Foundation Foundation in an integrated integrated environment.
Integration is not not supported supported in a heterogeneous heterogeneous internationalization environment.
Integration is not not supported supported with with applications applications in Project/As-built Project/As-built mode.
Special configuration configuration considerations considerations are required when using using workshare in conjunction conjunction with integration. integration. For implementations, implementations, including combinations combinations of workshare, handover, and integration, please consult the SmartPlant Enterprise Support organization. Check the validity validity and correctness of the data from both internal departments and and external partners before publishing documents, to ensure ensure the same standards are used. Use both the data integrity functions provided in each tool and other quality checks to resolve data integrity issues. Refer to each product’s product’s Compatibility Matrix on the Intergraph Intergraph Smart Support web site site for information on the compatibility of the versions of PP&M products used in your environment, as well as with versions of operating systems, service packs, databases, and other pre-requisite products.
Publish and Retrieve Retrieve Considerations
In a SmartPlant integrated integrated environment, publishing a document document is not synonymous synonymous with issuing a document. document. Publishing is for sharing data between engineering disciplines, prior to completing the design and issuing the document. When publishing, publishing, you have the option option of using the auto-correlate auto-correlate workflow, which loads loads the published published document and data into into the SmartPlant Foundation database, compares specific object data from different sources, and automatically correlates representations of the same object from different tools.
Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
6
Intergraph Proprietary Information
Publishing a document with the PublishForLoadOnly workflow allows you store the data in SmartPlant Foundation so that it can be reviewed and compared with data from other tools. However, when published using this workflow, a document cannot be retrieved into other authoring tools. You can also configure custom workflows, for instance workflows for review and approval that control when documents can be retrieved, by setting the SPFTEFIsRetrievable property SPFTEFIsRetrievable property of the document. In the early phases phases of design, when data is very preliminary, preliminary, publishing and and retrieving should be be infrequent. As design design progresses, you may consider publishing on a regular schedule, for example every two weeks, and as you approach any milestone, you should consider increasing the frequency of publish and retrieve operations. In general, disciplines disciplines that create documents documents that are heavily heavily relied upon by downstream disciplines, disciplines, such as the the Process discipline discipline and its P&IDs, should consider the impact of their changes to downstream applications and make an additional unscheduled publish as a result of significant changes. If a document is undergoing major revisions revisions that are not not completed in time for a scheduled publish, publish, the publishing publishing of that document should should be delayed until the revisions are completed, to prevent unnecessary changes in the downstream applications. If the catalog or reference reference data has recently recently been updated, updated, you should ensure ensure that the design data has been synchronized synchronized with the updated updated catalog or reference data prior to publishing. Before publishing any document, a new new revision can be obtained from SmartPlant SmartPlant Foundation, if required. required. If a new revision revision is not required, simply simply publish the document. Publishing can be be configured to send send an email notification notification automatically using a SmartPlant Foundation Foundation workflow, which can can send the email to a list of recipients by document type. Alternatively, the user can select an email notification workflow at actual publish time. In this way, the email recipient is alerted that a document is available for retrieval. Documents can be be published to any owning group available available in SmartPlant Foundation. Foundation. To retrieve a document document published published with an owning group, a user must have permissions configured in SmartPlant Foundation Foundation to allow them to retrieve documents in that owning group. This feature could be useful in a multi-EPC environment.
SmartPlant SmartPlant Instrumentation
Smart 3D
Current tool version
Current tool version
SmartPlant Instrumentation 2013 and later
Tool configuration dependencies (options, switches, configurations etc)
If using workshare for SPP&ID, you must publish from the SPP&ID Host site; therefore, P&IDs owned by a workshare satellite must first be transferred to the Host site, then can be published at the Host. (5,8 Diagram 1)
Ensure that all the DDP (Dimensional Data for Piping) groups defined in Smart 3D have been loaded in SmartPlant Instrumentation before publishing the DDPs.
Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
Smart 3D 2014 and later
Tool configuration dependencies (options, switches, configurations etc)
Nested symbols, such as a symbol for the main body of a control valve that calls another symbol for the actuator, are not supported with this integration. For these situations, the symbol must include all parts. In other words, in this example, the symbol must include the body and the actuator. The instrument symbols are based on prominent instrument manufacturer catalogs, including Rosemount, Endress+Hauser, Daniel, Brooks, and 7
Intergraph Proprietary Information SmartPlant SmartPlant Instrumentation
Enable switch called "Dimensional Data" in t he instrument type profile
Use the IntoolsEF.db as the seed database for SmartPlant Instrumentation
Smart 3D Yokogawa. Likewise, the control valve and actuator symbols are based on manufacturer catalogs, e.g. Fisher and Samson. The Smart 3D symbols and the SmartPlant Instrumentation symbols (DDPs) have been made available on the Intergraph Smart Support web site, which is updated once a month. A bitmap is available for each instrument and control valve symbol as a means of documenting the dimensional basis of the symbol. If a suitable symbol is not available, the user can request that a new symbol be developed at no cost to the user, if the following criteria are satisfied: 1) the user provides the manufacturer’s catalog for the instrument or control valve; and 2) Intergraph’s schedule for delivering the symbol on the Intergraph Smart Support web site is acceptable to the user.
Refer to existing integration documentation for further configuration details, including the Working with Integration in t he SmartPlant Instrumentation Basic Engineering User’s Guide and the Integration Administrator’s Guide.
To download the content from the Intergraph Smart Support site, go to https://smartsupport.intergraph.com, https://smartsupport.intergraph.com, then browse to Smart3D > Content > Current Version Updates / Plant Content (Current) > SmartPlant Instruments DDPs.
Tool processes leading up to publish to ensure successful completion (e.g. (e.g. tag u niqueness, etc)
All piperuns with inline inline instruments must must have the flow direction direction defined, with “End 1 Upstream” or “End 1 Downstream”. Bidirectional flow is not supported. This applies to the piperuns in the P&ID that will be published to SmartPlant Instrumentation.
Publishing process timing and frequency
The project must plan for intervals when all the P&IDs owned by a workshare Satellite are transferred to the Host site in order to publish the
Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
New custom instrument part classes can be created and associated to SmartPlant Instrumentation dimensional groups. This is not a tr ivial process; see the first bullet above. Refer to existing integration document for further configuration details, including the Intergraph Smart™ 3D Integration Plant Mode Reference Guide and Integration Administrator’s Guide. When Smart 3D communicates with SmartPlant Foundation, your OS user name must must match a SmartPlant Foundation Foundation account. If the OS user name does not match a SmartPlant Foundation account, you cannot perform integration operations, such as publish.
Tool processes leading up to retrieve to ensure successful com pletion (e.g. (e.g. tag u niqueness, etc)
NA
Retrieving process timing and frequency
The following only applies when using SmartPlant P&ID: 8
Intergraph Proprietary Information SmartPlant SmartPlant Instrumentation
Smart 3D
P&IDs. Progress on the P&IDs should not continue at the Satellite (although this is technically possible in standalone workshare) until the P&IDs have been transferred back to the Satellite. (5,8 Diagram 1)
Instrument dimensions (DDPs) should be published as soon as they are available from SmartPlant Instrumentation so that the piping designer can model accurate instruments in Smart 3D. DDPs (one per instrument) can be published whenever data is completed for any set of instruments in SmartPlant Instrumentation.
The timing for retrieval of DDPs should be based on the P&IDs that have been retrieved. This will facilitate placement of the instrument with appropriate DDP information from the P&ID design basis. basis .(19 Diagram 1)
The deletion of tags (equipment, instruments, and so forth) that have been published previously should result in the republishing of the documents where they existed as soon as possible.
Ar e ther e any o th er to ol s t hat p art ici pate i n th is i nt egr atio n on th e publish side
The physical dimensions of the instruments in SmartPlant Instrumentation can be supplied by the instrument vendor via export/import.
Ar e ther e any o th er to ols th at par ti cip ate in th is i nt egrat ion on t he retrieve side
SmartPlant P&ID. For more information, see the capability statement P&ID Guided 3D Design and Consistency Checking Checking . The following only applies when using SmartPlant P&ID:
Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
P&IDs retrieved into Smart 3D prior to the retrieval of DDP information contain additional data (e.g. topology and pipe run data) that can be used to augment the placement process of the instrument in the 3D model. It is important important to retrieve the P&ID into SmartPlant Instrumentation and correlate the SmartPlant P&ID instrument to t he SmartPlant Instrumentation instrument prior to publishing the DDP to Smart 3D. This is necessary necessary in order order to have a single instrument instrument and proper connection (port) representation in the 3D design basis. See the section on correlation in the "Tool processes leading up to publish to ensure completion" for more information. (10 Diagram 1)
9
Intergraph Proprietary Information SmartPlant SmartPlant Instrumentation
Smart 3D
Work process aspects to consider and what limitations/constraints apply
Work process aspects to consider and what limitations/constraint s apply
NA
The following only applies when using SmartPlant P&ID:
It is recommended to place the instrument by selecting it in the P&ID design basis; i.e. the P&ID Viewer. (23 Diagram 1)
The 3D designer typically models from the P&IDs by viewing one P&ID in the P&ID Viewer window, and when finished working with this P&ID, moves on to the next P&ID to work with until all the required P&IDs have been viewed. (20 Diagram 1) You can update an existing Smart 3D instrument with new DDP data without deleting and replacing the instrument, unless the topology of the instrument changes (for instance, with a different number of ports, or with different body angles, in which case deleting the old instrument is recommended). (19 Diagram 1; 6 Diagram 2) There are two possible scenarios to update the instrument, depending on whether the existing instrument was placed with or without DDP data:
Mapping considerations for publish
To add a new instrument dimensional group:
Modify Intoolsmap.xml file to add new new SPMapClassDef SPMapClassDef for the new new group (Use existing group for defining the Map Class Definitions)
Add the new DIM Group to the Enumlist
Map the desired properties
If the existing instrument was initially placed without DDP data, use the Design Basis Viewer to update the instrument with the new DDP data.
The Insert Component command displays a list of retrieved instrument tags, thus eliminating the need to remember and key in the tag number.
Mapping considerations for retrieve
Out-of-the-box delivered content includes mapping of DDP properties for retrieval. When adding a new DDP in SmartPlant Instrumentation, add the new Dimension Group in Smart 3D and in the SmartPlant Schema.
The following only applies when using SmartPlant P&ID:
Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
If the existing instrument was initially placed with DDP data, use the Compare Design Design Basis command, Basis command, and select Update, Update, to update the instrument with the new DDP data.
SmartPlant P&ID 2009 Service Pack 4 and 2009 Service Pack 3 HF10 introduced the relationship OwnsComponentOcc (OCC) to correctly 10
Intergraph Proprietary Information SmartPlant SmartPlant Instrumentation
Smart 3D assign component ownership at specification breaks. By default, this relationship is not mapped between the SmartPlant P&ID map file (SPPIDDataMap.xml) and the SmartPlant Schema.
Naming Convention constraints for publish
When publishing publishing P&ID drawings drawings for use by Smart 3D, you should update the SPPIDDataMap.xml to include the OCC relationship. If you do not include this relationship, the new auto-correlation in Smart 3D 2011 R1 and later places the piping component in the ambiguous section of the auto-correlate dialog instead of assigning the component to the correct piperun. However, when publishing P&ID drawings for use use by SmartPlant Instrumentation 2009 Service Pack 2 or earlier, you should continue to exclude this relationship. The relationship may cause SmartPlant Instrumentation to switch between the two piperuns at the spec break each time the P&ID is retrieved.
Naming Convention constraints for retrieve
NA
NA
Data Warehouse Current version
SmartPlant Foundation 2014 and later
Configuration precautions
Modify the CMF file to add the new DIM Group to the Enumlist
Map the desired properties (Publish/Retrieve)
General Considerations
What is the document con tainer (eg P&ID) P&ID) being published?
Instrument DDP
For what other purposes can this published document be used? The instrument DDP published document is used for this integration work process and the data and document document are loaded into the SmartPlant Foundation Foundation repository for viewing and navigating navigating data. The instrument tag on the DDP can be used for auto-correlation. Once correlated, it is possible to navigate navigate to the DDP document document from other documents. documents.
Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
11
Intergraph Proprietary Information
What is the scope of data/content data/content being publ ished OOTB, OOTB, or where can can I find that info rmation in the user docum entation Refer to the SmartPlant Enterprise Data Exchange flow diagrams and SmartPlant Adapter for SmartPlant Instrumentation Guide, SmartPlant Adapter f or Intergraph Smart™ 3D Guide posted on the Intergraph Smart Support Support web site under Product Documentation. Does this integration suppo rt publis h/compare in SPF SPF (e.g. (e.g. is it a likely candidate for interdiscipl inary consist ency check)? The data contained on the instrument instrument DDP is tailored for providing the physical dimensions dimensions to construct the 3D model. It is not a likely candidate for publish/compare. Is a graphic file published and is it hot spotted in SPF? In work process 1 involving involving SmartPlant SmartPlant P&ID, yes, the P&ID is a graphic graphic file and is hotspotted.The DDP document publish includes a viewable file showing the physical dimensions; however, it is not hotspotted. Ar e ther e lim itat io ns o n au to -cor relat ion in SPF? The instrument tag published with the instrument instrument DDP can be used used for autocorrelation autocorrelation as long as it matches, exactly, the tags of previously loaded instruments. However, piping ports on instruments from Smart 3D and SmartPlant Instrumentation are not auto-correlated in SmartPlant Foundation. What is the content being extracted out of the document con tainer being retrieved? properties.
Instrument physical physical dimensions, dimensions, weight, weight, and connection
Documentation SmartPlant SmartPlant Instrumentation
Smart 3D
Enterprise Work Process for Instrumentation
Enterprise Work Process for Piping and Equipment Design
SmartPlant Instrumentation Administration User’s Guide
Piping User's Guide (plant mode)
Define and Map DDP Data Dimensional Data and Piping
Integration Administrator’s Guide
Correlating Instruments
SmartPlant Instrumentation Detailed Engineering User’s Guide
SmartPlant Instrumentation Basic Engineering User’s Guide
Import DDP Library Data
SmartPlant Instrumentation in an Integrated Environment
SmartPlant Instrumentation Installation and Upgrade Guide
Working with SmartPlant Integration
Preparing the Integrated Environment
Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
12
Intergraph Proprietary Information Work Process Documentation Updates The full set of available Integration Capability Statements and Enterprise Work Process guides is on Intergraph Smart Support under View Documentation > Work Process Guides. Guides . Access the Intergraph Smart Support Web site for the most up-to-date information about all Intergraph Work Process guides. To access the Intergraph Smart Support W eb site, browse to the following site, https://smartsupport.intergraph.com, https://smartsupport.intergraph.com, and type your user name and password. Intergraph gives its customers permission to print as many copies of the delivered PDF files as they need for their non-commercial use. Do not print the PDF files for resale or redistribution.
Revision Revision History Version
Date
Change
1.2
2/27/12
Added cover page and legal disclaimer
1.3
3/26/12
Added Review and approve to diagram
1.4
6/1/12
Minor updates to Publish and Retrieve Considerations and General Considerations; update to software version references.
1.5
8/21/12
Updated SmartPlant Foundation version information.
1.6
1/3/13
Revised statement about instruments placed in early phase of design before DDP is available.
1.7
3/25/13
Added SPP&ID 2009 SP3 HF10 to the OwnsComponentOcc (OCC) precaution. Added note about instrument on P&ID piperun with bidirectional flow not being supported.
1.8
7/16/13
Added information about about using PublishForLoadOnly workflow to compare data and restrict a document from being retrieved by other tools and publishing and retrieving using owning groups. Added references to Engineering Work Processes in documentation section. Updated SPI version to 2013, and SmartPlant Foundation version to 2014.
1.9
9/23/13
Updated product name to Intergraph Smart™ 3D. Updated version to 2014.
1.10
2/17/14
Removed the precautions for diagram 1 steps 12 & 15 and for diagram 2 steps 6 & 7, and adjusted the work process diagrams accordingly. Added a reference to the P&ID Guided 3D Design and Consistency Checking capability statement. Replaced references to eCustomer with references to Intergraph Smart Support.
1.11
6/27/14
Updated the precaution under Work process aspects to consider for consider for Smart 3D, regarding updating instruments previously placed with or without DDP data. Added the Smart 3D tool configuration dependency that nested symbols are not supported.
Integration Capability Statements Using Instrument Dimensional Data to Drive 3D Design
13
