Embracing change to reduce cost and delay whilst improving quality. How Hyperion Data Relationship Management (DRM) can become your change management platform. Tuesday August 17th, 2010 12:00pm
7.pdf This presentation captures many uses and the significance of the number...
Fitter Faster Smarter
1. Fitter, Faster, Smarter Embracing change to reduce cost and delay whilst improving quality Simon Kilshaw Oracle BI & EPM Applications Tuesday 17 th August, 2010 The most comprehensive Oracle applications & technology content under one roof
2.
3.
4.
5.
6. Reference data is any kind of data that is used to group, categorize or relate enterprise information assets either within or beyond the boundaries of the enterprise. Types & Codes Taxonomies Relationships Standards Transaction Codes Industry Classifications (e.g., NAICS, SIC) Product / Segment; Product / Geo Currencies Lookup Tables Product Categories Transaction Codes / Financial Accounts Time Zones Status Codes Sales Territories Customers / Sales Hierarchy Calendar Role Codes Market Segments Valid Code Combinations Tax Rates
7. Reference Data Management Definition An enterprise process to govern the consistent creation, maintenance and consumption of groupings , classifications , standards and relationships between different information asset types
Every application / business function has its own structures – no consistency or shared perspective. To make it usable broadly, requires a lot of IT resources to reconcile the master data Users who know what the structures should be are unable to make the changes themselves and are often forced to involve IT With DRM, … we provide a business user facing application to make different structures usable across the enterprise while retain the business perspectives unique to each function / stakeholder. Enable business users to drive change while allowing IT to govern the master data by codifying business rules that build consistency in enterprise master data.
Just an example of customers at the end of FY 2008. Not a complete list. Note the spread across industries, but the specific strength in financial services (we may have to merge some of those icons, though) Strong references include Washington Mutual (despite recent issues!), Dell, Telenor Growing presence in EMEA, and emerging clients in APAC.
A maturity model measures value through an objective assessment of current ‘capabilities’. It shows how those capabilities can be enhanced (through an evolutionary process) toward a higher level of maturity. It facilitates decisions upon where effort (and limited resources) should be expended to increase capabilities. It’s not necessary for an organization to always aim for the highest level of maturity. Rather, these models help target effort on the most tangible benefits that can be realized. For Enterprise Dimension Management, the critical characteristics are Dimension / hierarchy maintenance processes Responsibilities for that maintenance Alignment of dimensions across the enterprise (systems, business functions, technology stacks) Enabling (and enforcing) data governance Workflow processes required Indicators of each level of maturity So, driving improvements in capability: Not a linear process But … cannot just jump from level 1 to level 5 Some jumps are more difficult: From level 2 (home-made) to level 3 (centralized) From level 4 (aligned) to level 5 (devolved) Compare to “chasm” & “gap” in the BI Maturity Model So, must maximize ROI for the enterprise Value of Dimension Management Maturity Model: Facilitates implementation of enterprise dimension management Supports capability improvements in other areas: EPM & BI Enterprise data governance ERP (transactional) systems [Use this model to open discussions between IT and the business experts] [DISCUSS EXAMPLES – MOST CLIENTS START IN COLUMN 2 AND ASPIRE TO COLUMN 4]