SCADA and HMI Systems

The working kit of a SCADA and HMI engineer: an architecture and tag database you trust, screens operators can read at a glance, healthy telemetry links, a clean historian and a control network that is locked down.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for SCADA and HMI Systems, and click Install. It goes into your own files, and works offline from then on.

Before you start: this plan is general information to help you organise your own work. It does not replace your professional judgement, the rules of your regulator or professional body, your firm's policies, or advice from a qualified lawyer, accountant or other adviser. Where a law, code or standard applies, use the current official version for your country, and get qualified sign-off on regulated or safety-critical work.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🔧 Engineering Practice

SCADA and HMI Systems

Designing and maintaining SCADA and HMI systems: screens and alarms, historians, communications with field devices, user access and security for control networks.

  1. SCADA system architecture and asset inventory
  2. Tag database export and naming convention
  3. Field communications and protocol map
  4. Control network zones and conduits drawing
  5. SCADA user accounts and roles audit
  6. HMI screen audit against ISA-101
  7. Historian coverage and data quality baseline
  8. SCADA licences, versions and support register
  9. SCADA functional design specification
  10. Weekly telemetry and communications health review
  11. Monthly SCADA user access review
  12. SCADA patch and antivirus update routine
  13. Historian data integrity checks
  14. HMI screen change control and revision log
  15. Remote access session log review
  16. SCADA server redundancy failover test
  17. Time synchronisation and sequence of events check
  18. Control network security event monitoring
  19. SCADA server health and capacity watch
  20. High-performance HMI principles in practice
  21. DNP3 polling, events and unsolicited reporting
  22. Modbus register maps, data types and scaling
  23. OPC UA servers, certificates and information models
  24. IEC 62443 for SCADA engineers
  25. Historian queries, aggregates and reports
  26. Telemetry radio and cellular link planning
  27. Safe scripting in the SCADA platform
  28. Overview display rebuilt to high-performance standard
  29. HMI colour palette and symbol library
  30. Alarm presentation on the HMI
  31. Choosing a SCADA platform for replacement
  32. Migrating serial telemetry links to IP
  33. Historian consolidation decision
  34. Web and mobile HMI access decision
  35. Replacing shared operator logins with named accounts
  36. Secure remote access redesign
  37. SCADA software version upgrade
  38. Integrating a new remote site into SCADA
  39. OT cyber incident tabletop exercise
  40. Operator training on new screens before go-live
  41. Annual control system vulnerability assessment
  42. First 90 days as a utility SCADA engineer
  43. HMI developer at a system integrator
  44. Sole SCADA engineer for a small operator
  45. Moving from IT networking into OT and SCADA
  46. Control room operator moving into SCADA engineering
  47. IEC 61850 substation integration into SCADA
  48. Pipeline SCADA displays and leak detection support
  49. One-way historian replication to the business network
  50. Control room display wall and console layout review

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

SCADA system architecture and asset inventory

Most SCADA systems grew one site and one server at a time, and few engineers inherit a drawing that shows every server, client, RTU, PLC, switch and radio as it really is. Walking the system and writing it down gives you the map every later change, patch and security decision depends on, and it usually turns up at least one forgotten machine still talking to the control network.

First tasks

  • Export the device list from the SCADA configuration and network switches
  • Walk the server room and control room recording every device and label
  • Draw the architecture from primary server to the furthest field site
  • Flag every device you cannot match to a drawing or an owner

Tag database export and naming convention

Tag databases of twenty thousand points nearly always mixes three naming styles, orphaned tags with no field device and duplicates that disagree. Exporting it to a spreadsheet and writing down the naming convention you will hold from now on makes every screen build, historian query and alarm change faster and less error prone.

First tasks

  • Export the complete tag database to a spreadsheet
  • Filter for tags with no field address, no units or no scaling
  • Draft the naming convention and review it with the operations lead
  • Compare a fresh tag export against the last one for unexplained changes @recurring(quarterly)

Field communications and protocol map

When a remote site goes grey on the overview, the first question is how its data travels, and the answer is often a chain of serial Modbus, a licensed radio, a cellular router and a protocol gateway that nobody has drawn. A communications map that names every link, protocol, polling rate and failover path turns a two-hour outage hunt into a ten-minute check.

First tasks

  • List every communications channel configured in the SCADA server
  • Record protocol, transport, polling rate and timeout for each channel
  • Find and back up the configuration of every protocol gateway
  • Mark each link with no alternative path on the map

Make it yours.

Install SCADA and HMI Systems, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.