What this page solves: why a substation must have UPS

Substation UPS and station battery systems keep critical protection, IEDs, time sync and SCADA alive when auxiliary power fails. This page focuses on the electronic implementation: charging and balancing PMICs, health AFEs, fault bypass paths and notifications into higher-level automation.

Typical failure scenarios without a substation-grade UPS

In many legacy substations, auxiliary AC or station DC drops during a fault. Protection relays, IEDs and communication gateways can lose power and reboot at the very moment tripping decisions are required. The result is a station that is blind, mute and unable to act while fault currents escalate.

In other cases, station batteries have aged silently under float charge. After a fault and restart sequence, undervoltage events during reboot can corrupt logs, leave IEDs in undefined states and prevent remote close or control operations until staff visit the substation.

Critical brains and the last channels that must stay alive

A substation UPS is not a convenience accessory. It protects the small group of functions that must never go dark, even when feeders, transformers and primary breakers are heavily stressed:

• Protection relays and substation IEDs – device logic must evaluate currents, voltages and communication inputs without interruption to issue valid trip and block commands.
• Time sync and PTP/GNSS clocks – synchrophasors, event logs and fault records require a stable time reference across the disturbance and recovery period.
• SCADA and substation gateways – control centers need a live channel to observe states, archive disturbance data and coordinate switching sequences.
• Cybersecurity and secure access modules – security boundaries should remain enforced during outages, including VPN, firewall and authenticated remote access.

Design goals for a substation UPS and station battery system

• Maintain Tier 1 loads for a defined backup duration and across fault, restart and reconfiguration sequences, not only for a static runtime number.
• Expose remaining backup time and usable actions to SCADA and maintenance teams before batteries become unreliable under load.
• Fail in a safe and predictable manner, preferring controlled shutdown and clear alarms over random resets or corrupted states.
• Provide traceable logs of station DC voltage, current and temperature so that post-event analysis reveals whether the backup system behaved as intended.

System boundary: where the substation UPS fits

A substation UPS sits between the rectifier, station battery strings and the critical DC bus. The focus here is the electronics inside that block: charging and balancing PMICs, health AFEs, fault bypass paths and monitoring interfaces into SCADA and higher-level controllers.

Typical substation DC topology and UPS position

In a typical station DC system, main AC feeds a rectifier and charger that drive a 110 V or 220 V DC bus and one or more station battery strings. The UPS block manages these battery strings, conditions power for the critical DC bus and exposes health and status to automation systems.

Within this page, the scope is limited to the electronics inside the UPS and station battery system. AC/DC rectifier topologies, tap-changing strategies and grid-level control are covered in other pages dealing with HVDC auxiliary control and distribution AVR.

Functions covered by this page

• PMIC-based charging, pre-charge and float charge control for station battery strings.
• Cell and string balancing strategies and their implementation inside the UPS block.
• Health AFEs for voltage, current and temperature monitoring and their connection to ADCs and controllers.
• Fault detection, ideal diode OR-ing and bypass paths between batteries, rectifier and DC bus.
• Monitoring, logging and communication interfaces towards SCADA, IEDs and microgrid controllers.

Functions handled on other pages

• Rectifier and AC/DC conversion strategies, including tap changing and regulation of primary DC buses (see HVDC auxiliary control and distribution AVR pages).
• Detailed cybersecurity policies, key management and secure communication standards (see grid cybersecurity module page).
• Microgrid, DER and load-shedding strategies that consume UPS health data and decide when to enter islanded or degraded modes (see microgrid controller and DER aggregator pages).

Critical loads and runtime targets

A substation UPS is sized around a small group of critical loads and the time they must remain alive. Tiering loads into critical, important and non-critical groups prevents non-essential devices such as HVAC from draining the same backup pool that keeps protection, IEDs, time sync and SCADA operating during disturbances.

Tiered view of substation loads

Tiered classification helps turn vague statements like “30 minutes runtime” into concrete engineering inputs. Each tier has different expectations for continuity of operation, tolerable restart behavior and the number of breaker operations that should be supported during an outage.

• Tier 1 – critical: protection relays, substation IEDs, time sync and clocks, SCADA gateways, cybersecurity modules and core access control or security video recorders that guard the site.
• Tier 2 – important: HMIs, engineering workstations and selected lighting used for safe local intervention, configuration and verification after events.
• Tier 3 – non-critical: HVAC, general lighting and office outlets that usually draw from building services or separate IT UPS and should not burden the station DC backup pool.

Typical runtime and restart expectations by load tier

Once tiers and expected runtimes are defined, backup capacity can be estimated. For example, a 400 W Tier 1 group that must run for 30 minutes requires at least 200 Wh of usable energy. On a 110 V station DC bus this equates to around 1.8 Ah, which is then increased to account for efficiency, ageing and temperature margins.

The resulting ampere-hours and recharge window determine the minimum charging current that PMICs need to support. Later sections reuse these tiered loads and runtime targets as inputs when evaluating UPS architectures and selecting charging and balancing ICs.

UPS architecture options and battery chemistries

Substation backup systems can be implemented as classic AC UPS chains, station DC battery systems or hybrid architectures with local storage at critical nodes. Each choice shapes how charging and balancing PMICs and health AFEs are deployed and which battery chemistries are most appropriate.

Three typical architecture patterns

The physical layout of backup power in a substation drives not only wiring and switchgear but also the PMIC and AFE design. Most projects fall into one of three patterns or a combination of them.

• AC UPS + DC-DC – main AC feeds a conventional IT-style UPS, which outputs AC to racks and control room equipment. Individual devices then convert AC to local DC rails.
• DC UPS / station battery on the DC bus – main AC feeds a rectifier and charger that drive a 110 V or 220 V station DC bus and station battery strings supplying protection, control and communication.
• Hybrid DC UPS with local DC-DC and storage – a central station DC system coexists with small batteries or supercapacitors near selected IEDs, RTUs or communication nodes for local ride-through.

Battery chemistries and implications for PMICs and AFEs

The choice of battery chemistry directly influences charging voltage profiles, balancing approaches, allowable temperature ranges and safety limits enforced by PMICs and AFEs. Only key characteristics relevant to UPS electronics are highlighted here.

• VRLA – cost-effective and well understood for station batteries. PMICs focus on accurate float voltage, temperature compensation and avoidance of chronic overcharge.
• NiCd – resilient to deep discharge and low temperatures but sensitive to prolonged overcharge. Charging controllers should support multi-stage profiles and robust temperature monitoring.
• Li-ion – high energy density and compact footprints. PMICs and BMS must enforce tight limits on cell voltage, current and temperature, provide precise balancing and manage protective FETs.
• Supercapacitors and hybrid storage – suited for short ride-through and frequent cycling. Controllers emphasise current limiting, soft-start and coordination with conventional batteries rather than long-duration energy storage.

In a station DC architecture, PMICs and AFEs must therefore be chosen with both the electrical architecture and the intended battery chemistry in mind. Later sections use these architecture and chemistry choices as context when detailing charging, balancing and fault bypass design.

Charge and balance PMICs for station batteries

Charging and balancing PMICs determine how station batteries are treated over years of service. In a substation UPS, they must handle long-term float operation, frequent AC disturbances, wide ambient temperatures and occasionally multiple battery strings that share or hand over the backup role.

Charging modes for substation DC batteries

Most station battery systems follow a combination of bulk charge, constant-voltage finishing and long-term float. PMICs provide the current and voltage control loops, while the UPS controller supervises when to enter fast charge, when to remain in float and how to respond to disturbances on the AC side.

• Pre-charge and soft-start – limits inrush when a depleted battery string is reconnected or when a station DC bus is brought back from zero.
• Constant-current (CC) stage – delivers controlled current to refill the battery within the available charging window after an outage or maintenance event.
• Constant-voltage (CV) stage – tapers current as the battery approaches its target voltage, avoiding overshoot and reducing stress on ageing cells.
• Float mode – holds the battery at a slightly lower voltage level for long periods to counter self-discharge while minimising corrosion and gas evolution.

In a practical station, auxiliary AC may drop or flicker during faults and switching sequences. Every time AC returns, the charging PMIC must decide whether to re-enter fast charge or resume a gentler float regime. Decisions are typically based on measured battery voltage, temperature and the time spent offline, rather than blindly restarting a full fast charge cycle.

• Respect recent history of charge and discharge before returning to bulk charge.
• Apply temperature-dependent limits on maximum charging current and final float voltage.
• Coordinate charge state transitions with the UPS controller and SCADA so that operational staff know when backup capability is degraded.

Cell balancing patterns for station battery strings

As batteries age, cell-to-cell mismatch grows. Charge and balance PMICs mitigate this by redistributing or dissipating energy from stronger cells, helping to keep the whole string usable and predictable. The choice between passive and active balancing determines cost, efficiency and complexity.

• Passive balancing – bleed resistors dissipate energy from higher-voltage cells under PMIC control. This approach is simple and economical, well suited to classic VRLA and NiCd station batteries and many moderate-capacity Li-ion systems.
• Active balancing – inductive or capacitive circuits move charge between cells or between cells and the string, improving efficiency in high-energy Li-ion systems at the cost of extra hardware and control complexity.

In a substation UPS, balancing is usually scheduled during low-load periods, when station DC is stable and temperature is predictable. The UPS controller can log balancing activity, flag outlier cells and report persistent imbalance through SCADA so that maintenance can plan string replacement before runtime margins are exhausted.

Multi-string management and A/B battery banks

Many substations use A/B battery banks to provide redundancy, allow maintenance without losing backup and balance ageing across multiple strings. Charge and balance PMICs serve each bank, while high-side FETs or contactors connect them to the station DC bus under UPS controller supervision.

• Each bank has its own charging channel and balancing circuitry, even if the charger power stage is shared.
• High-side switches or ideal diode controllers determine which bank feeds the DC bus and whether banks can be paralleled in a controlled way.
• The UPS controller tracks operating hours, cycle counts and alarm history per bank to support rotation and preventive replacement policies.

Careful coordination between PMICs, high-side switches and the station DC bus prevents uncontrolled inrush currents and bus disturbances when switching banks. Pre-charge paths and soft-start strategies are common, especially in high-voltage installations and sites with long DC cable runs.

Health AFEs and diagnostic data

Health AFEs collect the voltage, current, temperature and insulation-related signals that define how a substation UPS battery is ageing. Their job is to provide stable, traceable measurements over many years so that the UPS controller and SCADA can estimate runtime, track degradation and trigger timely maintenance.

Key quantities monitored in a station battery system

A complete health-monitoring chain observes more than just the overall station DC voltage. Each measurement channel contributes a different perspective on battery behaviour and system stress during faults, recharge windows and normal operation.

• String and bus voltage – tracks the state of each battery bank and the station DC bus under different loading and charging conditions.
• Cell-level voltage – in systems with Li-ion or monitored VRLA strings, reveals imbalance between cells that would be invisible at string level.
• Charge and discharge current – records how much energy flows into and out of the battery, indicates breaker operation currents and supports fault detection.
• Distributed temperature points – track cabinet air, cell terminals and connection points to enforce safe limits and apply temperature compensation to charging.
• Insulation and leakage hooks – provide measurement points and inputs for dedicated insulation monitoring functions.

AFE and ADC topologies for battery health monitoring

Different substation designs call for different combinations of AFEs and ADCs. Some systems rely on integrated multi-channel front ends, while others separate high-voltage, high-precision and isolation functions into distinct components.

• Integrated multi-channel AFEs – combine differential amplifiers, filters and ADCs with analogue multiplexers for string voltages, shunt signals and temperature sensors.
• Isolated ADCs and sigma-delta modulators – sit close to high-voltage strings or shunts and send digitised data across isolation barriers to the UPS controller.
• Coordination with charging PMICs – PMICs drive the battery with appropriate charge profiles, while health AFEs provide higher-precision measurements for diagnostics, trending and alarms.

From raw measurements to diagnostics and trends

Health AFEs feed a UPS controller that converts raw voltages, currents and temperatures into higher-level diagnostic metrics. These include estimates of remaining runtime, state of charge and state of health as well as the effective internal resistance of battery strings.

• State of charge (SOC) combines voltage information and current integration to estimate remaining usable energy and the number of supported operations.
• State of health (SOH) compares present capacity and internal resistance against reference conditions, using long-term trends in current, voltage and temperature.
• Equivalent internal resistance is derived from transient responses to load and recharge events and indicates when strings are becoming weak or unstable.

High precision and long-term stability in these measurements is essential; otherwise small but meaningful degradation trends are lost in noise. Detailed insulation monitoring algorithms and transformer health diagnostics such as vibration and oil analysis are covered in dedicated pages and only referenced here through measurement hooks and status flags.

Fault detection and bypass strategy

A substation UPS cannot prevent every fault, but it can control how faults propagate. The fault detection and bypass design determines whether a failed battery string, charger or DC bus segment quietly degrades backup capability or rapidly collapses the station DC supply. This section focuses on the UPS’s own fault behaviour, not on feeder or ground-fault protection logic.

Battery-side faults: cells and strings

Battery-side faults range from subtle cell-level degradation to hard short circuits in a string. Charge and balance PMICs and health AFEs provide the measurement hooks, while high-side switches and contactors enforce isolation when thresholds are exceeded.

• Cell voltage collapse – a single cell drops significantly below its peers or minimum threshold, indicating local ageing or incipient failure.
• String open circuit – a connection failure or fuse operation leaves a battery string unable to deliver current even though the station DC bus may still be energised.
• String short or severe internal fault – high fault current flows through the string or its protection, threatening to drag down the station DC bus if not disconnected.

For cell-level issues, the preferred response is graceful degradation: derate runtime estimates, raise a maintenance flag and keep the string online if safety limits are met. For string-level opens or shorts, the design must quickly isolate the affected path and rely on remaining banks or rectifier power to support critical loads.

Charger-side faults: rectifier and PMIC issues

Charger faults disrupt how energy is replenished but do not immediately remove stored energy from the station. Detection focuses on rectifier output quality and PMIC operating conditions, while bypass focuses on preventing overvoltage or uncontrolled charging from damaging batteries.

• Rectifier undervoltage or loss of output – the station DC bus and battery currents indicate that charging is not available even though AC power may be present.
• Rectifier overvoltage or regulation failure – output rises above allowable limits, risking battery overcharge and downstream equipment damage.
• PMIC overtemperature or abnormal behaviour – persistent thermal stress or loss of control over charge current and voltage.

When charging is lost, the UPS moves into battery-only mode and announces that runtime is limited. When overvoltage or PMIC runaway is detected, the charger path must be opened and charging disabled, while the battery continues to support the DC bus within safe limits.

Output-side faults and redundant supply paths

Output-side faults involve the station DC bus and loads. Short circuits or sustained overloads must be cleared without causing all backup paths to collapse. Ideal diode OR-ing, eFuses and bypass contactors provide the building blocks for controlled isolation and automatic switchover between redundant UPS or battery paths.

• High-side eFuses or electronic switches disconnect a faulted UPS output from the DC bus within defined time limits and current thresholds.
• Ideal diode controllers allow multiple UPS or station battery paths to share the DC bus without backfeeding faults into healthy sources.
• Bypass contactors provide a slower, higher-current path that can connect a secondary UPS or alternate station battery bank once a primary path is cleared.

Allowed failure modes should be explicit: no single fault in a battery string, charger module or output switch should immediately remove all backup capability. After any single fault, the UPS should still deliver power for a defined minimum duration or a defined number of critical operations.

Protection and bypass actions must themselves be diagnoseable and logged so that redundant paths are not silently degraded. The substation protection relays handle ground- and feeder-fault logic; this section focuses solely on how the UPS detects and contains its own faults.

Event logging and SCADA notifications

Faults and health data only become useful when they are recorded and communicated. Event logging and SCADA notifications provide the link between UPS internals and operators in the control room. This section focuses on what the UPS reports and how, not on the detailed design of SCADA screens or gateway logic.

Local events and black-box logs

Inside the UPS controller, events are captured in a queue or ring buffer that records what happened, when it happened and which battery bank or charger path was involved. A separate black-box log preserves a compact history for post-event analysis in case of severe disturbances.

• Mode changes such as bulk/float transitions, bank A/B switchover and self-test start or completion.
• Fault events such as string isolation, charger failure, bypass activation, overtemperature and DC bus overload.
• Health-related triggers including capacity falling below targets, internal resistance exceeding limits and repeated warnings that have not been cleared.

Communication paths to SCADA and gateways

To the rest of the substation, the UPS behaves like a specialised IED that exposes measurements, status bits and diagnostic registers over standard protocols. A gateway or SCADA host aggregates these points with data from protection relays, breakers and other devices.

• Electrical quantities such as voltages, currents, temperatures and runtime estimates.
• Status indicators including active battery bank, charger mode, bypass path activity and self-test state.
• Alarm and event codes with timestamps and severity levels, suitable for trending and root-cause analysis.

Alarm levels: warning, alarm, trip and maintenance required

Not every deviation warrants the same reaction. The UPS should classify events into a small set of alarm levels that map cleanly onto SCADA priorities and operating procedures.

• Warning – conditions such as elevated temperature, moderate resistance increase or charge current derating that do not immediately compromise backup but deserve attention.
• Alarm – events like one bank being isolated, charger failure or bypass path engagement that reduce backup margins and may require operational restrictions.
• Trip or critical – loss of ability to meet minimum runtime or breaker-operation targets, indicating that critical loads may soon lose backup.
• Maintenance required – SOH falling below threshold, cycle counts approaching design limits or long-standing warnings that have not been resolved.

Key signals and example point list

A clear point list helps integrate the UPS into existing SCADA templates. The exact protocol mapping depends on the gateway, but the underlying signals are similar across projects.

• Real-time measurements: station DC bus voltage, per-bank voltage, charge/discharge current and key temperature points.
• Backup capability: estimated remaining backup time and estimated remaining breaker operations under current loading.
• Status: active bank, charger mode and fault bits, bypass status, self-test in progress and last self-test result.
• Health: SOH and SOC per bank, internal resistance trend flags and maintenance-required indicators.

The SCADA gateway or substation gateway page can define protocol mappings and HMI design. From the UPS perspective, the key requirement is to expose a stable, well-documented set of measurements, status bits and alarms that accurately reflect backup capability and health.

Cybersecurity and functional safety hooks

The substation UPS is part of the protection and control chain, not just a power accessory. Cybersecurity hooks ensure that control firmware and configuration changes are trustworthy, while functional safety hooks ensure that loss of backup power or mis-supply does not compromise protection relays and safety systems. This section focuses on security and safety features inside the UPS; detailed grid cybersecurity policies and key management are covered in the Grid Cybersecurity Module page.

Cyber hooks for the UPS controller

Cybersecurity for a substation UPS starts at the controller. The goal is to ensure that only trusted firmware runs, that only authorised parties can modify thresholds or send shutdown commands, and that tampering attempts leave a trace in security logs.

• Secure boot and signed firmware updates – the UPS MCU or SoC verifies digital signatures on firmware at boot and rejects unauthorised images. Anti-rollback prevents loading of older, vulnerable firmware, and security state bits are exposed for monitoring.
• Authenticated configuration and control writes – parameters such as voltage limits, temperature limits, charge current, bypass settings and remote shutdown commands require authenticated and authorised access. Read-only monitoring interfaces are kept separate from write-capable control ports.
• Change logging and audit trail – each configuration change is logged with a timestamp, user or role identifier, and before/after values. Security logs can be exported for compliance and root-cause analysis after disturbances.
• Physical tamper detection – cabinet door switches, critical contactor auxiliary contacts and unexpected current paths support detection of forced bypass, unauthorised rewiring or mechanical override of protection devices. Tamper events raise dedicated warnings or alarms and are captured in logs.
• Interface to grid cybersecurity infrastructure – the UPS acts as a secured endpoint behind the substation’s cybersecurity module. It supports protected channels (for example TLS or IEC 62351 profiles) where required, while certificate and key lifecycle management, VPNs and firewalls are handled by the Grid Cybersecurity Module.

Safety-related behaviours and interlocks

From a functional safety perspective, the UPS defines how long protection and control devices remain alive and how they behave during failures. Safety hooks describe how the UPS supplies protection relays, how it fails safely, and how it interfaces with Safety PLCs and safety relays.

• Correct supply for protection relays – the DC bus feeding protection relays and IEDs must always be supplied from monitored and qualified paths. Bank changeover logic avoids transitions that leave relays briefly unpowered or switched to an unmonitored source.
• Safe behaviour under severe battery faults – when cells or strings enter dangerous states such as internal short or thermal runaway, hardware protection has priority over runtime. Fuses, thermal cut-offs and contactors are dimensioned and wired to remove hazardous energy even if the controller fails.
• Defined failure modes and fail-safe defaults – loss of controller power, firmware crash or communication failure must not cause uncommanded disconnection of critical protection loads. Hardware interlocks and contactor logic keep the system in a conservative, stable state when control signals disappear.
• Clear status for safety logic – dedicated status signals indicate supply health, remaining backup capability and major UPS faults to Safety PLCs or safety relays. Safety logic can then enforce interlocks, inhibit certain operations or trigger orderly shutdowns.
• Coordination with protection and safety standards – the UPS design aligns with applicable standards such as IEC 60255 series for protection devices and IEC 61508 for safety-related systems. Detailed SIL allocation and safety validation remain with the overall protection and safety design.

Detailed communication security, key management and network zoning policies are handled at the substation cybersecurity level. The role of the UPS is to provide a secured, diagnosable source of backup power and trustworthy status information into that architecture.

Design checklist and engineering inputs

This checklist consolidates the design decisions from the previous sections into a single set of engineering inputs. Project teams can replace the example values with project-specific data and use the result as a requirements attachment when engaging UPS vendors, battery suppliers and IC providers.

Where the checklist refers to external topics such as protection relay settings, grid cybersecurity policies or SCADA gateway design, those details are covered on the corresponding pages. The UPS checklist focuses on the battery system, charging and measurement chain, protection and redundancy logic, and the information that must be available to higher-level systems.

FAQs about substation UPS and station battery design

These questions summarise the most common design doubts around substation UPS and station battery systems. Each answer is short enough to scan, and each item links back to the section where the topic is explained in more depth.

1. When is a dedicated substation UPS mandatory instead of relying only on AC supply, breaker spring-charging and local control power? (see H2-1 · What this page solves)

   A dedicated substation UPS is mandatory whenever loss of AC supply would immediately de-energise protection relays, IEDs, time synchronisation, SCADA gateways or cybersecurity appliances. Utilities typically require it when remote control, disturbance recording or PMU functions are present. The UPS keeps these critical brains and communication paths alive long enough to trip, reclose, analyse and coordinate restoration.

2. How should responsibilities be divided between the UPS module and the overall station DC system (rectifiers, distribution panels and DC-DC converters)? (see H2-2 · System boundary)

   The UPS module is responsible for battery charging and balancing, health monitoring AFEs, protection and bypass between batteries and the DC bus, and reporting status to SCADA. The broader station DC system covers rectifiers, DC distribution and downstream DC-DC converters. Clear boundaries simplify ownership, fault analysis and vendor responsibilities across the complete DC supply chain.

3. How do you decide the required backup runtime for a substation UPS: by minutes, by number of breaker operations, or by both? (see H2-3 · Critical loads & runtime targets)

   Backup runtime should be specified in both minutes and breaker operations. Time-based targets cover sustained outages and restoration delays, while operation-based targets ensure enough trip and reclose attempts for worst-case fault and switching scenarios. Tier 1 loads are sized for full protection and communication support; Tier 2 may only need short runtime for orderly shutdown.

4. When should a station battery use VRLA or NiCd, and when does it make sense to move to Li-ion or LiFePO4 for the substation UPS? (see H2-4 · UPS architecture options, H2-5 · Charge & balance PMICs)

   VRLA or NiCd are attractive where high ambient temperatures, simple maintenance concepts and long field experience are priorities. Li-ion or LiFePO4 fits compact installations, tight weight limits and projects demanding precise SOC and SOH estimation. The choice also drives PMIC complexity, cell monitoring needs and safety measures, so chemistry is a system-level decision.

5. When is a classic DC station battery system preferable to an AC UPS with downstream DC-DC converters, and when are hybrid architectures justified? (see H2-4 · UPS architecture options)

   A classic DC station battery is usually preferred for feeding protection relays, IEDs and DC trip circuits, especially in utilities with long-established DC practices. AC UPS plus DC-DC converters suits predominantly IT-focused or retrofit environments. Hybrid architectures are justified when critical protection loads need traditional DC while non-critical IT loads share a separate AC UPS.

6. What are the key differences in charger and PMIC strategy between VRLA station batteries and Li-ion or LiFePO4 packs in a substation UPS? (see H2-5 · Charge & balance PMICs)

   VRLA chargers focus on long-term float service, temperature-compensated voltage and modest block balancing. Li-ion or LiFePO4 packs require precisely controlled precharge, constant-current and constant-voltage stages, plus strong cell balancing and stricter cut-offs. PMICs for Li-based systems integrate tighter protections and per-cell monitoring, while VRLA solutions can be simpler but still need robust thermal management.

7. Which voltage, current and temperature channels are essential to estimate SOC and SOH accurately enough for planning substation battery maintenance? (see H2-6 · Health AFEs & diagnostics)

   At minimum, each battery string and the station DC bus require accurate voltage measurement, with at least one charge and discharge current channel and several temperature sensors per cabinet. Li-ion systems also benefit from cell-level voltages. Combined with high-resolution ADCs, these inputs support SOC, SOH and internal resistance trending, enabling predictive maintenance rather than calendar-based replacement.

8. How should battery string and output faults be handled so that a single failure does not black out all protection relays and IEDs? (see H2-7 · Fault detection & bypass)

   Each string needs its own protection and isolation path, such as an eFuse or high-side switch plus contactor, so shorted or open strings can be removed without collapsing the DC bus. The DC bus itself should be fed through ideal-diode OR-ing from multiple banks or UPS units, ensuring that a single fault does not extinguish Tier 1 protection loads.

9. What is the safest way to perform periodic UPS and station battery tests and bypass operations without risking loss of backup for protection devices? (see H2-7 · Fault detection & bypass, H2-8 · Event logging & SCADA notifications)

   Safe testing starts by pre-qualifying the secondary path, confirming that alternate banks or UPS units can sustain Tier 1 loads before any primary bypass. Procedures should define test windows, sequencing and required supervision. All tests are logged with timestamps and outcomes so operators can correlate later faults with recent maintenance activities and verify that redundancy was restored.

10. Which UPS events and health indicators should be sent to SCADA, and which can remain as local black-box logs only? (see H2-8 · Event logging & SCADA notifications)

    SCADA should receive events and indicators that influence operational decisions: active bank, estimated backup time, remaining breaker operations, major faults, bypass status and maintenance-required flags. High frequency details, such as individual balancing actions or minor threshold crossings, can remain in local black-box logs, preserving bandwidth while still supporting deep forensic analysis when needed.

11. When is a dual-UPS or dual-station-battery arrangement justified, and how should critical and non-critical loads be segregated between them? (see H2-3 · Critical loads & runtime targets, H2-4 · UPS architecture options, H2-7 · Fault detection & bypass)

    Dual UPS or dual station batteries are justified for high-importance substations or when independent protection systems must be physically separated. One UPS can feed core protection and tripping circuits, while the second supplies secondary protection, automation or HMI loads. Clear segregation and documented fault behaviour prevent a problem in one path from silently degrading overall protection capability.

12. What information should be captured in the engineering checklist before asking vendors to size a substation UPS and station battery system? (see H2-10 · Design checklist & engineering inputs)

    The engineering checklist should capture load tiers and power, target runtime and breaker operations, chosen battery chemistry and voltage, environmental conditions, EMC and standard requirements, redundancy goals, allowed failure modes and cybersecurity hooks. With these inputs, vendors can propose architectures, device families and station battery configurations that match real operating conditions instead of generic catalogue assumptions.