{"id":2009,"date":"2026-09-15T11:39:53","date_gmt":"2026-09-15T03:39:53","guid":{"rendered":"https:\/\/www.zishengelectric.com\/?p=2009"},"modified":"2026-09-15T11:39:56","modified_gmt":"2026-09-15T03:39:56","slug":"substation-auxiliary-power-system-epc","status":"publish","type":"post","link":"https:\/\/www.zishengelectric.com\/ar\/substation-auxiliary-power-system-epc.html","title":{"rendered":"Substation Auxiliary Power System for EPC Projects: AC\/DC Loads, Backup Supply and Acceptance"},"content":{"rendered":"

Zisheng Electric treats auxiliary power as a defined equipment interface in EPC substation planning. A main transformer can be ready for service while its cooling controls, protection relays or breaker trip circuits still depend on an incomplete auxiliary supply. A substation auxiliary power system<\/strong> therefore needs its own load schedule, operating cases, responsibility matrix and acceptance evidence.<\/p>\n\n\n\n

This guide focuses on coordination between the station-service transformer, AC distribution, battery charger, DC distribution and connected equipment. It provides review questions for EPC engineers and project owners rather than prescribing one voltage, battery capacity or protection setting. Those values must come from the approved project design and the equipment suppliers’ operating limits.<\/p>\n\n\n\n

Define the substation auxiliary power system boundary<\/h2>\n\n\n\n

Begin with a single-line diagram showing every normal, standby and temporary source. Identify the point where each supplier’s responsibility starts and ends. The main transformer package may include a marshalling cabinet but exclude the cable from the AC board. A switchgear supplier may provide trip coils but exclude the DC feeder. A charger supplier may provide an alarm contact but leave the SCADA connection to the integrator. These gaps should be visible before purchase orders are released.<\/p>\n\n\n\n

The boundary statement should identify who designs, supplies, installs, terminates, tests and accepts each interface. One organization may supply a cable while another sizes it. The arrangement is workable only when the design authority and final verification owner are explicit. Assign one owner to close each open item and one approver to accept the evidence; a list of several responsible parties usually delays closure.<\/p>\n\n\n\n

Use the same equipment identifiers on the load schedule, cable schedule and drawings. The substation cable interface schedule<\/a> should carry the source board, feeder, destination terminals and cable scope for every auxiliary circuit. This gives installers a traceable route from the design to the actual termination.<\/p>\n\n\n\n

Build a load schedule that separates function from nameplate demand<\/h2>\n\n\n\n

A total of connected watts is insufficient. Separate continuous loads, intermittent loads, starting loads and emergency duties. Record whether each load needs AC or DC, its rated voltage and acceptable operating range, normal current, inrush or starting demand, duty duration, and the consequence of losing supply. Include control equipment as well as power-consuming accessories.<\/p>\n\n\n\n

Continuous and intermittent AC loads<\/h3>\n\n\n\n

Continuous duties can include ventilation, control-panel heaters and charger input. Intermittent duties may include transformer cooling stages, breaker spring charging, maintenance outlets and lighting. Do not assume all intermittent duties are mutually exclusive. During recovery after an outage, several motors and chargers can demand power at the same time. The design case should identify which loads restart automatically and which are deliberately sequenced.<\/p>\n\n\n\n

Critical DC duties<\/h3>\n\n\n\n

Protection, tripping, communications and selected controls may depend on DC supply. Obtain the actual current and minimum operating voltage from each equipment supplier. Breaker close and trip coils can have short but significant current demand, while relays and communication equipment create a continuous duty. Both affect the sizing case, and the most demanding event can occur near the end of the required autonomy period.<\/p>\n\n\n\n

\n
Load or interface<\/th>Data required<\/th>Design consequence<\/th>Acceptance evidence<\/th><\/tr><\/thead>
Transformer cooling<\/td>Motor running current, starting demand, stage sequence<\/td>AC feeder rating and restart behavior<\/td>Approved motor list and functional sequence record<\/td><\/tr>\n
Breaker operating mechanism<\/td>Coil voltage limits, pulse current, operation sequence<\/td>DC voltage drop and event load<\/td>Supplier data and witnessed operating checks<\/td><\/tr>\n
Protection and communications<\/td>Continuous current, supply redundancy, ride-through needs<\/td>Autonomy and supply continuity<\/td>Load register and loss-of-source test record<\/td><\/tr>\n
Battery charger<\/td>Continuous load, recharge duty, input characteristics<\/td>Charger and upstream AC capacity<\/td>Settings sheet and charger performance record<\/td><\/tr>\n
DC outgoing feeder<\/td>Cable length, conductor size, device characteristic<\/td>Voltage at the remote load and fault clearing<\/td>Approved calculation and point-to-point inspection<\/td><\/tr>\n
Supply-loss alarms<\/td>Signal definition, contact state, delay and destination<\/td>Operator response and fault diagnosis<\/td>SCADA point list and end-to-end test evidence<\/td><\/tr>\n<\/tbody><\/table><\/div>\n\n\n\n

Evaluate operating cases before choosing redundancy<\/h2>\n\n\n\n

Two incoming AC feeders do not automatically create two independent sources. If both depend on the same upstream bus, transformer or switching device, a common outage can remove both. Mark common dependencies on the single-line diagram and check each operating case against the required service continuity. Redundancy should be demonstrated through the architecture and operating procedure, not inferred from the number of incomers.<\/p>\n\n\n\n

At minimum, assess normal operation, loss of one source, total AC loss, one charger unavailable, maintenance isolation, and restoration after a prolonged outage. Define which loads remain energized, which may be shed, and how long the critical duties must continue. The project owner should approve the acceptable loss of function for each case. Otherwise, designers can add expensive equipment without resolving the actual reliability requirement.<\/p>\n\n\n\n

Review temporary construction supplies separately. They may support installation activities but should not silently become the permanent commissioning basis. Record their protection, grounding, capacity and isolation arrangements. Before energization, verify that all temporary connections affecting the permanent auxiliary system have been removed or explicitly accepted under the commissioning procedure.<\/p>\n\n\n\n

\"Dry-type
AI-generated illustration of station-service AC equipment; not an actual installation.<\/figcaption><\/figure>\n\n\n\n

Coordinate the station-service transformer and AC board<\/h2>\n\n\n\n

The station-service transformer rating should follow the agreed coincident demand and growth allowance. Include charger recovery demand and motor starting in the assessment. The AC board must also be checked against the prospective fault duty and the protective devices used on its incomers and outgoing feeders. A larger transformer can improve starting voltage performance while increasing downstream fault duty, so capacity cannot be changed independently of the board review.<\/p>\n\n\n\n

For an indoor installation, coordinate heat rejection, access and the route for future removal. An auxiliary transformer squeezed into an available corner may obstruct cable termination or maintenance. Zisheng Electric’s transformer room layout guide<\/a> provides related questions for ventilation and access coordination. Final clearances must come from approved equipment drawings and the project requirements.<\/p>\n\n\n\n

Review alternatives such as a dry-type transformer<\/a> and the relevant low-voltage switchgear arrangement<\/a> against the actual application. These product links identify equipment families for discussion; they are not a claim that a particular catalog rating suits the project’s load schedule.<\/p>\n\n\n\n

Size DC duties around the required sequence of events<\/h2>\n\n\n\n

Battery autonomy is a duty requirement, not simply an ampere-hour label. The calculation needs the continuous load, event loads, duration, allowable end voltage and the selected battery’s performance information. Environmental conditions, ageing allowances and discharge characteristics belong in the approved design basis. Do not copy a battery capacity from a similar substation without checking the loads and operating sequence.<\/p>\n\n\n\n

Check voltage at the most remote critical device. The battery-terminal voltage alone does not show the voltage available at a trip coil after losses in distribution devices, cables and contacts. Review the circuit under the relevant event current and the agreed end-of-duty condition. The protection engineer, battery supplier and switchgear supplier should use the same voltage limits.<\/p>\n\n\n\n

Charger duty and recovery<\/h3>\n\n\n\n

Specify whether the charger must support continuous DC loads while recharging the battery and how the recovery requirement is defined. Confirm compatibility with the battery technology and its permitted operating conditions. For redundant chargers, identify load sharing, isolation and alarm behavior. A charger fault should be recognizable without requiring the operator to infer it from a later low-voltage alarm.<\/p>\n\n\n\n

The final settings sheet should identify approved operating modes and the authority permitted to alter settings. Record software or controller revisions where they influence operation. This avoids a situation in which factory settings, commissioning settings and the values shown in the handover document differ without a documented reason.<\/p>\n\n\n\n

\"Engineer
AI-generated illustration of battery, charger and DC distribution interfaces; not a test record.<\/figcaption><\/figure>\n\n\n\n

Make alarms and automatic transfers testable<\/h2>\n\n\n\n

Define the meaning of each signal. An AC supply-fail alarm, charger-fail alarm, DC low-voltage alarm and DC earth-fault alarm describe different conditions and demand different responses. State the source device, normal contact state, delay, terminal number, SCADA identifier and required operator action. Avoid one generic auxiliary-failure alarm where separate diagnosis is needed.<\/p>\n\n\n\n

If automatic source transfer is included, describe the sequence and interlocks in plain language before implementing logic. Identify loss detection, transfer permissives, any time delay, return-to-normal behavior and manual override. Confirm whether paralleling is permitted or prohibited by the project design. The test plan must demonstrate the specified behavior without creating an unintended connection between sources.<\/p>\n\n\n\n

Coordinate these checks with the switchgear commissioning plan<\/a>. A successful local lamp test does not prove that a remote alarm, trip or permissive reaches the intended destination. Acceptance should follow the complete signal path, with the operating equipment placed in a controlled condition by the responsible commissioning team.<\/p>\n\n\n\n

Use staged acceptance instead of one final checklist<\/h2>\n\n\n\n

Factory review should establish that the supplied equipment matches the approved drawings and load data. Check component ratings, terminal identification, enclosure arrangement, wiring documents, protection devices and applicable functional records. The FAT witness plan<\/a> should identify which auxiliary interfaces can be demonstrated at the factory and which require integrated site testing.<\/p>\n\n\n\n

Site acceptance then closes installation-dependent items: cable identity, polarity where relevant, termination quality, protective bonding, settings, isolation labels and end-to-end alarms. Functional tests should follow an approved method prepared by qualified personnel. This article does not provide instructions for live switching or battery work; the project-specific procedure must define safe isolation, responsibilities and test boundaries.<\/p>\n\n\n\n

Finally, demonstrate the agreed operating cases. Record the initial configuration, simulated failure, observed response, restored condition and any unresolved deviation. Where a result does not meet the design basis, identify whether the issue belongs to the calculation, equipment, wiring, settings or logic. Assign corrective action before marking the case accepted.<\/p>\n\n\n\n

\"Two
AI-generated illustration of auxiliary power acceptance planning; not actual commissioning evidence.<\/figcaption><\/figure>\n\n\n\n

A usable auxiliary-power interface register<\/h2>\n\n\n\n

The following example is hypothetical and illustrates document structure only. It does not describe an actual Zisheng Electric project.<\/em><\/p>\n\n\n\n