Change Orders are the heart of revision management. Duro's simplified Change Order workflow allows teams to quickly and efficiently highlight changes, review and approve them.
Creating a Change Order
To create a new Change Order, users can start from an individual Product or Component, or from the Create Change Orders tile on the dashboard.
Starting from a Product or Component, click on the triangle icon in the upper right and select Add to change order. This will create a new Change Order and auto populate the Products and Components table with the selected Product or Component. To add more Products or Components to the Change Order, use the sidebar on the right side of the page to search and select for them.
Change Order summary
Change Order type
Each Change Order can be one of two types:
ECO (Engineering Change Order) - Used for functional changes
MCO (Manufacturing Change Order) - Used for process or documentation changes
The Name field is used for a terse, yet descriptive title string for the Change Order. It does not have to be unique, but should be able to help an Approver to easily find and understand what the Change Order is for.
A more verbose field to enter details about the Change Order. Typical entries include what has changed, what the change is for, what impacts it may have, any inventory disposition requirements impacted by the change, etc.
The goal is to help an Approver quickly understand the Change Order and its impact, to most efficiently review and approve it.
Products and Components tab
Adding Products and Components
To add more Products and Components to the Change Order, simply use the search box in the upper right of the page and select from the list of results in the sidebar below. You can use shift and ctrl keys when clicking the checkboxes to select multiple entries at once.
The checkbox will have one of the following possible states:
This Product or Component is available and can be added to the Change Order.
This Product or Component has already been added to an open Change Order.
Include parent assemblies
Some teams require that the entire product assembly tree must be included in a Change Order, for any individual Components which have been modified. This allows for all parent assemblies to have their Revision values incremented, together and for the Change Order to be a single atomic revision.
Duro offers a convenient option to automatically add all direct parent Component assemblies and Products for the Components added to the table.
The Revision column in the Products and Components table clearly presents the current Revision value and the new Revision value for each Product and Component, once the Change Order is Approved.
When a Product or Component is promoting its Status value (i.e. DESIGN -> PROTOTYPE, or PROTOTYPE -> PRODUCTION), the new Revision value will default to the new Status value, but can be edited to a new desired Revision value. If the Status value of the Product or Component is not changing, the Revision value will automatically increment to the next appropriate value.
For Products or Components transitioning between Status levels for the current Change Order, there is an option to update the target value. A drop down menu will be available for those rows that are eligible for updating.
Note: After changing the Status level of any Product or Component in the table, the validation rules will be run again to confirm any changes don't cause subsequent issues that need to be resolved before submitting the Change Order for approval.
As Change Orders are a preferred means to share library data with outside suppliers and contract manufacturers, Duro runs a full validation ruleset to help identify any errors or issues that could cause delays or mistakes in a production run. Any issues found will generate a corresponding icon and tooltip in the leftmost column for the Product or Component. See the Validation engine help file for more details.
Approver List tab
This table allows you to add any users with the appropriate Role permissions to review the Change Order and submit a decision to Approve or Reject it.
Use the right sidebar to search for and select which users are to be invited to Approve the Change Order. Once the Change Order is submitted for approval, each user in the table will be sent an email notification with a summary of the Change Order and a link to view the Change Order for review.
Note: The original author of the Change Order will automatically be added to the Approval list and cannot be removed.
Duro makes routing of Change Orders simple and efficient, so teams can focus on what they do best, designing great products - not wasting time administering data. To streamline the Change Order routing process, Duro offers 3 simple Approval Types
- First-In : The first user in the Approval table to submit their decision (Approve or Reject) will set the final resolution for the Change Order. This is useful for minor changes that simply need a clear demarcation in its revision history.
- Majority : The first majority of users in the Approval table to have a consistent decision (Approve or Reject) will set the final resolution for the Change Order. This is useful for when a change needs more visibility across teams and to limit the risk of an important change being approved unilaterally.
- Unanimous : All users listed in the table must have the same decision (Approve or Reject) to set a final resolution. This type is reserved for only the most severe changes.
Notification List tab
All users in the Approval List will automatically be sent an email notification once the Change Order is closed, with the final resolution. In addition to these users, additional people who do not need to review the Change Order or don't have sufficient access permissions, can be added to just be notified with the final resolution.
On the right side panel, existing Duro account users can be added in the same way as done for the Approver List table.
However, in addition, people who do not have a valid Duro account can also be included in the Notification list. This is most commonly used for 3rd party suppliers who need to be notified about the Change Order, but do not necessarily have to be included in the initial review and approval process.
To add 3rd party users, simple enter their email address(es) in the text box on the bottom right side.
Change Order Status
Each Change Order progresses through a series of Status values:
- This Change Order has been created, but not Submitted for Approval, yet.
- This Change Order has been Submitted and is currently open for review by the Approvers.
- This Change Order has been resolved. Either a final Resolution was reached (Approved or Rejected), or an administrator closed the Change Order before the Resolution was made.
Each Change Order has one of 4 possible Resolution values:
- The Change Order has been Closed and Approved by the Approvers.
- The Change Order has been Closed and Rejected by the Approvers.
- The Change Order is still Open and awaiting a resolution by the Approvers.
- The Change Order is still in Draft status, or has been Closed prior to a final Decision was made.