Data Logistics

1
Data Logistics
In multi-application environment DALOGIS
Vroomen Fred/ 7 juni 2006 PELC
2
Introduction

• Presenter Fred Vroomen
• DSM Manufacturing Center, Geleen, Netherlands
• GroupBusiness Information Management
• Business Process Expert Maintenance/Inspections
• Topics Data/Document Handling, Application
  Management SAP-PM, CAE-environment, Inspection
  systems, Master Data Management
• fred.vroomen_at_dsm.com

3
Workshop Objectivessharing concepts Master Data
Logistics

• Master Data Management in Multi-Application
  environment
• Data in-consistency in numbers
• Alternative Approach
• Concept for brown field operations
• Organisational requirements
• Work Concepts
• Tooling requirements
• Data synchronisation time requirements

4
Need for change

• DSM is introducing shared service center
  structure Concentrating local departments in site
  and/or ww-department
• Site Geleen 14 plants concentrated technical
  dep. into manufacturing center.
• Inducing Standardisation of applications, media,
  ERP, document management
• Inducing Harmonisation of database contents, db
  structures
• Call for integrated operations and integrated
  data/document flows

5
Revealing History of .setting the path to

• Numerous Applications differing in revision level
  and use
• Standard Applications but various db structures
  present
• Non-aligned Document and Data Handling
• Workprocess differences maintenance, projects
• Large Scale Reduction of applications
• Integration and Harmonisation SAP
• Uniform Workprocedures with basis in business
  risc assesments
• Document Management and Data Management

6
Some Numbering..data alignment

• Application Reduction 800 ? 60 ? 9 Main Apps
  SAP
• Objects 500.000
• 20 data field descriptors per object per app.
• Document types 280 ? 90 Must Efficiency Docs
• 14 Originating Plants
• 1 1000 changes faulty.
• Measured 5 Data Object changes per year per
  plant
• 1.051.051.051.05gt 22 per 4 year object
  change
• 25.000 Objects are touched yearly
• 250.000 Objects in 10 Main Apps on the move
• 5000 Data field miss aligments non observed per
  year

7
The BrownField Problems Graphical
Data structure conflicts
Multiple dbs
PID
Intools
Revision level issues
LOGSIM
HERA
Non-aligned
ELCAD
ARIA
SAP
PID
Apps 10 - 60
?
Documentum
IP21
Different formats
overlap
Synchronisation issues
8
Solutions and Reflexes

• First Thought SAP master and direct linking
  to/from other Apps ? dont
• Second Thought Introduce Data Logistic and
  growing step by step towards thin integration
• ? We require Sequential Data Handling and
  matching, semi-synchronisation across apps and
  documents data logistic senquencing

9
Logical development Steps

• Harmonize within each Application (db reduction)
• Reducing the variaty of formats and structures
• Restructure the Object Definitions in each
  Application
• Create uniformous formats across applications ?
  high end tools
• Find/Define Areas of common Interest
• Repetitive Data Matching ? managing large to Do
  list
• ? indentify rule sets
• Redefine Areas of Common Interest
• Repetitive Data Matching ? managing smaller to Do
  list ? indentify fixed workprotocol/work order
• Introduce Thin Data matching tool

10
Data Logistics
11
Data Matching Cycle Data Logistics

• Process Engineers update Function Location Master
  (super index)
• Project Engineers Modify Project Environment of
  various Apps
• Promotion of data as built
• Data matching toward FLM reference and apps
• Create to do list for all other apps
• DALOGIS at work
• First on basis of rule sets equiped with high end
  tool for reshaping database structures
• Later on basis of protocolized platform with
  medium end tool for endlessly matching semi
  synchronuous data (and data in documents)

12
Document Handling requires FLM
The Basis is a well structured Function Location
Master as Reference
Aspentech workbench
Documentum
FLM
PFD
Index Function Location
SAP
Data Sheets
13
Document/Data Flow
Data and Document handling should be regarded as
one environment To be kept in Sync ! But no
realtime requirements in the Chemical Proces
Industry !
14
Realtime or Not Realtime data synchronisation?

• Statement
• JIT plants require real time data transfer
• Goods plants require near real time data transfer
• Chemical Plants require semi synchronised data
  matching protocols
• Small Plants do it on paper

15
Resumé

• Master Data Management in Chemical Plants
  requires an Data Logistic Approach
• There is no need for near real time data transfer
• There is need for data structure high end tools
• There is need for data matching tools in thin
  coupled manner
• Goal Think of an Orchestra of musicians ? Demo