ECO types and stages¶
Engineering change orders (ECOs) are categorized by the type of change they represent and their statuses are tracked via stages. Both ECO types and stages are defined by the user and can be customized to the specific needs of a business or industry.
ECO types¶
Each ECO type separates ECOs into different projects in the PLM Overview, ensuring collaborators and stakeholders only view and assist with relevant BoM improvements.
Example
An electronic chip manufacturer uses five ECO types: New Product Introduction
, BOM Updates
,
Component Change
, Product Improvement
, and Firmware Update
. In their configuration,
engineers can spend time exclusively on ECOs in the Component Change
and Firmware Update
types, while designers see ECOs in the New Product Introduction
type, allowing each
discipline to focus only on those changes that require their domain expertise.

Create an ECO type¶
要访问和管理 ECO 类型,请导航至
。点击 新建 ,创建新的 ECO 类型。在新的 ECO 类型 表格中,填写以下信息:
名称:ECO 类型的名称,它将组织项目中该*类型*的所有 ECO。
电子邮件别名:如果填写了此可选字段,则向此电子邮件地址提交的电子邮件将自动在此 ECO 类型的最左级生成 ECO。
Example
“配方变更” ECO 类型用于在单个项目中组织和追踪相关的 ECO。配置 电子邮件别名 字段后,“配方更改” 项目中的 ECO 会发送到电子邮件地址“pawlish-change@pawlished-glam.odoo.com”。

Edit ECO types¶
通过导航至
页面,修改现有 ECO 类型名称和电子邮件别名。在该页面中,从列表中点击所需的 ECO 类型。On the form for each ECO type, edit the Name or Email Alias fields.
阶段¶
Within the Engineering Change Orders Kanban view for a specific ECO type, stages are
milestones used to identify the progress of the ECO before the changes are ready to be applied. By
default, Odoo uses New
, In Progress
, Validated
, and Effective
, but these are fully
customizable to the specific life cycle of an ECO type.

注解
The Effective
stage is folded by default to avoid listing every single ECO that has gone into
effect. See Closing stage for more on this configuration.
Verification stages require a designated user to approve, ensuring that changes do not proceed until the ECO changes have been reviewed by the appropriate stake holders. Closing stages that can apply changes put BoM and operations changes into immediate effect, changing all pending and future MO to the latest BoM version.
小技巧
The most common practice is to have at least one verification stage, which is a stage with a required approver, and one closing stage, which stores ECOs that have been either cancelled or approved for use as the next production BoM.
更多内容
Verification stages¶
To configure a verification stage, hover over the intended stage, and select the (Actions). Then, click Edit to open a pop-up window and check the box for Allow to apply changes.
Next, add an approver in the Approvers section, by clicking Add a line, and specifying the Role of the reviewer, the User, and an Approval Type of Is required to approve. See more about approval types.
在弹出窗口中指定的阶段丢弃 ECO 时,会自动通知列出的审批人。完成后,点击 保存并关闭 。
更多内容
Closing stages¶
Click an ECO type from
to open the Kanban view of ECOs of this type.To configure a closing stage that applies BoM, edit the stage and tick the boxes for Folded in kanban view, Allow to apply changes, and Final Stage. When ECO cards are placed in a stage that will Allow to apply changes, then any BoM and operations changes validated in the ECOs will immediately be put into effect. To create a cancelled stage, create or edit a stage and tick the boxes for Folded in kanban view and Final Stage. ECOs in this stage are removed from the pipeline, but will not make changes.
Example
通过选中 折叠在看板视图中、允许应用变更 和 最后阶段 选项,可配置关闭阶段“有效”。
