LEVIATHAN SYSTEMS

Power

Rack PDUs for GPU Projects: Outlets, Metering and Scope

Technical contentPublished Updated

Compare rack PDUs by the exact part reference, physical outlet configuration, measurement level and remote-control function. Check the facility’s actual allocation separately from the PDU’s product rating. The buyer needs both an approved electrical arrangement and a clearly defined physical installation package; a managed or switched product label establishes neither on its own.

Define the question before comparing models

A request for a managed PDU can describe several different needs. Does the operator want to observe the combined load, obtain individual outlet readings or control an outlet remotely? Those requirements lead to different feature checks. A supplier can accurately describe a unit as managed while the buyer still lacks evidence that it provides the measurement detail the project expects.

Write the required observation or function in plain language before comparing product names. For example, “individual outlet readings in the operator’s chosen system” is more specific than “intelligent PDU.” Keep the requested measurement separate from the right to change power state. Monitoring access does not by itself establish authority to switch equipment.

Use the full manufacturer reference, regional variant, applicable documentation and any controller or firmware conditions when requesting confirmation. The examples here compare product descriptions; they do not select a PDU for an electrical design or recommend turning an outlet on or off.

Compare the same outlet count with different features

Schneider Electric’s current US marketplace pages make the distinction concrete within one named product generation. APDU11350ME describes PDU-level metering; APDU11350SW describes remote outlet control with PDU-level metering; APDU11350SM describes outlet-level and PDU-level metering together with remote outlet control. Each page identifies 48 outlets.

The comparison is deliberately narrow. It shows why matching the outlet count or reading only the shared family name cannot establish the feature set. It is not a ranking, a compatibility list for a particular GPU system or proof of stock, support entitlement or suitability in another country. Confirm the actual ordered reference and current documentation with the supplying party.

References: [S1][S2][S3]

Scroll the table horizontally on smaller screens.

Named manufacturer examples: shared outlet quantity, different documented functions
Exact referenceAdvertised outlet positionsMeasurement describedRemote outlet control describedSource
APDU11350ME48PDU levelNot described in the cited model description[S1]
APDU11350SW48PDU levelYes[S3]
APDU11350SM48Outlet and PDU levelYes[S2]

Source-qualified product-description comparison checked 15 October 2026. An omitted feature is not a universal impossibility claim. No input rating, circuit design, protective arrangement or deployment approval is derived from this table.

Count physical positions, not connector names

A combination outlet can accommodate more than one connector form at the same physical position. Schneider describes a four-in-one design in the cited family. That description does not multiply the number of positions available to connect equipment simultaneously. The advertised total and the actual outlet layout remain the useful starting points.

For a real package, request the exact outlet drawing and the approved equipment cord schedule. Record which equipment connection each position is intended to serve, the complete cord assembly reference and any required retention or mounting accessories. Do not infer a compatible cord, retention method or electrical limit merely because a connector designation looks familiar.

Count the requested connections from the approved equipment configuration. Dividing a rack power figure by an outlet rating does not establish how many individual power connections the delivered systems require. The responsible electrical and system owners must establish the actual arrangement; the physical team should receive an identifiable package rather than invent it from the GPU count.

References: [S1]

Read monitoring at the boundary it measures

A combined PDU reading and an individual outlet reading describe different boundaries. Ask which measurements the actual model exposes, where they are associated with the equipment record and what the receiving system retains. A statement that a product supports remote management does not answer all of those questions.

Consider a fictional buyer request for individual outlet usage in its existing monitoring platform. A proposed unit described only as “48-outlet managed” leaves the measurement level unresolved. A model page with aggregate metering answers a different question from one that explicitly describes outlet metering. Remote on/off capability would not fill the missing measurement evidence.

Even a documented outlet measurement needs the correct association to the equipment being reviewed. Where a device has multiple power connections, one outlet’s reading is not automatically the complete device result. Ask the system owner how those connections are represented. This article supplies no sampling-rate requirement, alarm threshold, diagnosis, accuracy acceptance rule or claim that a PDU meter proves workload performance.

References: [S1][S2][S3]

Keep facility allocation separate from the product

A manufacturer’s PDU specification describes a product. The facility’s permitted customer allocation is a separate input. Equinix’s published Secure Cabinet with kVA-Based Power documentation, for example, distinguishes a contracted draw cap from cabinet and circuit information. That is a provider-specific illustration, not the governing policy for every colocation site.

Obtain the actual facility confirmation and approved equipment arrangement from their responsible owners. Do not treat a larger product rating, an unused receptacle or a low observed reading as permission to add load. Likewise, two strips labelled A and B do not by themselves establish independent feeds or an accepted redundant arrangement. Those conclusions need the actual facility design and authorization.

Keep supplied units and measurement boundaries visible in the planning records. A product headline, a facility allowance and an observed load may refer to different quantities and conditions. Ask the qualified reviewer to reconcile them; do not silently convert an apparent-power allowance into an interchangeable real-power budget or apply a generic headroom percentage.

References: [E1]

Distinguish nameplate, TDP and observed power

A value can be expressed in watts and still answer the wrong planning question. A nameplate or product-specification value belongs to the identified product and the conditions its manufacturer states. Thermal design power belongs to a thermal-design definition for a component or product. A measured load belongs to the boundary, operating state and period that produced the observation. An observed peak also needs a definition; it is not automatically the largest possible instantaneous demand.

Intel's processor support note illustrates the difference: it describes TDP as a thermal-solution design target and separately discusses temporarily higher draw during turbo or certain workloads. Use that as a named processor example, not a universal definition for every GPU, a whole-server allowance or an invitation to set a power limit. For the purchased system, retain the exact manufacturer's specification and its stated conditions. Adding component TDP values does not account for every server component, conversion loss or operating condition.

Meter labels need the same care. The cited Schneider PM1125H manual defines its peak demand as the highest average reading since the last reset and retains the occurrence time. That is a specific documented statistic, not proof of an instantaneous transient or all future workload conditions. Request the measurement boundary, units, interval or averaging method, observation period, reset basis and relevant configuration before comparing two reported peaks. This is interpretation of supplied records, not a procedure for wiring a meter, taking live measurements or accepting its accuracy.

References: [I1][P3]

Scroll the table horizontally on smaller screens.

Power values in a project brief: identify the quantity before comparing the number
Label suppliedWhat to retain with itWhat it does not establish aloneSource
Nameplate or specification ratingExact equipment reference, rated quantity and applicable manufacturer conditionsActual observed demand, a contracted allocation or permission to add equipmentPlanning analysis
Component TDP or processor base powerThe component, its manufacturer definition and the stated configuration/workload basisA universal whole-server maximum or a measured rack load[I1]
Measured loadMetered boundary, quantity/unit, equipment state, observation time and methodA different boundary, all future workloads or approved expansion capacityPlanning analysis
Reported peakWhich statistic, averaging/interval basis, covered period and reset or collection historyAn instantaneous maximum simply because the report says peak[P3]

Original record-reading comparison. No protective-device, circuit, measurement, energization, power-cap or facility-capacity design is provided.

Read kW, kVA and MW with the quantity and boundary

NIST defines the watt as a power unit and the SI prefixes kilo and mega as factors of one thousand and one million. Thus 1 kW is 1000 W, and 1 MW is 1000 kW. These are decimal conversions, not the binary multiples sometimes used for computing storage. A prefix changes numerical scale; it does not identify whether a figure describes a component, a complete server, an IT room or an entire facility.

Keep real and apparent power distinct too. Schneider's metering documentation uses W or kW for real power and VA or kVA for apparent power, and its power-factor definition relates real power to apparent power. Changing kVA into kW therefore needs a valid relationship for the same boundary and conditions; it is not just removal of the letter A. Distinguish an actual load power factor from a product's separate output ratings or a contractual allowance. Do not insert an assumed factor because the equipment is described as modern or efficient.

In fictional EX-PU98, a supplied data row explicitly stipulates 100 kVA of apparent load and a true power factor of 0.90 for that same load and observation. The corresponding real-power arithmetic is 90 kW, or 0.09 MW. The factor and quantities are invented example inputs, not a typical server value, a measured customer record or a permitted load. Without the stipulated relationship, the 100 kVA figure alone would not justify entering 100 kW or 90 kW in the brief. No wiring, phase calculation, supply selection or operating adjustment follows from this example.

References: [N1][P1][P2]

Scroll the table horizontally on smaller screens.

Quantity and scale: original examples for reading supplied figures
Supplied figureValid interpretation or conversionBoundary still neededSource
500 kW real power0.5 MW real powerWhich equipment/facility boundary and whether rated, allocated or observed[N1]
0.5 MW facility headline500 kW at the stated facility boundaryWhether this is utility input, IT allocation, total supported plant or another defined quantity[N1]
100 kVA with no applicable relationshipApparent-power figure retained as supplied; no real-power total derivedApplicable load/measurement basis or separately stated real-power rating[P1][P2]
EX-PU98:100 kVA and stipulated true PF0.90 for the same load100 × 0.90 = 90 kW = 0.09 MW, under those fictional inputsNo conclusion about a purchased product, facility allowance or permissible load[N1][P2]

Educational unit and quantity arithmetic only. No generic power factor, headroom percentage, PUE, supply size or safe operating point is assumed.

Reconcile a power brief without inventing spare capacity

Fictional EX-PU99 combines a facility note headed 1.2 MW, a cabinet allowance stated as 80 kVA, an offered rack-PDU product rating of 60 kW and a supplied rack report showing 34 kW as a 15-minute average during an identified observation window. These four inputs concern different kinds of evidence. Converting 1.2 MW to 1200 kW is valid arithmetic, but it does not allocate any of that quantity to this cabinet. The cabinet allowance also remains in kVA until its governing meaning and applicable relationship are established by the responsible parties.

The rack report is an observation under its stated conditions. Subtracting its 34 kW average from the product's 60 kW rating gives a numerical difference, not an approved additional load. The report does not identify every future workload or other limiting interface, and the product rating is not the customer's allocation. Nor may the two feeds of an unverified A/B arrangement be added to invent one available pool. The facility and electrical/system owners must return the actual allocation, equipment basis and permitted arrangement.

A useful brief keeps the original values, identifies their sources and boundaries, normalizes only valid units, and names the unresolved comparison. Separate the requested physical mounting or documentation scope from the qualified capacity decision. If the relevant document, measurement condition or allocation is missing, record that specific gap instead of entering zero, an assumed efficiency or a standard spare-capacity percentage.

References: [E1]

Scroll the table horizontally on smaller screens.

EX-PU99: four fictional inputs, four different evidentiary boundaries
Input in the fictional briefUseful returned clarificationConclusion to withholdSource
Facility note:1.2 MWIdentify the defined facility/IT boundary, issue and whether capacity is committed or merely described1200 kW is available to this particular cabinetPlanning analysis
Cabinet allowance:80 kVARetain the actual provider allocation and its applicable quantities/conditions80 kW or a whole-facility allocation applies automatically[E1]
Offered rack-PDU rating:60 kWKeep the exact product reference and approved arrangement separate from allocationThe PDU authorizes that load at the customer sitePlanning analysis
Supplied rack report:34 kW 15-minute averageRetain boundary, equipment/workload state, period, method and responsible source26 kW of expansion capacity has been approvedPlanning analysis

All quantities, boundaries and returned questions are fictional. No electrical design, site capacity, load test, redundancy, customer result or legal interpretation is established.

Resolve a specific feature gap in the order

The fictional request below asks for individual outlet readings and a defined physical installation package. It does not ask the installer to design circuits or configure remote switching. A useful supplier clarification identifies what the exact proposal establishes and what still needs confirmation. Keep the agreed outcome with the equipment and work-package references rather than replacing it with the word approved.

If a supplier proposes another reference, repeat the affected feature and interface checks. A manufacturer’s suggested successor or similar-looking product name is not evidence that every mounting, cord, controller, monitoring or facility condition remains unchanged. The customer and relevant owners decide the acceptable substitution. No quotation, customer project or actual acceptance outcome is represented here.

Scroll the table horizontally on smaller screens.

Original hypothetical buyer clarification: a 48-outlet managed PDU request
Requested itemWhat the offered description establishesFocused clarificationSource
Individual outlet readingsOnly “managed” and a total outlet count are statedIdentify the exact model and documented measurement level; do not infer per-outlet metering.Planning analysis
Use in the customer’s monitoring systemA product page lists management capabilityConfirm the actual version, exposed measurements and required integration with the responsible system owner.Planning analysis
Power arrangement for the delivered equipmentA product reference and equipment list are availableObtain the qualified facility/electrical disposition and approved connection package; no capacity calculation is made here.Planning analysis
Physical installation and handoffThe request uses the broad word installationIdentify permitted mounting, customer-provided accessories, any separately agreed cord work and the records to deliver.Planning analysis

Original illustrative comparison questions, not an electrical design, product recommendation, configuration recipe, legal approval register or company SOP.

Scope the physical work without commissioning promises

For a scope discussion, provide the exact equipment and PDU references, approved rack positions, applicable mounting instructions, customer-provided accessories, site conditions and requested records. Identify who supplies the electrical design and facility release and who owns monitoring integration. Separate an observed label or mounting record from measured electrical performance.

Leviathan can discuss rack-and-stack, physical equipment mounting, cabling, labeling, inspection, remediation and agreed documentation within the engagement. Power-cord connections to existing approved equipment and rack-mounted PDUs may be considered only in a separately agreed scope, subject to OEM instructions, facility authorization, personnel qualifications and insurance. This is not an offer to construct electrical distribution, hardwire circuits, energize equipment or perform live electrical measurements.

Identify the appointed equipment/material supplier, approved configuration, quantities and delivery responsibilities before agreeing the physical work. Liquid-side work remains excluded; full system or software commissioning is not a standard service. Monitoring configuration, alarm policy, remote switching authority and electrical acceptance need their own responsible owners. Tell us about the project, and our team will follow up to discuss scope, requirements and availability.

References: [L1]

Common planning questions

Does a switched PDU necessarily meter every outlet?

Do not infer that from the word switched. The cited APDU11350SW description identifies PDU-level metering and remote outlet control, while APDU11350SM explicitly adds outlet-level metering. Confirm the exact product and current documentation for the actual requirement.

Does a four-in-one receptacle provide four simultaneous outlet positions?

No. The cited manufacturer describes multiple connector forms at one combination outlet. Use the actual outlet count and layout, then have the approved equipment/cord arrangement reconciled for the project.

Does the PDU rating establish the power we may draw in colocation?

No. The facility allocation and approved electrical arrangement are separate inputs. The Equinix example illustrates a provider-specific draw-cap model; the actual customer site and agreement control, with qualified review where required.

Will Leviathan commission the PDU or configure remote switching?

Full system/software commissioning, facility electrical work and energization are excluded. Leviathan can discuss the authorized physical package and records. Existing approved equipment/rack-PDU cord connections require a separately agreed scope and confirmed OEM, site, qualification and insurance conditions.

Can a facility MW figure or a kVA cabinet allowance be copied directly into a rack kW budget?

A MW-to-kW conversion changes numerical scale, not the allocation boundary. kVA describes apparent power, while kW describes real power; an applicable relationship or separately stated rating is needed before comparing them. The responsible facility and system/electrical owners must establish the actual allocation and arrangement.

Does a reported peak or a low average prove room for more equipment?

A reported peak needs its definition, boundary, averaging/interval basis and observation/reset period. A low average or an offered PDU rating does not establish the permitted additional load or every future condition. Preserve the applicable allocation and qualified capacity decision separately.

Primary sources

  1. [S1] Schneider Electric: APDU11350ME Gen 2 metered rack PDUChecked 2026-10-15. Exact US marketplace model identity,48-position headline, PDU-level measurement and combination-outlet description only. No voltage/current/capacity, compatibility, availability, cost or engineering recommendation adopted.
  2. [S2] Schneider Electric: APDU11350SM Gen 2 switched metered-outlet rack PDUChecked 2026-10-15. Exact model’s48-position headline, outlet/PDU metering and remote-switching feature distinction only; no operating instruction, firmware guarantee, accuracy or electrical approval.
  3. [S3] Schneider Electric: APDU11350SW Gen 2 switched rack PDUChecked 2026-10-15. Exact model’s48-position headline and description of remote outlet control plus PDU-level measurement. No blanket impossibility claim about undocumented features or other versions.
  4. [E1] Equinix: Secure Cabinet with kVA-Based PowerChecked 2026-10-15. Provider-specific distinction between contracted draw cap, cabinet and circuit information only. No policy adoption for another site, numerical limit, circuit design, legal interpretation or customer capacity decision.
  5. [L1] Leviathan Rack-and-Stack InstallationChecked 2026-10-15. Approved conditional physical-service and separately scoped power-cord boundary, corroborated by lib/company.ts founder wording. Purchasing and delivery require an approved scope. No electrical installation, energization, live measurement or commissioning authority established.
  6. [N1] NIST SP811 chapter4: power units and SI decimal prefixesChecked 2026-10-19. Watt power unit and decimal kilo/mega factors only. No facility-power boundary, engineering capacity or electrical installation rule inferred.
  7. [P1] Schneider PM1125H manual: real, reactive and apparent powerChecked 2026-10-19. Quantity/unit distinctions W/kW real and VA/kVA apparent only. No wiring, sizing, meter operation or actual equipment suitability adopted.
  8. [P2] Schneider PM5500 manual: power factor and true versus displacement PFChecked 2026-10-19. Real-to-apparent power ratio and true-PF versus displacement-PF distinction only. No assumed factor for actual IT loads, product output capability or design rule.
  9. [P3] Schneider PM1125H manual: peak demandChecked 2026-10-19. Named meter definition of highest average since reset and occurrence time only. No meter installation/reset/configuration, measurement protocol or accuracy acceptance supplied.
  10. [I1] Intel support000055611: TDP purpose and processor power conditionsChecked 2026-10-19. Named processor thermal-solution design-target purpose and separately described temporary turbo/workload draw only. Not a universal GPU/whole-server TDP definition or a power-limit/thermal/electrical design instruction.

Discuss the approved rack installation package

Share the equipment and PDU references, rack positions, site release and required physical records. Our team will follow up to discuss scope, requirements and availability.

Discuss a ProjectEmail Project Scope