How to Qualify an OBC Supplier for Automotive Production

Qualify an OBC supplier by auditing both the product engineering evidence and the factory’s ability to repeat that product at production volume. Require documented ownership, risk controls, validation results, traceability, capacity proof and contractual change management before approving a launch.

What should the RFQ require before technical evaluation?

Start with a controlled RFQ that defines the vehicle programme, operating envelope and evidence required at each gate. Specify input-voltage range, charging-power range, output architecture, cooling concept, communication interfaces, diagnostic expectations, environmental conditions, packaging constraints and service requirements without forcing a supplier to quote against assumptions it cannot verify. Ask each bidder to identify exclusions, open requirements and dependencies on the vehicle electrical architecture.

The RFQ should request a compliance matrix, preliminary block diagram, development schedule, sample plan, validation plan and manufacturing-location information. Require the supplier to state which elements are standard, which are adapted and which require new development. This distinction reveals whether the proposed schedule depends on unproven hardware, software, magnetics, power semiconductors or thermal interfaces.

Do not award on a single efficiency or power figure. Compare the complete operating map, derating behaviour, protection response, acoustic constraints, diagnostic coverage, cooling requirements and service strategy. Ask for representative test evidence and define which results must be repeated on programme-intent hardware. Exact limits should remain in the vehicle specification and controlled datasheet.

Who owns the design and the technical decisions?

Establish design ownership before commercial negotiations. The supplier should identify the legal entity responsible for system architecture, hardware, embedded software, mechanical design, magnetics, thermal design, calibration, cybersecurity interfaces and regulatory compliance. A trading company or assembly site may not control the critical design records, so the RFQ should name every engineering location involved.

Request a responsibility matrix covering requirements, design reviews, failure analysis, verification, validation, release, manufacturing transfer and field issues. The OEM or Tier-1 should retain access to the controlled requirements baseline, revision history, deviation records and test reports needed to maintain the vehicle programme. If intellectual-property restrictions limit access, define an escrow, audit or long-term support arrangement.

For safety-relevant functions, ask how the supplier manages item definition, hazard analysis, safety goals, technical safety requirements and confirmation evidence. ISO 26262 addresses functional-safety management across concept, hardware, software, production, operation and service activities.[1][4][8] Certification language alone is not sufficient; the buyer needs to see the project-specific work products and the allocation of responsibilities.

How can the factory prove process control?

Audit the complete route from incoming material to shipment, not only the final electrical test. Map critical operations such as power-module mounting, soldering or bonding, insulation assembly, torque-controlled fastening, thermal-interface application, sealing, connector installation, programming and end-of-line testing. For each operation, review the work instruction, process parameters, measurement method, reaction plan and records from recent production.

Look for controls that prevent defects rather than merely detecting them. Examples include keyed fixtures, barcode interlocks, automatic parameter capture, component-presence checks, torque verification, programming authorization and test-limit control. Review how operators are qualified and how temporary work instructions are approved. Layered process audits and periodic process reviews are consistent with the control expectations associated with automotive quality systems.[2][5][7]

Ask for PFMEA, control plan, process-flow diagram, measurement-system studies and capability evidence for critical characteristics. The documents must agree with one another and with the released drawing or specification. Where capability is not yet demonstrated, record the gap as a launch action with an owner, due date and containment method rather than treating a planned study as completed evidence.

What traceability is necessary for an OBC?

Traceability should connect the finished OBC to its manufacturing date, line, operator or station records, software and calibration versions, critical component lots, test results and any approved deviation. The required depth depends on the risk and customer contract, but the system should support rapid containment without placing an entire shipment or vehicle fleet on hold unnecessarily.

Verify that serial numbers are created and controlled at the correct point in the process. Check that rejected, reworked and scrapped units cannot re-enter production without authorization. Review sample records for power modules, capacitors, magnetics, connectors, thermal materials and safety-related components. Confirm that subcontracted operations and incoming inspection records are linked to the finished-unit identity.

Traceability is only useful if records are retrievable and protected from uncontrolled editing. Ask the supplier to demonstrate a live or representative record search during the audit. Confirm retention periods, backup arrangements, access permissions and the process for correcting erroneous entries. Include the required electronic data format in the supply agreement.

What validation evidence should release an OBC?

Require a validation plan that covers electrical, thermal, mechanical, environmental, EMC, communication, protection, software and manufacturing robustness. The plan should define sample configuration, test conditions, duration, acceptance criteria, instrumentation, anomaly handling and report approval. Tests on engineering prototypes should be clearly separated from tests on production-intent units built with released processes.

Review tests for abnormal input conditions, load transitions, short-circuit or fault response, insulation performance, thermal cycling, vibration, humidity, corrosion where relevant, connector durability, cooling interruption and repeated charging cycles. The appropriate matrix depends on the vehicle platform, region, duty cycle and applicable regulatory requirements. Ask the supplier to identify which conditions are covered by analysis, which by test and which remain open.

Validation evidence must include failures, not only successful summaries. Examine the original data, failed-unit containment, root-cause analysis, corrective action and regression testing. For software-controlled functions, check version control, requirements traceability, diagnostic behaviour, calibration management and release authorization. Confirm that the production test system uses controlled limits and that test equipment is calibrated.

Can the supplier support the required production volume?

Request a capacity model based on actual equipment, staffing, cycle time, yield, planned maintenance, changeover losses, test bottlenecks and working patterns. Capacity should be shown by process step, because an assembly line may appear adequate while programming, thermal testing, burn-in or final inspection limits output. Ask for assumptions and sensitivity cases rather than accepting one headline monthly figure.

Audit equipment ownership, installation status, preventive-maintenance records, spare-parts strategy and recovery plans for critical stations. Confirm the availability of qualified second sources for constrained materials and the supplier’s ability to manage allocation risk. For components with long lead times, review supplier commitments, approved alternatives and the engineering impact of substitution.

Use a staged ramp: pilot build, process-validation build, controlled launch and sustained production. Define exit criteria for yield, capability, open defects, test coverage, delivery performance and field feedback. A line that meets output during a supervised pilot may still lack the staffing, maintenance discipline or material resilience required for sustained vehicle production.

How should change management and ramp risk be controlled?

Make engineering and process changes subject to written approval before implementation. The agreement should cover component substitutions, software updates, tooling moves, manufacturing-site changes, subcontractor changes, process-parameter changes and test-limit changes. Require advance notification, impact analysis, sample approval and revalidation where the change affects fit, function, reliability, safety, EMC, cybersecurity or traceability.

Review the supplier’s last change records during the audit. Look for evidence that obsolete stock, work instructions, drawings, firmware and test programs were controlled together. Confirm how field units, service parts and inventory in transit are identified when a change is introduced. Customer-specific requirements may add obligations beyond the general quality system, so the contract must list the applicable OEM or Tier-1 requirements explicitly.[2][3][7]

Ramp risk should be managed with a live launch dashboard. Include open technical issues, special characteristics, supplier shortages, equipment readiness, operator training, first-pass yield, rework, warranty exposure and emergency-response contacts. Define escalation thresholds and containment authority before the first production shipment.

Which supplier evidence should determine the sourcing decision?

Use a weighted decision matrix agreed before bids are reviewed. Give separate scores to design maturity, validation quality, process control, traceability, supply-chain resilience, capacity, commercial risk and responsiveness. Mark safety, regulatory, traceability and ownership failures as disqualifying rather than allowing a strong commercial score to offset them.

The final award should depend on objective gate evidence, not the presentation quality of the audit. Require signed action plans for every gap, with containment, owner, due date and verification method. Before SOP, repeat the audit against the production-intent line and confirm that the released product, process, software, test system and supply chain are the same configuration that was qualified.