When a product shows a red light in the field, the issue is already visible to the customer. The useful work starts earlier: before the unit is released, before service needs an answer, and before engineering has to investigate with limited information. A red light tells you that something needs attention. The question is whether your team knows what to check first.
When the only signal is “error”, every answer takes longer.
Download the one-page PDF (no form) →When a unit fails in the field, what should your team check first?
A field failure in an OEM product is rarely simple to investigate. The unit is part of your product, and your team needs to understand what happened with limited information. The first question is often not only why one unit failed, but how many units may be affected. When the only signal is a general error, the team may start with very little context.
Most of what your team will need is decided before production, not during the first field return. This is the work APQP brings forward: deciding, before series production, what each unit should record, how it links to its lot and version, and who needs which information when a unit comes back. The goal is not more paperwork. The goal is a clearer starting point when something needs attention.
What your team needs connected to each unit
These connections are decided before production — not after the first returned unit.
Five questions to close before series production
Before production, were the likely field issues discussed?
List the main ways the product could fail in use, and define a test or a response for each.
Why it matters Field issues are easier to manage when likely risks were discussed earlier.
Does the test catch the issue, and does the signal give enough context?
Decide before production what the product should record, and which tests confirm it.
Why it matters A general error signal may not give enough context if useful information was not defined earlier.
Was this checked in real conditions before series production?
Validate the design at its real limits, and approve it before volume production.
Why it matters If validation is too close to series, the same issue may appear in more units.
If one unit fails, can you see which other units may be affected?
Define how each unit links to its lot, version, firmware and test result.
Why it matters The first question is often not only “why”, but also “how many units may be affected?”
Is there a response plan before the first field return?
Define what service, quality, engineering and the electronics supplier each need.
Why it matters When electronics are supplied by a partner, the response plan should be clear before production. Four questions show whether that partner really uses APQP.
An electronics design and manufacturing partner for OEMs
KELD is an electronics design and manufacturing partner for OEMs in HVAC, ventilation, motors, pumps and refrigeration. We apply APQP from the early stages of a project, so production and validation risks are found early — when they are still easy to fix. See how we work with OEM teams.
Field-failure readiness starts before production, not at the red light.
APQP helps define, before production, what your team will need to understand the cause.
Not every field issue can be prevented. But the investigation should not start from zero.
Request a Technical Discovery Call →
