Golden records and domains
A governed golden record per domain — customer, product, location, or the names this organization already uses. Domains are configured in metadata, not commissioned as a new application.
Trusted golden records. A single source of truth for the master data the business already argues about.
Metadata-driven, multi-tenant MDM — matching, survivorship, and data quality as deterministic engines; stewards as the last mile. Optional GenAI drafts; a person activates. Each tenant is a dedicated Azure deployment.
Guides for golden records, stewardship, configuration, and more — no login required to read.
Live product UI — golden records, record detail, source-to-golden mapping, stewardship, and domain modeling. Sample tenant data is not a customer list or a published metric.
A governed golden record per domain — customer, product, location, or the names this organization already uses. Domains are configured in metadata, not commissioned as a new application.
Matching, survivorship, and data-quality rules (MSH) decide which source values live on the golden record. The engines are deterministic — inspectable, repeatable, the system of record.
Stewards review and repair in an AG Grid workbench: filters, bulk edits, the record in front of the person who owns it.
Who changed what, when, and from which source. History is part of the record, not a sidecar log someone might enable later.
Entities, attributes, source mappings, and rules live in metadata. Standing up a new domain does not require a new codebase.
Ask MDM, plus glossary, data-quality, and modeling drafts. The model suggests; a person activates. Matching, survivorship, and quality engines remain the system of record.
Configure entities, attributes, match rules, and survivorship in metadata. A new domain is a configuration task, not a build.
Point source systems at those domains. Matching, survivorship, and data-quality engines produce the golden record from the values you already hold.
Stewards work the grid — review, repair, approve. Every change is kept. The audit trail is the record’s memory.
Optional GenAI drafts stay drafts until a person activates them. Each customer tenant runs as a dedicated Azure deployment.
Each tenant is one App Service and one SQL database, with stewards, source systems, and the Azure services beside them.
Eight short episodes of BizTech MDM as it runs today — golden records, matching, approvals, survivorship, hierarchy, security, and stewardship. The films use sample tenant data.
An overview of golden records, matched sources, and controlled change.
Watch on YouTube → What is BizTech MDM?. opens in a new tabHow master data is organized into domains.
Watch on YouTube → Golden data & domains. opens in a new tabHow source systems link to golden records through matching.
Watch on YouTube → Sources & matching (MSH). opens in a new tabOne person proposes a golden-record change; another reviews it.
Watch on YouTube → Maker-checker & approvals. opens in a new tabWhich source values remain when more than one system contributes.
Watch on YouTube → Survivorship. opens in a new tabRelated golden records as a readable map.
Watch on YouTube → Hierarchy. opens in a new tabUsers, roles, permissions, and masking of sensitive fields.
Watch on YouTube → Security. opens in a new tabThe worklist for match review and data-quality repair.
Watch on YouTube → Stewardship & DQ. opens in a new tabBizTech MDM Platform is the delivery vehicle for master data — not a substitute for naming owners, quality rules, and the operating model. Advisory and implementation remain available through the practice: governance, source mapping, steward design, and the cutover.
Consulting and product coexist. If the next conversation is still “whether MDM,” start with the practice. If it is “show the platform,” request a demo.
A walkthrough of BizTech MDM Platform starts with a note. No ticket queue — the same inbox as the rest of the firm.