[ADD] Quality: Control points doc
closes odoo/documentation#7635
X-original-commit: 1bf87a0db9
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
This commit is contained in:
parent
209864139d
commit
f9c0be63ee
@ -1,89 +1,132 @@
|
||||
====================
|
||||
Add quality controls
|
||||
====================
|
||||
======================
|
||||
Quality control points
|
||||
======================
|
||||
|
||||
.. _quality/quality_management/quality-control-points:
|
||||
.. |MO| replace:: :abbr:`MO (Manufacturing Order)`
|
||||
.. |MOs| replace:: :abbr:`MOs (Manufacturing Orders)`
|
||||
.. |QCP| replace:: :abbr:`QCP (Quality Control Point)`
|
||||
.. |QCPs| replace:: :abbr:`QCPs (Quality Control Points)`
|
||||
|
||||
Use Odoo *Quality* to control the quality of products before they are registered into stock, during
|
||||
picking operations, and when leaving the warehouse for a delivery order. By creating *quality
|
||||
control points*, manufacturers can set up quality checks that automatically trigger at specific
|
||||
points during production.
|
||||
In Odoo, *quality control points* (QCPs), are used to automatically create :doc:`quality checks
|
||||
<quality_checks>` at predetermined intervals. |QCPs| can be configured to create quality checks for
|
||||
specific operations (manufacturing, delivery, etc.), as well as specific products within those
|
||||
operations.
|
||||
|
||||
Using |QCPs| allows quality teams to ensure products are being regularly inspected for defects and
|
||||
other issues.
|
||||
|
||||
Configure quality control points
|
||||
================================
|
||||
|
||||
To create a new quality control point, go to :menuselection:`Quality Control --> Control Points -->
|
||||
Create`. Then, fill in the following form fields, accordingly:
|
||||
To create a new |QCP|, navigate to :menuselection:`Quality --> Quality Control --> Control Points`,
|
||||
and then click :guilabel:`New`.
|
||||
|
||||
- :guilabel:`Title`: give the quality control point a simple, but informative title so production
|
||||
floor and quality check teams can understand it easily
|
||||
- :guilabel:`Products`: indicate which product(s) should pass through the specific quality control
|
||||
point
|
||||
- :guilabel:`Operations`: determine which operations team(s) should perform the quality control
|
||||
check (e.g., `Manufacturing`, `Receipts`, `Delivery Orders`, etc.)
|
||||
- :guilabel:`Work Order Operation`: for manufacturing operations, use the drop-down menu to
|
||||
indicate which type of work order the quality control point applies to: :guilabel:`Manual
|
||||
Assembly`, :guilabel:`Packing`, :guilabel:`Assembly`, :guilabel:`Testing` or :guilabel:`Long time
|
||||
assembly`
|
||||
- :guilabel:`Company`: add the company that will implement the quality control point. Usually this
|
||||
will be the company that owns the Odoo database. However, a multi-company or vendor profile can
|
||||
be selected, as well, for cases where there are multiple manufacturing or engineering locations
|
||||
- :guilabel:`Control Type`: using the drop-down menu, choose from :guilabel:`All Operations`,
|
||||
:guilabel:`Randomly` or :guilabel:`Periodically` to determine how often the control point should
|
||||
executed
|
||||
- :guilabel:`Type`: using the drop-down menu, choose the control point type:
|
||||
:guilabel:`Instructions`, :guilabel:`Take a Picture`, :guilabel:`Pass - Fail`, or
|
||||
:guilabel:`Measure`
|
||||
- :guilabel:`Team`: decide which quality team should receive the results of the quality control
|
||||
point check
|
||||
- :guilabel:`Responsible`: add a point person to manage the status and evolution of the quality
|
||||
control point over time
|
||||
Begin filling out the new |QCP| by entering a unique :guilabel:`Title` that makes the |QCP| easily
|
||||
identifiable.
|
||||
|
||||
The tabs at the bottom of the form can be used to provide additional information to quality teams:
|
||||
In the :guilabel:`Products` field, select one or more products the |QCP| should apply to. If the
|
||||
|QCP| should apply to an entire product category, select it in the :guilabel:`Product Categories`
|
||||
field.
|
||||
|
||||
- :guilabel:`Instructions`: describe the quality check to be performed
|
||||
- :guilabel:`Message If Failure`: detail what should be done if the check fails
|
||||
- :guilabel:`Notes`: use to include any additional information
|
||||
In the :guilabel:`Operations` field, select the operation(s) that should trigger the |QCP|. For
|
||||
example, selecting the :guilabel:`Manufacturing` option in the :guilabel:`Operations` field causes a
|
||||
quality check to be created for new manufacturing orders (MOs).
|
||||
|
||||
.. image:: quality_control_points/quality-control-point-form.png
|
||||
.. note::
|
||||
When creating a new |QCP|, at least one operation must be listed in the :guilabel:`Operations`
|
||||
field. However, the :guilabel:`Products` and :guilabel:`Product Categories` fields can be left
|
||||
blank. If they are left blank, the |QCP| generates quality checks for every instance of the
|
||||
specified operation(s).
|
||||
|
||||
If the :guilabel:`Manufacturing` operation is selected in the :guilabel:`Operations` field, a new
|
||||
field appears below it, titled :guilabel:`Work Order Operation`. From this field, select a specific
|
||||
work order to generate quality checks for that operation, rather than the manufacturing operation in
|
||||
general.
|
||||
|
||||
For example, a |QCP| could be configured to create quality checks for the `Assembly` work order of
|
||||
the `Coffee Table` product. Then, if a new |MO| is confirmed for a `Coffee Table`, the |QCP| creates
|
||||
a quality check specifically for the `Assembly` operation.
|
||||
|
||||
The :guilabel:`Control Per` field is set to one of three options that determine *when* a new quality
|
||||
check is created:
|
||||
|
||||
- :guilabel:`Operation`: one check is requested for the specified operation, as a whole.
|
||||
- :guilabel:`Product`: one check is requested for each *unique* product included in the specified
|
||||
operation. For example, a delivery operation for one table and four chairs would generate two
|
||||
checks, since two *unique* products are included in the operation.
|
||||
- :guilabel:`Quantity`: a check is requested for a certain percentage of items within the specified
|
||||
operation. This percentage is set by enabling the :guilabel:`Partial Transfer Test` checkbox, and
|
||||
then entering a numerical value in the :guilabel:`Percentage` field that appears below. If the
|
||||
checkbox is not enabled, one quality check is created for the full quantity.
|
||||
|
||||
The :guilabel:`Control Frequency` field is set to one of three options that determine *how often* a
|
||||
new quality check is created:
|
||||
|
||||
- :guilabel:`All`: a quality check is requested every time the conditions of the |QCP| are met.
|
||||
- :guilabel:`Randomly`: a quality check is randomly requested for a certain percentage of
|
||||
operations, which can be specified in the :guilabel:`Every #% of Transfers` field that appears
|
||||
below.
|
||||
- :guilabel:`Periodically`: a quality check is requested once every set period of time, which is
|
||||
specified by entering a numerical value in the field below, and choosing either :guilabel:`Days`,
|
||||
:guilabel:`Weeks`, or :guilabel:`Months` as the desired time interval.
|
||||
|
||||
In the :guilabel:`Type` field, specify the type of quality check that should be performed. The
|
||||
method for processing quality checks created by the |QCP| depends upon the type of quality check
|
||||
selected:
|
||||
|
||||
- :guilabel:`Instructions` checks provide specific instructions for how to complete the quality
|
||||
check.
|
||||
- :guilabel:`Take a Picture` checks require a picture of the product be uploaded for later review by
|
||||
the assigned quality team.
|
||||
- :guilabel:`Register Production` checks prompt manufacturing employees to confirm the quantity of
|
||||
the product that was produced during the manufacturing operation.
|
||||
- :guilabel:`Pass - Fail` checks specify a criterion that products must meet for the check to pass.
|
||||
- :guilabel:`Measure` checks prompt employees to record a measurement of the product that must be
|
||||
within a tolerance of a norm value for the check to pass.
|
||||
- :guilabel:`Worksheet` checks provide an interactive worksheet that must be filled out by the
|
||||
employee processing the check.
|
||||
|
||||
.. important::
|
||||
An *Instructions* check is the same as a step on a work order for an MO.
|
||||
|
||||
When a step is added to a work order, Odoo stores it in the Quality app as a |QCP|. It is
|
||||
possible to manually create a |QCP| with the *Instructions* check type, and even assign it to an
|
||||
operation other than manufacturing, like receipts.
|
||||
|
||||
However, when creating a control point specifically for quality control purposes, using a
|
||||
different check type is probably more effective.
|
||||
|
||||
In the :guilabel:`Team` field, specify the quality team that is responsible for managing the |QCP|,
|
||||
and the quality checks it creates. If a specific quality team member is responsible for the |QCP|,
|
||||
select them in the :guilabel:`Responsible` field.
|
||||
|
||||
The :guilabel:`Step Document` field has two options that specify the location of an instructional
|
||||
document detailing how to complete the quality checks created by the |QCP|.
|
||||
|
||||
Select :guilabel:`Specific Page of Operation Worksheet` if the document is included with the
|
||||
instructional worksheet for the work order, then enter the page number in the :guilabel:`Worksheet
|
||||
Page` field that appears below.
|
||||
|
||||
Select :guilabel:`Custom` if the document should be included in the :guilabel:`Instructions` tab at
|
||||
the bottom of the |QCP|.
|
||||
|
||||
In the :guilabel:`Instructions` tab at the bottom of the form, enter instructions for how to
|
||||
complete the quality checks created by the |QCP|.
|
||||
|
||||
If the :guilabel:`Custom` option was selected in the :guilabel:`Step Document` field above, a
|
||||
document can be attached in this tab. To do so, either select the :guilabel:`Upload your file`
|
||||
button to open the device's file manager, and then select a file, or add a link to a Google Slides
|
||||
document in the :guilabel:`Google Slide Link` field.
|
||||
|
||||
In the :guilabel:`Message If Failure` tab, include instructions for what to do if the quality check
|
||||
fails. For example, instruct the employee processing the quality check to create a :doc:`quality
|
||||
alert <quality_alerts>`.
|
||||
|
||||
The :guilabel:`Notes` tab is used to provide additional information about the |QCP|, like the reason
|
||||
it was created. The information entered in this tab is **not** shown to employees processing the
|
||||
quality checks created by the |QCP|.
|
||||
|
||||
.. image:: quality_control_points/qcp-form.png
|
||||
:align: center
|
||||
:alt: An example of a completed quality control point form for a Pass-Fail test.
|
||||
|
||||
Once a control point has been configured, a quality check will be automatically created and
|
||||
assigned when the specified operation or work order has been reached. Quality checks can be managed
|
||||
by selecting :menuselection:`Quality Control --> Quality Checks`.
|
||||
|
||||
.. tip::
|
||||
To see all of the quality checks created by a control point, go to :menuselection:`Quality
|
||||
Control --> Control Points`, select a control point, and click :guilabel:`Quality Checks` in the
|
||||
top right corner.
|
||||
|
||||
Use case: configure a measure quality check
|
||||
===========================================
|
||||
|
||||
To ensure that a product meets specific measurement requirements, select :guilabel:`Measure` from
|
||||
the :guilabel:`Type` drop-down menu. Selecting the :guilabel:`Measure` quality check type reveals
|
||||
three new fields: :guilabel:`Device`, :guilabel:`Norm`, and :guilabel:`Tolerance`. These fields can
|
||||
be configured so that only products within a certain tolerance will pass the check:
|
||||
|
||||
- :guilabel:`Device`: select the measuring device that should be used to take the measurement
|
||||
(e.g., measuring tape).
|
||||
- :guilabel:`Norm`: specify the desired measurement that the product should conform to and the unit
|
||||
of measurement that should be used
|
||||
- :guilabel:`Tolerance`: select the range that a measurement can be within while still passing the
|
||||
check (e.g., :guilabel:`from` 59.5 mm :guilabel:`to` 60.5 mm)
|
||||
|
||||
.. image:: quality_control_points/measure_quality_check.png
|
||||
:align: center
|
||||
:alt: An example of a quality control point form configured for a measure quality check.
|
||||
|
||||
When the quality control points form is complete, click :guilabel:`Save`. Now, this
|
||||
measurement-based test will trigger for products that were specified on the form.
|
||||
|
||||
When production of the specified product reaches the operation that requires a measure quality
|
||||
check, the manufacturing employee responsible will be prompted to record and validate the measured
|
||||
value in the tablet view. For products that measure within the values indicated in the
|
||||
:guilabel:`Tolerance` fields, the test will pass. However, for products that measure outside of
|
||||
those values, the test will fail. In that case, the worker who performed the check would create a
|
||||
quality alert from the tablet view. That quality alert can then be addressed by the quality
|
||||
management team.
|
||||
:alt: A QCP configured to create Pass - Fail checks for a work order operation.
|
||||
|
Binary file not shown.
Before Width: | Height: | Size: 9.8 KiB |
Binary file not shown.
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
Before Width: | Height: | Size: 28 KiB |
Loading…
Reference in New Issue
Block a user