Comparison

OCOM vs Master Data Management

Executive summary

Master Data Management is the discipline and tooling for authoritative master data: golden records, identity resolution, data quality, and stewardship for customers, products, suppliers, and locations. OCOM is a governed description of operating reality, objects with identity, ownership, lifecycle, and evidence, including what MDM typically does not model as master data: decisions, contracts, policies, and the reasons behind a current state. MDM governs the master data about things; a model built with OCOM governs the operating record of what is true about them, why, and who answers for it.

Scope

Compared

  • Whether each governs master data values or the full operating record around them
  • How each treats decisions, contracts, and policy as first-class objects
  • Where identity resolution lives and how OCOM builds on it

Not compared

  • Specific MDM tooling or platforms
  • Data quality, matching, and deduplication algorithms
  • MDM governance operating models (steward councils, DAMA-DMBOK practice)

Terminology mapping

OCOMMDMEquivalent
IdentityGolden RecordPartial
ObjectMaster Data EntityPartial
OwnershipData StewardPartial
RegistrySystem of RecordPartial
ContractNone

Conceptual differences

AspectOCOMMDM
Centre of gravityObject-centric: the operating record of what is true and whyData-centric: the golden record of what a value is
TimeObject state and evidence over the whole lifecycleGolden value with a change history, not a governed lifecycle
GovernanceFirst-class: ownership, policy, constraint, decisionsData stewardship and quality rules, not operational accountability
ScopeSpans everything the organization must account forBounded to master data domains (customer, product, supplier, location)

Concept coverage

ConceptOCOMMDM
Golden record resolutionPartialCovered
Object identityCoveredPartial
LifecycleCoveredPartial
GovernancePartialPartial
OwnershipCoveredPartial
EvidencePartialOut of scope
AI retrievalPartialOut of scope

Four OCOM cells read Partial rather than Covered (Golden record resolution, Governance, Evidence, AI retrieval), and the reason for each is recorded in the specification's own register: Golden record resolution is Partial because OCOM governs identity and provenance but prescribes no matching or survivorship algorithm; Governance is a Core Characteristic of every Object that no document defines as one (AO-023); Evidence has no Meta, Models or Language definition, its Definition being reserved for a future version (AO-021); AI retrieval is disclaimed by AI/Context/Context Assembly.md, which prescribes no retrieval algorithms (AO-048). Workflow and Event are defined normatively at the Models tier and carry no Core Vocabulary term record.

Covered: the model defines the concept explicitly. Partial: the concept appears indirectly or by convention. Out of scope: the model does not set out to describe it; a boundary, not a deficiency.

Interoperability

References