Acme Corp company standard for UNS tag naming, folder hierarchy, data types, and descriptions. Apply to all new Acme solutions.
[alarm, alarms, alert, notification, group, area, limit, digital, pipeline, monitoring]

title: "Acme Corp — Tag Naming and Structure Standards" tags: [naming, convention, tags, structure, standard, acme, company] description: "Acme Corp company standard for UNS tag naming, folder hierarchy, data types, and descriptions. Apply to all new Acme solutions." version: "2.1" author: "Acme Corp Engineering"

When to Use This Skill

Use this skill when:

• Creating tags for any Acme Corp solution
• The user says "create tags", "add tags", or "set up the namespace"
• Reviewing or refactoring an existing Acme solution's tag structure

Tag Hierarchy

All Acme tags follow this 4-level hierarchy:

{Site}/{Unit}/{Equipment}/{Measurement}

Examples:

• Houston/Distillation/Column1/Temperature
• Houston/Distillation/Column1/Pressure
• Houston/Utilities/Boiler2/SteamFlow
• Baytown/Cracking/Reactor3/CatalystLevel

Rules:

• Site = city name (Houston, Baytown, Beaumont)
• Unit = process unit name (Distillation, Cracking, Utilities, Storage)
• Equipment = equipment ID with number suffix (Column1, Pump3, Boiler2)
• Measurement = what is measured (Temperature, Pressure, Level, Flow, Status, Speed)

Never use:

• Abbreviations in measurement names (use Temperature not Temp)
• Underscores (use PascalCase for multi-word names: SteamFlow not Steam_Flow)
• Generic names like Tag1, Analog1, Value

Data Type Standards

Important: Acme uses imperial units (°F, PSI, GPM), not metric. All tag descriptions must include the unit.

Description Format

Every tag must have a description following this format:

{Equipment full name} {measurement} in {unit}

Examples:

• "Distillation Column 1 temperature in °F"
• "Boiler 2 steam flow rate in GPM"
• "Cracking Reactor 3 catalyst level in %"

Example: Creating Tags for a New Pump

When the user asks to add tags for a pump, create this standard set:

{
  "table_type": "UnsTags",
  "data": [
    { "Name": "{Site}/{Unit}/Pump{N}/Status",      "DataType": "Integer", "Description": "{Unit} Pump {N} status (0=Off, 1=Running, 2=Fault)" },
    { "Name": "{Site}/{Unit}/Pump{N}/Speed",        "DataType": "Double",  "Description": "{Unit} Pump {N} speed in RPM" },
    { "Name": "{Site}/{Unit}/Pump{N}/DischargePressure", "DataType": "Double", "Description": "{Unit} Pump {N} discharge pressure in PSI" },
    { "Name": "{Site}/{Unit}/Pump{N}/SuctionPressure",   "DataType": "Double", "Description": "{Unit} Pump {N} suction pressure in PSI" },
    { "Name": "{Site}/{Unit}/Pump{N}/Flow",         "DataType": "Double",  "Description": "{Unit} Pump {N} flow rate in GPM" },
    { "Name": "{Site}/{Unit}/Pump{N}/BearingTemp",  "DataType": "Double",  "Description": "{Unit} Pump {N} bearing temperature in °F" },
    { "Name": "{Site}/{Unit}/Pump{N}/RunHours",     "DataType": "Double",  "Description": "{Unit} Pump {N} cumulative run hours" },
    { "Name": "{Site}/{Unit}/Pump{N}/StartCommand", "DataType": "Boolean", "Description": "{Unit} Pump {N} start command" },
    { "Name": "{Site}/{Unit}/Pump{N}/StopCommand",  "DataType": "Boolean", "Description": "{Unit} Pump {N} stop command" }
  ]
}

Ask the user for Site, Unit, and pump number, then substitute into the template.

Alarm Naming Convention

Alarm items follow this pattern:

{Site}_{Unit}_{Equipment}_{Condition}

Example: Houston_Distillation_Column1_TempHigh

Verification

After creating tags, verify:

1. All tags follow the 4-level hierarchy
2. No abbreviations in measurement names
3. All descriptions include units
4. DataTypes match the standard table above
5. Imperial units used (not metric)

In this section...