In the early days of automation, PLC programming was limited by memory. Tags were often cryptic addresses like N7:0 or I:1/0. If you didn’t have the “cheat sheet,” you didn’t know what the machine was doing.
Today, memory is cheap, but human time is expensive. In a Smart Manufacturing environment, standardized tag naming is the difference between a system that scales and a system that breaks the moment the lead engineer leaves the room.
Why Standardize? The Case for Global Discovery
As we move toward IT/OT convergence, PLC data is no longer confined to a local HMI. It flows to cloud analytics, Maintenance Management Systems (CMMS), and AI models. If every programmer uses their own naming style, the “data cleaning” process becomes a nightmare.
Standardization provides:
- Reduced Troubleshooting Time: Any technician can walk up to a machine and understand the tag’s function.
- Seamless Integration: Modern SCADA systems can “auto-discover” and “auto-bind” tags if they follow a predictable pattern.
- Asset Interoperability: A “Pump” at Plant A should look the same to the corporate database as a “Pump” at Plant B.
The Gold Standard: ISA-95 Hierarchy
The ISA-95 standard is the most widely recognized framework for integrating enterprise and control systems. It uses a “Functional Hierarchy” to organize data from the corporate level down to the individual sensor.
When naming tags, follow the “General to Specific” rule. This ensures tags group together logically in your controller’s tag database.
Formula:
[Area]_[Line]_[Cell]_[Device]_[Attribute]
| Level | Description | Example |
| Area | The physical department or zone. | Bottling |
| Line | The specific production stream. | Line01 |
| Cell/Machine | The specific piece of equipment. | Palletizer |
| Device | The component (Motor, Valve, Sensor). | Drive01 |
| Attribute | The specific data point or state. | CurrentDraw |
Example Breakdowns:
TX_Austin_Bottling_Line1_Filler_Motor_Speed- TX_Austin: The Site
- Bottling: The Area
- Line1: The specific production line
- Filler: The equipment entity
- Motor: The device
- Speed: The specific data point (Attribute)
Common Tag Naming Styles
While ISA-95 provides the “path,” you still need a consistent style for the words themselves. Here are the three most common:
| Style | Example | Best For |
| CamelCase | ConveyorMotorSpeed | Compactness; easy to read without underscores. |
| Snake_Case | Conveyor_Motor_Speed | Maximum readability; works well with HMI “find and replace.” |
| PascalCase | ConveyorMotorSpeed | Similar to CamelCase; often used for UDT (User Defined Type) names. |
Best Practices for Modern PLC Tags
1. Avoid “Memory-Based” Naming
Never name a tag based on its address (e.g., Input_Slot2_Bit0). If you move that wire to Slot 3 during a repair, your tag name is now a lie. Instead, name it by its function: Pallet_Present_Sensor.
2. Use “State-Based” Indicators for Booleans
For binary tags (True/False), include the state in the name so the logic is self-documenting.
- Bad:
Pump_Status(Does “True” mean it’s on? Or that it’s faulted?) - Good:
Pump_RunningorPump_Faulted.
3. Incorporate Engineering Units
If a value is an integer or a real number, the tag name should hint at the scale.
Tank_Level_Pct(Percent)Heater_Temp_C(Celsius)VFD_Freq_Hz(Hertz)
4. The “Object-First” Rule
Always put the most important noun first. This allows tags to group together alphabetically in your PLC’s tag monitor.
- Instead of:
Left_Motor_Start,Right_Motor_Start,Top_Motor_Start - Use:
Motor_Left_Start,Motor_Right_Start,Motor_Top_Start
Implementing the “Unified Namespace” (UNS)
The ultimate goal of modern tag naming is to support a Unified Namespace. This is a single source of truth where all data—regardless of where it comes from—lives in a consistent, hierarchical tree.
By naming your PLC tags according to ISA-95 standards, you are essentially building the “branches” of the UNS. When an MQTT broker or an IIOT gateway “scrapes” the PLC, it can perfectly map the machine’s data into the corporate structure without any manual translation.
Conclusion: Start Small, Stay Consistent
You don’t need a 50-page manual to start standardizing. Pick a hierarchy (like ISA-95) and a casing style (like Snake_Case) and stick to it. The “future you” who has to troubleshoot a machine at 2:00 AM will thank you for the clarity.