Incorporating SAP Metadata into your overall Information Management architecture. Case study from BP and IPL presented at Enterprise Data World, Tampa, FL April 2009

1. Including SAP data in your Information Architecture EDW Tampa, April 2009 Christopher Bradley & Ken Dunn

3. 1. BP Overview For alternative section dividers with images, please see the BP images where you can copy and paste a pre-set section divider slide (see BP templates in PowerPoint menu: File / New or www.bp.com/brand)

5. Our global presence

6. Areas of BP Business Exploration & Production Gas Refining Alternative Energy Chemicals Lubricants Fuels Marketing & Retail

8. 2. Information Architecture challenges at Bp

10. Information Architecture Framework ER/Studio Data Types Master Data MI/BI Data Transaction Data Structured Technical Data Digital Document Structure Models / Taxonomy Catalog / Meta data Integration and Access Quality Lifecycle Management Process Governance Planning People Goals Principles Purpose

12. 3. What’s the problem? For alternative section dividers with images, please see the BP images where you can copy and paste a pre-set section divider slide (see BP templates in PowerPoint menu: File / New or www.bp.com/brand)

14. SAP Physical Database…

15. … 70,000 Islands of Information

16. ...Need intelligible metadata

17. … and understandable Analytical Structures

18. 4. Why bother modelling when implementing ERPs? ….. For alternative section dividers with images, please see the BP images where you can copy and paste a pre-set section divider slide (see BP templates in PowerPoint menu: File / New or www.bp.com/brand)

21. BP HR example: Personnel tracking Data Modelling – where did it all go wrong? Candidate UK Employee Expatriated to US Joe’s “Engagements” DATA ON AN ENGAGEMENT Start & end date, Sponsor / Parent / Home Organisation, Contractual Details (e.g. Employment Status, Level, Legal Entity, Salary, Benefits) UK Employee Retiree Joe’s “Role Assignments” DATA ON A ROLE ASSIGNMENT Start & end date, Position (showing Job Type, Work Location, Working Time, Skills Requirements) 1/1/2007 1/9/2009 1/9/2012 1/1/2016 Trainee Geophysicist North Sea Geophysicist GOM Geophysicist (pt time) GOM GU Leader (pt time) GOM Geophysicist North Sea Geophysicist Sabbattical (No role assignment) Exploration Geophysical Consultant In this model a person goes through a sequence of “Engagements” (in this example: candidate, employee, expat, employee, retiree). For each Engagement, the positions filled are indicated by “Role Assignments”, showing start and end date in each position.

22. The Corresponding Entity-Relationship Diagram Data Modelling – where did it all go wrong? Engagement Role Assignment This is showing that “Role Assignment” is subordinate to “Engagement”. i.e. you can’t set up a Role Assignment until you have an Engagement to relate it to. An everyday language example: “Joe Bloggs’ role as Trainee Geophysicist falls under his UK contract of employment dated 1/1/2007”.

23. Data Modelling – where did it all go wrong? Person Engagement Position Role Assignment Org Unit Personal Details (e.g. Name, Bank Acct, Emergency Contact, Qualifications) Start & end date, Sponsor / Parent / Home Organisation, Contractual Details (e.g. Employment Status, Level, Legal Entity, Salary, Benefits) Start & end date Job Type, Work Location, Working Time, Skills Requirements Manager, Cost Centre Model 1 One way of keeping track of people… In this model a person goes through a sequence of “Engagements” (e.g. candidate, employee, expat, employee, sabbatical, employee, retiree). For each Engagement, the positions filled are indicated by “Role Assignments”, showing start and end date in each position. Each Position is part of an Organisation Unit, which in turn is part of a higher organisation unit, and so on. A Position is filled by different people over time (i.e. the various Role Assignments to one Position can be for different people).

24. Data Modelling – where did it all go wrong? Person Position Role Assignment Org Unit Personal Details (e.g. Name, Bank Acct, Emergency Contact, Qualifications) Start & end date, Sponsor / Parent / Home Organisation, Contractual Details (e.g. Employment Status, Level, Legal Entity, Salary, Benefits) Job Type, Work Location, Working Time, Skills Requirements Manager, Cost Centre Model 2 One possible simplification We might try to simplify the model by merging Engagement into Role Assignment (see below). But there are consequences. For example this would require us to repeat the sponsor and contractual details on a new Role Assignment each time the person moves to a new Position. Also if someone had simultaneous Role Assignments we would have to keep the multiple versions of their contractual details in step.

25. Data Modelling – where did it all go wrong? An example of why the model matters to SAP HR Person Engagement Position Role Assignment Org Unit Personal Details (e.g. Name, Bank Acct, Emergency Contact, Qualifications) Start & end date, Sponsor / Parent / Home Organisation, Contractual Details (e.g. Employment Status, Level, Legal Entity, Salary, Benefits) Start & end date Job Type, Work Location, Working Time, Skills Requirements Manager, Cost Centre This data field recorded on an Engagement might be better implemented as this relationship between the Engagement and an Org Unit. There are powerful reasons to do this: e.g. the processes of organisation definition (which maintain the list of Org Units) can ensure that, unlike now, no-one’s sponsor/parent/home gets lost as org units are merged, split, or dissolved; e.g. workflow can route transactions seamlessly via sponsor/parent/home when appropriate, rather than as now by using host org unit as a proxy with manual interventions (this applies to salary review & development decisions, for example). Adding the red relationship is a configuration choice in SAP. SAP is “vanilla” with it or without it.

29. 5. How can you incorporate SAP metadata into your overall model?

33. SAP Server N SAP Server 3 SAP Server 2 SAP Server 1 ABAP 2 1 5 1. Metadata extracted from SAP 2 Data Modelling Repository 3 4. User browses Saphir repository to Identify & subset metadata. 5. Model metadata in ER/Studio & store Data models in BP corporate repository. SAP Instance 1 SAP Instance 2 SAP Instance 3 SAP Instance N ABAP 1 (read only) Saphir Repository 1 Saphir Repository 2 Saphir Repository 3 Load Saphir repository Database Server Application Server Load Saphir repository Load Saphir repository Load Saphir repository ABAP 2 ABAP 1 (read only) ABAP 2 ABAP 1 (read only) ABAP 2 ABAP 1 (read only) Client 2. Extracted Metadata files moved to application server 3. Metadata loaded into Saphir repository 4 Saphir ER/Studio ER/Studio Repository Server Bp’s SAPHIR Architecture Saphir Repository N

36. View table and field information

37. Navigate relationships

38. Application Hierarchy & Program tree

39. Get information from screen X X X

41. 6. Lessons learned & benefits? For alternative section dividers with images, please see the BP images where you can copy and paste a pre-set section divider slide (see BP templates in PowerPoint menu: File / New or www.bp.com/brand)

46. Questions? Contact details Chris Bradley Business Consulting Manager [email_address] +44 1225 475000 Ken Dunn Head of Information Architecture [email_address] +1 630 836 7805

47. Backup Slides

48. Avoid the Death star!

49. Minimize Administration

50. Make models available to everyone

51. Survey Users: What benefits are you gaining from the service? We are not obtaining any benefits We are obtaining benefit through use of a common modelling tool We are obtaining benefit through utilisation of a common repository We are obtaining benefit through use of common standards, guidelines & processes We are obtaining benefit through re-use of models & artefacts We are obtaining benefit through provision of central support & help