POSC meeting Wednesday November 19th 2003

1
POSC meeting Wednesday November 19th
2003 Progress on implementation of a Global Data
Catalog within Shell Exploration
Production P.J. Kemper Head IM Tools Standards
Shell EP ( Europe ) Peter.kemper_at_shell.com 31
612 963624
2
Company Data Blueprint 2.1.4
The Company Data Blueprint is used to navigate
through data you know to information you are
looking for. The CMS defines how the company
is organised and in which context wich task is
executed. In every task information is produced
and is labeled and stored in the document
management system. The classification consist of
two parts Content and Context. The content
classification is performed with Document
Natures. The context classification is performed
with the Company Data Blueprint. The data in the
Company Data Blueprint is managed by monitored
copy management scripts, transforming the data
from the source systems to the Company Data
Blueprint Store. This guarantees the user knows
the data he his navigating. Also, this enables
others applications to integrate seamless with
the document management system.
For more info contact the EP Centre of Excellence
for Groupware Hugo Belder, NAM, ICP-D, ext. 63529
3
Scope of the Shell EP Catalogue GLOBAL

• EP-Catalogue will contain all Process / Document
  / Classification rules per Document Nature .
• Collection management will provide management per
  Managed Set of Documents and not per file.
• Capture_at_Source will provide In Process
  Classification
• Document Creation Classification from within
  the Web Work environment
• Uses EP Catalogue, Farmed out Document Handling
  will be dumbed down, Internal Document Handling
  will be Quality Focussed
• Implicit Use of Knowledge with minimal Impact on
  the EndUser
• Classification over the Document LifeCycle
• Integrated with MSOffice
• Traffic Light systems will show ( missing )
  Documents per Collections
• EP-Catalogue will Drive 3rd party file exchange (
  3rd part contractors / Selling Buying Assets )

4
Managed Collections

• Objectives
• Which collections?
• Which natures per collection?
• Criteria Traffic Lights
• Criteria Assets
• Define process to revisit the critera in time

ETL
MRD
Value Add
Consuming
Consumer Context
Generic Collection Viewer
Capture_at_Source
Published
Consumer Context
Soll
Ist
Add new info
Collaborative
DIMS.DLL
System e.g. DIMS
Quality Control Legacy
ControlRoom
Document
Legacy
WUP
WDIP
WDIP

• Scanning
• Bulk
• Document

Network (Drag Drop)
Archive
Producing
5
Concept EP Catalog
Process
Discipline
Asset
Services
Organisation
Inter related Keys Only
Project
Output
Input
Model around the Task / Activity Ultimately we
are in the same business doing mostly the same
things. Information only exists in Shell because
it is either an input or an output of a Task /
Activity
6

• Model is not the biggest problem, professionals
  agree among
• themselves on the structure easily.
• Model 90 finished / HSE main remaining part.
• Problem are the Data Value sets
• What is the standard and who will get the bill
  for transition cost ?
• What about Language ?
• What about Jargon / Tradition ?
• Business needs to sort out on the basis , but
  they have mostly the Local View.

7
From Local / Regional to Global Ownership Real
Ownership ? Who holds the tranisition Bill ?
Keys Only
Enterprise Reference Data
Not a principle problem. Which system contains
the values ? Is there a System ?
Unique Business Unit Reference Data
Not a Catalog issue
Transaction Data
8

• Approach
• Identify High Level Ownership with clear
  Discipline support with Feet in the Ground.
• Technical Datamodel is a Generic Datamodel,
  Flexibility is key.
• Make Software as generic as possible
• Separate Classes from real Business Entities (
  eg Facility Types , Document Types ).
• Allow Multi Classes but standardise on Business
  Entity level.
• Standardisation Needs across Industry
• Class structures,
• Industry driven 3rd party file exchange
• Document Natures

9
POSC meeting Wednesday November 19th
2003 Progress on implementation of a Global Data
Catalog within Shell Exploration
Production P.J. Kemper Head IM Tools Standards
Shell EP ( Europe ) Peter.kemper_at_shell.com 31
612 963624 Feel free to call ( mind the time
difference )