Technical GuideATM UPS Sizing: Convert the Device Load into a Clear RFQ
A device-level sizing guide: derive capacity from real watts, VA and working states, without repeating branch-network architecture.
Read engineering guide
Equipment-level UPS sizing
A UPS load sizing guide should use the complete operating chain, not a device category or nameplate shortcut. These articles show what to measure for payment, compute, network, storage, security, voice and mixed-rack systems.
For system integrators, IT teams, ELV contractors and buyers preparing a measurable UPS load schedule or RFQ.
Answer first
Record each device's real input, operating state and dependency path, then total watts and VA, apply the required reserve and runtime policy, and document every excluded load.
Measure AC or DC input at the correct boundary and avoid double-counting downstream loads.
Include network, storage, displays and shutdown dependencies needed for the required service.
Separate incompatible peripherals, dedicated supplies and approved egress or alarm behavior.
Decision area 01
Convert ATM, POS and server inputs into a load schedule without using cabinet size or rack height as a power value.
Technical GuideA device-level sizing guide: derive capacity from real watts, VA and working states, without repeating branch-network architecture.
Read engineering guide
Technical GuideA POS terminal rarely runs by itself. It sits on the same counter as a receipt printer, a card reader, a cash drawer and a router that links the store to a payment backend.
Read engineering guide
Technical GuideDevice-level focus on server configuration, redundant PSUs and load state rather than room-wide topology. Plan the project from the server configuration, measured demand, PSU behavior and shutdown integration.
Read engineering guideDecision area 02
Size PoE, NAS, NVR and video-wall support around the complete processing, storage and network path.
Technical GuideKeep the powered-device demand, the switch PoE budget, and the switch AC input as three separate boundaries. Plan the project from the switch input demand, powered-device list, and required backed-up port groups.
Read engineering guide
Technical GuideFocus on NAS operating and write dependencies for device-level UPS sizing, without repeating the B3 topology comparison.
Read engineering guide
Technical GuideCount the built-in PoE, external switches and the NVR unit as separate device-level loads. Plan the project from the NVR configuration, hard-drive count, PoE arrangement and recording objective.
Read engineering guide
Technical GuideControllers, decoders, encoders and LED panels hold different roles; a controller UPS is not a wall-wide runtime figure.
Read engineering guideDecision area 03
Distinguish controllers, locks, dedicated alarm supplies, routers, ONTs, PBX and gateway dependencies before adding capacity.
Technical GuideAn access-control system looks like one load on a one-line diagram, but it breaks into several power consumers with different behavior.
Read engineering guide
Technical GuideKeep the special compliance direction: a dedicated supply, batteries and panel requirements cannot be replaced by a desktop UPS.
Read engineering guide
Technical GuideChoose a DC mini UPS by output voltage, current, polarity and connector for each device, then confirm the combined wattage.
Read engineering guide
Technical GuideSize the UPS for the device-level inputs and the PoE phone power boundary of an IP-PBX and voice gateway package, without restating the whole voice-system architecture.
Read engineering guideDecision area 04
Coordinate industrial computers, printers, monitoring workstations and mixed-device racks with clear outlet and dependency assignments.
Technical GuideBase the backup choice on the single device's power input, the cabinet space, and a local action that works without a network.
Read engineering guide
Technical GuideSeparate printing technology and peak demand, so a low-power receipt printer's sizing is not copied onto a laser device.
Read engineering guide
Technical GuideFocus the workstation UPS decision on CPU and GPU decode load and the required screens, without repeating the full video wall discussion.
Read engineering guide
Technical GuideCombine already-sized single devices into a power group, handling outlets, PDUs and repeated power. Plan the project from the rack device schedule, outlet requirements and essential-service grouping.
Read engineering guidePrepare a useful UPS RFQ
A model request is more reliable when the supplier receives the same load, source, runtime, environment and acceptance assumptions used in the design.
Device models, quantities and power-input data
Normal, peak and startup operating states
AC/DC conversion and PoE counting boundary
Network, storage and shutdown dependencies
Required reserve, runtime and outlet assignment
Excluded devices and dedicated-supply responsibilities