A CRPS power supply specification is a compatibility stack, not proof that any two CRPS-labeled modules are interchangeable. Approval must bind an exact PSU ordering code and hardware/firmware revision to the applicable CRPS design-guide revision, mechanical option, airflow direction, backplane interface, AC input conditions, DC output curves, management behavior, chassis cooling, redundancy state, and compliance evidence.
A matching nominal wattage or exterior envelope closes only part of that stack. If the supplier cannot identify the controlling CRPS document and selected options, or if the chassis owner cannot provide the exact backplane and BMC requirements, the replacement remains unverified even when it inserts, powers on, and reports plausible telemetry.
Quick Answer
Interpret a CRPS data sheet in three layers: what the identified CRPS revision requires, which alternatives that revision permits, and what the supplier implemented in the exact ordered module. Then compare those details with the server’s bay, backplane, BMC, power budget, airflow, and failure policy. Treat missing evidence as open, not as compatible by default. A candidate passes only when document review and production-representative testing show that every interface used by the platform agrees under normal operation, PSU failure, and hot-service conditions.
Start with an Identifiable CRPS Design Guide
Intel and other platform vendors have published design guidance for common redundant power supply architectures used in server platforms. However, CRPS compatibility should not be determined by the “CRPS” label alone. The applicable design specification, revision, mechanical interface, electrical interface, management protocol, backplane requirements, airflow conditions, and platform implementation should be verified for the specific server system.
Controlled document identity matters more than the isolated word “CRPS.” A conformance statement should name the issuer, complete title, document number, revision, date, applicable options, deviations, and exact PSU ordering code. “Designed to CRPS” without those fields cannot show whether the module follows its declared specification, another platform owner’s derivative specification, or only a similar mechanical convention.
A CRPS design guide does not establish that every provision applies to every contemporary CRPS product. Platform owners and suppliers may use later controlled documents, supplemental requirements, licensed material, or their own qualified implementations. If the governing version is not public, obtain a publishable conformance statement from the platform owner or PSU supplier. At minimum, that statement should identify the document and revision, list selected options and deviations, and map the declaration to the exact production configuration.
Do not infer backward compatibility merely because one guide revision is newer. A revision can preserve the broad envelope while changing a drawing note, optional signal, test condition, management requirement, or interpretation. Only a revision-delta review can show whether a change touches an interface used by the server.
CRPS Alignment Can Permit More Than One Incompatible Implementation
Airflow variations illustrate why standards alignment is not the same as interchangeability. A PSU may be configured for different airflow directions, and those directions must be identified by the supplier using unambiguous inlet and outlet faces. The exact module’s airflow must match the chassis requirement rather than an assumed universal “CRPS airflow” direction.
The compatibility-relevant fact is that airflow direction is a controlled configuration attribute. The vendor-selected behavior is which direction the exact ordering code implements. The platform-level requirement is which face must be the inlet in the installed chassis. Two modules may have similar CRPS envelopes, yet one can oppose the server airflow when installed.
This is a compatibility-relevant option, not a cosmetic distinction. Opposing airflow can recirculate exhaust, alter pressure through the PSU bay, increase fan demand, heat the adjacent module, or push the candidate into a documented thermal derating region. The following evidence is needed to close the field:
- the CRPS option or requirement applicable to the claimed implementation;
- a supplier drawing with an airflow arrow and identified handle and connector faces;
- the exact ordering code or configuration record selecting that direction;
- the chassis airflow requirement and bay orientation;
- thermal qualification with all PSUs operating and with one PSU unavailable.
A catalog description such as “front-to-back” is inadequate unless “front” is unambiguous in both the PSU drawing and the server installation. Nor should procurement assume that every relevant option is encoded in a visible suffix. Some manufacturers control airflow, firmware, regional input cord assumptions, or internal revisions through separate configuration records. The supplier must state how the delivered configuration is identified.
Classify Each Requirement Before Comparing Values
A useful CRPS power supply specification separates four authorities. This prevents a common supplier behavior from being misrepresented as a universal requirement and prevents a standards option from being overlooked during substitution.
| Requirement source | Controlling evidence | What it can establish | What it cannot establish alone |
|---|---|---|---|
| CRPS design guide | Identified issuer, document number, revision, clause, table, figure, and selected option | Normative requirement or permitted alternative within its stated scope | Which option an ordered module contains or whether a server accepts it |
| PSU supplier | Exact data sheet, outline drawing, interface definition, derating curves, firmware note, and conformance matrix | How the exact module implements the applicable requirements | Completed-platform compatibility or system certification |
| Platform owner | Chassis drawing, backplane schematic or contact table, qualified-parts record, BMC contract, and failure policy | What the server requires from the PSU | Unstated behavior inside a candidate module |
| Compliance owner | Certificates, reports, conditions of acceptability, regional records, and change assessment | Whether the exact configuration remains within an evaluated compliance scope | Functional interchangeability with the chassis or BMC |
For example, a data sheet may state that a management bus is present. The applicable CRPS clause determines any standards-level obligation; the supplier interface specification defines implemented commands and behavior; the BMC specification defines what the server reads, writes, and interprets. None of those records replaces the others.
Translate the Data Sheet into Interface Questions
Mechanical envelope means datums and tolerances
Compare the PSU and bay drawings from shared datums: handle face, connector face, body surfaces, guide features, insertion stop, latch position, and mating centerline. Overall width, height, and length do not reveal whether the connector reaches full engagement or the latch closes after tolerances accumulate.
Inspect protrusions, keying, grille geometry, label thickness restrictions, handle travel, extraction clearance, and neighboring cable interference. A module that reaches the connector but cannot latch is not mechanically compatible. A module that latches but cannot be removed without disturbing the surviving PSU is not service-compatible.
Sample inspection should define acceptable insertion force, positive retention, connector engagement, removal clearance, and blanking behavior. These are separate from energized hot-swap approval. Hot-swap also depends on contact sequencing, isolation, inrush behavior, backplane design, controls, firmware response, and the platform’s service procedure.
The mating interface requires a position-by-position reconciliation
Connector appearance is weak evidence. Compare every populated, unpopulated, and reserved position between the candidate module and the exact backplane revision. The comparison should cover main output and return paths, protective grounding, standby output, control and status functions, management contacts, presence or identification functions, and any remote-sense implementation.
Current-carrying capability depends on more than nominal output voltage. Verify contact ratings, parallel-path requirements, backplane copper or busbar limits, connector temperature limits, and the conditions under which the PSU rating applies. A higher-rated module does not automatically increase platform capacity if the distribution path has a lower approved limit.
Reserved contacts need an explicit disposition. A position marked reserved in one specification is not available for undocumented use, and an optional function assigned by one implementation may conflict with a backplane that expects the position to remain open. Engagement order must come from controlled drawings and tolerance analysis, not photographs.
Input range is not an output guarantee
Record the accepted AC input range, frequency, input current, inrush behavior, power factor information, and the output available at each deployed input condition. A module may accept a low-line input without delivering its headline high-line output. The relevant value is the supplier’s input-dependent output curve for the exact part, combined with any thermal or altitude derating.
Rated DC output is capacity under stated conditions; it is not actual server consumption. Input real power can be estimated only after obtaining efficiency at the applicable input and load:
Approximate AC real power = DC load ÷ efficiency
In a hypothetical example, a server requiring 1,250 W DC at a verified operating-point efficiency of 94% would draw approximately:
1,250 W ÷ 0.94 ≈ 1,330 W AC
The approximately 80 W difference becomes conversion heat. This calculation does not replace documented input current, power factor, inrush, protective-device coordination, PDU phase loading, or facility loading requirements.
Output specification includes dynamics and protection
Compare main-output and standby-output ratings under their stated conditions, regulation limits, dynamic-response requirements, startup behavior, hold-up expectations where applicable, current sharing, protection thresholds, and recovery behavior. Avoid copying a wattage value into the matrix without its input and temperature conditions.
Sustained capacity and transient response are different tests. An accelerator server can remain below the PSU’s continuous rating yet produce a load step that exposes excessive output-path impedance or insufficient dynamic response. The PSU, connector, backplane, busbar, and local server capacitance form one power system. Spare nameplate wattage does not prove that this system remains inside the platform voltage envelope during a transition.
Management support is a behavioral contract
“PMBus supported” does not establish BMC compatibility. For the exact module firmware, identify required commands, addresses, units, scaling, status-bit meanings, response timing, unsupported-command behavior, write permissions, inventory fields, fault clearing, and behavior during AC loss, PSU failure, or physical removal.
A plausible power reading closes very little. The BMC may use PSU information to change fan speed, declare redundancy loss, apply workload caps, generate service alerts, or reject an unrecognized module. A candidate can deliver stable DC output and still be operationally incompatible.
Mixed-revision operation also needs a documented disposition. If the platform allows different PSU hardware or firmware revisions in one chassis, specify the accepted combinations and test them. If mixing is prohibited, receiving and service controls must prevent installation of an otherwise similar spare.
Worked Revision-Delta Review
The following is a hypothetical document-control example, not a claim about a particular CRPS revision or commercial PSU. It shows how to analyze a proposed change without assuming that “newer” means interchangeable.
| Interface | Approved baseline | Candidate revision | Engineering disposition |
|---|---|---|---|
| Envelope and connector datum | Supplier drawing D-14 Rev C | Drawing D-14 Rev D states no dimensional change | Document review passes; confirm production sample against the bay |
| Airflow | Connector-face inlet, recorded configuration AF-A | Same family offered in AF-A and opposite AF-B | Only AF-A remains eligible; receiving must identify the delivered option |
| Management firmware | Firmware 5.4 qualified with BMC 8.6.3 | Firmware 5.7 changes one status-bit interpretation | Open until BMC behavior and alert logic are retested |
| Input-dependent output | Required load supported at site input and maximum qualified inlet temperature | Derating curve revised | Recalculate survivor capacity from the new curve before testing |
| Certificate scope | Exact baseline code appears in the compliance file | New suffix not explicitly listed | Compliance owner must confirm family coverage or obtain updated evidence |
Only the unchanged drawing claim is initially close to approval, and even that requires sample confirmation. The airflow option is conditionally acceptable, the firmware change is an interoperability question, the derating change can alter redundancy, and certificate coverage belongs to the compliance owner. One unchanged field cannot approve the complete stack.
A Completed Compatibility Matrix Shows What “Approved” Means
This second hypothetical example demonstrates a controlled release record. The identifiers are illustrative and do not represent commercial products.
| Controlled item | Qualified value | Candidate evidence | Disposition |
|---|---|---|---|
| PSU candidate | Candidate C-17, hardware Rev B, firmware 5.7 | Supplier configuration declaration covers this exact combination | Pass for identity |
| CRPS basis | Platform-required guide revision and airflow option | Clause-mapped supplier conformance matrix supplied; two declared deviations reviewed | Pass only for documented scope |
| Chassis | CH-4 Rev D | PSU and bay drawings reconciled; sample inserts, latches, and extracts with adjacent module installed | Pass |
| Backplane | BP-4 Rev C | All contacts mapped; reserved positions remain open; current path reviewed | Pass |
| BMC | Version 8.6.3 | Required commands, scaling, status response, removal event, and fault alerts tested | Pass for this BMC version |
| Airflow | Connector-face inlet configuration AF-A | Supplier drawing and delivered-unit inspection agree | Pass; AF-B explicitly prohibited |
| Site input | Defined facility voltage and frequency envelope | Input and output curves show required capacity throughout the deployment range | Pass within recorded conditions |
| One-PSU survivor state | Full required server load after one module fails | Derated capacity calculation passes; representative failure test remains scheduled | Open until test completion |
| Compliance | Exact production suffix and intended region | Safety evidence received; completed-system change assessment not signed | Open |
This candidate is not yet released because two mandatory rows remain open. Document completeness is not measured by how many rows pass; it is determined by whether every release-critical requirement has an acceptable disposition.
Redundancy Must Be Calculated from the Surviving Module
Two installed PSUs do not automatically provide twice the usable redundant capacity. In a 1+1 design, one surviving module must support the required post-failure load at the deployed input, inlet temperature, altitude, airflow, and cooling state. Transition behavior and transient margin are additional requirements.
Assume a hypothetical platform has two nominally 1,600 W modules and a sustained DC demand of 1,250 W. Under normal active-active sharing, each module carries approximately:
1,250 W ÷ 2 = 625 W
Now assume the supplier’s verified curves limit one surviving module to 1,100 W under the platform’s worst approved input and thermal condition. After failure, the survivor must carry all 1,250 W:
1,250 W required − 1,100 W available = 150 W shortfall
The installation does not meet the stated 1+1 requirement, despite having 3,200 W of installed nameplate capacity. A platform power cap could change the answer only if its activation, timing, permitted workload, BMC dependency, and failure behavior are documented and qualified.
Active-standby and cold-redundant policies require further evidence: wake-up timing, trigger conditions, inactive-module readiness, voltage behavior during transition, and response to management or communication failures. These characteristics cannot be inferred from the CRPS designation.
Request Documents from the Party That Owns Them
The PSU vendor should provide the exact module data sheet, mechanical drawing, connector and signal definition, input/output and derating curves, airflow identification, management-interface specification, hardware and firmware control method, protection behavior, and clause-mapped CRPS conformance declaration. If an option is not encoded in the part number, the vendor should explain how production and receiving records identify it.
The chassis or platform owner should provide the bay drawing, backplane revision and interface requirements, approved input and output limits, thermal boundary conditions, qualified PSU combinations, BMC requirements, redundancy policy, hot-swap procedure, and acceptance test plan.
The organization responsible for platform integration should own the compatibility matrix, revision-delta review, sample testing, failure-state validation, mixed-module policy, receiving controls, and release record.
The compliance owner should determine whether safety, efficiency-program, environmental, electromagnetic-compatibility, and regional evidence covers the exact configuration. Component recognition does not automatically certify the completed server, and CRPS alignment does not establish regulatory approval.
Conditional Approval Rule for a CRPS Power Supply Specification
A CRPS power supply specification supports interchangeability only when the applicable guide revision and options are identified, the exact delivered module implements those options, and the chassis, backplane, BMC, electrical, thermal, redundancy, service, and compliance records all agree. Bind approval to the relevant PSU hardware, firmware, airflow configuration, chassis, backplane, BMC, site conditions, and certificate scope.
If a field lacks controlled evidence, leave it open. If the candidate conflicts with the connector map, airflow requirement, management contract, input-dependent output, or derated survivor capacity, reject that configuration regardless of physical fit or CRPS labeling. The correct purchasing decision is therefore conditional: buy the exact qualified compatibility stack, not merely a CRPS form-factor description.
