Engineering & Industry 4 min readORG-F11

SCADA System Design Guide: Tags, Users, Redundancy, Alarms, and Acceptance

Share

A SCADA design becomes reviewable when operational needs are traced into tag semantics, displays, alarms, users, audit, history, redundancy, cybersecurity, recovery, and acceptance tests. This guide organizes those decisions before implementation hides them in screens, scripts, and server settings.

The short answer

Define the operating model first: who observes and acts, which states and commands matter, what must happen during communications loss or server failure, and which evidence proves safe and usable operation. Build consistent tag, alarm, display, identity, audit, and history standards around that model. Redundancy is accepted only after realistic failure, resynchronization, and recovery tests.

  • Give every tag a stable identity, source, unit, range, quality, timestamp, scan expectation, and owner.
  • Design displays and alarm behavior around operator decisions and abnormal situations rather than graphic decoration.
  • Use named identities, least privilege, controlled engineering access, audit trails, and reviewed service accounts.
  • Specify and test backups, restore, redundancy, degraded modes, time synchronization, retention, and capacity.
SCADA design joins operational decisions with data, identity, availability, and lifecycle controls.
Text-free SCADA design overview connecting tag data, users, alarms, history, redundancy, and acceptance

SCADA design joins operational decisions with data, identity, availability, and lifecycle controls.

Decision guide

Design areaRequired decisionAcceptance focus
Tags and dataIdentity, semantics, quality, time, rate, deadband, ownershipCorrect mapping, units, bad quality, stale data, load and reconciliation
Users and commandsRoles, privileges, authentication, sessions, audit, approvalsAuthorized and denied paths, attribution, timeout and emergency procedure
Alarms and displaysPriority, limit, state, message, response, suppression and navigationOperator recognition, action, flood behavior, shelving and history
Availability and recoveryDependencies, redundancy, backup, restore and degraded operationComponent failure, failover, resynchronization, restore and return to service

A practical workflow

  1. 01

    Baseline process, operational use cases, users, commands, alarms, history, interfaces, availability, and recovery objectives.

  2. 02

    Approve tag, naming, display, alarm, identity, audit, time, retention, scripting, and configuration standards.

  3. 03

    Develop architecture and detailed design with dependencies, trust boundaries, capacity, redundancy, and lifecycle ownership.

  4. 04

    Build in controlled revisions and verify source mapping, permissions, displays, alarms, trends, audit, interfaces, and performance.

  5. 05

    Run FAT, SAT, failure, failover, restore, cybersecurity, operator, and handover tests against traceable requirements.

Approved standards keep implementation decisions consistent across screens, servers, and interfaces.
Text-free SCADA engineering workflow from requirements and standards through build and verification

Approved standards keep implementation decisions consistent across screens, servers, and interfaces.

Evidence and acceptance

The acceptance set should connect requirements to tag and alarm registers, display and navigation reviews, roles, architecture, software and licenses, configuration revisions, scripts, certificates, test procedures, timestamped results, defects, retests, backup and restore evidence, training, known limitations, and the released baseline.

Acceptance proves both normal capability and predictable behavior during faults and recovery.
Text-free SCADA acceptance evidence map covering normal operation, failures, recovery, security, and handover

Acceptance proves both normal capability and predictable behavior during faults and recovery.

Common mistakes

  • Starting from screen count while leaving operating decisions, commands, and abnormal conditions vague.
  • Importing inconsistent tags without rules for identity, units, quality, timestamps, and ownership.
  • Using shared administrator accounts or unreviewed service-account privileges.
  • Claiming redundancy from a topology diagram without testing dependencies and state resynchronization.
  • Treating a passed demo as FAT, SAT, cybersecurity acceptance, and operational authorization.

Engineering and security boundary

Primary sources

Technical claims and product boundaries were checked against these primary sources. Fact-checked

  1. ISA-101 Human-Machine InterfacesInternational Society of Automation
  2. ISA-18 Series of StandardsInternational Society of Automation
  3. Guide to Operational Technology Security, SP 800-82 Rev. 3National Institute of Standards and Technology

Frequently asked questions

What should be designed before SCADA graphics?

Define operations, process states, commands, tag semantics, alarms, users, audit, history, failure behavior, cybersecurity, and acceptance criteria before detailed display construction.

Does redundancy guarantee availability?

No. Shared power, networks, storage, identity, time, licensing, virtualization, configuration, and operator procedures can remain common failure points and must be tested.

What belongs in SCADA acceptance testing?

Traceable normal, load, data-quality, permission, command, alarm, history, audit, interface, communications-loss, component-failure, failover, restore, security, and operator tests.

Does AutoNexit run a SCADA system?

No. It organizes the engineering and acceptance record; the selected runtime platform performs supervision and control interaction.

Related articles

ORG-F08

What Is a SCADA System? Layers, Components, Data Flow, and Security Boundaries

A SCADA system supervises an industrial process by acquiring data, presenting state, managing alarms and trends, and supporting authorized operator actions. A useful design must show each component, trust boundary, data path, failure mode, and operating responsibility rather than reducing SCADA to a screen or server.