D_-_EA25WBM048_SPEC_PCS_Tag_Standards_0.2.0_DRAFT.pdf

West Basin Municipal Water District 17140 Avalon Blvd Carson, CA 90746 Phone: (310) 217-2411 www.WestBasinCA.gov

SCADA Standards

PCS Tag Naming v.0.2.0

West Basin Municipal Water District

Document PCS Tag Naming Standards

Revision Number 0.2.0

Effective Date 5/12/2026

Author Kaylee Halliday

Reviewed by Alex Coker, PE

Prepared By:

9050 Irvine Center Drive Irvine, CA 92618

(949) 769-6000 www.eaintegrator.com

PCS Tag Naming Standards v0.2.0 EA Project Number: EA25WBM048

17140 Avalon Blvd, Carson, CA 90746 Revision: 0.2.0 Tel 310-217-2411 Effective Date: 5/12/2026 www.WestBasinCA.Gov Page Number: 2 of 15

History Revision Date Description of Change Author Reviewed

0.1.0 3/18/2026 Draft release for client review KH AC

0.2.0 5/12/2026 Updates from client review comments KH AC

Table of Contents 1 Overview

1.1 Purpose

1.2 Acronyms and Terms

1.3 Supplemental Documents

1.3.1 HMI Style Guide

1.3.2 PLC Style Guide

1.3.3 Standards Implementation Guide

1.3.4 Standards Operating Guide

1.3.5 IC&E Standards

2 SCADA/PLC System Tag Standards

2.1 Tag Elements

2.2 Assembling Tag Names

2.2.1 Site Identifiers

2.2.2 Area Identifiers

2.2.3 Type Identifiers

2.2.4 Loop Numbers

2.2.5 Tag Grouping

2.2.6 Tag Extension

2.3 Tag Descriptions

2.3.1 Rules

2.3.2 Tag Description Examples

www.WestBasinCA.Gov Page Number: 3 of 15

1 Overview

1.1 Purpose

West Basin Municipal Water District (WBMWD) has created PLC and HMI programming standards to ensure consistent development of their PCS across all of their locations. In order to adhere to the programming standards, Modicon derived function blocks (DFB) and System Platform objects/graphics are used as reusable code templates. These templates require consistency of tags across all configuration environments for proper configuration of the control system.

This document outlines the specific tagging structure for the PLC and HMI tags. Subsequent sections of this document explain each element of the tagging structure to the reader. For specific information regarding each DFB (and its respective input/output parameters) and System Platform object/graphic (and its respective attributes, custom properties, and wizard options) please refer to the standards documentation for that DFB/object/graphic combination (see Supplemental Documents).

1.2 Acronyms and Terms

For the remainder of the document the following acronyms will be used.

Term Description

EA “Enterprise Automation” (Integrator)

WBMWD, the District “West Basin Municipal Water District”

PLC “Programmable Logic Controller”

PCS “Process Control System”

DFB “Derived Function Block”: PLC code module for Modicon

DDT “Derived Data Type”: PLC tag structure for Modicon

SCADA “Supervisory Control and Data Acquisition”

HMI “Human Machine Interface” www.WestBasinCA.Gov Page Number: 4 of 15

1.3 Supplemental Documents

1.3.1 HMI Style Guide

SPEC HMI Style Guide 1.0.0

1.3.2 PLC Style Guide

SPEC PLC Style Guide 1.0.0

1.3.3 Standards Implementation Guide

SPEC Standards Implementation Guide 1.0.0

1.3.4 Standards Operating Guide

SPEC Standards Operating Guide 1.0.0

1.3.5 IC&E Standards

SPEC IC&E Standards 1.0.0 www.WestBasinCA.Gov Page Number: 5 of 15

2 SCADA/PLC System Tag Standards

2.1 Tag Elements

SCADA/PLC tags are built from the following elements:

1. Site Identifier – Identifies the WBMWD site which the equipment is part of. Can be up to 3 characters. See section 2.2.1 for more details.

2. Area Identifier – Identifies the area where the equipment is located. Can be up to 6 characters depending on system. See section 2.2.2 for more details.

3. Type Identifier – Identifies the type of equipment or device and is defined by the equipment P&IDs. Can be up to 6 characters. See section 2.2.2.4 for more details.

4. Loop Number – Identifies the loop that the equipment serves. Loops are a specific segment of a process area and are defined by the equipment P&IDs. Can be up to 8 characters, or 9 with a special character. See section 2.2.4 for more details.

5. Tag Grouping – Identifies a meaningful grouping of tags within the larger structure. A tag grouping is only applied when the data structure contains a defined substructure/DDT. See section 2.2.5 for more details.

6. Tag Extension – Brief identifier of what the tag is being used for. Can be up to 16 characters.

See section 2.2.6 for more details.

www.WestBasinCA.Gov Page Number: 6 of 15

2.2 Assembling Tag Names

Tags that communicate between SCADA and PLC are constructed with the following syntax:

[Site]_[Area]_[Type][Loop Number].[Tag Grouping].[Tag Extension]

Object/DDT Instance Attribute/DDT Element

All PLC tags that communicate with SCADA should be part of a DDT. The name of the DDT should match the object tagname within SCADA to make I/O referencing easier. Elements of that DDT should match the names of attributes within the SCADA object.

The DDT instance is limited to 32 characters. Only alphabetical (A-Z or a-z), numeric (0-9), underscore (_), and period (.) characters are permitted, and tags names are not case sensitive*. Tag names should match between System Platform and Modicon whenever possible.

*Note: Tags will be configured with system, area, and type in all caps and the extension in title case.

Halliday, Kaylee Will need to update the screenshots when standards are configured www.WestBasinCA.Gov Page Number: 7 of 15

2.2.1 Site Identifiers

Each site has an up to three-letter identifier as described in the table below.

Site Identifier

ECLWRF ECL

HSEPS HYP

CNTP CNT

JMMCRWRP JMM

TRWRP TRW

2.2.2 Area Identifiers

Each area has an up to six-letter/number identifier as described in the tables in the following sections.

2.2.2.1 ECLWRF

The area/site identifier for E.C. Little consists of an up to six-letter/number identifier described in the table below.

Area Identifier Utilities UTIL High Rate Clarifiers T22HRC Title 22 Train 1 T22FT1 Title 22 Train 2 T22FT2 Title 22 Chlorine Contact Basin T22CCB Title 22 Pump Station T22PS Equalization Basins EQBSN Backwash High Rate Clarifiers BWWHRC Solids Handling SOLIDS Ozone OZONE Microfiltration Feed MFFEED Microfiltration Phase 3 MFP3 Microfiltration Phase 4 MFP4 Microfiltration Phase 5 MFP5 Microfiltration Pall Trailers MFTRLR Reverse Osmosis Transfer ROTFR Reverse Osmosis RO Ultraviolet UV Barrier Product Water BARPS Chevron Product Water CHEVPS Chemicals and CIP CHEM Research and Development RDPAD www.WestBasinCA.Gov Page Number: 8 of 15

2.2.2.2 HSEPS

The area/site identifier for Hyperion consists of an up to six-letter identifier described in the table below.

Area Identifier Utilities UTIL Pump Station PUMPS

2.2.2.3 CNTP

The area/site identifier for Chevron consists of an up to six-letter identifier described in the table below.

Area Identifier Utilities UTIL Plant Influent T22INF Chemicals CHEM Nitrification NIT Nitrified Product Water NITPRD Waste WASTE

2.2.2.4 JMMCRWRP

The area/site identifier for Carson consists of an up to six-letter/number identifier described in the table below.

Area Identifier Utilities UTIL Plant Influent T22INF Microfiltration MF Chemicals CHEM Reverse Osmosis Transfer ROTFR Reverse Osmosis RO Boiler Feed Product Water BFPRD Nitrification NIT Nitrified Product Water NITPRD Waste WASTE

2.2.2.5 TRWRP

The area/site identifier for Torrance consists of an up to six-letter/number identifier described in the table below.

Area Identifier Utilities UTIL Plant Influent T22INF Chemicals and CIP CHEM Microfiltration MF Reverse Osmosis Transfer ROTFR www.WestBasinCA.Gov Page Number: 9 of 15

Area Identifier Reverse Osmosis RO Boiler Feed Product Water BFPRD Nitrification NIT Nitrified Product Water NITPRD Waste WASTE www.WestBasinCA.Gov Page Number: 10 of 15

2.2.3 Type Identifiers

Each type of instrument and equipment has a unique abbreviation that may be up to 6 characters.

Type identifiers should match the P&IDs for a given site. Reference the WBMWD IC&E Standards for the list of type identifiers.

2.2.3.1 Loop Controllers

SCADA tags associated with control loops (e.g., PID Controller) do not have a specific type of equipment defined within the P&IDs but are required for SCADA configuration. SCADA tags associated with control loops will replace the equipment type with the controller type. PID control tags will use “PID” as the type. PWM control tags will use “PWM” as the type. Chemical pacing tags will use “CHM” as the type.

2.2.3.2 Sequence Control

SCADA tags associated with sequence control do not typically have a single piece of equipment or instrument that they are associated with. Sequence control tags will use “SEQ” as the type.

2.2.3.3 Non-Standard

Non-standard tag types are for tags that are not a part of a standard or single piece of equipment or instrument (i.e., process tags). These tags will use “SYS” as the type.

2.2.4 Loop Numbers

Loop numbers are typically provided by the P&IDs for a given site and should be used to determine the loop number for a tag. Reference the WBMWD IC&E Standards for information on how the loop number is decided. The loop number will be between 3 to 8 digits in length. In some circumstances, it is possible the SCADA/PLC tags will require a special loop identifier to be appended to the loop number.

2.2.4.1 Special Loop Number Identifiers

2.2.4.1.1 Signal identifier

Where a duplicate tag name would be generated for multiple signals from the same equipment (and associated single tag on the P&IDs), an optional 5th identifier can be used to create a unique tag for a specific signal. Use of the optional special identifier should be avoided where possible. The optional special identifier is added to the end of the loop number with a single alphabetic character.

For example, a power quality monitor may be monitoring voltage on multiple phases and therefore will have multiple analog signals associated with voltage.

2.2.4.1.2 Control Loop

SCADA tags associated with control loops (e.g., PID Controller) do not have a specific type of equipment defined within the P&IDs but are required for SCADA configuration. SCADA tags associated with control loops will utilize the loop number associated with the analog tag used for the process variable.

www.WestBasinCA.Gov Page Number: 11 of 15

2.2.4.1.3 Sequences

SCADA tags associated with sequences will often contain multiple devices and equipment that will have varying loop numbers. These SCADA tags will use the loop number associated with the equipment or vessel that is changing state. In the event that multiple pieces of equipment are being controlled through the sequence, the loop number will use any digits that the equipment has in common and use an “X” in place of the inconsistent digits.

2.2.4.1.4 Calculated values

In some cases, multiple tags are used to calculate a value such as a flow that is a sum or difference of two flow meter values. In these cases, the loop number will use the common digits of the two analog input values and replace the first uncommon number with a character such as x, y, or z. The remaining numbers can be generated sequentially.

Examples:

A calculated flow from FIT1010 + FIT1020 + FIT1020 would be FIT10X0.

A calculated flow from FIT2600 + FIT2400 would be FIT2X00.

Two calculated flows from FIT1010 + FIT1020 and FIT1010 + FIT1030 would be FIT10X0 and

FIT10Y0.

2.2.5 Tag Grouping

In some cases, tags within same type/loop number may be further grouped based on their specific function. This is used when the type contains multiple tags associated with the same I/O point (e.g., VLV0101.Posn.Value, VLV0101.Posn.FaultAlm). These distinct groupings should be assigned a name based on their function. Typically, this is used within the equipment standards when a single piece of equipment has multiple I/O points associated with it (see Standards Implementation Guide).

If a tag is not part of a grouping, “Tag Grouping” should be omitted from its name. It is possible for a single data structure to contain both grouped and ungrouped tags.

Will need to update screenshot when standards are configured www.WestBasinCA.Gov Page Number: 12 of 15

2.2.5.1 Analog I/O Groupings

Functional Description Group Name Chlorine Cl2 Conductivity Cond Current Curr Density Dens Differential pressure DPress Flow Flow Frequency Freq Level Level Ammonia NH3 pH pH Position Posn Position command PosnCmd Power Power Pressure Press Speed Spd Speed command SpdCmd Temperature Temp Torque Torq Turbidity Turb Vibration Vibr Voltage Volt Weight Weight

2.2.5.2 Discrete I/O Groupings

Functional Description Group Name Remote feedback Remote Open feedback Open Closed feedback Closed Open command OpenCmd Close command CloseCmd Running feedback Running Run command RunCmd Start command StartCmd Stop command StopCmd www.WestBasinCA.Gov Page Number: 13 of 15

2.2.5.3 Totalizer Groupings

Flow meters and certain equipment types have totalizers that calculate total flow or runtime, respectively. The naming of the totalizer extension will use one of the values (totalizer type) from the following table. This allows for multiple totalizers to be distinguished within the same unit/loop number.

Functional Description Group Name Perpetual total Total Hourly resetting total HourlyTotal Daily resetting total DailyTotal Monthly resetting total MonthlyTotal Cycle total (for current state, mode, sequence, etc.)

CycleTotal

2.2.6 Tag Extension

Tag extensions are added to the end of SCADA tags in order to provide a general description of the tag’s usage. The maximum length of a tag extension is 16 characters.

All tag extensions associated with standard PLC DFBs and HMI objects/graphics will be listed in the specification for those standards (see Standards Implementation Guide).

2.2.6.1 Non-Standard Extensions

Non-standard tag extensions are tags that need to be generated that are not a part of a standard (e.g., process tags). Custom extensions should adhere to the following rules:

• The extension should not exceed 16 characters

• The extension should be descriptive of what the tag is

• All alarm tags must end in “Alm”

Example:

ECL_T22FT1_SYS030X01.Permissive for a system permissive www.WestBasinCA.Gov Page Number: 14 of 15

2.3 Tag Descriptions

This section describes the rules for constructing tag description to be used when creating PLC/SCADA tags.

2.3.1 Rules

1. In general, all tags with the same tag base start with the same description, and all tags with the same tag extension end with the same description

2. All tag descriptions must be written in title case except when using acronyms or abbreviations.

3. In general, equipment and processes should use plain-English descriptions

4. Do not use any special characters other than a hyphen “-“ or underscore “_” within an equipment ID (i.e., FIT-0301 or FIT_0301). Use a hyphen if P&IDs use a hyphen, use an underscore if P&IDs use an underscore.

5. Do not use abbreviations for the extension descriptions (e.g., High High instead of Hi Hi)

6. Do not use any symbol or form of the word “number” for numbered equipment (e.g., Pump 1 instead of Pump #1)

7. All alarms will end with "Alarm"

8. All digital outputs will end with “Output”

9. All digital inputs will end with “Input”

10. All raw analog outputs will end with “Raw Command”

11. All scaled analog outputs will end with “Command”

12. All raw analog inputs will end with “Raw Value”

13. All scaled analog inputs will end with “Value”

14. Use the common chemical name for chemical related tags (e.g., Ammonia instead of Aqueous Ammonia 25%) (see table in section 2.3.1.1)

15. Make sure the I/O list is updated so the description of any I/O points matches the description of any I/O tags

16. All sequence tag descriptions will begin with the system name followed by the sequence name.

E.g., For the hold request tag in a Filter backwash sequence: Title 22 Train 1 Filter 1 Backwash Sequence Hold Request

17. All PID tag descriptions will begin with the system name followed by the control loop type.

E.g., For the Hyperion pressure control loop proportional setpoint: Hyperion Pump Station Pressure Control Proportional Setpoint

While the tag name will have “Alm”, the tag description will spell it out: “Alarm”

Updated examples so they are relevant to West Basin processes www.WestBasinCA.Gov Page Number: 15 of 15

2.3.1.1 Common Chemical Names

Chemical Accepted Abbreviations Anionic Polymer APoly Carbon Dioxide CO2 Cationic Polymer CPoly Citric Acid Citric Ferric Chloride FE Hydrogen Peroxide H2O2 Lime - Ozone - Polymer Poly Sodium Bisulfite SBS Sodium Hydroxide SOH Sodium Hypochlorite SHC Sulfuric Acid Sulfuric Threshold/Scale Inhibitor TI

2.3.2 Tag Description Examples

Tag Description ECL_CHEM_P4604.RunCmd.DO Sodium Hypochlorite Pump 1 Run Output ECL_CHEM_P4604.Running.DI Sodium Hypochlorite Pump 1 Running Input ECL_CHEM_P4604.SpdCmd.AO Sodium Hypochlorite Pump 1 Speed Raw Command ECL_CHEM_P4604.Spd.AI Sodium Hypochlorite Pump 1 Speed Feedback Raw Value ECL_T22PS_LIT411.AI Diversion Pump Station Level Raw Value ECL_T22PS_LIT411.Value Diversion Pump Station Level Value ECL_T22PS_LIT411.HiHiAlm Diversion Pump Station Level High High Alarm ECL_T22PS_LIT411.LoAlm Diversion Pump Station Level Low Alarm

2.3.2 Tag Description Examples