smartplant® enterprise work process for process design work... · smartplant® enterprise ....

SmartPlant® Enterprise Enterprise Work Process for Process Design

Version 2.0 April 2017

Hexagon PPM Proprietary Information

Enterprise Work Process for Process Design 2

Copyright Copyright © 2012 - 2017 Hexagon AB and/or its subsidiaries and affiliates. All rights reserved.

This computer program, including software, icons, graphic symbols, documentation, file formats, and audio-visual displays; may be used only as pursuant to applicable software license agreement; contains confidential and proprietary information of Hexagon AB and/or third parties which is protected by patent, trademark, copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from Hexagon AB and/or its subsidiaries and affiliates.

U.S. Government Restricted Rights Legend 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 Software License Agreement ("SLA") 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 SLA 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 redistribution. 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 SLA 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 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 OF SUCH 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 commercial-off-the-shelf software products, customized software and/or third-party software, including any technical data related thereto (“Technical Data”), obtained from Intergraph Corporation, its subsidiaries or distributors, is subject to the export control laws and regulations of the United States of America. Diversion contrary to U.S. law is prohibited. To the extent prohibited by United States or other applicable laws, Intergraph Corporation software products, customized software, Technical Data, and/or third-party software, or any derivatives thereof, obtained from Intergraph Corporation, its subsidiaries or distributors must not be exported or re-exported, directly or indirectly (including via remote access) under the following circumstances:

a. To Cuba, Iran, North Korea, the Crimean region of Ukraine, or Syria, or any national of these countries or territories. b. To any person or entity listed on any United States government denial list, including, but not limited to, the United States Department of Commerce Denied Persons, Entities, and Unverified Lists, the United States Department of Treasury Specially Designated Nationals List, and the United States Department of

State Debarred List (https://build.export.gov/main/ecr/eg_main_023148). c. To any entity when Customer knows, or has reason to know, the end use of the software product, customized software, Technical Data and/or third-party software obtained from Intergraph Corporation, its subsidiaries or distributors is related to the design, development, production, or use of missiles, chemical,

biological, or nuclear weapons, or other un-safeguarded or sensitive nuclear uses. d. To any entity when Customer knows, or has reason to know, that an illegal reshipment will take place.

Any questions regarding export/re-export of relevant Intergraph Corporation software product, customized software, Technical Data and/or third-party software obtained from Intergraph Corporation, its subsidiaries or distributors, should be addressed to PPM’s Export Compliance Department, 305 Intergraph Way, Madison, Alabama 35758 USA or at [email protected]. Customer shall hold harmless and indemnify PPM and Hexagon Group Company for any causes of action, claims, costs, expenses and/or damages resulting to PPM or Hexagon Group Company from a breach by Customer.



Intergraph®, the Intergraph logo®, Intergraph Smart®, SmartPlant®, SmartMarine, SmartSketch®, SmartPlant Cloud®, PDS®, FrameWorks®, I-Route, I-Export, ISOGEN®, SPOOLGEN, SupportManager®, SupportModeler®, SAPPHIRE®, TANK, PV Elite®, CADWorx®, CADWorx DraftPro®, GTSTRUDL®, and CAESAR II® are trademarks or registered trademarks of Intergraph Corporation or its affiliates, parents, subsidiaries. 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.

Table of Contents Work Process for Process Design ................................................................................................................................................................................................................................................................................................................................................. 5

Introduction .................................................................................................................................................................................................................................................................................................................................................................................. 5 How to Use this Document .......................................................................................................................................................................................................................................................................................................................................................... 5 Contents ...................................................................................................................................................................................................................................................................................................................................................................................... 6 Notes about this Work Process ................................................................................................................................................................................................................................................................................................................................................... 6

Assumptions ......................................................................................................................................................................................................................................................................................................................................................................... 6 General Notes ....................................................................................................................................................................................................................................................................................................................................................................... 6 Publish and Retrieve Recommendations.............................................................................................................................................................................................................................................................................................................................. 7

Process Design Work Process - FEED - Level 1 Diagram ......................................................................................................................................................................................................................................................................................................... 9 Process Design Work Process - FEED - Level 1 ...................................................................................................................................................................................................................................................................................................................... 10

Develop P&IDs (Rev 0 and 1) - FEED - Level 2 Diagram .................................................................................................................................................................................................................................................................................................. 11 Develop P&IDs (Rev 0 and 1) - FEED - Level 2 ................................................................................................................................................................................................................................................................................................................. 12

Process Design Work Process - Basic Engineering - Level 1 Diagram .................................................................................................................................................................................................................................................................................... 15 Process Design Work Process - Basic Engineering - Level 1 .................................................................................................................................................................................................................................................................................................. 16

Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 Diagram .............................................................................................................................................................................................................................................. 18 Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 ............................................................................................................................................................................................................................................................. 19

Process Design Work Process - Detailed Design - Level 1 Diagram ....................................................................................................................................................................................................................................................................................... 23 Process Design Work Process - Detailed Design - Level 1 ...................................................................................................................................................................................................................................................................................................... 24

Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 Diagram .............................................................................................................................................................................................................................................. 25 Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 ............................................................................................................................................................................................................................................................. 26

Appendix .................................................................................................................................................................................................................................................................................................................................................................................... 30 Check Data Consistency - Instrumentation ........................................................................................................................................................................................................................................................................................................................ 31 Check Data Consistency - Equipment ................................................................................................................................................................................................................................................................................................................................ 32 Check Data Consistency - Piperuns ................................................................................................................................................................................................................................................................................................................................... 33 Validate Engineering Integrity - Diagram ............................................................................................................................................................................................................................................................................................................................ 34 Validate Engineering Integrity ............................................................................................................................................................................................................................................................................................................................................. 35 P&ID Guided 3D Design and Consistency Checking ......................................................................................................................................................................................................................................................................................................... 36 Checking Instrument Consistency Between P&IDs and Instrumentation ........................................................................................................................................................................................................................................................................... 37 Defining Electrical Consumers from P&IDs ........................................................................................................................................................................................................................................................................................................................ 38 Creating Line Lists in SmartPlant Foundation .................................................................................................................................................................................................................................................................................................................... 39 Sharing Data between PFDs and P&IDs ............................................................................................................................................................................................................................................................................................................................ 40

Revision History......................................................................................................................................................................................................................................................................................................................................................................... 41



Work Process for Process Design

Introduction The Hexagon PPM Work Process guides map the process, power, and marine industries’ basic work processes to Hexagon PPM solutions. This documentation helps your organization transition from previous work practices to using Hexagon PPM tools as the new way of executing projects, and includes:

Enterprise Work Processes to describe an entire engineering discipline or process at two different levels:

Providing a swim lane diagram to define the typical roles and high-level processes involved in a project

Showing how Hexagon PPM tools are used to produce required deliverables

Integration Capability Statements to describe a specific work process among a set of Hexagon PPM tools:

Explaining the out-of-the-box capabilities of the tools and their recommended use

Providing a swim lane diagram to show how the tools interact in the work process

Stating critical requirements and precautions

Enterprise Work Processes and Integration Capability Statements can be customized and enhanced by your organization to create best practices that combine project expertise and software capabilities.

How to Use this Document The Enterprise Work Processes contain diagrams organized into two levels.

The Level 1 diagrams represent the typical work process based on organization roles (disciplines), with a focus on the deliverables produced by that discipline and how that discipline interacts with other disciplines and external entities, such as vendors. At this level, no specific tools are involved.

The Level 2 diagrams represent the sequence of major tasks performed using Hexagon PPM solutions, and other tools, to produce each deliverable for that discipline. While there are multiple ways to produce a deliverable, the work processes described in this document represent typical paths using Hexagon PPM solutions (out-of-the box, or with minimum configuration) and do not include system customizations that could further enhance the work processes.

Reading diagrams and user stories

In some Level 1 and Level 2 diagrams, some steps have a black shadow which indicates the step is described in more detail in a separate work process diagram in this document. In some cases, a series of steps in a Level 1 diagram are grouped together in a larger box to represent a subprocess that is described in more detail in another Level 1 or Level 2 diagram.

Because Level 1 diagrams represent disciplines or roles, they are represented using same color swim lanes. However, in Level 2 diagrams, Hexagon PPM tools are represented by specific colors and non-Hexagon PPM tools are represented in gray.

The swim lane diagrams should be read in conjunction with the user stories that follow each diagram for better understanding. Numbers in the diagram boxes correspond to the numbered steps in the user story. If a step has a red flag, this indicates supporting information in an Integration Capability Statement, which is referenced at the bottom of the diagram, in the user story, and in the Appendix.

Most engineering work processes are not sequential, but instead are parallel and iterative. The numbers in the process steps do not necessarily indicate the strict order in which tasks must be accomplished. Although there is a general time sequence of process steps from left to right on the diagrams, the sequence does not represent a strict timeline.

To view large diagrams on screen, you can use the Pan & Zoom feature in Adobe Acrobat by selecting View > Zoom > Pan & Zoom.

Printing the document For best results, EWP documents must be printed using the landscape orientation to a printer that supports 11 in x 17 in (US tabloid) or A3 (297mm x 420 mm).



Contents Process Design is divided into several Level 1 diagrams representing typical industry work processes by project phase (FEED, Basic Engineering, and Detailed Design) and several Level 2 diagrams representing the development of Process deliverables by project phase.

Process Design is comprised of a total of five swim lane diagrams.

Swim lane diagrams Process Design Work Process – FEED

Develop P&IDs (Rev 0 and 1)

Process Design Work Process – Basic Engineering

Develop P&IDs (Rev 2 - IFC)

Process Design Work Process – Detailed Design

Develop P&IDs (Rev 2 - IFC)

Check Data Consistency - Instrumentation

Check Data Consistency - Equipment

Check Data Consistency - Piperuns

Validate Engineering Integrity

In addition, the following Integration Capability Statements are referenced in the diagrams, with a red flag and the number listed below, to provide more information on specific integration work processes:

2 P&ID Guided 3D Design and Consistency Checking

4 Checking Instrument Consistency Between P&IDs and Instrumentation

7 Defining Electrical Consumers from P&IDs

11 Creating Line List in SmartPlant Foundation

13 Sharing process and equipment data between PFDs and P&IDs

The work process diagram for each of these Integration Capability Statements is referenced in the Appendix. The full set of available Integration Capability Statements and Enterprise Work Process guides is on the support page under View Documentation > Work Process Guides. Access the support site for the most up-to-date information about all work process guides. To access the support site, browse to the following site, https://smartsupport.intergraph.com, and type your user name and password.

Hexagon PPM 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.

Notes about this Work Process Assumptions The name Process is used to refer to a single department that provides all of the deliverables assigned to it in this document.

The processes described are based on a single site EPC project execution model at any design stage, in other words, not a joint venture model.

FEED work is being done by one engineering company and, potentially, handed over for basic and detailed design to another engineering company. However, the work processes described also apply when the same EPC executes all three design phases.

General Notes SmartPlant P&ID drawings can now include ducting (HVAC) objects, giving users the ability to create D&IDs. Although the drawings containing ducting objects can be published to SmartPlant Foundation and retrieved into Smart 3D, and the ducting

objects themselves are published from SmartPlant P&ID to SmartPlant Foundation, these ducting objects cannot yet be retrieved into Smart 3D. Retrieval and correlation of ducting objects is planned for future versions.



In the Level 1 diagrams, some process steps are shown without any stated input, such as Run Calculations, because these steps take place outside any PPM software.

SmartPlant Foundation workflows can be used to help automate components of the load process. The following are general notes about the use of workflows when publishing:

The diagrams and user stories in this document assume that the PPM tools are publishing documents using the AutoLoadPublish or Auto-Correlate workflow, delivered out-of-the-box with SmartPlant Foundation, which automatically loads the published document and any published data into the SmartPlant Foundation database. Without using this, or another workflow designed to perform this operation, the document information will be created in the database, but the published data will not be loaded automatically. The process of loading the data into the database will need to be initiated manually. Downstream tools can retrieve data that has not been loaded into the SmartPlant Foundation database, but Data Consistency Checks on that data will not be possible.

Using the Auto-Correlate workflow when publishing documents allows you to perform data consistency checks on published data without retrieving into another PPM tool, as illustrated in the Data Consistency Check diagrams later in this document. Auto-Correlate loads the published document and data into the SmartPlant Foundation database, compares the object data from different sources, and automatically correlates representations of the same object from different tools.

Using custom workflows, publish can be configured to send an email notification. The workflow can send an email to a list of recipients, by document type if desired.

Workflows can be defined for use across an entire site for all publishes automatically, or they can be selected at the time of publish.

Publish and Retrieve Recommendations In a SmartPlant integrated environment, publishing a document is different from issuing a document. Use publishing to share data between engineering disciplines, prior to completing the design and issuing the document. A question that is often raised is When should I publish or retrieve a document?

You should publish documents (P&IDs, the instrument index, the 3D model, and more) at the same time as each official issue milestone, but do not limit publishing only to these official issue times.

One of the benefits of publishing documents, even when they are not retrieved into other applications, is that data for objects that exist in multiple applications, including equipment, instruments, and pipe runs, can be checked in SmartPlant Foundation for consistency across these applications. However, the primary benefit of publishing documents from one application is the ability to retrieve these documents into a downstream application. Users of the downstream applications then review and use the new or updated data as needed to continue or update their design and deliverables. You do not need to publish all documents, for instance all P&IDs, at the same time; you can publish the documents from one Unit only, publish one document, or publish a specific set of documents.

Below are some general timing recommendations for publishing and retrieving documents.

1. In the early phases of design, when data is very preliminary, publishing and retrieving should be infrequent and can be based on communication between the discipline leads to determine the appropriate times. After the documents have reached the Issue for Design stage, publishing and retrieving should become more frequent, even on a pre-determined time schedule, according to the pace of design changes, such as every week or every two weeks. In this way, downstream applications can make use of data updates on a regular basis.

2. You should publish data that has passed some level of quality check. This quality check involves two separate items:

a. If the catalog or reference data has recently been updated, you should ensure that the design data has been synchronized with the updated catalog or reference data prior to publishing.

b. When the work process involves a checker verifying the work done by a designer, publishing should be done after the checker has verified the design.

There are specific situations when you may not want to wait as long as one or two weeks, as discussed in the following points. The project should discuss which major changes can have a high impact on the schedule or project costs and, therefore, are candidates for triggering a new publishing operation. Designers should notify their lead person regarding potential impacts to the publish schedule. The lead person will make the decision to publish or not when such a situation occurs. Some suggested guidelines are given below.

1. Additions, deletions, and major updates to equipment data should be published as soon as they can be approved because they are critical to downstream disciplines.

2. Instrument dimensions (DDP) should be published as soon as they are available from SmartPlant Instrumentation so that the piping designer can model accurate instruments in Intergraph Smart™ 3D.

3. The deletion of tags (equipment, instruments, and so on) that have been published previously should result in the re-publishing of the documents where they existed as soon as possible.

4. In general, disciplines that create documents that are heavily relied upon by downstream disciplines, such as Process and their P&IDs, should consider the impact of their changes to downstream applications and make an additional unscheduled publish as a result of significant changes.

5. If a document is undergoing major revisions that are not completed in time for a scheduled publish, the publishing of that document should be delayed until the revisions are completed to prevent unnecessary changes in the downstream applications.

6. As you approach the Issue for Construction milestone, you should consider increasing the frequency of the publish and retrieve operations to incorporate all types of modifications as soon as possible and ensure the project stays on schedule.

The following are some general notes about publishing and retrieving documents:

When an object is published in documents coming from multiple tools, the data coming from the various tools can be checked for consistency in SmartPlant Foundation. The opportunity to check this data is represented in the Level 2 diagrams with a Check Data Consistency (subprocess) step. Data for specific objects, such as equipment and instruments, can be compared in SmartPlant Foundation as soon as the data is published from multiple tools’ documents (such as a P&ID and the instrument index). A separate set of Check Data Consistency (subprocess) diagrams that illustrate this process can be found at the end of this document. Data of a few objects, such as pipe runs, can only be compared after the object has been published by one tool (such as SmartPlant P&ID) and then retrieved and published by a second tool (such as Smart 3D).

The PublishForLoadOnly workflow allows you to publish a document and 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. Also, you can configure custom workflows (such as for review and approvals) that control when documents can be retrieved by setting its SPFTEFIsRetrievable property.



Before publishing any document, a new revision can be obtained from SmartPlant Foundation, if required. If a new revision is not required, publish the document or documents.

Documents can be published to any owning group available in SmartPlant Foundation. To retrieve a document published with an owning group, a user must have permissions configured in SmartPlant Foundation to allow them to retrieve documents in that owning group.



Process Design Work Process - FEED - Level 1 Diagram



Process Design Work Process - FEED - Level 1 1. As a process engineer, I need to determine the detailed stream analysis and case studies, using input from licensor technology and client input on engineering standards and guidelines, production requirements, site requirements, and local standards,

so that I can define the process release for use by the project.

2. As a process engineer, I need to define the steam balance so that I can adequately determine the steam load needed for the plant’s equipment and distribution network.

3. As a process engineer, I need to develop the process data sheets and equipment data sheets so that I can convey liquid hold up times, nozzle inputs not shown on PFDs, and other data not shown in the process release.

4. As a process engineer, I need to define the heat and mass balance for each major piece of equipment so that I can size equipment, pipelines, heat tracing, and so forth. This task is typically done using process simulation.

5. As a process engineer, I need to develop PFDs and BFDs (block flow diagrams for utilities, tank farms, auxiliary systems, and so forth) so that I can provide graphical awareness of the plant configuration, and so that Instrumentation can start defining the initial control strategy, Piping can start the 3D modeling, and the project team can identify long lead equipment items.

6. As a process engineer, I need to run calculations so that I can include line sizing, pressure safety valves, pump differentials, and so forth, as I develop the P&IDs.

7. As a process engineer, I need to develop P&IDs (Rev 0 and 1) so that I can provide the schematic awareness of piping and instrumentation for the physical design of the plant. See the work process Develop P&IDs (Rev 0 and 1) - FEED - Level 2 Diagram (on page 11) for more information.

Inputs:

Heat and mass balance

Steam balance

PFDs and BFDs

Equipment list

Equipment data sheets

Process data sheets

Instrument index

Consumers:

Instrumentation for updating the instrument index

Process for developing the line list, data sheets, and equipment list

Piping to develop the 3D model

Project Controls to update the cost estimates

Electrical for power requirements

8. As a process engineer, I need to develop the line list so that I can convey detailed pipe and fluid information not shown on the P&ID.

9. As a process engineer, I need to create early MTOs so that I can give necessary estimates to the project controls department.



Develop P&IDs (Rev 0 and 1) - FEED - Level 2 Diagram



Develop P&IDs (Rev 0 and 1) - FEED - Level 2 1. As a licensor, I need to provide the process technology to the client as purchased, so that the process release can be developed.

2. As the client, I need to provide engineering standards and guidelines, production requirements, site requirements, and local standards so that the engineering contractor understands the scope of the project.

3. As a process engineer, I need to perform a series of process simulations so that I can determine the optimum operating conditions for the plant.

4. As a process engineer, I need to determine the detailed stream analysis and case studies, using input from licensor technology and client input on engineering standards and guidelines, production requirements, site requirements, and local standards, so that I can define the process release for use by the project.

5. As a process engineer, I need to define the heat and mass balance for each major piece of equipment so that I can size equipment, pipelines, heat tracing, and so forth.


7. As a mechanical engineer, I need to develop the equipment data sheets so that I can provide basic equipment information to develop the P&IDs.

8. As a mechanical engineer using Aspen Basic Engineering, I need to develop the equipment list so that I can provide basic equipment information to develop the P&IDs.

9. As an Aspen Basic Engineering user, I need to publish the equipment list so that I can share this data with other applications.

10. As a process engineer using Aspen Basic Engineering, I need to develop PFDs and BFDs (utilities, tank farms, auxiliary systems, and so forth) so that I can convey the general process flow of the plant to other disciplines.

11. As an Aspen Basic Engineering user, I need to publish the PFDs and BFDs (utilities, tank farms, auxiliary systems, and so forth) so that I can share this data with other applications.

12. As a process engineer using Aspen Basic Engineering, I need to develop the process equipment data sheets so that I can convey liquid hold up times, nozzle inputs not shown on PFDs, and other data not shown in the process release.

13. As an Aspen Basic Engineering user, I need to publish the process data sheets and the equipment data sheets so that I can share that information with other applications.

14. As an instrument engineer, I need to start developing the instrumentation for the plant.

15. As an instrument engineer, I need to publish the instrument index so that the Process department can update the P&IDs.

16. If the document has publishable data, the document and data are loaded into SmartPlant Foundation and are subsequently available for use by other applications. If the document does not have publishable data, it is available for viewing in SmartPlant Foundation.

17. After documents with data are published and loaded in the SmartPlant Foundation data warehouse, it is possible to check the consistency of data coming from various tools for the objects published in that document, such as instruments, equipment, or pipe runs. See the applicable subprocess.

18. As a member of the Process department, I need to retrieve the PFDs, equipment list, and process and equipment data sheets.

See the following Integration Capability Statements for more information:

Checking Instrument Consistency Between P&IDs and Instrumentation

Sharing Data Between PFDs and P&IDs

19. As a process engineer, I need to run calculations so that I can update line sizing, pressure safety valves, pump differentials, and other items as I continue to develop the P&IDs.

20. As a member of the Process department, I need to develop P&IDs (Rev 0) so that I can convey the updated status of the plant to other disciplines and update the line list.

21. As a member of the Process department, I may validate the integrity of the P&IDs by checking their contents against the project standards. For more information, see the Validate Engineering Integrity - Diagram (on page 34).

22. As a member of the Process department, I need to publish the P&IDs so that the information can be shared with other disciplines.



25. As a member of the Process department, I need to retrieve the P&IDs so that I can develop the line list (Rev 0).

See the following Integration Capability Statement for more information:

Creating Line Lists in SmartPlant Foundation

26. As a process engineer, I need to develop the line list so that I can convey detailed pipe and fluid information not shown on the P&IDs.

27. As a member of the Process department, I need to publish the line list so that the information can be shared with other disciplines.



28. As an instrument engineer, I need to retrieve the P&IDs so that I can update the instrumentation information.

29. As an instrument engineer, I need to use the information supplied by the P&IDs to further develop the instrumentation.


31. As an electrical engineer, I need to retrieve the P&IDs so that I can create or update electrical consumers and design the electrical network of the plant.


Defining Electrical Consumers from P&IDs

32. As an electrical engineer, I need to design the electrical distribution so that I can create or update the electrical load list.

33. As an electrical engineer, I need to update the electrical load list so that I can size the required power supply and the electrical equipment properly.

34. As a member of the project team using Smart 3D, I need to retrieve the P&IDs so that I can start the FEED 3D model.

35. As a member of the project team using Smart 3D, I need to use the information supplied by the P&IDs to create a series of physical arrangements of equipment and facilities for plant optimization and cost estimation.

36. As a process engineer, I need to perform a series of process simulations so that I can determine the optimum operating conditions for the plant.

37. As a process engineer, I need to define the heat and mass balance for each major piece of equipment so that I can size equipment, pipelines, heat tracing, and so forth.


39. As a mechanical engineer, I need to develop the equipment data sheets so that I can provide basic equipment information to develop the P&IDs.

40. As a mechanical engineer using Aspen Basic Engineering, I need to retrieve the P&IDs so that I can continue developing equipment lists and the PFDs and BFDs.



41. As a mechanical engineer using Aspen Basic Engineering, I need to develop the equipment list so that I can provide basic equipment information to develop the P&IDs.

42. As an Aspen Basic Engineering user, I need to publish the equipment list so that it is available for use by other applications.

43. As a process engineer using Aspen Basic Engineering, I need to develop PFDs and BFDs (utilities, tank farms, auxiliary systems, and so forth) so that I can convey the general process flow of the plant to other disciplines.

44. As an Aspen Basic Engineering user, I need to publish the PFDs and BFDs (utilities, tank farms, auxiliary systems, and so forth) so that they are available for use by other applications.

45. As a process engineer using Aspen Basic Engineering, I need to develop the process equipment data sheets so that I can convey liquid hold up times, nozzle inputs not shown on PFDs, and other data not shown in the process release.

46. As an Aspen Basic Engineering user, I need to publish the process data sheets and equipment data sheets so that they are available for use by other applications.



49. As a member of the Process department, I need to retrieve the instrument index and the documents from Aspen Basic Engineering: PFDs, equipment list, and process and equipment data sheets.

See the following Integration Capability Statements for more information:




51. As a member of the Process department, I need to develop P&IDs (Rev 1) so that I can convey the updated status of the plant to other disciplines and update the line list.

52. As a member of the Process department, I need to generate early MTOs so that Project Controls can create a cost estimate, and long-lead items can be procured

53. As a member of the Procurement department, I need to import early MTO reports from the P&IDs so that long-lead items can be procured

54. As a member of the Procurement department, I need to procure long lead items so that they can be available when needed in the field for construction.

55. As a member of the Process department, I need to publish the early MTOs. These reports are published as viewable documents only.




57. As a member of the Process department, I need to publish the P&IDs so that the information can be shared with other disciplines.



60. As a member of the Process department, I need to retrieve the P&IDs so that I can develop the line list (Rev 1).



61. As a process engineer, I need to develop the line list so that I can convey detailed pipe and fluid information not shown on the P&IDs.

62. As a member of the Process department, I need to publish the line list so that the information can be shared with other disciplines.






68. As an electrical engineer, I need to retrieve the P&IDs, so that I can create or update electrical consumers and design the electrical network of the plant.



69. As an electrical engineer, I need to design the electrical distribution so that I can create or update the electrical load list.


71. As a member of the project team using Smart 3D, I need to retrieve the P&IDs so that I can develop the FEED 3D model.

72. As a member of the project team using Smart 3D, I need to use the information supplied by the P&IDs to create a series of physical arrangements of equipment and facilities for plant optimization and cost estimation.

73. As a member of the project controls department, I need to review the MTO reports so that I can provide updated cost estimates.

74. As a member of the project controls department, I need to review the P&IDs so that I can provide updated cost estimates.

75. As a member of the project controls department, I need to update the cost estimates based on the MTO reports and P&IDs.



Process Design Work Process - Basic Engineering - Level 1 Diagram



Process Design Work Process - Basic Engineering - Level 1 1. As a process engineer, I need to update the steam balance so that I can adequately determine the steam load needed for the plant’s equipment and distribution network.

2. As a process engineer, I need to run calculations so that I can include line sizing, pressure safety valves, pump differentials, and other items as I continue to develop the P&IDs.

3. As a process engineer, I need to create hydraulic process data sheets so that I can give the information to Instrumentation so that they can size instruments.

4. As a process engineer, I need to develop P&IDs (Rev 2) so that I can convey the updated status of the plant with information added since P&IDs (Rev 1), including, but not limited to, calculations such as line sizing, pressure safety valves, pump differential, hydraulic analysis, and so forth. See the work process Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 Diagram (on page 18) for more information.

Inputs

Instrument information

Pipe specification from the Piping and Materials groups to validate the components on the P&ID

Vendor P&IDs

Equipment list


Line list

Consumers:

Instrumentation for updating the instrument information

Project controls to update the cost estimates

Electrical to update the load list

Piping to update the 3D model

Process for updating the line list, the equipment data sheets, and the equipment list

Project controls for cost estimating

5. As a process engineer, I need to continue developing the line lists so that I can convey detailed pipe and fluid information not shown on the P&IDs.

6. As a process engineer, I need to create early MTOs so that I can give necessary estimates to the project controls department.

7. As a process engineer, I need to update the steam balance so that I can adequately determine the steam load needed for the plant’s equipment and distribution network.

8. As a process engineer, I need to run calculations so that I can include line sizing, pressure safety valves, pump differentials, and other items as I continue to develop the P&IDs.

9. As a process engineer, I need to update the hydraulic process data sheets so that I can give the information to Instrumentation to update instruments.

10. As a process engineer, I need to develop P&IDs (Rev 3) so that I can convey the updated status of the plant with information added since P&IDs (Rev 2), including, but not limited to, calculations such as line sizing, pressure safety valves, pump differentials, hydraulic analysis, and so forth.

Inputs:

Equipment list

Equipment data sheet

Steam balance

Calculations

Hydraulic process data sheets

Updated vendor P&IDs

Line list

Instrument index

3D Model



Consumers (Some consumers listed below are shown in the next diagram - Detail Design Level 1):

Project controls to update the cost estimates

Process for developing the line list, the equipment data sheets, and the equipment list


Electrical to update the electrical consumers


Safety for safety studies, including HAZOP



Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 Diagram



Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 1. As a mechanical engineer, I need to update the equipment data sheets so that I can provide the project information to develop P&IDs.

2. As a solution vendor (package, skid, or technology), I need to provide P&IDs so that they can be included in the project P&IDs.

3. As a mechanical engineer using Aspen Basic Engineering, I need to develop the equipment list so that I can provide the project information to develop P&IDs.



4. As a mechanical engineer using Aspen Basic Engineering, I need to develop the equipment data sheets so that I can provide the project information to develop P&IDs.

5. As an Aspen Basic Engineering user, I need to publish the equipment list or equipment data sheets so that they are available for use in other applications.

6. As a process engineer using SmartPlant Foundation Authoring, I need to develop the line list (Rev 2) so that I can convey detailed pipe and fluid information not shown on the P&ID.



7. As a SmartPlant Foundation user, I need to publish the line list (Rev 2) so that the information can be shared with other disciplines.







12. As a member of the Process department, I need to retrieve the equipment list, equipment data sheets, and the instrument index.


14. As a member of the Process department, I need to continue developing P&IDs (Rev 2) so that I can convey the updated status of the plant to other disciplines and update the line list.


16. As a member of the Process department, I need to generate MTO reports for procurement and so that project controls can do cost estimating.

17. As a member of the Process department, I need to publish the MTO reports so that the information can be made available to other disciplines. These reports are published as viewable documents only.

18. As a member of the Process department, I need to publish the P&IDs so that the information is available to other disciplines.



21. As a process engineer, I need to retrieve the P&IDs so that I can update the line list.




23. As a SmartPlant Foundation user, I need to publish the line list so that the information can be shared with other disciplines.












29. As an electrical engineer, I need to design the electrical network.

30. As a member of the Piping department, I need to retrieve the P&IDs so that I can update the 3D model.


P&ID Guided 3D Design and Consistency Checking

31. As a member of the Piping department, I need to use the information supplied by the P&IDs to update the 3D model.

32. As a member of the project controls department, I need to review the MTO reports so that I can provide updated cost estimates. Note: In addition, if the 3D model is not sufficiently developed at this point, the MTO reports can also be imported in Smart Materials in order to procure material, as was done in the FEED stage for long lead items. This may be done for multiple revisions of the P&IDs, until the 3D model has reached some level of maturity.



35. As a mechanical engineer, I need to update the equipment data sheets so that I can provide the project information to develop P&IDs.


37. As a mechanical engineer using Aspen Basic Engineering, I need to retrieve the P&IDs so that I can update the equipment list and equipment data sheets.

38. As a mechanical engineer using Aspen Basic Engineering, I need to update the equipment list so that I can provide the project information to develop P&IDs.








44. As a process engineer, I need to run calculations so that I can update line sizing, pressure safety valves, pump differential calculations, and other items as I continue to develop the P&IDs.

45. As a member of the Process department, I need to continue developing P&IDs (Rev 3) so that I can convey the updated status of the plant to other disciplines, perform safety studies, and update the line list.
































65. As an Aspen Basic Engineering User, I need to publish the equipment list or equipment data sheets so that they are available for use in other applications.













76. As a process engineer using SmartPlant Foundation Authoring, I need to develop the line list (Rev IFC) so that I can convey detailed pipe and fluid information not shown on the P&ID.
















86. As a member of the Process department, I need to continue developing P&IDs (Rev IFC) so that I can convey the updated status of the plant to other disciplines, perform safety studies, update the line list, and issue the P&IDs.

87. As a member of the Process department, I need to publish the P&IDs so that the information is available to all.




Process Design Work Process - Detailed Design - Level 1 Diagram



Process Design Work Process - Detailed Design - Level 1 1. As a process engineer, I need to continue developing P&IDs (Rev 3) so that I can convey the updated status of the plant to other disciplines, update the line list, and perform a safety study. See the work process Develop P&IDs (Rev 2 - IFC) - Basic

Engineering and Detailed Design - Level 2 Diagram (on page 18) for more information. See the last step in the previous diagram – Basic Engineering Level 1 – for a list of inputs and consumers.

2. As a process engineer, I need to continue developing the line list so that I can convey detailed pipe and fluid information not shown on the P&IDs.


4. As a process engineer, I need to continue developing P&IDs (Rev 4) so that I can convey the updated status of the plant to other disciplines and update the line list. See the work process Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 Diagram (on page 18) for more information.

Inputs:

Calculations

Equipment list


Line list

Instrument index

3D Model

Results of the safety studies, including HAZOP

Consumers:


Process for updating the line list

Piping to develop the 3D model

5. As a process engineer, I need to continue developing the line list so that I can convey detailed pipe and fluid information not shown on the P&IDs.


7. As a process engineer, I need to finish developing P&IDs (Rev IFC) so that I can convey the updated status of the plant to other disciplines, update the line list document, and then issue the P&IDs. See the work process Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 Diagram (on page 18) for more information.

Inputs:

Calculations

Line list

Instrument index

3D Model

Consumers:


Process for updating and issuing the line list

Construction


8. As a process engineer, I need to finish developing the line list so that it can be issued for construction.



Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 Diagram



Develop P&IDs (Rev 2 - IFC) - Basic Engineering and Detailed Design - Level 2 1. As a mechanical engineer, I need to update the equipment data sheets so that I can provide the project information to develop P&IDs.


3. As a mechanical engineer using Aspen Basic Engineering, I need to develop the equipment list so that I can provide the project information to develop P&IDs.








7. As a SmartPlant Foundation user, I need to publish the line list (Rev 2) so that the information can be shared with other disciplines.









14. As a member of the Process department, I need to continue developing P&IDs (Rev 2) so that I can convey the updated status of the plant to other disciplines and update the line list.


16. As a member of the Process department, I need to generate MTO reports for procurement and so that project controls can do cost estimating.

17. As a member of the Process department, I need to publish the MTO reports so that the information can be made available to other disciplines. These reports are published as viewable documents only.

























32. As a member of the project controls department, I need to review the MTO reports so that I can provide updated cost estimates. Note: In addition, if the 3D model is not sufficiently developed at this point, the MTO reports can also be imported in Smart Materials in order to procure material, as was done in the FEED stage for long lead items. This may be done for multiple revisions of the P&IDs, until the 3D model has reached some level of maturity.















































65. As an Aspen Basic Engineering User, I need to publish the equipment list or equipment data sheets so that they are available for use in other applications.













76. As a process engineer using SmartPlant Foundation Authoring, I need to develop the line list (Rev IFC) so that I can convey detailed pipe and fluid information not shown on the P&ID.
















86. As a member of the Process department, I need to continue developing P&IDs (Rev IFC) so that I can convey the updated status of the plant to other disciplines, perform safety studies, update the line list, and issue the P&IDs.

87. As a member of the Process department, I need to publish the P&IDs so that the information is available to all.




Appendix

Subprocess Diagrams 1. Check Data Consistency - Instrumentation

2. Check Data Consistency - Equipment

3. Check Data Consistency - Piperuns

4. Validate Engineering Integrity

Integration Capability Statements The first page of each referenced Integration Capability Statement, showing the work process diagram, is included in the following pages.

2 P&ID Guided 3D Design and Consistency Checking

4 Checking Instrument Consistency Between P&IDs and Instrumentation

7 Defining Electrical Consumers from P&IDs

11 Creating Line List in SmartPlant Foundation

13 Sharing process and equipment data between PFDs and P&IDs

The complete set of Integration Capability Statements can be found on the support site at https://smartsupport.intergraph.com under View Documentation > Work Process Guides. You must have an account to access this page.



Check Data Consistency - Instrumentation



Check Data Consistency - Equipment



Check Data Consistency - Piperuns



Validate Engineering Integrity - Diagram



Validate Engineering Integrity 1. As a standards organization, we define and provide engineering best practices and standards, sometimes by industry, so that facilities are designed with sound engineering practices for safe and efficient operation.

2. As an engineering company, we define our EPC corporate design standards to be used in our projects, based on our own experience and best industry practices, so that they can be executed as efficiently and safely as possible.

3. As an administrator of SmartPlant Engineering Integrity for the EPC, I need to create the library of rules based on the corporate and industry standards so that they can be used in projects.

4. As an owner company, we define our standards to be used during the design and operation of our facilities, based on our own experience and best industry practices.

5. As an administrator of SmartPlant Engineering Integrity for the owner, I need to create the library of rules based on the corporate and industry standards so that they can be used in projects.

6. As an administrator of SmartPlant Engineering Integrity for the owner, I need to select the rules that apply to this particular project so that I can use them internally and also send them to the EPC to use during the project. I may also receive and import some rules from the EPC.

7. As an administrator of SmartPlant Engineering Integrity for the EPC, I need to select from our corporate library of rules for use in the project and also import the rules supplied by the owner, if applicable, so that they can be used on this specific project.

8. As a user of SmartPlant P&ID, SmartPlant Instrumentation, or SmartPlant Electrical for the EPC, I need to develop the engineering design for the project.

9. As a user of SmartPlant Engineering Integrity for the EPC, I need to identify the subset of rules that need to be used, based on the current design phase of the project, so that the engineering design can be checked against them. For instance, I may select a small subset of rules during the FEED stage and the complete set of rules during Detailed Design.

10. As a user of SmartPlant Engineering Integrity for the owner, I need to identify the subset of rules that need to be used, based on the current design phase of the project, so that the engineering design can be checked against them. For instance, I may select a small subset of rules during the FEED stage and the complete set of rules during Detailed Design.

11. As a user of SmartPlant Engineering Integrity for the EPC, I need to import the engineering design data into my environment so that I can validate it against the rules.

12. As a user of SmartPlant Engineering Integrity for the EPC, I need to run the rules against a set of the engineering design data so that the design complies with the standards. It is possible that some rules will need adjustments based on new configurations, project requirements, or revised standards.

13. <decision point> As a user of SmartPlant Engineering Integrity for the EPC, I need to determine if the design data complies with the project rules.

14. <decision point> As an engineer, I need to determine if the non-compliance found is acceptable to the project.

15. As a user of SmartPlant P&ID, SmartPlant Instrumentation, or SmartPlant Electrical, I need to correct the P&ID so that it complies with the project standards and the rules can be re-run against it.

16. As a process engineer, I need to issue the P&IDs to the owner so that they can be reviewed.

17. As a user of SmartPlant P&ID Engineering Integrity for the owner, I need to run the rules against a set of P&IDs received from the engineering company so that I can check if the design complies with the standards. It is possible that some rules will need adjustments based on new P&ID configurations, project requirements, or revised standards.

18. <decision point> As a user of SmartPlant P&ID Engineering Integrity for the owner, I need to determine if the design data complies with the project rules.

19. As an owner company, we approve the design data.



Sharing Data between PFDs and P&IDs



Revision History

Version Date Change

1.0 2/13/12 Changes to the Check Data Consistency – Pipelines/Piperuns and miscellaneous updates

1.1 4/16/12 Added SmartPlant Materials

1.2 6/1/12 Minor updates

1.3 5/8/13 Reorganized diagram order.

1.4 7/16/13 Added information about using PublishForLoadOnly workflow to compare data and restrict a document from being retrieved by other tools and publishing and retrieving using owning groups.

1.5 9/23/13 Revised the Load Documents and Data step. Removed equipment list and equipment datasheets from SPF-Authoring.

1.6 2/12/14 Replaced references to eCustomer with references to Intergraph Smart Support. Added a Table of Contents to improve navigation in the document.

1.7 6/19/14 Added a General Note about new HVAC (ducting) objects not yet being publishable.

Added new Validate P&ID Integrity steps in both Develop P&IDs level 2 diagrams and the corresponding work process using SmartPlant P&ID Engineering Integrity in the Appendix.

1.8 11/13/15 Replaced SmartPlant Layout with Smart 3D.

2.0 3/15/17 Removed SmartPlant Safety and Safety swimlanes from the Develop P&IDs diagrams. Updated the name of the SmartPlant Engineering Integrity product, which now works with SmartPlant P&ID, SmartPlant Instrumentation, and SmartPlant Electrical. Updated the general note about the publish and retrieval of ducting (HVAC) objects.