Engineering Change Management Features

You use ECOs to:

Feature	Description
Define who approves the ECO	Defining ECO approvers enables you to: Establish levels of approval so that each member of the first review group must approve the ECO before the next group receives notification. Locate the status of an ECO and review who has approved it and who has yet to approve it. Use electronic mail to notify reviewers and approve ECOs. Create and maintain bill of material data that is associated with the change. Notify reviewers during the approval process. Limit access to the approval records.
Define which items to change	Defining which items to change enables you to: Describe the change. Define the parts and processes that are necessary to implement the ECO. Include multiple parent item or component relationships on the same change order.
Define the change to the routing instructions	Defining the change to the routing instructions enables you to itemize the steps required to make the change.
Define additional detail	Defining additional detail enables you to: Enter into a centralized database supporting data, such as costs, dates, reasons, status, affected work and purchase orders, approval history, and implementation steps. Identify the originator of and reason for the change. Set up user-defined codes (UDCs) to define the reason, status, and disposition of the change order. Attach supplemental information.