optimizing the benefits of edm and soa by coordinating strategies

Hitachi Consulting

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 protected]

April 16, 2008

Hitachi Consulting

Inspiring Your Next Success!® 2

Table of Contents

Case for Coordinated EDM and SOA Strategies

Summary of Key EDM and SOA Strategy Coordination Points

C-SODA Framework for Coordinated EDM and SOA Strategies

C-SODA Capability Maturity Model

Next Steps and Opportunities

Q & A

Appendix: Coordinated EDM – SOA w/ Oracle Tools & Products

Hitachi Consulting

Case for Coordinated EDMand SOA Strategies

3

Information Quality Management is a major component of SOA!

Hitachi Consulting

Inspiring Your Next Success!®

SOA and Data Dependencies – The CIO Perspective

4

More than half of CIOs surveyed say that Customer Data Integration and Master Data Mgmt (MDM) are key business drivers for their SOA projects.

Right behind these are (also data-centric) Business Analytics and Knowledge Management business drivers.

Majority of interviewees noted that SOA creates interdependencies between systemsdemanding 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.

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.

IDG Research Services, 2008

Hitachi Consulting


“The Perfect Storm” for EDM and SOA

Hitachi Consulting


Data Governance» Organization: Define roles, responsibilities and

communication protocol for data stewardship across the enterprise and its applications

» Process: Define common processes and policies for managing enterprise data definitions, maintenance, and usage, especially for Master Data and common Metadata

Master Data Management (MDM)» Enterprise-wide tools to manage and enforce a common

repository of master data hierarchies business entities and business metric definitions.

Metadata Management»Domain-specific tools that:

» Establish business process and business rules definitions» Inventory data and services» Enable data and services reuse» Support consolidation of data and services» Captures security classifications and assignments

Enterprise Information Architecture (EIA)» 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

Enterprise Data Management (EDM) ComponentsEDM: The overarching framework of ongoing processes and organizational interactions that define, integrate, manage, prioritize, and measure the business value of enterprise data over time

Data Security / Privacy

» Establish / Maintain privacy rights policy and controls

» Determine access rights, audit and control mechanisms for MDM and Governance concerns

Data / Process Monitoring and Controls» Implement point-to-point controls to ensure data

integrity from data acquisition through reporting» Implement business controls to validate information

content based on defined variance thresholds

Data Quality / Profiling / Metrics» Define key metrics to evaluate an overall measure of

the data quality (e.g. consistent, complete, accurate)» Implement data profiling tools and define processes

and roles for data source analysis, business rules definition, and data cleansing and augmentation

An EDM initiative is generally comprised of selected components from this framework.An EDM initiative is generally comprised of selected components from this framework.

6

LegendPrimary EDM – SOA

Coordination Component

Secondary EDM – SOA Coordination Component

Hitachi Consulting


Enterprise Information Architecture (EIA)

Business ProcessesO

rgan

izat

ion

Go

vern

ance

Metadata Management

Data Integration

Data Quality

Enterprise Information Architecture

Service Oriented Architecture

Transaction Data Data Warehouse

Master Data Management

Hitachi Consulting


EDM Framework and Component Considerations

Data Governance, MDM, Metadata Mgmt, & EIA have primary impacts & dependencies on SOA strategies.

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.

An organization pursuing an EDM or SOA strategy should ask: If pursuing one strategy, is the other underway or anticipated near future? Which Service-related Data & Metadata associated w/ SOA Strategy should be

considered for Data Management within an EDM strategy? Which Data should be Service-enabled and for what purposes?

Data Governance should be applied & coordinated w/ SOA Governance for ALL Master Data and selected Metadata utilized by Services.

SOA Governance should be applied & coordinated w/ Data Governance for all managed Service – Data relationships & related Services initiatives and releases

8

Hitachi Consulting


Service-Oriented Architecture (SOA) Components

Remote Devices

App BApp A

Presentation Services B2B Services

Registry Management

(Registry, Versioning)

Service Management

(Audit, SLA, QOS)

Composite Applications

Application and Data Access Services(EAI , Data Manipulation, Metadata)

Coarse GrainedBusiness Services

Large GrainedBusiness Services

Fine GrainedEnterprise Data and Metadata Services

Access and Security Services

B2B

InfrastructureLDAP, Search, Network and System

Mgmt, Etc.

DepartmentalApplications

Enterprise ApplicationsERP, CRM, Custom, Legacy

Enterprise Data Platform Services and Infrastructure

Enterprise Business Services

MainframeApplications

SOA

Gov

erna

nce

& IT

Ser

vice

s M

anag

emen

t(M

onito

rs, M

anag

es, a

nd S

ecur

es S

ervic

es, A

pplic

ation

s, &

Reso

urce

s)

Enterprise Services Bus (ESB) & Messaging Middleware

Enterprise Services Bus (ESB) & Messaging Middleware

Comm

on In

frastr

uctu

re Se

rvices

(Secu

rity,

Monit

oring

, Log

ging,

Excep

tion H

andli

ng)

Wor

kflo

w M

anag

emen

t Ser

vice

s &

Busi

ness

Rul

es(A

utom

ates

& O

rche

strat

es B

usine

ss P

roce

sses

and

Dat

a Fl

ows)

A SOA initiative is generally comprised of selected components from this reference architecture.A SOA initiative is generally comprised of selected components from this reference architecture.

9

Hitachi Consulting


SOA Component Considerations

SOA Governance, Workflow Mgmt & Business Rules, Access & Security Services, Enterprise Business Services, ESB, & Enterprise Data Platform Services have primary impacts & dependencies on EDM strategies.

SOA Governance – Data Governance processes ensure Services use right Data & Metadata, and any proliferation of Data for Services is managed for quality.

Workflow Management & Business Rules – Metadata Mgmt includes commonly managed automation and workflow routing rules, SLAs, and Business Rules.

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.

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.

ESB – Metadata Mgmt drives rules & config. of ESB for transaction processing. Enterprise Data Platform Services – MDM & EIA have similar impacts as for

Enterprise Business Services.

10

Hitachi Consulting


SOA Best Practices Considerations

Another way to consider SOA strategy impacts to and synergies with EDM is by exploring how organizations achieve SOA best practices.

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.

Top 6 Best Practices for a SOA (or EDM) strategy:

1) When thinking about Services, don’t forget to consider the Data2) Focus on avoiding proliferation of unshareable services3) Reward both reusability and reuse4) When establishing Governance, stay away from dictatorships5) Establish a COE to provide guidance, governance, and coordination6) Invest in systematically designed sets of fundamental core services initially,

allowing for rapid opportunistic extensions later.

11

Hitachi Consulting


1. When Thinking About Services, Don’t Forget to Consider the Data

Four degrees of Service – Data Normalization, from immature to mature orgs:

Service–Data Normalization maturity levels are part of overall maturity model for coordinated EDM & SOA programs.

Evolution towards greater Service – Data Normalization maturity will primarily be facilitated by coordination of:

» Data Governance with SOA Governance organizations and programs

» MDM, Metadata Management, and EIA with the SOA initiatives’ enterprise services architecture and development teams

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.

12

“Wild West” Ownership / Stewardship

Encapsulation Object

Virtually non- existent or Ad Hoc (pockets of) Normalization

Service Design Builds Upon the Data Design

Service and Data Designs are Jointly Coordinated

Service and Data Designs are One & the Same.

Service implementation takes Data Ownership to another level where its Master Data value is known only inside Service implementation.

Hitachi Consulting


2. Focus on Avoiding the Proliferation of Unshareable Services

Without managed Data coordination within SOA initiatives:» Services inadvertently propagate non-”gold standard” data copies to consumers of

Services that are created or updated by initiatives. These are unshareable!!

» Worse, architects & developers may create their own data stores to support their Services, further propagating unmanaged Data, and damaging BOTH strategies!!

Avoiding unshareable services implies coordination is required for:» Data Governance with SOA Governance organizations, roles, and processes

» EIA and its Enterprise Data Model, with the SOA Services Portfolio and release mgmt

» MDM & Metadata Mgmt w/ SOA initiatives’ design, including the Data Services layer

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.

13

Hitachi Consulting


3. Reward Both Reusability and Reuse

Reusability applies to Services & Data, both in development & consumption. 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.

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.

To properly reward reusability and reuse, coordination is required for:» Data Governance with SOA Governance organizations, roles, and processes» EIA, MDM, & Metadata Mgmt processes & tools with those of Service initiatives’ design

Reusability & Reuse Incentives should be developed in the organization so –» Services & Data are designed and implemented for reusability, AND» Organizational behavior encourages resulting reuse in practice

14

Hitachi Consulting


4. When Establishing Governance, Stay Away From Dictatorships

Major Governance approaches from non-existent to Highly Centralized orgs:

While “Wild West” is a problem in lack of control or coordination, Dictatorship swings pendulum too far to centralization of ALL decisions regarding Assets.

Definite advantages not having Domains maintain disparate versions of shared or standardized Enterprise-wide assets but control over Domain-specific assets.

For highly effective Governance, what is needed for an organization is:1. Federated approach to facilitate Domain implementation flexibility, WITH…

2. Centralized Governance of shared & standardized Enterprise-wide processes, tools, assets.

To effectively establish Data – SOA Governance, coordination is required for:» Data Governance with SOA Governance organizations, roles, and processes» Enterprise EDM assets w/ enterprise SOA assets (EA, Services Model, & Services Portfolio)» Enterprise-wide EDM & SOA architecture & design processes and tools

15

“Wild West” Federated Dictatorship

Virtually non-existent or Ad Hoc (pockets of) Governance

Lack of Enterprise Coordination, but there may be minimal Governance processes and roles developed out of necessity within some Domains.

Coordinated independent efforts between various Domains.

Standards, Best Practices, & Tools are inconsistent by Domain.

Inconsistent Coordination Points w/ Business for Reqts., Testing, etc.

Centralized Control of all related assets.

Here everything is coordinated, but at the cost of Domain-specific flexibility.

Hitachi Consulting


5. Establish a COE to Provide Governance and Centralized Coordination

Enterprise Architecture / IT Governance

Enterprise Information Architecture

EDM-SOA COE / ICC

Data Governance

- Enterprise Data Architecture- Master Data Mgmt- Shared Metadata Mgmt- Enterprise Data Model Release Management- Data Stewardship- Data-Service Normalization- Data Quality Mgmt- Data / Metadata Reqts.- Data Architecture & Testing Tools, Best Practices

- Strategic IT Architecture- Systems Architecture- Integration Framework- IT Standards- IT Tools & Best Practices- Systems Change Mgmt- IT Quality Mgmt

- Prototypes / POCs- Services-Data Integration Arch., Dev., & Testing Tools- ICC Systems Mgmt & Integration Tools- ICC Non-Functional Reqts.- ICC Network Mgmt- ICC Database Mgmt- ICC Configuration Mgmt- ICC Environments Mgmt

SOA Governance

- Services Portfolio Mgmt- Business Process Integration & Workflow Mgmt- Business Rules- ESB Configuration- Services Stewardship- Service-Data Normalization- Service / ESB Security Mgmt- Service / Appl. Reqts.- Service Development & Testing Tools, Best Practices

Enterprise Data Model

Data Warehouse

Master Data Models

Online Transaction Databases

Shared Metadata Models

Services Portfolio

Services Repository

ESB Queue

Services Metadata

UDDI Repository

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.

If an org already has a COE Consider expanding its mission for integrated Data & Services and coordinated best practices & tools within a comprehensive ICC.

Hitachi Consulting


6. Invest in Systematically Designed Fundamental Core Services

…Allowing for rapid opportunistic extensions later.» Ensures joint Data – Services program evolves systematically & progressively over time.» Launch tactical, flexible starting point, pragmatically incorporating scope via Gov., ICC.» Most key Services will access information from common Data Services layer.

SOA causes organization to implement EIA & Data Services layer to support Services:» Provide abstraction b/t producers & consumers, insulating complexity & system changes» Present consumers actionable, consistent near real-time information & aggregated views» Centrally manage, monitor, and report on Enterprise view of the Data and Metadata.

Systematically designing core Services, coordination is required for:» Data Governance w/ SOA Governance organizations, roles, & processes; and COE / ICC» EIA & its Enterprise Data Model, with the Services Portfolio & release mgmt» EIA, MDM, & Metadata Mgmt processes & tools w/ those of Service initiatives’ design

Organizations evaluate its Data Services layer maturity for systematic design by:» Are Services impacted by changes to repositories or databases being accessed?» Do Services typically access 2 or more repositories to read / update information?» Do Data repositories being accessed contain overlapping or redundant info?» Can Data Services provide “gold standard” single version of truth for Master Data?» Is the Enterprise Master Data model exposed for consumption by Data Services?

17

Hitachi Consulting

Summary of Key EDM and SOA StrategyCoordination Points

18

With an enlightened SOA approach that consistent w/ EDM objectives, not only Services are reused, but also Data; hence, another reason for coordinating strategies is to facilitate these natural synergies.

Hitachi Consulting


Key EDM – SOA Coordination Points from the EDM Perspective

1. Data Governance & Data Stewardship with SOA Governance & Services Stewardship » Organizational roles, processes, checkpoints, and strategic program and project-level decisions (e.g. for SOA-

related Master Data and Metadata)

» Roadmap evolutionary releases for related Services and Data

» Strategic decisions related to Master Data sent by SOA Services and/or over the ESB

2. EIA and its Enterprise Data Model with the Services Portfolio and release mgmt» EIA release management and SOA release management for services utilizing data in the EIA

3. MDM and Metadata Mgmt with Services’ initiatives architecture and design » Data Services layer architecture and designs

» Strategic and tactical decisions related to Master Data sent by SOA Services or over the ESB

» All other related Master Data and Metadata for (Infrastructure, Data, or Business) Services’ designs

4. Metadata defined for or used by, and Metadata Mgmt associated with, Service components such as Services’ WSDL , ESB configuration, or security settings)

5. EIA, MDM, and Metadata Mgmt processes and tools with SOA Services’ initiatives –» Organizational processes and roles for EIA, MDM, and Metadata Mgmt with Services’ architecture

» 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

» Tools and artifacts for EIA, MDM, and Metadata Mgmt with SOA architecture tools, artifacts

6. EIA, MDM, & Metadata Mgmt w/ SOA initiatives’ Enterprise Services development –» Initiative processes & roles for EIA, MDM, & Metadata Mgmt w/ Services initiatives’ design processes & roles

19

Hitachi Consulting


Key EDM – SOA Coordination Points from the SOA Perspective

1. SOA Governance & Services Stewardship with Data Governance & Data Stewardship » Organizational roles, processes, & strategic program / project decisions (e.g. for SOA-related Master Data)» Roadmap release management for related Services and Data » Strategic decisions related to Master Data sent by SOA services and/or over the SOA ESB

2. SOA Services Portfolio and release mgmt with the EIA and its Enterprise Data Model» Roadmap evolutionary releases for related Services and Data» SOA release management with EIA release management for the services utilizing data in the EIA

3. Services’ design with Master Data defined for, and MDM associated with, these –» Strategic and tactical decisions related to SOA services and the ESB that utilizes Master Data

4. Service initiatives’ architecture and designs with MDM and Metadata Mgmt» Service designs associated with the Data Services layer» SOA designs related to Master Data & Metadata for Enterprise Infrastructure, Data, and Business Services

5. Services with related Metadata defined for these, and associated Metadata Mgmt» SOA components’ (e.g. Services’ WSDL and ESB configuration or security settings) associated Metadata

6. Services’ initiatives design processes and tools with EIA, MDM, and Metadata Mgmt» Organizational processes & roles for Services’ design with those for EIA, MDM, and Metadata Mgmt» 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» Tools and artifacts for Services’ architecture tools & artifacts with EIA, MDM, and Metadata Mgmt

7. SOA initiatives’ Enterprise Services development teams with EIA, MDM, & Metadata Mgmt» Initiative-level SOA services architecture processes & roles with EIA, MDM, and Metadata Mgmt

20

Hitachi Consulting


Other Coordination Points in a Mature EDM – SOA Environment

COE / ICC with Data – SOA Governance, EIA & Enterprise Data Model» COE / ICC with Data & SOA Governance processes & roles

» COE / ICC Roadmap development & releases w/ EIA releases & Enterprise Data Model

COE / ICC with the SOA Services Portfolio and release management» COE / ICC) roadmap development & releases w/ SOA Services Portfolio &

release mgmt

PMO prioritization, decision criteria, and status reporting for EDM & SOA initiatives, including COE / ICC-related activities and releases

21

Hitachi Consulting


Significant MDM and SOA Dependencies & Synergies

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.

» 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.

» 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.

» Using Enterprise Data Model as jump-start, scope of Master Data includes core subject area elements & standard Services for MDM change mgmt & Governance.

First step when creating service-oriented apps is aligning Master Data & Metadata as a precursor to SOA designs. Without a focus on MDM:

» Impossible to communicate information about transactions w/ no common understanding of basic business objects to which Services and events refer.

» Services don’t know where to access “gold standard” version of truth for Master Data

» Data still has to be the same between producers & consumers of Services

Technical intersection of MDM w/ SOA is in Enterprise Data & Metadata Svcs» MDM provides the necessary semantic integration of Services for Master Data.

» Services provide consistent information to consumers across multiple Data Providers.

22

Hitachi Consulting

C-SODA Framework for CoordinatedEDM and SOA Strategies

23

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.

Hitachi Consulting


The C-SODA Framework for Coordinated EDM and SOA Strategies

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.

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.

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.

24

Hitachi Consulting


WHATWHAT

WHOWHO

HOWHOWEDM 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.

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:

1. Strategy—Are the high-level overarching business strategies clearly described, and how do these impact decisions about data and services?

2.Process—Are the core business and IT processes effective, efficient, and supportive in managing strategic data and services?

3. Metrics—Is the right mix of measures for key performance indicators utilized?

4.Data—Is the right data and metadata available to support core processes and strategic services?

5.Services / Applications—Does the software and systems enhance core processes and enable reusable Services and Data?

6.Architecture—Is the correct infrastructure & enterprise architecture in place to support the business with necessary Data and Services?

7. People—Are the human and organizational capital applied to core processes appropriate and sufficient?

Hitachi Consulting Framework for Assessing Strategic Readiness of

EDM and SOA Programs

Strategy

Metrics

Data

Services /Applications

Architecture

People

Coordinated Service-Oriented Data Architecture (C-SODA) Framework Overview

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.

25

Hitachi Consulting


26

Strategy

Data

Services /Applications

Architecture

People

Primary & Secondary Dimensions & Components of the C-SODA Framework Hitachi’s framework considers the interrelationships between key building blocks

Business IT

Business Alignment

Breadth Accessibility Functionality

(Re)Usability Composability Breadth Metadata Supportability Performance

IT

Narrow Footprint

Integration Security Scalability Performance

Manageability

Adaptability Reliability Usability Accessibility

Business IT

Visibility Timeliness Depth/Granularity

Breadth Metadata Services

Definitions / Metadata

Master Data Metadata

Management Integration Quality/Auditibility Augmentation Security Data Model /

Architecture

Business and IT

Organization Leadership Roles & Responsibilities Skills and Alignment Competencies and Experiences Accountability and Incentives Individual Performance

Evaluations Communication and Teamwork Retention/Attrition

Business and IT

Metadata Adoption Actionable Accountability Appropriateness

Balance Linkage Predictive

Value Alignment Cascading

Measurability Calculations Definition Consistency

Business IT

Leadership Rhythms

Target Setting

Initiative Prioritization and Funding

Program Governance

Governance Coordination

Program Mgmt Office (PMO) Standards & Guidelines Data Stewardship Service Stewardship Change Management Policies and Procedures Services Model Release Management EDM – SOA Initiatives Mgmt COE / ICC Mgmt

Business IT

Strategy Map Themes/Alignment Objectives Initiatives Annual Plan Multi Year Plan Data

Ownership/Stewardship

Vision and Alignment to Themes

Multi Year Plan Annual Plan Capital Investment vs.

Operational Support Approach

Metrics

Process

26

Hitachi Consulting


Fine-Tuning and Utilizing the C-SODA Framework for Your Organization

1. 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.

2. Evaluate current state of your coordinated EDM – SOA strategies.» Detailed as necessary to drive granularity of capabilities & potential initiatives for maturity.» 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.

» 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.

3. Inventory the initiatives that are underway or expected to start soon for which improvements will be made to current state ratings.

4. Determine desired future vision based upon same C-SODA Framework.» 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.

5. Determine gaps to be filled between the current state, plus known initiatives, & future vision of C-SODA, perhaps further granulized into intermediate steps.

6. Evaluating gaps in C-SODA capabilities, develop detailed initiatives definitions.7. Prioritize / Schedule gap-filling Roadmap initiatives to achieve desired C-SODA

capabilities.

27

Hitachi Consulting

C-SODA Capability Maturity Model

28

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.

Hitachi Consulting


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

Use

r Porta

ls, Dash

board

, Rep

ortin

g U

I

Operational / Third-Party

Systems

Siebel

Oracle

PeopleSoft

Data Warehouse(EDW)

Master Data Mgmt

Data Mining / Profiling

ETL

Operational Data Store (ODS)

Services & Data Hubs

Wo

rkfl

ow

Man

agem

ent

- E

AI O

rch

estr

atio

n

29

Future Vision – Conceptual Service-Oriented Data Architecture (SODA)

etc.

Metadata Mgmt

DataMetadata

ServicesMetadata

3rd Party /B2B

Business Rules

SOA / ESBEIA / Data Integration Layer

Wo

rkfl

ow

Man

agem

ent

- E

AI O

rch

estr

atio

n

SOA / ESB

Services & Data Hubs

Business Rules

Hitachi Consulting


30

Data Ownership / Stewardship

Enterprise Information OptimizationEnterprise Information Optimization

Initiation – Data FoundationInitiation – Data Foundation

Data Services EnablementData Services Enablement

Data & Services AgilityData & Services Agility

Data & Services ReuseData & Services Reuse

Data Definitions

Data Monitoring,Controls & Balancing

Data QualityManagement

MetadataManagement

EIA & EnterpriseData Model

“Gold Standard”Data Sources

Master Data Management (MDM)

Enterprise DataIntegration (ESB/SOA)

DataTransformation

Enterprise DataServices (e.g.

Access, Monitoring)

Business Process Management (BPM)

& Orchestration

Enterprise BusinessServices (SOA)

Business RulesEngine Driven

Corporate PerformanceManagement (CPM)

Data Governance

Enterprise Business Intelligence

C-SODA Capability Maturity Model: Building Blocks

Integrated Data –SOA Governance

Enterprise InfrastructureServices (e.g. CRUD)

Enterprise DataMgmt (EDM)

Enterprise Data Platform Services

(e.g. ETL)

WorkflowManagement

Services (SOA)

Service-Oriented DataArchitecture (SODA)

Data & Services Managed as Corporate Assets

Centralized

Managed

Enabled

Optimized

C-SODA Strategy Phases:

Business Value

Converging

30

Hitachi Consulting


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.

Most organizations have reached some degree of centralized Data sources, but still have inconsistent management of common Data and Services

Most organizations have reached some degree of centralized Data sources, but still have inconsistent management of common Data and Services

Disparate Converging Centralized Managed Enabled Optimized

Process

Manual data reconciliationShort-term firefighting

Ad-hoc workflow

Repeatable Data reconciliationsData discovery techniquesStart MD analysis

Data Governance maturesSOA Governance emergesSingle version of selected business rulesReactive processes

Integrated Data-SOA Governance emergesFocused initiatives to improve information quality and delivery

BPM & OrchestrationProactive Data & Services analysis, alertsQuality measurable, linked to strategy

Integrated Data-SOA Governance maturesCorporate Performance MgmtClosed-loop data / services integrity (e.g. TQM)

Services / Applications

Functional Module Structured Analysis & Des.Opportunistic, un-reusable apps, services, & data

O-O ModelingSome reusable services, dataNo central coordination b/t services and/or data

Component-Based Dev.Reusable Infrastructure & Data Services emergeData Services layer established

Service-Oriented ModelBusiness Services emerge, evolveData-Service Normalization emerges

Process Integration via BPM & Composite Business ServicesData-Service Normalization matures

Dynamic Assembly & Process Integration of Composite Apps via Business Grammar Modeling & Context-Aware Invocation

Architecture

Use any and all partial architectures that you haveFew services and little reusabilityLimited, disconnected domains architected without an enterprise viewMany disparate platforms, technologies, toolsets

Shared integration points between domainsLong-term vision of enterprise emergesTechnologies and Tools become relevant and shared between domains

Common Enterprise Architecture viewBusiness Services emergeEnterprise Infrastructure Services establishedWorkflow integration becomes relevantCommon technologies, tools, and best practices

ESB emergesIntegrated Workflow Business Rules emergeServices StewardshipEA centrally managed by Arch. / SOA GovernancePrescribed technologies, arch. tools, practicesWorkflow integration tools, best practices

Enterprise Business Services establishedWorkflow Mgmt ServicesBusiness Rules EngineEA version-controlled & evolved according to planMaturing std technologies, tools, and practicesShared Domain Reference Architectures

Service-Oriented Data Arch.EA managed to future state with planned / managed initiatives for intermediate target releases (Roadmap)EA-integrated Workflow Mgmt & supporting Business Rules in planned releasesArchitectural tools, processes are performance-driven

Data

Use what data you haveLimited data integrationReconciliation sheetsNo centralized governance, prescribed tools, practices

Data Governance emergesLong-term data visionData Stewardship establishedData Quality Mgmt

Data Governance adopted across domainsMDM emergesMetadata Mgmt emergesCommon data tools EIA, Ent. Data Model

EDM emergesEnterprise Data ServicesStd. Data TransformationTools incorporated into broader data architecture (e.g. MDM, data profiling)

Standardized data tools, best practices prescribedDomain-specific master data analysis (CDI, PDI)

EDM maturesEnterprise Business Intelligence (BI) Process and tools are integratedAdvanced statistical analytics

C-SODA Capability Maturity Model: EDM View

Initiation“Keep The Lights On”

Deployment“Build The Foundation”

Agility“Expand Capabilities”

Business Value

Data & Services Managed as Corporate Assets

Framework

Dimension

C-SODA Strategy

Phase:

Hitachi Consulting


Emerging Enterpr. Asset Portfolio

Mgmt, Org

Strategic Enterprise & Coordinated Governance

Dynamically aligned Skills & Asset Portfolio

Mgmt via Strategic Governance

Disparate Managed Enabled OptimizedCentralizedConverging

Level 0 Level 3 Level 4 Level 5Level 2Level 1

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

InformationAs 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

ComponentizedBusiness and

Services

Mix & match Business and context-aware capabilities for

independent svc centers

Componentized Business

BusinessProcess

Integration

Processes through service

composition

Monolithic Architectures, LOB-Specific

Emerging Project-Based

SOA

Dynamically Re-Configurable SOA Environ.

w/ Virtualization

ComponentArch. w/ common reusable infrastr.

Layered Architecture w/ Enterprise Stds.

Common Shared SOA

EnvironmentArchitecture

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”

BusinessValue

Hitachi Consulting


Next Steps and Opportunities

Organizations develop appropriate coordinated Data – SOA Governance and Capability Maturity Model Job One towards C-SODA capability maturity.

As a Data / SOA Governance Model is developed / adopted, it should be closely coordinated for processes, checkpoints & stewardship / ownership.

Coordinated Data – SOA Governance, & progressive Roadmap initiatives, should include all relevant Data sources, Services, and supporting products.

Periodic C-SODA maturity assessments to evolve EDM – SOA Roadmap If an organization has overarching PMO that plans initiatives, coordination

should prioritize progressive initiatives towards advanced C-SODA maturity.» 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.

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.

COE / ICC will further facilitate bringing stakeholders together early & often to drive necessary coordination during all stages of EDM – SOA initiatives.

33

Hitachi Consulting


Thank You

MerciGrazie

GraciasObrigado

Danke

Japanese

French

Russian

GermanItalian

Spanish

Brazilian Portuguese

Arabic

Chinese

Hindi

Swedish

Thai

KoreanTack

Hitachi Consulting

Appendix: Coordinated EDM – SOA withOracle Tools and Products

35

Hitachi Consulting


EDM – SOA Governance & Coordination using Oracle Platform

Governance Services

Shared Platform Services

WebServicesManager

ApplicationsRepository

ServicesRegistry

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)

Hitachi Consulting


J2EE Application ServerOracle AS, JBoss, WebLogic, WebSphereMessaging

Metadata Repository

DATA SERVICES & CONNECTIVITY

Apps

AdaptersAdapters

Partners

B2BB2B

RFID

SESSES

DB

ODIODI

ETL / BulkReplication

Multi Protocol Routing

XSLTTransform

Enterprise Services Bus (ESB)Enterprise Services Bus (ESB)

NativeBPEL

Business Rules

Human Workflow

BPEL Process ManagerBPEL Process Manager

ROUTING & ORCHESTRATION

UDDI / DiscoveryPolicies

Management

Security

Web Services Web Services ManagerManager

RegistryRegistry

GOVERNANCEEvents Analytics

BusinessMonitoring

System Monitoring

Enterprise Enterprise ManagerManager

BAMBAM BIBIMANAGEMENT

&MONITORING

App DevFramework

JDeveloperJDeveloper

Analyst Tools

BPA SuiteBPA Suite

Metadata Management Coordination with the Oracle SOA Platform

Mediation

LegacyData Quality

WS Policies

Hitachi Consulting


38

Office

ROUTING & ORCHESTRATIONForums WikiChat

Collaboration - Oracle Web CenterCollaboration - Oracle Web Center

Content Servers

Packaged apps, external

services

Portlets Forms Process Dashboards

Worklist

User, Role Directory

Process Templates – Oracle Appl. Integration ArchitectureProcess Templates – Oracle Appl. Integration Architecture

Metadata Repository

Metadata Management Coordination with the Oracle BPM Platform

BPELExecution

BPM server - Oracle SOA SuiteBPM server - Oracle SOA Suite

Human WF Rules BAM

Model, Simulate & PublishOracle BPA SuiteOracle BPA Suite

ESB

Generic business processes and Industry specific templates

ImagingImaging Integration Integration ContentContent

Applications, Legacy sysImageServer

Document Services

Hitachi Consulting


New Human – Services Process Metadata Integration

Technical Modeling

Oracle SOA SuiteBPEL Process Designer

Business Modeling

Oracle BPA Suite (BPMN, EPC)

Conceptual Model

ExecutableModel

Logical Model

Shared Metadata“Process Blueprint”

optimizing the benefits of edm and soa by coordinating strategies

Technology

data integrity

data dependencies

data cleansing

data acquisition

data stewardship

bad data

enterprise data definitions

data governance organization