Traditionally, financial data marts and operation data stores are built and managed by IT. So how does the business user view and manage the hierarchies and metadata attributes without IT getting in the way? Coming from the IT side of the house, I have had the opinion that the business might “know the business”, but given the opportunity to manage a technical system they will take shortcuts and ultimately bring the IT solution back to a level they are comfortable with…and thanks to Bill Gates, Microsoft Excel ends up trumping the investment in technology.
I have found that there needs to be a bridge between IT and business users. By the nature of a bridge, there is a span that straddles an open gap with the potential if not built correctly the plunge can be a long and ‘fatal’ fall.
There are many companies offering workflow tools to bridge the gap by helping the communication between business and IT. Alone these solutions still leave opportunity for failure as IT is managing systems it does not have an intimate ownership in. Nor does IT have the knowledge to determine if the business is going to request a change that will impact the system. IT presumes that if the software allows the change than there is no reason why not to do it. As we all have experience one time or another, this is a bad assumption.
Of the many tools I have worked with, currently the Oracle Data Relationship Management (DRM) tool (formally Hyperion MDM / Razza Dimension Server) fills the gap between business and IT. Using a tool such as this gives a strong user interface that the business can use and buy into while allowing IT to be involved by building edit checks and integrity checks into DRM. Additionally it provides IT the vested ownership while keeping the business from impacting their own “business rules”. Not to mention IT’s data governance policies are enforced which keeps IT happy.
A win, win for everyone… right?
Wednesday, May 19, 2010
Why not EPMA…who needs DRM?
Over the past several months, and quite possibly the past year or two, there have been numerous discussions regarding the need for a separate master data management (MDM) tool such as Hyperion / Oracle Data Relationship Management (DRM) to manage Hyperion metadata outside of the Enterprise Performance Management Architect (EPMA) tool that comes with Hyperion System 9 and Oracle Fusion 11.
Recently at a users’ conference, I heard comments like “EPMA is DRM ‘Light’” and “EPMA is DRM with a Web interface”.
Hyperion, and obviously now Oracle, has invested deeply in EPMA and it is difficult to identify how and where it might differ from the DRM product. Oracle has even used portions of the DRM base code and underlying architecture in EPMA and when looking at vapor-ware demos, you might draw similar conclusions to those quotes above. In reality, EPMA, in its current state, is a pumped up version of the old Hyperion HUB as it relates to metadata management. Granted, EPMA has updated the user interface leveraging the glyphs (icons) and nomenclature from DRM while completely missing the intellectual aptitude that a master data tool provides.
Below are the key uses that were provided in a recent Oracle presentation as well shows the difference between EPMA and DRM:
EPMA
• Unifies and aligns application administration processes across the Hyperion EPM system
• Imports and shares business dimensions in the Dimension Library
• Builds, validates, and deploys applications in the Application Library
• Designs and maintains business rules in Calculation Manager
• Loads and synchronizes transaction data into and between EPM applications
DRM
• Manages change of business master data across enterprise applications
• Consolidates and rationalizes structures across source systems
• Conforms dimensions and validate integrity of attributes and relationships
• Synchronizes alternate business views with corporate hierarchies
• Key Features include:
i. Versioning and Modeling
ii. Custom rules and validation
iii. Configurable exports
iv. Granular security
v. Change tracking
*Oracle Hyperion Data Relationship Management, Fusion Edition 11.1.1- Robin Peel
Recently at a users’ conference, I heard comments like “EPMA is DRM ‘Light’” and “EPMA is DRM with a Web interface”.
Hyperion, and obviously now Oracle, has invested deeply in EPMA and it is difficult to identify how and where it might differ from the DRM product. Oracle has even used portions of the DRM base code and underlying architecture in EPMA and when looking at vapor-ware demos, you might draw similar conclusions to those quotes above. In reality, EPMA, in its current state, is a pumped up version of the old Hyperion HUB as it relates to metadata management. Granted, EPMA has updated the user interface leveraging the glyphs (icons) and nomenclature from DRM while completely missing the intellectual aptitude that a master data tool provides.
Below are the key uses that were provided in a recent Oracle presentation as well shows the difference between EPMA and DRM:
EPMA
• Unifies and aligns application administration processes across the Hyperion EPM system
• Imports and shares business dimensions in the Dimension Library
• Builds, validates, and deploys applications in the Application Library
• Designs and maintains business rules in Calculation Manager
• Loads and synchronizes transaction data into and between EPM applications
DRM
• Manages change of business master data across enterprise applications
• Consolidates and rationalizes structures across source systems
• Conforms dimensions and validate integrity of attributes and relationships
• Synchronizes alternate business views with corporate hierarchies
• Key Features include:
i. Versioning and Modeling
ii. Custom rules and validation
iii. Configurable exports
iv. Granular security
v. Change tracking
*Oracle Hyperion Data Relationship Management, Fusion Edition 11.1.1- Robin Peel
Subscribe to:
Posts (Atom)