Global Operation Data Integration - GODI...Reference Semantic Model standard Operator IBM C&P Model...
Transcript of Global Operation Data Integration - GODI...Reference Semantic Model standard Operator IBM C&P Model...
Classification: Internal (Restricted Distribution) Status: Draft
Global Operation Data Integration - GODI
Oskar FredagsvikDiscipline Advisor IO, StatoilHydro TNE PPT POMM
2
Our ambitions with IO
All fields and facilities are IO compliant
Develop a global competence network leveraging IO
Remove boundaries with IO
Realize the potential from R&D projects in our operations
3
Integrated OperationsIO Compliance in Production Optimisation
ICT Solutions
Refining plant data into Knowledge
IO Compliance
Common working practices and toolsGoverning documents
and work processes
Skills and competences
4
DOFF
5
New web based data- and communication standards …
Vendor
Vendor
Common XML schemasDrilling/wells, Reservoir and Production,
Operation and Maintenance
StatoilHydro
Semantic webIntelligent data
ISO15926O&G ontologies
Smart Web Services
OLF
6
OMM in StatoilHydro
like ISO15926 & ISA
Targeted by IMS project
Drilling & completion Reservoir & productionmanagement
Operation & maintenance
Corporate processes & applications(standardized)
Plant specific procedures & applications
(varies significantly from plant to plant)
Local & globaloperation centres
Real-time IT integration solution
• Common access to information
• Service-oriented• Based on key
industry standards
Drilling & completion Reservoir & productionmanagement
Operation & maintenance
Corporate processes & applications(standardized)
Plant specific procedures & applications
(varies significantly from plant to plant)
Local & globaloperation centres
• Common access to information
• Service-oriented• Based on key
industry standards GODI – Global Operation Data Integration
7
Data integration in E&P
Data integration across E&P creates an oil & gas
ontology2): From software integration to interoperability
Sharing today
Software integration
Sharing todaySharing todaySharing today
Software integration Interoperability
Sharing tomorrow
ISO
159
26 O
il an
d G
as O
ntol
ogy
Interoperability
Sharing tomorrow
Interoperability
Sharing tomorrowSharing tomorrowSharing tomorrow
ISO
159
26 O
il an
d G
as O
ntol
ogy
ISO 15926 is an instrument for data integration that provides interoperability1
1)Interoperability = The ability of two or more systems or components to exchange information and to use the information that has been exchanged.
2)Ontology = A hierarchical data structure containing concepts, relationships, properties and rules for a specific domain
8
D&V map
Global Operation
Data Integration
GODIProof of Concept 07
Full scale pilot 08
Rollout 09-
Information
Visualisation
•Roles
•Level
Tools
Applications•CM-rotating equip.•Fiscal Meetering•Advanced Wells•F&G Detectors•Transmitters•Valves
Collaborationtools
Data Integration
Plant Historian
Rotating
Meetering
SAS
Real Time
•Work Order
•Risk management
•Performancemanagement
•Plant Integrity
ERP systemDocumentationTag informationSynergi
Tools•Statoil@work
•Cell Phone
•Suppliers
•PDA
IO-g2
Global O
perationPTEC Production
opimization
AN
ALY
SIS
ofre
al ti
me
data
ba
sed
onC
ritic
ality
, Vol
ume,
..
CBM
CM
Plant 1-n
9Building blocks for the C&P SOA is built with standards and industry participationRSM Team• MIMOSA- Alan Johnson, Ken Beaver
• OAGi – Dave Connelly
• WBF – Dave Emerson
• ISA 88 – Dennis Brandl
• ISA 95 – Keith Unger
• OLF/PCA – Tore Langeland, Magne Valen-Sendstad, Nils Sandsmark
• OSIsoft – Jack Aude
• DNV - Henrik Smith-Meyer
• DOW – Russ Dickinson
• SISCO – Herb Falk
• IBM – Lorenzo Childress, Jon Siudut, Karthik Seetharaman, Jerry Kopecky
• OPC – Vishwanath Narayan
RSM Team Objectives/Milestones• Objectives
– Advance the modeling work
– Insure compliance with the participating standards
• Milestones
– Identify the appropriate standards community to own the RSM
– Initial release of the RSM in the October timeframe
10OAGIS
Purdue’s reference model for manufacturing
5 Enterprise Network
4 Site Business Planning
Demilitarized ZoneShared Access
SIL Regime
3 Manufacturing Operations
1 Process Control
0 Equipment
Plant Floor Area
2 Automation/Connectivity
ISA S95 (4,3)
Standard forcommunication betweenERP Level and Manufacturingoperation MES OAGIS:Standard for messageexchange in S95
ISA S88 (0,1,2)
Standard forbatch control describes how the floor equipment willcarry out the work of creating products
MIMOSAStandard through witch equipmentcan communicate about its statusand need for maintenance
PLC, DCS software that guides machinery
SCADA, scheduled tasks, Keeptrack of the DCS. Historian (IMS),HMI
MES, give data to ERP, Planningquality management, maintenance
Equipment
ERP System, SAP, Master, vedlikeholdsregimer, planer
11
Industrial ITUpstream
4-20 mA / HART I/O module
DP/PA linkDP/PA coupler
PRO
FIBU
S PA
SIPART PS
SITRANS F
SITRANS P
PRO
FIBU
S DP
Field devices
DistributedI/O
IndustrialEthernet
PRO
FIBU
S DPController
Ex
Office Ethernet
Office NetworkOnshore
Internet
SOIL
SAP
IP21
STID
PIM
Access@
Plant
Access@
Plant
GODIRTV/IFM (NAVIPRO)
TKTT
Access@Plant
HMISISSAS
IMSElectro Lab
SOLStatoil@Plant
Weather
@WorkSAPIMSSTIDPIM
Connect ITRemote Access
Company specific applications+ access to
StatoilHydro applicationsApplication
Projects
12
GODI process forward Evaluation
Process
PILOT TAIL F0B
GODI Strategy Procurement Product
Y
Ni
Pilots in production
Plan B
•Procurement
•Operation
•Success criterias
•Interface projects and R&D
Replace pilots
•Vendors
• Evaluation criterias
• Procurement
• Plan
• Techn. Development Roll Out
Q1.09Q3.08
13
StatoilHydro F0B / GODI: Logical Security Architecture
•AspenTechIP.21
IIF
ModelAware
OPC Client
Adapter
OPC Tools
•SAP PM
JMS/IPJMS/IP
•OSIsoft PI
•EC/Prosti
OPCModelAware
OPC ServerAdapter
ABBApp
SOAP/HTTP
MorningMeeting
OPC
IIF Workbench
HTML/HTTP
REST/HTTP
ModelAwareRDBMSAdapter
IMSFacility 1
Prod AcctFacility 1
SQL
Asset MgmtFacility 1
HSEFacility 1
Weather
BAPIWS
WS
XML/HTTPGODI
14
Reference Sem
antic M
odel
PRIMARYO&M
APPLICATIONS &
INFORMATION REPOSITORIES
Reference
Services ArchitectureR
eference IntegrationArchitecture
Mobile ClientServicesApplication Services
Portal Services
User dashboards
Model + P&IDworkbench
FieldOperator
UI
EquipmentMonitoring
Service
New compositeapp
Assetmanagement
DistributedControlSystem
Realtimedata
historian
Realtimedata
historian
ProcessAnalysis
OPC/DA-HDAOPC/UA
SOAP/HTTPJMS/MQ
SOAP/HTTPREST/HTTP
F0 Common
ArchitectureFoundation
Tested
Pending
Bus apps / svcs
IBM SystemsArchitectural construct
SOAP/HTTPJMS/MQ
SecurityServices
RT Semantic ModelCore Services
RT Semantic ModelAdapter Services
RT Semantic ModelVisualization Services
RT ModelManagement
Mobile ESB Services
Real Time - Enterprise Services BusRT Semantic ModelAccess Services
ProcessManagement
F0B
TAIL Pilot: Packages and main components
Infrastructure Services – Security – Systems ManagementENTERPRISEDOMAIN
PROCESS CONTROLDOMAIN
15
Tail Pilot: Reference semantic model (RSM) for
An Integrated Information Framework – Providing an efficient pipeline for real-time data transfer and analysis of data
Vendor
Vendor
Field data• Drilling & well
operations• Reservoir &
production operations
• Operation & maintenance
A Real-Time Information Pipeline leveraging the
Reference Semantic Model standard
Operator
IBM C&P Model Based SOA Integrated Manufacturing Solution
Frame Work
Web-service enabled applications
The RSM is composed of:• WITSML/PRODML information
mapped to RSM, MeasurementValues, class
• ISA S88/S95, ISO 15926, IEEE 61970/68 for asset and physical hierarchy representation
• ISO 15926, & Mimosa, for asset life cycle management
Field 1
Field 2
IBM has developed a semantic model for operation and maintenance based partly on
the following standards:
ISA S88 and S95
IEEE 61970
ISO 15926
MIMOSA
WITSML
PRODML
16
GODIOngoing work and challenges
GODI as a corporate solution vs local knowledge and solutions
Urgency or not
User satisfaction
Standardisation
StatoilHydro strategies
Standardisation Bodies
ISO 15926
Industrial products
Automation and Industrial IT
Interface projects
Discipline and technology ownership
17
Work processes, are we improving?