PCA Services is a commercial entity focused on industrial data interoperability. It aims to facilitate sharing of precise data between organizations through projects that apply standardized reference data. Two example projects are ILAP, which uses semantic technology to integrate lifecycle asset planning data across different software tools, and STI, which seeks to standardize definitions and formats for technical information on common equipment in the oil and gas industry. PCA Services provides a reference data library and technical platform to enable broad application of standardized data between domains and systems.

1. Industrial Data Interoperability
An introduction to who we are and what we’re here for

2. Agenda
① Introduction to PCA Services
② A project example: ILAP
③ Another project example: STI

3. Introduction to PCA Services


4. The PCA and PCA Services:
Key characteristics and differentiators
POSC Caesar Association
→ Non-profit member organization; since ’97. Independent, global
→ Standardization focus: ISO 15926 initiator, PCA RDL custodian
→ Membership activities: SIG workgroups, meetings, conferences
PCA Services
→ A new commercial legal entity; since ’14. So far Norway-located
→ Runs projects to help adopters take benefit from reference data
→ Runs/supports a Reference Data Service (based on PCA RDL)

5. The EU has identified 3 x dimensions of interop.
(from IDABC: Interoperability Framework for Pan-European eGov. Services)
Organizational Interoperability
Goals, requirements, processes,
collaboration and exchanges
Semantic Interoperability
Precise meaning, with consistent
understanding across appliances
Technical Interoperability
Linking computer sys./services,
open interfaces, data integration

6. If you only care to remember a few things
§ We are all about Industrial Data Interoperability.
And we believe in facilitating customer benefit
via broad appliance of data (with precise meaning)
§ PCA Services is a small, but qualified business
→Domain and model knowledgeable
→A collaborative environment; our standard modus
operandi is to work in quality loops or circles
→We «walk the walk»

7. © 2014 MIMOSA and PCA
LIFE CYCLE ENGINEERING
Systems
Automation
and Control
Systems
Enterprise
Business
Systems
Big Data and
Analytics
Supplier Neutral
Open Specifications
Critical
intersection
for
a
supplier-­‐neutral
solution,
enabling
multi-­‐domain
systems
interoperability

8. ISO 15926: «Industrial Automation Systems –
Integration of Life-Cycle Data for Process Plants,
including Oil and Gas Production Facilities»

9. General state of data management
§ Today, most data mgmt. takes place behind corporate walls
§ Furthermore, most data mgmt. happens inside discipline silos
→ Administrative business areas: sales, distribution, accounting, etc.
→ Engineering & production business: product design, testing, manufacturing
→ Customer side business: actual use, condition monitoring, etc.
§ When owners see demand for some data exchange, we often build
another silo, …which becomes part of a growing corporate legacy
§ Owners become systems integrators, plugging in special solutions
from different vendors, mitigating several incompatible installations

10. Logical organisation of reference data
Core
classes
Manufactured product classes
Commodity product classes
Proprietary product classes
Data
model

11. The DRIVE Method (a.k.a. GIM Process)
Implement
Verify
Enhance
Represent
Define
IT Expertise
Modeling
Expertise
Domain
Expertise

12. What does our Reference Data Services
offering consist of?
Technical Platform
– Configuration and Management
– Software (run-time environment)
– Hardware (cloud/system instances)
CONTENT
Œ ‘Wrapper’ Services
→ Everything required to
provide relevant offerings
with predictable quality
on Internet scale
 CONTENT
→ The PCA Reference Data Library
Ž Technical Platform
→ Everything required to
underpin points Œ and 
 Governance
→ Everything required to
manage above aspects as one

13. A project example: ILAP
(EPIM Integrated Lifecycle Asset Planning)
‚

14. ILAP Connected
Through Semantic technology, ILAP takes care of sending data from
one location to the other, and perform the necessary translations
Ms Project
SAP
Safran
Primavera
Project Controls
Software
SAP Description 7IFS . Other Tools

15. A ‘puzzle’ with many kinds of pieces
CoP Eni Statoil
Aibel
Owners/Operators
Contractors C.FabricomAkSo ApplyS. Reinertsen Rosenberg WP
…?...Sub-­contractors
Software tools MS-­Project
adapter vendor X
Primavera P6
adapter vendor Y
Safran
(Safran)
SAP (PM, PS)
adapter vendor Z
…?... …?... …?... …?... …?... …?... …?... …?... …?... …?...
Lundin
Standards ISO 15926 Part 13 (ILAP)

16. Another project example: STI
(EPIM Standardization Initiative)
ƒ

17. Standard equipment & datasheets:
Challenges in the industry
www.epim.no
Technical information
(LCI/DFO) for Standard
Equipment, delivered
as project specific
information to
Project A
Technical information
(LCI/DFO) for
Standard Equipment,
delivered as project
specific information
to Project B
Technical information
(LCI/DFO) for Standard
Equipment, delivered as
project specific
information to
Project …X
Equipment Types representing Standard Equipment:
Have not been clearly defined in the industry
Formats and standards: Have not been clearly defined
for existing industry hubs for Standard Equipment
Attributes (mainly datasheets) for each Equipment Type, representing Standard
Equipment: Have not been clearly defined in the industry
Each project delivery
followed up by
Operations and
Maintenance during
the installation
lifecycle
Facility I
Each project delivery
followed up by
Operations and
Maintenance during
the installation
lifecycle
Facility II
Each project delivery
followed up by
Operations and
Maintenance during
the installation
lifecycle
Facility …Y

18. – Thank you!
We would love to hear from you! Please reach us
via @dataneering (Twitter), info@posccaesar.com or by
telephone, e.g. (+47) 90 17 37 97 (André Torkveen)