Name |
The name for the engineering change. |
Type |
Engineering type |
Description |
A detailed description for the engineering
change. |
Validation Required |
If Yes, at least one test case must be related to
the engineering change. In the Validate state, any related test
cases must be executed. The engineering change cannot be promoted to
the Formal Approval state until the related test cases have a Pass
status. |
Category of Change |
The category for the change. Values
include:
- Vendor Requirement
- Unassigned
- Product Improvement
- New Product Introduction
- Marketing Requirement
- Facilitate Manufacturing
- Drafting Error
- Cost Reduction
|
Reported Against |
The object this change is reported against.
|
Distribution List |
The member lists to be used as a distribution list
for notifying users. |
Reviewer List |
The route template defined with the Route
Base Purpose of "Review" to be used as a reviewer list. This
includes enterprise and personal route templates. If you do not
select a Reviewer List, the app creates a route with no tasks/persons defined for this
engineering change. You then need to edit that route as
required. |
Approval List |
The route template defined with the Route Base
Purpose of "Approve" to be used as an approval list. This includes
enterprise and personal route templates. If you do not select an
Approval List, the app creates a route with no tasks/persons defined for this
engineering change. You then need to edit that route as
required. |
Severity |
Values are Low, Medium, and
High. |
Policy |
The policy that governs the engineering
change. |