Solutions
Synopps software: one engine, three modules for master data tasks
Academy
Master data training built on real project practice
Implementation · SAP MDG and other MDM platforms
We design the master data model, configure MDM, cleanse the master data and connect your business systems. Methodology, architecture and development sit in one team: the people who design the solution also implement it.
Requests
Consuming systems
One master data source for all business systems
Fewer duplicates and conflicts between databases
Clear roles and workflows for create and change requests
Reconciliation of one object across systems
Controlled publication of golden records to ERP, business systems and document management
Our clients include
Definition
MDM implementation is a project after which the company has one source of master data: materials, products, vendors and customers, organisational structure. Each item is created once, goes through checks and approval, and then reaches every system in the same form.
Without MDM
Bolt M12x60 galv.BOLT M12*60 ISO 4014Bolt zinc plated 12 by 60Stock, purchasing and reporting count three different items. They can only be matched by hand.
With MDM
Fasteners › Bolts
Bolt, hex head: M12×60, ISO 4014, zinc plated
The record is created once from the class template and reaches every system with one code.
This is an illustration. In a project, naming templates and attribute sets are built from your master data.
When you need it
MDM is needed where the same master data lives in several systems, departments and subsidiaries, and errors in it hit procurement, the warehouse, production and reporting.
Different master data rules across departments and sites
Duplicates and mismatches of the same domain between systems
Data is updated late and this causes errors in operations
A lot of manual work on master data maintenance
Integrations break because there is no common data model
Moving to a group model a group ERP or a new ERP
A complex distributed landscape dozens of databases, several platforms
No single source of data for ERP, the data warehouse and reporting
A large catalogue but no master data team? You can start not with a full MDM but with checks at entry to the catalogue. That is new material requests with checks, and it also works on top of an MDM you already have.
Stages
Five stages, and for each one you know in advance what we do and which documents you get. We configure MDM and cleanse master data in parallel, so clean data is loaded at go-live.
What we do
What you get
What we do
What you get
What we do
What you get
What we do
What you get
What we do
What you get
Master data cleansing
Cleansing does not have to be part of an MDM implementation. It can be done separately, before you choose a platform or in a system that already runs. Read more on the page about master data cleansing.
We run it in parallel with MDM configuration, so golden data is loaded at go-live.
We clean up the existing catalogue before MDM or without it.
We hand over the Synopps methodology and tools and support you on disputed cases.
Project management
Every project document has an owner. Weekly status, a risk and issue log, working meetings on master data domains, and separate architecture decisions on disputed points.
Project documents
MDM implementation is more than a configured system. It is a data model, rules and workflows by which master data is maintained after go-live. These are the key project documents.
| Domain | Master system | Consuming systems | Owner |
|---|---|---|---|
| Materials | MDM | ERP, WMS, EAM | Master data team |
| Vendors and customers | MDM | ERP, DMS | Finance |
| Units of measure | MDM | all systems | Master data team |
| Organisational structure | HR system | MDM, ERP | HR |
Class: Bolts
TypeThread×LengthStandard,Coating
Bolt, hex head: M12×60, ISO 4014, zinc plated
Duplicate found: the request goes back to the requester with a link to the existing item
| ERP | WMS | EAM | DWH | |
|---|---|---|---|---|
| Materials | ||||
| Vendors and customers | ||||
| Equipment | ||||
| Units of measure |
publishednot published
We also hand over:
The documents are shown as examples. In a project they are built from your master data and systems.
Request scenarios
One of the main choices in the project. It drives user convenience, integration complexity, timeline and cost. We choose together with you at the design stage.
A
The whole process of creating and processing requests runs in MDM. One point of control for the process and the data. Rules, duplicate checks and approvals in one place. Minimal changes to business systems, a fast start, simple support.
Users need to get used to working in a separate system.
B
The user starts in their own system and opens MDM with a button. A familiar entry point. Logic, checks and approvals stay in MDM. Lower risk than a full single window.
You need to plan authentication and the parameters passed, and adapt the source systems.
C
The user works in their own system, MDM processes the request and returns the result. Maximum comfort: no switching between systems.
Changes in every system, complex returns and comments, risk of status mismatches, longer timeline and higher cost.
What we recommend. For a reliable, controlled go-live, start with scenario A. Scenario B is a sensible balance between convenience and control. Scenario C is possible, but it is better left for a later stage, once the process is stable.
Timeline and cost
We give the exact timeline and cost after a kick-off meeting and a short assessment. Below are guidelines and what they depend on.
Piloton one domain, such as materials or vendors
Wave 1key domains: materials and vendors, quality rules, roles and request workflows, first integrations
Wave 2financial dimensions, organisational structure, other domains and new consuming systems
We go live in waves. We start the next wave only when the first works steadily and the architecture, integrations and data governance model are proven.
We price the project by stage: the scope and result of each stage are clear before work starts.
Risks
The same causes delay MDM projects again and again. We record them at the start, track them in the risk log and close them with decisions at the design stage.
The integration flows are only clarified at the end of the project
The integration diagram and master data register are ready at stage 1, before MDM is configured
Duplicates and incomplete records are loaded into MDM
We cleanse in parallel with configuration, so golden data is loaded at go-live
Consuming systems bypass MDM and items are created locally
Publication matrix and mismatch control show where a record appeared outside MDM
Approvals on the client side take too long
Steering committee at milestones, an issue log, an owner for every document
A domain has no owner, and maintenance rules conflict
Data owners and the role model are fixed in the project charter
Users do not accept the new system
We choose the request scenario around users and train key and end users before go-live
MDM practice
In large groups a standard MDM runs into the specifics of distributed production. Here are two extensions we build in projects.
Extension
The same item is accounted for differently at different plants and in different databases: as finished goods in one, as semi-finished goods in another. The accounting group is set in the request for each database. The result: one record, no duplicates and no manual fixes on site.
Extension
Rules on which records go to which systems are set in the user interface: domain, selection condition, list of consuming systems. Fewer manual export errors, new domains connect faster, and the rules are the same for all consuming systems.
For companies on SAP we implement SAP MDG. We also work with other MDM platforms and help choose the solution and edition for the scale of your master data and integration landscape.
Our own tools
Synopps modules take over routine work: duplicate search, classification, splitting descriptions into attributes. The decision on every disputed case stays with an expert.
Synopps Data Health
Duplicate and equivalent search, classification, descriptions by template.
Learn moreSynopps New Record
Checks at entry: class, attributes, duplicates, confirmation from external sources.
Learn moreSynopps Core
The same request checks inside your SAP, ERP or MDM, without a separate interface.
Learn moreExperience
We have implemented, developed and supported MDM in metals, pharmaceuticals, automotive retail, pipeline transport, manufacturing and the public sector. Several projects are described in detail.
Pharmaceuticals
Master data centralised, MDM integrated with consuming systems through the corporate middleware, corporate master data cleansed.
Automotive retail
A combined MDM and group ERP solution, methodology and cleansing of the material and vendor master data.
Metals
Redesigned maintenance processes for materials, services and vendors, master data cleansed during the roll-out.
Public sector
MDM, group ERP and public sector accounting systems adapted, integrations developed and supported.
More projects in completed projects.
FAQ
MDM is a system and a way of managing master data: materials, products, vendors and customers, organisational structure and other domains. It gives the company one source of reliable data for ERP, warehouse and business systems, analytics and reporting. Each item is created once, goes through checks and reaches every system in the same form.
Assessment of data and processes, design of the target data model, MDM platform configuration, master data cleansing, integrations with business systems, testing, user training and go-live in waves. At the end the company has a working MDM and a master data maintenance SOP.
A pilot on one domain can go live in 2 to 3 months. A production implementation usually takes 4 to 9 months and depends on the number of domains, the volume and condition of the data, the number of systems in the integration landscape and the migration requirements.
The cost depends on the number of domains, the volume and quality of the data, how much cleansing is already done, the number of connected systems and the request scenario. We price the project by stage after a kick-off meeting and a short assessment, so you see what you pay for at each step.
Yes, before or during the implementation. If you load duplicates, incomplete records and inconsistent naming into MDM, the system simply centralises the existing mess. Cleansing can be a separate project, done by your team with our methodology, or part of a turnkey implementation. In a turnkey project we run it in parallel with MDM configuration, so golden data is loaded at go-live.
Yes, and we recommend it. The first wave usually covers materials and vendors. Later waves add financial dimensions, organisational structure and other domains only after the architecture, integrations and data governance model are proven.
ERP, HR and finance systems, document management, SAP, warehouse systems, procurement and maintenance systems, data warehouses and analytics. We build the exchange through the corporate integration middleware or directly if there is none.
The choice depends on the IT landscape, the number of domains, data volume, integration requirements, the complexity of approval workflows and the budget. For companies on SAP we implement SAP MDG. We help choose the solution and edition for your task before the implementation starts.
A catalogue in ERP serves one system. MDM manages master data for all systems at once: it checks an item at creation, looks for duplicates, runs approval and publishes the golden record to every database. With more than one system, data drifts apart over time without MDM.
The problem is usually at entry: new items are created without checks, and the catalogue gets cluttered again. We audit quality, clean the existing records and add checks on new items. The checks can be built into the MDM you already run.
Next step
Tell us which systems and master data domains you have. At the first meeting we will go through the task and propose a scenario and the order of waves.
Current systems, master data domains and key issues
We look at the data and master data processes
Scenario, waves, timeline and cost estimate