[IMP] PLM: Update style in ECO

dfsdf

dfsdf

Fix unfinished sentence

Remove tablet link

Apply suggestions from code review

Restore view

closes odoo/documentation#12866

X-original-commit: 3e9c7f8759
Signed-off-by: Samuel Lieber (sali) <sali@odoo.com>
Signed-off-by: Zaz Linkous (stul) <stul@odoo.com>
Co-authored-by: Sam Lieber (sali) <36018073+samueljlieber@users.noreply.github.com>
This commit is contained in:
Zaz Linkous
2025-04-01 22:15:52 +00:00
parent 41e2ef2edf
commit a0e5062459
11 changed files with 70 additions and 113 deletions

View File

@@ -15,7 +15,6 @@ products, and :doc:`bills of materials <../../manufacturing/basic_setup/bill_con
Engineering change orders can be created:
#. :ref:`directly in the ECO type <plm/eco/create-eco>`.
#. by an operator in the :ref:`tablet view <plm/eco/tablet-view>` of an operation.
#. automatically from feedback submitted to the :ref:`ECO type's email alias <plm/eco/eco-type>`.
.. _plm/eco/create-eco:
@@ -23,15 +22,14 @@ Engineering change orders can be created:
Create ECO
==========
To create a new |ECO|, begin by navigating to the *PLM* app. Then, select the |ECO| type card that
will be used to track the progress of the change. On the :guilabel:`Engineering Change Orders` page,
click the :guilabel:`New` button in the top-left corner.
To create a new |ECO|, begin by navigating to the **PLM** app. Then, select the |ECO| type that
should be used to track the progress of the change. On the :guilabel:`Engineering Change Orders`
page, click the :guilabel:`New` button in the top-left corner.
.. note::
Learn how to create new :ref:`ECO types <plm/eco/eco-type>` to categorize and organize change
orders. Doing so ensures employees only view the |ECOs| related to their responsibilities,
whether it involves new product introductions, targeted product line updates, or regulatory
compliance fulfillment.
:doc:`ECO types <eco_type>` categorize and organize change orders. Doing so can ensure that
employees only view the |ECOs| related to their responsibilities, whether it involves new product
introductions, targeted product line updates, or regulatory compliance fulfillment.
On the |ECO| form, fill in the following fields accordingly:
@@ -43,16 +41,24 @@ On the |ECO| form, fill in the following fields accordingly:
- :guilabel:`Bill of Materials` specifies the changed |BOM|. It auto-populates if the product in
:guilabel:`Product` field has an existing |BOM|. If multiple |BOMs| exist, select the intended
radio options from the drop-down menu.
.. important::
A :guilabel:`Product` must be selected before :guilabel:`Bill of Materials` options is
available.
- :guilabel:`Company` field is used in multi-company databases. Specify if the change applies to
products in a specific company, or leave blank if the change applies to all companies.
.. note::
:guilabel:`Company` is only available to specify with multiple companies enabled. See
:doc:`../../../general/multi_company`.
- :guilabel:`Responsible` represents the assignee in charge of this |ECO|. (Optional)
- :guilabel:`Effective` specifies when the |ECO| becomes live. Choosing :guilabel:`As soon as
possible` means the |ECO| applies to the production |BOM| as soon as an authorized user
:ref:`applies the changes <plm/eco/apply-changes>`.
On the other hand, choosing :guilabel:`At Date`, and setting a specific date, leaves a date that
makes it easier to track the version history of the |BOM|, and the specific date |BOMs|, used for
production.
:ref:`applies the changes <plm/eco/apply-changes>`. :guilabel:`At Date` with a specific date
selected will only apply the |BOM| at that date, making it easier to track the version history of
the |BOM| in production.
- :guilabel:`Tags` are assigned to |ECOs| for prioritization and organization. Create a new tag by
typing the name in the field and selecting :guilabel:`Create` from the drop-down menu. (Optional)
@@ -61,7 +67,7 @@ the changes.
By pressing :guilabel:`Start Revision`, three actions occur:
#. The :guilabel:`Documents` smart button appears, storing relevant files of the |BOM|.
#. The :guilabel:`Documents` smart button appears, storing the relevant files of the |BOM|.
#. A copy of the production |BOM| is stored in the newly-appeared :guilabel:`Revision` smart button
of the |ECO|. The next available version number (e.g., `V2`, `V3`, ...) is also assigned to keep
track of all |BOM| versions.
@@ -73,8 +79,7 @@ By pressing :guilabel:`Start Revision`, three actions occur:
Revision` button has been pressed.
.. image:: engineering_change_orders/eco-form.png
:align: center
:alt: ECO with overview of stages in the top-right corner, and *Revision* smart button.
:alt: ECO with overview of stages in the top-right corner, and Revision smart button.
Change components
=================
@@ -89,7 +94,6 @@ the current version, by flagging the test |BOM| with a large :guilabel:`Archived
Doing so opens the archived |BOM|, marked with a large red :guilabel:`Archived` flag.
.. image:: engineering_change_orders/archived-bom.png
:align: center
:alt: Show the archived Bill of Materials.
On the new |BOM|, in the :guilabel:`Components` tab, proceed to modify the components list, by
@@ -103,15 +107,20 @@ changing the :guilabel:`Quantity` of existing components, adding new components
additional component, `Stabilizers`, is added.
.. image:: engineering_change_orders/version-2-bom.png
:align: center
:alt: Make changes to components by going to the new BoM with the *Revision* smart button.
:alt: A revised BOM
Compare changes
---------------
Once the changes are complete, navigate back to the |ECO|, by clicking `ECO00X` in the breadcrumbs
located in the top-left corner. On the |ECO| form, a new :guilabel:`BoM Changes` tab displays the
differences between the current |BOM| and the new version.
To compare a revised |BOM| to the previous version, navigate to the |ECO| for that |BOM| in either
of these ways:
#. From the revised |BOM|, click the |ECO| name (for example, `ECO005: Improve...`) in the
breadcrumbs located in the top-left corner.
#. From the :guilabel:`PLM Overview`, select the |ECO| type in the :guilabel:
On the |ECO| form, a new :guilabel:`BoM Changes` tab displays the differences between the current
|BOM| and the new version.
Blue text indicates new components added to the revised |BOM| that are not in the production |BOM|.
Black text represents updates shared by both |BOMs|, while red text indicates components removed in
@@ -125,8 +134,7 @@ used in production. That is, until the :ref:`changes are applied <plm/eco/apply-
:guilabel:`BoM Changes` tab of the |ECO|.
.. image:: engineering_change_orders/bom-changes.png
:align: center
:alt: View summary of component changes in the *BoM Changes* tab.
:alt: View summary of component changes in the BoM Changes tab.
Change operations
=================
@@ -152,8 +160,13 @@ clicking the :guilabel:`Archive Operation` button.
Compare changes
---------------
Once the changes are complete, navigate back to the |ECO|, by clicking `ECO00X` in the breadcrumbs
located in the top-left corner.
To compare a revised operations to the previous version, navigate to the |ECO| for the |BOM| in
either of these ways:
#. From the revised |BOM|, click the |ECO| name (for example, `ECO005: Improve...`) in the
breadcrumbs located in the top-left corner
#. From the :guilabel:`PLM Overview`, select the |ECO| type card, and then the correct |ECO| from
the Kanban view.
On the |ECO| form, a new :guilabel:`Operation Changes` tab displays the differences between the
current production |BOM| and the new version.
@@ -182,8 +195,7 @@ reflect the following information:
it.
.. image:: engineering_change_orders/instructions-smart-button.png
:align: center
:alt: Show *Instructions* smart button to check whether an operation has additional
:alt: Show Instructions smart button to check whether an operation has additional
instructions.
- :guilabel:`Step Type` details the type of quality control for further instructions in the
@@ -212,8 +224,7 @@ reflect the following information:
provides additional assembly details.
.. image:: engineering_change_orders/operation-changes.png
:align: center
:alt: Show *Operation Changes* tab in an |ECO|.
:alt: Operation Changes tab in an |ECO|.
.. _plm/eco/apply-changes:
@@ -231,7 +242,7 @@ archives the original production |BOM|, and the revised |BOM| becomes the new pr
Verify changes
--------------
To ensure the changes are live, from the |ECO| where the :guilabel:`Apply Changes` button was just
To ensure the changes are live, from the |ECO| where the :guilabel:`Apply Changes` button was
pressed, return to the revised |BOM| by clicking the :guilabel:`Revision` smart button.
On the revised |BOM|, the large red :guilabel:`Archived` flag is removed.
@@ -251,73 +262,16 @@ latest |ECO|.
:guilabel:`Revision` smart button of the |ECO|.
.. image:: engineering_change_orders/bom-version.png
:align: center
:alt: View current *BOM* version in the Miscellaneous tab.
:alt: View current BOM version in the Miscellaneous tab.
.. _plm/eco/tablet-view:
View changes
============
Create ECO from tablet view
===========================
To review proposed changes, navigate to the :menuselection:`PLM app --> Overview`. In the `BOM
Updates` |ECO| type card, the :guilabel:`# Engineering Changes` button represents the number of
operational changes created.
Operators can directly suggest clearer operation instructions, while performing manufacturing orders
(MOs) in the *Manufacturing* app.
To create |ECOs| in this manner, begin by navigating to :menuselection:`Manufacturing app -->
Operations --> Manufacturing Orders`. Then, select the desired :abbr:`MO (Manufacturing Order)` and
switch to the :guilabel:`Work Orders` tab. Then, click the :guilabel:`📱 (mobile phone)` icon for
the desired work order to open the *tablet view* of the operation.
.. important::
The :guilabel:`📱 (mobile phone)` icon is **only** available for :abbr:`MOs (Manufacturing
Orders)` with a :guilabel:`Confirmed` or :guilabel:`In Progress` status.
.. image:: engineering_change_orders/tablet-icon.png
:align: center
:alt: Find the tablet icon for each operation, second from the far right.
Next, add an instructional step, by clicking the :guilabel:`☰ (three horizontal lines)` icon in the
tablet view of an operation. Doing so opens the :guilabel:`Menu` of action items for a :abbr:`MO
(Manufacturing Order)`. Then, click the :guilabel:`Add a step` button.
.. image:: engineering_change_orders/additional-options-menu.png
:align: center
:alt: Open the *Add a Step* pop-up by clicking the three horizontal lines icon in tablet view.
Clicking the button reveals an :guilabel:`Add a step` pop-up window, where the proposed changes are
submitted.
In the :guilabel:`Title` field, enter a short step description. Next, in the :guilabel:`Instruction`
text field, type the instructions of the step in greater detail. Optionally, add an image to the
:guilabel:`Document` field. Once completed, finish by clicking the :guilabel:`Propose Change`
button.
.. example::
To propose an additional check for broken components, enter the details in the :guilabel:`Add a
Step` pop-up window. Doing so creates an instructional quality control point that will be
reviewed in the following section.
.. image:: engineering_change_orders/add-a-step.png
:align: center
:alt: Fill out the *Add a Step* form to suggest an additional quality control point.
Based on the inputs from the :guilabel:`Add a Step` pop-up window, an |ECO| is created with the
following information:
#. :guilabel:`Description` is the name of the operation, followed by the :abbr:`MO (Manufacturing
Order)` number for reference.
#. The |ECO| :guilabel:`Type` is automatically assigned to `BOM Changes`.
#. :guilabel:`Product` and :guilabel:`Bill of Materials` fields are automatically populated, based
on the |BOM| used in the :abbr:`MO (Manufacturing Order)`.
#. :guilabel:`Responsible` is the operator who submitted the feedback.
View ECO
--------
To review the proposed changes, navigate to the :menuselection:`PLM app --> Overview`. In the `BOM
Updates` |ECO| type card, the :guilabel:`X Engineering Changes` button represents the amount of
operational changes created from the tablet view.
Click on the :guilabel:`X Engineering Changes` button to open the kanban view of the |ECO| type. To
Click on the :guilabel:`# Engineering Changes` button to open the Kanban view of the |ECO| type. To
view the suggestion, select an |ECO| in the `New` stage.
On the |ECO|, view a summary of the proposed changes in the :guilabel:`Operation Changes` tab. Click
@@ -325,31 +279,35 @@ the :guilabel:`Revision` smart button to navigate to the revised |BOM| and look
changes in greater detail.
.. example::
An operator suggested another check for broken components by adding a step from the tablet view,
while performing the `Assemble switches` operation for the :abbr:`MO (Manufacturing Order)`
`WH/MO/00010` for the product, `Keyboard`.
An operator suggested another check for broken components by adding a step while performing the
`Assemble switches` operation for the :abbr:`MO (Manufacturing Order)` `WH/MO/00010` for the
product, `Keyboard`.
Then, this created |ECO| can be viewed by navigating to the `BOM Changes` ECO type found in
:menuselection:`PLM app --> Overview`. By default, |ECOs| created from tablet view are set to
spawn in the `New` stage.
:menuselection:`PLM app --> Overview`.
The :guilabel:`Responsible` field is assigned to the operator who made the suggestion, allowing
the employee revising the |BOM| to seek further clarification from the person who proposed the
changes.
.. image:: engineering_change_orders/view-bom-change.png
:align: center
:alt: Find the new ECO in the "BOM Changes" ECO type, in the *New* stage.
On the revised |BOM|, switch to the :guilabel:`Operations` tab, and select the :guilabel:`☰ (three
horizontal lines)` icon. Doing so opens a list of :guilabel:`Steps` to perform the operation, with
the newest instruction titled `New Step Suggestion:`, followed by the user-entered title. Click the
line item to view the suggested changes.
.. image:: engineering_change_orders/view-bom-change.png
:alt: Find the new ECO in the "BOM Changes" ECO type, in the "New" stage.
On the revised |BOM|, switch to the :guilabel:`Operations` tab, and select the :icon:`fa-list-ul`
:guilabel:`(Show Instructions)` icon. Doing so opens a list of :guilabel:`Steps` to perform the
operation, with the newest instruction titled `New Step Suggestion:`, followed by the user-entered
title. Click the line item to view the suggested changes.
.. image:: engineering_change_orders/show-instructions.png
:align: center
:alt: "Show Instructions" icon in the *Operations* tab of a BoM.
Quality control points
----------------------
.. important::
The :doc:`Quality <../../quality>` app is required to configure quality control points.
On the :ref:`quality control point <quality/quality_management/quality-control-points>` form, ensure
the following form fields are accurately filled out to give detailed instructions for operators:
@@ -370,10 +328,9 @@ Once the quality control point is configured, return to the :guilabel:`Steps` li
breadcrumbs. Finally, drag the last quality control line item to its intended order of instructions.
.. example::
Drag and reorder the `Check for broken switches` instruction, by clicking and dragging its "6
dots" icon to move it from the bottom to the second position.
Drag and reorder the `Check for broken switches` instruction, by clicking and dragging its
:icon:`oi-draggable` :guilabel:`(draggable)` icon to move it from the bottom to the second
position.
.. image:: engineering_change_orders/reorder.png
:align: center
:alt: Drag and reorder instructions by selecting the "6 dots" icon on the far left.
:alt: Drag and reorder instructions by selecting the "draggable" icon on the far left.

Binary file not shown.

Before

Width:  |  Height:  |  Size: 23 KiB

After

Width:  |  Height:  |  Size: 8.9 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 6.3 KiB

After

Width:  |  Height:  |  Size: 6.2 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

After

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 14 KiB

After

Width:  |  Height:  |  Size: 14 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 17 KiB

After

Width:  |  Height:  |  Size: 17 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 22 KiB

After

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 31 KiB

After

Width:  |  Height:  |  Size: 11 KiB