What should drive the choice?
Buy local metering for a staffed rack with simple load checks. Buy remote monitoring when someone will own alerts, history and management network access.
Research based on linked manufacturer documentation. We have not physically tested this equipment.
Choose around the person who must see the load
The useful distinction between a metered PDU and a monitored PDU is where the power information reaches the operator. A local display serves a person standing at the rack. A network interface can put information into a management workflow elsewhere. Neither label by itself tells you whether every outlet is measured, whether outlets can be switched, or whether a particular alert reaches the right person. Those are separate purchasing questions.
Terminology differs across product families. Eaton describes local metered units separately from monitored units, while its metered input product family includes remote monitoring. Treat the label as a starting point and compare the exact data sheet. Eaton’s PDU definitions and metered input family page illustrate why a keyword match alone is insufficient.
A buyer replacing a working basic PDU should first name the missing operational capability. Is the problem that technicians cannot see remaining capacity during additions? Is it that nobody knows a closet is near its limit until the next visit? Is management asking for a trend by rack? Each problem implies different data, access and ownership. Buying an Ethernet port without that requirement can create another device to maintain without solving the actual problem.
Write the requirement before comparing prices
Use a small requirements matrix with a row for input current, input power, energy history, bank current, outlet current, threshold alarms and remote outlet control. Mark each row required, useful or unnecessary. A salesperson should be able to map every required row to the exact SKU and firmware documentation. If the product page says monitoring without identifying the measurement boundary, leave that row unresolved rather than assuming outlet precision.
Then add the operational requirements: supported management protocol, authentication, time synchronization, firmware support, alert destination and access when the normal office network is unavailable. These details can matter more than screen appearance. A dashboard that only one former administrator can access is a weak source of operational evidence, even if the PDU has excellent electrical specifications.
| Requirement | Local metering may fit | Remote monitoring may fit |
|---|---|---|
| Adding equipment at a staffed rack | Display is accessible and checked before additions | A remote approver needs the same information |
| Trend investigation | Someone records readings consistently | A supported system records timestamped data |
| After-hours response | A technician is present | An assigned responder receives actionable alerts |
| Per-device attribution | Not established by the label | Still requires explicit outlet measurement support |
A closet example shows the real value of visibility
Consider an illustrative branch closet that is visited monthly. The technician can read a local meter during each visit, but a new server workload may change the load the day after that visit. Remote monitoring could shorten the interval between a change and an investigation. That benefit comes from the response process, not from a claim that networking increases the PDU’s electrical capacity.
Now consider a lab rack attended every day. The team changes equipment frequently, records its planned power budget and does not need unattended alerts. A visible current reading at the point of change may address the immediate requirement. A monitored model can still be useful, but its business case should include a named owner, expected data use and support cost. Avoid treating every remotely accessible feature as an automatic productivity gain.
For both racks, define the action associated with a threshold before enabling it. A warning might lead to checking the inventory, investigating a changed workload or postponing an addition. It should not automatically cause arbitrary power interruption. Setpoints and capacity limits must come from the installed equipment ratings and the site’s approved operating limits, rather than a generic percentage copied from another rack.
Input totals and outlet data answer different questions
Input measurement is useful for the rack total and changes over time. Bank measurement can help locate which group is carrying a load. Outlet measurement can support device-level investigation, but requires accurate mapping between outlets and equipment. If a server has two supplies on different feeds, one outlet does not represent its total consumption. If a management controller and server share an external supply, the outlet might cover more than one logical asset.
Decide the measurement boundary you actually need. For a rack with a small number of known devices, an input total plus a reliable inventory may be sufficient. For chargeback or individual equipment investigation, ask about measurement accuracy, sampling, energy accumulation and export behavior. Do not turn a current reading into a billing claim without checking the manufacturer’s specifications for that purpose.
Even detailed measurement does not establish spare capacity on an upstream circuit. A PDU may only see part of a shared supply. The facility record and approved electrical design remain separate evidence. Keep the meter reading in the worksheet alongside the upstream limit, not in place of it.
Network monitoring adds a small system to maintain
A network PDU needs more than an available switch port. Before ordering, decide how it will receive an address, who can administer it, which management system will poll it and how configuration changes are recorded. Confirm that firmware updates can be obtained for the intended ownership period. Review the supported security settings with the person who owns the management network.
Ask what happens to monitoring when the switch serving the closet loses power. Power data that disappears during the event may still be useful afterward, but it is different from an out-of-band alarm. The purchase brief should state the availability assumption instead of silently relying on the same equipment being monitored.
A local screen remains useful on many remotely monitored units. Check its position in the installed orientation. A display blocked by rear cable bundles does not help a visiting technician. Similarly, a network module placed where cables cannot be serviced can make a sensible feature surprisingly expensive to operate.
Compare matched products rather than management labels
Our matched 120V Eaton comparison uses the local-meter PDUMH15, monitored PDUMNH15 and switched PDUMH15NET2LX to separate those decisions. The monitored PDUMNH15 is specified with eight NEMA 5-15R outlets, a 12-foot input cord and an LX interface. That combination is not interchangeable with every locally metered SKU. See the exact PDUMNH15 specification.
When two shortlisted units differ in outlet count, cord length or mounting position, price the complete arrangement you need. A lower unit price can disappear if the outlet layout forces additional hardware or creates unsuitable cable runs. Conversely, paying for unused remote control because a monitored SKU has fewer outlets is a sign to widen the shortlist.
The purchase order should identify voltage, input connector, continuous load rating, outlet mix, mounting hardware and the required monitoring functions. Request written clarification for any ambiguous feature. Choose the least complex model that fulfills those documented requirements, then include monitoring ownership in the handover so its value survives the installation.
Sources and research basis
- Eaton rack mount PDU solutions and feature definitionsPrimary documentation · checked 15 October 2026
- Eaton metered input rack PDU familyPrimary documentation · checked 15 October 2026
- Eaton PDUMNH15 monitored PDU specificationsPrimary documentation · checked 15 October 2026
Manufacturer specifications describe the documented configuration. Buying recommendations are our interpretation of those features. No original runtime, acoustic, efficiency, switching or software test is claimed. Report a correction.