{"id":2422,"date":"2026-09-30T13:00:00","date_gmt":"2026-09-30T05:00:00","guid":{"rendered":"https:\/\/shenhengglobal.com\/?p=2422"},"modified":"2026-09-28T21:05:24","modified_gmt":"2026-09-28T13:05:24","slug":"substation-scada-architecture","status":"publish","type":"post","link":"https:\/\/shenhengglobal.com\/ar\/blog\/substation-scada-architecture\/","title":{"rendered":"Substation SCADA Architecture and Data Points"},"content":{"rendered":"
\n

substation SCADA architecture<\/strong> requires a clear engineering boundary before it can support a purchase, inspection or commissioning decision. Substation SCADA architecture connects field measurements and controls to operators, historians and maintenance teams through a defined chain of sensors, intelligent electronic devices, remote terminal units, communication networks and supervisory software. A useful design starts with the one-line diagram and operating decisions, then defines each data point, timestamp, quality flag, command permission and fallback state. It should improve visibility without weakening local protection or safety interlocks.<\/p>\n

Start from the operating decisions<\/h2>\n

List the decisions the control room must make: breaker or switch status, feeder load, voltage, alarms, protection trips, transformer temperature, battery or charger health and communication state. A point without an operating use is a maintenance burden and a possible source of confusion.<\/p>\n

Separate indication, alarm, measurement, control and event data. State the source, engineering unit, scaling, timestamp, quality flag, deadband and expected update rate. Keep the point list linked to the approved one-line and cause-and-effect schedule.<\/p>\n

Map the architecture layers<\/h2>\n

A typical architecture has field sensors and switchgear contacts, protection or control IEDs, an RTU or gateway, a station network, a supervisory server or HMI and a historian or control center link. The exact implementation depends on the utility and project.<\/p>\n

Document each interface, protocol, address range, time source, redundancy path and cybersecurity boundary. Avoid hidden converters and unmanaged switches. The diagram should show what remains functional when a server, network link or auxiliary supply fails.<\/p>\n

Define data quality and time<\/h2>\n

Operators need to distinguish a healthy zero from a stale, substituted, bad or communication-lost value. Events from different devices also need a consistent time source for sequence-of-events analysis.<\/p>\n

Specify quality flags, time synchronization, source priority, failover behavior and retention. Test loss of communications, clock drift and restoration. Do not allow the HMI to display a stale value as if it were live.<\/p>\n

Specify command permissions<\/h2>\n

Remote commands should include selection, permission, interlocking, command timeout, feedback and an audit trail. Local protection and mechanical interlocks remain authoritative.<\/p>\n

Define local, remote and maintenance modes, role permissions, two-step commands and rejection messages. Test a failed command, contradictory feedback and loss of control power. Never bypass a physical interlock to make SCADA appear complete.<\/p>\n

Plan alarms and events<\/h2>\n

Alarm priorities should reflect consequence and required response. A flood of nuisance alarms hides a genuine trip or abnormal transformer temperature. Events should retain source, time, state transition and acknowledgement.<\/p>\n

Create an alarm philosophy and point-by-point acceptance list. Verify that protection trips, loss of voltage, battery alarms, door or gas conditions and communication failures reach the correct operator and historian.<\/p>\n

Secure and maintain the system<\/h2>\n

Operational technology security includes asset inventory, controlled remote access, segmentation, backups, patch governance and recovery procedures. The system also needs maintainable spares, tested firmware and documented credentials handled under the owner\u2019s process.<\/p>\n

Coordinate the SCADA design with the site security plan and applicable utility requirements. Retain configuration backups, point lists, network drawings, test records and change approvals. Re-test after a relay, gateway, firmware or network change.<\/p>\n

Define the equipment boundary<\/h2>\n

Start with the exact asset, voltage class, construction and released drawing. A useful engineering answer is tied to a physical boundary and a defined operating state. Record where the calculation, inspection or comparison starts and ends, and identify equipment intentionally excluded. This prevents a general catalog description from being mistaken for a project acceptance value.<\/p>\n

Keep the product identity consistent through design, procurement and commissioning. Note the supplied model, accessories, enclosure, cable interface and environmental assumptions. If the installed arrangement differs from the drawing, stop and obtain an approved disposition instead of filling a missing value from another product family.<\/p>\n

Use standards and manufacturer evidence together<\/h2>\n

Standards define the framework, test concepts and terminology, while manufacturer documents define the verified construction and operating limits of the supplied equipment. A standard link cannot prove that an unverified modification is acceptable, and a brochure cannot replace the project specification or safety rules.<\/p>\n

For procurement, request the standard edition, design verification or type-test scope, routine test records, installation limits and any altitude or environment correction. Store the evidence with the asset record. When a result is disputed, compare definitions, test conditions and boundaries before comparing numbers.<\/p>\n

Plan installation and commissioning<\/h2>\n

Installation quality often determines whether a sound design remains sound in the field. Confirm foundations, access, lifting, clearances, ventilation, cable bend radius, earthing, labels and control interfaces before energization. Use the approved method statement and permit system. A neat cabinet is not proof that every bond, interlock or sensor is connected correctly.<\/p>\n

Commissioning should move from document checks to visual inspection, mechanical operation, electrical continuity, functional logic, protection or control tests and final restoration. Record instrument identity, settings, raw values, exceptions and the person who performed the check. Keep equipment isolated whenever a test or inspection exposes a hazard.<\/p>\n

Control changes and handover<\/h2>\n

A change to a cable route, relay setting, tap position, cooling path or earthing connection can alter the original design basis. Use a controlled change process with an owner, technical review, drawing revision and acceptance evidence. Temporary test arrangements must be removed or clearly tagged before handover.<\/p>\n

The final package should include as-built drawings, test sheets, approved settings, equipment identity, maintenance instructions, deviations and training records. A future operator should be able to reproduce the decision without relying on memory or an unlabelled photograph.<\/p>\n

Safety note<\/h2>\n

Electrical equipment can retain energy and can be energized from more than one source. This article is not a switching instruction. Qualified personnel must follow local regulations, isolation, absence-of-voltage verification, grounding and supervision requirements. Never reach into an energized compartment or defeat an interlock to make a measurement.<\/p>\n

If a test fails, an enclosure is damaged, abnormal noise or discharge is observed, or the actual configuration is unclear, keep the asset in a safe state and escalate to the responsible engineer. Repeated energization without diagnosis can increase damage and risk.<\/p>\n

Record the baseline<\/h2>\n

Keep the initial operating condition, measurement method and acceptance decision with the asset record. A baseline makes later troubleshooting and retesting more efficient.<\/p>\n

When the installation changes, compare the new result with the approved baseline and document the reason for any difference.<\/p>\n

\"Substation
Use the approved product drawing and site conditions when applying this guidance.<\/figcaption><\/figure>\n

How to use the result in a project<\/h2>\n

Start with the released design and final equipment identity. Note the operating state, measurement point, environmental conditions and decision the evidence must support. Then compare the record with the applicable standard, manufacturer instruction and project acceptance plan. If a prerequisite is missing, keep the item open rather than filling the gap with a generic value. This gives procurement, commissioning and operations teams the same reference point.<\/p>\n

For a supplier inquiry, ask for the calculation basis, verified arrangement, limits, test records and deviations. For site work, record the person, instrument, date, isolation boundary and restoration check. A concise record is more useful than a long report that hides the one fact needed to approve the next step.<\/p>\n

\"Substation
Field verification should document the actual configuration, not only a general catalog illustration.<\/figcaption><\/figure>\n
\n\n\n\n\n\n\n\n\n\n
Project checks for substation SCADA architecture<\/caption>\n
Check<\/th>\nEvidence<\/th>\nDecision use<\/th>\n<\/tr>\n<\/thead>\n
Definition<\/td>\nBoundary, equipment identity and operating state<\/td>\nPrevents different teams comparing different quantities.<\/td>\n<\/tr>\n
Design basis<\/td>\nRatings, environment and duty assumptions<\/td>\nConnects the answer to the real installation.<\/td>\n<\/tr>\n
Verification<\/td>\nApproved method, instrument, raw result and acceptance basis<\/td>\nCreates an auditable record.<\/td>\n<\/tr>\n
Change control<\/td>\nDeviation, review owner and as-built revision<\/td>\nStops hidden field changes becoming risk.<\/td>\n<\/tr>\n
Handover<\/td>\nSettings, tests, photos, maintenance and exceptions<\/td>\nSupports safe future operation.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

Related product and engineering guides<\/h2>\n

For the matching Shenheng product context, see the relevant product page<\/a>. For the broader topic, read the parent engineering guide<\/a>. Related reading: first related guide<\/a> and second related guide<\/a>.<\/p>\n

Sources and standards<\/h2>\n

Authority source 1<\/a> \u00b7 Authority source 2<\/a><\/p>\n

Video for system context<\/h2>\n

This neutral Practical Engineering explainer provides background on substations, transformers and switchgear. It is educational context, not a switching or test instruction.<\/p>\n