Common RFQ Mistakes That Delay Power Supply Programs

When your program timeline depends on a compliant, custom power supply, an incomplete or misdirected RFQ can cost you months. Or derail qualification entirely.

We’ve reviewed hundreds of RFQs across military, medical, space, and industrial programs. The most significant delays don’t come from technical complexity. They come from missing information that forces multiple clarification cycles, prevents accurate NRE scoping, or reveals compliance gaps too late in the development process.

An effective RFQ does more than request a quote. It transfers enough program context to enable realistic scheduling, accurate cost estimation, and early identification of qualification risks. When critical details are omitted or assumptions go unstated, both parties lose time.

The Core Problem: Information Gaps That Compound

Most RFQ mistakes fall into predictable patterns. Engineering teams assume certain details are obvious or will be resolved later. Procurement teams focus on price comparison without providing the technical depth needed for custom development. The result is the same: back-and-forth clarifications, scope creep during development, and schedule compression when compliance requirements emerge late.

The hidden cost isn’t just time. It’s the risk transfer that never happens. Without clear compliance requirements, environmental constraints, and qualification ownership defined upfront, you’re building uncertainty into your program. And your supplier can’t price or schedule for risks they don’t know exist.

Common RFQ Mistakes by Category

1. Compliance Requirements Listed Without Context

The Mistake: “Must meet MIL-STD-461” or “IEC 60601-1 required” with no additional detail.

Why It Delays Programs: Standards have classes, levels, test configurations, and interpretations that fundamentally change design approach, cost, and schedule. MIL-STD-461 alone has different requirements for Army, Navy, and Air Force platforms. IEC 60601-1 requires knowing MOPP/MOOP classification, applied part types, and whether you need operator or patient protection.

What’s Missing:

Which specific classes or limits apply (e.g., MIL-STD-461 CS116 for Navy, RE102 limits for airborne)
Who owns qualification testing (OEM or supplier)
Whether compliance must be demonstrated on the PSU alone or integrated in your system
Existing test reports you can leverage or whether full testing is required

What to Include Instead: Specify the exact standards revision, applicable test methods, required limits or classes, and who performs/witnesses testing. If your platform is airborne Navy, state that. Don’t make your supplier guess which subset of 461 applies.

2. Environmental Extremes Described Generically

The Mistake: “Ruggedized” or “harsh environment” or “wide temperature range” without quantified limits.

Why It Delays Programs: Component selection, thermal design, and qualification testing all depend on specific numbers. A ground-based industrial system operating 0°C to 50°C is fundamentally different from a UAV operating -40°C to 85°C at 50,000 feet with rapid thermal cycling.

What’s Missing:

Operating and storage temperature ranges (with altitude derating if applicable)
Shock and vibration profiles (MIL-STD-810 methods, or specific g-levels and frequencies)
Humidity, salt fog, or contamination exposure
Thermal cycling rates and dwell times
Altitude operating limits

What to Include Instead: Provide the actual environmental test plan or reference the platform’s qualification specification. If you’re flying at 40,000 feet, your supplier needs to derate components accordingly. This affects cost and feasibility from day one.

3. Electrical Specifications Without Load Context

The Mistake: Output voltage and current listed without load profile, transient behavior, or sequencing requirements.

Why It Delays Programs: Static specs don’t reveal the real design challenge. A 500W output that powers a resistive heater is trivial. A 500W output that powers a pulsed laser with 10:1 peak-to-average ratio and 100µs edge times requires completely different architecture, output capacitance, and control topology.

What’s Missing:

Load type (resistive, motor, capacitive, pulsed, regenerative)
Transient step response requirements (load steps, edge rates, acceptable voltage deviation)
Inrush current limits or soft-start requirements
Output sequencing or tracking between rails
Hold-up time during input interruptions
Ripple and noise limits (peak-to-peak or RMS, bandwidth specified)

What to Include Instead: Describe what the power supply is actually powering. If your load pulses, provide duty cycle, repetition rate, and peak current. If you need 20ms hold-up, state it. If rails must sequence with 5ms separation, specify it upfront, not during design review three months later.

4. Mechanical Integration Treated as an Afterthought

The Mistake: “We’ll provide mechanical details later” or envelope dimensions given without mounting, cooling, or connector constraints.

Why It Delays Programs: Mechanical design and electrical design happen in parallel. Discovering late that your 2U chassis can’t accommodate the required heatsink, or that MIL-DTL-38999 connectors won’t fit your backplane, forces redesign that cascades through the entire schedule.

What’s Missing:

Mounting orientation and available fastener locations
Cooling airflow direction, velocity, and inlet temperature (or conduction path if convection-cooled)
Connector type, pinout, and accessibility constraints
Shock/vibration mounting requirements (isolation needed, or hard-mounted)
EMI shielding or grounding integration with your enclosure
Cable retention, strain relief, or serviceability requirements

What to Include Instead: Provide a mechanical interface drawing or at minimum an envelope with keep-out zones, airflow paths, and mounting points. If you’re integrating into an existing chassis, share that context. Your supplier can often adapt semi-custom platforms instead of starting from scratch.

5. Lifecycle and Production Volume Ambiguity

The Mistake: “Initial order 10 units, potential for more” with no program timeline or production forecast.

Why It Delays Programs: Suppliers make fundamentally different design decisions for a 10-unit R&D program versus a 500-unit production run. Component selection, tooling investment, and NRE recovery all depend on lifecycle visibility. If you’re planning multi-year production but only communicate prototype quantity, you may get a design optimized for low-volume that doesn’t scale.

What’s Missing:

Program phase (prototype, qualification, LRIP, full-rate production)
Expected annual volume and program duration
Production ramp schedule
Obsolescence management expectations (5-year availability, 10-year, 15-year?)
Configuration control and PCN requirements

What to Include Instead: Be transparent about program scope. If this is a 3-unit prototype for a program that may run 300 units/year for 10 years, say so. If it’s a one-time 50-unit build with no future orders, that’s equally valuable information. This allows your supplier to make the right trade-offs on tooling, component longevity, and design for manufacturability.

6. Qualification and Testing Ownership Undefined

The Mistake: No mention of who performs compliance testing, who owns the qualification documentation, or how test failures are resolved.

Why It Delays Programs: Qualification is often the longest-lead and highest-risk part of custom power development. If it’s unclear whether the supplier must deliver a qualified unit or simply a design that the OEM will qualify, the NRE estimate, schedule, and risk allocation are all wrong.

What’s Missing:

Who performs EMI, safety, environmental, and performance testing
Who owns and maintains qualification documentation (test reports, design history files, risk analysis)
Whether supplier must achieve compliance or OEM will integrate and test in final system
How non-conformances or test failures are addressed (rework, redesign, cost/schedule responsibility)
Whether witnessing or third-party testing is required

What to Include Instead: Explicitly state qualification ownership. If you expect the supplier to deliver a MIL-STD-461-tested unit with full test reports, budget and schedule for that. If you’re planning to integrate and test in your system, clarify that the supplier’s responsibility ends at interface compliance, not system-level qualification.

7. Schedule Expectations Disconnected from Complexity

The Mistake: “Need prototypes in 8 weeks” for a custom, standards-compliant, environmentally qualified design.

Why It Delays Programs: Custom power development isn’t catalog selection. A semi-custom design adapting an existing platform may deliver in 10-12 weeks. A full-custom design with MIL-STD-461 qualification, thermal vacuum testing, and DO-160 compliance may require 6-9 months. Unrealistic schedule demands force either corner-cutting or eventual program delays when reality surfaces.

What’s Missing:

Recognition of design, simulation, prototype, test, and qualification phases
Acknowledgment of long-lead components (magnetics, high-reliability capacitors, MIL-spec parts)
Buffer for test failures and design iteration
Coordination dependencies (your mechanical drawings, test fixture availability, witness test scheduling)

What to Include Instead: Ask your supplier for a realistic schedule based on the full scope: design, prototype, qualification testing, and documentation. If you have a hard program deadline, state it and ask what scope or approach adjustments would meet it. A semi-custom solution might hit your timeline where a full-custom won’t.

Industry-Specific RFQ Pitfalls

Military Programs

Unique Mistakes:

Platform type unstated (airborne, shipboard, ground-mobile, shelter-based). Each has different MIL-STD-461 and MIL-STD-810 requirements
Altitude operating range omitted, forcing conservative (expensive) derating
DFARS or domestic content requirements not mentioned until after design selection
Security clearance or ITAR access requirements unclear
Government ownership of data rights or technical data package (TDP) expectations undefined

What to Add: Specify platform integration environment, applicable military standards with platform-specific tailoring, any DFARS/ITAR/domestic source requirements, and data rights expectations.

Medical Programs

Unique Mistakes:

MOPP/MOOP classification not provided. This fundamentally changes isolation, creepage, and clearance requirements
Applied part type (BF, CF, unspecified) unstated
Whether power supply must be part of your DHF (Design History File) unclear
Leakage current limits assumed rather than specified to system-level requirements
Risk management documentation ownership undefined (ISO 14971 responsibility)

What to Add: Specify IEC 60601-1 edition, MOPP/MOOP class, applied part type, leakage current limits, and whether supplier must contribute to DHF and risk management file. If you’re planning FDA submission, clarify supplier’s documentation role.

Space Programs

Unique Mistakes:

Radiation environment not quantified (total ionizing dose, SEE susceptibility)
Thermal vacuum profile omitted (operating pressure, thermal cycling, bakeout requirements)
Launch vibration levels and random vibe profiles not provided
Mission duration unstated. A 5-year mission changes parts selection versus 15-year
Derating requirements or parts selection guidance (NEPP, high-reliability screening) undefined

What to Add: Provide radiation environment (TID, SEE requirements), thermal-vac profile, launch vibration spectrum, mission duration, and any parts selection constraints (e.g., NASA EEE-INST-002 compliance, NEPP preferred parts, radiation lot testing).

Industrial Programs (Robotics, CNC, Laser, Additive Manufacturing)

Unique Mistakes:

Continuous operation duty cycle assumed rather than specified (24/7/365 vs. intermittent use)
Power factor correction (PFC) requirements for facility compliance not mentioned
Regenerative load conditions (servo drives, motors with regen) omitted
EMC requirements for CE marking or industrial standards (EN 55011, EN 61000-6-2) unclear
Production scaling timeline vague, which impacts tooling investment and cost reduction path

What to Add: Specify operating duty cycle, input power quality or PFC needs, whether load is regenerative or motor-driven, applicable EMC standards for your target markets, and production scaling timeline. If you’re designing for CE mark, state that upfront.

How to Build a Better RFQ

Before You Send the RFQ

Gather This Information:

Your platform/system context: What is this power supply going into? What does it power?
Compliance framework: Which standards apply, and who qualifies to them?
Environmental exposure: Actual temperature, shock, vibration, altitude, humidity data
Electrical load behavior: Static and dynamic requirements, transient response, sequencing
Mechanical constraints: Envelope, cooling, connectors, mounting
Lifecycle plan: Prototype quantity, production forecast, program duration
Schedule reality: What’s your actual program timeline, and what’s driving it?

Structure the RFQ in Sections

Section 1: Program Overview

Application and end-use environment
Platform type (if military/aerospace) or system type (if industrial/medical)
Program phase and production forecast
Key schedule drivers

Section 2: Electrical Requirements

Input range and transient tolerance
Output voltages, currents, regulation, ripple
Load type and transient behavior
Efficiency or thermal constraints
Any special features (power-good, remote sense, current sharing)

Section 3: Environmental Requirements

Operating and storage temperature
Shock and vibration (profile or standard reference)
Altitude, humidity, contamination exposure
Cooling method and available airflow or conduction path

Section 4: Compliance and Standards

Applicable standards with revision and specific classes/levels
Testing and qualification ownership
Documentation and certification requirements
Agency approvals needed (UL, CE, DFARS, FDA, etc.)

Section 5: Mechanical and Integration

Envelope dimensions and keep-out zones
Mounting and connector requirements
Cooling integration
EMI shielding or grounding approach

Section 6: Lifecycle and Support

Production volume and timeline
Obsolescence management expectations
Configuration control and PCN requirements
Service, repair, or sparing strategy

Section 7: Commercial Terms

NRE and unit cost breakdown requested
Payment terms and milestones
Data rights and IP ownership
Delivery and acceptance criteria

RFQ Checklist: Don’t Send Until You Can Check These Boxes

Technical Completeness

Input voltage range and transient tolerance specified
Output voltages, currents, and regulation limits provided
Load type and transient behavior described (or load profile attached)
Ripple/noise limits specified with measurement bandwidth
Operating and storage temperature ranges defined
Shock and vibration requirements quantified (or standard referenced)
Altitude operating range stated (if above sea level)
Mechanical envelope and mounting constraints provided
Cooling method and available thermal path described
Connector type and pinout specified (or interface drawing attached)

Compliance and Standards

Applicable standards listed with revision and specific test classes
Qualification testing ownership defined (OEM vs. supplier)
Documentation requirements specified (test reports, certifications, DHF contribution)
Agency approvals identified (UL, CE, FDA, DFARS, ITAR)
EMI/EMC requirements clarified (conducted/radiated limits, test setup)

Program and Lifecycle

Program phase identified (prototype, qualification, LRIP, production)
Initial order quantity and production forecast provided
Program duration or lifecycle length stated
Schedule expectations and key milestones outlined
Obsolescence management and PCN expectations defined
Configuration control requirements stated

Risk and Ownership

Qualification ownership and test responsibility assigned
Data rights and IP ownership clarified
Non-conformance resolution process outlined
Acceptance criteria and inspection requirements defined
Warranty and long-term support expectations stated

Industry-Specific (Check if applicable)

Military:

Platform type specified (airborne, naval, ground, shelter)
Applicable MIL-STDs tailored to platform (461, 810, etc.)
DFARS, ITAR, or domestic content requirements stated
Security clearance or facility access requirements defined
Data rights (government purpose, limited, unlimited) clarified

Medical:

IEC 60601-1 edition and MOPP/MOOP classification specified
Applied part type identified (BF, CF, unspecified)
Leakage current limits provided
DHF contribution and risk management (ISO 14971) ownership defined
FDA or notified body submission expectations clarified

Space:

Radiation environment quantified (TID, SEE)
Thermal vacuum profile provided
Launch vibration spectrum attached
Mission duration stated
Parts selection and derating requirements defined (NEPP, high-rel screening)

Industrial:

Operating duty cycle specified (continuous, intermittent, hours/year)
Power factor correction (PFC) requirements stated
Regenerative load conditions identified
EMC standards for target markets defined (CE, FCC, EN 55011)
Production scaling and cost reduction timeline outlined

What Happens When You Get It Right

A complete RFQ achieves three outcomes:

Accurate NRE and unit cost estimates. Your supplier can price for the actual scope, not a guess.
Realistic schedules with fewer surprises. Design, qualification, and delivery timelines reflect real complexity.
Faster trust-building and program kickoff. You’ve demonstrated program maturity and transferred the right level of detail for custom development.

You’ll still have technical discussions during development. But those discussions will focus on optimization and trade-offs, not discovering missing requirements that should have been in the RFQ.

Need Help Scoping Your RFQ?

If you’re not sure which details matter most for your application, or you’d like a second set of eyes on your RFQ before issuing it, we can help. Horizon PSS has supported hundreds of custom power programs across military, medical, space, and industrial applications.

Contact our engineering team to review your requirements, discuss compliance pathways, and ensure your RFQ sets your program up for success from day one.