[REF] Inventory and MRP: Update TOC tree

closes odoo/documentation#5961

X-original-commit: 7b67d69abd
Signed-off-by: Zachary Straub (zst) <zst@odoo.com>
This commit is contained in:
John Holton (hojo)
2023-08-23 11:21:39 -07:00
committed by Zachary Straub (ZST)
parent 175a138eac
commit 51a1623f69
79 changed files with 134 additions and 64 deletions
@@ -1,10 +0,0 @@
:nosearch:
===========
Maintenance
===========
.. toctree::
:titlesonly:
maintenance/add_new_equipment
@@ -1,85 +0,0 @@
=================
Add new equipment
=================
In Odoo, **equipment** refers to any item that is used in everyday operations, including the
manufacturing of products. This can mean a piece of machinery on a production line, a tool that is
used in different locations, or a computer in an office space. Equipment registered in Odoo can be
owned by the company that uses the Odoo database, or by a third party, such as a vendor in the case
of equipment rentals.
Using Odoo **Maintenance**, it is possible to track individual pieces of equipment, along with
information about their maintenance requirements. To add a new piece of equipment, navigate to the
:guilabel:`Maintenance` module, select :menuselection:`Equipments --> Machines & Tools --> Create`,
and configure the equipment as follows:
- :guilabel:`Equipment Name`: the product name of the piece of equipment
- :guilabel:`Equipment Category`: the category that the equipment belongs to; for example,
computers, machinery, tools, etc.; new categories can be created by navigating to
:menuselection:`Configuration --> Equipment Categories` and clicking :guilabel:`Create`
- :guilabel:`Company`: the company that owns the equipment; again, this can be the company that uses
the Odoo database, or a third-party company
- :guilabel:`Used By`: specify if the equipment is used by a specific employee, department, or both;
select :guilabel:`Other` to specify both an employee and a department
- :guilabel:`Maintenance Team`: the team responsible for servicing the equipment; new teams can be
created by navigating to :menuselection:`Configuration --> Maintenance Teams` and
selecting :guilabel:`Create`; the members of each team can also be assigned from this page
- :guilabel:`Technician`: the person responsible for servicing the equipment; this can be used to
assign a specific individual in the event that no maintenance team is assigned or when a specific
member of the assigned team should always be responsible for the equipment; any person added to
Odoo as a user can be assigned as a technician
- :guilabel:`Used in location`: the location where the equipment is used; this is a simple text
field that can be used to specify locations that are not work centers, like an office, for
example
- :guilabel:`Work Center`: if the equipment is used at a work center, specify it here; equipment can
also be assigned to a work center by navigating to :menuselection:`Maintenance --> Equipments -->
Work Centers`, selecting a work center or creating a new one using the :guilabel:`Create` button,
and clicking the :guilabel:`Equipment` tab on the work center form
.. image:: add_new_equipment/new-equipment-form.png
:align: center
:alt: An example of a fully configured new equipment form.
Include additional product information
--------------------------------------
The :guilabel:`Product Information` tab at the bottom of the form can be used to provide further
details about the piece of equipment:
- :guilabel:`Vendor`: the vendor that the equipment was purchased from
- :guilabel:`Vendor Reference`: the reference code assigned to the vendor
- :guilabel:`Model`: the specific model of the piece of equipment
- :guilabel:`Serial Number`: the unique serial number of the equipment
- :guilabel:`Effective Date`: the date that the equipment became available for use; this is used to
calculate the :abbr:`MTBF (Mean Time Between Failures)`
- :guilabel:`Cost`: the amount the equipment was purchased for
- :guilabel:`Warranty Expiration Date`: the date on which the equipment's warranty will expire
.. image:: add_new_equipment/new-equipment-product-information.png
:align: center
:alt: The product information tab for the new piece of equipment.
Add maintenance details
-----------------------
The :guilabel:`Maintenance` tab includes information that can be useful to maintenance teams:
- :guilabel:`Preventive Maintenance Frequency`: specifies how often maintenance should be
performed to prevent equipment failure
- :guilabel:`Maintenance Duration`: the amount of time required to fix the equipment when it fails
- :guilabel:`Expected Mean Time Between Failure`: the average amount of time that the equipment is
expected to operate before failing
.. image:: add_new_equipment/new-equipment-maintenance.png
:align: center
:alt: The maintenance tab for the new piece of equipment.
.. Note::
The :guilabel:`Maintenance` tab also includes sections for :guilabel:`Mean Time Between Failure`,
:guilabel:`Estimated Next Failure`, :guilabel:`Latest Failure`,
and :guilabel:`Mean Time To Repair`. These values are calculated automatically based on
maintenance requests if any exist.
.. tip::
To see the maintenance requests for a piece of equipment, go to the page for the equipment and
select :guilabel:`Maintenance` in the top right corner of the form.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 12 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 9.0 KiB

@@ -1,8 +1,8 @@
:nosearch:
========================
Manufacturing management
========================
=======================
Manufacturing workflows
=======================
.. toctree::
:titlesonly:
@@ -1,11 +0,0 @@
:nosearch:
===============
Quality control
===============
.. toctree::
:titlesonly:
quality_control/quality_control_points
quality_control/quality_alerts
@@ -1,79 +0,0 @@
=====================
Create quality alerts
=====================
Configuring quality control points is a great way to ensure that quality checks are performed at
routine stages during specific operations. However, quality issues can often appear outside of these
scheduled checks. Using Odoo *Quality*, users can create quality alerts for issues that are not
detected by automated processes.
.. seealso::
:doc:`Add quality control points <quality_control_points>`
Find and fill out the quality alerts form
=========================================
In some situations, it is necessary to manually create quality alerts within the *Quality* module.
.. example::
A helpdesk user who is notified of a product defect by a customer ticket can create an alert that
brings the issue to the attention of the relevant quality team.
To create a new quality alert, start from the :menuselection:`Quality` module and select
:menuselection:`Quality Control --> Quality Alerts --> Create`. The quality alert form can then be
filled out as follows:
- :guilabel:`Title`: choose a concise, yet descriptive title for the quality alert
- :guilabel:`Product`: the product about which the quality alert is being created
- :guilabel:`Product Variant`: the specific variant of the product that has the quality issue, if
applicable
- :guilabel:`Lot`: the lot number assigned to the product
- :guilabel:`Work Center`: the work center where the quality issue originated
- :guilabel:`Picking`: the picking operation during which the quality issue originated
- :guilabel:`Team`: the quality team that will be notified by the quality alert
- :guilabel:`Responsible`: the individual responsible for managing the quality alert
- :guilabel:`Tags`: classify the quality alert based on user-created tags
- :guilabel:`Root Cause`: the cause of the quality issue, if known
- :guilabel:`Priority`: assign a priority between one and three stars to ensure more
urgent issues are prioritized
The tabs at the bottom of the form can be used to provide additional information to quality teams:
- :guilabel:`Description`: provide additional details about the quality issue
- :guilabel:`Corrective Actions`: the method for fixing affected products
- :guilabel:`Preventive Actions`: procedures for preventing the issue from occurring in
the future
- :guilabel:`Miscellaneous`: the product vendor (if applicable), the company that produces
the product, and the date assigned
.. image:: quality_alerts/quality-alert-form.png
:align: center
:alt: An example of a completed quality alert form.
Add quality alerts during the manufacturing process
===================================================
Odoo enables manufacturing employees to create quality alerts within a work order without accessing
the *Quality* module. From the work order tablet view, click the :guilabel:` ☰ ` hamburger menu
icon in the top left corner and select :guilabel:`Quality Alert`.
.. image:: quality_alerts/work-order-tablet-view-menu-button.png
:align: center
:alt: Access the work order menu.
The quality alert form can then be filled out as detailed in the previous section. After saving the
form, a new alert will appear on the :guilabel:`Quality Alerts` dashboard that can be found through
the :menuselection:`Quality --> Quality Control` menu.
Manage existing quality alerts
==============================
By default, quality alerts are organized in a kanban board view. The stages of the kanban board are
fully configurable and alerts can be moved from one stage to the next by dragging and dropping or
from within each alert. Additional options are available for viewing alerts, including graph,
calendar, and pivot table views.
.. tip::
Filter alerts based on diverse criteria like date assigned or date closed. Alerts can also be
grouped by quality team, root cause, or other parameters found under the :guilabel:`Filters`
button menu.
Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

@@ -1,87 +0,0 @@
====================
Add quality controls
====================
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.
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:
- :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
The tabs at the bottom of the form can be used to provide additional information to quality teams:
- :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
.. image:: quality_control_points/quality-control-point-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.