3/22/10 FOOTER: EDIT THIS AND THE DATE IN THE “MASTER” >

“SLIDE MASTER” UNDER THE “INSERT” MENU.

REPLACE GREY BOX

WITH COMPANY LOGO.

EDIT THIS IN THE

“SLIDE MASTER”.

SPI - SP-P&ID - SPEL INTEGRATION

John Dressel, FLUOR Applications Specialist

3/22/10

SPI - SP-P&ID - SPEL Integration

SP-P&ID Publishes to SmartPlant Foundation for SPI & SPEL Retrieval

SPI correlates Instrument tag Numbers with SP-P&ID and Publishes Instrument Power

requirements and signals for SPEL

SPEL Retrieves Instrument power requirements and signals from SPI and Electrical

Equipment from P&ID

3/22/10

Implementation of SP-P&ID Integration

SmartPlant P&ID “Publish” 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

3/22/10

SP-PID to SPI Interface

PRE-REQUISITES:

SPI and SP P&ID must be configured for integration

– Plant, Area, Unit structure needs to be compatible with the integrated environment

Note: Make sure to register all units associate with the plant for SP P&ID.

– SP P&ID Symbols library must be developed with any project specific modification

included.

– Instrument Tag Naming Conventions from SPI and SP P&ID must be compatible for

data correlation.

– The project configuration needs to register to SP PID client workstation.

3/22/10

Publish SP-PID to SmartPlant Foundation

When P&ID is ready to publish to SPF, a revision

needs to be created and assigned to the P&ID.

The P&ID can be re-published anytime with a new

version number

– If P&ID Revision Number does not change before re-

publish, The SPF interface will assign a sub-number to

the current revision.

– A P&ID may be published as many time as necessary

to maintain a data centric interface

3/22/10

Retrieve SP-PID Data from SPF to SPI

Only the current revision of the published P&ID is

retrievable

Note! Tags that are in both SPI and SP_PID will

correlate to each other without having to identify

new Tags in SPI

This will allow SPI users to create an Instrument

index in SPI before P&ID publishing without having

data overwritten

For Tag correlation to work the Unit Number conflict

must be corrected with a “Hot Fix”

May use Macro Expansion for implied Tags

3/22/10

Workflow SP-PID from SPF in SPI

Review Action To-Do list items

If it is the first retrieve

– Run Create Instrument tags in SPI

– Run Create Line in SPI

– Run Create Piping Port 1, 2 in SPI

If it is not the first retrieve

– If New Tag

Run Create Instrument tags in SPI.

Run Create Line in SPI

Run Create Piping Port 1, 2 in SPI

– If Existing Tag

Run Update / Delete Instrument tags

in SPI

Run Update / Delete Line in SPI

3/22/10

Process SP-PID from SPF in SPI

Create command means that instrument is

not yet in SPI, when you run create it will

create instrument in SPI with new value.

Instruments already in SPI with matching

Tags will associate with SP-PID Tags

Created Instruments must be edited to

add proper Instrument Type, associate to

Loop and re-launch profiles for Spec,

Process and wiring data

3/22/10

Publish SPI data to SPF

Verify and Review data from Instrument Index

– When Instrument Index is ready to publish to

SPF, the revision needs to be assigned to the

document.

– Each time new instruments are retrieved and

created in SPI, an index must be published to

SPF with the new tags to complete the

establishment of the required relationships.

– Once the Instrument index is published, the

instrument tags on the index will be correlated

with SP PID and the necessary relationships will

be established, and Instrument will change status

to share from SPF

3/22/10

Change Management

Because P&ID’s on a project are subject to strict change management procedures,

when you implement the P&ID’s with integration, the incorporation of approved

changes must apply to the shared data as well as the P&ID drawings.

To support this work process, the P&ID’s and associated data available for retrieval

into SPI must be kept current with the project scope. This requires that the P&ID’s be

maintained in SP P&ID and published to Smart Plant Foundation as changes are

approved.

PUBLISH PUBLISH

RETREVE DO NOT

RETREVE

3/22/10

Implementation of SPEL Integration

SmartPlant Electrical Retrieves Instrument Power Requirements and Signals from SPI

and Electrical Equipment Numbers from SP-P&ID and Tray Data from SP-3D

SmartPlant Electrical Publishes Cables requirements to SP-3D and Instrument

circuiting with Electrical Signals to SPI

3/22/10

– 12 –

Implementation of SPEL Integration

SPI and SPEL already separate some of the tasks without duplicating them but there are

some that can be done in both places (i.e. cable routing)

Current integration addresses 2 main tasks:

– Management of power supply for instrument entities (cabinets, panels and externally powered

instruments)

– Management of electrical I/O signals in control systems.

– It is also possible to cross-report on SPI control loop diagram in SPEL and cross-report on SPEL

schematic in SPI when both products are installed on the same workstation.

3/22/10

June 3, 2012 – 13 –

Integrated I&E functional roles

One of the issues with the current integration is that SPI and SPEL are two applications and

not one. Mainly this is because traditionally SPI is primarily used by I&C department or

instrument or I&C section of the I&E department, while SPEL is designed to be used by

Electrical department or by the electrical section of the I&E department.

There are customers, mostly in Europe, where both functions of I&C and electrical (low

voltage) are combined in one functional role. They would like to see more similarity in SPEL

and SPI user interface, especially in

– Similar properties for the same/related items (electrical signals, device panels, etc);

– Extended representation of the SPEL tree/data in SPI

– Extended presentation of the SPI data in SPEL and similar.

The question we face is how relevant/important this is for the broad user community and

users in both applications? This will be one of the subjects of discussion at the June 3

Global TUF meeting during the joint I&E session between Instrumentation and Electrical

TUF’s

3/22/10

June 3, 2012 – 14 –

In trying to find the most optimal path for integration between the three applications we

constantly face these questions:

– Is there a need for a single common cable schedule?

– Where should such cable schedule reside?

– Is there a need for a single cable routing reporting/documentation mechanism for both I&E cables and

if so which discipline is usually responsible for it and what tool should be the master for this function?

– SPEL and SP3D have an interface as part of the SP Enterprise integration (SPE). Does it make

sense to develop separate SPI-SP3D interface using a similar interface or does it make more sense

to extend SPI-SPEL integration to cover cables and to/from locations and use SPEL as a common

cable schedule?

Cable Management for SPI & SPEL

3/22/10

SPI and SPEL Cable Management

New SmartPlant Instrumentation Cable Browser View

– Allows SPI to export the instrument cable requirements to SPEL

– SPEL can then Publish both Electrical and Instrument Cable

requirements to SP3D for Tray Loading

– Cable Tray Routing and Loading done in SP3D will Provide

Lengths and Routing Data

– The SP3D Cable Lengths and Routing is Published Back to

SPEL

– Cable Schedules can be Published from SPEL for Electrical and

Instrument Cables

or

– Instrument Cable Data may be Exported from SPEL and

Imported into SPI for Instrument Cable Schedules

3/22/10 FOOTER: EDIT THIS AND THE DATE IN THE “MASTER” >

“SLIDE MASTER” UNDER THE “INSERT” MENU.

REPLACE GREY BOX

WITH COMPANY LOGO.

EDIT THIS IN THE

“SLIDE MASTER”.

QUESTIONS

SPI - SP-P&ID - SPEL INTEGRATION