How to choose your MDM system?
Quick viewpoint by
Pierre Bonnet, COO at Orchestra Networks
www.orchestranetworks.com
www.pierre-bonnet.com
pierre.bonnet@orchestranetworks.com
Creative commons MDM Alliance Group
1
If you are a newcomer in MDM
Look at where your ref/master are managed within your IS (1/2)
Reference and Master Data = shared data, cross domains (not core transaction data)
Many meta-data:
Spreadsheets
Heterogeneous database models,
Data flows
SLA, configuration,
out of
data duplications,
without real data
permission, SOA,
governance
data links spanning several databases
models
ERP customs, etc.
Data in
the Cloud
Message
Message
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 systems
Creative commons MDM Alliance Group
2
If you are a newcomer in MDM
Look at where your ref/master are managed within your IS (2/2)
Reference and Master Data = shared data, cross domains (not core transaction data)
Many meta-data:
Spreadsheets
Heterogeneous database models,
Data flows
SLA, configuration,
out of
data duplications,
without real data
permission, SOA,
governance
data links spanning several databases
models
ERP customs, etc.
Data in
the Cloud
Message
Message
EAI/ESB
Information
lineage
(traceability,
auditability)
Data governance
- data approval
- data validation
- data entry, query
- version, etc.
Repository of ref/master data
MDM
based on a unified data model
+ BRMS if needed (see next)
Internal consumer and producer systems and third party systems
Creative commons MDM Alliance Group
3
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)
Capture of the business
concepts dictionary
and business objects
with their lifecycles
60%
Model-driven
MDM
UI data
governance
validation
Declarative Data model
adaptations within the MDM
directly and under the
control of business users
Gap analysis
DSL (UML)
++ 60%
Most of the time less
than 4 iterations
are sufficient
Model-driven
MDM
iteration++
100%
IT integration
User Acceptance Test and Delivery
T0
NO TUNNEL EFFECT
Model-driven allows for
reducing useless
software development as
a large part is generated
from the data model
automatically
BUSINESS VALIDATION
Taking 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
T0+ 2 months
Creative commons MDM Alliance Group
4
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.)
The four ERP pains
in the ref/master
data field
Pain #2
•
Lack of ref/master data governance functions and bad ref/master
data lineage
ERP scope
Ref/Master
data
Pain #3
•
Publication to third party systems is not recommended due to UI
concerns and security risks
?
Data Governance
Data lineage
Foreign Keys
Foreign Keys
Foreign Keys
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
Next: find out how to remove these pains
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
Creative commons MDM Alliance Group
5
Key technology to support the ERP sustainability (2/2)
The sustainability of this ERP is ensured
Its use can be extended without any risks in relation to ref/master data
ERP scope
Ref/Master
data
Other system
Ref/Master
data
Other system
Ref/Master
data
Third party systems
Data Governance
Data lineage
MDM
uses – self provisioning – reporting – export…
uses
Via the cloud
Rules lineage align with
ref/data lineage
BRMS
Creative commons MDM Alliance Group
6
Key technology to enforce the SOA governance
Other system
ERP scope
Other system
Via the cloud
services
services
services
SOA governance time platform (development, provisionning)
• services portfolio
• SLA
• configuration, parameterization
• all meta-data applied to data, rules
and processes
rights
to the
MDM
system
Data lineage
Rules lineage
Rules lineage
Project lifecycle management
Configuration, test
MDM
• data flows
• validation
• business audit trail
• data flows recycling management
BRMS
• Policies
• Pre and post-conditions
of services
• data mapping rules
BPM
Web portal and dvpt platform
• Orchestration in relation
to interworking concerns
SOA execution time
platform (production)
Monitoring
MDM
BRMS
BPM
Web
portal
Capacity planning
Data injection
Virtualization
end user with
selfprovisioning
rights
CMDB
SAML
SSO
WSDM
UDDI
ESB, WS-* stack, portal, app
end user
Creative commons MDM Alliance Group
7
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
Creative commons MDM Alliance Group
8
Orchestra Networks
Pure 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
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
•Iterative lifecycle
project thanks to the
Model-driven
approach
•+ 40 references in
production: reliability,
performance,
responsiveness
•First project in
production within 2
months
•USA, UK, Europe
•4 days training
•Evangelization
through 2 not-forprofit organizations:
MAG and S-IT-A
Creative commons MDM Alliance Group
9
Orchestra Networks
Reliable, Performant and Responsive
Partial list of customers
see www.orchestranetworks.com to be updated
Creative commons MDM Alliance Group
10
Thanks
www.orchestranetworks.com
www.pierre-bonnet.com
pierre.bonnet@orchestranetworks.com
Creative commons MDM Alliance Group
11