Backup Power for Connected Equipment: Start With the Outage Plan

When connected equipment loses its primary power, the important question is what the complete system must do next. Some installations need time for an orderly shutdown; others may need selected functions to continue for longer. A backup power device can support a plan, but its presence alone does not establish that every controller, network component and safety function will remain available.

Define the required response to an outage

Before requesting a backup-power quotation, identify the equipment and the required sequence when primary power fails. Does an operator need to save data, bring a process to a controlled state or maintain communication with another system? Who decides when the equipment can restart? The answers depend on the process and should be agreed by the people responsible for operations and safety.

The NIST Guide to Operational Technology Security says outage effects should be considered in operational technology architecture. It discusses alternative power for orderly shutdown as well as longer-term power where a continuity plan requires continued operation. These are planning considerations; the guide does not prescribe one backup duration for every machine.

List the loads that must be supported

Record each controller, operator terminal, communications device and other component that the agreed sequence depends on. Identify the equipment's power requirements from its current documentation and ask qualified electrical personnel to review the complete configuration. A controller that remains powered may still be unable to perform the desired function if its network or another required device has shut down.

Distinguish equipment that needs uninterrupted supply from equipment that must stop safely during an outage. Do not assume that every motor or robot arm should be connected to a battery backup. The correct architecture depends on the application, manufacturer's requirements, electrical design and safety assessment.

Treat runtime as conditional

A UPS runtime estimate depends on the connected load and battery condition. Schneider Electric's Easy-UPS runtime guidance notes that runtime varies with attached load, battery charge and battery age. That statement applies to the described product family; a buyer should obtain the relevant curves and instructions for the model actually offered.

When comparing quotations, ask what load, battery configuration, temperature and state of charge were assumed. A runtime at a light load should not be presented as the expected runtime at a different load. If the supplier provides an estimate, retain its assumptions and identify it as an estimate rather than a guarantee of a future outage duration.

Plan monitoring and maintenance

Record the backup device and battery identifiers, installation date, service responsibilities and the manufacturer's maintenance requirements. Decide who will receive and respond to alarms. Batteries and other components need ongoing attention, and a system installed years ago may not provide the same capacity as a new system under the same conditions.

Testing or replacing electrical equipment can affect production and may introduce hazards. Use qualified personnel, the manufacturer's instructions and the site's approved maintenance process. Do not disconnect primary power or perform a runtime test on a live process merely to check a quotation. Agree the scope, timing and safeguards of any test in advance.

Record dependencies and restart responsibilities

Document the interfaces between the backup supply, equipment controller, alarms and any external service. Identify which functions remain available and which are expected to stop. Where a process requires a controlled restart, specify who checks the equipment state and authorizes the next step. A power restoration event should not be treated as proof that every part of the process is ready to resume.

Include the communications path used to notify the responsible team. If an alarm depends on a network device that loses power earlier than the controller, the team may not receive the expected notice. This is a dependency to review in the site design, not a reason to connect equipment without electrical and operational approval. Record the outcome of that review with the outage plan.

The NIST guide also discusses recovery planning and restoring failed components. A site plan can identify the documents, contacts and checks needed after an outage. The plan should be reviewed when equipment or operating procedures change, and tested under an approved approach appropriate to the site's risks.

Ask for evidence at handover

Request the equipment list, supplier calculations, assumptions, manuals and maintenance schedule with the backup-power proposal. Agree which measurements or demonstrations are required for acceptance and who will perform them. If a runtime figure or a dependency is not verified, record it as an open item rather than silently relying on it.

For a related equipment record, see our asset inventory guide and browse the smart equipment archive. A clear outage plan connects the power equipment to the actual operational sequence it is meant to support.