Specify a C13/C19 PDU by starting with the rack power architecture, then confirming voltage, phase, input plug, circuit capacity, outlet mix, mounting position, monitoring, environmental sensing, and regional compliance. For a multi-rack deployment, standardize the specification where possible, but allow outlet density and monitoring features to vary by rack load and equipment type.
- Choose outlet quantity and C13/C19 ratio from the equipment schedule, not from a generic rack template.
- Validate input voltage, phase, breaker capacity, and connector compatibility before approving the Rack PDU.
- Use basic units for straightforward distribution and intelligent units when metering, alarms, or remote management are required.
- Separate the base cabinet design from optional monitoring, sensors, cable assemblies, and regional plug configurations.
A multi-rack Data Center PDU specification must balance electrical compatibility, space utilization, operational visibility, and future expansion. The distinction between C13 and C19 matters because C13-to-C14 cabling is commonly used in server rooms, while C19 connections are more suitable for higher-power equipment, as summarized by UltraEdge’s PDU definition. Vertiv also describes combination C13/C19 outlets as a way to reduce human error through three operational improvements, making outlet selection relevant to both engineering and day-to-day operations.
1. Define the rack power architecture before selecting outlets
The correct specification begins with the rack’s electrical architecture rather than the outlet count. Document the utility or UPS source, nominal voltage, phase arrangement, available circuit capacity, redundancy model, and the expected load per rack. A PDU can distribute power safely only when its input design is compatible with the upstream distribution system and the equipment connected downstream.
For a dual-corded server, the specification should normally account for two independent power paths. Each path may use a separate vertical unit, separate branch circuit, or separate upstream source, depending on the data center design. The important requirement is that one PDU failure or one upstream maintenance event should not unintentionally remove both power feeds from a critical device.
Use a rack-by-rack load schedule to prevent overgeneralization across the facility. A conventional rack may contain mostly C13-fed servers and network equipment, while a high-density compute rack may require more C19 outlets and a different circuit strategy. Record both connected load and expected operating load, and ask the electrical engineer to confirm the applicable derating, protection, and local installation requirements.
Minimum electrical schedule
- Nominal voltage and allowable operating range.
- Single-phase or three-phase input arrangement.
- Input plug and cable length.
- Branch-circuit rating and protective-device coordination.
- Number of power paths per rack.
- Expected connected load, normal load, and expansion allowance.
- Required outlet types, outlet quantity, and outlet orientation.
2. Build the C13/C19 outlet mix from the equipment schedule
The right C13/C19 ratio is the one that matches the actual equipment connectors while preserving controlled expansion. C13 outlets are commonly selected for general servers, switches, and storage devices, whereas C19 outlets are typically considered for higher-power equipment and compatible high-current cabling. The final choice must follow the equipment manufacturer’s inlet specification and the applicable cable standard.
Do not treat a combination outlet as a substitute for electrical planning. Combination designs can improve deployment flexibility and reduce connector-selection mistakes, but the PDU input rating, branch protection, internal bus design, and outlet grouping still determine how much power can be delivered safely. Vertiv’s discussion of combination outlets provides a useful reference for the human-error reduction objective: read the Vertiv explanation of combination rack outlets.
| Equipment category | Typical outlet consideration | Planning question | Recommended verification |
|---|---|---|---|
| General server | C13 often used | Does the equipment use a C14 inlet? | Confirm the manufacturer cable and inlet data |
| Network switch | C13 often used | Are dual power supplies installed? | Count both feeds and reserve outlet capacity |
| High-power compute system | C19 may be required | Does the input cable require a C20 connection? | Check current, voltage, and cable compatibility |
| Mixed-purpose rack | C13/C19 combination | Will future equipment change the outlet ratio? | Use the approved equipment schedule and expansion plan |
Outlet quantity should also account for power supplies, maintenance equipment, and planned additions. Avoid filling every position if doing so would make cable routing difficult or leave no practical expansion capacity. For high-density deployments, outlet grouping and clear labeling can be as important as the total number of receptacles.
3. Select 0U, 1U, or 1.5U mounting deliberately
Mounting position affects usable rack space, cable access, airflow, and serviceability. A 0U vertical PDU is intended to use the side or rear area of a cabinet without consuming front rack units, while 1U and 1.5U horizontal units are suited to standard rack positions at the front or rear. The choice should be made together with the cabinet layout and cable-management plan.
| Mounting format | Rack space consumed | Primary benefit | Potential constraint |
|---|---|---|---|
| 0U vertical | 0U front rack position | Preserves horizontal rack space | Requires cabinet compatibility and side or rear clearance |
| 1U horizontal | 1U | Fits standard rack mounting positions | Consumes usable rack height |
| 1.5U horizontal | 1.5U | Provides an alternative for outlet density and access | Needs explicit rack-space approval |
Use 0U installation when preserving server positions and improving vertical cable organization are priorities. Use horizontal mounting when the cabinet layout, service procedure, or equipment arrangement makes a front or rear rack position more accessible. Confirm mounting brackets, reversibility, cable exit direction, and the clearance required for plugs before the purchase order is released.
4. Decide between basic and intelligent monitoring
A basic PDU is appropriate when the main requirement is stable distribution and outlet compatibility. This approach can reduce configuration complexity in locations that have established upstream monitoring and do not need outlet-level visibility.
An intelligent PDU is appropriate when operators need remote measurement, alarms, or integration with a data center management system. Intelligent features may include total or circuit-level metering, outlet-level measurement, remote switching, event logs, and environmental sensors. SNMP is commonly used to connect intelligent units with monitoring platforms, but the integrator should confirm the supported protocol, authentication method, network interface, firmware process, and management-system compatibility.
Outlet-level metering is most valuable when the operations team needs to identify the consumption of individual devices or circuits. Environmental sensors are useful when temperature and humidity trends must be associated with a particular cabinet. Remote switching can be powerful, but it should be governed by access control and a documented change process to reduce accidental shutdown risk.
Monitoring selection checklist
- Define whether total, circuit, or outlet-level measurement is required.
- Specify measurement accuracy requirements in the procurement document.
- List the management protocols and network-security controls required by the client.
- Confirm alarm thresholds, notification methods, and event retention.
- Identify sensor types, sensor quantity, cable length, and mounting locations.
- Test integration with the target monitoring platform before volume deployment.
5. Specify regional compatibility and protection features
Regional plug and socket requirements must be confirmed before production because the input connector, cable, outlet configuration, approvals, and labeling may vary by country or project site. A multi-country rollout should use a controlled configuration matrix rather than assuming that one input cable will fit every location.
Surge protection may be useful in office and cabinet applications where the project calls for additional protection against voltage disturbances. It should not be treated as a replacement for the facility’s grounding, upstream protection, UPS design, or electrical coordination. Specify whether protection is required, how its status is indicated, and what replacement or service procedure applies.

Certification requirements belong in the initial design brief. Ask the supplier to identify the applicable product and installation standards, provide declaration or test documentation where required, and confirm that the exact configured model—not merely a similar family model—matches the project requirements.
6. Convert the specification into a multi-rack procurement schedule
A procurement schedule should separate common platform requirements from rack-specific options. This method enables standardization without forcing every cabinet to use the same outlet mix or monitoring level.
| Specification block | Required entries | Example configuration count | Approval owner |
|---|---|---|---|
| Electrical input | Voltage, phase, input plug, cable length | 1 approved input configuration per site | Electrical engineer |
| Outlet arrangement | C13 quantity, C19 quantity, grouping, labeling | 1 or more rack profiles | Systems integrator |
| Mechanical design | 0U, 1U, or 1.5U; bracket and cable exit | 1 approved cabinet fit | Rack design team |
| Monitoring | Basic, metered, switched, sensors, protocol | 1 profile per operational tier | Facilities and operations |
| Quality and delivery | Inspection stages, packaging, documents, logistics | 3 quality-control stages | Procurement and quality |
Use a formal design-review process before mass production. The practical sequence is requirements confirmation, electrical and mechanical design, sample approval, functional and safety testing, and then production release. A three-stage quality process covering incoming materials, in-process checks, and pre-shipment inspection can help reduce batch defects, provided the inspection plan is documented and evidence is retained.
7. A field scenario: standardizing mixed-density racks
A mixed-density deployment benefits from a common PDU enclosure platform with different outlet and monitoring profiles. For example, standard server racks may use a C13-dominant configuration, while compute racks may use a higher proportion of C19 outlets. Both profiles can retain the same mounting approach, labeling convention, network-management method, and documentation structure.
The integrator should first validate the equipment schedule, then install a representative sample rack and test cable reach, plug clearance, breaker behavior, monitoring alarms, and cabinet-door closure. This practical test often reveals issues that a spreadsheet cannot show, including blocked outlets, excessive bend radius, inaccessible reset controls, or inadequate sensor placement.
After acceptance, freeze the approved bill of materials by rack profile. Record the exact input plug, outlet arrangement, firmware version, accessories, labels, test documents, and replacement procedure. This creates a repeatable deployment package for later racks and simplifies maintenance across the facility.
Frequently asked questions
1. What is the difference between a C13 and a C19 outlet?
C13 and C19 are different IEC connector formats used for data-center equipment. C13 connections are common for many servers and network devices, while C19 is generally selected for compatible higher-power equipment. Always verify the equipment inlet and cable before ordering.
2. Should every rack use the same outlet ratio?
No. Standardizing the enclosure, mounting, labeling, and management interface is useful, but the C13/C19 ratio should follow the equipment schedule and rack density. Different rack profiles are often more efficient than one universal configuration.
3. Is a 0U PDU better than a 1U PDU?
Neither is universally better. A 0U vertical design preserves horizontal rack space, while a 1U or 1.5U horizontal design may fit a cabinet layout or service process more naturally. Confirm clearance, brackets, cable routing, and rack-space priorities.
4. When should a system integrator specify an intelligent PDU?
Specify an intelligent unit when remote monitoring, metering, alarms, outlet-level diagnostics, environmental sensing, or management-system integration is required. A basic unit may be sufficient when upstream systems already provide the needed visibility.
5. Does outlet-level metering measure the complete rack load?
Outlet-level metering provides visibility for individual connected outlets or devices, depending on the model. It should be compared with total and circuit-level readings during commissioning to confirm the monitoring architecture.
6. What information is needed for a PDU quotation?
Provide the site region, input voltage, phase, input plug, cable length, mounting format, outlet quantities, outlet types, monitoring level, sensor requirements, protection features, certifications, quantity by rack profile, and delivery documentation.
7. How can buyers reduce deployment risk?
Approve a representative sample, test it in the target cabinet, verify electrical and management integration, freeze the bill of materials, and require incoming, in-process, and pre-shipment quality checks. This is more reliable than approving only a catalog image or a nominal outlet count.
Supplier support and next steps
Newsunn PDU supports project-oriented selection for data centers, server rooms, communications sites, industrial applications, and international procurement. Available approaches can include basic or intelligent distribution, 0U or horizontal mounting, C13/C19 configurations, sensors, accessories, OEM, ODM, and private-label programs. For a multi-rack project, prepare the rack load schedule and regional requirements first, then request a configuration review, sample plan, test documentation, and delivery schedule before production approval.
Newsunn
Post time: Oct-14-2026

