diff --git a/content/applications/inventory_and_mrp.rst b/content/applications/inventory_and_mrp.rst index 06a115034..04a007315 100644 --- a/content/applications/inventory_and_mrp.rst +++ b/content/applications/inventory_and_mrp.rst @@ -7,9 +7,10 @@ Inventory & MRP .. toctree:: - inventory_and_mrp/inventory - inventory_and_mrp/manufacturing - inventory_and_mrp/purchase - inventory_and_mrp/barcode - inventory_and_mrp/quality - inventory_and_mrp/maintenance + inventory_and_mrp/inventory + inventory_and_mrp/manufacturing + inventory_and_mrp/purchase + inventory_and_mrp/barcode + inventory_and_mrp/quality + inventory_and_mrp/maintenance + inventory_and_mrp/plm diff --git a/content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst b/content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst index 820fa3bd0..b41046eb1 100644 --- a/content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst +++ b/content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst @@ -1,15 +1,15 @@ -========================== -Create a bill of materials -========================== +================= +Bill of materials +================= .. _manufacturing/management/bill-configuration: -A *Bill of Materials* (or *BoM* for short) is a document that defines the quantity of each -component required to make or deliver a finished product. It can also include various operations -and the individual step guidelines needed to complete a production process. +A *bill of materials* (or *BoM* for short) is a document that defines the quantity of each component +required to make or deliver a finished product. It can also include various operations and the +individual step guidelines needed to complete a production process. In Odoo Manufacturing, multiple :abbr:`BoMs (Bills of Materials)` can be linked to each product, so -that even product variants can have their own tailored :abbr:`BoMs (Bills of Materials)`. +even product variants can have their own tailored :abbr:`BoMs (Bills of Materials)`. Correctly setting up a :abbr:`BoM (Bill of Materials)` helps optimize the manufacturing process and save time. diff --git a/content/applications/inventory_and_mrp/plm.rst b/content/applications/inventory_and_mrp/plm.rst new file mode 100644 index 000000000..0d46c7c09 --- /dev/null +++ b/content/applications/inventory_and_mrp/plm.rst @@ -0,0 +1,19 @@ +:nosearch: +:show-content: +:hide-page-toc: +:show-toc: + +============================ +Product lifecycle management +============================ + +Odoo *Product Lifecycle Management* (*PLM*) offers a systematic approach for testing, collaboration, +and iteration of products across concept development, design, manufacturing, marketing, and +post-launch support stages. + +With approvals, key stakeholders can review changes before implementation. + +.. toctree:: + :titlesonly: + + plm/manage_changes diff --git a/content/applications/inventory_and_mrp/plm/manage_changes.rst b/content/applications/inventory_and_mrp/plm/manage_changes.rst new file mode 100644 index 000000000..bde0de177 --- /dev/null +++ b/content/applications/inventory_and_mrp/plm/manage_changes.rst @@ -0,0 +1,9 @@ +================= +Change management +================= + +.. toctree:: + :titlesonly: + + manage_changes/eco_type + manage_changes/engineering_change_orders diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst b/content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst new file mode 100644 index 000000000..349fb8b98 --- /dev/null +++ b/content/applications/inventory_and_mrp/plm/manage_changes/eco_type.rst @@ -0,0 +1,143 @@ +.. _plm/eco/eco-type: + +.. |BOM| replace:: :abbr:`BoM (Bill of Materials)` +.. |BOMs| replace:: :abbr:`BoMs (Bills of Materials)` +.. |ECO| replace:: :abbr:`ECO (Engineering Change Order)` +.. |ECOs| replace:: :abbr:`ECOs (Engineering Change Orders)` + +======== +ECO type +======== + +An *ECO type* is assigned to *engineering change orders* (ECOs) to organize and track changes to +products and bills of materials (BoMs). Each |ECO| type separates |ECOs| into a project in Gantt +view, ensuring collaborators and stakeholders **only** view and assist with relevant |BOM| +improvements. + +For example, an electronic chip manufacturer might use 'New Product Introduction', 'Product +Improvement', 'Component Change', and 'Firmware Update' |ECO| types. Then, designers and engineers +can focus on |ECOs| in the 'New Product Introduction' and 'Product Improvement' projects, avoiding +unrelated supplier change or firmware update |ECOs|. + +Create ECO type +=============== + +To access and manage ECO types, navigate to :menuselection:`PLM app --> Configuration --> ECO +Types`. + +Create a new ECO type by clicking :guilabel:`New`. On the new :guilabel:`ECO Types` form, fill in +the following information: + +- :guilabel:`Name`: the name of the |ECO| type, which will organize all of the |ECOs| of this *type* + in a project. +- :guilabel:`Email Alias`: if this optional field is filled, emails submitted to this email address + automatically generate |ECOs| in the left-most stage of this |ECO| type. + +.. example:: + The `Formulation change` |ECO| type is used to organize and track related |ECOs| in a single + project. Configuring the :guilabel:`Email Alias` field generates |ECOs| in the `Formulation + change` project sent to the email address, `pawlish-change@pawlished-glam.odoo.com`. + + .. image:: eco_type/create-eco-type.png + :align: center + :alt: Example of an ECO type. + +Edit ECO type +============= + +Modify existing |ECO| type names and email aliases by navigating to the :menuselection:`PLM app --> +Configuration --> ECO Types` page. There, click on the desired |ECO| type from the list. + +On the form for each |ECO| type, proceed to edit the :guilabel:`Name` and :guilabel:`Email Alias` +fields. + +.. _plm/eco/stage-config: + +Stages +====== + +Within an |ECO| type project, *stages* are like milestones and are used to identify the progress of +the |ECO| before the changes are ready to be applied. (e.g. 'Feedback', 'In Progress', 'Approved', +'Complete') + +Additionally, required approvers can be added to each stage, ensuring that changes to the production +|BOM| cannot proceed until the approver reviews and approves the |ECO|. Doing so prevents errors on +the production |BOM| by enforcing at least one review of suggested changes before they're applied on +a production |BOM|. + +For best practice, there should be at least one *verification* stage, which is a stage with a +required approver, and one *closing* stage, which stores |ECOs| that have been either canceled or +approved for use as the next production |BOM|. + +Create stage +------------ + +To add a stage, go to the :menuselection:`PLM` app and select the intended project for an |ECO| type +from the :guilabel:`PLM Overview` dashboard. + +Then, on the :guilabel:`Engineering Change Orders` project pipeline for the |ECO| type, click the +:guilabel:`+ Stage` button. Doing so reveals a text box to fill in the name of the stage. After +filling it in, click the :guilabel:`Add` button to finish adding the stage. + +.. example:: + A new `Assigned` stage separates assigned |ECOs| from the unassigned ones in the `New` stage. + Adding another stage helps the product manager track unassigned tasks. + + .. image:: eco_type/create-stage.png + :align: center + :alt: Create a new stage in a project for an ECO type. + +Verification stage +------------------ + +Click an ECO type from :menuselection:`PLM app --> Overview` to open a kanban view of |ECOs| of this +type. + +To configure a verification stage, hover over the intended stage, and select the :guilabel:`⚙️ +(gear)` icon. Then, click :guilabel:`Edit` to open a pop-up window. + +Configure the verification stage in the edit stage pop-up window, by checking the box for +:guilabel:`Allow to apply changes`. + +Then, add an approver in the :guilabel:`Approvers` section, by clicking :guilabel:`Add a line`, and +specifying the :guilabel:`Role` of the reviewer, their :guilabel:`User`, and :guilabel:`Approval +Type`. + +Make sure at least one approver is configured with the :guilabel:`Approval Type`: :guilabel:`Is +required to approve`. + +The approver listed is automatically notified when |ECOs| are dropped in the stage specified in the +pop-up window. Once finished, click :guilabel:`Save & Close`. + +.. example:: + In the |ECO| type `New Product Introduction`, the verification stage `Validated` is configured by + clicking the :guilabel:`⚙️ (gear)` icon, and selecting :guilabel:`Edit`. Doing so opens the + :guilabel:`Edit: Validated` pop-up window. + + By adding the `Engineering manager` as an approver, only |ECOs| approved by this user can proceed + to the next stage, and have the changes applied on the production |BOM|. + + Additionally, check the :guilabel:`Allow to apply changes` option to ensure proper behavior. + + .. image:: eco_type/verification-stage.png + :align: center + :alt: Show "Allow to apply changes" option is checked. + +Closing stage +------------- + +Configure a closing stage by opening the :guilabel:`Edit: [stage]` pop-up window. To do so, hover +over the intended stage and click the :guilabel:`⚙️ (gear)` icon that appears in the top-right +corner. Then, click :guilabel:`Edit` from the drop-down menu. + +On the :guilabel:`Edit: [stage]` pop-up window, select the check boxes for :guilabel:`Folded in +kanban view`, :guilabel:`Allow to apply changes` and :guilabel:`Final Stage`. + +.. example:: + The closing stage, `Effective` is configured by checking the :guilabel:`Folded in kanban view`, + :guilabel:`Allow to apply changes`, and :guilabel:`Final Stage` options + +.. image:: eco_type/closing-stage.png + :align: center + :alt: Show configurations of the closing stage. + diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/closing-stage.png b/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/closing-stage.png new file mode 100644 index 000000000..c9c8fe423 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/closing-stage.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/create-eco-type.png b/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/create-eco-type.png new file mode 100644 index 000000000..ec17a1c25 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/create-eco-type.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/create-stage.png b/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/create-stage.png new file mode 100644 index 000000000..c48b94a1f Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/create-stage.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/verification-stage.png b/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/verification-stage.png new file mode 100644 index 000000000..61440340c Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/eco_type/verification-stage.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst new file mode 100644 index 000000000..94cb4ba02 --- /dev/null +++ b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders.rst @@ -0,0 +1,378 @@ +========================= +Engineering change orders +========================= + +.. |BOM| replace:: :abbr:`BoM (Bill of Materials)` +.. |BOMs| replace:: :abbr:`BoMs (Bills of Materials)` +.. |ECO| replace:: :abbr:`ECO (Engineering Change Order)` +.. |ECOs| replace:: :abbr:`ECOs (Engineering Change Orders)` + +.. _plm/eco: + +Utilize *engineering change orders* (*ECOs*) to track, implement, and revert change versions made to +products, and :ref:`bills of materials `. + +Engineering change orders can be created: + +#. :ref:`directly in the ECO type `. +#. by an operator in the :ref:`tablet view ` of an operation. +#. automatically from feedback submitted to the :ref:`ECO type's email alias `. + +.. _plm/eco/create-eco: + +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. + +.. note:: + Learn how to create new :ref:`ECO types ` 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. + +On the |ECO| form, fill in the following fields accordingly: + +- :guilabel:`Description` is a brief summary of the improvement. +- :guilabel:`Type`: specifies the |ECO| type project for organizing the |ECOs|. +- :guilabel:`Apply on` determines if the |ECO| changes the :guilabel:`Bill of Materials` or the + :guilabel:`Product Only`. +- :guilabel:`Product` indicates the product being improved. +- :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. +- :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. +- :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 `. + + 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. +- :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) + +After filling out the |ECO| form, click the :guilabel:`Start Revision` button to begin implementing +the changes. + +By pressing :guilabel:`Start Revision`, three actions occur: + +#. The :guilabel:`Documents` smart button appears, storing 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. +#. The stages of the |ECO| :guilabel:`Type` are displayed in the top-right corner of the |ECO|. + +.. note:: + The :guilabel:`Revision` smart button is available **only** when the :guilabel:`Bill of + Materials` radio button is selected in the :guilabel:`Apply on` field, and the :guilabel:`Start + 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. + +Change components +================= + +To modify the components in a |BOM|, click the :guilabel:`Revision` smart button on an |ECO| to +access the new version of the |BOM|. Odoo distinguishes the non-production version of the |BOM| from +the current version, by flagging the test |BOM| with a large :guilabel:`Archived` tag. + +.. example:: + After clicking the :guilabel:`Start Revision` button for an |ECO| for the product, `[D_0045 + Stool]`, make changes to the product's |BOM| by clicking the :guilabel:`Revision` smart button. + 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 +changing the :guilabel:`Quantity` of existing components, adding new components using the +:guilabel:`Add a line` button, and removing components with the :guilabel:`🗑️ (trash)` icon. + +.. _plm/eco/example-keyboard: + +.. example:: + In version two of the |BOM| for a keyboard, the component quantities are reduced, and an + 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. + +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. + +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 +the revised |BOM|. + +Changes and tests are encapsulated in the revised |BOM|, and do **not** affect the |BOM| currently +used in production. That is, until the :ref:`changes are applied `. + +.. example:: + View the summary of the differences between the current and revised keyboard |BOMs| in the + :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. + +Change operations +================= + +To modify the operations in a |BOM|, click the :guilabel:`Revision` smart button on an |ECO| to +access the archived, new version of the |BOM|. + +In the new |BOM| version, switch to the :guilabel:`Operations` tab to view and edit |BOM| +operations. To make changes, select each operation, which opens the corresponding :guilabel:`Open: +Operations` pop-up window. + +.. note:: + The :guilabel:`Operations` tab is *not* available by default. To enable it, navigate to + :menuselection:`Manufacturing app --> Configuration --> Settings`, and check the :guilabel:`Work + Orders` box. + +Make changes to any of the fields in the :guilabel:`Open: Operations` pop-up window, then click +:guilabel:`Save` once completed. + +Create new operations by clicking the :guilabel:`Add a line` button, and remove new operations by +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. + +On the |ECO| form, a new :guilabel:`Operation Changes` tab displays the differences between the +current production |BOM| and the new version. + +Blue text indicates new operations added to the revised |BOM| that do not yet exist in the +production |BOM|. Black text represents updates shared by both |BOMs|, while red text indicates +operations removed in the revised |BOM|. + +Modifications to the |BOM| in an |ECO| will **not** affect the |BOM| used in production. That is, +until the :ref:`changes are applied `. + +In the :guilabel:`Operation Changes` tab, each row of details, beneath the columns in the table, +reflect the following information: + +- :guilabel:`Operation`: Name of the operation that was modified. +- :guilabel:`Step`: specifies the quality control point, visible when the operation includes + detailed instructions. + +.. note:: + To check for instructions, click the operation line item in the :guilabel:`Operations` tab of a + |BOM|. Then, in the :guilabel:`Open: Operations` pop-up window, look for the + :guilabel:`Instructions` smart button displayed at the top. + +.. example:: + The `Assembly` :guilabel:`Operation` includes `10` detailed :guilabel:`Instructions` to complete + it. + + .. image:: engineering_change_orders/instructions-smart-button.png + :align: center + :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 + operation. +- :guilabel:`Type` corresponds with the colored text to specify how the revised |BOM| differs from + the production |BOM|. Operation change types can be :guilabel:`Add`, :guilabel:`Remove`, or + :guilabel:`Update`. +- :guilabel:`Work Center` specifies the work center at which the operation is performed. +- :guilabel:`Manual Duration Change` refers to the change in the :guilabel:`Default Duration` field + in the :guilabel:`Open: Operations` pop-up window, which specifies the expected time for + completing the operation. + +.. example:: + The :guilabel:`Operation Changes` tab compares the production |BOM| with the revised |BOM| in the + |ECO|. + + In the revised |BOM|, a new `Assembly` :guilabel:`Operation` at the :guilabel:`Work Center` + `Assembly Line 1` is added. In addition, the expected duration of the operation is `20.00` + minutes, as specified by the :guilabel:`Manual Duration Change`. + + To supplement the `Assembly` operation, two quality control point instructions are added: + + #. The first is the :guilabel:`Step` `QCP00039`, a :guilabel:`Step Type` to :guilabel:`Register + Production` of components. + #. The second :guilabel:`Step` is `QCP00034`, an `Instructions` :guilabel:`Step Type` that + provides additional assembly details. + + .. image:: engineering_change_orders/operation-changes.png + :align: center + :alt: Show *Operation Changes* tab in an |ECO|. + +.. _plm/eco/apply-changes: + +Apply changes +============= + +After verifying the changes, move the |ECO| to a :ref:`verification stage `, +which are stages that require approval before the revised changes can be applied to the production +|BOM|. + +Once the approvers accept the changes, the :guilabel:`Apply Changes` button becomes available. Click +this button, and the |ECO| is automatically moved to a closing stage. The changes are applied, which +archives the original production |BOM|, and the revised |BOM| becomes the new production |BOM|. + +Verify changes +-------------- + +To ensure the changes are live, from the |ECO| where the :guilabel:`Apply Changes` button was just +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. + +To further verify the changes, check the production |BOM| by going to :menuselection:`Manufacturing +app --> Products --> Products` and select the product. + +Then, on the product form, click the :guilabel:`Bill of Materials` smart button, and select the +|BOM| from the list. In the :guilabel:`Miscellaneous` tab of the |BOM|, the :guilabel:`Version` +field is updated to match the version number shown on the :guilabel:`Revision` smart button of the +latest |ECO|. + +.. example:: + After applying the changes of the |ECO| for the :ref:`keyboard `, view + the version of the current keyboard |BOM| in the :guilabel:`Miscellaneous` tab. Here, the + :guilabel:`Version` number has been updated to `2`, matching the `V2` that appears in the + :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. + +.. _plm/eco/tablet-view: + +Create ECO from tablet view +=========================== + +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 +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 +the :guilabel:`Revision` smart button to navigate to the revised |BOM| and look into the proposed +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`. + + 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. + + 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/show-instructions.png + :align: center + :alt: "Show Instructions" icon in the *Operations* tab of a BoM. + +On the :ref:`quality control point ` form, ensure the following form +fields are accurately filled out to give detailed instructions for operators: + +- :guilabel:`Title`: rename to give a concise description of the new instruction. +- :guilabel:`Control per`: using the drop-down menu, determine whether this instruction applies + broadly for the :guilabel:`Product`, specifically for this :guilabel:`Operation` *only*, or a + particular :guilabel:`Quantity` of the product. +- :guilabel:`Type`: categorizes the control point type. From the drop-down menu, select + :guilabel:`Instructions` to detail an instruction for the worker. To receive input from the + workers, select the :guilabel:`Take a Picture`, :guilabel:`Register Consumed Materials`, + :guilabel:`Print Label`, or other :ref:`quality check options `. + +.. seealso:: + :ref:`Configure quality control points ` + +Once the quality control point is configured, return to the :guilabel:`Steps` list using the +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. + + .. image:: engineering_change_orders/reorder.png + :align: center + :alt: Drag and reorder instructions by selecting the "6 dots" icon on the far left. + diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/add-a-step.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/add-a-step.png new file mode 100644 index 000000000..1fdf4af69 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/add-a-step.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/additional-options-menu.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/additional-options-menu.png new file mode 100644 index 000000000..00efc0e54 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/additional-options-menu.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/archived-bom.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/archived-bom.png new file mode 100644 index 000000000..0ae219401 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/archived-bom.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/bom-changes.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/bom-changes.png new file mode 100644 index 000000000..489d20348 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/bom-changes.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/bom-version.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/bom-version.png new file mode 100644 index 000000000..626d67685 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/bom-version.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/eco-form.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/eco-form.png new file mode 100644 index 000000000..d1dee2908 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/eco-form.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/instructions-smart-button.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/instructions-smart-button.png new file mode 100644 index 000000000..2e1e47e40 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/instructions-smart-button.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/operation-changes.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/operation-changes.png new file mode 100644 index 000000000..bb7cdf8a0 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/operation-changes.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/reorder.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/reorder.png new file mode 100644 index 000000000..0bcfb1fbe Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/reorder.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/show-instructions.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/show-instructions.png new file mode 100644 index 000000000..d9ced1276 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/show-instructions.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/tablet-icon.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/tablet-icon.png new file mode 100644 index 000000000..17694d791 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/tablet-icon.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/version-2-bom.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/version-2-bom.png new file mode 100644 index 000000000..b40b59381 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/version-2-bom.png differ diff --git a/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/view-bom-change.png b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/view-bom-change.png new file mode 100644 index 000000000..59045f0b7 Binary files /dev/null and b/content/applications/inventory_and_mrp/plm/manage_changes/engineering_change_orders/view-bom-change.png differ diff --git a/content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst b/content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst index 93104848b..e76043d12 100644 --- a/content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst +++ b/content/applications/inventory_and_mrp/quality/quality_management/quality_checks.rst @@ -12,7 +12,7 @@ Using a Quality Control Point (QCP), it is possible to create quality checks aut regular intervals. When quality checks are created by a |QCP|, they appear on a manufacturing or inventory order, where the employee processing the order will be prompted to complete them. For a full explanation of how to create and configure a |QCP|, see the documentation on :ref:`quality -control points `. +control points `. While quality checks are most commonly created automatically by a |QCP|, it is also possible to manually create a single quality check. Creating a check manually is useful when an employee wants @@ -81,7 +81,7 @@ specific work order operation, the check is processed in the tablet view for the It is not possible to manually create a single quality check that is assigned to a specific work order operation. Quality checks for work order operations can only be created by a |QCP|. See the documentation on :ref:`Quality Control Points - ` for information about how to configure a + ` for information about how to configure a |QCP| that will create quality checks for a specific work order operation. Quality check page diff --git a/content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst b/content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst index 6a8367b5e..23b3b59f6 100644 --- a/content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst +++ b/content/applications/inventory_and_mrp/quality/quality_management/quality_control_points.rst @@ -2,7 +2,7 @@ Add quality controls ==================== -.. _manufacturing/quality_control/quality-control-points: +.. _quality/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