Enterprise Work Process for Construction Work Package Planning

SmartPlant® Enterprise Enterprise Work Process for Construction Work Package Planning Version 2.0 January 2017

Hexagon PPM Proprietary Information 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; 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 H exagon AB and/or its subsidiaries and affiliates.

U.S. Government Government Restrict ed 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 copyrigh copyrightt laws of t he United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 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 vered 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 t he terms contained within the applicable license agreement, 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. 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 license to use the D ocumentation or Other Documentation for Licensee’s Licensee’s internal non-commercial non-commercial use. Intergraph Corporation gives Licensee permission to print a reasonable number of copies of Other Documentation for Licensee’s internal, non-commercial 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 disclaim ms s 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 t o 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 furnished under a license and may be used or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE I S 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 COR PORATION BE LIABLE FOR ANY DIRECT, INDI RECT, CONSEQUENTIAL INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INC LUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF REVENUE OR PROFIT, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF IN TERGRAPH 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 WI TH THE SUBJECT MATTER OF THIS DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2) YEARS AFTER THE EVENT GIVING RISE TO T HE CAUSE OF ACTION HAS OCCURRED. IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, T HEN INTERGRAPH LIMITS ITS LIABILITY TO THE MAXIMUM EXTENT ALLOWED BY SAID LAW.

Export Controls Intergraph Corporation’s commercial-off-the-shelf 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. D iversion 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 (including via remote access) under the following circumstances: a.

To Cuba, Iran, North Korea, the Crimean Crimean region of Ukraine, Ukraine, or Syria, or any national of these countries countries or territories. territories.

b.

To any person or entity listed on any U nited States government denial list, including, including, but not limited to, t he 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 DebarredList (https://build.export.gov/main/ecr/eg_ (https://build.export.gov/main/ecr/eg_main_02314 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, 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 Customer knows, or has reason to know, that an illegal illegal reshipment will take take place.

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

Enterprise Work Process for Construction Work Package Planning

2

Hexagon PPM Proprietary Information 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; 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 H exagon AB and/or its subsidiaries and affiliates.

U.S. Government Government Restrict ed 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 copyrigh copyrightt laws of t he United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 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 vered 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 t he terms contained within the applicable license agreement, 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. 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 license to use the D ocumentation or Other Documentation for Licensee’s Licensee’s internal non-commercial non-commercial use. Intergraph Corporation gives Licensee permission to print a reasonable number of copies of Other Documentation for Licensee’s internal, non-commercial 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 disclaim ms s 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 t o 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 furnished under a license and may be used or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE I S 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 COR PORATION BE LIABLE FOR ANY DIRECT, INDI RECT, CONSEQUENTIAL INCIDENTAL, SPECIAL, OR PUNITIVE DAMAGES, INC LUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF REVENUE OR PROFIT, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF IN TERGRAPH 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 WI TH THE SUBJECT MATTER OF THIS DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2) YEARS AFTER THE EVENT GIVING RISE TO T HE CAUSE OF ACTION HAS OCCURRED. IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, T HEN INTERGRAPH LIMITS ITS LIABILITY TO THE MAXIMUM EXTENT ALLOWED BY SAID LAW.

Export Controls Intergraph Corporation’s commercial-off-the-shelf 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. D iversion 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 (including via remote access) under the following circumstances: a.

To Cuba, Iran, North Korea, the Crimean Crimean region of Ukraine, Ukraine, or Syria, or any national of these countries countries or territories. territories.

b.

To any person or entity listed on any U nited States government denial list, including, including, but not limited to, t he 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 DebarredList (https://build.export.gov/main/ecr/eg_ (https://build.export.gov/main/ecr/eg_main_02314 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, 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 Customer knows, or has reason to know, that an illegal illegal reshipment will take take place.

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


2

Hexagon PPM Proprietary Information Intergraph®, the Intergraph logo ®, Intergraph Smart ®, SmartPlant ®, SmartMarine, SmartSketch ®, SmartPlant Cloud ®, PDS®, FrameWorks ®, I-Route, I-Export, ISOGEN ®, SPOOLGEN, SupportManager 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.


3

Table of Contents Work Process for Constru cti on Work Package Planni ng .................................... ...................................... ..................................... ...................................... ..................................... ...................................... ..................................... ...................................... . 5 Introduction .................................................................................................................................................................................................................................................................................................................................................................................. 5 How to Use this Document .......................................................................................................................................................................................................................................................................................................................................................... 5 Contents ...................................................................................................................................................................................................................................................................................................................................................................................... 6 Notes about this Work Process ................................................................................................................................................................................................................................................................................................................................................... 6 Hand over Considerations .................................................................................................................................................................................................................................................................................................................................................... 6 Construction - Work Package Planning - Level 1 Diagram ................................. ...................................... ..................................... ...................................... ..................................... ...................................... ...................................... ..................................... . 8 Construction - Work Package Planning - Level 1.................................... ..................................... ...................................... ...................................... ..................................... ...................................... ..................................... ...................................... ............. 9 Construction - Define Construction Strategy - Project Configuration - Level 2 Diagram..................................... ...................................... ..................................... ...................................... ..................................... ...................................... ................... 10 Construction - Define Construction Strategy - Project Configuration - Level 2 ................................ ...................................... ...................................... ..................................... ...................................... ..................................... ...................................... 11 Construction - Define and Develop Installation Work Packages (IWPs) - Level 2 Diagram ........................................... ...................................... ...................................... ..................................... ...................................... ..................................... ....... 12 Construction - Define and Develop Installation Work Packages (IWPs) - Level 2 .................................. ..................................... ...................................... ..................................... ...................................... ..................................... ................................ 13 Construction - Determine the Installation Work Package (IWP) Constructability - Level 2 Diagram ................................................................................................................................................................................................................................. 14 Construction - Determine the Installation Work Package (IWP) Constructability - Level 2 ................................. ..................................... ...................................... ...................................... ..................................... ...................................... ................... 15 Construction - Issue Installation Work Package (IWP) and Monitor Progress - Level 2 Diagram ...................................................................................................................................................................................................................................... 16 Construction - Issue Installation Work Package (IWP) and Monitor Progress - Level 2 ..................................... ..................................... ...................................... ...................................... ..................................... ...................................... ................... 17 Scenario 1 – Hand over to Construction ............................................................................................................................................................................................................................................................................................................................. 18 Construction - Hand over to Construction - Subprocess Diagram .................................................... ...................................... ..................................... ...................................... ...................................... ..................................... ..................................... 19 Construction - Hand over to Construction - Subprocess .................................... ...................................... ..................................... ...................................... ..................................... ...................................... ...................................... .............................. 20 Scenario 2 – Deliver Design Data for Construction ............................................................................................................................................................................................................................................................................................................ 21 Construction - Deliver Design Data to Construction - Subprocess Diagram ..................................... ..................................... ...................................... ..................................... ...................................... ...................................... ..................................... 22 Construction - Deliver Design Data to Construction - Subprocess................................. ...................................... ...................................... ..................................... ...................................... ..................................... ...................................... .................. 23 Scenario 3 – Use Design Data for In-House Construction ................................................................................................................................................................................................................................................................................................. 24 Construction - Use Published Design Data Directly for In-House Construction - Subprocess Diagram ...................................... ..................................... ...................................... ...................................... ..................................... ................................ 25 Construction - Use Published Design Data Directly for In-House Construction - Subprocess ........................................................................................................................................................................................................................................... 26 Appendix..................................... ..................................... ...................................... ..................................... ...................................... ..................................... ...................................... ...................................... ..................................... ................................... 27 Smart Construction Capability by Document Type ............................................................................................................................................................................................................................................................................................................. 28 Smart Construction OnSite Work Process........................................................... ..................................... ...................................... ...................................... ..................................... ...................................... ..................................... .............................. 29 Diagram 1: Creating Pipe Spools for Procurement and Fabrication .................................... ...................................... ...................................... ..................................... ...................................... ..................................... ...................................... ............ 30 Diagram 2: Managing Pipe Spools for Construction..................................... ...................................... ..................................... ...................................... ..................................... ...................................... ...................................... .................................... 31 Defining the Rules of Progress for Construction .................................... ...................................... ..................................... ...................................... ..................................... ...................................... ...................................... ..................................... ..... 32 Revision History......................................................................................................................................................................................................................................................................................................................................................................... 33

Hexagon PPM Proprietary Information

Work Process for Constructi on Work Package Planning 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 stori es

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 t o 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 r epresented 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 r eferenced 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).


5


Contents The construction work package planning work process can be illustrated with a Level 1 diagram representing typical industry work processes and several Level 2 diagrams. Also, three handover scenarios for providing the data to construction are included in this document and the software capabilities provided by Intergraph Smart™ Construction depend on which document types are available, as listed in the Smart Construction Capability by Document Type (on page 28) matrix in the Appendix.

Level 1 swimlane diagram: 

Work Package Planning

Level 2 swimlane diagrams: 

Define Construction Strategy – Project Configuration



Define and Develop Installation Work Packages (IWPs)



Determine the Installation Work Package (IWP) Constructability



Issue Installation Work Package (IWP) and Monitor Progress



Smart Construction OnSite Work Process

Handover Scenario diagrams: 

Hand over to Construction



Deliver Design Data to Construction



Use Published Design Data Directly for In-House Construction

Capability matrix: 

Smart Construction Capability by Document Type

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: 16

Diagram 1: Creating Pipe Spools for Procurement and Fabrication

16

Diagram 2: Managing Pipe Spools for Construction

19

Defining the Rules of Progress for Construction

The work process diagram for each of t hese 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 m any copies of the delivered PDF files as t hey need for their non-commercial use. Do not print the PDF files f or resale or redistribution.

Notes about this Work Process Hand over Considerations There are several different ways that construction can obtain the data it needs for work package planning. Some scenarios will depend on who is doing the construction. Is it the same company as the one doing the engineering or a separate company? Will all the design data be handed over to construction, or only the deliverables it requires? Another consideration is how often the data will be shared. Will it occur one time at the end of the design or multiple times, based on a time schedule or the status of the design? Although export, import, back up, restore, and publish processes are shown once for each tool in the diagrams, they may occur multiple times, based on the project needs. Regardless of the scenario used, the construction manager should coordinate with the engineering team to define: 

How to split the engineering data for publishing (by modules, volume, and so forth)



How to sequence the publish of drawings and 3D models in order to meet construction schedules


6


Scenario 1 - Hand over to Construction This scenario documents the situation where design data is developed in a full SmartPlant Enterprise environment and then transferred to Smart Construction using a handover process. This handover process allows the transfer of data through a packaging process that sends copies of the engineering documents published to the SmartPlant Foundation Data Warehouse. Once the documents are transferred, the data published in them is loaded into Smart Construction for creating and managing work packages. SPE (or SPO) Handover is a commercial product that must be purchased separately before you can implement this scenario.

Scenario 2 - Deliver Design Data for Construction In this environment, the design data may or may not be developed in a f ully-integrated SmartPlant Enterprise environment before being transferred to Smart Construction. When design data is ready to be shared with Smart Construction, the engineering tools will create backups of their databases, which are then transferred to the construction environment. Once transferred, the databases are restored and the data is published to the construction SmartPlant Foundation site for use with Smart Construction.

Scenario 3 - Use Design Data for In-house Construction In this scenario, Smart Construction has access to the design data created by the engineering tools, as soon as it is published by the engineering tools – without waiting for either a handover process or a scheduled database backup/retrieve. The SmartPlant Foundation database to which the engineering tools publish is the same database accessed by Smart Construction for work package planning.


7


Construction - Work Package Planning - Level 1 Diagram


8


Construction - Work Package Planning - Level 1 1.

As an owner, I need to provide a set of standards and specifications, including safety standards, quality assurance standards, and so forth.

2.

As an owner, I need to define minimum site and plant requirements so that the construction company can put together a contract strategy. Site requirements might include site access, site security, and other restrictions.

3.

As a member of the Project Management group, I need to provide project requirements, including an extended set of standards and specifications originating from the owner’s input, to construction to create the contract strategy. These documents might be attached to the work packages later, as needed.

4.

As a construction planner, I need to do the following steps that define the construction strategy and project configuration: 

Establish, based on industry best practices, the appropriate construction strategy for work package planning.



Define the Construction Work Areas (CWAs) and project parameters, including the list of contractors, rules of progress, disciplines, labor factors and standard efficiency, authority, and so forth.



Get the construction work package (CWP) schedule from Project Controls to ensure that my work packages will match the parameters established by the construction schedule.

See the work process Construction - Define Construction Strategy - Project Configuration - Level 2 Diagram (on page 10) for more information. 5.

As a member of an engineering group, I need to provide design data to the construction planner to build and visualize the work packages. Design data may include 3D models, P&ID drawings, spool drawings, isometric drawings, and so forth.

6.

As a member of the Project Management group, I need to define the CWP schedule with estimated man hours so that I can share the construction timeframes with the construction planners.

7.

As a member of an Engineering group, I need to refresh the design data sent to the construction planner to build and visualize the work packages. Design data may include 3D models, P&ID drawings, spool drawings, isometric drawings, and so forth.

8.

As a fabricator, I need to supply fabrication deliverables, such as drawings, mill test reports, quality assurance (QA) documents, and so forth, to the construction planner.

9.

As a vendor, I need to provide documents, such as installation and maintenance documents, operation manuals, detailed drawings, quality certificates, and so forth, to the construction planner.

10. As a construction planner, I need to define and develop the installation work packages (IWPs) by providing detailed information about the work package and the relevant scope and schedule. See the work process Construction - Define and Develop Installation Work Packages (IWPs) - Level 2 Diagram (on page 12) for more information. 11. As a construction planner, I need to apply the rules of progress so that work steps are assigned and standard man hours are calculated. 12. As a construction planner, I need to do the following steps that determine the installation work package (IWP) constructability. 

Define the sequence of the installation work packages (IWPs) and their components.



Check the availability of materials.



Manage the constraints.

See the work process Construction - Determine the Installation W ork Package (IWP) Constructability - Level 2 Diagram ( on page 14) for more information. 13. As an owner, I need to review the sequence of installation work packages (IWPs) so t hat I can ensure that t he construction process is efficiently planned and meets the contractual requirements. 14. As a member of the Material Controls group, I need to provide the material availability information, which includes inventory and expected deliveries. 15. As a construction planner, I need to do the following steps to issue the installation work packages (IWPs) and monitor their progress. 

Issue the installation work packages (IWPs) according to project parameters.



Collect actual progress data during construction.



Monitor and report on the actual progress so that I can drive the successful completion of the construction project.

See the work process Construction - Issue Installation Work Package (IWP) and Monitor Progress - Level 2 Diagram (on page 16) for more information.


9

Hexagon PPM Proprietary Information Construction - Define Construction Strategy - Project Configuration - Level 2 Diagram


10

Hexagon PPM Proprietary Information Construction - Define Construction Strategy - Project Configuration - Level 2 1.

As a member of the Project Management team, I need to establish the construction strategy. I need to evaluate the information from other organizations, so I can plan the best approach to execute construction planning with the resources available. This information includes the design data and where it i s coming from (SmartPlant Enterprise or other), project schedule, site parameters, and so forth, and will drive the project configuration of Smart Construction.

2.

As a Smart Construction administrator, I need to define security for the construction project, such as planning groups (optional), roles, and users to set user access rights. This information is defined using the SmartPlant Foundation Desktop Client.

3.

As a project scheduler, I need to define the construction schedule using Primavera or some other scheduling software. This information can be: (Option A) created in Primavera or as part of the project configuration information imported into Smart Construction using spreadsheets; or (Option B) configured directly in Smart Construction using the SmartPlant Foundation Desktop Client.

4.

As a Smart Construction administrator, I need to import the construction schedule from Primavera or some other scheduling software into Smart Construction.

5.

As a construction planner, I need to set the rules of progress, including work steps and unit rates, according to the discipline, purpose, and component class definition. This information should be entered into a special template delivered with Smart Construction. See the following Integration Capability Statement for m ore information: 


6.

As a Smart Construction administrator, I need to define, in SmartPlant Server Manager, the path to the spreadsheet that contains the rules of progress information stored on the Smart Construction application server for reference by the software.

7.

As a Smart Construction administrator, I need to retrieve design data into Smart Construction so that I can plan the work packages. For more information see the handover scenario diagrams described later in this document.

8.

As the components are associated with the work package, the rules of progress are applied automatically by Smart Construction to determine the actual work steps and the planned man hours.

The project configuration information can be (Option A) imported from spreadsheets into Smart Construction or (Option B) entered directly into Smart Construction using the SmartPlant Foundation Desktop Client.

9.

As a Smart Construction administrator, I need to validate that work steps and rates are applied to all components using the Rules of Progress Utility.

10. As a Smart Construction administrator, I need to determine if the work steps and rates are defined for all the components. 11. As a Smart Construction administrator, I need to add the missing rules of progress (work steps and/or rates) for the components that were not covered. Next, I will manually apply the rules of progress (option 1), or wait until the next “Retrieve Design Data” operation (option 2) to validate again that the work steps and rates are applied to all components. 12. (Option 1) As a Smart Construction administrator, I need to apply the rules of progress within the Rules of Progress utility. 13. (Option A) As a construction planner using a spreadsheet, I need to define the project configuration in Excel. The project configuration information defines construction work packages, contractors, contracts, construction resources, crews, and schedule information and relates drawings and relates planning groups. This information should be entered into a special template delivered with Smart Construction 14. (Option A) As a Smart Construction administrator using a spreadsheet, I need to import the project configuration spreadsheet. 15. (Option B) As a Smart Construction administrator using SmartPlant Foundation Desktop client, I need to interactively define the project configuration information. The project configuration information defines construction work packages, contractors, contracts, construction resources, crews, and schedule information and relates drawings and relates planning groups. The project configuration information can be imported into Smart Construction using a spreadsheet (Step 14) or it can be created directly in Smart Construction using the SmartPlant Foundation Desktop Client (Step15). Once the information has been loaded into the database, it can be manipulated further using the SmartPlant Foundation Desktop Client.


11

Hexagon PPM Proprietary Information Construction - Define and Develop Installation Work Packages (IWPs) - Level 2 Diagram


12

Hexagon PPM Proprietary Information Construction - Define and Develop Installation Work Packages (IWPs) - Level 2 1.

As a construction planner, I need to create or update the installation work packages (IWPs) with information such as work package number; the related construction work package from the schedule; and contractors, disciplines, purpose, status, and area from project configuration information.

2.

As a construction planner, I need to schedule each installation work package (IWP) with planned start and finish dates and estimated man hours.

3.

As a construction planner, I can provide additional details of the scope of the installation work packages (IWPs), such as any special circumstances, so that it is available to the workforce.

4.

(subprocess) As a construction planner, I need to retrieve the design data from the SmartPlant Foundation Engineering site into Smart Construction. For more information see the handover scenario diagrams described later in this document.

5.

As a construction planner, I can add drawings from design tools for reference, if needed. When a drawing is added to the installation work package (IWP), I can choose to automatically attach the components to the installation work package (IWP).

6.

As a construction planner, I can add fabrication drawings for reference, if needed. When a fabrication drawing is added to the installation work package (IWP), I can choose to automatically attach the components to the installation work package (IWP).

7.

As a construction planner, I can manually add components to the work package so that the work package is fully defined with all requirements to complete the work. Components may be manually added to installation work packages (IWPs) from within models, drawings, and component registers, or by manually creating ad-hoc component items directly in the IWP Components screen.

8.

As the components are associated with the installation work package (IWP), the rules of progress are applied automatically by Smart Construction to determine the actual work steps and the planned man hours.

9.

As a construction planner, I can attach relevant documents to the installation work package (IWP) for reference as needed, such as vendor documents, standards and specification documents as supplied by the owner, checklists, images, videos and other documents.

Components must be added using one or more of the methods described in steps 5-7.

10. As a construction planner, I need to r efine and validate the installation work packages (IWPs). This may include adjusting work steps, printing and validating the work package.


13

Hexagon PPM Proprietary Information Construction - Determine the Installation Work Package (IWP) Constructability - Level 2 Diagram


14

Hexagon PPM Proprietary Information Construction - Determine the Installation Work Package (IWP) Constructability - Level 2 1.

As a construction planner, I need to define a time frame that represents a portion of the construction so that the software identifies the appropriate installation work packages (IWPs) include in the simulation based their planned start and finish dates.

2.

As a construction planner, I need to perform a 4D (of a model or a drawing) simulation so that I can review the sequence of the installation work packages (IWPs) within that time frame to ensure constructability.

3.

As a construction planner, I need to watch the simulation to determine if the order of the installation work packages (IWPs) is acceptable or if any occur out of sequence (such as columns being placed prior to foundations being installed).

4.

As a construction planner, to address any encountered conflicts, I need to redefine the sequence of the installation work packages (IWPs), move components from one work package to another, or delete components from the work package. Snapshots can be used to document any conflicts encountered during the 4D simulations. See the work process Construction - Define and Develop Installation Work Packages (IWPs) - Level 2 Diagram (on page 12) for more information.

5.

As a construction planner, I need to select an installation work package (IWP) to review in SmartPlant Review and use its animation features to review installation paths of one or more components within the installation work package (IWP).

6.

As a construction planner, I need to select the specific components for animation.

7.

As a construction planner, I need to apply the timeline and create the installation path.

8.

As a construction planner, I need to review the animation of the installation path of the included components to ensure the most efficient installation sequence.

9.

As a construction planner, I need to determine if the animation illustrated any conflicts that need to be addressed.

10. As a construction planner, I can record and send a video of the component installation sequence animation so that it can be attached to the installation work package (IWP). 11. As a construction planner, I need to send the component sequence from SmartPlant Review to Smart Construction. 12. The component sequence is updated automatically using data from SmartPlant Review. 13. As a construction planner, I need to attach the SmartPlant Review video to the work package so that the work crew has a visual aid to complete the installation of the installation work package (IWP). 14. As a construction planner, I need to check if the materials required for the installation work package (IWP) will be available by the planned start date of the installation work package (IWP) by running a forecast in Intergraph Smart® Materials. If another materials management system is used, customization is required. 15. Smart Materials builds a forecast, based on the drawing and the components attached to the installation work package (IWP), to check if the material is in inventory or available based on upcoming shipments. The results are returned to Smart Construction. If you are using Smart Materials and have configured it to work with the delivered Smart Construction API, this report is created automatically in Smart Materials through a command in Smart Construction. For any other material management applications, an API is provided and additional customization is required. 16. As a construction planner, I need to determine if the material is available when it is needed based the forecast results returned by Smart Materials. 17. As a construction planner, to address material shortages, I need t o redefine the sequence of the work packages, move components from one work package to another, or delete the components from the work package. See the work process Construction - Define and Develop Installation Work Packages (IWPs) - Level 2 Diagram (on page 12) for more information. 18. As a construction planner, based on the material availability from the forecast, I need to run a reservation to ensure the materials in Smart Materials are allocated for the installation work package (IWP). 19. Smart Materials reserves the materials based on the f orecast and availability. 20. As a construction planner, I need to determine if all other constraints (such as equipment, tools, permits, and crews) are met. 21. As a construction planner, I need to determine if the constraints can be resolved. 22. As a construction planner, to address any unresolvable constraints, I need to redefine the sequence of the work packages, move components from on work package to another, or delete the components from the work package. See the process Construction - Define and Develop Installation Work Packages (IWPs) - Level 2 Diagram (on page 12) for more information. 23. As a construction planner, I need to resolve the remaining constraints. 24. As a construction planner, I need to prepare the installation work package (IWP) for issue so that construction can begin.


15

Hexagon PPM Proprietary Information Construction - Issue Installation Work Package (IWP) and Monitor Progress - Level 2 Diagram


16

Hexagon PPM Proprietary Information Construction - Issue Installation Work Package (IWP) and Monitor Progress - Level 2 1.

As a construction planner, I need to print the installation work package (IWP) report with drawings and all attachments.

2.

As a construction planner, I may route the installation work package (IWP) for approval, if needed.

3.

As a construction planner, I need to update the installation work package (IWP) status to IFC after the approval cycle and necessary revisions have been made so that the foreman knows that the installation work package (IWP) is ready to begin and is assigned to him.

4.

As a member of the materials department, I need create the material issue report so that the warehouse crew can identify and stage the necessary materials required to complete the work package.

5.

As a member of the construction team, I need to pick up the materials.

6.

As a member of the construction team, I need to execute the work required to complete the installation work package (IWP).

7.

As a member of the construction team, I need to determine if the Smart Construction OnSite mobile application will be used to input progress.

8.

As a member of the construction team using SPC OnSite, I need to input the progress on a regular basis by marking work steps complete on my device. For more information on using the Smart Construction OnSite application, see the Smart Construction OnSite Work Process (on page 29) diagram in the Appendix.

9.

When the device is connected to the SPC server, the installation work package (IWP) progress is automatically updated in Smart Construction.

10. As a member of the construction team, I need to r eport on the progress on a r egular basis by providing a scorecard (a marked-up document that indicates what work has been completed). 11. As a construction planner, I need to input the progress information into Smart Construction for components. 12. As a construction planner, I may attach documents and photographs from construction, as needed, documenting the work done, issues encountered that impacted reported progress to date, or problems that might arise later. 13. As a construction planner, I need to m onitor the progress by installation work package (IWP), by contractor, by discipline, or by construction work package (CWP). 14. As a construction planner, I may choose to display and filter the model, based on t he completion status of the installation work packages (IWPs), to track the progress and to visually compare t he actual progress to the plan. This visual comparison can be used to influence the scheduling of other installation work packages (IWPs), as well as in weekly project meetings. 15. As a construction planner, I need to determine if the work is completed by using the progress reported, documents and photographs attached, and any other available information. 16. As a construction planner, I need to m ark the installation work package (IWP) complete in Smart Construction, entering completion date and attaching any final documentation, as necessary.


17

Hexagon PPM Proprietary Information Scenario 1 – Hand over to Construction


18

Hexagon PPM Proprietary Information Construction - Hand over to Constructi on - Subprocess Diagram


19

Hexagon PPM Proprietary Information Construction - Hand over to Constructi on - Subprocess This process describes the controlled hand over from engineering to construction using a handover package of published engineering documents.



This process includes steps in two SmartPlant Foundation databases – the SmartPlant Foundation Engineering database, where design data is developed and shared in a SmartPlant Enterprise environment, and another SmartPlant Foundation Construction database, where the published documents and data are made available for use in construction. These two databases may be in different locations or belong to different companies; therefore, a handover process is required.



SPE Handover (or SPO Handover) is a commercial product that must be purchased separately before you can implement this scenario.

1.

As an engineer or designer, I may provide structural detail in the CIS/2 format for Smart3D or SDNF for PDS.

2.

As an engineer or designer, I may provide the 3D model that can be translated by Intergraph Smart® Interop Publisher and whose format is supported by Smart Construction so that it can be shared with the SmartPlant Enterprise environment. Smart Construction support components from models translated by Smart Interop Publisher coming from t he following applications: 

Intergraph Smart® 3D: full support



AVEVA PDMS: support for ATT/RVM files and basic properties which can be extended by SPIOP mapping



Tekla IFC: support for basic properties, and including implied items such as bolts, nuts, washers, and welds

3.

As an engineer or designer, I need to publish the Intergraph Smart™ 3D model and drawings.

4.

As an engineer or designer, I need to publish the PDS model and drawings.

5.

As an engineer or designer, I need to translate the 3D model using Smart Interop Publisher, so that it can be published and shared with Smart Construction.

6.

As a tool administrator, I need to publish the Smart Interop Publisher Smart Model.

7.

As an engineer or designer, I need to publish SmartPlant P&ID drawings.

8.

As an engineer or designer, I need to publish SmartPlant Instrumentation documents. Note that these documents do not provide components to Smart Construction.

9.

As an engineer or designer, I need to publish SmartPlant Electrical documents. Note that these documents do not provide components to Smart Construction.

10. As an engineer or fabricator, I may publish SmartPlant Spoolgen drawings. See the following Integration Capability Statement for more information: 

Creating Pipe Spools for Procurement and Fabrication

11. SmartPlant Foundation places the published files in the vault for storage. 12. As an engineering administrator, I need to create t he handover package by selecting the documents ready to be issued and shared with Smart Construction. 13. As an engineering administrator, I need to export the handover package and send the issued documents extracted from the engineering SmartPlant Foundation vault to the construction SmartPlant Foundation environment. 14. As a Smart Construction administrator, I need t o import handover package files into the construction SmartPlant Foundation environment. 15. As an engineer or fabricator, I need to publish SmartPlant Spoolgen drawings. See the following Integration Capability Statement for more information: 


16. SmartPlant Foundation places the published files in the vault for storage. 17. As a Smart Construction administrator, I need retrieve the models and drawings for use in work packages.


20

Hexagon PPM Proprietary Information Scenario 2 – Deliver Design Data for Construction


21

Hexagon PPM Proprietary Information Construction - Deliver Design Data to Construction - Subprocess Diagram


22

Hexagon PPM Proprietary Information Construction - Deliver Design Data to Construction - Subprocess This process describes the controlled transfer of design data from engineering to construction using backup and restore of the SmartPlant tools' data. In this case, a SmartPlant Enterprise integration environment may or may not exist on the engineering side. The construction company has all the tool data and will control when it is published and made available to Smart Construction. The design data may be backed up and restored multiple tim es over the course of the project (for instance at significant project milestones) without aff ecting the existing data that has already been used by Smart Construction. After restoring the design data at Construction, re-registration of the r estored databases with the SmartPlant Foundation plant at Construction must take place, and t he plant signature must remain unchanged. This can be achieved by specifying the same Tool Plant Description during registration of the restored tool databases. 1.

As a tool administrator, I need to back up the Smart 3D database.

2.

As a tool administrator, I need to restore the Smart 3D database in the construction SmartPlant Enterprise environment.

3.

As a tool administrator, I need to publish the Smart 3D model and drawings.

4.

As a tool administrator, I need to back up the PDS database.

5.

As a tool administrator, I need to restore the PDS database in the SmartPlant Enterprise environment.

6.

As a tool administrator, I need to publish the PDS model and drawings.

7.

As an engineer or fabricator, I need to back up the SmartPlant Spoolgen drawings.

8.

As a tool administrator, I need to restore the SmartPlant Spoolgen drawings in the SmartPlant Enterprise environment.

9.

As a tool administrator, I need to publish SmartPlant Spoolgen drawings. See the following Integration Capability Statement for more information: 


10. As a tool administrator, I need to back up the SmartPlant P&ID database, including the SmartPlant Engineering Manager database. 11. As a tool administrator, I need to restore the SmartPlant P&ID database, including the SmartPlant Engineering Manager database, in the construction SmartPlant Enterprise environment. 12. As a tool administrator, I need to publish SmartPlant P&ID drawings. 13. As a tool administrator, I need to back up the SmartPlant Instrumentation database. Note that these documents do not provide components to Smart Construction. 14. As a tool administrator, I need to restore the SmartPlant Instrumentation database in the SmartPlant Enterprise environment. 15. As a tool administrator, I need to publish SmartPlant Instrumentation documents. Note that these documents do not provide components to Smart Construction. 16. As an engineer or designer, I may provide structural detail in the CIS/2 format for Smart 3D or SDNF for PDS. 17. As a tool administrator, I need to back up the SmartPlant Electrical database, including the SmartPlant Engineering Manager database. Note that these documents do not provide components to Smart Construction. 18. As a tool administrator, I need to restore the SmartPlant Electrical database, including the SmartPlant Engineering Manager database, in the construction SmartPlant Enterprise environment. 19. As a tool administrator, I need to publish SmartPlant Electrical documents. Note that these documents do not provide components to Smart Construction. 20. As an engineer or designer, I need to prepare the 3D model t hat can be translated by Smart Interop Publisher and whose format is supported by Smart Construction* so t hat it can be shared with the SmartPlant Enterprise environment. *Smart Construction supports components from models translated by Smart Interop Publisher coming from the following applications: 

Smart 3D: full support



AVEVA PDMS: support for ATT/RVM files and basic properties which can be extended by Smart Interop Publisher mapping




21. As an engineer or designer, I need to translate the 3D m odel using Smart Interop Publisher, so that it can be published and shared with Smart Construction. 22. As a t ool administrator, I need to publish the Smart Interop Publisher Smart Model. 23. SmartPlant Foundation places the published files in the vault for storage. 24. As a Smart Construction administrator, I need retrieve the models and drawings for use in work packages.


23

Hexagon PPM Proprietary Information Scenario 3 – Use Design Data for In-House Construction


24

Hexagon PPM Proprietary Information Construction - Use Published Design Data Directly for In-House Construction - Subprocess Diagram


25

Hexagon PPM Proprietary Information Construction - Use Published Design Data Directly for In-House Construction - Subprocess In this case, there is no separate SmartPlant Enterprise environment where published data is managed and shared before it is transferred to Smart Construction. The Smart Construction and SmartPlant Foundation databases are the same. Construction has control of what published documents will be r etrieved into the Smart Construction application. 1.

As an engineer or designer, I may provide structural detail in the CIS/2 format for Smart3D or SDNF for PDS.

2.

As an engineer or designer, I may provide the 3D model that can be translated by Smart Interop Publisher and whose format is supported by Smart Construction so that it can be shared with the SmartPlant Enterprise environment. Smart Construction support components from models translated by Smart Interop Publisher coming from t he following applications: 

Smart 3D: full support



AVEVA PDMS: support for ATT/RVM files and basic properties which can be extended by Smart Interop Publisher mapping




3.

As an engineer or designer, I need to publish the Intergraph Smart™ 3D model and drawings.

4.

As an engineer or designer, I need to publish the PDS model and drawings.

5.

As an engineer or designer, I need to translate the 3D model using Smart Interop Publisher, so that it can be published and shared with Smart Construction.

6.

As a tool administrator, I need to publish the Smart Interop Publisher Smart Model.

7.

As an engineer or designer, I need to publish SmartPlant P&ID drawings.

8.

As an engineer or designer, I need to publish SmartPlant Instrumentation documents. Note that these documents do not provide components to Smart Construction.

9.

As an engineer or designer, I need to publish SmartPlant Electrical documents. Note that these documents do not provide components to Smart Construction.

10. As an engineer or fabricator, I need to publish SmartPlant Spoolgen drawings. See the following Integration Capability Statement for more information: 


11. SmartPlant Foundation places the published files in the vault for storage. 12. As a Smart Construction administrator, I need retrieve the models and drawings for use in work packages.


26


App endi x Capability Matrix Smart Construction Capability by Document T ype

Add iti onal Work P roc ess Di agram Smart Construction OnSite Work Process

Integration Capability Statement The first page of t he referenced Integration Capability Statements are included on the following pages. 16

Diagram 1: Creating Pipe Spools for Procurement and Fabrication

16

Diagram 2: Managing Pipe Spools for Construction

19


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


27

Hexagon PPM Proprietary Information Smart Construction Capability by Document Type Smart Construction Capability by Document Type Documents available to Smart Construction Models Models published published by Smart 3D by PDS

SmartPlant Review models published by Smart Interop Publisher

Smart 3D models published by Smart Interop Publisher

PDS models AVEVA PDMS published by models Smart published by Interop Smart Interop Publisher Publisher

Tekla models (via IFC) published by Smart Interop Publisher

Spool drawings published by SpoolGen

P&IDs published by SmartPlant P&ID

Cable schedules published by SmartPlant Electrical

Microsoft Excel registers

SmartPlant Data Validator (SDV) registers

Y

Y

Y

Y

Y

Y

Y

Y

Smart Construction Capability Y

Y

Y

Y

Y

View 3D models

Y

Y

Y

Y

Y

Y

Y

Drag model components into work packages

Y

Y

Y

Y

Y

Y

Y (see Note 1)

Filter 3D model

Y

Y

Y

Y

Y

Y

Y (see Note 2)

Schedule animation of 3D model

Y

Y

Y

Y

Y

Y

Y

View/Attach drawings

Y

Y

Y

Y

Drag drawing components into work packages

Y

Y

Y

Y

Filter drawing

Y

Y

Y

Y

Schedule animation of drawings

Y

Y

Y

Y

Integrate with Smart Materials

Y

Y

Generate material requests

Y

Y

Y

Y

Plan generated work steps

Y

3D Models

Drawings

Materials

Y

Y

Where Y is shown, the Smart Construction capability is available if all product capabilities were used when the data was created in the authoring application shown. Gray boxes signify that the functionality is not applicable.

1.

Some structural objects (such as stairs and handrails) are easier to select if they exported from Tekla to IFC as full structural assemblies instead of exploded parts.

2.

We recommend creating a custom filter to highlight the structural components with the same piece mark or assembly mark.


28

Hexagon PPM Proprietary Information Smart Construction OnSite Work Process


29

Hexagon PPM Proprietary Information Diagram 1: Creating Pipe Spools for Procurement and Fabrication


30

Hexagon PPM Proprietary Information Diagram 2: Managing Pipe Spools for Construction


31

Hexagon PPM Proprietary Information Defining the Rules of Progress for Construction


32

Enterprise Work Process for Construction Work Package Planning

Recommend Documents