About Change Intent
Change intent provides a proactive way of planning ‘intended’ product changes without requiring the commitment to the next sequential revisions. In the planning stage of the change notice, you can identify the affected objects, and assign the proposed change intent to it. In the implementation stage, the work related to the resulting objects is performed in accordance with the approved affected objects and their assigned change intent. This capability offers a better understanding of the relationship between the affected objects and the resulting objects on a change notice, and easier ways to quickly understand the differences.
You can set change intent for one or more affected object types in the affected objects table. For more information on how to set change intent, see Setting Change Intent.
List of Change Intent Values for All Primary Affected Object Types
The following table lists a set of common change intent values available for affected object types:
|
Affected Object Types
|
Common Change Intent Values
|
||
|---|---|---|---|
|
All Local Affected Object Types
|
• Save As
• Revise
• Reference
• New
• None
|
||
|
All External Affected Object Types
|
• Reference
• None
|
||
|
Parts
|
• Supersede
• Prototype Use
• Production Use
• Service Use
• Obsolete
• Effectivity
• Affected End Item
• One-off Revised
• Unincorporated Change
|
||
|
Document
|
• None
• New
• Effectivity
• Reference
• Revise
• Save As
• One-off Revised
• Unincorporated Change
|
||
|
EPM Document
|
• None
• New
• Reference
• Revise
• Save As
|
For more information about defining mapping rules for the common change intent, see Define Mapping Rules for Change Management.
 |
If a mapping rule is not defined for any affected object types, then a global list of all available change intents is considered.
|
Related Topics