Identify the affected subassembly and every machine or operation depending on it before revising the plan. Record the inspection outcome, repair or replacement decision and the changed availability. Other assembly work may continue, but the machine should retain a visible dependency so apparent progress does not hide the unresolved component blocking acceptance.
Understand the decision
In a sample build, a purchased hydraulic unit is fitted to a skid before a leak appears during testing. A replacement has a long lead time, and the supplier proposes repair. The team must decide whether to remove the unit, continue unrelated wiring and revise the promised factory test date.
Work through the requirements
- Record the failed unit and affected parent assembly.
- Approve repair, replacement or return with the owner.
- Replan dependent work and customer acceptance milestones.
| Record or decision | Why it matters |
|---|---|
| Inspection exception | Describe failure and affected identity. |
| Disposition decision | Authorize repair or replacement. |
| Dependency update | Show which machine milestone is blocked. |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
A machine can be almost assembled and still be far from acceptable. Keep component failures connected to the delivery promise, and avoid closing the original exception simply because a repair request or replacement order has been created.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Industrial equipment manufacturing in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Odoo 19: manufacturing product configuration ↗Odoo 19: multilevel bills of materials ↗Odoo 19: vendor pricelists ↗Odoo 19: quality control points ↗