Your SlideShare is downloading. ×
0
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Optimizing the Benefits of EDM and SOA by Coordinating Strategies
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Optimizing the Benefits of EDM and SOA by Coordinating Strategies

1,459

Published on

Demonstrates the benefits of coordinating an organization\'s EDM and SOA strategies, then introduces a new C-SODA Framework and Capability Maturity Model for doing so, and shows one example of how to …

Demonstrates the benefits of coordinating an organization\'s EDM and SOA strategies, then introduces a new C-SODA Framework and Capability Maturity Model for doing so, and shows one example of how to use Oracle technologies in this situation.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,459
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Transcript

    • 1. Optimizing the Benefits of EDM & SOA by Coordinating these Strategies: The Power of Synergistic Data and Services (with the C-SODA Framework and Maturity Model) Keith R. Worfolk Sr. Architect, Hitachi Consulting [email_address] April 16, 2008
    • 2. Table of Contents <ul><li>Case for Coordinated EDM and SOA Strategies </li></ul><ul><li>Summary of Key EDM and SOA Strategy Coordination Points </li></ul><ul><li>C-SODA Framework for Coordinated EDM and SOA Strategies </li></ul><ul><li>C-SODA Capability Maturity Model </li></ul><ul><li>Next Steps and Opportunities </li></ul><ul><li>Q & A </li></ul><ul><li>Appendix: Coordinated EDM – SOA w/ Oracle Tools & Products </li></ul>
    • 3. Case for Coordinated EDM and SOA Strategies <ul><li>Information Quality Management is a major component of SOA! </li></ul>
    • 4. SOA and Data Dependencies – The CIO Perspective <ul><li>More than half of CIOs surveyed say that Customer Data Integration and Master Data Mgmt (MDM) are key business drivers for their SOA projects. </li></ul><ul><li>Right behind these are (also data-centric) Business Analytics and Knowledge Management business drivers. </li></ul><ul><li>Majority of interviewees noted that SOA creates interdependencies between systems </li></ul><ul><li>demanding high-quality & consistent data, suggesting full benefit of SOA cannot be realized if projects don’t incorporate an EDM strategy to address widespread and expensive problem of data inconsistency and inaccuracy. </li></ul><ul><li>Without a service-oriented data-centric architecture, SOA can result in bad data being propagated to more applications and users, much faster than ever before. </li></ul>IDG Research Services, 2008
    • 5. “ The Perfect Storm” for EDM and SOA
    • 6. <ul><li>Data Governance </li></ul><ul><ul><li>Organization: Define roles, responsibilities and communication protocol for data stewardship across the enterprise and its applications </li></ul></ul><ul><ul><li>Process: Define common processes and policies for managing enterprise data definitions, maintenance, and usage, especially for Master Data and common Metadata </li></ul></ul><ul><li>Master Data Management (MDM) </li></ul><ul><ul><li>Enterprise-wide tools to manage and enforce a common repository of master data hierarchies business entities and business metric definitions. </li></ul></ul><ul><li>Metadata Management </li></ul><ul><li>Domain-specific tools that: </li></ul><ul><ul><li>Establish business process and business rules definitions </li></ul></ul><ul><ul><li>Inventory data and services </li></ul></ul><ul><ul><li>Enable data and services reuse </li></ul></ul><ul><ul><li>Support consolidation of data and services </li></ul></ul><ul><ul><li>Captures security classifications and assignments </li></ul></ul><ul><li>Enterprise Information Architecture (EIA) </li></ul><ul><ul><li>Design enterprise data architecture, Master Data, and metadata definitions and structures, tables, staging mechanisms, and both application OLTP and data warehouse logical architectures to support enterprise-wide data sourcing, analysis, and transition </li></ul></ul>Enterprise Data Management (EDM) Components EDM: The overarching framework of ongoing processes and organizational interactions that define, integrate, manage, prioritize, and measure the business value of enterprise data over time <ul><li>Data Security / Privacy </li></ul><ul><ul><li>Establish / Maintain privacy rights policy and controls </li></ul></ul><ul><ul><li>Determine access rights, audit and control mechanisms for MDM and Governance concerns </li></ul></ul><ul><li>Data / Process Monitoring and Controls </li></ul><ul><ul><li>Implement point-to-point controls to ensure data integrity from data acquisition through reporting </li></ul></ul><ul><ul><li>Implement business controls to validate information content based on defined variance thresholds </li></ul></ul><ul><li>Data Quality / Profiling / Metrics </li></ul><ul><ul><li>Define key metrics to evaluate an overall measure of the data quality (e.g. consistent, complete, accurate) </li></ul></ul><ul><ul><li>Implement data profiling tools and define processes and roles for data source analysis, business rules definition, and data cleansing and augmentation </li></ul></ul>An EDM initiative is generally comprised of selected components from this framework. Legend Primary EDM – SOA Coordination Component Secondary EDM – SOA Coordination Component
    • 7. Enterprise Information Architecture (EIA) Business Processes Organization Governance Metadata Management Data Integration Data Quality Enterprise Information Architecture Service Oriented Architecture Transaction Data Data Warehouse Master Data Management
    • 8. EDM Framework and Component Considerations <ul><li>Data Governance , MDM , Metadata Mgmt , & EIA have primary impacts & dependencies on SOA strategies. </li></ul><ul><li>Applications & Services in a SOA environment need consistent Data. If there is insufficient Data Quality or Integrity, and duplicate or wrong records or inconsistent data definitions are the norm, then Services that span multiple transactions cannot function well or be reused with confidence. </li></ul><ul><li>An organization pursuing an EDM or SOA strategy should ask: </li></ul><ul><ul><li>If pursuing one strategy, is the other underway or anticipated near future? </li></ul></ul><ul><ul><li>Which Service-related Data & Metadata associated w/ SOA Strategy should be considered for Data Management within an EDM strategy? </li></ul></ul><ul><ul><li>Which Data should be Service-enabled and for what purposes? </li></ul></ul><ul><ul><li>Data Governance should be applied & coordinated w/ SOA </li></ul></ul><ul><ul><li>Governance for ALL Master Data and selected Metadata utilized by Services. </li></ul></ul><ul><ul><li>SOA Governance should be applied & coordinated w/ Data </li></ul></ul><ul><ul><li>Governance for all managed Service – Data relationships & related Services </li></ul></ul><ul><ul><li>initiatives and releases </li></ul></ul>
    • 9. Service-Oriented Architecture (SOA) Components A SOA initiative is generally comprised of selected components from this reference architecture.
    • 10. SOA Component Considerations <ul><li>SOA Governance , Workflow Mgmt & Business Rules , Access & Security Services , Enterprise Business Services , ESB , & Enterprise Data Platform Services have primary impacts & dependencies on EDM strategies. </li></ul><ul><li>SOA Governance – Data Governance processes ensure Services use right Data & Metadata, and any proliferation of Data for Services is managed for quality. </li></ul><ul><li>Workflow Management & Business Rules – Metadata Mgmt includes commonly managed automation and workflow routing rules, SLAs, and Business Rules. </li></ul><ul><li>Access & Security Services – MDM includes security classifications for Master Data & user types, while Metadata Mgmt includes descriptions & rules for handling of each classification for Services & Data. </li></ul><ul><li>Enterprise Business Services – MDM ensures availability & controlled releases of Master Data for business services, whether fine-grained Data access or composite services. Metadata Mgmt similarly ensures business services utilize appropriate Metadata. EIA is directly referenced & influenced by releases. </li></ul><ul><li>ESB – Metadata Mgmt drives rules & config. of ESB for transaction processing. </li></ul><ul><li>Enterprise Data Platform Services – MDM & EIA have similar impacts as for Enterprise Business Services. </li></ul>
    • 11. SOA Best Practices Considerations <ul><li>Another way to consider SOA strategy impacts to and synergies with EDM is by exploring how organizations achieve SOA best practices.  </li></ul><ul><li>According to Gartner, the following are key best practices when pursuing a SOA strategy. Note that most of these SOA Best Practices also apply as EDM Best Practices as well. </li></ul><ul><li>Top 6 Best Practices for a SOA (or EDM) strategy: </li></ul><ul><ul><li>When thinking about Services, don’t forget to consider the Data </li></ul></ul><ul><ul><li>Focus on avoiding proliferation of unshareable services </li></ul></ul><ul><ul><li>Reward both reusability and reuse </li></ul></ul><ul><ul><li>When establishing Governance, stay away from dictatorships </li></ul></ul><ul><ul><li>Establish a COE to provide guidance, governance, and coordination </li></ul></ul><ul><ul><li>Invest in systematically designed sets of fundamental core services initially, allowing for rapid opportunistic extensions later. </li></ul></ul>
    • 12. 1. When Thinking About Services, Don’t Forget to Consider the Data <ul><li>Four degrees of Service – Data Normalization, from immature to mature orgs: </li></ul><ul><li>Service–Data Normalization maturity levels are part of overall maturity model for coordinated EDM & SOA programs. </li></ul><ul><li>Evolution towards greater Service – Data Normalization maturity will primarily be facilitated by coordination of: </li></ul><ul><ul><li>Data Governance with SOA Governance organizations and programs </li></ul></ul><ul><ul><li>MDM, Metadata Management, and EIA with the SOA initiatives’ enterprise services architecture and development teams </li></ul></ul><ul><li>Forgetting the Data in Services design can result in Services that deliver poor performance, information, or application integrity. Strive to design Services coordinated with design model of underlying Data stores and reach at least Encapsulation level of Service – Data Normalization maturity. </li></ul>“ Wild West” Ownership / Stewardship Encapsulation Object <ul><li>Virtually non- existent or Ad Hoc (pockets of) Normalization </li></ul><ul><li>Service Design Builds Upon the Data Design </li></ul><ul><li>Service and Data Designs are Jointly Coordinated </li></ul><ul><li>Service and Data Designs are One & the Same. </li></ul><ul><li>Service implementation takes Data Ownership to another level where its Master Data value is known only inside Service implementation. </li></ul>
    • 13. 2. Focus on Avoiding the Proliferation of Unshareable Services <ul><li>Without managed Data coordination within SOA initiatives: </li></ul><ul><ul><li>Services inadvertently propagate non-”gold standard” data copies to consumers of Services that are created or updated by initiatives. These are unshareable!! </li></ul></ul><ul><ul><li>Worse, architects & developers may create their own data stores to support their Services, further propagating unmanaged Data, and damaging BOTH strategies!! </li></ul></ul><ul><li>Avoiding unshareable services implies coordination is required for: </li></ul><ul><ul><li>Data Governance with SOA Governance organizations, roles, and processes </li></ul></ul><ul><ul><li>EIA and its Enterprise Data Model, with the SOA Services Portfolio and release mgmt </li></ul></ul><ul><ul><li>MDM & Metadata Mgmt w/ SOA initiatives’ design, including the Data Services layer </li></ul></ul><ul><li>One way to ensure proliferation of only shareable Services is by avoiding proliferation of unshareable Data by Services. When MDM , Metadata Mgmt , & Data Governance are coordinated with Service design and release mgmt, thus SOA Governance , Services are developed to only utilize “gold standard” Data sources. </li></ul>
    • 14. 3. Reward Both Reusability and Reuse <ul><li>Reusability applies to Services & Data, both in development & consumption. </li></ul><ul><li>In some cases, SOA Governance will advocate the development of a new or improved Service when it makes business sense. Data Governance usually advocates reuse of existing Master Data or Metadata, but decreasingly over time there may be reasons to alter the “gold standard” Data. </li></ul><ul><li>Reuse should be enforced, and Best Practices established, by Data & SOA Governance . Governance services include identifying Data / Services to be reused in initiatives, and criteria for when new Data / Services are justified. </li></ul><ul><li>To properly reward reusability and reuse, coordination is required for: </li></ul><ul><ul><li>Data Governance with SOA Governance organizations, roles, and processes </li></ul></ul><ul><ul><li>EIA, MDM, & Metadata Mgmt processes & tools with those of Service initiatives’ design </li></ul></ul><ul><li>Reusability & Reuse Incentives should be developed in the organization so – </li></ul><ul><ul><li>Services & Data are designed and implemented for reusability, AND </li></ul></ul><ul><ul><li>Organizational behavior encourages resulting reuse in practice </li></ul></ul>
    • 15. 4. When Establishing Governance, Stay Away From Dictatorships <ul><li>Major Governance approaches from non-existent to Highly Centralized orgs: </li></ul><ul><li>While “Wild West” is a problem in lack of control or coordination, Dictatorship swings pendulum too far to centralization of ALL decisions regarding Assets. </li></ul><ul><li>Definite advantages not having Domains maintain disparate versions of shared or standardized Enterprise-wide assets but control over Domain-specific assets. </li></ul><ul><li>For highly effective Governance, what is needed for an organization is: </li></ul><ul><ul><li>Federated approach to facilitate Domain implementation flexibility, WITH… </li></ul></ul><ul><ul><li>Centralized Governance of shared & standardized Enterprise-wide processes, tools, assets. </li></ul></ul><ul><li>To effectively establish Data – SOA Governance, coordination is required for: </li></ul><ul><ul><li>Data Governance with SOA Governance organizations, roles, and processes </li></ul></ul><ul><ul><li>Enterprise EDM assets w/ enterprise SOA assets (EA, Services Model, & Services Portfolio) </li></ul></ul><ul><ul><li>Enterprise-wide EDM & SOA architecture & design processes and tools </li></ul></ul>“ Wild West” Federated Dictatorship <ul><li>Virtually non-existent or Ad Hoc (pockets of) Governance </li></ul><ul><li>Lack of Enterprise Coordination, but there may be minimal Governance processes and roles developed out of necessity within some Domains. </li></ul><ul><li>Coordinated independent efforts between various Domains. </li></ul><ul><li>Standards, Best Practices, & Tools are inconsistent by Domain. </li></ul><ul><li>Inconsistent Coordination Points w/ Business for Reqts., Testing, etc. </li></ul><ul><li>Centralized Control of all related assets. </li></ul><ul><li>Here everything is coordinated, but at the cost of Domain-specific flexibility. </li></ul>
    • 16. 5. Establish a COE to Provide Governance and Centralized Coordination <ul><li>If an organization doesn’t have COE to support either their EDM or SOA strategies  One should be defined and established to progressively support both EDM & SOA. </li></ul><ul><li>If an org already has a COE  Consider expanding its mission for integrated Data & Services and coordinated best practices & tools within a comprehensive ICC. </li></ul>
    • 17. 6. Invest in Systematically Designed Fundamental Core Services <ul><li>… Allowing for rapid opportunistic extensions later. </li></ul><ul><ul><li>Ensures joint Data – Services program evolves systematically & progressively over time. </li></ul></ul><ul><ul><li>Launch tactical, flexible starting point, pragmatically incorporating scope via Gov., ICC. </li></ul></ul><ul><ul><li>Most key Services will access information from common Data Services layer. </li></ul></ul><ul><li>SOA causes organization to implement EIA & Data Services layer to support Services: </li></ul><ul><ul><li>Provide abstraction b/t producers & consumers, insulating complexity & system changes </li></ul></ul><ul><ul><li>Present consumers actionable, consistent near real-time information & aggregated views </li></ul></ul><ul><ul><li>Centrally manage, monitor, and report on Enterprise view of the Data and Metadata. </li></ul></ul><ul><li>Systematically designing core Services, coordination is required for: </li></ul><ul><ul><li>Data Governance w/ SOA Governance organizations, roles, & processes; and COE / ICC </li></ul></ul><ul><ul><li>EIA & its Enterprise Data Model, with the Services Portfolio & release mgmt </li></ul></ul><ul><ul><li>EIA, MDM, & Metadata Mgmt processes & tools w/ those of Service initiatives’ design </li></ul></ul><ul><li>Organizations evaluate its Data Services layer maturity for systematic design by: </li></ul><ul><ul><li>Are Services impacted by changes to repositories or databases being accessed? </li></ul></ul><ul><ul><li>Do Services typically access 2 or more repositories to read / update information? </li></ul></ul><ul><ul><li>Do Data repositories being accessed contain overlapping or redundant info? </li></ul></ul><ul><ul><li>Can Data Services provide “gold standard” single version of truth for Master Data? </li></ul></ul><ul><ul><li>Is the Enterprise Master Data model exposed for consumption by Data Services? </li></ul></ul>
    • 18. Summary of Key EDM and SOA Strategy Coordination Points <ul><li>With an enlightened SOA approach that consistent w/ EDM objectives, not </li></ul><ul><li>only Services are reused, but also Data; hence, another reason for </li></ul><ul><li>coordinating strategies is to facilitate these natural synergies. </li></ul>
    • 19. Key EDM – SOA Coordination Points from the EDM Perspective <ul><li>Data Governance & Data Stewardship with SOA Governance & Services Stewardship </li></ul><ul><ul><li>Organizational roles, processes, checkpoints, and strategic program and project-level decisions (e.g. for SOA-related Master Data and Metadata) </li></ul></ul><ul><ul><li>Roadmap evolutionary releases for related Services and Data </li></ul></ul><ul><ul><li>Strategic decisions related to Master Data sent by SOA Services and/or over the ESB </li></ul></ul><ul><li>EIA and its Enterprise Data Model with the Services Portfolio and release mgmt </li></ul><ul><ul><li>EIA release management and SOA release management for services utilizing data in the EIA </li></ul></ul><ul><li>MDM and Metadata Mgmt with Services’ initiatives architecture and design </li></ul><ul><ul><li>Data Services layer architecture and designs </li></ul></ul><ul><ul><li>Strategic and tactical decisions related to Master Data sent by SOA Services or over the ESB </li></ul></ul><ul><ul><li>All other related Master Data and Metadata for (Infrastructure, Data, or Business) Services’ designs </li></ul></ul><ul><li>Metadata defined for or used by, and Metadata Mgmt associated with, Service components such as Services’ WSDL , ESB configuration, or security settings) </li></ul><ul><li>EIA , MDM , and Metadata Mgmt processes and tools with SOA Services’ initiatives – </li></ul><ul><ul><li>Organizational processes and roles for EIA, MDM, and Metadata Mgmt with Services’ architecture </li></ul></ul><ul><ul><li>EA release management, including technical architecture supporting the EIA and its databases, the ESB and its integration points to these databases, other data sources, and data consumers </li></ul></ul><ul><ul><li>Tools and artifacts for EIA, MDM, and Metadata Mgmt with SOA architecture tools, artifacts </li></ul></ul><ul><li>EIA , MDM , & Metadata Mgmt w/ SOA initiatives’ Enterprise Services development – </li></ul><ul><ul><li>Initiative processes & roles for EIA, MDM, & Metadata Mgmt w/ Services initiatives’ design processes & roles </li></ul></ul>
    • 20. Key EDM – SOA Coordination Points from the SOA Perspective <ul><li>SOA Governance & Services Stewardship with Data Governance & Data Stewardship </li></ul><ul><ul><li>Organizational roles, processes, & strategic program / project decisions (e.g. for SOA-related Master Data) </li></ul></ul><ul><ul><li>Roadmap release management for related Services and Data </li></ul></ul><ul><ul><li>Strategic decisions related to Master Data sent by SOA services and/or over the SOA ESB </li></ul></ul><ul><li>SOA Services Portfolio and release mgmt with the EIA and its Enterprise Data Model </li></ul><ul><ul><li>Roadmap evolutionary releases for related Services and Data </li></ul></ul><ul><ul><li>SOA release management with EIA release management for the services utilizing data in the EIA </li></ul></ul><ul><li>Services’ design with Master Data defined for, and MDM associated with, these – </li></ul><ul><ul><li>Strategic and tactical decisions related to SOA services and the ESB that utilizes Master Data </li></ul></ul><ul><li>Service initiatives’ architecture and designs with MDM and Metadata Mgmt </li></ul><ul><ul><li>Service designs associated with the Data Services layer </li></ul></ul><ul><ul><li>SOA designs related to Master Data & Metadata for Enterprise Infrastructure, Data, and Business Services </li></ul></ul><ul><li>Services with related Metadata defined for these, and associated Metadata Mgmt </li></ul><ul><ul><li>SOA components’ (e.g. Services’ WSDL and ESB configuration or security settings) associated Metadata </li></ul></ul><ul><li>Services’ initiatives design processes and tools with EIA , MDM , and Metadata Mgmt </li></ul><ul><ul><li>Organizational processes & roles for Services’ design with those for EIA, MDM, and Metadata Mgmt </li></ul></ul><ul><ul><li>EA release management including the technical architecture supporting the ESB and its integration points to data stores and data consumers, as well as the EIA and its database references </li></ul></ul><ul><ul><li>Tools and artifacts for Services’ architecture tools & artifacts with EIA, MDM, and Metadata Mgmt </li></ul></ul><ul><li>SOA initiatives’ Enterprise Services development teams with EIA , MDM , & Metadata Mgmt </li></ul><ul><ul><li>Initiative-level SOA services architecture processes & roles with EIA, MDM, and Metadata Mgmt </li></ul></ul>
    • 21. Other Coordination Points in a Mature EDM – SOA Environment <ul><li>COE / ICC with Data – SOA Governance , EIA & Enterprise Data Model </li></ul><ul><ul><li>COE / ICC with Data & SOA Governance processes & roles </li></ul></ul><ul><ul><li>COE / ICC Roadmap development & releases w/ EIA releases & Enterprise Data Model </li></ul></ul><ul><li>COE / ICC with the SOA Services Portfolio and release management </li></ul><ul><ul><li>COE / ICC) roadmap development & releases w/ SOA Services Portfolio & release mgmt </li></ul></ul><ul><li>PMO prioritization, decision criteria, and status reporting for EDM & SOA initiatives, including COE / ICC-related activities and releases </li></ul>
    • 22. Significant MDM and SOA Dependencies & Synergies <ul><li>Master Data is not all Data, just that required for sharing, standardization. It infrequently changes & often referenced by business processes, events, transactions, & reusable Services. This is MDM’s undeniable linkage to SOA. </li></ul><ul><ul><li>MDM encompasses areas such as CDI and PIM, which have Services implications. Through 2010 Gartner predicts 60% of organizations implementing CDI & PIM initiatives will link these efforts as part of an EDM strategy. </li></ul></ul><ul><ul><li>Need for MDM often identified within EIA of overall EDM or EA initiative. Lack of consistent & accurate information is barrier to enterprise agility, operational efficiency. </li></ul></ul><ul><ul><li>Using Enterprise Data Model as jump-start, scope of Master Data includes core subject area elements & standard Services for MDM change mgmt & Governance. </li></ul></ul><ul><li>First step when creating service-oriented apps is aligning Master Data & Metadata as a precursor to SOA designs. Without a focus on MDM : </li></ul><ul><ul><li>Impossible to communicate information about transactions w/ no common understanding of basic business objects to which Services and events refer. </li></ul></ul><ul><ul><li>Services don’t know where to access “gold standard” version of truth for Master Data </li></ul></ul><ul><ul><li>Data still has to be the same between producers & consumers of Services </li></ul></ul><ul><li>Technical intersection of MDM w/ SOA is in Enterprise Data & Metadata Svcs </li></ul><ul><ul><li>MDM provides the necessary semantic integration of Services for Master Data. </li></ul></ul><ul><ul><li>Services provide consistent information to consumers across multiple Data Providers. </li></ul></ul>
    • 23. C-SODA Framework for Coordinated EDM and SOA Strategies <ul><li>SOA naturally exposes Data issues to more people, processes, & integrated systems. Focus on EDM is further needed when supporting a SOA strategy. Via EDM, organizations achieve information asset consistency, accuracy, & integrity in support of strategic initiatives, incl. migration to SOA environment. </li></ul>
    • 24. The C-SODA Framework for Coordinated EDM and SOA Strategies <ul><li>Both Framework and Maturity Model introduced here are based upon a Coordinated Service-Oriented Data Architecture . The C-SODA is built upon data architecture , as the pertinent data architectural aspects that support a service-oriented environment . </li></ul><ul><li>The C-SODA Framework is not intended to supplant full-fledged EDM or SOA frameworks or maturity models. Instead, it complements these by specifically identifying the dependencies and synergies , as well as the evaluation criteria and maturity phases, of appropriately coordinated EDM – SOA strategies . </li></ul><ul><li>The C-SODA is intended to gauge & drive an organization’s strategic readiness for necessary coordination and maturity along the Framework’s dimensions in both EDM and SOA domains . </li></ul>
    • 25. Coordinated Service-Oriented Data Architecture (C-SODA) Framework Overview WHAT WHO HOW <ul><li>EDM and SOA programs are inherently complex. To be successful, they require careful planning and execution along several interdependent dimensions. Further, when these programs are to be executed in parallel (the case for many companies), coordination between EDM and SOA concerns is also required to promote success. </li></ul><ul><li>Hitachi Consulting uses a proven framework to evaluate 7 critical dimensions that determine the strategic readiness of an EDM, SOA, or Coordinated Service-Oriented Data Architecture (C-SODA) program: </li></ul><ul><ul><li>Strategy — Are the high-level overarching business strategies clearly described, and how do these impact decisions about data and services? </li></ul></ul><ul><ul><li>Process — Are the core business and IT processes effective, efficient, and supportive in managing strategic data and services? </li></ul></ul><ul><ul><li>Metrics — Is the right mix of measures for key performance indicators utilized? </li></ul></ul><ul><ul><li>Data — Is the right data and metadata available to support core processes and strategic services? </li></ul></ul><ul><ul><li>Services / Applications — Does the software and systems enhance core processes and enable reusable Services and Data? </li></ul></ul><ul><ul><li>Architecture — Is the correct infrastructure & enterprise architecture in place to support the business with necessary Data and Services? </li></ul></ul><ul><ul><li>People — Are the human and organizational capital applied to core processes appropriate and sufficient? </li></ul></ul>Hitachi Consulting Framework for Assessing Strategic Readiness of EDM and SOA Programs Strategy Metrics Data Services / Applications Architecture People Process While all framework dimensions would be addressed in detail for an EDM or SOA Strategy Roadmap, we primarily focus on the Process, Architecture, and Data components in the context of coordinating EDM and SOA program objectives, dependencies, and synergies. The other components are referenced secondarily within the C-SODA framework.
    • 26. Primary & Secondary Dimensions & Components of the C-SODA Framework Strategy Data Services / Applications Architecture People Hitachi’s framework considers the interrelationships between key building blocks Metrics Process Business IT <ul><li>Business Alignment </li></ul><ul><li>Breadth </li></ul><ul><li>Accessibility </li></ul><ul><li>Functionality </li></ul><ul><li>(Re)Usability </li></ul><ul><li>Composability </li></ul><ul><li>Breadth </li></ul><ul><li>Metadata </li></ul><ul><li>Supportability </li></ul><ul><li>Performance </li></ul>IT <ul><li>Narrow Footprint </li></ul><ul><li>Integration </li></ul><ul><li>Security </li></ul><ul><li>Scalability </li></ul><ul><li>Performance </li></ul><ul><li>Manageability </li></ul><ul><li>Adaptability </li></ul><ul><li>Reliability </li></ul><ul><li>Usability </li></ul><ul><li>Accessibility </li></ul>Business IT <ul><li>Visibility </li></ul><ul><li>Timeliness </li></ul><ul><li>Depth/Granularity </li></ul><ul><li>Breadth </li></ul><ul><li>Metadata </li></ul><ul><li>Services Definitions / Metadata </li></ul><ul><li>Master Data </li></ul><ul><li>Metadata Management </li></ul><ul><li>Integration </li></ul><ul><li>Quality/Auditibility </li></ul><ul><li>Augmentation </li></ul><ul><li>Security </li></ul><ul><li>Data Model / Architecture </li></ul>Business and IT <ul><li>Organization </li></ul><ul><li>Leadership </li></ul><ul><li>Roles & Responsibilities </li></ul><ul><li>Skills and Alignment </li></ul><ul><li>Competencies and Experiences </li></ul><ul><li>Accountability and Incentives </li></ul><ul><li>Individual Performance Evaluations </li></ul><ul><li>Communication and Teamwork </li></ul><ul><li>Retention/Attrition </li></ul>Business and IT <ul><li>Metadata </li></ul><ul><li>Adoption </li></ul><ul><li>Actionable </li></ul><ul><li>Accountability </li></ul><ul><li>Appropriateness </li></ul><ul><li>Balance </li></ul><ul><li>Linkage </li></ul><ul><li>Predictive Value </li></ul><ul><li>Alignment </li></ul><ul><li>Cascading </li></ul><ul><li>Measurability </li></ul><ul><li>Calculations </li></ul><ul><li>Definition </li></ul><ul><li>Consistency </li></ul>Business IT <ul><li>Leadership Rhythms </li></ul><ul><li>Target Setting </li></ul><ul><li>Initiative Prioritization and Funding </li></ul><ul><li>Program Governance </li></ul><ul><li>Governance Coordination </li></ul><ul><li>Program Mgmt Office (PMO) </li></ul><ul><li>Standards & Guidelines </li></ul><ul><li>Data Stewardship </li></ul><ul><li>Service Stewardship </li></ul><ul><li>Change Management </li></ul><ul><li>Policies and Procedures </li></ul><ul><li>Services Model </li></ul><ul><li>Release Management </li></ul><ul><li>EDM – SOA Initiatives Mgmt </li></ul><ul><li>COE / ICC Mgmt </li></ul>Business IT <ul><li>Strategy Map </li></ul><ul><li>Themes/Alignment </li></ul><ul><li>Objectives </li></ul><ul><li>Initiatives </li></ul><ul><li>Annual Plan </li></ul><ul><li>Multi Year Plan </li></ul><ul><li>Data Ownership/Stewardship </li></ul><ul><li>Vision and Alignment to Themes </li></ul><ul><li>Multi Year Plan </li></ul><ul><li>Annual Plan </li></ul><ul><li>Capital Investment vs. Operational Support Approach </li></ul>
    • 27. Fine-Tuning and Utilizing the C-SODA Framework for Your Organization <ul><li>Determine Primary and Secondary dimensions, and further determine the dimensional components for consideration. This is the C-SODA that will be used for your organization, or at least for the program or initiative under consideration. </li></ul><ul><li>Evaluate current state of your coordinated EDM – SOA strategies. </li></ul><ul><ul><li>Detailed as necessary to drive granularity of capabilities & potential initiatives for maturity. </li></ul></ul><ul><ul><li>Rate each dimension and component for the current state capabilities relative to a desired current state; note this is not the desired future state, but instead a readout of how well the EDM – SOA Process , Architecture , & Data dimensions & components meet current needs. </li></ul></ul><ul><ul><li>Typically a color-coded ( red , yellow , green ) or numbered rating system will be used to rate each component, summarized by dimension; utilize whatever ratings work best in your organization. </li></ul></ul><ul><li>Inventory the initiatives that are underway or expected to start soon for which improvements will be made to current state ratings. </li></ul><ul><li>Determine desired future vision based upon same C-SODA Framework. </li></ul><ul><ul><li>For short, intermediate, or long-term goals as needed; if a long-term goal is desired, it is useful to break this down into what will be accomplished at key intermediate points. </li></ul></ul><ul><li>Determine gaps to be filled between the current state, plus known initiatives, & future vision of C-SODA, perhaps further granulized into intermediate steps. </li></ul><ul><li>Evaluating gaps in C-SODA capabilities, develop detailed initiatives definitions. </li></ul><ul><li>Prioritize / Schedule gap-filling Roadmap initiatives to achieve desired C-SODA capabilities. </li></ul>
    • 28. C-SODA Capability Maturity Model <ul><li>EDM & SOA are integral parts of the same EA puzzle, and neither can mature successfully without the other. As with the many dependencies and synergies for the simultaneous implementation of these strategies, a common Framework and Maturity Model lends to the evaluation of an organization’s readiness as well as the planning of Roadmap initiatives for these strategies & capabilities in a coordinated fashion. </li></ul>
    • 29. Future Vision – Conceptual Service-Oriented Data Architecture (SODA) etc. Metadata Mgmt Data Metadata Services Metadata 3 rd Party / B2B Business Rules SOA / ESB EIA / Data Integration Layer Workflow Management - EAI Orchestration SOA / ESB Services & Data Hubs Business Rules Coordinated EDM-SOA Strategy (Business Alignment, Roadmap, Vision) PMO, Methodologies (Prioritization, Funding, Delivery) Data-SOA Governance (Stewardship, Master Data, Shared Metadata, Services, ICC, Stds & Practices) Coordinated Architecture (Master Data, Metadata, Security, Services Management, ICC, Tools) User Experience / Presentation Layer / Bus. Intelligence User Portals, Dashboard, Reporting UI Operational / Third-Party Systems Siebel Oracle PeopleSoft Data Warehouse (EDW) Master Data Mgmt Data Mining / Profiling ETL Operational Data Store (ODS) Services & Data Hubs Workflow Management - EAI Orchestration
    • 30. C-SODA Capability Maturity Model: Building Blocks Data Ownership / Stewardship Enterprise Information Optimization Initiation – Data Foundation Data Services Enablement Data & Services Agility Data & Services Reuse Data Definitions Data Monitoring, Controls & Balancing Data Quality Management Metadata Management EIA & Enterprise Data Model “ Gold Standard” Data Sources Master Data Management (MDM) Business Process Management (BPM) & Orchestration Enterprise Business Services (SOA) Business Rules Engine Driven Corporate Performance Management (CPM) Data Governance Enterprise Business Intelligence Integrated Data – SOA Governance Enterprise Infrastructure Services (e.g. CRUD) Enterprise Data Mgmt (EDM) Enterprise Data Platform Services (e.g. ETL) Workflow Management Services (SOA) Service-Oriented Data Architecture (SODA) Data & Services Managed as Corporate Assets Centralized Managed Enabled Optimized C-SODA Strategy Phases: Converging Enterprise Data Integration (ESB/SOA) Data Transformation Enterprise Data Services (e.g. Access, Monitoring) Business Value
    • 31. Business value of EDM – SOA environments grow slowly in early phases as organizations consolidate Data, deliver Services providing consistent information, and empower users w/ reliable and reusable Services. Value accelerates in later phases as C-SODA becomes an enterprise-wide philosophy driving critical processes & competitive advantage. <ul><li>Most organizations have reached some degree of centralized Data sources, but still have inconsistent management of common Data and Services </li></ul>C-SODA Capability Maturity Model: EDM View Initiation “ Keep The Lights On” Deployment “ Build The Foundation” Agility “ Expand Capabilities” Data & Services Managed as Corporate Assets Framework Dimension C-SODA Strategy Phase: Disparate Converging Centralized Managed Enabled Optimized Process <ul><li>Manual data reconciliation </li></ul><ul><li>Short-term firefighting </li></ul><ul><li>Ad-hoc workflow </li></ul><ul><li>Repeatable Data reconciliations </li></ul><ul><li>Data discovery techniques </li></ul><ul><li>Start MD analysis </li></ul><ul><li>Data Governance matures </li></ul><ul><li>SOA Governance emerges </li></ul><ul><li>Single version of selected business rules </li></ul><ul><li>Reactive processes </li></ul><ul><li>Integrated Data-SOA Governance emerges </li></ul><ul><li>Focused initiatives to improve information quality and delivery </li></ul><ul><li>BPM & Orchestration </li></ul><ul><li>Proactive Data & Services analysis, alerts </li></ul><ul><li>Quality measurable, linked to strategy </li></ul><ul><li>Integrated Data-SOA Governance matures </li></ul><ul><li>Corporate Performance Mgmt </li></ul><ul><li>Closed-loop data / services integrity (e.g. TQM) </li></ul>Services / Applications <ul><li>Functional Module Structured Analysis & Des. </li></ul><ul><li>Opportunistic, un-reusable apps, services, & data </li></ul><ul><li>O-O Modeling </li></ul><ul><li>Some reusable services, data </li></ul><ul><li>No central coordination b/t services and/or data </li></ul><ul><li>Component-Based Dev. </li></ul><ul><li>Reusable Infrastructure & Data Services emerge </li></ul><ul><li>Data Services layer established </li></ul><ul><li>Service-Oriented Model </li></ul><ul><li>Business Services emerge, evolve </li></ul><ul><li>Data-Service Normalization emerges </li></ul><ul><li>Process Integration via BPM & Composite Business Services </li></ul><ul><li>Data-Service Normalization matures </li></ul><ul><li>Dynamic Assembly & Process Integration of Composite Apps via Business Grammar Modeling & Context-Aware Invocation </li></ul>Architecture <ul><li>Use any and all partial architectures that you have </li></ul><ul><li>Few services and little reusability </li></ul><ul><li>Limited, disconnected domains architected without an enterprise view </li></ul><ul><li>Many disparate platforms, technologies, toolsets </li></ul><ul><li>Shared integration points between domains </li></ul><ul><li>Long-term vision of enterprise emerges </li></ul><ul><li>Technologies and Tools become relevant and shared between domains </li></ul><ul><li>Common Enterprise Architecture view </li></ul><ul><li>Business Services emerge </li></ul><ul><li>Enterprise Infrastructure Services established </li></ul><ul><li>Workflow integration becomes relevant </li></ul><ul><li>Common technologies, tools, and best practices </li></ul><ul><li>ESB emerges </li></ul><ul><li>Integrated Workflow Business Rules emerge </li></ul><ul><li>Services Stewardship </li></ul><ul><li>EA centrally managed by Arch. / SOA Governance </li></ul><ul><li>Prescribed technologies, arch. tools, practices </li></ul><ul><li>Workflow integration tools, best practices </li></ul><ul><li>Enterprise Business Services established </li></ul><ul><li>Workflow Mgmt Services </li></ul><ul><li>Business Rules Engine </li></ul><ul><li>EA version-controlled & evolved according to plan </li></ul><ul><li>Maturing std technologies, tools, and practices </li></ul><ul><li>Shared Domain Reference Architectures </li></ul><ul><li>Service-Oriented Data Arch. </li></ul><ul><li>EA managed to future state with planned / managed initiatives for intermediate target releases (Roadmap) </li></ul><ul><li>EA-integrated Workflow Mgmt & supporting Business Rules in planned releases </li></ul><ul><li>Architectural tools, processes are performance-driven </li></ul>Data <ul><li>Use what data you have </li></ul><ul><li>Limited data integration </li></ul><ul><li>Reconciliation sheets </li></ul><ul><li>No centralized governance, prescribed tools, practices </li></ul><ul><li>Data Governance emerges </li></ul><ul><li>Long-term data vision </li></ul><ul><li>Data Stewardship established </li></ul><ul><li>Data Quality Mgmt </li></ul><ul><li>Data Governance adopted across domains </li></ul><ul><li>MDM emerges </li></ul><ul><li>Metadata Mgmt emerges </li></ul><ul><li>Common data tools </li></ul><ul><li>EIA, Ent. Data Model </li></ul><ul><li>EDM emerges </li></ul><ul><li>Enterprise Data Services </li></ul><ul><li>Std. Data Transformation </li></ul><ul><li>Tools incorporated into broader data architecture (e.g. MDM, data profiling) </li></ul><ul><li>Standardized data tools, best practices prescribed </li></ul><ul><li>Domain-specific master data analysis (CDI, PDI) </li></ul><ul><li>EDM matures </li></ul><ul><li>Enterprise Business Intelligence (BI) </li></ul><ul><li>Process and tools are integrated </li></ul><ul><li>Advanced statistical analytics </li></ul>Business Value
    • 32. Emerging Enterpr. Asset Portfolio Mgmt, Org Strategic Enterprise & Coordinated Governance Dynamically aligned Skills & Asset Portfolio Mgmt via Strategic Governance Services / Applications Metrics Process People Data Strategy Functional Module Structured Analysis & Design Svc-Oriented Modeling, Bus. Svcs, Svc-Data Normalization Dynamic Assembly & Process Integration of Context-aware Composite Apps via Bus. Grammar Modeling Component Dev., Reusable Infra. / Data Services O-O Modeling, Some Reusability Ad Hoc LOB-Specific Emerging Strategic cross-LOB & Governance Automated, Evolving, & Configurable Enterprise-wide w/ Coordinated Gov. Common cross-LOB for short-term Governance needs Ad Hoc Enterprise-wide Ad Hoc LOB IT Strategy & Governance Integrated Data-SOA Gov., part of overall IT Gov. Evolving Data-SOA & IT Governance via Policy, Corp. Performance Mgmt Common IT, Data, SOA Strategy & Governance Ad Hoc Enterprise IT Strategy, Data Gov. emerges Maturing Data-SOA Governance, BPM & Orchestration via Bus. Rules Process Integration via BPM & Composite Services LOB-Specific Functional Skills & Organization Strategic cross-LOB & IT Enterpr. Mgmt, Org Shared LOB / Enterprise Skills & Organization Application-Specific Information As a Service Virtualized Data Services and Semantic Data Vocabularies Canonical Enterprise Models LOB or Enterprise Specific Enterprise Business Data Dictionary & Repository Isolated Business Line Driven Componentized Business and Services Mix & match Business and context-aware capabilities for independent svc centers Componentized Business Business Process Integration Processes through service composition Monolithic Architectures, LOB-Specific Emerging Project-Based SOA Dynamically Re-Configurable SOA Environ. w/ Virtualization Component Arch. w/ common reusable infrastr. Layered Architecture w/ Enterprise Stds. Common Shared SOA Environment Architecture C-SODA Capability Maturity Model: SOA View Silos Strategic Enterprise Asset Portfolio and Skills Mgmt & Org Initiation “ Keep The Lights On” Deployment “ Build The Foundation” Agility “ Expand Capabilities” Business Value Disparate Managed Enabled Optimized Centralized Converging Level 0 Level 3 Level 4 Level 5 Level 2 Level 1
    • 33. Next Steps and Opportunities <ul><li>Organizations develop appropriate coordinated Data – SOA Governance and Capability Maturity Model  Job One towards C-SODA capability maturity. </li></ul><ul><li>As a Data / SOA Governance Model is developed / adopted, it should be closely coordinated for processes, checkpoints & stewardship / ownership. </li></ul><ul><li>Coordinated Data – SOA Governance, & progressive Roadmap initiatives, should include all relevant Data sources, Services, and supporting products. </li></ul><ul><li>Periodic C-SODA maturity assessments to evolve EDM – SOA Roadmap </li></ul><ul><li>If an organization has overarching PMO that plans initiatives, coordination should prioritize progressive initiatives towards advanced C-SODA maturity. </li></ul><ul><ul><li>As Governance model & processes are expanded for additional enterprise Data scope and Service areas, related granular processes & checkpoints (e.g. MDM, Metadata Mgmt, and Services – Data Stewardship) should similarly expand and increase maturity.  </li></ul></ul><ul><li>Scale progressive EDM – SOA Maturity Model w/ selected coordinated Roadmap initiatives, Data – SOA Governance; complemented with education to inform EDM & SOA resources how to effectively leverage each other.   </li></ul><ul><li>COE / ICC will further facilitate bringing stakeholders together early & often to drive necessary coordination during all stages of EDM – SOA initiatives.  </li></ul>
    • 34. Thank You Merci Grazie Gracias Obrigado Danke Japanese French Russian German Italian Spanish Brazilian Portuguese Arabic Chinese Hindi Swedish Thai Korean Tack
    • 35. Appendix: Coordinated EDM – SOA with Oracle Tools and Products
    • 36. EDM – SOA Governance & Coordination using Oracle Platform Governance Services Shared Platform Services Web Services Manager Applications Repository Services Registry SOA Suite (Infrastructure, Data, Metadata & Business Services) Application Server Enterprise Manager Grid Control (Run-time Governance) EDM – SOA Governance Services Business Process Analysis Suite (Process Governance, Business Rules) Warehouse Builder (Enterprise Metadata Management) MDM Suite (Customer Data Hub, Product Data Hub)
    • 37. Metadata Management Coordination with the Oracle SOA Platform J2EE Application Server Oracle AS, JBoss, WebLogic, WebSphere Messaging Mediation Legacy Data Quality WS Policies Metadata Repository DATA SERVICES & CONNECTIVITY Apps Adapters Partners B2B RFID SES DB ODI ETL / Bulk Replication Multi Protocol Routing XSLT Transform Enterprise Services Bus (ESB) Native BPEL Business Rules Human Workflow BPEL Process Manager ROUTING & ORCHESTRATION UDDI / Discovery Policies Management Security Web Services Manager Registry GOVERNANCE Events Analytics Business Monitoring System Monitoring Enterprise Manager BAM BI MANAGEMENT & MONITORING App Dev Framework JDeveloper Analyst Tools BPA Suite
    • 38. Metadata Management Coordination with the Oracle BPM Platform Office ROUTING & ORCHESTRATION Forums Wiki Chat Collaboration - Oracle Web Center Content Servers Packaged apps, external services Portlets Forms Process Dashboards Worklist User, Role Directory Process Templates – Oracle Appl. Integration Architecture Metadata Repository BPEL Execution BPM server - Oracle SOA Suite Human WF Rules BAM Model, Simulate & Publish Oracle BPA Suite ESB Generic business processes and Industry specific templates Imaging Integration Content Applications, Legacy sys Image Server Document Services
    • 39. New Human – Services Process Metadata Integration Technical Modeling Oracle SOA Suite BPEL Process Designer Business Modeling Oracle BPA Suite (BPMN, EPC) Conceptual Model Executable Model Logical Model Shared Metadata “ Process Blueprint”

    ×