Master Data Management

One trusted version of customer, product and supplier records: a domain inventory and baseline, match, merge and survivorship rules, stewardship routines, a hub go-live and the controls that stop duplicates coming back.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Master Data Management, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

212

Starter tasks

📊 Data & Analytics

Master Data Management

Keeping one accurate version of core records such as customers, products and suppliers across many systems, with matching and merge rules.

  1. Master data domain and system inventory
  2. Costing the damage done by duplicate records
  3. Choosing the first master data domain
  4. Attribute-level system of record map
  5. Duplicate and completeness baseline
  6. Critical data elements for the customer master
  7. Master data requester, approver and steward roles
  8. Global master identifier and crosswalk design
  9. Choosing the MDM architecture style
  10. Single front door for new and changed records
  11. Clerical review queue for possible matches
  12. Monthly master data quality scorecard
  13. Monthly data stewardship working session
  14. Crosswalk and orphan key reconciliation
  15. Dormant record review and blocking
  16. Supplier bank detail change controls
  17. Reference data code list upkeep
  18. Quarterly match rule tuning
  19. Matching techniques for names and addresses
  20. Survivorship rules for golden records
  21. International address standardisation
  22. Legal entity names and registry identifiers
  23. Probabilistic record linkage fundamentals
  24. Hierarchy modelling for customers and products
  25. Labelled pair sample for match quality
  26. MDM platform selection
  27. Point-of-entry controls in source systems
  28. Customer base duplicate clean-up
  29. Unmerge and split procedure
  30. Golden record distribution to consuming systems
  31. Product master attribute model
  32. Customer account hierarchy for credit exposure
  33. Third-party reference data subscription decision
  34. First domain go-live and cutover
  35. Initial hub load and reconciliation
  36. Master data readiness for an ERP replacement
  37. Annual master data audit sample
  38. First-year results readout to sponsors
  39. Lean master data for a team without a platform
  40. Merging customer and supplier masters after an acquisition
  41. Rolling out across countries with local rules
  42. Master data operations team in shared services
  43. Erasure and consent requests across master records
  44. Onboarding a new data steward
  45. Effective-dated history for golden records
  46. Machine learning assisted matching
  47. Multi-domain relationships between parties, products and sites
  48. Attribute-level source provenance
  49. Supplier screening at onboarding and on a schedule
  50. Master data service levels for consumers

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Master data domain and system inventory

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Before anyone buys a hub or writes a match rule, someone has to say which records count as master data and where each copy lives.

First tasks

  • List the five or six entity types your teams argue about most often
  • Ask each system owner which master records their system creates or stores
  • Record approximate record counts per system and domain
  • Mark which systems can create records and which only read them
  • Refresh the domain inventory against new and retired systems @recurring(yearly)

Costing the damage done by duplicate records

Master data programmes stall when they are sold as tidiness. Putting a number on what duplicates and bad records already cost, from duplicate supplier payments and returned post to split credit limits and two sales reps chasing the same account, gives sponsors a reason to fund the work and gives you a baseline to beat.

First tasks

  • Ask accounts payable how many duplicate supplier payments they caught last year
  • Collect returned-mail and failed-delivery counts from operations
  • Ask sales operations how often two reps worked the same customer
  • Estimate an annual cost for each incident type with stated assumptions
  • Present the case to the sponsor and record the decision

Choosing the first master data domain

Trying to master customers, products and suppliers at once is the classic way these programmes run for three years and deliver nothing. Scoring each domain on business pain, number of systems, data volume and sponsor appetite picks the one where a first release within six months is realistic and visible.

First tasks

  • Set four scoring criteria and agree them with the sponsor
  • Score every domain from the inventory against the criteria
  • Write a half-page note comparing the top two domains
  • Record the chosen domain and why the others were deferred

Make it yours.

Install Master Data Management, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.