The presentation I gave back in October ’15. The conference was held in London by ACI (see http://www.wplgroup.com/aci/event/digital-oilfield-summit-europe/)

1. Integrated Lifecycle Asset Planning
Introduction given at 3rd European Digital Oilfield Summit,
held in London on October 14th, 2015. Presented by André Torkveen

3. © 2014 MIMOSA and PCA
LIFE CYCLE ENGINEERING
Systems
Automation
and Control
Systems
Enterprise
Business
Systems
Big Data and
Analytics
Supplier-Neutral
Open Specifications
Cri$cal
intersec$on
for
a
supplier-­‐neutral
solu$on,
enabling
mul$-­‐domain
systems
interoperability

4. ISO
15926:
«Industrial
Automa0on
Systems
–
Integra(on
of
Life-­‐Cycle
Data
for
Process
Plants,
including
Oil
and
Gas
Produc0on
Facili0es»

5. What do you see here?
(the image is from an Amec Foster Wheeler oil sand plant in Alberta, Canada)
http://www.amecfw.com/sectors/upstream/oil-and-gas-production

6. The
challenges

7. Function : Floating Production, Storage & Offloading (FPSO) platform
Capacity : 170M barrels production over 15 years (estimated; from subsea wells)
First Oil : June 2015 (estimated)
Oil Field : Goliat (located in the Arctic Barents Sea; North of Norway)
Design : Sevan 1000 Concept, including new ‘winterization’ systems
Owner : Eni (Italy; here as licensed operator on Norwegian Continental Shelf)
Yard/EPC : Hyundai Heavy Industries (South Korea)
Power : Electrical, to be supplied via mainland cable
Weight : 64 K ton (metric)
Diameter : 107 meter
Delayed startup cost: € 670 Millions

8. What if?

9. Oslo -
Amsterdam
Amsterdam –
New York
New York -
Houston
What do you expect?

10. What if mobile industry was like this?

11. Operations
Maintenance
Operational risk
Projects
Automation
contractor
Mechanical
contractor
Electrical
contractor
Note: Very simplified
Engineering Procurement Construction Installation
Sub-
contractor
Sub-
supplier
Sub-
contractor
Sub-
contractor

12. This is planning today!

13. Planning tomorrow!

14. The
solution

15. Application and ILAP standard
Planning
tool B
ILAP
standard
Adapter A Adapter B
Planning
tool A
XML XML

16. ILAP Asset Life Cycle Model
Acquire
Greenfield development project
Modification project
Brownfield redevelopment project
Disposal project
DisposeDevelop Operate* and maintain and renew**
Study
Go/no go decision
Governance
ASSET LIFE CYCLE ACTIVITIES
GOVERNING, TIMING
AND CLASSIFICATION
OF ASSET LIFE CYCLE
PROJECTS
* Incl. drilling
** Incl. Turnarounds and High Activity Periods

17. The ILAP project goal
§ Main target: Develop a public ISO standard for
exchange of planning data
§ Second target: Enable development of adapters
that support the ISO standard
§ Third target: Get broader international usage of
the standard

18. ILAP is a new framework for
making planning data
interoperable
within the oil and gas industry
So, what is ILAP, in a sentence?

19. The goal
By 2017, transfers of planning
data is no longer an issue
– it’s seamless!
We have an ISO standard for
it, supported by the industry
and software companies alike!

20. Some
Possibilities

21. There are two main new
possibilities with ILAP
1. Better analysis of larger plans
2. Enable far wider integration of information

22. Integration across domains
Plan
Materials Weather Documents Personnel

23. Why multiple different representations?
Ž Adapter developers’ perspective :
both XSD and RDL implementations
– harmonize across proprietary and open formats
Œ ILAP Planning Expert Group’s perspective : Plain English w/illustrations (+OWL)
— a dedicated specialists’ view; attending to Norwegian oil & gas demands
 ISO (TC 184/SC4/WG3) perspective :
ISO 15926 Part 13 opens up for very broad
appliance; generic, to fit general purpose
Auto-generation
(from OWL to XSD)

24. Please visit ilap.org online!

25. Top-level view of ILAP;
here the Planning Core [concepts]

26. ILAP top structure (topics)

27. The upper-level term set in the
ILAP ontology
Go back
Planned and
Scheduled
Activities
Shutdown
Risk
Standardized
User Field
WBSCriticality
Plans
and Work
Orders
Activity
Networks
WBS
Use Case
Plan
Classifiers
Plan Content
ILAP 2.5 Ontology
DisciplineMilestone
Priority
Contract
Cost
Work Order
Use Case
Status
Progress
Activity Constraint CalendarSchedule
Responsible
Phase
Resource Result Asset
Person or
Organization
ILAP Planning
Core
ILAP Specified User
& Free Text Fields
Plans and
Work Orders
Legend
Plan
Specified
User Field
Free Field
Completely
Free Field
Free Field
Hierarchy
LocationProject
ILAP Modeling
examples
Planning
Core

28. A deeper snapshot of ILAP; here in
W3C OWL (Semantic Web/Linked Data)
ISO 15926-12
ISO 15926-12

29. A deeper view of ILAP;
here in UML (class diagram)

30. The ILAP ontology: a systemisation
of a [domain] understanding
project(data
class&of&activity
class&of&individual
ISO(15926312
ISO(15926313plan&for&activity
ISO(1592634activity&specification
schedule& for&plan
requirements& for&activity
activity
possible&individual
planning
specification&definition
required&activity actual&activity
required&activity&A
planning&for&activity&A
actual&activity&A
activity&A&requirements&
version&2
activity&A&plan&version&3
activity&A&schedule
version&3.2
activity&A&schedule
version&3.3
actual&activity&A&to
2015?03?21
planning&for&activity&A&to
2015?03?21
plan&definition&for
monitors
fulfi
ls
has&requirements&specification
temporal&part&
of
has&source&requirements
temporal&part&
of
monitors
has&current&plan
has&current&schedule
has&baseline&schedule
follows&plan
follows&plan

31. ILAP Data Exchange Patterns
Send via trusted network only,
and only full/complete plans
‘Tin can’
1st generation: 2015
Available via public Internet,
but highly secured. Richer
feature set (analytics, etc.)
Cloud
3rd generation: T.B.D.
Driver: Support incremental
updates. Possibly also adding
integration via shared infra–
structures, still trusted network
2nd generation: 2016
message
broker
Web Services (option)

32. Œ Begin by mimicking the desired workflow as a contextual skeleton
 Add ‘doers’ (i.e. Actors in ROLES) – and content – onto that skeleton
Ž Have IT systems to support just that; parts Œ and  above
sub-planbecomespart ofSAP plan
How do we ‘attack’ the challenge?
Make
[sub-]plan
Send
[sub-]plan
Receive
[sub-]plan
Include
[sub-]plan
Make
[sub-]plan
Send
[sub-]plan
Receive
[sub-]plan
Include
[sub-]plan
Here, a contractor
representative -Peter-
is our SENDER
…while an owner/operator
representative -Paul-
is our RECEIVER
Sub-planmade ine.g. P6
<from>AS</from><to>Op1</to>
format
conversion,
pick recipient
format
conversion
Reference Data

33. Adapters: Sender & Receiver sides
Reference
data in cloud
ILAP
file
SAP-
Interface
SAP
Safran-
Interface
Safran
Project
Primavera-
Interface
Primavera
P6
MS-Project
Interface
MS-Project
Adapter
X Interface X
Reference data
GUIDs & URIs
Configurations
SAP-
Interface
SAP
Safran-
Interface
Safran
Project
Primavera-
Interface
Primavera
P6
MS-Project
Interface
MS-Project
Adapter
X InterfaceX
Reference data
GUIDs & URIs
Configurations
ILAP GUIILAP GUI

34. Additionally, in print
§ ISO 15926 Part 13 and (currently in Committee Draft status)
and ILAP Adapter SRS (Sw. Req. Spec.)
Key documentation
Available online
§ http://ilap.org/ (or http://staging.data.posccaesar.org/ilap/documentation/)
§ http://mapping.posccaesar.org:8080/xsd/release/2.5.6/documentation/

35. Questions?
?

36. – Thank you for your time and attention!
For more information, please contact:
Project Manager: Steinar Dalva, mobile (+47) 93 44 84 80, mailto: sd@epim.no
Leader Steering committee: Robert Skaar, mobile (+47) 48 89 16 67, mailto: robsk@statoil.com

37. (Additional material)
(the following is
solely intended for
supplements during
follow-up discussions)

38. 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)

39. Software
developers
A ‘puzzle’ with many kinds of pieces
Software users
Software tools
Microsoft
Project
Oracle
Primavera P6
Safran
Project
SAP
PM/PS modules
CENTRAL
standardization
body
ISO (TC184/SC4/WG3)
P6 ILAP
Ad.: Pipeline Sw.
MS-Proj. ILAP
Adapter: TPG
Safran ILAP
Adapter: Safran
SAP ILAP
Adapter T.B.D.
…?... …?... …?... …?... …?... …?... …?... …?... …?...
TC184 : Automation systems and integration
SC4 : Industrial data
WG3 : Oil, Gas, Process and Power
Standards
Norway
NATIONAL
standardization
body
ANSI DIN
…?...
ILAP.orgcollaboration

40. Planner
1
Planner
2
Planner
3
Planner
5
Planner
6
Organiza(on
1
Organiza(on
3
Project
1
Project
X
Project
2
Project
Y
Organiza(on
2
Planner
4
Planner
2
Planner
7
Some practical aspects

41. After ILAP 2.5’s public release (as Part 13),
the standard must be operationalized
PCA
RDL
ISO
RDL
(spreadsheet)
ILAP
Adapter
(external sources)
ILAP
Int.
Central
(as developed by
software vendors)
(when in use at
operators’ sites)
ILAP
Adapter
NPD
Fact
Pages
BrReg
(‘company’)
NORSOK
Z-­‐014
(review, submit) (review, decide)
ILAP
Project
(reference data)
(create, submit)
So:ware
VendorsPublic
Authori(es
ILAP
joint
venture
Oil
&
Gas
Operators
with
partners

42. ISO 15926 Part 13 – the big picture in ISO’s eyes
ISO
15926-­‐2
–
generic
concepts
for
life
cycle
integraIon
ISO/TS
15926-­‐3
–
ontology
for
geometry
and
topology
ISO/TS
15926-­‐4
–
core
reference
data
for
process
plant
Ontologies
for
other
applicaIons
(producIon
reporIng,
asset
management,
logisIcs)
Interfaces
to
other
applicaIons
extensions
to
the
core
reference
data
for
other
disciplines
ANSI-­‐SPARC
Architecture
external
level
community
level
ISO
15926-­‐12
–
ontology
for
life
cycle
integraIon
ontology
ISO
15926-­‐13
–
ontology
for
integrated
lifecycle
asset
planning
ISO
15926-­‐13
–
scheduling
applicaIon
view
model
ISO
15926-­‐13
–
scheduling
applicaIon
XSD

43. ISO 15926 Part 13 - the big picture in EPIM’s eyes
ISO
15926-­‐13
–
ontology
for
integrated
lifecycle
asset
planning
PCA
RDL
ISO
15926-­‐13
–
scheduling
applicaIon
view
model
ISO
15926-­‐13
–
scheduling
applicaIon
XSD
NPD
fact
pages
ISO
19008
Brønnøysund
Register
EPIM
ontology
for
reporIng
WITSML/PRODML
EPIM
ontology
for
logisIcs
logisIcs
interface
other
EPIM
implementaIon
stacks
ISO
15926-­‐2
–
generic
concepts
for
life
cycle
integraIon
ISO
15926-­‐12
–
ontology
for
life
cycle
integraIon

44. ILAP Ontology Legend & Structure
ILAP Core Model
ILAP Data
Exchange Model
Subclass (Class that is a subclass of another Class)
Type (individual instance of Class or, or class member of Class of Class
Go back
Object Property
Datatype Property
Object Property instance
Datatype Property instance
ILAP Data
Exchange Model
ISO 15926-13 second order Class of Class, owl:Class
ISO 15926-13 first order Class, owl:Thing
ISO 15926-13 Individual, instance
Object
Property
Datatype
Property
Datatype
Relation
Object
Relation
ILAP Exchange
Data
ILAP Exchange
Data
ISO 15926-13 first order Class, owl:Thing
ISO 15926-13 Individual, rdf:type
LCI Model ISO 15926-12
External
Reference Data NORSOK Z-014, NPD, BRREG

45. ILAP Core model of Responsible Actor
Organization Crew
Drill Crew
Activity 101
in Plan version 2
for project P
Actvity in Plan Project
npd: Operating
Company
brreg:
Company
Person A
Project P
Drill Crew A Drill Crew B
Person
has
Operator
has Main
Contractor
has
Project Leader
has Sub
Contractor
has Actual
Operator
has Actual Main
Contractor
has Actual Sub
Contractor
This page shows the Class hierarchy and Prpoerties used to describe Responsibility
Aker
Solutions AS
Statoil ASA
Go back

46. ILAP Core model of Resource
Resource
Resource in
Plan
Cost Based
Resource in
Plan
Time Based
Resource in
Plan
Activity Planning
Resource
SCCS:
Z-014 Activity COR
Planning Resource
Class
SCCS: COR_K
757 Classes cover
SCCS:COR
Class of
Resource
Software
Application
Software
Application
Cost Based
Resource
Time Based
Resource
Activity 101
in Plan 2 version 1
for project P
Engineering
Manhour
Resource
Project Resource 1
has
Resource
Possible
Individual
SCCS:
COR_KO
Go back

47. ILAP Core model of Result
Result
Result of
Plan
Activity Planning
Result
SCCS:
Z-014 Activity PBS
Planning Result
Class
SCCS: PBS_B
777 Classes cover
SCCS:PBS
Class of Result
Project
Deliverable
Project Deliverable 1
has
Result
SCCS: PBS_A
Possible
Individual
Activity 101
in Plan 2 version 1
for project P
SCCS:
PBS_ADDC
Go back

48. NPD:
Troll
userfield: has
Field
ILAP Core model of Asset
Specified User
Field
Asset in PlanWell Type
Petroleum Field
Class of Asset
Well
CompletionType
Asset Facility
Possible
Individual
Wellbore Well
NPD: Wellbore NPD: Well NPD: Field NPD: Facility
NPD:
Wellbore-5192
NPD:
Well-1 2-2
NPD:
Troll A
has Specified
User Field
userfield: has
Facility
userfield: has
Operating Unit
userfield: has
Living Quarter
has
Asset
Activity 101
in Plan 2 version 1
for project P Go back

49. ILAP Standard Model of Project
Go back
Greenfield
Project
High Activity
Period
Project P
Plan for ILAP
Data 1 SCCS: SAB E
Specified User
Field
has Specified
User Field
Free Field
Value
userfields: has
Project Phase
Plan 1 version 1
for Project P
Project Phase
has Project has Plan
has Project
AFE id
has Project
Phase
has Project
Status
has Project
Type
has Result
has
Project Leader
has Lifecycle
Asset Phase
has Project
Milestone
has Contract
Milestone
userfields: has
Project Type
has
Description
has Short
AFE29
userfields: has
Project Responsible
userfields: has
Project Code
Data
Person A
Active
Milestone 2
Milestone 1
PBS AB
Substructure

50. SCCS: COR_K
ILAP Standard Fields for Discipline
Go back
Discipline
userfield: Specified
User Field for Activity
102 in Plan 3 Version 1
for Project P
Class of
Staff Time
Activity 102
in Plan 3 version 1
for Project P
has Specified
User Field
Actvity in Plan
Free Field 4
Value 1
userfield: has
Discipline Code
SCCS:
COR KD
Drilling
ILAP:
COR KI
Automation
ILAP:
COR KK
Maintenance
ILAP:
COR KX
LCI30 Classes defined
by NORSOK to
cover standard
Engineering
Disciplines
userfield: has
Catgeory
ILAP Resource
Can define any number of ILAP extensions to represent sub disciplines
has
Discipline
userfield: has
Discipline
EXP ENG
Explosive
Engineering
has
Description
has Short

51. Geographic
Location
Physical
Location
Area Country Continent
ILAP Core model of Location
Go back
Specified User
Field
Point in SpaceRegion in Space
Part of the
Surface of the
Earth
Business Area
NPD:
License 037
License Block
Activity 101
in Plan 2 version 1
for project P
has Specified
User Field
userfield: has
License
Actvity in Plan
Physical Object
Free Field
Value
userfield: has
Location on Facility
userfield: has
Location of Material
Work Center
Main
Work Center
Operational
Work Center
Operational
Work Center A
has Location
userfield: has
Location of Work

52. Plan with Levelhas Plan Level
Level 3 -
Project Master Schedule
Project
Type
Activity Planning
Result
Asset Lifecycle
Phase
Activity Planning
Resource
Activity Planing
Location
Activity
Objective
Project
Contract Type
Go back
ILAP model of Plan Classifiers
Plan for ILAP
Plan 1
Version 1
for project P
has Resource
Type
has Result
Type
has Contract
Type
has Cost Type
has Location
has Lifecycle
Phase
has Objective
has Project
Type
Operation and
Maintenance Project
PBS AEAC
Pipeline Protection
OPEX Project
SAB O
Operation Phase
COR KU
Subsea
License Block
Activity to Maintain
Business as Usual
Accrued Time Project
Project
Cost Type

53. ILAP User Fields – Use Case example
Go back
This example illustrates how a Free Text Field is used to describe Activity data
in a Use Case involving data transfer from Contractor A to Operator A
Activity 102
in Plan 3
Version 2
for Project P
Specified Userfield 1
for Activity 102
in Plan 3 Version 2 for
Project P
has Specified
User Field
Free FieldActivity in Plan Free Field Value
has
Work Order
Specified
UserField
has
Field Name
Total of 90 userfields
Free Field Set
Free Field Set 1
userfields:
has Free Field
for Specified
User Field
General Work
Free Field for
Work Order
Total of 4 values for local varaible «Prosjektstruktur i IFS»
in Use Case data example received from Operator A
mapped to hasWorkOrder with 4 instances of Free Field Value
Free Field for Work
Order Value 1
Målepakke
Nedstrøms 3.trinn
seperator (duplex)
Package 1
Generell
Mlepk
Nedstrm
Package 1
has
Description
has Short
has
Description
has Short
has
Description
has Short
has
Description
has Short
Free Field for Work
Order Value 2
Free Field for Work
Order Value 3
Free Field for Work
Order Value 4
has Value
userfield:
has Work
Order

54. ILAP model of WBS elements
External Reference Data used to describe WBS elements Go back
Project P
Specified User
Field 1 for
Activity 103 in
Plan 3 Version 1
for Plan P
has Specified
User Field
Free Field
Value
AFE29
WBS description
has
Description
CAPEX
Project
SCCS:
SAB 52
Free Field
Value
Free Field
Value
Free Field
Value
Free Field
Value
Free Field for
WBS Part 5
Value 1
has
Description
Assistanse
Offshore
Statfjord
Statfjord
A
Skifte
filterhus
på
80-­‐C
UJ-­‐AB
Pumpe
A
has
Description
has
Description
has
Description
has
Description
userfield: has
WBS part 1
userfield: has
WBS part 2
userfield: has
WBS part 3
userfield: has
WBS part 4
userfield: has
WBS part 5
Resource 1
Result 1
Activity 101
in Plan 2
Version 1
for project P
Activity in Plan
has Project
AFE id
has Project
AFE id
has Cost Type
has Resource
has Result
has Activity
Type
SCCS:
COR KD
SCCS:
PBS ADDC