OmniApproval™ - ECO Approvals
by Viindoo
| Lines of Code | 436 |
| Technical name | viin_mrp_plm_approval |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/19.0/viin_mrp_plm_approval |
| Read description for | v 15.0 v 16.0 v 17.0 v 18.0 |
| Required Apps | Manufacturing (mrp) Discuss (mail) Inventory (stock) Employees (hr) |
| Included Dependencies | Product Lifecycle (PLM) Viindoo Base OmniApproval™: One platform. Every approval. Advanced HR Management OmniApproval™ - Stock Approvals OmniApproval™ - MRP Approvals Safe IR Metadata Proxies |
Engineering changes signed off on record before they apply
For manufacturers whose engineers prepare changes that someone else signs off
Ask for approval of an engineering change order (ECO) from the ECO itself and keep every sign-off on record; marking the approved request as done applies the change.
Odoo 19.0 · Odoo Community · Viindoo Cloud · OPL-1
Extends Product Lifecycle (PLM) with the approval engine of OmniApproval™.
What changes for your team
Ask for sign-off from the change itself
Today: engineers copy the change into an email and wait for a reply.
→ Get Approved on an engineering change order (ECO) opens an approval request already filled in with the ECO, its product, bill of materials and manufacturing order. The engineer submits it as it is.
Every sign-off on record
Today: who agreed to a change, and when, lives in someone's inbox.
→ The request keeps its approvers, its progress and the approval date, and the ECO shows a ribbon - Waiting for Approvals, then Fully Approved - so production sees the status without asking.
Approved changes apply in the same step
Today: someone applies the change by hand once the reply arrives.
→ Marking the approved request as done applies the ECO with the rights of the person who marks it: a bill-of-materials change takes effect, and a change on a manufacturing order moves the order to the new version. An ECO already applied by hand is left as it is.
Ready on day one
An approval type for ECOs
Every company receives an Engineering Change Order approval type that asks for the manager's approval.
Reachable from PLM
The PLM app opens the ECO approval types from its Changes menu and from each ECO type card on its dashboard.
Installs on its own
Once Product Lifecycle and OmniApproval™ - MRP Approvals are both installed, this module installs itself.
What you set first
Who approves and in how many steps, on the approval type; the PLM right for engineers and the approval right for approvers.
What is included
The Engineering Change Order approval type for every company, Get Approved and the approval status on each ECO, and the application of the ECO when its request is marked as done. Approvers, steps and access rights come from OmniApproval™, set by each company.
Before you decide
Does an ECO have to wait for approval?
No. The approval is a record of who agreed and when; by default it blocks nothing. An ECO applied directly stays applied, and its request leaves it as it is.
Who approves, and in how many steps?
Each company decides on its approval type, which starts with the employee's manager. The module adds no approver, group or access rule of its own. When no manager of the employee is a Team Approver, the request says on screen who approves instead.
Who sees what?
Engineers need the PLM User right to work on ECOs and request approval. Approvers use the rights of the approval app: Team Approver, Officer or Administrator. Marking a request as done applies the ECO with the rights of the person who marks it.
What happens when a request is refused or cancelled?
The ECO is not applied, and its ribbon shows the refusal or the cancellation, so nobody mistakes it for an approved change.
Where does the data live, and which languages ship?
Everything stays in your Odoo database; the module calls no outside service. It ships in English and Vietnamese.
Try it, then ask us
The Live Preview button opens the ECOs on a demo database; the Documentation tab walks through each role.
Pre-sales & partnership
viindoo.com/contactusTechnical support
viindoo.com/ticketTechnical requirements
- Odoo version: 19.0
- Editions: Odoo Community, Viindoo Cloud
- Required modules: Product Lifecycle (PLM), OmniApproval™: One platform. Every approval., OmniApproval™ - MRP Approvals
- License: OPL-1
- Languages: English, Vietnamese
ECO Approvals
For engineers, approvers and administrators who use the PLM and Approval apps.
Note
Extends PLM - see its documentation: to_mrp_plm.
Note
Extends Approval - see its documentation: viin_approval.
Overview
ECO Approvals lets a business have an engineering change order (ECO) reviewed and signed off before it is applied. The engineer files the request from the ECO itself, the approvers decide on the approval request, and marking the request as done applies the ECO. The approval is a record of who agreed to the change and when; it adds no restriction to the ECO.
The process runs in three stages:
- Request - the engineer chooses Get Approved on the ECO and submits the request that is created.
- Decide - the approvers approve or refuse the request.
- Apply - when the approved request is marked as done, the ECO is applied.
| Role | What they do | Access right to assign |
|---|---|---|
| Engineer | Prepares the ECO, files it for approval and follows the request. | PLM: User |
| Approver | Reviews the request, approves or refuses it and marks it as done. | Approvals: Team Approver or Officer |
| Approval administrator | Maintains the approval type of the ECOs and its approvers. | Approvals: Administrator |
Who approves, in how many steps, is decided by the approval type of each company; this module adds no approver and no access right of its own.
Setup (for the Administrator)
Installation
- Open Apps, search for ECO Approvals and click Install. PLM and Approval are installed with it.
- Each company receives an approval type named Engineering Change Order. Open Approval ‣ Configuration ‣ Approval Types to review its approvers and steps, or open PLM ‣ Changes ‣ Request to see the ECO types only.
The same list opens from the dashboard: on PLM ‣ Dashboard, open the menu of an ECO type card and choose ECO Approvals.
By default the request goes first to the manager of the employee who files it. When no manager of that employee is a Team Approver, the request shows a warning and the approval administrator approves instead; add the manager to the Team Approver group to avoid it.
Assigning access rights
- Open Settings ‣ Users & Companies ‣ Users and select a user.
- Give engineers the User right of PLM, and approvers the Team Approver or Officer right of Approvals.
- Give the User right of PLM to everyone who marks a request as done: the ECO is applied with the rights of the person who marks the request as done, so that person must be allowed to read and apply ECOs.
Engineer: get an ECO approved
Request approval
Open PLM ‣ Changes ‣ Engineering Change Orders and select an ECO.
Click the gear icon next to the ECO name and choose Get Approved.
In the Submit for Approval window, keep the Engineering Change Order request type and click Create Approval Request.
The request opens in Draft. It lists the ECO with its product, label, bill of materials and manufacturing order. The View ECO button returns to the ECO.
Submit the request
Check the ECO listed on the request.
Click Submit. The request moves to To Approve and the approvers can act on it.
Follow the outcome
A ribbon on the ECO shows where its approval stands, for example Waiting for Approvals. To open the requests of the ECO, click the gear icon next to its name and choose View Approval Requests.
Approver: decide and apply
Review and decide
Open the request from Approval ‣ Approval Request ‣ Request, or from the ECO with View Approval Requests.
Review the ECO listed on the request.
Click Approve to sign off, or Refuse to reject the request.
When the last required approval is given, the request moves to Approved. The ECO is not applied yet.
Apply the ECO
Click Mark as Done on the approved request. The request moves to Done and the ECO is applied in the same step.
The ECO is effective and its ribbon shows that it is fully approved. An ECO that was already applied from its own form is left as it is.
The person who marks the request as done must be allowed to read ECOs. Otherwise the request cannot be marked as done and the ECO stays unchanged.
This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software.
The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
