creative commons mdm alliance group 1 how to choose your mdm system? quick viewpoint by pierre...

11
1 Creative commons MDM Alliance Group How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks www.orchestranetworks.com www.pierre-bonnet.com [email protected]

Upload: gabriel-lamb

Post on 17-Dec-2015

213 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

1Creative commons MDM Alliance Group

How to choose your MDM system?

Quick viewpoint byPierre Bonnet, COO at Orchestra Networkswww.orchestranetworks.com [email protected]

Page 2: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

2Creative commons MDM Alliance Group

If you are a newcomer in MDMLook at where your ref/master are managed within your IS (1/2)

Which ref/master data must be used or updated and where?What is the information lineage performance (auditability, traceability)?

Internal consumer and producer systems and third party systemsInternal consumer and producer systems and third party systems

?

Heterogeneous database models,data duplications,

data links spanning several databases

Spreadsheetsout of

governance

MessageMessageMessageMessage

Data flows without real data

models

Many meta-data:SLA, configuration, permission, SOA,ERP customs, etc.

Data inthe Cloud

Reference and Master Data = shared data, cross domains (not core transaction data)

Page 3: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

3Creative commons MDM Alliance Group

If you are a newcomer in MDMLook at where your ref/master are managed within your IS (2/2)

Internal consumer and producer systems and third party systemsInternal consumer and producer systems and third party systems

MDMRepository of ref/master data based on a unified data model

+ BRMS if needed (see next)

Data governance- data approval- data validation- data entry, query- version, etc.

EAI/ESBEAI/ESB

Informationlineage

(traceability,auditability)

Heterogeneous database models,data duplications,

data links spanning several databases

Spreadsheetsout of

governance

MessageMessageMessageMessage

Data flows without real data

models

Many meta-data:SLA, configuration, permission, SOA,ERP customs, etc.

Data inthe Cloud

Reference and Master Data = shared data, cross domains (not core transaction data)

Page 4: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

4Creative commons MDM Alliance Group

Which lifecycle management project?Top-notch project lifecycle management to succeed in MDM

IT Business Users

Capture requirements applied to a MDM domain such as HR, Financial, Product, Organization, etc.

DSL (UML)60%

MDM

Model-drivenUI data

governance validation

Declarative Data model adaptations within the MDM directly and under the control of business users

Gap analysis

DSL (UML)

MDM

Model-driven

Most of the time less than 4 iterationsare sufficient

IT integration

Capture of the business concepts dictionary and business objects with their lifecycles

++ 60%

User Acceptance Test and Delivery

100%

iteration++

T0

T0+ 2 months

NO TUNNEL EFFECTModel-driven allows for reducing useless software development as a large part is generated from the data model automatically

BUSINESS VALIDATIONTaking into account data models adaptations by using a declarative data modeling feature within the MDM directly, empowering Business Users to really participate in the project and then secure the deliverable

Page 5: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

5Creative commons MDM Alliance Group

Key technology to support the ERP sustainability (1/2)

Pain #1

• Lack of data links management to ref/master data located outside the ERP scope

• It means that integrity constraints applied to foreign keys connected to something outside the ERP scope are not managed in data models and database systems, but in heavy and dangerous hard-coded software elsewhere (applications, EAI/ESB, etc.)

Pain #2

• Lack of ref/master data governance functions and bad ref/master data lineage

Pain #3

• Publication to third party systems is not recommended due to UI concerns and security risks

Pain #4

• When a BRMS must be connected to the ERP it means that rules lineage cannot be really enforced as ref/master data used by business rules are frozen within the ERP

• BRMS use is key when a company wants to reduce its customs implementations within the ERP, and then optimize its maintenance and migration when new ERP releases are integrated

The four ERP painsin the ref/master

data field

Ref/Masterdata

ERP scope

Foreign Keys

Foreign Keys

Foreign Keys

Data GovernanceData lineage?

Next: find out how to remove these pains

Page 6: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

6Creative commons MDM Alliance Group

Key technology to support the ERP sustainability (2/2)

Ref/Masterdata

ERP scope

Ref/Masterdata

Other system

Ref/Masterdata

Other system

MDM

including Foreing Keysin

cludin

g Fore

ing K

eysin

clu

din

g

Fo

rein

g K

eys

Data GovernanceData lineage

BRMS

Rules lineage align withref/data lineage

uses

Third party systems

uses – self provisioning – reporting – export…

Via the cloud

The sustainability of this ERP is ensuredIts use can be extended without any risks in relation to ref/master data

Page 7: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

7Creative commons MDM Alliance Group

Key technology to enforce the SOA governance

ERP scope

services

ERP scope

services

Other system

services

Other system

services

Other system

services

Other system

services

Via the cloud

Project lifecycle management

Configuration, test

Web portal and dvpt platformMDM

• services portfolio• SLA• configuration, parameterization• all meta-data applied to data, rules and processes

• data flows• validation• business audit trail• data flows recycling management

Data lineage

BRMS

Rules lineage

BPM

Rules lineage

SOA governance time platform (development, provisionning)

SOA execution time platform (production)

Data injection

Monitoring

Capacity planning

Virtualization

ESB, WS-* stack, portal, app

MDM BRMS BPM

CMDB SAMLSSO

WSDM UDDI

• Policies• Pre and post-conditions of services• data mapping rules

• Orchestration in relation to interworking concerns

end user

Webportal

end user with self-

provisioning rights

rights to the MDM

system

Page 8: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

8Creative commons MDM Alliance Group

What do you need to enforce this architecture?

You need a Model-driven MDM with reliable, performant and responsivess Data Governance Functions open to business users

In priority look at www.orchestranetworks.com

Page 9: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

9Creative commons MDM Alliance Group

Orchestra NetworksPure player in Model driven MDM and Data Governance

IT•Full web, java, XML schema

•Full Data Governance functions

•Full Information lineage and lifecycle management

•RDBMS persistence with XML-ORM

•Distributed repository

•Ready to integrate to back-ends and third party solutions

Method•Full Model-driven which reduced the workload of bespoke software development

•Rich data model can be modeled: the more powerful feature existing on the market

•Iterative lifecycle project thanks to the Model-driven approach

•First project in production within 2 months

•4 days training

Strategy•Pure player in the field, no locked-in to any third party solutions such as EAI/ESB, Data Quality, etc.

•Full cross industries and business units

•Founded in 2000, +10 years of R&D

•+ 40 references in production: reliability, performance, responsiveness

•USA, UK, Europe

•Evangelization through 2 not-for-profit organizations: MAG and S-IT-A

Page 10: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

10Creative commons MDM Alliance Group

Orchestra NetworksReliable, Performant and Responsive

Partial list of customerssee www.orchestranetworks.com to be updated

Page 11: Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks

11Creative commons MDM Alliance Group

Thanks

www.orchestranetworks.com [email protected]