How do I define the canonical fields?

What format is the generated data contract?

A JSON Schema (draft 2020-12) that carries the owner, freshness SLA, sensitivity, source systems, identifiers, consumers, and quality rules as extension keys, alongside a field contract table. Treat it as a draft for design review against your governance standards.

Is my entity design sent anywhere?

No. The worksheet is generated entirely in your browser and nothing is uploaded.

Who should own a business entity?

A business owner who can decide what the entity means and which source wins when systems disagree, such as supply chain operations for a product entity, supported by the technical teams that run the source systems.

Business data contract worksheet

A data contract is an agreed definition of a business entity's fields, types, sources, owner, quality rules, and freshness that producers and consumers rely on.

Define an entity's owner, sources, identifiers, canonical fields, quality rules and consumers, and export a draft JSON Schema. Runs in your browser.

Browser-sideNo accountCopy, download, or print

Last reviewed 30 Oct 2026

Your inputs are saved as a draft in this browser only. Nothing is uploaded.

Jump to result

Result

EntityProduct360

OwnerSupply Chain Operations

Canonical fields5

Required fields3

Sensitivityinternal

Freshness SLAhourly

Draft canonical contract for design review; validate field types, ownership, and quality rules against your governance standards.

Field contract

Field	Type	Required	Source
productId	string	required	SAP ECC
productName	string	required	SAP ECC
category	string	optional	PLM
availableToPromiseQuantity	number	required	WMS
preferredSupplier	string	optional	Supplier portal

Data quality rules

Rule
productId must be globally unique
availableToPromiseQuantity cannot be negative
category must map to approved taxonomy

Product360 canonical contract (JSON Schema):

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Product360",
  "type": "object",
  "x-owner": "Supply Chain Operations",
  "x-freshnessSla": "hourly",
  "x-sensitivity": "internal",
  "x-sourceSystems": [
    "SAP ECC",
    "PLM",
    "WMS",
    "Supplier portal"
  ],
  "x-identifiers": [
    "materialNumber",
    "plantCode",
    "supplierSku"
  ],
  "x-consumers": [
    "Inventory planning app",
    "Customer portal",
    "Procurement workflow",
    "AI order promising assistant"
  ],
  "properties": {
    "productId": {
      "type": "string",
      "x-source": "SAP ECC"
    },
    "productName": {
      "type": "string",
      "x-source": "SAP ECC"
    },
    "category": {
      "type": "string",
      "x-source": "PLM"
    },
    "availableToPromiseQuantity": {
      "type": "number",
      "x-source": "WMS"
    },
    "preferredSupplier": {
      "type": "string",
      "x-source": "Supplier portal"
    }
  },
  "required": [
    "productId",
    "productName",
    "availableToPromiseQuantity"
  ],
  "x-qualityRules": [
    "productId must be globally unique",
    "availableToPromiseQuantity cannot be negative",
    "category must map to approved taxonomy"
  ]
}

Product360 canonical contract (JSON Schema):

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Product360",
  "type": "object",
  "x-owner": "Supply Chain Operations",
  "x-freshnessSla": "hourly",
  "x-sensitivity": "internal",
  "x-sourceSystems": [
    "SAP ECC",
    "PLM",
    "WMS",
    "Supplier portal"
  ],
  "x-identifiers": [
    "materialNumber",
    "plantCode",
    "supplierSku"
  ],
  "x-consumers": [
    "Inventory planning app",
    "Customer portal",
    "Procurement workflow",
    "AI order promising assistant"
  ],
  "properties": {
    "productId": {
      "type": "string",
      "x-source": "SAP ECC"
    },
    "productName": {
      "type": "string",
      "x-source": "SAP ECC"
    },
    "category": {
      "type": "string",
      "x-source": "PLM"
    },
    "availableToPromiseQuantity": {
      "type": "number",
      "x-source": "WMS"
    },
    "preferredSupplier": {
      "type": "string",
      "x-source": "Supplier portal"
    }
  },
  "required": [
    "productId",
    "productName",
    "availableToPromiseQuantity"
  ],
  "x-qualityRules": [
    "productId must be globally unique",
    "availableToPromiseQuantity cannot be negative",
    "category must map to approved taxonomy"
  ]
}

How to use it

Name the business entity and its business owner.
List source systems and identity keys one per line, then add canonical fields one per line as name|type|required|source.
Add data quality rules, then set the freshness SLA, data sensitivity, and consumers.
Review the field contract and generated JSON Schema, then copy, download, or print it.

Questions

How do I define the canonical fields?: Enter one field per line as name|type|required|source, for example productId|string|required|SAP ECC. Each line becomes a property in the generated JSON Schema with its source system recorded.
What format is the generated data contract?: A JSON Schema (draft 2020-12) that carries the owner, freshness SLA, sensitivity, source systems, identifiers, consumers, and quality rules as extension keys, alongside a field contract table. Treat it as a draft for design review against your governance standards.
Is my entity design sent anywhere?: No. The worksheet is generated entirely in your browser and nothing is uploaded.
Who should own a business entity?: A business owner who can decide what the entity means and which source wins when systems disagree, such as supply chain operations for a product entity, supported by the technical teams that run the source systems.