Change Control



38100127635Air Force Life Cycle Management CenterStandard ProcessforChange ControlProcess Owner: AFLCMC/EZSCDate: 21 November 2019Version: 2.500Air Force Life Cycle Management CenterStandard ProcessforChange ControlProcess Owner: AFLCMC/EZSCDate: 21 November 2019Version: 2.5Record of Changes. This page summarizes the changes from each revision of the process to the next. Revision numbering starts with 1.0. Minor changes are annotated by changing the second digit, i.e., the first minor change after the basic document would be recorded as “1.1.” Major changes are annotated by changing the first digit, i.e., the first major change after release of the basic document would be numbered as “2.0.” Example:Record of ChangesVersionEffective DateSummary1.06 March 2014Standard process was reviewed and approved by S&P Board on 6 Mar 20142.019 November 2015This process was updated to include further definition as obtained from lessons learned since initial implementation and approved by S&P Board on 19 Nov 15.2.122 January 2016Administrative change - corrected format issues with the ToC and process flows2.28 April 2016Changed title of document from Configuration Control to Change Control2.319 April 2017Administrative updates. Incorporated reference to GEIA-HB-649A, Configuration Management Handbook Implementation Guide. Reviewed & approved by S&P Board 20 APR 2017.2.412 July 2018Administrative updates. Updated AFMCI 21-402 reference; applied page numbers to attachments. Approved by S&P board on 12 July 2018. 2.521 November 2019Terms updated due to publication of EIA-649C include: Class I and Class II change to Major and Minor and Variances; Forms updatedContentsContents TOC \o "1-3" \h \z \u 1.0Description. PAGEREF _Toc441216480 \h 42.0Purpose PAGEREF _Toc441216481 \h 53.0Entry/Exit Criteria and Inputs/Outputs PAGEREF _Toc441216482 \h 53.1Entry Criteria PAGEREF _Toc441216483 \h 53.2Exit Criteria PAGEREF _Toc441216484 \h 63.3Inputs. PAGEREF _Toc441216485 \h 63.4Outputs. PAGEREF _Toc441216486 \h 64.0Process Workflow and Activities. PAGEREF _Toc441216487 \h 64.1Suppliers, Inputs, Process, Outputs, Customers (SIPOC) Table – Attachment 1 PAGEREF _Toc441216488 \h 64.2Process Flowchart PAGEREF _Toc441216489 \h 74.3Work Breakdown Structure (WBS) – Attachment 3 PAGEREF _Toc441216490 \h 95.0Measurement. PAGEREF _Toc441216491 \h 136.0Roles and Responsibilities. PAGEREF _Toc441216492 \h 147.0Tools. PAGEREF _Toc441216493 \h 178.0Training. PAGEREF _Toc441216494 \h 199.0Definitions, Guiding Principles and/or Ground Rules & Assumptions. PAGEREF _Toc441216495 \h 1910.0References to Law, Policy, Instructions or Guidance. PAGEREF _Toc441216496 \h 21SIPOC Tables (Attachment I)Major Engineering Change ……………………………………………………………………. 22 Variance and Temporary Modification…………………………………………………………. 23Process Flow Charts (Attachment II)WBS 3.1 Identification and Classification of Engineering Changes……………………24WBS 3.2 Major Engineering Changes…………………………………………………..25WBS 3.3 Major Variances……………………………………………………………….27 WBS 3.4 Temporary Modifications……………………………………………………...29WBS Table (Atttachment III)WBS 3.1 Identification and Classification of Engineering Changes…………………….31WBS 3.2 Major Engineering Changes…………………………………………………..38WBS 3.3 Major Variances……………………………………………………………….55 HYPERLINK \l "ModWBS" WBS 3.4 Temporary Modifications……………………………………………………...71Description. Configuration Control (synonymous with Change Control) is the function which is perhaps the most visible element of Configuration/Data Management (C/DM). It facilitates the systematic proposal, justification, evaluation, coordination, approval or disapproval of configuration changes and the implementation of approved configuration changes to a Configuration Item (CI) along with the corresponding configuration baseline documentation data. This process document describes the process and documentation to maintain configuration baselines by applying change control as defined in MIL-HDBK-61A, Section 6, Configuration Control. Government change control begins when the technical baseline is established, via government approval and control, and continues through the life cycle of the item. There are three distinct configuration baselines employed: Functional, Allocated and Product as further defined in MIL-HDBK-61A, Section 5.5 and DoDI 5000.02, Enclosure 3, paragraph 8, as well as EIA-649C and GEIA-HB-649A. The organization requesting a change to an approved technical baseline, in accordance with an approved Modification or Engineering Change Proposal (ECP), or approval to violate a baseline in accordance with an approved Variance, will submit a Change Request (CR) to the program office. The program office will validate the need and process the approval to move forward with the formal change. The requesting organization may be the contractor, the using command or the program office. Once validated, a formal request will be developed and provided as a Change Action (CA) to the program office for evaluation. When the government is the Current Document Change Authority (CDCA), the requested change will be reviewed by the program Configuration Control Board (CCB) members for recommended approval/disapproval of the change action. A recommendation will be presented to the CCB Chairperson to approve or disapprove the requested change. The CCB decision will then formally be provided to the contractor by the contracting officer. When an organic change is issued the CCB decision will be provided to the modification center. All changes shall be tracked from initiation through implementation by appropriate stakeholders and evidence of implementation provided to the Configuration Manager for closure of the CA. Records pertaining to the change and its implementation will be archived after CA closure.Purpose Change control is a necessary function in all phases and types of acquisition and sustainment programs. The creation of the AFLCMC brought various ways of accomplishing changes under one center. Creating a standard process that can be used by each AFLCMC organization through the life cycle of the product will provide basic consistency to maintain and control documented baselines. This standard process is mandatory for all AFLCMC organizations. Organizations may utilize local and/or organizational Configuration Change Control processes as long as they adhere to this standard process. Organization processes shall be coordinated through AFLCMC/EZSC to ensure there is no departure from this standard process.Entry/Exit Criteria and Inputs/OutputsEntry CriteriaAn approved Functional, Allocated and/or Product configuration baseline.A recommended change or variance to/from the approved baseline. Changes that enter the process can include: A proposed temporary modification for a short-term operational mission requirement change (T1) along with a completed AF Form 1067, Modification Proposal, requesting approval, or a change to the developmental and/or test capabilities (T2). Orginal Equipment Manufacturers (OEMs) can also request a T2 modification via CDRLs. See AFI 63-101/20-101 and AFI 10-601 for application. A proposed permanent change to the technical baseline. An AF Form 1067 and/or Capability Development Document (CDD) in accordance with (IAW) AFI 10-601, can also be used as a vehicle to generate a proposed permanent change package that will then require the submittal of a Change Action. See AFI 63-101/20-101 for application. Permanent Modifications are to be converted to ECPs or equivalent Change Action. An RFV is used to temporarily depart from a particular requirement or particular requirements of a specific item’s approved configuration documentation for a specific number of units and/or a specified period of time. Variances do not change the approved documented baseline; rather, they document acceptance of an item that does not comply with the approved baseline documentation and does not significantly degrade the performance of the item. Variances are requested by contractors prior to, during, or after item manufacture. A variance requested during or after manufacture was formerly called a waiver and those requested prior to manufacture were formerly called deviations. EIA-649 and GEIA-HB-649A guidance uses the term “variance”, although MIL-HDBK-61A and legacy processes may still use waiver and or deviation. Engineering Order AF Form 3925 process IAW AFMCI 21-401 is also an acceptable method to address the product baseline changes that are made during sustainment. Additionally, an AFTO Form 252, IAW TO 00-5-3 may be utilized as an entry criteria to the process for sustainment programs. Exit CriteriaChange Board Chair decision to disapprove a change request, ECP, temporary change proposal (T1 or T2), or RFV. Direction to process a ECP in accordance with the internal ECP procedures because an approved technical baseline would not be affected by the change. Approved evidence of change implementation for previously approved Major changes.Approved evidence of corrective action on a product previously granted a variance or removal of a temporary change to return all units of product to compliance with documented product baselines.Inputs. CR. CR validation and classification and notification to originator. Formal CA package.Outputs. A CCB decision documented on an AFTO872, CCBD or equivalent; AF Form 1067, Modification Proposal or equivalent; AFMC Form 244, T-2 Modification Configuration Control Board Directive. Procuring Contracting Officer (PCO) Letter, contract modificationArchived records of activities related to the change or other documents as required.Process Workflow and Activities.Suppliers, Inputs, Process, Outputs, Customers (SIPOC) Table – Attachment 1Description. SIPOC Tables identify Suppliers, the Inputs they provide to a process step/activity, the Process Step/Activity that receives those inputs, the Outputs of those activities, and the Customers of those outputs. As such, they provide a summary of major process activities that will be necessary to produce the desired products and permit exiting the process. The process activities can be read in order down the center column of the table. They assume success at each step and are an easy to understand picture of the process in tabular form. The party responsible for performing the process step in one row becomes the supplier in the next, the outputs of their process steps become the input on the next row, and the customer at the end of one row becomes the party responsible for performing the process activities shown in the next row. In Attachment I, two different tables are provided – a separate one for Major engineering changes and another for Variances and Temporary Modifications. Purpose.The simplicity of SIPOC tables provides an easy way to identify gaps and disconnects in a process. Even when none exist, SIPOCs are a good place to start when considering a potential improvement to a process and are therefore a vital component of Continuous Process Improvement. By showing interactions between suppliers, interim products, and customers, they can help in performing what-if analyses on a process by identifying the ramifications of a process change that may be under consideration.SummaryAn abbreviated combined version of the Configuration Control SIPOC Tables is shown below. For complete versions as described above, click here or see Attachment I to this attachment.SUMMARY SIPOC TABLE SuppliersInputsProcess ActivitiesOutputsCustomersContractor, Using Command, Program OfficeInformal CRValidate and Classify CR Validated/Classified CRProgram OfficeProgram OfficeRFP Major Changes Only Prepare and Formally Submit CA PackageCA PackageResponsible Configuration ManagerResponsible Configuration ManagerDistributed CAReview/Comment on CA; Provide RecommendationComments/ RecommendationCCBCCBAuthority to ProceedMonitor ImplementationEvidence of CompletionCognizant Configuration ManagerProcess Flowchart. Changes to the configuration baseline can be accomplished in various ways. Since different types of changes use different forms and documents, separate process flows have been created to reflect the differences. Process Flow 3.1, Identification and Classification of Engineering Changes, shows a series of decisions leading to the determination of whether a CR is valid and what type of change it would create.Process Flow 3.2, Major (Major )Engineering Changes, is to be used when Flow 3.1 validates a CR and identifies the change as a Major Change.Process Flow 3.3, Major Variance, is to be used when Flow 3.1 validates a CR and identifies the change as a Major Variance.Process Flow 3.4, Temporary Modification, is to be used when Flow 3.1 validates a CR and identifies the change as a Temporary Modification.Process Flows 3.2.8.x, 3.3.7.x, and 3.4.7.x provide additional notional information regarding external processes with which each of the above process flows interact. They aren’t part of the Change Management Process but are provided to help explain the activities that need to occur as part of non-C/DM processes in order for a change to be fully implemented. Each of the C/DM process flows has a point of departure leading to these external processes and return therefrom.Summary. A summary of a success-oriented Change Control Flowchart without decision points and feedback loops is shown below. In addition to leaving out feedback loops for incorrect and incomplete action, the summary also leaves out WBS designators in order to conserve space. For complete versions as described above, click here or see Attachment II to this Attachment.-318052149418SUMMARY FLOWCHART00SUMMARY FLOWCHARTWork Breakdown Structure (WBS) – Attachment 3. The WBS provides details for the flowchart activities. It’s the most detailed of the three Process Workflows and Activities, explaining how each of the process steps shown on the flow charts is to be accomplished. WBS numbers correspond to task numbers shown on the detailed flow charts.Summary. A summary of the Configuration Control WBS is shown beginning on the next page. It explains each of the process steps shown on the Summary Flowchart. In the flowchart the WBS numbers have been left out in order to conserve space. They are included in the complete flowcharts in Attachment II. For the complete WBS click here or see Attachment III to this Attachment.WBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescription3.?- Configuration Control ProcessIdentified Need for Change715010-2984500This process will be used to ensure that all technical baseline changes are developed and managed in a controlled environment from the time the need for a change is identified until the change has been dispositioned and implemented.3.1?- Identification and Classification of Engineering ChangesIdentified Need for ChangeThis sub-process will be used to validate an identified need for a change and determine, for valid needs, the type of change and its classification based on established parameters. Step 3.1.5 is essentially where all valid changes are categorized. The rest of the flowchart shows how to respond based on the determinations made in step 3.1.5. All of the decisions shown need to be consciously determined in order to ensure that the correct flow is selected for subsequent process performance.3.1.53.1.5.1, 3.1.5.3, 3.1.5.6???- Validate and Move Forward, ID Type and Classification and route to appropriate sub-processIf the determination is that the CR is valid and of high enough priority to move forward with its implementation, the Responsible Technical and Configuration Management Authority are to determine its type and classification. Classifications and their Types include Major or 2 Engineering Changes, Major or Minor Deviations, or Permanent or Temporary Modifications. Contract Change Proposals (CCP) are not Engineering changes and are to be forwarded to those who own the CCP process (usually the Program Office’s Contracts Management organization). See WBS 3.1.5.7. If the determination is that the CR will result in a Major Engineering Change in accordance with established criteria, the CR is to be forwarded to the Major Engineering Change sub-process (WBS 3.2). If a determination is that the change is a Major Variance, the CR is to be forwarded to the Variance sub-process (WBS 3.3), and if a Temporary Modification to the Temporary Modification sub-process (WBS 3.4)3.2- Major Engineering ChangesDetermination of Need for a Major Change68896113889This sub-process will be used to process Major Engineering changes through implementation and archive of official records.3.2.11.2- Request ProposalUpon being notified of the Cognizant Authority’s determination that a Major Engineering Change project should be implemented, the Program Office will request a proposal (WBS 3.2.1.1) for implementing the change. 3.2.4, 3.3.1,3.4.11.3,2.2- Prepare/ submit ECP, RFV, or Request for a Temporary Modification The contractor will respond to an RFP with a formal proposal (WBS 3.2.4.1) or if the determination is that a Major Variance is required, a Request for Variance (WBS 3.3.1.1) or if a Temporary Modification is needed, the CR Originator will prepare and submit a Form 1067 or equivalent (WBS 3.4.1.1). Upon receipt, the tracking system will be updated with delivery information.WBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescription3.2.2, 3.3.2, 3.4.2/ 3.2.3, 3.3.3, 3.4.3- Log RFP Release, receipt of RFV, or Request for Temporary Modification into tracking system; - Monitor Progress, Update Tacking RecordA Change Management Tracking System will be used to monitor the project against the schedule identified in the RFP. The Tracking Record (WBS 3.2.2.1, 3.3.2.1, or 3.4.2.1) will collect information from the document artifacts created throughout the process. This information will be used to report the required Quality and Timeliness metrics after a project is closed. 3.2.5, 3.3.4, 3.4.41.4, 2.3- Distribute for ReviewECPs, RFVs, and Requests for Temporary Modifications will be distributed to cognizant team and functional organizations for Review/Comment/Recommendations. This may include external stakeholders such as DCMA, Test organizations, etc.3.2.6, 3.3.5, 3.4.5/ 3.2.6.2, 3.3.5.2, 3.4.5.21.5, 2.4- Review/ Comment; - Send to BoardStakeholders will review the proposals/requests, providing comments and recommendations regarding the project. The Tracking System will be updated to reflect comments and recommendations received so that timeliness of the review process and quality of the proposal/request can be determined for reporting metrics. If reviewing organizations believe the proposal is ready to be sent to the CCB and/or Airworthiness Board(s), they are to notify the Responsible Configuration Manager/Change Board Secretariat, who will schedule a board and put the change on the agenda.WBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescription3.2.7, 3.3.6, 3.4.61.6, 2.5- BoardA Configuration Change and/or Airworthiness Board, with membership composed of senior management from the program office and additional interested parties to include contractor management as appropriate, will be convened to review proposed Major changes and comments thereto that make it through the review stage. The Board Chair will have final authority to render a decision after consideration of comments and recommendations from reviewers and board members. Possible decisions can include returning the proposal to the contractor for further revision, approving the proposed change as is or with minor revisions agreed to at the board, or rejecting the proposal outright. The disposition will be documented on an appropriate form such as an AFTO872, Configuration Control Board Directive, signed by the board chair to formally document the decision, and the Tracking System updated to revise metrics. Further details on Board processes should be documented in Board Charters and processes that describe membership, other interested stakeholders, scheduling, project dispositioning, roles and responsibilities, etc.3.2.7.1, 3.3.6.1, 3.4.6.1- Approve Change as is or with minor revisions agreed to at the boardWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionManagement will notify stakeholders of the status and update the tracking system.3.2.8, 3.3.7, 3.4.71.7, 2.6- Exit to External ProcessesAs described under WBS 3.2.7.1, 3.3.6.1, and 3.4.6.1, once implementation of a change is approved by a change board, several other processes are triggered, suspending the change process and its collection of metrics data until evidence of change implementation is received by Configuration Management, at which time the project can be closed. External processes that intersect with the change process are discussed under 3.2.8.x, 3.3.7.x, and 3.4.7.x and subs.Once the external processes have completed their actions, the return to the Change process will occur with evidence that the engineering data has been updated (3.2.8.1, 3.3.7.1, and 3.4.7.1) and the Status Accounting Process can now take over. 3.2.9, 3.3.8, 3.4.81.8, 2.7- Close Project, Collect and Report Metric Data using the Tracking Record Upon receipt of official evidence of project implementation from external processes, Configuration Management will notify stakeholders, update the tracking system to close the project, and archive official records. Final metrics will report the time from receipt of the approved completion certificate to project closure and records archive.Measurement. Efficiency and effectiveness of each of the sub-processes (WBS Numbers 3.1, 3.2, 3.3, and 3.4) will be measured and reported to AFLCMC with its own set of metrics to show Cycle Time and Quality.In addition to the above metrics, AFLCMC/EZSC will also track and review the following: Variance Approvals/Disapprovals – This metric will measure the number of Variance requests approved, percentage recurring and how many and type of items affected with each request. Approved Variances that result in a follow-on specification change (ECP) will also be identified. T1/T2 Approvals – This metric will measure the number of T1/T2 Modifications approved, number of units affected, period of time requested and when the units were returned to original baseline. (Note: Quick Reaction Capability Acquisition Decision Memorandum fulfills AF Form 1067 parts I, II, III and V; part IV shall be documented by the Program Manager).Process Evaluation. Metrics will be evaluated to determine the amount of time it takes for each change and type. The information will be used to identify opportunities for improvement to ensure that cycle times specified in the WBS section of the process are met or, when deemed appropriate, adjusted. The quality and completeness will be measured to determine how to ensure that quality products are submitted without need for resubmittal. Variances will be evaluated for number submitted, number of items affected and trends that require immediate attention. The metric will be used to evaluate if repeat Variances are being approved and why. Roles and Responsibilities. AFLCMC/EZSC Configuration/Data Management Branch (Process Owner):Manages, recommends and coordinates all changes to this process.Leads and/or assigns personnel to work on any process improvement and change events related to this process.Evaluates metrics from a Center perspective.Provides Center Change Control training, guidance and expertise.Reviews/inspects local/organizational processes to ensure they adhere to this standard.Responsible Technical Authority: Reviews CR and Identifies type and classification.Requests CA for validated CR if one hasn’t been received.Can serve as the CCB Chairperson when delegated from the Program Director in accordance with the established board charter.Can serve as the Project Engineer for the product addressed by a CA when not serving as the CCB Chair.Directorate Configuration Management Lead: Enforces adherence to this process within the programs in their directorate to include collection of data for development of metrics.Reviews quarterly metrics for programs within their directorate to identify opportunities for improvement. Can serve as the lead Program Configuration ManagerCan serve as the Responsible Configuration Change Manager and/or board secretariat as required. Program Director: Serves as Configuration Change Authority (CCB Chairperson). He/she may delegate responsibility to the Deputy Director or Chief Engineer as defined in the CCB Charter. May review formal CA and provide relevant comments and recommendations to responsible project manager and/or engineer.Can serve as responsible Project Manager when not serving as the CCB Chair or delegate responsibility. CCB Chairperson:Using the recommendations and inputs of the reviewing members and advisors, approves or disapproves the CA. Single change authority for the program. Issues disposition via an AFTO872, Configuration Control Board Directive, or equivalent; AFMC Form 243, Temporary Release for Flight Certificate; AFMC Form 244, T-2 Modification Configuration Control Board Directive; AFMC Form 272, Physical Configuration Inspection, AFMC Form 273, Final Release for Flight Certificate. (See AFMCI 21-126, Temporary 2 (T-2) Modification of Aerospace Vehicles).Designates, in writing, the CCB primary and alternate membership. Lead Program Configuration ManagerEnforces adherence to this process within their programCan perform duties of the Responsible Configuration Change Manager and/or board secretariat as requiredMaintains Configuration Control of, and manages, documented baselines, CCB Charter, and CCB primary and alternate CCB membership lists for their assigned program(s) Maintains program office local/organizational Change Control process which adheres to this standard process. Coordinates with AFLCMC/EZSC AW C/DM on Military Type Certificate/Military Flight Release process. See AWBs located on the Airworthiness site. () Configuration Change Manager (CM): Supports responsible Technical Authority to identify CR type and classification.Can perform duties of the Lead program Configuration Manager.Can perform CCB Secretariat duties. Receives and distributes CA.Logs and tracks each CA from receipt through implementation – monitors progress, updates the tracking record, collects metrics for the Directorate Configuration Management Lead, and keeps stakeholders apprised of status. Reviews the CA under CCB consideration, provides comments to the project lead and provides a configuration/data management (C/DM) recommendation to CCB.Prepares a formal technical evaluation for C/DM related proposal items, which will form the basis for negotiation. Represents C/DM during contract negotiations as needed. Maintains official list of board membership and ensures required functional organizations are represented at CCB by appropriate members.Verifies responsible change implementation monitor ensures changes are correctly incorporated.Verifies responsible change implementation monitor signs evidence of completion, including temporary modification expiration/de-modification, or extension of a temporary modification. Supports engineering in providing artifacts for Airworthiness (AW) considerations and Airworthiness Board (AWB) action for reportable/non-reportable changes as it relates to modifications under the change control process. CCB Secretariat: Verifies all documentation is ready for CCB.Schedules and conducts any pre-board reviews/activities to develop CCB recommendation prior to CCB. Generates and distributes official board agenda to notify all participants. Administers the CCB and obtains CCB Authority decision and signature. Generates and distributes board minutes and maintains documented records of the CCB.Project Manager/Engineer: Works with contractor personnel to develop CA.Develops CA package when CR has been validated and is not covered by a contract. Initiate Requests for Proposals (RFP), through contracting officer, to contractor to develop ECP. Adjudicates comments to CA.Works with CM to prepare documentation for CCB.Resolves issues/comments prior to boarding the CA. Prepares CCB presentation. Can serve as Change Implementation Monitor.Can serve as responsible Technical Authority for changes affecting assigned products. Using Commands:When recommending Temporary Modifications, develop, IAW AFI 63-101/20-101, Modification Management, a completed AF Form 1067 package for approval/disapproval.Review CA, provide comments, recommend approval/disapproval and participate in CCB.Can serve as Change Implementation Monitor.Functional Membership (CCB Members): Functional membership will consist of Engineering, Safety, Configuration, Logistics, Finance, Contracts, Test, Training and others, as needed, and will be designated as members of the program office’s CCB membership. Review CA and provide comments and recommendations to change manager for inclusion into CCB documentation.Attend CCB and concur/non-concur on CCB Chairperson decision. Chief Engineer:Ensure all changes address OSS&E and the OSS&E Baseline Document has been documented with required update(s). Ensures all changes address potential AW impacts.Can act as responsible Technical Authority.Can serve as Configuration Change Authority (CCB Chair).Contracting Officer: Recommends approval/disapproval of CA. Provides contractor initial notification of CCB results. Negotiates contracts for changes and consideration for Variances to requirements, to include implementation and corrective action plans.Issues contract modification to contractor.Maintains all contractual records/documentation related to changes. Change Implementation Monitor:Monitor Change implementation, corrective action, and modification removal.Sign evidence of completion of change incorporation/corrective action/modification removal and forwards to Configuration Change Manager.Tools. MEARS (Multi-User ECP Automated Review System) is a low-cost, government-owned, automated tool that is available to handle ECP processing. Contact the AFLCMC/EZSC Data Management point of contact for more information. Other third-party automated tools developed and owned by contractors.The Configuration Management SharePoint site is available for sharing configuration management documents, i.e., training documentation, process documents, etc. Streamlining and Standardization Information System (ASSIST). A database system for DoD-wide standardization document information. ASSIST is located at the Document Automation and Production Service (DAPS), Philadelphia, PA. ASSIST-Online provides web-based access to digital documents on the ASSIST database. ASSIST is the official source of DoD specifications and standards. Also, ASSIST provides online, interactive listing of source documents and Data Item Descriptions (DID) that DoD has approved for repetitive contractual application in DoD acquisitions and those DoD has cancelled or superseded. ASSIST can be accessed at , Table 6-1, Activity Guide: Configuration Control Process Evaluation Checklist. Various Prime Contractor Website and database applications provided for access to submittals of documentation required by CDRLs.Training. C/DM Training/Certification Requirements. C/DM personnel, as identified in para 6.6, 6.7, and 6.8 are responsible for executing this standard process and are required to be APDP (Acquisition Professional Development Program) certified. C/DM personnel will be responsible for meeting elements in the C/DM Training Plan. AFLCMC/EZSC manages the standard C/DM Training Plan as implemented by the supervisors of all C/DM personnel. General training opportunities for those personnel involved in this process (other than C/DM personnel) is as follows:SYS 028, Intro to Configuration Management (AFIT). LOG 204, Configuration Management (DAU). AFLCMC C/DM Forums and local training forums (e.g., Focus Week training).Additional Reading: Current versions of MIL-HDBK-61, EIA-649, EIA-649-1, GEIA-HB-649A, AFI 63-101/20-101 and AFI 10-601Tool Training: MEARS tool training or local/organizational Change Control tool, as applicable. Definitions, Guiding Principles and/or Ground Rules & Assumptions. AF Form 1067, Modification Proposal – Documents the requirements for temporary or, in conjunction with ECPs, permanent modifications to existing systems (in theater). (AFI 63-101/20-101).AFMC Form 243, Temporary Release for Flight Certificate – The AFMC Form 243 is issued for no more than 180 days for an aerospace vehicle, due to incomplete installation or documentation of a T-2 modification. AFMC Form 244, T-2 Modification Configuration Control Board Directive – The document that records the approval/disapproval decision of the CCB for a temporary modification. AFMC Form 273, Final Release for Flight Certificate – The AFMC Form 273 is issued to formally release an aerospace vehicle for mission use based upon sufficient engineering and flight tests to ensure safe flight within a specified envelope. Final flight release implies completion of the modification installation and documentation or de-modification process. AFTO872, Configuration Control Board Directive – A document that records approval/disapproval decision of the CCB and provides the direction to the contracting activity. Allocated Baseline – The approved allocated configuration performance-oriented documentation for a work product or configuration item to be developed. It describes the functional and interface characteristics that are allocated from those of the higher-level CI and the verification required to demonstrate achievement of those specified characteristics.Baseline – An approved description of the attributes of a product, document, or set of documents at a point in time, which serves as a basis for defining change, for conducting verifications, and for other management activities. See: Allocated Baseline (ABL), Functional Baseline (FBL), and Product Baseline (PBL). CCB – A chartered board composed of representatives who recommend approval or disapproval of proposed engineering changes to, and proposed Variances from, a configuration item’s current approved configuration documentation. CCB Authority/Chairperson – The person who has the authority to approve/disapprove changes and chairs the P – A contract change that has the potential to impact contract cost, schedule or performance and no-cost or pre-planned and programmed execution B Members – Individuals that have been designated as CCB representatives to review and recommend approval/disapproval to requested changes. They will be designated in writing by the CCB Chairperson and will attend the CCBs.CDCA – (Current Document Change Authority) is the authority currently responsible for the content of a drawing, specification or other documents and which is the sole authority document change approval. CDCA may be a government activity or a contractor, and the authority may be transferred. Change Action (CA) – Formal developed change package after identification of CR type and classification to be dispositioned by the CCB. Can be an ECP, RFV, organic temporary change action (AF Form 1067) or equivalent. Change Manager – The Configuration Manager assigned responsibility for a particular CA.Change Request (CR) – Means by which a change is proposed, described, justified and submitted to the Responsible Technical Authority to have its type and classification validated. Major ECP – A Major ECP (also referred to as a Major change) is an ECP that proposes a change to the approved documented configuration baseline. It affects any physical or functional requirement documented in the approved baseline. (See MIL-HDBK-61A for complete criteria).MajorI ECP – A MajorI ECP (also referred to as a Minor change) is any change to the approved documented configuration baseline that has little or no significant impact and does not fit the criteria for a Major ECP.Configuration Baseline – The approved configuration of a product, at a specific point in time, which serves as a basis for defining change.Configuration Item (CI) – Any hardware, software, or combination of both that satisfies an end use function and is designated for separate configuration management. Configuration items are typically referred to by an alphanumeric identifier which also serves as the unchanging base for the assignment of serial numbers to uniquely identify individual units of the CI. (See also: Product-Tracking Base-Identifier.) Note: The terms “CI” and “Product” are identified as aliases in EIA 649 and are used interchangeably within this document. Configuration Management – A technical and management process for establishing and maintaining consistency of a product’s functional and physical attributes with its requirements, design and operational information throughout its life. ECP – An ECP is the management tool used to propose a configuration change to an approved Configuration baseline. Functional Baseline – The approved functional configuration documentation or work product describing a system’s or top-level configuration item’s performance. This includes its functional, interoperability and interface characteristics as well as the verification required to demonstrate the achievement of those specified characteristics.Modification – A modification is an alteration to the form, fit, function or interface of an in-service Air Force configuration item. Permanent Modification – Changes the configuration of an asset/software for operational effectiveness, suitability, survivability, service life extension and/or reduces ownership costs of a fielded weapon system, subsystem or item. Permanent modifications shall only be accomplished in response to an approved AF Form 1067, Capability Requirements Document and will require a change to the documented configuration baseline via an ECP.Product Baseline – The approved technical documentation and work product (i.e., “build-to” and “code-to” items such as specifications, drawings, software code, Interface Control Documents, and related materials) which describes a CI during the production, fielding/deployment and operational support phases of its life cycle.Project Manager/Project Engineer – The individual that will process a requested change through CCB.Responsible Technical Authority (RTA) – The Chief Engineer or delegate assigned to the product addressed by a CR.Responsible Configuration Change Manager – The Configuration Manager who has configuration management responsibility for the product affected by a proposed change.Temporary Modification – Temporary Modifications are not managed as an acquisition program. The baseline and additional documentation will be attached to the AF Form 1067 for review and subsequent approval. Temporary Modifications are to be removed in accordance with an approved Removal Plan that is part of an AF Form 1067.T-1 Modification – A T-1 modification changes the configuration of an item in order to satisfy short-term operational mission requirements by adding, modifying or removing hardware and/or software components or capabilities in a manner that provides an immediate operational benefit. The T-1 Modification proposal shall specify the number of units to be modified, duration of installed T-1 Modification and plans for removing the modification or converting it to a permanent modification. All temporary modification projects will close out when they are replaced by permanent modifications or removed from the host system or component as specified in the approved AF Form 1067. T-2 Modification – A T-2 modification is used to evaluate, demonstrate or exercise the technical performance, operational effectiveness and/or the operational suitability of developmental and/or test material capabilities. T-2 modifications are also used to install and operate Test and Evaluation (T&E) specific support equipment, instrumentation and data recording equipment, etc., on T&E assets. Variance – A specific written authorization to depart from a particular requirement(s) of an item’s approved configuration baseline for a specific number of units and/or a specified period of time. The documented configuration baseline will not be changed.References to Law, Policy, Instructions or Guidance. AFI 10-601, Operational Capability Requirements Development AFI 63-101/20-101, Integrated Life Cycle Management AFMCI 21-126, Temporary 2 (T-2) Modification of Aerospace VehiclesAFMCI 63-1201, Implementing Operation Safety Suitability and Effectiveness (OSS&E) and Life Cycle Systems Engineering (LCSE)DODI 5000.02, Operation of the Defense Acquisition SystemEIA-649, National Consensus Standard for Configuration ManagementEIA-649-1, Configuration Management Requirements for Defense ContractsGEIA-HB-649A, Configuration Management Handbook Implementation GuideMIL-HDBK-61A, Configuration Management Guidance1917136484Attachment I4000020000Attachment ISIPOC TABLE -- MAJOR CHANGESSuppliersInputsProcess Activities*OutputsCustomersContractor, Using Command, Program OfficeInformal CR1.1 Validate and Classify CR Validated/ Classified CRProgram OfficeResponsible Technical Authority and Configuration ManagerValidated CR Classified as a Major Change1.2 Prepare Request for Proposal (RFP) RFPContractorProgram OfficeRFP 1.3 Prepare and Formally Submit CA Package (ECP)CA PackageResponsible Configuration ManagerContractorCA Package1.4 Distribute CA for ReviewCA Tracking Record (to be updated as appropriate – not further reflected below)All StakeholdersDistributed CA PackageResponsible Configuration ManagerDistributed CA1.5 Review/Comment on CA; Provide RecommendationComments/ RecommendationCCBAll StakeholdersRecommendation to Proceed with Change 1.6 Board ChangeDisposition – authority to proceed (e.g., CCBD)Change Implementing Organization (Depot, Field, Contractor, etc.)Change Monitoring Organization (DCMA, Contractor, Using Command, Program Manager, Contracting Officer)CCBAuthority to Proceed1.7 Monitor ImplementationEvidence of CompletionCognizant Configuration ManagerChange Monitoring Organization Evidence of Completed CA1.8 Close Project & Archive RecordsArchived Records of Change ProcessAll Stakeholders*Note: Numbers refer to SIPOC Identifiers listed in the WBS TableSIPOC TABLE -- VARIANCES AND MODIFICATIONSSuppliersInputsProcess Activities*OutputsCustomersContractor, Using Command, Program OfficeInformal CR and/or Change Action Package (CA)2.1 Validate and Classify CR and/or CA Validated/ Classified CR/CACR InitiatorResponsible Technical Authority and Configuration ManagerValidated/ Classified CR Classified as a Major Deviation or Temporary Modification2.2 Prepare/Update and Formally Submit CA PackageCA PackageResponsible Configuration ManagerCR InitiatorCA Package2.3 Distribute CA for ReviewCA Tracking Record (to be updated as appropriate – not further reflected below)All StakeholdersDistributed CA PackageResponsible Configuration ManagerDistributed CA2.4 Review/Comment on CA; Provide RecommendationComments/ RecommendationCCBAll StakeholdersRecommendation to Proceed with Change 2.5 Board ChangeDisposition -- authority to proceed (e.g., CCBD)Change Implementing Organization (Depot, Field, Contractor, etc.)Change Monitoring Organization (DCMA, Contractor, Using Command, Program Manager, Contracting Officer)CCBAuthority to Proceed2.6 Monitor Implementation or Corrective ActionEvidence of CompletionCognizant Configuration ManagerChange Monitoring Organization Evidence of Completed CA2.7 Close Project & Archive RecordsArchived Records of Change ProcessAll Stakeholders*Note: Numbers refer to SIPOC IDentifiers listed in the WBS Table344613416232Attachment II00Attachment II803910110795LINKS TO WBS TABLE HYPERLINK \l "WBS311" 3.1.13.1.23.1.33.1.43.1.53.1.5.13.1.5.23.1.5.33.1.5.43.1.5.53.1.5.63.1.5.7LINK TO TABLE OF CONTENTS0LINKS TO WBS TABLE HYPERLINK \l "WBS311" 3.1.13.1.23.1.33.1.43.1.53.1.5.13.1.5.23.1.5.33.1.5.43.1.5.53.1.5.63.1.5.7LINK TO TABLE OF CONTENTS770572520320LINKS TO WBS TABLE HYPERLINK \l "WBS321" 3.2.13.2.23.2.33.2.43.2.5 HYPERLINK \l "WBS326" 3.2.63.2.6.13.2.6.23.2.73.2.7.13.2.7.23.2.7.33.2.9_______LINK TO TABLE OF CONTENTS0LINKS TO WBS TABLE HYPERLINK \l "WBS321" 3.2.13.2.23.2.33.2.43.2.5 HYPERLINK \l "WBS326" 3.2.63.2.6.13.2.6.23.2.73.2.7.13.2.7.23.2.7.33.2.9_______LINK TO TABLE OF CONTENTS756285020320LINKS TO WBS TABLE HYPERLINK \l "WBS328x1" 3.2.8.x13.2.8.x23.2.8.x33.2.8.x43.2.8.x53.2.8.x63.2.8.x73.2.8.x83.2.8.x93.2.8.x10LINK TO TABLE OF CONTENTS0LINKS TO WBS TABLE HYPERLINK \l "WBS328x1" 3.2.8.x13.2.8.x23.2.8.x33.2.8.x43.2.8.x53.2.8.x63.2.8.x73.2.8.x83.2.8.x93.2.8.x10LINK TO TABLE OF CONTENTS792480010795LINKS TO WBS TABLE HYPERLINK \l "WBS331" 3.3.13.3.23.3.33.3.43.3.53.3.5.13.3.5.23.3.63.3.6.13.3.6.23.3.6.33.3.73.3.8LINK TO TABLE OF CONTENTS0LINKS TO WBS TABLE HYPERLINK \l "WBS331" 3.3.13.3.23.3.33.3.43.3.53.3.5.13.3.5.23.3.63.3.6.13.3.6.23.3.6.33.3.73.3.8LINK TO TABLE OF CONTENTS782955010795LINKS TO WBS TABLE HYPERLINK \l "WBS337x1" 3.3.7.x13.3.7.x23.3.7.x33.3.7.x43.3.7.x53.3.7.x6LINK TO TABLE OF CONTENTS00LINKS TO WBS TABLE HYPERLINK \l "WBS337x1" 3.3.7.x13.3.7.x23.3.7.x33.3.7.x43.3.7.x53.3.7.x6LINK TO TABLE OF CONTENTS765810029845LINKS TO WBS TABLE HYPERLINK \l "WBS341" 3.4.13.4.23.4.33.4.43.4.53.4.5.13.4.5.23.4.63.4.6.13.4.6.23.4.6.33.4.73.4.8LINK TO TABLE OF CONTENTS0LINKS TO WBS TABLE HYPERLINK \l "WBS341" 3.4.13.4.23.4.33.4.43.4.53.4.5.13.4.5.23.4.63.4.6.13.4.6.23.4.6.33.4.73.4.8LINK TO TABLE OF CONTENTS 747712520320LINKS TO WBS TABLE HYPERLINK \l "WBS347x1" 3.4.7.x13.4.7.x23.4.7.x33.4.7.x6LINK TO TABLE OF CONTENTS00LINKS TO WBS TABLE HYPERLINK \l "WBS347x1" 3.4.7.x13.4.7.x23.4.7.x33.4.7.x6LINK TO TABLE OF CONTENTSWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime3.?- Configuration Control ProcessIdentified Need for ChangeThis process will be used to ensure that all technical baseline changes are developed and managed in a controlled environment from the time the need for a change is identified until the change has been dispositioned and implemented.Configuration Management See below???? HYPERLINK \l "FlowChart31Links" 3.1?- Identification and Classification of Engineering Changes sub-processIdentified Need for ChangeThis sub-process will be used to validate an identified need for a change and determine, for valid needs, the type of change and its classification based on established parameters. Step 3.1.5 is essentially where all valid changes are categorized. All subsequent steps show how to respond based on the determinations made in step 3.1.5. All of the decisions shown need to be consciously determined in order to ensure that the correct flow is selected for subsequent process performance.Configuration Management HYPERLINK \l "FlowChart31Links" 3.1.1Input to 1.1 or 2.1??- Create Change Request (CR) and Route to the Responsible Technical Authority to trigger the beginning of the processAny stakeholder in the Using Command, Program Office, Contractor, or external stakeholder may identify the need for a change to a technical baseline throughout the product's lifecycle. That identified need can result from a variety of events, such as technological breakthroughs, obsolescence issues, deficiency reports, etc., and can be expressed in any format to the Responsible Technical Authority for the product to be affected by the change.Using Command, Program Office, Contractor HYPERLINK \l "FlowChart31Links" 3.1.21.1, 2.1?? - Receive/ Review CRThe Technical Authority for the affected product will gather whatever information is needed to do an evaluation of the CR. The Responsible Technical Authority and Configuration Change Manager will review the CR and supporting documentation to determine its validity and classification.Responsible Technical AuthorityWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart31Links" 3.1.3???- Reject the Request, close, notify originator, and documentIf the initial determination by the Technical Authority and Configuration Change Manager is that the request is invalid, they are to document the rejection and notify the originator. CRs can be determined to be invalid from a Configuration Management perspective for a variety of reasons, including requests for contract change which should be engineering changes, requests for engineering changes which don't affect a configuration baseline, requests which would result in a safety or airworthiness degradation, requests which would be in conflict with other planned changes, etc.Responsible Technical Authority?20 Days (for one OR the other)? HYPERLINK \l "FlowChart31Links" 3.1.4???- Validate the request, put on hold, and monitor statusIf the initial determination by the Responsible Technical and Configuration Management Authority is that the CR is valid but there are reasons for not immediately addressing it, they are to place it on hold, notify the originator, and monitor its status with the intent that if circumstances change, making the CR invalid or raising its priority, then it will be rejected (3.1.3) or moved on in the process (3.1.5), respectively.Responsible Technical AuthorityWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart31Links" 3.1.5???- Validate and Move Forward, ID Type and ClassificationIf the determination is that the CR is valid and of high enough priority to move forward with its implementation, the Responsible Technical and Configuration Management Authority are to determine its type and classification. Classifications and their Types include Major or 2 Engineering Changes, Major or Minor Deviations, or Permanent or Temporary Modifications. Contract Change Proposals (CCP) are not Engineering changes and are to be forwarded to those who own the CCP process (usually the Program Office's Contracts Management organization). See WBS 3.1.5.7.Responsible Technical Authority10 days after validation of the change HYPERLINK \l "FlowChart31Links" 3.1.5.1???- Major Engineering Change Determination/ Route to sub-processIf the determination is that the CR will result in a Major Engineering Change in accordance with established criteria, the CR is to be forwarded to the Major Engineering Change sub-Process (WBS 3.2).Responsible Technical Authority?See belowWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart31Links" 3.1.5.2???- Minor Engineering Change Determination/ Route to Responsible Organization (e.g., DCMA)If the determination is that the CR will result in a Minor Engineering Change, the CR is to be forwarded to the Cognizant Organization used for such changes. This can include DCMA and/or the Contractor or some other organization. While contractors usually have the authority to implement Minor changes without government permission, a government organization such as DCMA should verify the classification of such changes prior to permitting implementation. It is also good practice for the government (e.g., DCMA) to monitor implementation. The originator of the CR should be notified of the decision and the CR closed.Responsible Technical Authority?10 Days HYPERLINK \l "FlowChart31Links" 3.1.5.3???- Major Variance Determination/ Route to sub-processIf the determination is that the CR will result in a Major Variance, the CR is to be forwarded to the Variance sub-Process (WBS 3.3).Responsible Technical Authority?10 Days HYPERLINK \l "FlowChart31Links" 3.1.5.4???- Minor Variance Determination/ Route to Cognizant Organization (e.g., DCMA)If the determination is that the CR will result in a Minor Variance, the CR is to be forwarded to the cognizant organization (e.g., DCMA) for verification of the classification and monitoring of its implementation. The originator of the CR should be notified of the decision and the CR closed.Responsible Technical Authority?10 Days HYPERLINK \l "FlowChart31Links" 3.1.5.5???- Permanent Modification Determination/ Revisit Type and Classification DeterminationIf the determination is that the CR will result in a Permanent Modification, the determination that it isn't a Major Change is to be revisited, with the intent to revise its identification from a modification to a Major (the expected norm) or Minor Engineering Change. Responsible Technical Authority?10 DaysWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart31Links" 3.1.5.6???- Temporary Modification Route to sub-processIf the determination is that the CR will result in a Temporary Modification, the CR is to be forwarded to the Temporary Modification sub-Process (WBS 3.4).Responsible Technical Authority?10 Days HYPERLINK \l "FlowChart31Links" 3.1.5.7???- CCP Determination/ Route to Contract Management/ Close ProjectAs discussed under WBS 3.1.5, if the determination is that the CR may be a valid Contracts Change but not an Engineering Change, if a CCP has been prepared and submitted it should routed to the organization responsible for management of the contract (usually the Program Office's Contract Management organization). If a CCP hasn't been prepared the request should be returned to the originator for appropriate action.Responsible Technical Authority?10 Days HYPERLINK \l "FlowChart32Links" 3.2?- Major Engineering Changes sub-processDetermination of Need for a Major ChangeThis sub-process will be used to process Major Engineering changes through implementation and archive of official records.Configuration Management?See below HYPERLINK \l "FlowChart32Links" 3.2.11.2??- Request ProposalUpon being notified of the Cognizant Authority's determination that a Major Engineering Change project should be implemented, the Program Office will request a proposal (WBS 3.2.1.1) for implementing the change. Program Office?See Contracts and/or Program Management Process for RFP DevelopmentWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart32Links" 3.2.2???- Log RFP Release into tracking systemA Change Management Tracking System will be used to monitor the project against the schedule identified in the RFP. The Tracking Record (WBS 3.2.2.1) will collect information from the document artifacts created throughout the process. This information will be used to report the required Quality and Timeliness metrics after a project is closed. Configuration Management?3 Days HYPERLINK \l "FlowChart32Links" 3.2.3???- Monitor Progress, Update Tacking RecordAs the source of information for determining whether a planned change is on track and for populating metrics, the Tracking System must be updated as a change makes its way through the process. With each milestone achieved and artifact record created, dates of achievement and quality information need to be entered into the system.Configuration ManagementOn-going HYPERLINK \l "FlowChart32Links" 3.2.41.3??- Prepare/ submit ECPThe contractor will respond to the RFP with a proposal (WBS 3.2.4.1). Upon receipt, the tracking system will be updated with delivery information.Contractor?30 Days HYPERLINK \l "FlowChart32Links" 3.2.51.4??- Distribute for ReviewThe ECP will be distributed to cognizant team and functional organizations. This may include external stakeholders such as DCMA, Test organizations, etc.Configuration Management?5 DaysWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart32Links" 3.2.61.5??- Review/ CommentStakeholders will review the proposal, providing comments and recommendations regarding the project. The Tracking System will be updated to reflect comments and recommendations received so that timeliness of the review process and quality of the proposal can be determined for reporting metrics.Program Office, Using Command, Other External Stakeholders, Contractor?20 Days HYPERLINK \l "FlowChart32Links" 3.2.6.1???- Return for RevisionIf reviewing organizations believe the proposal should be revised prior to being taken to board for a final disposition, the ECP will be returned to the contractor (return to WBS 3.2.4). It should be noted the reviewing organizations don't have the authority to cancel the project, which would override the Responsible Technical Authority's decision to send the request into the change process.Program Office, Using Command, Other External Stakeholders, Contractor?5 Days (to do one or the other)? HYPERLINK \l "FlowChart32Links" 3.2.6.2???- Send to BoardIf reviewing organizations believe the proposal is ready to be sent to the CCB and/or Airworthiness Board(s), they are to notify the Responsible Configuration Manager/Change Board Secretariat, who will schedule a board and put the change on the agenda.Program Office, Using Command, Other External Stakeholders, ContractorWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart32Links" 3.2.71.6??- BoardA Configuration Change and/or Airworthiness Board, with membership composed of senior management from the program office and additional interested parties to include contractor management as appropriate, will be convened to review proposed Major changes and comments thereto that make it through the review stage. The Board Chair will have final authority to render a decision after consideration of comments and recommendations from reviewers and board members. Possible decisions can include returning the proposal to the contractor for further revision, approving the proposed change as is or with minor revisions agreed to at the board, or rejecting the proposal outright. The disposition will be documented on an appropriate form such as an AFTO872, Configuration Control Board Directive, signed by the board chair to formally document the decision, and the Tracking System updated to revise metrics. Further details on Board processes should be documented in Board Charters and processes that describe membership, other interested stakeholders, scheduling, project dispositioning, roles and responsibilities, etc.Change Control and/or Airworthiness BoardsSee belowWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart32Links" 3.2.7.1???- Approve Change as is or with minor revisions agreed to at the boardIf the Board Chair approves a project for implementation the decision will trigger processes external to the Change Control process. Since they are external to this process, they aren't described here but are summarized for additional information in an Attachment to this process under 3.2.8.x. At this point the Engineering Change process will stop collecting metrics data, as each of the other processes will collect and report on their own performance, until engineering data is updated. Configuration Management will notify stakeholders of the status and update the tracking system.Change Control and/or Airworthiness Boards?30 Days (to do one of the three)?? HYPERLINK \l "FlowChart32Links" 3.2.7.2???- Return for RevisionIf the Board Chair determines the project shouldn't be disapproved but that substantial revision to the ECP is needed, it will be returned to the contractor to make the revisions (return to WBS 3.2.4). Configuration Management will notify stakeholders and update the tracking system, including reasons for the needed revisions, the date when the contractor is notified of the needed revisions, and the schedule for return of the revised ECP.Change Control and/or Airworthiness Boards HYPERLINK \l "FlowChart32Links" 3.2.7.3???- Disapprove ChangeIf the Board Chair determines the project should be disapproved outright, the decision will be turned over to Configuration Management for project closure (see WBS 3.2.9), including updating the Tracking System.Change Control and/or Airworthiness BoardsEXTERNAL PROCESS INTERACTIONS – WBS 3.2, Major Engineering Change Sub-ProcessWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescription HYPERLINK \l "FlowChart32xLinks" 3.2.8.x??Major Change Board ApprovalThis section identifies processes external to the Major Engineering Change sub-process which are required to be performed prior to closing an approved Major change project in the change process tracking system.? HYPERLINK \l "FlowChart32xLinks" 3.2.8.x1- Configuration Identification ProcessThe role of the Configuration Identification process as part of an Engineering change is to assign appropriate part numbers and/or nomenclature to new or changed products in order to ensure consistency across a product's lifecycle as well as to avoid redundancy between different products. The output of the Configuration Identification process is a unique part number, including a Computer Program Identification Number (CPIN) as needed, and/or nomenclature (WBS 3.2.8.x1.1). The new numbers/names are provided to the Engineering Data Management process for updates to Engineering data. HYPERLINK \l "FlowChart32xLinks" 3.2.8.x2???- Engineering Data Management ProcessThe role of the Engineering Data Management process as part of an Engineering change is to update engineering data with part numbers and/or nomenclature assigned to new or changed products by the Configuration Identification process. The output of the Engineering Data Management process is updated engineering data (WBS 3.2.8.x2.1). The updated data is provided to the contracting process for incorporation into the contract for the new change.EXTERNAL PROCESS INTERACTIONS – WBS 3.2, Major Engineering Change Sub-ProcessWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescription HYPERLINK \l "FlowChart32xLinks" 3.2.8.x3???- Contract Award ProcessThe role of the Contract Award process as part of an Engineering change is to put the change on contract. The output of the Contract Award process is a signed contract, including a Change Implementation Plan (WBS 3.2.8.x3.1). The contract will trigger the design and development work necessary to develop the change and the production work required to produce it in accordance with the design. The Change Implementation Plan is used by the organization which will implement the change and the implementation monitoring organization(s). HYPERLINK \l "FlowChart32xLinks" 3.2.8.x4???- Design/ Technical ReviewUpon contract award any necessary development work can begin. When technical reviews of the design are passed it will be baselined and come under configuration control. The output of the design process, an approved documented design (WBS 3.2.8.x4.1), will be used in the Configuration Audit process. HYPERLINK \l "FlowChart32xLinks" 3.2.8.x5???- Production ProcessThe Production Process will use the baselined design to produce a production representative product (WBS 3.2.8.x5.1) to be used in the Configuration Audit process. HYPERLINK \l "FlowChart32xLinks" 3.2.8.x6???- Configuration Audit ProcessThe Functional and Physical Configuration Audit (FCA/PCA) processes verify the functional characteristics of the change against the performance requirements as well as the physical characteristics of the product against the baselined design. The output of the audit processes is a document (WBS 3.2.8.x6.1) attesting that the as-designed and as-built product meet all requirements, which provides approval to implement the change in affected product.EXTERNAL PROCESS INTERACTIONS – WBS 3.2, Major Engineering Change Sub-ProcessWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescription HYPERLINK \l "FlowChart32xLinks" 3.2.8.x7???- Monitor ImplementationAfter implementation of a change is authorized, an authority identified in the contractual implementation plan will need to verify the plan is met and attest to that fact. The output of the change implementation monitoring will be a document stating implementation has been completed (WBS 3.2.8.x7.1). This will be used to authorize update of engineering data for the affected unit of product. HYPERLINK \l "FlowChart32xLinks" 3.2.8.x8???- Engineering Data ProcessThe role of the Engineering Data Management process at this point in an Engineering change is to update engineering data for the unit of product recently obtaining the change. The output of the Engineering Data Management process is updated engineering data (WBS 3.2.8.x8.1), which is provided to the configuration status accounting process for continued accounting of the configuration of the affected unit(s) of product. Evidence of the completion of the update to the Engineering Data is provided to the responsible Change Manager to indicate the project can be closed for the product receiving the change.EXTERNAL PROCESS INTERACTIONS – WBS 3.2, Major Engineering Change Sub-ProcessWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescription HYPERLINK \l "FlowChart32xLinks" 3.2.8.x9???- Status Accounting ProcessThe Configuration Status Accounting process is a customer of the Change Control process in that it receives updated engineering data that results from the change process and uses it to monitor the current configuration status of products. HYPERLINK \l "FlowChart32xLinks" 3.2.8.x10???- Return to Major Engineering Change Process, WBS 3.2.9The connection back to the change control process from the external processes that are driven by a positive change board decision provides the authorization to close the project and archive its records. A final metric identifies the lapsed time from receipt of evidence that the change has been properly implemented on the last affected unit of product till the project is closed and records archived.WBS 3.2, Major Engineering Change Sub-ProcessWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart32Links" 3.2.91.8??- Close Project, Collect and Report Metric Data using the Tracking RecordUpon receipt of official evidence of project implementation from external processes or board disapproval of the project, Configuration Management will notify stakeholders, update the tracking system to close the project, and archive official records. Final metrics will report the time from receipt of the approved completion certificate or board decision to project closure and records archive.Configuration Management5 DaysWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart33Links" 3.3?- Major Variance sub-processDetermination of Need for a Major VarianceThis sub-process will be used to process Major Deviations through corrective action to eliminate the discrepancy, creating a fully qualified product and permitting closure of the deviation and archiving of its records. If it is desired that corrective action not be performed but the condition be allowed to remain on the affected product, an additional review should occur to determine whether a Major Engineering Change would be appropriate. While under certain circumstances it may be desirable to "live with the condition" and not fix it via an ECP, the norm should be that corrective action will eventually be planned and completed. See below? HYPERLINK \l "FlowChart33Links" 3.3.12.2?Determination of Need for a Major Variance- Prepare/Submit RFVWhen a Major Deviation is needed, the contractor must prepare and submit an RFV (3.3.1.1) to the Program Office Configuration Management organization. It may be that the initial CR comes in to the cognizant authority as an RFV, in which case the Responsible Technical Authority should forward it to Configuration Management after determining its validity and classification as major, or the issue may be identified less formally to the Responsible Authority who would then notify the contractor that a major variance needs to be requested on an RFV.Contractor HYPERLINK \l "FlowChart33Links" 3.3.2???- Log RFV into tracking systemA Change Management Tracking System will be used to ensure proper vetting of RFVs and determine if the review process and eventual corrective action remain on track in accordance with the schedule identified in the RFV and corrective action plan. Information related to the document artifacts created by the process will be used to develop Quality and Timeliness metrics. Configuration Management?3 DaysWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart33Links" 3.3.3???- Monitor Progress, Update Tracking Record, Collect Metrics to Project ClosureAs the source of information for determining whether managing a planned deviation is on track and for populating metrics, the Tracking System must be updated as a variance makes its way through the process. With each milestone achieved and artifact record created, dates of achievement and quality information need to be entered into the system.??On-going HYPERLINK \l "FlowChart33Links" 3.3.42.3??- Distribute RFV for ReviewThe RFV will be distributed to cognizant team and functional organizations. This may include external stakeholders such as DCMA, Test organizations, etc.??5 Days HYPERLINK \l "FlowChart33Links" 3.3.52.4??- Review/CommentStakeholders will review the RFV, providing comments and recommendations regarding it. The Tracking System will be updated to reflect comments and recommendations received so that timeliness of the review process and quality of the proposal can be determined for reporting metrics.Program Office, Using Command, Other External Stakeholders, Contractor?20 Days HYPERLINK \l "FlowChart33Links" 3.3.5.1???- Return for RevisionIf reviewing organizations believe the RFV should be revised prior to being taken to board for a final disposition, it will be returned to the contractor (return to 3.3.1.). Program Office, Using Command, Other External Stakeholders, Contractor5Days (to do one or the other) HYPERLINK \l "FlowChart33Links" 3.3.5.2???- Send to BoardIf reviewing organizations believe the RFV is ready to be sent to a Variance Review Board and/or Airworthiness Board, they are to notify the Responsible Configuration Manager/Change Board Secretariat, who will schedule a board, put the request on the agenda, and update the tracking system.Program Office, Using Command, Other External Stakeholders, ContractorWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart33Links" 3.3.62.5??- BoardA Variance Review and/or Airworthiness Board, with membership composed of program office personnel and additional interested parties to include contractor management as appropriate, will be convened to review RFVs that make it through the review stage. The Board Chair has final authority to render a decision after consideration of comments and recommendations from reviewers and board members. Possible decisions can include returning the RFV to the contractor for further revision, approving the request as is or with minor revisions agreed to at the board, or rejecting it outright. The decision will be documented on an appropriate form such as an AFTO872, Configuration Change Board Directive, signed by the board chair, and the Tracking System updated to revise metrics. Further details on Board processes should be documented in Board Charters and processes that describe membership, other interested stakeholders, scheduling, RFV dispositioning, roles and responsibilities, etc.Change Control and/or Airworthiness Boards?See BelowWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart33Links" 3.3.6.1???- Approve RFV as is or with minor revisions agreed to at the boardIf the Board Chair approves an RFV for implementation the decision will trigger processes external to the Change Control process. Since they are external to this process, they aren't described here but are summarized for additional information in an Attachment to this process under 3.3.7.x. At this point the Major Variance process will stop collecting metrics data, as each of the other processes will collect and report on their own performance, until revised engineering data or approved Completion Certificate is received. Configuration Management will notify stakeholders of the status and update the tracking system.Change Control and/or Airworthiness Boards30 DaysHYPERLINK \l "FlowChart33Links"3.3.6.2???- Return for RevisionIf the Board Chair determines the RFV shouldn't be disapproved but that substantial revision to it is needed, it will be returned to the contractor to make the revisions (return to 3.3.1). Configuration Management will notify stakeholders and update the tracking system with sufficient information to collect and report both quality and timeliness metrics, including reasons for the needed revisions and the date when the contractor is notified of them.Change Control and/or Airworthiness BoardsWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart33Links" 3.3.6.3???- Disapprove RFVIf the Board Chair determines the RFV should be disapproved outright, the decision will be turned over to Configuration Management for closure (3.3.8). Often this results in delays to the delivery schedule, which might mean a new RFV or CCP against schedule requirements would be appropriate.Change Control and/or Airworthiness Boards?30 Days HYPERLINK \l "FlowChart33Links" 3.3.72.6??- Exit to External ProcessesAs described under 3.3.6.1, once an RFV is approved by a Deviation board, several other processes are triggered, suspending the change process and its collection of metrics data until evidence of completed corrective action or documented decision not to perform corrective action is received by Configuration Management. The Contracting Process negotiates consideration for acceptance of the deviation and provides the agreed-to Corrective Action Plan stating whether and how the deficiency will be corrected. Configuration Management owned processes that intersect with the change process for Major Variances may include the Engineering Data Management and Configuration Status Accounting processes.Once the external processes have completed their actions, the return to the Change process will occur with evidence that the affected engineering data has been updated and the Status Accounting Process can now take over or evidence of completed corrective action provided (3.3.7.1). ??EXTERNAL PROCESS INTERACTIONS – WBS 3.3, Major Variance Sub-ProcessWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescription3.3.7.x??Major Variance Board ApprovalThis section identifies processes external to the Major Variance sub-process which are required to be performed prior to closing an approved Major Variance in the change process tracking system. HYPERLINK \l "FlowChart33xLinks" 3.3.7.x1???- Negotiate Consideration and finalize Corrective Action PlanWhen the government agrees to accept product not meeting all requirements some amount of consideration from the contractor is required for as long as the nonconforming condition is allowed to remain on the product. The program office's Contracts Management organization will negotiate the consideration and agree to a documented Corrective Action Plan for addressing the nonconformance. Agreed-to corrective action can include the following:1. When possible, bring the affected product into full compliance with its requirements (WBS 3.3.7.x1.1). 2. Permit the nonconforming condition to remain on the product (WBS 3.3.7.x1.2) due to risks involved in removing the condition or other considerations. 3. Permit the condition to remain on the product but bring it into conformance by revising requirements (WBS 3.3.7.x1.2). This may require additional testing to determine whether the condition meets necessary requirements and would result in the need for a Major change. HYPERLINK \l "FlowChart33xLinks" 3.3.7.x2???- Monitor Corrective ActionAfter accomplishing the corrective action a signed completion certificate (WBS 3.3.7.x2.1) should be forwarded to the Change Manager, permitting a return to the Major Deviation process so the deviation can be closed in the tracking system and records archived. At this time the contractor will also request return of the consideration that was originally withheld.EXTERNAL PROCESS INTERACTIONS – WBS 3.3, Major Variance Sub-ProcessWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescription HYPERLINK \l "FlowChart33xLinks" 3.3.7.x3???- Exit to WBS 2., Major Engineering Change ProcessIf it is determined that a Major change would be appropriate to make the condition that led to the deviation acceptable, the Major Change Control process would take over. Evidence that it has done so (WBS 3.3.7.x3.1) in the form of an RFP, ECP, or equivalent will authorize return to the Major Deviation process to clos63e the deviation and archive its records. The original withheld consideration can be made a part of the contracted Major change. HYPERLINK \l "FlowChart33xLinks" 3.3.7.x4??- Exit to Engineering Data Management ProcessIf it is determined that a nonconforming condition that leads to a variance will be permitted to stay on the affected product due to risks, cost, etc., engineering data for the product will need to be updated to note the condition (WBS 3.3.7.x4.1). An exit to the Engineering Data Management process will occur. Authorization to return to the Major Variance process to close the variance will come in the form of evidence that the engineering data has been updated. The negotiated consideration in these cases will not be returned to the contractor. HYPERLINK \l "FlowChart33xLinks" 3.3.7.x5??- Status Accounting ProcessThe Configuration Status Accounting process is a customer of the Major Deviation process when it receives updated engineering data that results from the deviation process and uses it to monitor the current configuration status of products. HYPERLINK \l "FlowChart33xLinks" 3.3.7.x6???- Return to Major Variance Process, WBS 3.3.8Evidence that a deviation has been removed from affected product, that the condition will be handled by the Major Engineering Change process, or that engineering data has been updated to reflect the condition when it will be allowed to remain on the product, will trigger a return to the Major Deviation process for closing the deviation record and archiving records.WBS 3.3, Major Variance Sub-ProcessWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart33Links" 3.3.82.7??- Close RFV in the Tracking System and archive official records. Upon receipt of a negative board disposition, evidence that the affected engineering data has been updated and the Status Accounting Process can now take over, or completed corrective action, Configuration Management will notify stakeholders, update the tracking system to close the project, and archive official records. Final metrics will report the time from receipt of the approved completion certificate or board decision to variance closure and records archive.??5 Days HYPERLINK \l "FlowChart34Links" 3.4?- Temporary ModificationDetermination of need for a Temporary ModificationThis sub-process will be used to process Temporary Modifications through removal permitting closure of the project and archive of its records. If it is desired that the modification should remain on the product, an additional review should occur to determine whether a Major Engineering Change would be appropriate. While under certain circumstances it may be desirable to keep the modification without a Major change, the norm should be that the modification will be removed or a Major change implemented. ??WBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart34Links" 3.4.12.2?Determination of need for a Temporary Modification- Prepare 1067 or equivalent CAA temporary modification project will normally be initiated by the Using Command through preparation and submittal of a Form 1067. Contractors or other stakeholders (e.g., test organizations) can also request temporary modifications. They should use a 1067 or equivalent request form to do so.?? HYPERLINK \l "FlowChart34Links" 3.4.2???- Log CA into tracking systemA Change Management Tracking System will be used to ensure proper vetting of Temporary Modification CAs and determine if the review process and eventual removal of the modification remain on track in accordance with the schedule identified in the CA. Information related to the document artifacts created by the process will be used to develop Quality and Timeliness metrics.??3 Days HYPERLINK \l "FlowChart34Links" 3.4.3???- Monitor Progress, Update Tacking Record, Collect Metrics to Project ClosureAs the source of information for determining whether managing a temporary modification is on track and for populating metrics, the Tracking System must be updated as a CA makes its way through the process. With each milestone achieved and artifact record created, dates of achievement and quality information need to be entered into the system.On-going HYPERLINK \l "FlowChart34Links" 3.4.42.3??- Distribute for ReviewThe CA will be distributed to cognizant team and functional organizations. This may include external stakeholders such as DCMA, Test organizations, etc.5 DaysWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart34Links" 3.4.52.4??- Review/CommentStakeholders will review the CA, providing comments and recommendations regarding it. The Tracking System will be updated to reflect comments and recommendations received so that timeliness of the review process and quality of the proposed modification can be determined for reporting metrics.20 Days HYPERLINK \l "FlowChart34Links" 3.4.5.1???- Return for RevisionIf reviewing organizations believe the CA should be revised prior to being taken to board for a final disposition, it will be returned to the contractor (return to 3.4.1.). 5 Days (to do one or the other) HYPERLINK \l "FlowChart34Links" 3.4.5.2???- Send to BoardIf reviewing organizations believe the CA is ready to be sent to a Change Control Board and/or Airworthiness Board, they are to notify the Cognizant Configuration Manager/Change Board Secretariat, who will schedule a board, put the request on the agenda, and update the tracking system.WBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart34Links" 3.4.62.5??- BoardA Change Control and/or Airworthiness Board, with membership composed of program office personnel and additional interested parties to include contractor management as appropriate, will be convened to review CAs that make it through the review stage. The Board Chair will have final authority to render a decision after consideration of comments and recommendations from reviewers and board members. Possible decisions can include returning the CA to the contractor for further revision, approving the request as is or with minor revisions agreed to at the board, or rejecting it outright. The decision will be documented on an appropriate form such as an AFTO872, Configuration Control Board Directive, signed by the board chair, and the Tracking System updated to revise metrics. Further details on Board processes should be documented in Board Charters and processes that describe membership, other interested stakeholders, scheduling, CA dispositioning, roles and responsibilities, etc.Configuration Management?WBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart34Links" 3.4.6.1???- Approve CA as is or with minor revisions agreed to at the boardIf the Board Chair approves a CA for implementation the decision will trigger processes external to the Change Control process. Since they are external to this process, they aren't described here but are summarized for additional information in an Attachment to this process under 3.4.7.x. At this point the Temporary Modification process will stop collecting metrics data, as each of the other processes will collect and report on their own performance, until engineering data is updated or evidence of removal of the modification is received. Configuration Management will notify stakeholders of the status and update the tracking system.?30 Days HYPERLINK \l "FlowChart34Links" 3.4.6.2???- Return for RevisionIf the Board Chair determines the CA shouldn't be disapproved but that substantial revision to it is needed, it will be returned to the originator to make the revisions (return to 3.4.1). Configuration Management will notify stakeholders and update the tracking system with sufficient information to collect and report both quality and timeliness metrics, including reasons for the needed revisions and the date when the originator is notified of them.?WBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart34Links" 3.4.6.3- Disapprove CAIf the Board Chair determines the CA should be disapproved outright, the decision will be turned over to Configuration Management for closure (3.4.8). Configuration Management30 Days HYPERLINK \l "FlowChart34Links" 3.4.72.6??- Exit to External ProcessesAs described under 3.4.6.1, once a CA is approved by a Change board, several other processes are triggered, suspending the change process and its collection of metrics data until evidence of completed removal of the modification or documented decision not to remove it is received by Configuration Management. Implementation of the modification will need to be monitored, as well as its removal afterward. If the modification is to remain on the product, an ECP, triggering the Major Engineering Change Process, may be required, Engineering Data may have to be updated, and the Status Accounting Process would be affected.Once the external processes have completed their actions, the return to the Change process will occur with evidence that the affected engineering data has been updated and the Status Accounting Process can now take over, or evidence of removal of the modification provided (3.4.7.1). Using Command, Program Office, Contractor?EXTERNAL PROCESS INTERACTIONS – WBS 3.4, Temporary Modification Sub-ProcessWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescription3.4.7.x?Temporary Modification Board ApprovalThis section identifies processes external to the Temporary Modification sub-process which are required to be performed prior to closing an approved Temporary Modification in the change process tracking system. HYPERLINK \l "FlowChart34xLinks" 3.4.7.x1?????- Monitor Implementation and Determine Removal PlanPrior to implementation of a temporary modification a plan for removing it (WBS 3.4.7.x1.1) should be developed. Normally, this would be included in the original request (e.g., Form 1067). Implementation of the modification should be monitored by interested parties. HYPERLINK \l "FlowChart34xLinks" 3.4.7.x2?- Remove ModificationTemporary modifications should be removed in accordance with the removal plan. A completion certificate (WBS 3.4.7.x2.1) should be signed off by the monitoring organization(s) and forwarded to the Change Manager. HYPERLINK \l "FlowChart34xLinks" 3.4.7.x3?- Exit to WBS 2., Major Engineering Change ProcessIf it is determined subsequent to modification implementation that the modification will be left on the affected product, a Major Engineering Change is necessary in order to ensure the approved baseline is updated to match the as-built product. Evidence that the Major Engineering Change process has taken over, such as an RFP, ECP, etc., will provide authorization to return to the Temporary Modification process. HYPERLINK \l "FlowChart34xLinks" 3.4.7.x6?- Return to Temporary Modification Process, WBS 3.4.8Evidence that a temporary modification has been removed from affected product or that the Major Engineering Change process has been initiated to reflect that the modification will be allowed to remain on the product, will trigger a return to the Major Variance process for closing the variance record and archiving records.WBS 3.2, Temporary Modification Sub-ProcessWBSApplicable SIPOC Table IDProcess/ Sub-ProcessInitial InputTaskDescriptionOPRTime HYPERLINK \l "FlowChart34Links" 3.4.82.7??- Close CA and archive records Upon receipt of a negative board disposition, evidence that the affected engineering data has been updated and the Status Accounting Process can now take over, or evidence of modification removal, Configuration Management will notify stakeholders, update the tracking system to close the project, and archive official records. Final metrics will report the time from receipt of the approved documentation or board decision to 1067 closure and records archival.??5 Days ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download