Map shot counts to the actual run configuration before using them to estimate output. Record active cavities, setup cycles, rejected parts and counter resets, then reconcile to accepted quantity. A machine integration should preserve raw observations and a reviewed production result so the team can investigate differences without rewriting the original evidence.
Understand the decision
In a sample run, the machine starts with several trial cycles, one cavity is disabled and a counter resets after a power interruption. A simple shots-times-cavities formula would overstate finished output. The operator’s accepted-part count needs a clear relationship to machine observations, including each change during the run.
Work through the requirements
- Identify the run and effective cavity configuration.
- Capture resets and non-production cycles explicitly.
- Reconcile calculated output with accepted and rejected counts.
| Record or decision | Why it matters |
|---|---|
| Machine observation | Preserve counters and timestamps. |
| Run configuration | Record active cavities and changes. |
| Reviewed output | State accepted, rejected and unexplained quantities. |
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
Automating an unqualified counter can make bad quantities arrive faster. Agree the meaning of each observation and test configuration changes before allowing the interface to influence stock availability, production completion or management reports used for operational decisions.
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 Plastics 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: quality control points ↗Odoo 19: lot numbers ↗