Presentation is loading. Please wait.

Presentation is loading. Please wait.

Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks www.orchestranetworks.com.

Similar presentations


Presentation on theme: "Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks www.orchestranetworks.com."— Presentation transcript:

1 Creative commons MDM Alliance Group 1 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

2 Creative commons MDM Alliance Group 2 If you are a newcomer in MDM Look 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 systems ? Heterogeneous database models, data duplications, data links spanning several databases Spreadsheets out of governance Message Message Data flows without real data models Many meta-data: SLA, configuration, permission, SOA, ERP customs, etc. Data in the Cloud Reference and Master Data = shared data, cross domains (not core transaction data)

3 Creative commons MDM Alliance Group 3 If you are a newcomer in MDM Look at where your ref/master are managed within your IS (2/2) Internal consumer and producer systems and third party systems MDM Repository 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/ESB Information lineage (traceability, auditability) Heterogeneous database models, data duplications, data links spanning several databases Spreadsheets out of governance Message Message Data flows without real data models Many meta-data: SLA, configuration, permission, SOA, ERP customs, etc. Data in the Cloud Reference and Master Data = shared data, cross domains (not core transaction data)

4 Creative commons MDM Alliance Group 4 Which lifecycle management project? T op-notch project lifecycle management to succeed in MDM ITBusiness Users Capture requirements applied to a MDM domain such as HR, Financial, Product, Organization, etc. DSL (UML) 60% MDM Model-driven UI 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 iterations are 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 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

5 Creative commons MDM Alliance Group 5 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 pains in the ref/master data field Ref/Master data ERP scope Foreign Keys Data Governance Data lineage ? Next: find out how to remove these pains

6 Creative commons MDM Alliance Group 6 Key technology to support the ERP sustainability (2/2) Ref/Master data ERP scope Ref/Master data Other system Ref/Master data Other system MDM including Foreing Keys Data Governance Data lineage BRMS Rules lineage align with ref/data lineage uses Third party systems uses – self provisioning – reporting – export… Via the cloud The sustainability of this ERP is ensured Its use can be extended without any risks in relation to ref/master data

7 Creative commons MDM Alliance Group 7 Key technology to enforce the SOA governance Via the cloud Project lifecycle management Configuration, test Web portal and dvpt platform MDM 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 MDMBRMSBPM CMDB SAML SSO WSDMUDDI Policies Pre and post-conditions of services data mapping rules Orchestration in relation to interworking concerns end user Web portal end user with self- provisioning rights rights to the MDM system

8 Creative commons MDM Alliance Group 8 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.comwww.orchestranetworks.com

9 Creative commons MDM Alliance Group 9 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 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

10 Creative commons MDM Alliance Group 10 Orchestra Networks Reliable, Performant and Responsive end user Partial list of customers see www.orchestranetworks.com to be updatedwww.orchestranetworks.com

11 Creative commons MDM Alliance Group 11 Thanks www.orchestranetworks.com www.pierre-bonnet.com pierre.bonnet@orchestranetworks.com


Download ppt "Creative commons MDM Alliance Group 1 How to choose your MDM system? Quick viewpoint by Pierre Bonnet, COO at Orchestra Networks www.orchestranetworks.com."

Similar presentations


Ads by Google