Template

Tag naming & data‑tagging standard template — tag creation & registry form

An interactive tag-registration template that captures a canonical tag name (built from segments), required metadata, ownership, change-control details, and MES/ERP mappings. Use it to register trustworthy, discoverable IIoT/MES tags in a data catalog and reduce naming inconsistency, duplication, and noisy signals.

Interactive Tool

Tag creation & naming template

Why this template matters

Consistent, discoverable tags are the foundation for reliable dashboards, analytics, MES/AI, and operator trust. Use this form to create a canonical tag entry that contains naming, ownership, source, sample characteristics, retention, and mappings so your signals are auditable and reusable.

Recommended naming convention

Use an underscore-separated, segment-based name: SITE_LINE_ASSET_SIGNAL_UNIT (prefer uppercase for visual consistency). Typical segments:

  • SITE — short plant code (e.g., PLT1)
  • LINE — production line or cell (e.g., LINEA)
  • ASSET — equipment identifier (e.g., PUMP01)
  • SIGNAL — measured item or metric (e.g., FLOW, TEMP)
  • UNIT — measurement unit or code (e.g., LPM, C, PSI)

Example: PLT1_LINEA_PUMP01_FLOW_LPM

Recommended pattern (guideline): ^[A-Z0-9]+_[A-Z0-9-]+_[A-Z0-9-]+_[A-Z0-9-]+_[A-ZA-Z0-9%]+$. Adapt to local constraints but keep the segment structure and document any deviations.

How to use

Complete the fields below to create a canonical tag. The system will compose the canonical tag name from the segment fields unless you specify a pre-built name. Required metadata helps analytics, auditing, and future integrations with MES/ERP systems. If your organization copies this template into an enterprise or plant domain, tailor the pattern and required approvals to local standards.

Choose 'No' to compose the canonical name from the segment fields below. Choose 'Yes' if you already have a finalized name to enter.
Enter the finalized tag name only if you selected 'Yes' above. Otherwise leave blank and the system will assemble the name from the segment fields.
Short plant or site code (e.g., PLT1). Keep it consistent with enterprise site master data.
Production line or cell identifier (e.g., LINEA).
Equipment identifier (e.g., PUMP01, OVEN3). Use existing asset tags when available.
Short, standardized metric name (e.g., FLOW, TEMP, PRESSURE, RUN_STATE). Prefer canonical vocabulary used across the plant.
Measurement unit code used in the tag name (e.g., LPM, C, PSI, BOOL). If percentage, use PCT or % per your local standard.
Person or role responsible for the signal (e.g., Maintenance Lead, Controls Engineer). Ownership ensures someone is accountable for correctness.
Owner contact email so reviewers and integrators can follow up.
Where the data originates.
Typical sampling interval. Use 0 for event or discrete values. Important for downstream rollups and analytics.
Choose the most appropriate type for storage and analytics.
Human-readable unit for dashboards and labels (e.g., L/min, °C, psi).
How long raw data must be kept before archiving/deletion. Helps storage planning and compliance.
What happens after retention expires.
Optional mapping to MES field or tag for cross-system joins.
Optional mapping to ERP master data if relevant (e.g., material, batch).
Indicate whether this tag creation requires a formal approval (recommended for process-critical signals).
Enter a ticket number, approval ID, or attach reference to approval documentation.
What this signal represents and how it should be used in dashboards or alarms. Explain units, expected range, and known quirks.
Helpful keywords (e.g., 'flow', 'pump', 'production', 'quality') to improve discoverability in the data catalog.
Document any filtering, smoothing, known noise sources, or required preprocessing.
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.