Draw power equipment on the same plan
Power devices should not live in a separate note. Put the UPS and PDU on the canvas with the network devices they support. This makes the plan easier to review before hardware is purchased.
HLBuilder includes UPS and PDU node types, so power planning can sit next to network planning instead of after it.
Protect the gateway and storage path
A useful UPS plan starts with the devices that keep the lab reachable and recoverable. That usually means the router, switch, and storage device need attention before experimental hosts.
A visual example can show which devices should stay powered during a short outage. The details of runtime still need real hardware specs, but the dependency map can be drawn early.
Tie power decisions to services
Service placement affects power planning. A DNS host, backup target, or storage device has a different power need from a temporary test node. HLBuilder can show those service hosts on the same diagram as the UPS.
This gives the user a planning path: choose services, place hosts, then decide which hardware needs protected power.
Builder checks
Check
UPS and PDU nodes are visible.
Check
Gateway and storage devices are marked as protected when needed.
Check
Experimental hosts are not treated the same as core infrastructure.
Check
Power planning is reviewed before the shopping list.
Common questions
Should a UPS be included in a homelab diagram?
Yes, when power behavior matters. A visible UPS node shows which devices are expected to stay online or shut down cleanly.
Does HLBuilder calculate UPS runtime?
HLBuilder can show power equipment and device roles. Runtime still depends on the actual UPS and load selected by the user.