Upload
buingoc
View
259
Download
2
Embed Size (px)
Citation preview
FLUOR
SmartPlant ©
Implementation Team
By John Dressel
Integration Standards for SmartPlant Instrumentation
Copyright © 2017 Fluor Corporation all rights reserved
2
Integration Standards for SPI Introduction
In June 2017, Intergraph was officially rebranded as Hexagon PPM, embracing a new brand and a honed vision for enabling the smart digital industrial facility and extending its expertise to truly leverage the depth and breadth of Hexagon’s innovations and technological capabilities.
As part of the rebranding, several new products and initiatives were introduced:
– A new commitment to support Data Centric Engineering Environments
– The introduction of the Smart Digital Asset Collaboration Module
– The introduction of the SmartPlant Enterprise for Owner Operators
– The addition APIs for to the SmartPlant Enterprise information interoperability
“This commitment provides for Hexagon PPM Intergraph’s web-based Smart solutions to simplify how deliverables and information is made available to the right stakeholders - securely, anywhere, anytime, on any device”
To implement these initiatives Hexagon PPM announced the support and adoption of international standards including ISO 15926, CFIHOS, and OData
3
Integration Standards for SPI - Agenda
Issues addressed by applying Integration Standards
Basic Mapping Fundamentals and Methods for data integration
ISO 15926-1 Overview and Fundamental Principles and Parts
ISO 15926-2 Data Model Mapping to a Common Data Dictionary
ISO 15926-4,5,6 Reference Data and Topology for Specific Industries
ISO 15926-7 Template Methodology for Complex Data Mapping
ISO 15926-8 Ontology Web Language Implementation (iRING)
IEC 62424 CAEX Standards Data exchange between P&ID and CAE tools
NAMUR / NE 100 Interface Data Definition for vendor data exchange
PIP DMDIM001 Instrumentation Metadata Requirements Specification
CFIHOS - Capital Facilities Information Hand-Over Specification
ODATA APIs - Open Data Protocol (OData) for building APIs
Hexagon PPM - Support and adoption of international standards
Multiple Standard Associations across several continents creates confusion
Different Languages and Measurement Standards cause data inconsistencies
Different Database Dictionaries and Architectures require unique mapping
Developing Application Programing Interfaces (API) required for integration
Information stored as Notes, in UDFs or Narratives will not integrate easily
AV\filename.ppt 4
Issues addressed by Integration Standards
Typical Application Data Map
AV\filename.ppt 5
Mapping Data between applications requirements
– Knowledge of all data dictionary structures
– A one to one relationship between key data fields
– Methods for handling null or empty data fields
– Custom data maps for each combination of data dictionaries
Common Data Dictionary Data Map
AV\filename.ppt 6
Mapping Method using a Common Data Dictionary or Neutral File Format
– Only knowledge of common data dictionary and parent data structures are required
– Flexible in that Hierarches, Key data fields, and relationships may be defined
– Reference data may be added to the Common Data Dictionary as needed
– This Common Dictionary methodology is the basis for the ISO 15926 standard
AV\filename.ppt 7
ISO 15926-1 International Standard
ISO 15926 Industrial automation systems and integration - Integration of life-cycle data for process plants including oil and gas production facilities
– Part 1 – Introduction, Purpose is to facilitate integration of data
– Part 2 - Data Model, a generic model that can support all disciplines, supply chain company types and life cycle stages
– Parts 3 – 6 - Reference Data, the terms used within facilities for the process industry.
– Part 7 – 9 - Implementation, Methods for the integration of distributed systems, defining an implementation architecture that is based on the W3C Recommendations for the Semantic Web
The Intergraph SmartPlant Foundation Data Model uses the Common Dictionary basis of ISO 15926 Part 2
AV\filename.ppt 8
ISO 15926-2 International Standard Data Model
ISO 15926-2 Industrial automation systems and integration Data Model. a generic 4D model that can support all disciplines
The definitions in part 2 are not specific to any industry, but is sufficient to enable all domain specific entities to be described
The generic model has 201 entity types in one Hierarchy with THING at the top
This representation is specified by a generic, conceptual data model designed to be used in conjunction with reference data: standard instances that represent information common to a number of users, process plants, or both
The use and definition of reference data for process plants is the subject of Parts 3, 4, 5 and 6 of ISO 15926
Thing
Possible
Individual Abstract
Object
Class
Relationship
Multidimentional
Object
Template Class of
Relationship
AV\filename.ppt 9
ISO 15926 International Standard Analogy
The Parts of ISO 15926 function similar to publishing a book:
AV\filename.ppt 10
ISO 15926 Reference Data Architecture
A Typical ISO 15926 data model hierarchy
11
ISO 15926 Compliance
Data integration is more successful when ambiguity is eliminated
Am
big
uit
y S
cale
Greatest Compliance
Least Compliance
Least Ambiguity
Greatest Ambiguity
Full Template Implementation
Interoperability Template Defined
Neutral File Format (CSV)
Data Dictionary Level (XML)
ISO 15926 Part 8 - OWL / RDL - iRING
ISO 15926 Part 7 – Template Data
ISO 15926 Part 6 – Reference Data
ISO 15926 Part 4 – Reference Data
ISO 15926 Part 2 – Data Model
Initial Reference Data Defined
Methodology Reference Data
ISO 15926 Application Interoperability
ISO 15926 Realtime Interoperability Network Grid (iRING) is the global information interoperability solution architecture based for ISO 15926 Part 8 Reference Data Standard that enables high fidelity information interoperability
12
Developed by :
– Fiatech,
– POSC
– Caesar,
– ISO,
– USP
Goals: – Lower overall project costs
– Decreased time to start
– Improved plant safety
– Improved maintenance efficiency
– Reduced planned and unplanned downtime
IEC 62424 CAEX Standards
Defines the exchange of process control
engineering data using a data transfer
language Computer Aided Engineering
eXchange (CAEX)
CAEX represents meta data in a
hierarchal data model of System, Role,
Interface and Instance.
The Intergraph SmartPlant Suite uses a
hierarchal data model (P-A-U) similar to
CAEX for SmartPlant P&ID integration
IEC 62424 specifies how process control engineering requests are
represented in a P&ID for automatic transferring data between P&ID
and CAE tools to avoid misinterpretation of graphical P&ID symbols
IEC 62424 CAEX Standards
Updated definitions and new definitions
Identification replaced with reference
designation
Updated categories and process
functions
CAEX version 3.0, introduction
Nested interfaces
life cycle meta information
Separate Attribute library
Updated examples
Updated electronic data model
New extended attribute library
IEC 62424:2016 replaces the first edition published in 2008
The main changes and extensions are:
AV\filename.ppt 15
NAMUR / Prolist Standards
NAMUR / Prolist NE-100 Interface Data Definition
PROLIST NE-100 for engineering processes to build and maintain chemical plants using Lists of Properties (LOP) for data exchange
The provision of standardized characteristics and lists of characteristics through PROLIST, including the data model and its implementation in the PROLIST database,
The international standardization process has been initiated through a work proposal to IEC and is being supported by PROLIST and its members,
Leading providers of business process solutions, such as SAP and Intergraph, are currently implementing the technology,
NAMUR / Prolist Standards
NE-100 for engineering processes to build and maintain chemical plants using Lists of Properties (LOP) for data exchange
– NE-100 Version 3.1 (2009) contains 105 LOP for: • Measuring instruments (51)
• Interface Devices (37)
• Actuators (17)
eCl@ss Data Standard ISO 15926 Data Standard
17
NAMUR / Prolist Standards
The types of lists of properties: – Device List of Properties (DLOP),
describing the technical features of a device
– Operating List of Properties (OLOP), describing the operating aspects, i.e. ambient conditions
– Administrative List of Properties (ALOP), describing all the information needed for data exchange
– Commercial List of Properties (CLOP), describing all the applicable commercial data
NE 100 uses the eCl@ss Standardized Reference Data Library as its description scheme and can be mapped to ISO 15926
eCl@ss has established itself
as the worldwide Reference
Data standard for the
manufacturing industries
AV\filename.ppt 18
PIP DMDIM001
PIP DMDIM001 Instrumentation Metadata Requirements
This Practice provides a data modeling framework and defined field identifiers for establishing structured electronic information for process instruments.
This Practice provides standardized instrumentation data element labels and associated field identifiers based on common usage, such that instrumentation data can be readily uploaded into various electronic databases.
This Practice promotes accurate, timely input of instrument requirements as instrumentation is specified for purchase
AV\filename.ppt 19
PIP DMDIM001
Leveraging electronic data management capabilities, the standardized data can be mapped to smart design and maintenance management database systems for ready retrieval and visualization of instrumentation data
This Practice enables single source input which provides the following benefits:
– Eliminates duplication of effort for operations and project teams
– Reduces the cycle time for operations readiness during equipment commissioning
– Enhances the use of instrument information in daily facility operations, maintenance, and other administration uses
AV\filename.ppt 20
PIP DMDIM001
PIP DMDIM001 Instrument Design Tool Configuration (IDTC) for gathering industry input to facilitate updating the Standard
IDTC Purpose:
– Facilitate Data Sharing
– Create Generic Practice
– Define a ‘Harmonized’ Mapping
– Provide Autonomy to Each Data Contributor
– Review industry standards (e.g., ISA, OSI, SPI, ISO, NE-100 Etc...) and incorporate instrument datasheets.
– Focus on data elements for flow, level, pressure, and temperature instruments
Houston SPI LTUF is conducting a IDTC Special Interest Group
AV\filename.ppt
21
CFIHOS Standard Specification
Capital Facilities Information Handover Specification (CFIHOS)
Purpose: Create a Handover (HO) Specification for operators, contractors, suppliers and equipment manufacturers to standardize the specification of information handover requirements for a project
Deliverables from the CFIHOS stakeholders:
– CFIHOS for “process industry”, Specification document with rules and principles for information handover in data format.
– CFIHOS RDL referencing ISO 15926-4 as common language for the stakeholders working with the CFIHOS specification.
– Tools by commercial software suppliers to adopt the CFIHOS specification
– Guidance document for all stakeholders how to implement CFIHOS
Spec Template
Test RDL
O/O O/O
EPC
AV\filename.ppt 22
CFIHOS Standard Specification
Today the set of documentation for CFIHOS is much more than the actual specification for tag classes, types and properties that enable a plant breakdown structure and document types with properties creating:
– Improved regulatory compliance
– Improved efficiency
– Standardized information requirements
– Assistance in achieving License to Operate
The inclusion of the Reference Data Library enables Data that is published via ISO 15926 to be accessed easily by a customer developed API for integration
Note: The CFIHOS ISO 15926 part 10X standard will be initiated end of 2017 Q-4
AV\filename.ppt 23
Building APIs with OData Resources
OData (Open Data Protocol) is an ISO/IEC approved, OASIS standard that defines a set of practices for building and consuming RESTful APIs.
Representational State Transfer (REST) or RESTful web services provides interoperability between computer systems on the Internet.
OData helps you focus on your business logic while building RESTful APIs without having to worry about the various approaches to define request and response headers, status codes, HTTP methods, URL conventions, media types, payload formats, query options, etc.
OData also provides guidance for tracking changes, defining functions/actions for reusable procedures, and sending asynchronous/batch requests
The OData metadata, a machine-readable description of the data model of the APIs, enables the creation of powerful generic client proxies and tools
AV\filename.ppt 24
Hexagon PPM Standards Adoptions
Hexagon PPM support and adoption of international standards including ISO 15926, CFIHOS, and OData
Hexagon PPM, as a pioneer in the field of data-centric engineering design and information management, contributes actively to the development and adoption of international standards that promote the efficient exchange and reuse of facility information.
POSC/Caesar, ISO 15926, and Fiatech Hexagon PPM has been an active member of POSC/Caesar and delivered the first ever POSC/Caesar data warehouse in 1997. POSC/Caesar initiated the development of the ISO 15926 standard. SmartPlant Foundation data model has shared a common basis with ISO 15926 Part 2
CFIHOS (Capital Facilities Information Hand-Over Specification) for process industries Whilst the CFIHOS standard is still under development, Hexagon PPM considers that it provides a good pragmatic basis for defining standard information requirements for life-cycle asset management using ISO 15926 . We are adopting this standard within our new Smart Digital Asset portfolio of products
OData APIs SmartPlant Foundation and the solutions built on this, such as SmartPlant Enterprise for Owner Operators, already benefit a wide range of read-write OData APIs. Over the coming years, our Smart design tools will support more OData APIs.
AV\filename.ppt 25
What This Means For SPI
With Hexagon PPM and Manufactures adoption of international standards comes the opportunity for better integration in future versions of SPI
Mapping SPI data dictionary to ISO 15926 will allow:
– More SPI data to be passed through SPF to other SP applications
– Development of more SPI APIs for Integration to Vendor Applications
Adoption of IEC 62424 allows better integration between P&IDs and SPI
Mapping the NAMUR NE100 Lists of Properties to ISO 15926 will allow:
– Using ISO 15926 templates for SPI Data Exchange to and from eCl@ss
– Development of more SPI APIs for Integration to Vendor Applications
Adoption of PIP DMDIM001 for future SPI Spec Module will allow:
– Standardized data dictionary across all SPI spec sheets forms
– Development of more SPI APIs for Integration to Vendor Applications
Adoption of CFIHOS allows SPI more consistent data deliverables to EPC Clients and Owner Operators
26
Integration Standards for SPI
“I've upped my standards.
Now, up yours.” ~ Pat Paulsen