Leverage your Existing MDM Investments to Achieve ... · Bringing competency and excellence in Information Management into an organization requires comprehensive planning and well-considered,
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Understand what really gets managements attention: Acceleration, Cost Management, and Risk Mitigation. Essentially do more with less.
Understand business drivers and how technology best meets those objectives
Articulate the value proposition and differentiators in how yourorganization manages and leverages its information
Understand how to bring unique differentiation to drive better analytical insight to competitive situations
Think differently about how you tackle your companies Information Management challenges
The desired outcome from today's session is to provide a fresh perspective on how to deliver maximum corporate value to your Information Management and Analytics solutions so that you will be able to:
EIM common capabilities can be delivered within a Shared Services Organization (SSO) structure to enable information management toalign with business needs and support their execution
Data ArchitectureData ArchitectureData ArchitectureStructured Data Unstructured Data
Service ExcellenceService ExcellenceService Excellence
Data GovernanceData GovernanceData Governance
Data Architecture serves as the foundation for all Information Management capabilities
Technical capabilities
manage specific aspects of data
acquisition, integration, analysis and
access
Governance and Service Excellence provide overall direction and alignment of technical
capabilities for the continued benefit of business needs
Large number of unreconciled Operational Data Stores in the Enterprise– What data is there, what is its’ source and its’ quality?– What is this store doing (what business is it servicing and to what end)?– What governance policies are in place?
Information Consolidation and Information Management– It’s impossible to rationalize into a single enterprise data model that everyone agrees!– The complexities of the data model force a large number of mediation tables:
How do business developers interact with the consolidated domain?Can we create specific views that simplify / segment the model?Given several “equivalent” entities, how do I rationalize which one to use?
– What do I tell the business who wants to “own their information”Does ownership translate to be in control of changes to it? or reads against it?
– Application consolidation of structured and unstructured information
What is the translation of my SOA mandate to information contracts?– Is there a way to understand where a change to a data model impacts a service
contract?– How do I consistently bring together information to fulfill a request – CRUD
SIM is the discipline of managing and integrating enterprise data based on the principle of capture data’s formal business meaning
Understanding the business semantics can ensure the business meaning of data is universally understood and the data may be found, used & aggregated without
There are many Data Service providers which integrate multi-modal data for more consistent developer access
There are even some that maintain transactional consistency, but it’s pessimistic Transaction Management styled and lock-constrained
II-TS focused on:– Model Mastering (bootstrap and then txn management)
How do I get into a federated domainHow do I participateHow do I re-sync on disconnectHow do I reconcile a participants model change (version the federate and version the federation)
– Federation contexts… what are the local and federation contexts that are critical to declared cooperative models
– Multi-master synchronization (active-active) reconciliation in Structured domainsChange data propagation, change mastering and synchronization
– Contextual annotations on a Canonical Model for improved information governance
– Auditability of federated information changes as an extension to SOA Governance
Change Data Messages are sent out by Change Data Source systems;these changes can be mastered by systems that act as Mastering Services; mastered changes to entities that result from these Change Data Messages are sent out to interested parties as Change Entity Messages
Messages sent across the ESB are all kept in a Canonical form– The form for a message may be domain-specific, but for a given domain a common
canonical form is chosen so that services can remain loosely coupled and messages can be routed dynamically to various service endpoints
– At the “edges” of the ESB, messages are transformed to a Local (or application-specific) form for services that do not understand the Canonical form used on the ESB
– Currently, an adapter pattern is used to manage this process
Multi-part messages used extensively– To track the message’s history– To provide the ability to maintain information that may not survive the transformation
to a canonical form accessible (by keeping a record of the original message in its local form as one part of the message being sent across the ESB)
In the SIM model, all information domains defer meaning (a conceptual model) to a single Enterprise Information OntologyEach domain maps its domain specific structures (e.g. customer table, customer document, modify customer transaction) onto a single concept modelSIM was designed for the Internet, so it is federated by design. A single monolithic data model is not required. Only the mappings and respect of the semantic model contracts are required.
During requirements, a coherent conversation is possible about business requirements and rules.During design the EIO supports the rationalization and analysis of servicesDuring implementation the EIO can be leveraged for automated adaptor interface generation (through a canonical model)At Runtime, dynamic transformation leveraging the EIO can avoid the hard coding of adaptors
Decreased “Time to Value”– Improved correctness & completeness of data– More contemporary updates (shorten the “batch window”)
Reduced “Time to Feature”– Support versioned changes to both interfaces AND Data Models through integrated impact analysis
Increased Agility and Decreased “Time to Market”– Ability to rapidly deploy scalable “Views for Purpose”
Improved Governance & Compliance– Solve for CONTEXT of use, and consistent policy execution / compliance event propagation
Gartner’s latest hype cycle for Master Data Management states:By 2012, master data management (MDM) will lead to a 60% reduction in costs associated with the elimination of redundant master data.Through 2012, 70% of SOA projects in complex, heterogeneous environments will fail to yield expected business benefits unless MDM is included.Through 2012, due to the lack of a sufficiently business-oriented approach, appropriate governance and an accompanying metrics structure, 60% of MDM programs will be regarded as failures