06.04.13

Insert Company Name or LOGO Here

SMARTER INTEGRATION Rethinking SmartPlant P&ID and SmartPlant Instrumentation Integration John Dressel, Fluor, Principal Application Specialist

06.04.13

Insert Company Name or LOGO Here Value Proposition

• The Integration of Data between Intergraph SmartPlant P&ID and SmartPlant Instrumentation is not being done effectively Business Problem

• We must Rethink how we use SmartPlant P&ID and SmartPlant Instrumentation in an Integrated data centric environment Solution

• By Rethinking our SmartPlant P&ID and SmartPlant Instrumentation work processes we will be able to improve the quality and quantity of the integrated data

Benefits

• Better integration of data between SmartPlant P&ID and SmartPlant Instrumentation will improve the overall quality of Control Systems Engineering, Procurement and Construction

Anticipated Long-Term Benefits (optional)

• We plan to utilize multiple solutions for integration by changing how we use SmartPlant P&ID and employing other Intergraph integration tools for data management

Future Plans/Strategy or Summary Statement

2

06.04.13

Insert Company Name or LOGO Here Rethinking SmartPlant P&ID and SPI

Integration of SP-P&ID with SPI - The Story – The Great Story of SP-P&ID Integration

SmartPlant P&ID Integration Issues – Timing of Publish and Retrieve cycle – Handling of Instrument Types and Technology – Expanding and Excluding Integrated Tags – Quality and Quantity of P&ID Data

Fluor’s SmartPlant P&ID Integration – Fluor’s NEXTGENERATIONsm Initiative – Correlation of P&ID Tags from SPF to SPI

Tools for Integration of SP-P&ID with SPI – SPI Batch Loop Creation Templates – SPI Macro Expansion of Implied Tags – SmartPlant P&ID Engineering Data Editor – SmartPlant P&ID Engineering Integrity

Applying what we have learned by Rethinking Smart

06.04.13

Insert Company Name or LOGO Here The Great Story of SP-P&ID Integration

“SmartPlant P&ID Instrument Integration consists of creating the Instrument Tags in SP-P&ID then Publishing them to SPF so they can be Retrieved and automatically built in SPI.” – REALLY? – Integrating Instrument Tag Numbers early in the P&ID development will

not have sufficient quality of data to support line and process association

– Usually when the P&ID’s are complete enough to extract Tag numbers, it is too late to meet schedule for publishing the first Index from SPI

– Just bringing Tag Numbers into SPI does not initiate all of the required associations needed to propagate Instrument Types, Specs, Wiring, Etc…

– Not all Tags required in SPI are shown on the P&ID so additional implied tags will need to be added manually which is a slow tedious process

– Not all Tags shown on the P&ID are required to be Indexed in SPI so we must exclude unwanted Tags during the Publish and Retrieve cycle

– The Quality and Quantity of Instrument Data on the P&ID is Minimal

06.04.13

Insert Company Name or LOGO Here SmartPlant P&ID Integration Issues

When it is Piping and Instrumentation DATA!

Mitigating Issues when Integrating Data – Timing of Publish and Retrieve cycle – Handling SPI Instrument Types – Showing Technology on P&IDs – Expanding Implied Tags in SPI – Excluding Unwanted Tags – Quality of P&ID Data – Minimal P&ID Data

When is a P&ID not a “Piping and Instrument Diagram”

Since you can’t integrate Graphics - the P&ID Data must be correct, consistent and compliant for execution in an integrated environment

06.04.13

Insert Company Name or LOGO Here SmartPlant P&ID Integration Issues

Timing of Publish and Retrieve cycle – The First issue of the SPI Instrument Index is usually required long

before the P&ID is ready for design – Even when the P&ID Graphics look complete, the Data is not necessarily

ready for publishing – Fast track Engineering projects require P&ID and SPI data to be

developed concurrently Method for mitigating the timing issues between SPI and P&ID

– Create the Instrument Tags and Data in each tool independently and Correlate Tags in SmartPlant Foundation during Integration

06.04.13

Insert Company Name or LOGO Here SmartPlant P&ID Integration Issues

Handling SPI Instrument Types – The Instrument Type Profiles in SPI are essential for proper introduction

and automation of new Tags into the SPI Index – The Out of the Box Instrument Types in P&ID and SPI do not match in

Type or Description

Methods for aligning Instrument Types: – Allow improper instrument Types from P&ID

to Integrate to SPI and correct in SPI – Do not map P&ID Instrument Types and

assign them in SPI after integration – Retrieve SPI Instrument Types into P&ID and

synchronize proper type for each Tag in the P&ID data properties before Integration

– Create all Tags in SPI and Correlate to P&ID

All of these SPI Instrument Types are

defined as “CV” in P&ID

06.04.13

Insert Company Name or LOGO Here SmartPlant P&ID Integration Issues

Showing Technology on P&IDs – The Symbols used on most P&IDs do not properly convey Data such as

Device Type, Signal Type, Measurement Technology or System Type – The use of outdated or abbreviated symbols results in Data gaps when

Integrating, Reading or Interpreting P&IDs Current Symbol Standard ANSI/ISA-5.1-2009

– Defines Symbols for BPCS, DCS, PLC & SIS – Defines Symbols for Hardware and Software – Added Signal Type Symbols for Wireless,

Fieldbus, Smart Digital or Serial signals – Added New Measurement Technology Symbols – Added Valves with Positioner and Controllers – Added Function modifier "Z" for SIS – Defines Naming Conventions for Loops and Tags – Now has over1000 Instrument Type identifiers

The Instrument Type “CV” is Not an ISA

Recognized Identifier

06.04.13

Insert Company Name or LOGO Here SmartPlant P&ID Integration Issues

Expanding Implied Tags in SPI – The Required number of Instrument Tags in SPI are much more than the

number of Tags shown on the P&ID by using abbreviated symbols Methods for Including Implied Tags in SPI integration

– Show All Instrument Tags on the P&ID without Details – Use Macro Expansion in SPI to expand loops with Implied Tags – Create all Required Tags in SPI then Correlate to P&ID

P&ID Typical Details

06.04.13

Insert Company Name or LOGO Here SmartPlant P&ID Integration Issues

Excluding Unwanted Tags in SPI – SPI is used to document field hardware and wiring data and may not

contain the Soft or System Tags that are shown on the P&ID Methods for Excluding Unwanted Tags in SPI

– Exclude unwanted Instrument Types in P&ID Integration mapping – Manual selection of wanted Tags in the To-Do list during Integration – Create only required Tags in SPI and Correlate to P&ID

Typical DCS Configuration

06.04.13

Insert Company Name or LOGO Here SmartPlant P&ID Integration Issues

Quality of P&ID Data – The P&ID is developed by Process Graphics users who are focusing on

the graphic and visual content of the P&ID without regard to the underlying Data so the quality of underlying data is suspect

Methods for Improving the Quality of P&ID Data – Generate reports and check data in P&ID before Integration – Limit the amount of data that is mapped and published from P&ID – Use P&ID Engineering Integrity or Data Editor to correct the P&ID Data

P&ID Data Properties

06.04.13

Insert Company Name or LOGO Here SmartPlant P&ID Integration Issues

Quantity of P&ID Data – The lack of dependable Instrument Data properties in the P&ID results in

only a few fields of data being mapped and integrated to SPI – The Symbol Properties do not provide for enough useful Data Fields for

Identify the measurement technology or signal types of instruments

Methods for expanding the Quantity of Instrument Data during integration: – Create new Symbol Properties as needed – Use P&ID Engineering Data Editor and

Engineering Integrity to populate and validate Instrument Data properties

– Use Macro Expansion in SPI and define additional data in the SPI Instrument Type Profiles and Spec Templates

Minimum P&ID Data

06.04.13

Insert Company Name or LOGO Here

Fluor’s SmartPlant P&ID Integration

Fluor’s NEXTGENERATIONsm Initiative

Correlation of P&ID Tags from SPF to SPI

PUBLISH PUBLISH

RETREVE DO NOT

RETREVE

Mission Statement: Fluor’s investment supporting the NEXTGENERATIONsm Initiative

is a proactive approach to successfully deploy the Intergraph SmartPlant Suite of technologies within Fluor in advance of all production projects

06.04.13

Insert Company Name or LOGO Here

Fluor’s NEXTGENERATIONsm Initiative

SmartPlant P&ID Publishes P&ID Diagram Numbers, Instrument Numbers, Line Numbers, Equipment Numbers and Associated Data to SmartPlant Foundation

Other SmartPlant tools retrieve the P&ID Data from the SmartPlant Foundation

06.04.13

Insert Company Name or LOGO Here SmartPlant P&ID Content

Drafting Shortcuts Corrupt the Quality of Data

No Practice for Entering or Checking Tag Data

Implied Symbols result in Implied or Missing Data

No Standard for Data Properties assigned to Symbols

15

Graphics

Database

06.04.13

Insert Company Name or LOGO Here SPI Macro Expansion

16

SmartPlant Instrumentation Macro Expansion for Loop Generation – Assign a Macro name for each P&ID detail

to a carrier Tag in the loop

– Limits the amount of data required on the P&ID for Loop and Tag Creation in SPI

– Allows Control Systems to create Tag and Loop Data in SPI without Instrument Type

– Adds the Ability to Create P&ID Implied Tags and remove unwanted Tags in SPI during Integration

– Improves Quality of Instrumentation Data by leveraging the SPI Instrument Type Profile when automatically Creating Tags

06.04.13

Insert Company Name or LOGO Here SPI Macro Expansion

17

Instrument and Loop Typicals in SPI Macro Structure Defined in SPI Macro Carrier assigned in SP-PID Additional Tags show up In SPI To-Do-List

SPI Data before Retrieving from SP-PID

SPI Data after Retrieving from SP-PID

06.04.13

Insert Company Name or LOGO Here SP-P&ID Engineering Data Editor

18

Already built into the standard SP-PID Engineering Client Installation

Allows Engineering Access to P&ID Data and Properties without affecting Process Graphics

Creates Cross Discipline SmartPlant P&ID Work Processes

Establishes Discipline Data Ownership in the P&ID database

Improves the Quantity and Quality of Data in SP-PID before Integration

06.04.13

Insert Company Name or LOGO Here SP-P&ID Engineering Data Editor

19

Allows the Control Systems Engineer to: – Assign and Maintain Instrument Tagging in

the P&ID Database – Associate Instruments to Loops on the P&ID – Add additional information to the Loop and

Tag Properties inside the P&ID Database – Check and Validate the loop and Instrument

Data in the P&ID Will Not Allow the Control Systems Engineer to:

– Modify the P&ID Graphics in any way – Add or Remove Tags or Loops on the P&ID

Needs: MOC and Group Rights to be considered a useful tool on Production databases

06.04.13

Insert Company Name or LOGO Here SP-P&ID Engineering Integrity

SmartPlant P&ID Engineering Integrity will check the P&ID against safety rules, engineering practices and project standards then report any inconsistency.

Delivered with over 3,000 rules Allows users to create their own rules Can validate data in SPI and P&ID Ensure the quality and dependability of

Integrated data Capture Discipline, Client and EPC’s Best

Practices with Custom Rules Creates Cause and Effects Diagrams

06.04.13

Insert Company Name or LOGO Here SP-P&ID Engineering Integrity

21

Some typical Instrumentation Engineering Integrity Rules – Missing or Incorrect Car Seals on Relief Valve Bypasses and blocks – Missing or incorrect flow direction across Flow Instruments – Instruments not associated to proper Process Function – Missing Line Spec Data to support In-Line Instruments – Instrument Type and Tag numbers are incorrect – Instruments not associated to a Loop number – Missing signal types on Instrument bubbles – Missing failure states on Control Valves – Relief valves sizes and end sizes

21

SmartPlant P&ID Needs: Ability to run in continuous mode to

check data and graphics as it is entered

06.04.13

Insert Company Name or LOGO Here What We Learned by Rethinking Smart!

Improve Control Systems involvement in Developing and Validating P&ID Symbols and Content on all Projects

Develop New Practices and Work Processes based on current SP-PID and SPI NEXTGENERATION Practices

Establish Practice and Work Process using SPI Macro Expansion Establish Practice and Work Process using SP-PID Engineering Establish Work Processes using SP-PID Engineering Integrity

Please hold your questions until after the end of the next presentation or contact:

John Dressel,

Fluor Principle Applications Specialist

John.Dressel@Fluor.com

06.04.13

Insert Company Name or LOGO Here The Next Great Story Starts Here

Once the data is integrated into SmartPlant Instrumentation, we must address using and documenting the data in a work sharing environment

Dee Dee Honea, Foster Wheeler SPI Administrator will now address Documenting Challenges and Solutions when using SmartPlant Instrumentation in a Integrated work sharing engineering environment

SmartPlant

Integration Work Sharing

The Great Story of SmartPlant Instrumentation