Skip to content

Commit b48e20f

Browse files
Felicioushojo-odoo
andcommitted
[ADD] engineering change order
Co-authored-by: hojo-odoo <123424465+hojo-odoo@users.noreply.github.com>
1 parent 91895e7 commit b48e20f

File tree

17 files changed

+284
-0
lines changed

17 files changed

+284
-0
lines changed

content/applications/inventory_and_mrp/manufacturing.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,4 +21,5 @@ and allow workers to trigger maintenance operations, feedback loops, quality iss
2121

2222
manufacturing/maintenance
2323
manufacturing/management
24+
manufacturing/plm
2425
manufacturing/quality_control

content/applications/inventory_and_mrp/manufacturing/management/bill_configuration.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,8 @@
22
Create a bill of materials
33
==========================
44

5+
.. _manufacturing/management/bill-configuration:
6+
57
A *Bill of Materials* (or *BoM* for short) is a document that defines the quantity of each
68
component required to make or deliver a finished product. It can also include various operations
79
and the individual step guidelines needed to complete a production process.
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
:nosearch:
2+
3+
============================
4+
Product Lifecycle Management
5+
============================
6+
7+
Odoo Product Lifecycle Management (PLM) offers a systematic approach for testing, collaboration, and
8+
iteration of products across concept development, design, manufacturing, marketing, and post-launch
9+
support stages. With approvals, key stakeholders can review changes before implementation.
10+
11+
.. toctree::
12+
:titlesonly:
13+
14+
plm/engineering_change_orders
Lines changed: 265 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,265 @@
1+
=========================
2+
Engineering change orders
3+
=========================
4+
5+
.. |BOM| replace:: :abbr:`BoM (Bill of Materials)`
6+
.. |BOMs| replace:: :abbr:`BoMs (Bills of Materials)`
7+
.. |ECO| replace:: :abbr:`ECO (Engineering Change Order)`
8+
.. |ECOs| replace:: :abbr:`ECOs (Engineering Change Orders)`
9+
10+
.. _plm/eco:
11+
12+
Utilize *Engineering Change Orders* (ECO) to track and implement changes to products and :ref:`bills
13+
of materials <manufacturing/management/bill-configuration>`. View and create :abbr:`ECOs
14+
(engineering change orders)` within each *ECO type*, a project pipeline in Gantt view that consists
15+
of stages, ensuring progress tracking for collaborators and stakeholders.
16+
17+
Engineering change orders can be created:
18+
19+
#. :ref:`directly in the ECO type <plm/eco/create-eco>`
20+
#. by an operator in the :ref:`tablet view <plm/eco/tablet-view>` of an operation
21+
#. automatically from feedback submitted to the :ref:`ECO type's email alias <plm/eco/eco-type>`.
22+
23+
.. _plm/eco/create-eco:
24+
25+
Create new ECO
26+
==============
27+
28+
To create a new |ECO|, begin by navigating to the :menuselection:`PLM app` and select the ECO type
29+
card that will be used to track the progress of the change. On the :guilabel:`Engineering Change
30+
Orders` page, click on the :guilabel:`New` button at the top left.
31+
32+
On the |ECO| form, type in a short :guilabel:`Description` of the change and select the
33+
:guilabel:`Product` from the drop-down field. In the :guilabel:`Apply on` field, select either the
34+
:guilabel:`Bill of Materials` or :guilabel:`Product Only` radio selection options.
35+
36+
Optionally, set a particular deadline for the completion of the change with an :guilabel:`Effective`
37+
date, or add :guilabel:`Tags` for categorization.
38+
39+
Finally, click :guilabel:`Start Revision` after filling out the form to begin implementing the
40+
changes. Clicking the button unveils the stages of the ECO type, the :guilabel:`Documents` smart
41+
button, the :guilabel:`Revision` smart button and the new |BOM| version number.
42+
43+
.. note::
44+
:guilabel:`Revision` smart button is available only when the :guilabel:`Bill of Materials` radio
45+
button is selected for the :guilabel:`Apply on` field.
46+
47+
.. image:: engineering_change_orders/eco-form.png
48+
:align: center
49+
:alt: Active ECO with overview of stages in the top right, and *Revision* smart button.
50+
51+
Change components
52+
-----------------
53+
54+
To modify the components in a |BOM|, click the :guilabel:`Revision` smart button on an active |ECO|
55+
to access the new version of the |BOM|. Odoo distinguishes the non-production version of the |BOM|
56+
from the current version by flagging the test |BOM| with a large :guilabel:`Archived` tag.
57+
58+
On the new |BOM|, switch to the :guilabel:`Components` tab. Modify the components list by changing
59+
the :guilabel:`Quantity` of existing components, adding new components using the :guilabel:`Add a
60+
line` button, and removing components with the :guilabel:`🗑️ (trash)` icon.
61+
62+
.. _plm/eco/example-keyboard:
63+
64+
.. example::
65+
In version two of the |BOM| for a keyboard, the component quantities are reduced, and an
66+
additional component, `Stabilizers`, is added.
67+
68+
.. image:: engineering_change_orders/version-2-BOM.png
69+
:align: center
70+
:alt: Make changes to components by going to the new BoM with the *Revision* smart button.
71+
72+
Once the changes are complete, navigate back to the |ECO| itself by clicking `ECO00X` in the
73+
breadcrumbs in the top left. On the |ECO| form, a new :guilabel:`BoM Changes` tab displays the
74+
differences between the current |BOM| and the new version. This ensures changes and tests are
75+
encapsulated in the revised |BOM| and do not affect the |BOM| currently used in production. That is,
76+
until the :ref:`changes are applied <plm/eco/apply-changes>`.
77+
78+
.. example::
79+
View the summary of the differences between the current and revised keyboard |BOMs| in the
80+
:guilabel:`BoM Changes` tab of the |ECO|.
81+
82+
.. image:: engineering_change_orders/BoM-changes.png
83+
:align: center
84+
:alt: View summary of component changes in the *BoM Changes* tab.
85+
86+
Change operations
87+
=================
88+
89+
To modify the work orders in a |BOM|, click the :guilabel:`Revision` smart button on an active |ECO|
90+
to access the archived, new version of the |BOM|. In the new |BOM| version, switch to the
91+
:guilabel:`Operation Changes` tab and make changes to existing operations by selecting each
92+
operation line item and opening the corresponding :guilabel:`Open: Operations` pop-up window. Make
93+
changes to any of the fields in the pop-up and click :guilabel:`Save` once completed. Create new
94+
operations by clicking the :guilabel:`Add a line` button, and remove new operations by clicking the
95+
:guilabel:`Archive` button.
96+
97+
.. note::
98+
The :guilabel:`Operations` tab is not available by default. To enable it, navigate to
99+
:menuselection:`Manufacturing --> Configuration --> Settings` and check the :guilabel:`Work
100+
Orders` box.
101+
102+
Once the changes are complete, navigate back to the |ECO| itself by clicking `ECO00X` in the
103+
breadcrumbs in the top left. On the |ECO| form, a new :guilabel:`Operation Changes` tab displays the
104+
differences between the current production |BOM| and the new version. Modifications to the |BOM| in
105+
an |ECO| will not affect the |BOM| used in production. That is, until the :ref:`changes are applied
106+
<plm/eco/apply-changes>`.
107+
108+
.. _plm/eco/apply-changes:
109+
110+
Apply changes
111+
=============
112+
113+
After verifying the changes, move the |ECO| to a :ref:`verification stage <plm/eco/stage-config>`.
114+
Once the approvers accept the changes, the :guilabel:`Apply Changes` button will become available.
115+
Click this button, and the |ECO| will be automatically closed.
116+
117+
To ensure the changes are live, navigate to the :guilabel:`Revision` smart button. The |BOM| will
118+
have the large red :guilabel:`Archived` tag removed. Additionally, navigate to the product form,
119+
switch to the :guilabel:`Miscellaneous` tab, and the :guilabel:`Version` field will be updated to
120+
match the version number shown on the :guilabel:`Revision` smart button of the latest |ECO|.
121+
122+
.. example::
123+
After applying the changes of the |ECO| for the :ref:`keyboard <plm/eco/example-keyboard>`, view
124+
the version of the current keyboard |BOM| in the :guilabel:`Miscellaneous` tab. Here, the
125+
:guilabel:`Version` number has been updated to `2`, matching the `V2` that appears in the
126+
:guilabel:`Revision` smart button of the |ECO|.
127+
128+
.. image:: engineering_change_orders/BOM-version.png
129+
:align: center
130+
:alt: View current *BOM* version in the Miscellaneous tab.
131+
132+
.. _plm/eco/tablet-view:
133+
134+
Create ECO from tablet view
135+
===========================
136+
137+
|ECOs| created in *tablet view* are intended for operators to directly suggest clearer assembly
138+
instructions. To create an |ECO|, navigate to the :guilabel:`Work Orders` tab on an ongoing
139+
manufacturing order. Click the :guilabel:`tablet icon` for the desired work order to open the tablet
140+
view of the operation.
141+
142+
.. image:: engineering_change_orders/tablet-icon.png
143+
:align: center
144+
:alt: Find the tablet icon for each operation, second from the far right.
145+
146+
Next, add an instructional step by clicking the :guilabel:`☰ (three horizontal lines)` icon in
147+
tablet view of an operation. Then, click the :guilabel:`Add a step` button.
148+
149+
.. image:: engineering_change_orders/additional-options-menu.png
150+
:align: center
151+
:alt: Navigate to the "Add a Step" pop-up by clicking the three horizontal lines icon in tablet
152+
view.
153+
154+
In the :guilabel:`Title` field, enter a short step description. Next, in the
155+
:guilabel:`Instructions` text field, type the instructions of the step in greater detail.
156+
Optionally, add an image to the :guilabel:`Document` field. Once completed, finish by clicking the
157+
:guilabel:`Propose Change` button.
158+
159+
.. example::
160+
To propose an additional check for broken components, enter the details in the :guilabel:`Add a
161+
Step` pop-up. Doing so creates an instructional quality control point that will be reviewed in
162+
the following section.
163+
164+
.. image:: engineering_change_orders/add-a-step.png
165+
:align: center
166+
:alt: Fill out the *Add a Step* form to suggest an additional quality control point.
167+
168+
View ECO
169+
--------
170+
171+
To review the proposed changes, go to the `BOM Changes` ECO type from :menuselection:`PLM app -->
172+
Overview` and click on the card to view the contained |ECOs|. Click on the newly created |ECO| in
173+
the `New` stage, and view a summary of the proposed changes in the :guilabel:`Operation Changes`
174+
tab. To implement the changes, click the :guilabel:`Revision` smart button.
175+
176+
.. example::
177+
178+
An |ECO| adding another check for broken components is created in the `BOM Changes` ECO type
179+
found in :menuselection:`PLM app --> Overview`. By default, |ECOs| created from tablet view are
180+
named with the manufacturing order number for reference.
181+
182+
.. image:: engineering_change_orders/view-BOM-change.png
183+
:align: center
184+
:alt: Find the new ECO in the "BOM Changes" ECO type, in the *New* stage.
185+
186+
On the new |BOM|, switch to the :guilabel:`Operations` tab and select the :guilabel:`☰ (Show
187+
Instructions)` icon. Doing so opens a list of :guilabel:`Steps` to perform the operation, with the
188+
newest instruction titled `New Step Suggestion:` followed by the user-entered title. Click the line
189+
item to view the suggested changes.
190+
191+
.. image:: engineering_change_orders/show-instructions.png
192+
:align: center
193+
:alt: "Show Instructions" icon in the *Operations* tab of a BoM.
194+
195+
On the :ref:`quality control point <quality/quality_control_points>` form, ensure the following form
196+
fields are accurately filled out to give detailed instructions for operators:
197+
198+
- :guilabel:`Title`: rename to give a concise description of the new instruction
199+
- :guilabel:`Control per`: using the drop-down menu, determine whether this instruction applies
200+
broadly for the :guilabel:`Product`, specifically for this :guilabel:`Operation` only, or a
201+
particular :guilabel:`Quantity` of the product
202+
- :guilabel:`Type`: categorizes the control point type. From the drop-down menu, select
203+
:guilabel:`Instructions` to detail an instruction for the worker. To receive input from the
204+
workers, select the :guilabel:`Take a Picture`, :guilabel:`Register Consumed Materials`,
205+
:guilabel:`Print Label`, or other :ref:`quality check options <quality/quality_control_points>`.
206+
207+
Once the quality control point is configured, return to the :guilabel:`Steps` list using the
208+
breadcrumbs. Finally, drag the last quality control line item to its intended order of instructions.
209+
210+
.. example::
211+
Drag and reorder the `Check for broken switches` instruction by clicking and dragging its "6
212+
dots" icon to move it from the bottom to the second position.
213+
214+
.. image:: engineering_change_orders/reorder.png
215+
:align: center
216+
:alt: Drag and reorder instructions by selecting the "6 dots" icon on the far left.
217+
218+
.. _plm/eco/eco-type:
219+
220+
Create ECO type
221+
===============
222+
223+
To access and manage ECO types, navigate to :menuselection:`PLM app --> Configuration --> ECO
224+
Types`. Create a new ECO type by clicking :guilabel:`New`, and fill in the :guilabel:`Name`. The
225+
:guilabel:`Email Alias` field is optional, but feedback submitted to the filled-in email address
226+
will automatically create an |ECO| in this ECO type. Modify existing ECO type names and email
227+
aliases by clicking on the respective ECO type in the list.
228+
229+
Existing ECO types are displayed in task form on the :guilabel:`PLM Overview` page, accessible by
230+
navigating to :menuselection:`PLM app --> Overview`.
231+
232+
.. _plm/eco/stage-config:
233+
234+
Stage configuration
235+
-------------------
236+
237+
Click an ECO type from :menuselection:`PLM app --> Overview` to open a kanban view of |ECOs| of this
238+
type. In the pipeline, ensure there is at least one *verification* stage, where |ECO| changes can be
239+
applied, and a *closing stage*, for storing completed |ECOs|. To configure a stage, hover over the
240+
intended stage and select the :guilabel:`⚙️ (gear)` icon. Then, click :guilabel:`Edit` to open a
241+
pop-up window.
242+
243+
Configure the verification stage in the edit stage pop-up by checking the box for :guilabel:`Allow
244+
to apply changes`. Optionally, add :guilabel:`Approvals` to automatically notify people to verify
245+
the changes before they go live. Once finished, select the :guilabel:`Save & Close` button.
246+
247+
.. example::
248+
249+
The stage named `Validated` is intended to store |ECOs| to be reviewed by the main approver, the
250+
engineering manager, before the changes are applied to production. To reflect this, the
251+
engineering manager is listed in the :guilabel:`Approvals` section. Additionally, the
252+
:guilabel:`Allow to apply changes` option is checked.
253+
254+
.. image:: engineering_change_orders/verification-stage.png
255+
:align: center
256+
:alt: Show "Allow to apply changes" option is checked.
257+
258+
Next, hover over the closing stage and select the corresponding :guilabel:`⚙️ (gear)` icon to open
259+
the edit stage pop-up. Ensure that the :guilabel:`Folded in kanban view`, :guilabel:`Allow to apply
260+
changes`, and :guilabel:`Final Stage` options are checked.
261+
262+
.. image:: engineering_change_orders/closing-stage.png
263+
:align: center
264+
:alt: Show configurations of the closing stage.
265+
6.34 KB
Loading
22.9 KB
Loading
51.4 KB
Loading
18.8 KB
Loading
18.4 KB
Loading
39.1 KB
Loading

0 commit comments

Comments
 (0)