Managing Change Objects
Windchill includes standard change management functionality that is used to manage change at the upper level and lower level of the product structure. Windchill Aerospace & Defense Configuration Items and Design Solutions configuration management includes specialized functionality to handle the needs of the change process at the configuration level.
 |
The standard Windchill change management process is used in the upper and lower levels of the product structure. For more information, see About Change Management.
|
Windchill Aerospace & Defense Configuration Items and Design Solutions configuration level change management includes the following change objects:
• Change Directive—A change to the configuration level of the product structure.
• Change Action—A statement of work required to implement a change directive. The definition of a missing solution needed to fulfill a change.
If necessary, you can create new change directive object types in the Type and Attribute Management utility. If you create a new change directive object type, you must define relationship constraints and specify the appropriate effectivity properties.
The creation of new change action object types is not supported.
Defining Relationship Constraints for Change Objects
Use the Type and Attribute Management utility to define relationship constraints.
The part usage relationship constraints specify the valid parent-child part types for part usage links. By default, the Windchill Aerospace & Defense Configuration Items and Design Solutions delivers a relationship constraint between the out-of-the-box Change Directive object and the out-of-the-box Configuration Item part subtype. If you create new change objects with a type of Change Directive, you must define a relationship constraint that specifies configuration items as the only allowable child type. Likewise, if you create a new part subtype with a Configuration Item structure-level property, you must define a relationship constraint specifying it as the child of a Change Directive object type.
|
|
• Only specify relationship constraints for change directive types that do not have subtypes. Also ensure that change directive types that have subtypes are not instantiable. For example, if change directive type Change Directive 1 has a change directive subtype of Change Directive 1a, then Change Directive 1 should not be instantiable and should not have relationship constraints specified while Change Directive 1a should be instantiable and should have relationship constraints specified.
• If you have the system configured to use both the CI-DS model and the CI-LO-DS model, do not specify a configuration item part type from each pattern as children of the same change directive in the Manage Relationship Constraints window. For example, if a configuration item part type Configuration Item-1 is set up for the CI-DS model, and a configuration item part type Configuration Item (LO)-1 is set up for the CI-LO-DS model, they cannot both be specified as children of the same change directive in the Manage Relationship Constraints window.
Otherwise, columns in the Change Directives or Change Actions table appear with invalid data. See the example below:  |