Describe the operating pattern, not only the load
Equipment duty cycle describes how often a load operates, how long it remains energized, and what happens between operating periods. A load that runs steadily at a predictable level presents different selection questions from one that starts and stops frequently, operates in short intense bursts, or alternates between light and heavy demand. Average demand alone can obscure the electrical and thermal stresses created by repeated operation. For a useful specification, document expected operating hours, starts or switching events per hour or day, typical run duration, idle intervals, and anticipated changes across shifts or seasons. Identify whether operation is continuous, intermittent, cyclic, standby, or emergency-related, and explain any unusual sequence. These details give the design team context for reviewing the equipment’s intended service. They also help distinguish normal operating conditions from occasional events that should be addressed through separate protection or system design decisions.
Connect load duration to thermal considerations
Current flowing through conductors and switching components produces heat, so the time profile of a load matters alongside its magnitude. A brief demand peak and a sustained demand at the same current are not necessarily equivalent conditions for equipment evaluation. Repeated cycles can also leave less time for components to cool between operations. Provide expected current or demand by operating state, the duration of each state, and the interval before the next cycle. Where available, include measured load profiles, motor or process operating data, and anticipated future expansion. Engineers can use this information to assess thermal performance in the context of the proposed assembly and installation, including ambient conditions and enclosure considerations. Do not treat an assumed duty cycle as a substitute for required ratings or protection. Qualified professionals must determine the applicable ratings, protective devices, and code requirements for the project, using verified equipment data and system conditions.
| System | Voltage, phase, current and available fault current |
|---|---|
| Configuration | Lineup, protection, controls and enclosure as specified |
| Compliance | Applicable standards and listing confirmed for the assembly |
| Delivery | California and nationwide; schedule confirmed by quote |
Account for starting, switching, and transient events
Operating frequency includes more than how many hours equipment runs. Frequent motor starts, switching operations, transformer energization, or abrupt process changes may create inrush, transient, or repeated mechanical demands that deserve review. Describe which loads start together, whether starting is direct or controlled by other equipment, and whether the sequence is expected to change. Note any cycling that could cause protective devices to operate during normal service, while leaving settings and protection decisions to qualified engineers. If loads are supplied by variable-frequency drives, soft starters, or other power-electronic equipment, identify them and provide relevant manufacturer data when available. Their behavior can affect system characteristics and coordination considerations. Avoid relying on a simple label such as “heavy duty” to convey these details. A clear event sequence, expected frequency, and duration lets the design team ask focused questions about switching duty, protection, and the relationship between the equipment and connected loads.
Consider standby and emergency operation separately
Standby or emergency loads may run infrequently but still need to perform under defined conditions. Specify how often the system will be tested, the expected duration of a test or actual operation, and whether loads transfer in stages or start simultaneously. Clarify which loads are essential, what operating sequence is expected, and whether a source transfer or restoration event changes the duty profile. Infrequent use should not be interpreted as permission to relax requirements: the equipment must be evaluated for the intended system conditions and applicable safety obligations. Where emergency, backup, or other special service is involved, identify governing project requirements and have qualified professionals determine applicable codes, protection, and ratings. For medium- or high-voltage equipment, identify the standards applicable to that specific equipment and verify them for the project; requirements should not be assumed from a low-voltage product category. Keep testing duty distinct from expected service duty so both can be reviewed.
Put duty-cycle assumptions into the specification
A useful equipment specification records both the stated operating profile and the basis for it. Include expected load levels, cycle duration, operating frequency, annual or seasonal variation, starting sequence, standby conditions, and known future changes. Identify assumptions that remain uncertain, such as a process still under development, and state who will confirm them before design is finalized. Attach load studies, one-line diagrams, control sequences, or equipment data where they help explain the duty. Ask the switchgear builder to review the information against the requested equipment scope and flag missing inputs or constraints for resolution. If the operating profile changes after submittal, communicate the change promptly; a revised duty cycle may affect equipment selection, protective coordination, or project documentation. For projects with schedule-sensitive needs, discuss options early, recognizing that feasibility and timing depend on project review. A documented, realistic duty profile supports a more informed selection and clearer expectations among the owner, engineer, contractor, and manufacturer.
