Industrial Networks and OT · #90
Online PLC and SCADA Tag List Diff
Shows the differences between two tag lists in one table for commissioning and revision checks.
- Data is processed in your browser and not sent to a server
- Export: CSV
Tool
What does this tool do?
If an address changed in the PLC program is not carried to SCADA, the operator screen shows the wrong value or a command goes to the wrong bit. Comparing two lists line by line in revisions or third-party integration takes hours. The tool matches by tag name and finds address and type differences, tags in only one list, duplicate names and different tags using the same address.
How to use it
- Paste the PLC (A) and SCADA (B) tag lists as CSV; the header needs
name,address, type, descriptionoptional. - Choose case-insensitive name matching and description comparison.
- Press Run; download the differences as CSV.
Fields
- List A (e.g. PLC)
- CSV; first row header.
- List B (e.g. SCADA)
- CSV; first row header.
- Case-insensitive name matching
- Also compare descriptions
Worked example
| Input | Value |
|---|---|
| List A (e.g. PLC) | |
| List B (e.g. SCADA) | |
| Case-insensitive name matching | ✓ |
| Also compare descriptions | – |
Expected result: Old_Tag only in the PLC; Valve_Open and Alarm_Horn only in SCADA and both use the same address (%M12.0); Motor1_Speed moved from %MW20 to %MW22; 3 tags identical.
The address collision is the most critical finding: a command written to Valve_Open in SCADA also changes the horn bit. The Motor1_Speed difference may be a data block shift in the PLC; confirm which is right with the PLC cross-reference.
Second scenario
| Input | Value |
|---|---|
| List A (e.g. PLC) | |
| List B (e.g. SCADA) | |
| Case-insensitive name matching | – |
| Also compare descriptions | – |
Expected result: In case-sensitive mode 'flow' is a separate tag only in A; 'Flow' shows a type change REAL → FLOAT.
Method and assumptions
Tags are matched by name (optionally case-insensitive). Address and type (case-insensitive) are compared; description optionally. Duplicate names and different tags sharing an address are reported per list.
Using the result and troubleshooting
Add differences to the commissioning checklist and compare both lists again at each revision. Use the Register Address Converter for Modbus addresses.
Limits and common mistakes
- Names written differently (e.g. prefixes/suffixes) do not match; address formats (%MW20 vs DB1.DBW20) are not converted. Type names (REAL/FLOAT) are not treated as equivalent.
Frequently asked questions
How do I export the list?
From the PLC tags table in TIA Portal, via tag export in Studio 5000, and from the SCADA project or tag database export. Rename columns to name, address, type if needed.
Related tools and service
- OT Network Segment and Asset InventoryMatches each device's IP address in the inventory to defined OT segments and finds inconsistencies.
- Modbus Register Address ConverterConverts the register number in a device manual to the address your SCADA/PLC driver expects.
Related service: SCADA, MES and ERP Connectivity