MCO Overview

The MCO is used to change a Part's Approved Manufacturer List (AML) after a Part is released. The simplicity of the MCO avoids the need to propagate through the entire ECN process for this type of modification. Let's take a look at the Life Cycle Map of a part, while keeping in mind that this process occurs automatically as the Part is modified, reviewed, and released through an MCO

The following is an example of an MCO workflow map:

The MCO is initiated by any user of the Aras Innovator system by filling out required information and attaching necessary files for the MCO. After selecting the Affected Part property the MCO is saved and a workflow is automatically started to assign work and track the change.

During the Prepare Change activity, the CSI reviews all information and makes decisions to submit the AML change. Another possible voting selection for this workflow would be to cancel. For this example we do not vote to cancel and the MCO is updated to the Draft Changes activity. Here a person as the Assigned Creator on the Affected Part is assigned the task of doing the AML change. When the MCO is opened a new button appears on the MCO form to launch the AML editor. This is a special dialog used to edit the AML of Parts that are released. This dialog prevents editing of any other properties or relationships of the affected part. The Assigned Creator launches the AML editor and uses it to make a change and votes to Complete the activity.

The MCO is then transferred to the Change Analyst to review the vendor update during the Initial Review activity. The Change Analyst can then either Reject, promote to a Full Review, or Fast Track Approve the MCO. If the MCO is rejected it passes back to the Assigned Creators to modify and resubmit to the Change Analyst. Fast Track Approve provides a transition to quickly approve the change and release the MCO. Releasing the MCO automatically updates the life cycle state of the affected part. A final option is to vote a Full Review. This is an in-depth review process for formal/informal reviews using other team members and then transfers to the CCB Review activity. After the CCB audit is complete the MCO is released, which also automatically updates the life cycle state of the affected part.

The following table is a summary of the workflow activities and life cycle states of the MCO and may choose to reject changes, Review Changes, and CCB Review activities.