Quality Control IoT for Manufacturing
by Viindoo
| Lines of Code | 483 |
| Technical name | viin_iot_quality_mrp |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/17.0/viin_iot_quality_mrp |
| Required Apps | Manufacturing (mrp) Discuss (mail) Inventory (stock) |
| Included Dependencies | Manufacturing Quality Control Stock Quality Control Quality Internet Of Things IoT Manufacturing IoT Quality |
The Scale At The Station Is The Scale On The Check
Quality Control IoT for Manufacturing quietly connects IoT Manufacturing and IoT Quality: a quality check on a work order reads its measurement from the scale nominated at that exact work center - not from wherever the control point happens to point.
One less number for anyone to key in by hand.
Extends viin_iot -
see its documentation.
Extends viin_iot_mrp -
see its documentation.
Extends viin_iot_quality -
see its documentation.
This is a connector, not a stand-alone app. It has something to do only once you already run IoT Manufacturing (lets a work center nominate its own instruments) and IoT Quality (lets a quality check read a measurement from an instrument) side by side. Own both already? Add Quality Control IoT for Manufacturing and it turns itself on - no install step to remember, no setting to switch.
Key Feature
Your Work Order's Own Scale Answers The Check
A quality check that belongs to a work order now reads its measurement from the scale nominated on that work order's own work center, automatically - no dropdown, no decision for the operator running the check. Move the work order to a different station and the very same check follows: the next reading comes from the new station's scale, with nothing to reconfigure. A station that has not nominated a scale of its own simply falls back to the control point's instrument, exactly as before - it never guesses among several instruments that happen to be attached but not nominated. A quality check with no work order at all is not touched by any of this.
How It Works
An IoT administrator nominates a scale on the work center once - the same screen already used to set up that station's other instruments. No IoT permission is needed by anyone after that: the operator running the check never sees a setting, a group, or a choice - only a measurement to take.
From then on, opening a quality check from a work order at that station shows its Instrument field already resolved to the station's own scale.
This is IoT Quality's own quality-check screen, not a screen this module adds. Quality Control IoT for Manufacturing is what resolved the Instrument field shown here to the work order's own work center - control point QCP00019 names no instrument of its own.
If that scale doesn't answer, the check says so plainly - a "No response yet" or "No reading" status the operator can act on - rather than quietly letting the check look measured when it was not. Nothing else about the check changes: same tolerance band, same pass/fail verdict, same screen your quality team already knows.
Need help with Quality Control IoT for Manufacturing?
Pre-Sales & Partnership
Talk to Viindoo before you buy.
viindoo.com/apps/modules/17.0/viin_iot_quality_mrpTechnical Requirement
- Odoo version: 17.0
- Editions: Community, Enterprise
-
Required apps: IoT Manufacturing (
viin_iot_mrp), IoT Quality (viin_iot_quality), Manufacturing Quality (to_quality_mrp) - Installation: Automatic - installs itself once all three required apps above are present. There is no menu entry to install it manually.
- License: OPL-1
Already running IoT Manufacturing and IoT Quality?
Add Quality Control IoT for Manufacturing and the connection turns itself on.
See It On The Live DemoDon't have one of the other two yet?
IoT Manufacturing IoT QualityQuality Control IoT for Manufacturing
Note
Extends viin_iot - see its documentation.
Note
Extends viin_iot_mrp - see its documentation.
Note
Extends viin_iot_quality - see its documentation.
This module has no screen of its own. It adds no menu, no view and no settings page - it only changes ONE thing behind the scenes: when a quality check belongs to a work order, and that check asks an instrument for its measurement, the check now asks the instrument nominated on that work order's OWN work center first, instead of only ever asking the instrument named on the control point behind it. A customer who already has IoT Manufacturing, IoT Quality and Manufacturing Quality Control simply gets this join - there is nothing extra to switch on.
A quality check that is not on a work order is completely unaffected by this module.
Installation
This module installs itself automatically the moment three other apps are all present, so you rarely need to install it by hand:
- Open Apps.
- Search for and install IoT Manufacturing (skip if already installed).
- Search for and install IoT Quality (skip if already installed).
- Search for and install Manufacturing Quality Control (skip if already installed).
- Quality Control IoT for Manufacturing installs itself once all three are active.
It has no menu and no app icon of its own, so it will not show up in Apps unless the Apps-only search filter is removed first. The more direct way to check whether it is active, or to turn it on or off, is the IoT application's own settings:
- Open Settings ‣ IoT.
- Under IoT Integrations, find Quality Control IoT for Manufacturing.
- Switch the toggle on to install the module, or off to remove it.
Configuration
There is nothing to configure inside this module itself - it has no configuration screen of its own. What DOES need setting up lives on its two neighbours, and two different roles are usually involved.
Nominate the instrument on the work center
This is the one-time setup step this module actually depends on. It is done in the Manufacturing application and needs at least the IoT app's User access level:
- Open Manufacturing ‣ Configuration ‣ Work Centers and open the work center where the operator will take the measurement.
- Go to its IoT page and add a registered scale to the IoT Devices field.
- Nominate that scale in the Scale field.
An ordinary quality operator does not need this, or any other IoT access level, to benefit from it - see Usage below.
Naming an instrument on the control point (optional, and not this module's job)
A control point can still name its own measuring instrument, exactly as before this module was installed - that setup step belongs to IoT Quality and needs Administrator access under Quality, not any IoT permission. This module never touches that setting; it only decides which instrument a WORK-ORDER check asks first. See the viin_iot_quality documentation for that step, its permission, and everything else about naming an instrument on a control point.
Usage
A work-order check reads its own work center's instrument
Open a quality check that belongs to a work order and whose type is Measure - for example from Quality ‣ Quality Control ‣ Quality Checks, or from the work order itself - and click Measure. The dialog names the instrument that will supply the reading before anything is pressed, and that instrument is the one nominated on this check's OWN work center - never a dropdown, never a choice for the operator. This is true even when the control point behind the check names no instrument of its own, or names a different one: for a work-order check, the work center's own nomination always wins.
From there, requesting the reading, seeing it fail to arrive, and seeing where a measurement came from all work exactly as IoT Quality alone documents - this module only changed which instrument is asked, nothing about how the reading itself is requested, reported or recorded.
Moving a work order to a different work center
Because the instrument is resolved from the work order's OWN work center, moving a work order to a different work center changes which instrument its checks read from immediately, with no extra setup: the check simply asks whichever work center the work order sits on right now.
When the work center has no instrument nominated
A work center that has not nominated a scale is not treated as an error. The check falls back to the control point's own instrument, exactly as if this module were not installed - it never guesses among several instruments that happen to be attached to the work center but not nominated for the Scale role.
A check that is not on a work order, or not a Measure check
A quality check that is not tied to a work order behaves exactly as IoT Quality alone specifies - this module has nothing to add there. The same is true for a work-order check whose type is Take a Picture rather than Measure: this module only changes where a MEASUREMENT comes from, so a picture check still reads the camera named on its control point.
Troubleshooting
- A work-order check still reads from the control point's instrument, not the work center's.
- The work center has no scale nominated. Open Manufacturing ‣ Configuration ‣ Work Centers, open the work center the check's work order runs on, and nominate a scale on its IoT page.
- I cannot find a settings page for this module.
- There is none - this module adds no screen of its own. Check Settings ‣ IoT ‣ IoT Integrations for its toggle instead, or remove the Apps-only filter under Apps to find it there.
- The check does not name any instrument at all.
- Neither the work order's work center nor the control point behind the check names an instrument. Nominate one on either - the work center for a work-order-wide default, or the control point for everything else - or keep filling the check in by hand, exactly as before this module was installed.
- A Take a Picture check on a work order still reads the control point's camera, not the work center's.
- That is expected. This module only resolves the instrument for a Measure check; a picture check is unaffected and always reads the control point's own camera.
FAQ
- Does this module add a menu, a view or a settings screen of its own?
- No. It adds none of these - it only changes which instrument a work-order measurement check asks.
- Do I need to install this module myself?
- Usually not. It installs itself automatically once IoT Manufacturing, IoT Quality and Manufacturing Quality Control are all present. You can still switch it on or off by hand under Settings ‣ IoT ‣ IoT Integrations.
- Does an operator need any extra permission because this module is installed?
- No. This module changes no access rights at all - an ordinary quality operator with no IoT permission still just takes the measurement, exactly as before.
- Which instrument wins when both the work center and the control point name one?
- For a work-order check, the work center's own nomination always wins. The control point's instrument is used only when the work center has none nominated.
- Does this change anything for a quality check that is not tied to a work order?
- No. A check with no work order is completely unaffected and behaves exactly as IoT Quality alone specifies.
This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software.
The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.