File Library

**See attached PPT for properly formatted outline.
**See attached PPT for functional and technical environment view.

Key Concepts:
Hierarchy Management as a Service
Baker Hughes has developed architecture to support an enterprise hierarchy management solution as a service. The focus is to to accomplish:
Tight integration with sources for Operational Master Data.
Tight integration with consuming application interfaces.
Recognized as System of Record for financial master data reporting structures.
The objective is to share both a functional and technical overview of our solution.
A Data Driven Model
The objective is to share an overview of how Baker Hughes leverages an array of derived properties to create a data driven model. Examples include:
Examples:
Using derived properties to dynamically generate complex mappings to send to the MDM hub for consumption by the SAP to Hyperion data load to transform a range of source accounts to an array of target accounts (a one-to-many relationship).
Using derived properties to dynamically generate mappings to deliver data to target applications where the hierarchy is shared but each application has different aggregation levels.

Supporting the Business from an Enterprise view
Supporting multiple domains:
HR, HS&E
Personnel Areas
Employees
Supply Chain/Manufacturing
Plants
Finance
Cost Centers
Profit Centers
Functions
Marketing
Product Lines
Blending operational master data from separate domains:
Example: Building a hierarchy blending Personnel Area and Employee (from SAP HRMS module) into an entity hierarchy composed of Cost Centers and Profit Centers (from SAP FI). The results is layering in the HR members under cost centers by leveraging inferred relationships in the data records.
Any source. Sourcing operational master data into DRM.
SAP FI
SAP SCM
SAP HRMS
Well Master system
Rig Count system
Centrally managed, supporting financial and non-financial business units.
Manage operational and analytical master data in a single location.
Provide domains their own sets of properties to provide individually tailored results.
Any target, DRM managing the enterprises Analytical MDM spectrum.
SAP Business Warehouse, BOBJ Universe (Pulled)
Hyperion HFM, Essbase & Planning (Pushed)
Microsoft SSAS, Powerview (Virtualized)
Tibco Spotfire (Virtualized)
SAP ECC: (Pushed)
OneSource Tax Data Manager and Provision application (Pushed)

Underlying Technology
DRM 11.1.2.2
Informatica (ETL)
Oracle Data Integrator (ODI)
Data Services
Oracle Exadata

Technical Overview
Multi-Layer architecture.
Integration of operational master data from source systems (Informatica)
Enterprise MDM Bus (staging area) – a schema residing on Exadata leveraging Informatica for cleansing, matching, enhancing, and managing master data elements
Integration of operational master data to DRM (Informatica/MDM Connect/Web Services). DRM database residing on Exadata.
Integration of Analytical master data to an enterprise MDM Hub (staging area) – a schema residing on Exadata containing hierarchies, mappings, and definitions
Outbound Integration layer - management of standardized loads and processes to support master data and data loads to subscribing applications utilizing a combination of Informatica, ODI, and Data Services where master data is either pushed or pulled into subscribing system application and/or BI layers.