Playbook

Manufacturing Data Catalog Template & Governance Playbook

A practical playbook, examples, governance checklist, and an interactive tag-proposal form to build a canonical tag catalog, naming standards, owners, sampling and aggregation rules, and downstream mappings for trustworthy analytics and MES integration.

Interactive Tool

Manufacturing Tag Proposal & Canonical Catalog Entry

Why a canonical tag catalog matters

Confusing, duplicate, or undocumented tags break dashboards, delay decisions, and frustrate teams. A canonical tag catalog makes shopfloor signals discoverable, reliable, and ready for analytics and MES integration. This playbook shows what each catalog entry should contain, offers naming-pattern examples, defines roles and governance, and includes a simple form to propose or register tags.

Quick template (fields every catalog entry should capture)

  1. Tag name (canonical)
  2. Description & units
  3. Source system and owner (PLC/Historian/MES/etc.)
  4. Sampling rate and aggregation rules
  5. Data type & allowed values
  6. Data lineage and downstream consumers
  7. Change control and review cadence

Governance notes: Define owners and stewards, require change requests for name or semantics changes, set a review cadence (quarterly or per-change depending on criticality), and lock canonical names in integrations to prevent drift.

Naming pattern examples

Use consistent, compact segments that give context. Example patterns:

  • PLANT-LINE-ASSET-SIGNAL-MSR (e.g., PL01-LN1-MXR01-PRESS-PSI)
  • Region.Site.Area.Asset.Signal.Unit (e.g., NA.CHI.A1.Pump03.Flow.LPM)

Keep names human-readable but parseable by tooling. Reserve special characters and avoid spaces.

Roles & lifecycle

  • Tag Owner: Accountable for the signal (usually the system owner or engineering lead).
  • Tag Steward: Maintains metadata, coordinates naming, and reviews proposals.
  • Catalog Manager: Administers the central catalog, enforces policies, and operates change control.

Lifecycle states: Proposed → Approved → Active → Deprecated → Removed. Record deprecation date and replacement mapping.

Common pitfalls to avoid

  • Duplicate tags with different names but same signal (create an alias/merge process).
  • Ambiguous units (always include units and unit conversions where applicable).
  • Uncontrolled ad-hoc tags in dashboards (require catalog registration before dashboarding).

Use the form below to propose a new canonical tag or register an existing signal. Stewards will review submissions and publish approved entries in the canonical catalog.

Proposed canonical tag name using your naming standard. Example: PL01-LN1-MXR01-PRESSURE.PA
Short description of the signal and its units (e.g., 'Mixer 1 pressure — psi'). Include unit conversions if needed.
Where the raw value originates (PLC, SCADA, Historian, MES, IIoT gateway, manual entry, etc.).
Person or role accountable for the signal (e.g., Instrumentation Lead, Process Engineer). Include team email or role.
Person or team responsible for metadata upkeep and review (may be same as owner).
How frequently the value is sampled or emitted. Examples: '1s', '500ms', 'on change', '1min'. If variable, describe typical patterns.
How the value should be aggregated for analytics and dashboards.
Primary data type for the signal.
List allowed values and their meanings for enums or coded statuses. Leave blank if not applicable.
Where this tag is used (analytics jobs, dashboards, MES fields, alerts, reports). List names or owners so consumers can be notified of changes.
Reference to an asset registry ID, PLC address, tag ID in historian, or mapping document. Helps automated lineage and impact analysis.
How critical is this signal for operations, safety, quality, or compliance? High-criticality tags get faster review cadence.
1.0 10.0
Select categories that apply for filtering or stewardship assignment.
If yes, changes will require a formal change request and steward approval.
When should this canonical name be considered active? Use YYYY-MM-DD or 'immediate' for now.
Any other details for stewards (mapping to legacy tags, conversion notes, scripts, or dashboards to update).
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.