spi interfaces & integrationspi-ltuf.org/gtuf11/10 future spi integration.pdfglobal smartplant...

SPI Interfaces & Integration

“the future is not what it used to be”

John DresselSmartPlant Instrumentation Application Specialist

Sunday, June 5. 2011 – Orlando Fl.

Global SmartPlant Instrumentation Users Forum 2011

The Beginning

In the beginning there was INtools and the known universe of Control Systems Engineering Automation revolved around itThis was good - but INtools only had limited interfaces and no integration to fulfill our Vision of a Data Centric environment


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

We Wanted More!


INtools capabilities

Excerpts from a 1998 INtools PresentationINtools 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.

We Wanted More!


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

We Wanted More!


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


The SmartPlant Integration Manager

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


The SmartPlant Integration Manager

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


The SmartPlant P&ID Integration with SPI

Currently the P&ID Data published to the Foundation can only be correlated with the SPI Instrument Index and SPEL I/O Equipment List


The SmartPlant Electrical Integration with SPI

Currently the SPEL Data published to the Foundation can only be correlated with the SPI Power and Cabinets data and SP3D cable data


The SmartPlant 3D Integration with SPI

Currently the SmartPlant 3D can only retrieve SPI DDP Data Sheets through the SmartPlant Foundation Share Base


The Future SmartPlant Integration Manager

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

We Want More!


SmartPlant Foundation

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


There are a myriad of Vendor and System interfaces to SmartPlantInstrumentation that are developed but we still lack true integration

Vendor Data Integration


The Vision of Vendor 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 SystemsVendor 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


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

SMARTLOOPSPEC 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


Control Valve Vendor Integration Functionality

Build Control Valve Tags and input process sizing and selection data into SPI using automation functions Create Control Valve Datasheets in SPI– Use SPI or Vendor valve sizing calculations – Use Vendor Valve Selection software– Import Manufacturer and Model Numbers from

Vendor Selection Software to SPI– Export DDP data to SP3D model

This Functionality should work the same for all Vendors and all Control Valve types We Want More!


Instrument Vendor Integration Functionality

Build all 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

We Want More!


Control Systems Vendor Integration Functionality

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 DCS I/O data to DCS Configuration

data to Vendor Configuration ProgramsOperation 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

We Want More!


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 in the capabilities of different pillars on a work share project

Suggestions to correct underutilization of SPI Vendor Interfaces– Remove the required special license key for each DCS interfaces and make all

Interfaces part of the standard 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 Library import needs 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 simpler– The magnitude of data fields on Spec forms are confusing use more man hours to

properly populate SpecsUse Interoperability Integration Standards when developing SPI Interfaces


Interoperability Standards Vision

While many of the Interface Standards work together and even complement each other, Others contradict or duplicate data transfer definitionsWhatever standards the Intergraph SmartPlant Foundation integration component of SmartPlant Enterprise adopt – will probably become the de-facto standard for other interfacesThe 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

We Want More!


Interoperability Standards

The Process Engineering communities need to further coordinate efforts in areas critical to lifecycle information Interface and IntegrationCompanies like Intergraph, Fluor, Emerson and Bechtel 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


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 Intergraph SmartPlant Foundation data model shares a common basis with ISO 15926 Part 2.

Cross Product Data Mapping Integration Standard


SmartPlant Foundation Vendor Interfaces

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


SmartPlant Foundation System Interfaces

The addition of ISO15926 and NE-100 to SmartPlant Foundation will also provide for the creation of numerous System Interfacesfor Project Management and Asset Management applications


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

We Want More!


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


SmartPlant Interoperability Future Vision

With Global Work Sharing and Joint Venture projects the need for secure web based access to applications and data from any network device and any location in the world is becoming an important part of InteroperabilityMore and more companies are looking at Cloud Computing as a mechanism to simplify the delivery method of IT services.We Want More!



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



With the advent of Cloud Computing, Mobile Access, Web Security, Refined Standards and new SmartPlant Applications the Future Vision of Engineering Automation Data Integration with SmartPlant Instrumentation looks very promising


Questions and Comments

What is the Future Vision of

SmartPlant Instrumentation

Integration?

spi interfaces & integrationspi-ltuf.org/gtuf11/10 future spi integration.pdfglobal smartplant...

Documents