Action to develop a plan for the tasks required to validate, verify or audit a change.

      Such plans should be based on the decision taken concerning the introduction point and effectivity of the change. It will cover both production embodiment and retrospective embodiment, before or after the

delivery of the product as appropriate. An approved change is planned and scheduled for implementation in all documents, facilities, hardware and software impacted change. The implementation is carried out in accordance with the plan. Implementation of a change involves the release of new or revised configuration documentation including requirements and design information. The implementation may involve changes to operation and maintenance information, build and test information, and sales information (such as catalogues, marketing literature). The new or revised information is identified and released as PCI. The release process should correlate the document revisions to the change or changes incorporated. A common method of disseminating document change is by means of document change notices, which establish a permanent record of specific changes and facilitates distribution.

• Availability: Depth: Industry
• Capability: Depth: Industry
• Spares Inclusive: Depth: MOD
• Traditional: Depth: MOD

• C.1 Sustain Design

• C.1 Sustain Design

• Level 3

• LCIA

C6A1D3D829534A2FB863D6CBD175AB01

738A662ECAD145519E79B128C1B28D29

• Configuration Management Navigation View model

• 03.1.3 Plan Upgrades Activity Insight Model
• 03.4.2 Plan and Initiate Sustainment Tasks Activity Insight Model
• 06.1.4 Perform Configuration Verification Activity Model
• 06.1.4.1 Scope configuration Verification Activity Insight Model
• 06.1.4.2 Plan configuration Verification Activity Insight Model
• 06.1.4.3 Execute configuration Verification Activity Insight Model
• CONFIGURE Activity Model