04.09.13: edit or delete this in the “master” > “slide ... integration.pdf · intools is a...

Insert Company Name or LOGO Here

04.09.13: EDIT OR DELETE THIS IN THE “MASTER” > “SLIDE MASTER” UNDER THE “INSERT” MENU.


SmartPlant Instrumentation Integration Perspective John Dressel, Fluor, Principal Application Specialist

Insert Company Name or LOGO Here Value Proposition

• The Integration of Data with SmartPlant Instrumentation is inconsistent among all of the different users and systems that require data centricity with the SPI DBMS

Business Problem

• We must find common elements of integration and realign the SmartPlant Instrumentation interfaces to take advantage of the power data centricity

Solution

• By leveraging the SmartPlant Instrumentation interfaces we will be able to enter data one time and move data between applications without excessive data manipulation

Benefits

• By mitigating data integration issues with SmartPlant Instrumentation and other software solutions we will improve the ability of users to leverage data centricity in the future

Anticipated Long-Term Benefits (optional)

• Fulfilling a vision of global Engineering automation data integration with SmartPlant Instrumentation for all types of data management and software systems

Future Plans/Strategy or Summary Statement

3

Insert Company Name or LOGO Here The Beginning

In the beginning there was INtools and the known universe of Control Systems Automation revolved around it

This was good - but INtools only had limited interfaces and no integration to fulfill our Vision of a Data Centric environment

Insert Company Name or LOGO Here The Vision

We looked into the INtools crystal ball and saw a Vision for the Future of Engineering Automation – The Import / Export capabilities of INtools

would give us the ability to interface with other software We could Import data into INtools to

complement the engineering data We could Export data to Excel and dBase

for use on other programs – But we still didn’t have real integration with

other software or applications

Insert Company Name or LOGO Here INtools capabilities

Excerpts from a 1998 INtools Presentation INtools is a Microsoft Windows based Application and uses the standard

Windows Graphical User Interface. INtools uses ODBC compliant databases such as Oracle, MS-SQL and Sybase. INtools is more than an Engineering tool. It is also is the plant operations and

maintenance software used by Owner Operator companies. INtools has become the de facto standard for Control Systems Automation. INtools is being integrated with other Engineering Tools to create a data centric

engineering environment.. INtools is integrated to other applications, such as Fisher Firstview valve sizing,

AutoCAD and Microsoft CAD systems. INtools is state of the art and supports new instrument concepts such as

Communications, Fieldbus and ISA compliant datasheets.

Insert Company Name or LOGO Here The Vision Grows

When Intergraph purchased INtools in 1999 the Vision of a truly integrated Engineering Environment grew – Intergraph already had a development plan for

creating a SmartPlant Integrated suite of products

– They quickly included INtools in the SmartPlant Enterprise and SmartPlant Instrumentation – Powered by INtools was born

Now we had a promise for the future Integration of Engineering Automation

Insert Company Name or LOGO Here The Vision Grows

With Interfaces into SmartPlant P&ID and SmartPlant Electrical we saw the possibilities of other interfaces for EPC, Owner and Vendor Data. A vision of integration for SmartPlant Instrumentation became closer

Insert Company Name or LOGO Here The SmartPlant Integration Manager

With the introduction of the SmartPlant Foundation a framework for real integration of SmartPlant Instrumentation becomes available


On closer inspection we discover that the Integration for SmartPlant Instrumentation only includes a few specific data sets that can be published and retrieved for other SmartPlant Applications

Insert Company Name or LOGO Here The SmartPlant P&ID Integration with SPI

Currently the P&ID Data published to the Foundation has serious limitations for integration with SPI Instrumentation around dissimilar instrument types

Insert Company Name or LOGO Here The SmartPlant Electrical Integration with SPI

Currently the SPEL Data published to the Foundation is limited to SPI Power and Signal correlation but cable data must manually manipulated

Insert Company Name or LOGO Here The SmartPlant 3D Integration with SPI

Currently the SmartPlant 3D can only retrieve SPI Dimensional Data for Piping for in line instruments from SP Foundation


As the SmartPlant Foundation integration management matures the number and quality of integrated data sets will improve including EPC, Owner Operator and Instrument Vendor data interfaces as well as other SmartPlant applications


We have the capability of creating SmartPlant Foundation adaptors to interface EPC or Owner Operator software applications into the share base developing another layer of integration

EPC and O/O Data Integration


Many EPC and O/O companies that use SmartPlant Instrumentation have other applications to manage and maintain additional instrument data

Proper Integration requires a good understanding of both the source and destination database structures and formatting for accurate data mapping

Unfortunately most of them work around SPI by importing data directly into the DBMS or Import Module without regard to SPI data relationships



Integrating Engineering Data Issues – Tendency of EPCs to work outside of SPI then

try to push data in using the Import Module – Importing and Exporting Data over remote

servers in a work share environment – Source data formatting doesn’t match the SPI

database requirements – Overuse of user defined fields due to

unfamiliarity with the SPI database structure Integrating Operations Data Issues

– Lack of experienced Database Administrators to maintain the SPI data integration

– Trying to do too much in SPI by not defining the proper data ownership (e.g. Alarms in DCS)



There are a myriad of Vendor and System interfaces to SmartPlant Instrumentation that are developed but most are not used well

Vendor Data Integration


Integrating Vendor Data – Consistent Spec Sheet Generation for Sizing and

Selection Control Valves and Instruments – SPI integration for Control System wiring I/O – SPI integration for DCS Configuration data – SPI integration for Plant Maintenance and

Operation Systems Vendor Integration Challenges

– Using SmartPlant Instrumentation in As-Built, work-sharing, multi-contractor environments

– Lack of integration standards and consistent methods of data definition and transfer

– Problems with underutilization of SmartPlant Instrumentation Vendor Integration

Vendor Data Integration

Insert Company Name or LOGO Here SmartPlant Instrumentation Vendor Interfaces

Index

TAG NUMBER Instrument Type

PROFILE

Dimensions

line data

Service

DDP

Spec Sheets

Spec Data

Process

Sizing Data

Wiring

I/O Loading

Field

DCS

SMARTLOOP SPEC SHEET

RULE BASE

3D MODEL SPEC SHEETS CONSTRUCTION DRAWINGS

Control Valve Sizing & Selection

Instrument Sizing & Selection

DCS I/O CARD LIBRARY

DCS CONFIGURATION

PLANT OPERATIONS


Users build Instrument Tags and input process, sizing and selection data in SPI using automation functions

Create Instrument Datasheets in SPI – Export to Vendor Sizing and Selection Software – Use Vendor sizing and selection of instruments – Import Manufacturer and Model Numbers into

SPI From Vendor Selection Software – Issue Purchase Orders and Construction

Hookup documents from SPI This Functionality should work the same for all

Vendors across all Instrument types

SmartPlant Instrumentation Vendor Interfaces


Users create the Field Wiring Network with I/O Loading in SPI – Import Vendor I/O Card Libraries into SPI – Connect devices and cables in SPI using the

SPI Wiring Explorer and Modules – Export SPI I/O data and DCS Configuration

data to Vendor Configuration Programs Operation and Maintenance Owner Operator

Functionality for Control Systems – Use the Vendor Configuration software and SPI

Wiring data to Configure and Maintain Process Control System

This Functionality should work the same for all Vendors across all Control System Types

SmartPlant DCS Vendor Interfaces

Insert Company Name or LOGO Here Issues with Vendor interfaces and Integration

When using SPI in As-Built, work-sharing or multi-contractor environment – The SPI Database can have limited access - adding complexity to the use of interfaces – Some SPI Functions do not work in the “EPC” and “Owner / Operator” As-Built Mode – Inconsistency of SPI user capabilities of different pillars on a work share project

Problems with underutilization of SPI Vendor Interfaces – Remove the required special license key for all DCS interfaces and make the Interfaces

part of the standard available add-ons for all licenses – Develop a standard DCS data exchange library that will work across multiple DCS

Vendors to import and export SPI data – The I/O Card and wiring device imports need to be separated from the DCS Interface – Standardize the interfaces and data transfer so interfaces work the same from vendor

to vendor makes user training and adding vendors simpler – The magnitude of data fields on Spec forms are confusing use more man hours to

properly populate Specs, Identify required fields The Vendors have had a lack of adherence to an Interoperability Standards when

developing a SPI Interfaces


Interoperability Standards Vision

While many of the Interface Standards work together and even complement each other, Others contradict or duplicate data transfer definitions

Whatever standards the Intergraph SmartPlant Foundation integration component of SmartPlant Enterprise adopt – will probably become the de-facto standard for other interfaces

The demand for Vendor Interfaces and Integration into Engineering Automation tools is growing and Intergraph is well positioned to take the lead in furnishing well designed and functional interfaces for some time to come

Insert Company Name or LOGO Here Interoperability Standards

Intergraph, Fluor, Emerson, Bechtel and Other companies are working together to utilize international data interface standards for interoperability

Data Interoperability, Interface and Integration STANDARDS WARS – NAMUR / Prolist NE-100 Interface Data Definition Interface Standard for engineering

processes to build and maintain chemical plants – ISO 15926 is a Cross Product Data Mapping Integration Standard for data exchange

developments in the oil and gas industries

Additional Standards that may apply – eCl@ss has established a Product, Services and Materials Naming Code Standard in many

European market places and is integrating the German classifications (ETIM, Proficlass, …) – PIDX (Petroleum Industry Data Exchange) is the eCommerce Standard for using XML Data

Integration as a basis for procurement processes and data exchanges in oil and gas – ECCMA – (Electronic Commerce Code Management Association) developed a standard

descriptive language for Data Exchange Compliance Requirements and cataloging individuals, organizations, locations, goods and services


NAMUR / PROLIST NE-100 Standard

PROLIST NE-100 for engineering processes to build and maintain chemical plants using Lists of Properties (LOP) for data exchange – NE-100 Version 3.2 contains 107 LOP for:

Sensor Types (51) Interface Devices (37) Actuator Types (19) DCS/PLC I/O Types are in Development

XML Interface Data Definition Interface Standard

Insert Company Name or LOGO Here ISO 15926 Integration Standard

ISO 15926 is the basis for many developments in oil and gas data exchange – Part 1 - Introduction, information concerning engineering, construction and operation

of production facilities is created, used and modified by many different organizations throughout a facility's lifetime. The purpose of ISO 15926 is to facilitate integration of data to support the lifecycle activities and processes of production facilities.

– Part 2 - Data Model. a generic 4D model that can support all disciplines, supply chain company types and life cycle stages, regarding information about functional requirements, physical solutions, types of objects and individual objects as well as activities.

– Parts 4,5,6 - Reference Data, the terms used within facilities for the process industry. – Part 7 - Implementation methods for the integration of distributed systems, defining

an implementation architecture that is based on the W3C Recommendations for the Semantic Web.

SmartPlant Foundation is the information management and integration component of SmartPlant Enterprise. The underlying SmartPlant Foundation data model shares a common basis with ISO 15926 Part 2.

Cross Product Data Mapping Integration Standard

Insert Company Name or LOGO Here SmartPlant Foundation Vendor Interfaces

The addition of ISO15926 and NE-100 to SmartPlant Foundation will provide for the creation of numerous Standard Interfaces to Integrate Vendor Sizing, Selection and Purchasing Data into SPI

Insert Company Name or LOGO Here Interoperability Beyond SmartPlant

Vendor Application Interfaces may open up new functionality to SmartPlant Instrumentation – Integrated Vendor catalogs for selection, dimensioning

and connection information – Supply chain applications for electronic purchasing and

material management – Electronic pricing applications for Bidding and

Estimating Utility Application Interfaces may add additional

functionality to SmartPlant Instrumentation – Data auditing and progress reporting applications – Integration programs for Safety and Fire & Gas

Systems – Special applications for other business sectors such as

Nuclear, pharmaceutical, mining and manufacturing

Insert Company Name or LOGO Here Interoperability Beyond SmartPlant

Adding the ability to easily create adaptors for User Interface and Interoperability Programs will allow EPC, Owner Operator, Vendors and System programmers to Integrate through SmartPlant Foundation

Insert Company Name or LOGO Here SmartPlant Interoperability Future Vision

With Global Work Sharing and Joint Venture projects the need for secure access to applications and data from any network device in any location in the world is becoming an important part of Interoperability

More and more companies are looking at Cloud Computing as a mechanism to simplify the delivery method of IT services

The unique data sharing capabilities of SmartPlant Foundation lends itself to web based interoperability


Recoding the SmartPlant TEF WEB adaptors in AJAX or other web based technology will allow cloud Integration to a SmartPlant Foundation Integration and Info management cloud server

SmartPlant Interoperability Future Vision


With the advent of Cloud Computing, Secure Web Centers, Interoperability Standards and the SmartPlant Enterprise the Vision of Global Engineering Automation Data Integration with SmartPlant Instrumentation is becoming a reality

SmartPlant Interoperability Future Vision


04.09.13: EDIT OR DELETE THIS IN THE “MASTER” > “SLIDE MASTER” UNDER THE “INSERT” MENU.

04.09.13: edit or delete this in the “master” > “slide ... integration.pdf · intools is a...

Documents