Power distribution, with purpose.
Generator load shedding keeps a paralleling system within its available capacity when generation is lost, a source trips, or demand rises beyond an approved limit. The design is not simply a relay that disconnects loads: it translates the owner’s operating priorities into measurable thresholds, output assignments, and a restoration plan that the generator controls and downstream equipment can coordinate with.
Start with a ranked load map
Build the load map around what must remain energized, what can tolerate a brief interruption, and what may be disconnected until capacity returns. For each feeder or load group, record normal and emergency kW and kVA, power factor, starting or inrush demand, operating schedule, and the consequence of losing power. Identify life-safety and legally required systems separately; their treatment must follow the project’s applicable codes and authority-having-jurisdiction requirements, not an assumed shed sequence.
The owner and engineer should approve the priority tiers before control logic is finalized. A practical map may identify critical loads as non-shed, a first shed tier for deferrable demand, and later tiers for loads that may remain off longer. These labels are planning tools, not a promise that every load can be switched without process effects. Confirm how each load behaves on interruption, whether local controls will restart it automatically, and whether a feeder contains mixed-priority circuits that need to be separated.
Representative outage sequence
For a hypothetical facility with three generators operating in parallel, imagine one unit trips while the remaining units continue carrying the bus. The controller detects the changed available capacity, and the approved logic sheds a designated lower-priority group if the remaining generation cannot support demand with the required reserve. A further deficit can trigger the next owner-approved tier. The actual trigger could be based on available kW, frequency, reserve margin, or a combination; the appropriate method depends on generator controls, system dynamics, and the project’s operating philosophy.
When a standby unit starts, synchronizes, and is accepted onto the bus, restoration should not automatically reconnect every shed load at once. A reviewed sequence can restore groups in priority order with intentional delays, verifying capacity before each step and accounting for motor starting and other transient demand. The owner must decide whether restoration is automatic, requires an operator command, or combines both approaches. A conservative staged return can protect system stability, but longer delays may affect production or building operations.

Define output behavior and interfaces
Discrete outputs turn control decisions into actions, such as operating a shunt-trip device, signaling a load-control panel, or requesting a response from another controller. Specify each output’s destination, normal state, energized or de-energized action, contact form, voltage and current requirements, isolation needs, and failure response. Confirm whether the receiving device expects a maintained state or a momentary signal, and whether a separate acknowledgement or status input is needed. Output count and electrical characteristics must be verified for the proposed equipment and controls.
Coordination requires an interface schedule across the paralleling switchgear, generator control system, protective devices, automatic transfer equipment, building management or energy-management systems, and any third-party load controls. Define which system owns each decision and which signals are exchanged, including source availability, breaker status, load-shed request, load-block status, and restoration permission as applicable. Avoid ambiguous commands that could cause a downstream controller to reconnect a load while the paralleling logic still considers it unavailable.
Balance stability, continuity, and recovery
More aggressive shedding can preserve frequency and reduce the risk of a wider outage, but it may disconnect useful loads earlier than the owner expects. Delayed or insufficient shedding may preserve service briefly while allowing overload, frequency decline, or protective trips to worsen the event. Engineering review should compare generator step-load capability, spinning reserve, load characteristics, protective coordination, and the time required to start and accept another unit. Settings should be grounded in the actual generator and system data rather than generic thresholds.
Restoration has its own risks. Large motors, compressors, transformers, and groups of electronic loads can create a substantial pickup or inrush demand, while process equipment may need an operator check before restart. The specification should address minimum off-time, restart permissives, failed-start handling, and what the system does if capacity falls again during restoration. Testing should validate the intended sequence using approved procedures and project-specific test conditions; a control narrative alone does not prove that field wiring and connected loads behave as expected.
Provide quote inputs and approval boundaries
For a useful quote, provide the one-line diagram, generator and paralleling-system data, bus and feeder schedule, available protective-device information, load list with priorities and demand characteristics, and the desired outage and recovery narrative. Include existing controller models, communications or hardwired interface requirements, output destinations, sequence timing expectations, applicable project specifications, and the required documentation or testing scope. Identify the owner, engineer, and other parties authorized to approve priorities, control intent, and changes.
The manufacturer can evaluate a proposed new switchgear build and its available control options against those inputs, but product availability, discrete I/O, components, ratings, short-circuit capability, standards, and any U.S.-origin requirements must be confirmed for the specific order. The owner and project engineer retain approval of which loads may be interrupted and the acceptable restoration behavior; interface responsibilities and field work must be expressly defined in the project scope. For Dallas–Fort Worth projects or shipments elsewhere, provide delivery constraints and site receiving requirements without assuming a local factory or installation service.
Specifications & planning
Review the details that matter for your application. Final specifications and availability should be confirmed for your project.
| Evaluation factor | Information to resolve |
|---|---|
| Load priority | Owner-approved shed and non-shed groups |
| Shed trigger | Capacity measure, threshold basis, and response delay; engineering review required |
| Discrete interface | Output destination, electrical characteristics, and expected state |
| Restoration | Priority order, delay, permissives, and operator approval |
| Quote basis | Drawings, equipment data, load schedule, scope, and project requirements |
