Template

Manufacturing Tag Catalog Template (Interactive)

A practical, fillable tag/catalog template for manufacturing signals and KPIs. Collects canonical names, source mappings, units and timestamps, ownership, quality checks, lifecycle and governance fields, example queries and visualizations — helping teams reduce tag sprawl and make shopfloor signals discoverable and trustworthy.

Interactive Tool

Manufacturing Tag Catalog Entry

Use this form to create or update a canonical entry for a sensor, PLC signal, historian point, calculated KPI, or other shopfloor data element. Capture consistent names, ownership, units, timestamp rules, quality checks, and example queries so dashboards, MES integrations, and analytics are reliable and discoverable.

Fill required fields and provide examples where possible. This form is a living record: update it whenever mappings, calculations, owners, or lifecycle status change.

A stable identifier used across systems (example: PLT1.PLC1.AI_1234 or plant.asset.signal). Must be unique.
Human-friendly canonical name (example: Motor A - Vibration RMS).
Other names used historically or in upstream systems (comma- or newline-separated).
Where the raw data originates.
Describe the physical sensor, PLC tag, or calculation in plain language. Include terminal, module, channel, or I/O details if known.
Plant, line, cell, bay, or equipment (example: Plant 1 - Line B - Cell 3).
Link to the asset registry or CMMS asset id if applicable.
Units of measure (example: mm, °C, m/s, amps). Use SI where practical.
How the value behaves.
Typical sampling frequency or event cadence (example: 1s, 100ms, on-change). Include units.
Where the timestamp is assigned (device, historian, MES) and precision expectations.
How long raw and aggregated data are retained (example: raw 90 days, aggregated 7 years).
Describe automated quality rules (range checks, stuck-value detection, plausibility rules) and recommended alert thresholds.
Lower bound for data quality/validation.
Upper bound for data quality/validation.
If this is a derived KPI, provide the calculation (pseudocode, SQL, or formula) and dependencies (source tags).
Include example queries or scripts that analysts and dashboards can reuse. Provide time range, aggregation, and filters if relevant.
Suggested charts, aggregations, or KPIs that use this tag (OEE inputs, trend charts, alarms).
List KPIs, dashboards, or reports that depend on this tag (links or identifiers).
Person accountable for correctness and stewardship (name).
Best contact method for questions or change requests.
Team responsible for managing access, quality, and onboarding (example: Controls, Reliability, IT).
Controls who can see or use the data.
Current lifecycle state for the tag.
If deprecated, when and what replaces it?
Canonical ID of the replacement tag if relevant.
Record important changes, approvals, or links to design documents, change requests, or tickets.
Keywords to help discovery (example: vibration, temp, safety, throughput).
Who created this entry.
Date of initial creation.
Name of person who last updated the entry.
Date of last 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.