A battery-backed computer is not much use for cloud work if the office router loses power. Equally, keeping a network switch running will not protect unsaved work on an unprotected desktop. An office UPS plan should begin with the activity you need to preserve, then identify every device that activity depends on.
For a UAE office, that might mean keeping a small network available during a short interruption, giving staff time to save work, or allowing a local server to shut down cleanly. These are different objectives. Write down the required duration and the acceptable interruption before comparing equipment.
Map the complete power dependency
List the internet termination device, firewall or router, core switch, wireless access points and any local system needed for the chosen activity. Include power adapters and Power over Ethernet loads. An access point powered by a switch depends on the switch remaining powered; a separate injector adds another device to check.
A simple example is a reception team using a cloud booking system. Protecting its laptop charger alone may not preserve access. The local network path and provider connection matter too. A UPS cannot guarantee that equipment outside your premises, the internet provider or the cloud application remains available.
- Essential continuity: devices needed for the specific activity you intend to maintain.
- Controlled shutdown: systems that must save state and stop safely.
- Nonessential loads: equipment that does not need battery power for the agreed objective.
Have IT and the business owner approve this list together. Do not let spare UPS sockets become an invitation to connect extra equipment without checking capacity.
Check load capacity and runtime separately
Watts and VA describe different aspects of electrical load. Check both the UPS's watt and VA limits against the connected equipment, allowing appropriate headroom and startup behaviour. A VA number alone does not tell you how many minutes the battery will provide.
Runtime depends on the connected load and battery configuration. Compare the manufacturer's runtime data at the expected load, then validate the installed arrangement. Schneider Electric's UPS selection guide distinguishes capacity, runtime and battery-backed versus surge-only outlets.
Ask the supplier to document the load assumptions and the exact proposed model. Include local voltage and connector compatibility, space, ventilation, maintenance access and any management accessory needed. Avoid selecting a unit only because another office uses the same model.
As part of ITZ's office network planning service, you can discuss the network dependency list and required continuity. Plan an office network power review with your equipment inventory and the business activity that must remain available.
Plan what happens before the battery runs out
A UPS has finite runtime. If a server must shut down, allow time for its applications, virtual machines and operating system to stop in the correct order. Confirm that the selected hardware and software support the required communication and shutdown method.
Schneider Electric describes PowerChute management options for graceful shutdown, with compatibility depending on the UPS and management arrangement. Treat this as a capability to verify for the proposed equipment, not a feature to assume is included with every battery backup.
Document the restart sequence as carefully as the shutdown. For example, storage or network services may need to be ready before an application starts. Decide who checks the system after power returns and how staff learn whether work can resume.
Use an agreed acceptance test
- Record the installed devices, outlet assignments, load reading and battery status.
- Check that monitoring alerts reach the nominated person through a usable route.
- Arrange a maintenance window and follow the manufacturer's supported test method with a qualified technician.
- Verify the chosen business activity during battery operation and record interruptions.
- Check that any configured shutdown completes with a suitable reserve rather than at battery exhaustion.
- Restore normal operation and confirm the network, applications and monitoring recover as intended.
Do not improvise electrical work or disconnect production power to discover what happens. The test plan should include a safe stopping point, recovery responsibilities and notification to affected staff. A brief self-test is useful, but it does not demonstrate every application dependency or the full required runtime.
Keep the plan current
Reassess the load when switches, access points or servers change. Include battery condition, alerts and maintenance in the support record. Power continuity also does not replace backup and recovery planning; a restore test answers a different question about whether data and applications can be recovered.
Plan your office network power review
Give ITZ your network equipment list, any local servers and the activity you need to preserve during an interruption. Request a scope covering dependencies, load checks, management compatibility and an acceptance test. Electrical installation requirements should be confirmed with the appropriate qualified provider.
