PMA275_CMP_2014_09_01.pdf

V-22 Program Configuration Management Plan dated 1 September 2014

Prepared By:

PMA-275 Configuration Manager V-22 Joint Program Office

Prepared For:

Department of the Navy Naval Air Systems Command 47123 Buse Road, Unit IPT Building 2272, Suite 0151

Patuxent River, MD 20670-1547 ii ii

V-22 CHANGE CONTROL BOARD CHARTER

1. PURPOSE: The V-22 Program Manager (PMA-275) is hereby delegated the authority to establish and chair a Decentralized Change Control Board (DCCB). This authority is to be exercised in accordance with NAVAIRINST 4130.1 series except as modified and approved in writing by the V-22 Configuration Management Plan (CMP). PMA-275 shall ensure that all Class 1 Engineering Change Proposals, Requests for Deviations, and Rapid Action Minor Engineering Changes presented to the DCCB have been processed using the Change Control Board Request/Directive forms identified by NAVAIRINST 4130.1.

2. EXPIRATION DATE: This Charter shall remain in effect for a period of two years or until a revision to the V-22 CMP is approved, whichever comes first.

3. BACKGROUND: The V-22 Osprey is a tilt rotor, vertical takeoff and landing aircraft for Joint Service application. A Physical Configuration Audit was conducted on 10 February 2000, which transferred configuration management of the aircraft to the government. The V-22 Program is presently in Full Rate Production.

4. INTERFACES: The V-22 aircraft and its interfaces are defined in and shall be controlled to SD-572-1-3 Detailed Specification for V-22.

5. DETAILS: Specific configuration management practices and procedures are provided in the V-22 CMP and current operating instructions. During the effective period of this charter, PMA- 275 shall maintain status accounting of all approved configuration changes/deviations for the V- 22 Weapon System.

6. EXTENSION and REVISIONS: Extensions and revisions of this charter shall require approval by AIR-1.1.3.

iii

FOREWORD

This Configuration Management Plan (CMP) defines policies and procedures for processing configuration documentation throughout the V-22 Osprey Program life cycle.

This CMP shall be used by the V-22 Osprey Program Office and other program offices managing V-22 assets under Program Executive Offices to include: Direct Reporting Program Managers, Commodity Program Managers, Naval Air Systems Command Headquarters, supporting field activities and other applicable Department of Defense (DoD) organizations whose programs interface with the V-22 aircraft or its associated systems and equipment.

DoD standardization for Configuration Management has evolved to the use of industry standards rather than military standards. There will be a long period of transition as pre-existing contracts complete their life cycle under prior acquisition strategy and new contracts phase in the new methodology. The applicable references in this CMP reflect the baseline methodologies that may be contractually in place. Below are the options the V-22 Osprey Program may exercise based on acquisition strategy, logistics support planning, and sound management judgment.

-MIL-STD-973 has been cancelled but continues to affect existing contracts.

-MIL-HDBK-61A is the current reference in the CMP.

-ANSI/EIA-649-B is the configuration management standard used by industry.

This CMP does not constitute or grant authority or approval for the modification, revocation, or addition to any contract, purchase order, work order, or subcontract.

iv

1 GENERAL INFORMATION 1

1.1 PURPOSE 1

1.2 OBJECTIVE 1

1.2.1 SPECIFIC OBJECTIVES 1

1.3 DEFINITIONS 1

1.4 PROGRAM BACKGROUND 1

1.5 CONFIGURATION MANAGEMENT PLAN SUMMARY 2

1.6 CONFIGURATION MANAGEMENT TEAM 2

1.7 CONFIGURATION MANAGEMENT PLANNING RESPONSIBILITIES 2

1.8 PRIME CONTRACTOR RESPONSIBILITIES, POLICIES AND PROCEDURES 3

1.9 LIFE CYCLE AND LIFE CYCLE COSTS 3

2 APPLICABLE DOCUMENTS 3

2.1 GOVERNMENT DOCUMENTS 3

2.2 INDUSTRY DOCUMENTS 4

2.3 ORDER OF PRECEDENCE 4

3 CONFIGURATION IDENTIFICATION 4

3.1 CONFIGURATION ITEMS 4

3.2 V-22 CONFIGURATION BASELINES 5

3.3 SPECIFICATIONS 5

3.4 DRAWINGS AND ASSOCIATED TECHNICAL DATA 5

3.5 TECHNICAL DOCUMENT NUMBERING 5

3.6 NOMENCLATURE AND SERIAL NUMBERS 5

4 CONFIGURATION AUDITS AND TECHNICAL REVIEWS 5

4.1 PURPOSE 5

4.2 GENERAL 6

4.3 TYPES OF CONFIGURATION AUDITS 6

v

4.4 EXECUTION OF AUDITS: 6

4.5 TECHNICAL REVIEWS 6

5 CONFIGURATION CONTROL 6

5.1 PURPOSE 6

5.2 OBJECTIVE 7

5.3 CONFIGURATION CHANGE PROCESS 7

5.3.1 LEVEL 2 CHANGE BOARD 7

5.3.2 CHANGE REVIEW BOARD 7

5.3.3 V-22 DECENTRALIZED CHANGE CONTROL BOARD 7

5.4 ENGINEERING CHANGE PROPOSALS 10

5.4.1 CLASSIFICATION OF ECPs 10

5.4.2 REVIEW AND DISPOSITION OF CLASS I CHANGES 10

5.4.3 REVIEW AND DISPOSITION OF CLASS 2 CHANGES 10

5.5 DEVIATIONS 10

5.5.1 CLASSIFICATION OF DEVIATIONS 10

5.5.2 REVIEW AND DISPOSITION OF DEVIATIONS 10

5.6 AIR FORCE MODIFICATIONS 11

5.6.1 TEMPORARY MODIFICATIONS 11

5.6.2 PERMANENT MODIFICATIONS 11

5.7 TECHNICAL DIRECTIVES / TIME COMPLIANCE TECHNICAL ORDERS 11

5.8 CHANGE INITIATION AND STAFFING 11

6 CONFIGURATION STATUS ACCOUNTING 11

6.1 PURPOSE 11

6.2 CONFIGURATION STATUS ACCOUNTING SYSTEM 11

6.3 CONTRACTOR(S) CSA SYSTEM 12

7 DATA MANAGEMENT 12

7.1 PURPOSE 12

7.2 OBJECTIVE 12

7.3 DATA REQUIREMENTS 12

7.4 DATA DELIVERY 12

7.5 DATA PROTECTION 12

vi

7.6 DATA REQUIREMENTS REVIEW BOARD 13

CM MAJOR MILESTONES 15

ACRONYMS 17

ATTACHMENT I 1

ATTACHMENT II 2

1 GENERAL INFORMATION

1.1 PURPOSE

The purpose of this Configuration Management Plan (CMP) is to define the requirements, describe the administrative processes, and outline the responsibilities governing Configuration Management (CM) on the V-22 Weapon System. This CMP establishes the responsibilities for V-22 CM and provides the guidelines to be used by the V-22 Decentralized Change Control Board (DCCB). CM is a joint effort between the government, prime contractors, and suppliers.

1.2 OBJECTIVE

The objective of this CMP is to tailor and document CM policies and procedures in accordance with NAVAIRINST 4130.1 series, MIL-STD-973, MIL-HDBK-61A, NAVAIR 00-25-300, AFPD 63-11, AFI 63-1101, and AFI 21-101 to meet the specific requirements of the V-22 Weapon System.

1.2.1 SPECIFIC OBJECTIVES

The objectives of the CMP are:

• Implement CM in accordance with NAVAIRINST 4130.1 series, AFI 21-101, and MIL-HDBK-61A as tailored herein to meet V-22 program requirements.

• Establish and control the baseline for V-22 Configuration Items (CIs) including the aircraft and all of its support assets (Support Equipment, Test Program Sets, trainers, and associated software, etc.) for which the government is the configuration control authority of the detail design.

• Provide the essential processes to protect the V-22 hardware and software baselines as they have been established.

• Define procedures to evaluate and control changes to the V-22 configuration baselines.

• Establish configuration status accounting requirements and procedures.

• Define requirements for CM audits.

1.3 DEFINITIONS

CM terminology employed herein is in accordance with standard definitions contained in NAVAIRINST 4130.1 series. Unique terms are defined at their first appearance and cross-referenced in Appendix B.

1.4 PROGRAM BACKGROUND

This CMP establishes PMA-275 as the Office of Primary Responsibility for CM and defines the responsibilities of the Chief Engineer, Product Support Manager (PSM), Business Financial Manager, Procurement Contracting Officer (PCO), MV Integrated Product Team (IPT), CV IPT, In-Service IPT, Level 2 IPTs, Test and Evaluation team, Production team, and all supporting activities within the Naval Air Systems Team for V-22 CM related subjects.

A Memorandum of Agreement (MOA) (Attachment I) has been established between the Department of the Navy (DoN), the Department of the Air Force, and the United States Special Operations Command (USSOCOM) which describes policies, relationships, resources, organizations, and responsibilities pertaining to the V-22 acquisition and life cycle support. The

Under Secretary of Defense (Acquisition & Technology) has designated the DoN as the Lead Service for the V-22.

A MOA (Attachment II) has been established between PMA-275 and Air Force Special Operations Command (AFSOC) which establishes a joint format for Technical Directives (TDs) and Time Compliance Technical Orders (TCTOs). The MOA also defines the roles, responsibilities, and authority for drafting and distributing TDs/TCTOs.

PMA-275, a multi-service joint program office, is the Department of Defense (DoD) organization responsible for the development, test and evaluation, procurement, fielding, sustainment, and life cycle support of the V-22 Weapon System. The V-22 aircraft is a tilt-rotor, vertical takeoff and landing aircraft for joint service application. The V-22 Program is designed to provide an aircraft to meet the United States Marine Corps' Amphibious/Vertical Assault mission, the United States Navy’s Fleet Combat Support and Combat Search and Rescue mission, and USSOCOM’s Special Operations mission. The V-22 will replace the CH-46E and CH-53D helicopters in the Marine Corps, replace AFSOC’s MH-53J/M, and supplement USSOCOM’s MC-130E/H fleet.

1.5 CONFIGURATION MANAGEMENT PLAN SUMMARY

This plan provides guidelines, objectives, responsibilities, definitions, references, and procedures for CM of the V-22 Program. It has been written to provide various entities within the V-22 Program a reference for implementation of CM policies and procedures. CM for the V-22 Weapon System shall be conducted in accordance with NAVAIRINST 4130.1 series, AFI 21- 101, MIL-HDBK-61A, MIL-STD-973, NAVAIR 00-25-300, the DCCB charter, and this plan.

1.6 CONFIGURATION MANAGEMENT TEAM

PMA-275 is chartered to manage the configuration of the V-22 Weapon System. The CM team is a sub-element of the Program Integration organization. The CM team is responsible for the planning, execution, and implementation of the V-22 CM program. The V-22 Configuration Manager serves as the CM Team Lead. The CM team consists of CM specialists that provide guidance and support to IPT leads, engineers, logisticians, contract specialists, and prime contractors in matters related to the CM process. The responsibilities of the CM team are identified in the CM Team Charter. The engineers, logisticians, and contract specialists within the IPTs, although not members of the CM Team, are an integral part of the CM process and work closely with the CM Team.

1.7 CONFIGURATION MANAGEMENT PLANNING RESPONSIBILITIES

CM is an ongoing all-hands effort that requires detailed planning throughout the acquisition cycle. The V-22 Configuration Manager shall maintain this plan to ensure that actions are defined and responsibilities for execution are assigned. The Configuration Manager shall also ensure the program is adhering to policies, procedures, and requirements specified in NAVAIRINST 4130.1 series, AFI 21-101, NAVAIR Notice 5234, MIL-HDBK-61A, applicable MIL-STDs, and this CMP.

1.8 PRIME CONTRACTOR RESPONSIBILITIES, POLICIES AND PROCEDURES

Bell-Boeing and Rolls-Royce Corporation are on contract to conduct CM in accordance with this CMP and their government approved CMPs. The contractors’ CMPs are submitted to the program office for approval and shall reflect the requirements of the V-22 program. Updates to the contractors’ CMPs shall be submitted to the V-22 Program Office for approval whenever contractual modifications dictate, when major changes to governing directives occur, or when directed by the government. The contractors shall ensure that the requirements of this CMP and their government approved CMP are levied on suppliers.

1.9 LIFE CYCLE AND LIFE CYCLE COSTS

Life Cycle identifies all phases of the acquisition, operation, and logistics support of an item, beginning with concept definition and continuing through disposal of the item. Life cycle costs are the total costs to the tasking activity of acquisition and ownership of that system over its life cycle. It includes the cost of development, acquisition, support, and disposal. The contractor is responsible for researching life cycle costs for all proposed changes and including them in each Engineering Change Proposal (ECP).

2 APPLICABLE DOCUMENTS

2.1 GOVERNMENT DOCUMENTS

Cancelled military standards referenced in this plan are annotated for use as guidance only.

Although cancelled, these standards comply with the requirements of the associated industry standards and they provide additional detailed information helpful for clarification and execution of requirements.

AFI 21-101 Aerospace Equipment Maintenance Management

AFI 63-1101 Modification Management

AFPD 63-11 Modification System

DoDI 5230.24 Distribution Statements on Technical Documents

DOD-STD-100 Engineering Drawing Practices

MIL-DTL-18307H Nomenclature Identification For Aeronautical Systems

Including Joint Electronics Type Designated Systems and Associated Support Systems

MIL-HDBK-61A Military Handbook Configuration Management Guidance

MIL-STD-490 Specification Practices

MIL-STD-973 Configuration Management

MIL-T-31000 Technical Data Packages

NAVAIR 00-25-300 NAVAIR Technical Directives System

NAVAIRINST 4130.1 NAVAIR Configuration Management Process

NAVAIRINST 4200.25D Management of Critical Application Items Including

Critical Safety Items

NAVAIRINST 4355.19D Systems Engineering Technical Review Process

NAVAIR Notice 5234 NAVAIR Guidelines for e.POWER Document

Management and Workflow Software

PMA275-OI-CM01 V-22 Engineering Change Proposal Initiation Process

PMA275-OI-CM04 V-22 Engineering Change Proposal Staffing

T.O. 00-5-1 Air Force Technical Order System

T.O. 00-5-2 Technical Order Distribution System

T.O. 00-5-15 Air Force Time Compliance Technical Order System

MOA for Management of the V-22 Osprey Program

MOA for V-22 Joint TD/TCTO Process

2.2 INDUSTRY DOCUMENTS

ANSI/EIA-649-B Configuration Management Standard GEIA-HB-649 Implementation Guide for Configuration Management

2.3 ORDER OF PRECEDENCE

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence.

3 CONFIGURATION IDENTIFICATION

3.1 CONFIGURATION ITEMS

CIs were identified concurrent with the establishment of the product baseline and shall continue through the production and operational phases. PMA-275 manages components and software of the following major systems as CIs:

• MV-22 Aircraft – Marine Corps Configuration

• CV-22 Aircraft – Air Force Configuration

• HV-22 Aircraft – Navy Configuration

• AE1107C Liberty Engine (Commercial)

• All Training Devices and Systems

• All V-22 Peculiar Support Equipment

3.2 V-22 CONFIGURATION BASELINES

The V-22 baselines consist of configuration documentation that defines hardware/software CIs and are points of departure for control of future changes. There are three baselines for the V-22 program: Functional, Allocated, and Product. These baselines are defined in NAVAIRINST

4130.1 series.

The product baseline for all variants of the V-22 was established at the fourth aircraft (BUNO 165436) of Low Rate Initial Production 1 after completion of a Physical Configuration Audit in February 2000. At that time CM was formally transitioned from the contractor to the government. The CV-22 configuration was initially defined by ECP V-22-0457 and established with the delivery of the first Production Representative Test Vehicle (020024).

3.3 SPECIFICATIONS

The identifier for the V-22 detail specification is SD-572. The identifier for the AE1107C Liberty engine specification is 937A. Any changes to these specifications will be processed as Class 1 ECPs and requested in accordance with the associated Contracts Data Requirements List (CDRL). Specifications for Foreign Military Sales customers, when required, will be captured in an addendum to the SD-572.

3.4 DRAWINGS AND ASSOCIATED TECHNICAL DATA

Engineering drawings and associated technical data shall be prepared in accordance with MIL-T- 31000 Technical Data Packages and DOD-STD-100 Engineering Drawing Practices and submitted in accordance with the applicable CDRLs.

3.5 TECHNICAL DOCUMENT NUMBERING

Specifications, drawings and associated technical data, associated parts lists, reports, and plans shall be assigned unique identification numbers. Revisions to technical documents shall supersede previous versions in their entirety except for ECPs. In certain cases, revisions to ECPs may be submitted as amendments to the original.

3.6 NOMENCLATURE AND SERIAL NUMBERS

Nomenclatures, nameplates, and serial numbers are controlled in accordance with MIL-DTL- 18307H. Once assigned, serial numbers of CIs will not be changed even if the part number is changed due to retrofit.

4 CONFIGURATION AUDITS AND TECHNICAL REVIEWS

4.1 PURPOSE

Audits verify that the configuration documentation for a CI is accurate; complete; will meet program acquisition, technical, product support, and user requirements; and to confirm the compatibility of baseline documentation with higher level design documentation. Audits are conducted in accordance with MIL-HDBK-61A, contractors' approved CMPs, and applicable approved audit plans.

4.2 GENERAL

Configuration audits shall be conducted for any major design effort in order to determine that configuration documentation accurately describes the hardware and software being developed or produced. The requirements for each audit shall be included in the Statement of Work (SOW) for the design effort.

The contractor shall propose the time and place for audits to be conducted and shall obtain government concurrence. The contractor is responsible for ensuring that sub-contractor, supplier, or co-producer participation is available as required. During the audit the contractor is responsible for all necessary support including agenda preparation, conference rooms, hardware, software, data, and for providing stenographic services for recording and publishing of minutes.

Access to the CI being audited shall be provided during normal daytime working hours. These procedures and methods will be described in the contractor-prepared Configuration Audit Plan and approved by the government.

4.3 TYPES OF CONFIGURATION AUDITS

There are two recognized types of configuration audits: the Functional Configuration Audit (FCA) and the Physical Configuration Audit (PCA). Both audits must be completed as a prerequisite to establishment of a product baseline. The FCA and PCA are defined in NAVAIRINST 4130.1 series and ANSI/EIA-649-B.

4.4 EXECUTION OF AUDITS:

The Level 1 IPT Leads will designate a government Chairperson for each audit. The Chairperson will be responsible for the overall execution of the audit and for ensuring participation by all required functional disciplines or competencies. Assistance in planning and conducting an audit is available from AIR-1.1.3.

4.5 TECHNICAL REVIEWS

Technical reviews are a series of systems engineering activities by which the technical progress on a project is assessed relative to its technical or contractual requirements. The reviews shall be conducted at logical transition points in the development effort to identify and correct problems resulting from the work completed thus far before the problems can disrupt or delay the technical progress. The reviews provide a method for the contractor and government to determine that the development of a configuration item and its documentation is meeting the contractual requirements. Technical reviews are defined in, and conducted in accordance with, NAVAIRINST 4355.19D.

5 CONFIGURATION CONTROL

5.1 PURPOSE

Configuration control ensures that proposed changes to a CI baseline are properly documented, accurate configuration identification is maintained, and changes are approved prior to implementation. The control and procedures for processing, evaluating, and the disposition of Class 1 ECPs, Rapid Action Minor Engineering Changes (RAMECs), Requests for Deviations (RFDs), Proposed Specification Change Notices, and Master Government Furnished Equipment

Lists within the V-22 Program Office are based on the policy and guidance defined in NAVAIRINST 4130.1 series, AFI 21-101, AFI 63-1101, and this CMP.

5.2 OBJECTIVE

The objective of the Configuration Control process is to ensure effective planning, thorough review/processing, and timely implementation of approved engineering changes.

5.3 CONFIGURATION CHANGE PROCESS

The configuration change process involves change preparation, submittal, review, approval, contract modification, update to the baseline documentation, and installation. Included in the change process are problem identification, requirements definition, proposed solution, change development, change approval, authorization, testing, validation, verification, and implementation.

5.3.1 LEVEL 2 CHANGE BOARD

The Level 2 Change Board (L2CB) provides a detailed technical and logistical review of proposed changes prior to their presentation at Change Review Board (CRB). The board also reviews and dispositions technical oversight issues, minor deviations, and Class II changes brought forward by either the contractor or Defense Contract Management Agency (DCMA).

In-scope changes to CIs that occur after CDR but prior to delivery of the first production unit will be presented to the L2CB for approval to update the baseline documentation.

The L2CB is co-chaired by the Configuration Manager, Product Support Team Lead (PSTL), Lead Deputy Assistant Program Manager Systems Engineering (LDAPMSE), and Level 2 IPTs.

It is supported by various engineering disciplines and logistics element managers from the government and industry as required.

5.3.2 CHANGE REVIEW BOARD

The CRB provides a programmatic, technical, logistical, and business review of proposed configuration changes and deviations. The board is chaired by the Level 1 IPT leads, facilitated by the V-22 Configuration Manager, and is supported by Level 2 IPTs, engineering, logistics, contracts, financial, test, and training representatives from government and industry.

5.3.3 V-22 DECENTRALIZED CHANGE CONTROL BOARD

The approved DCCB Charter is to be exercised in accordance with NAVAIRINST 4130.1 series as modified by this CMP.

5.3.3.1 MEMBERSHIP OF THE V-22 DCCB

DCCB members shall have full authority to address all issues for items under their cognizant area of expertise with assistance from their competency as deemed appropriate. Voting members occupying the billets identified below will sign the 4130/1 signifying their concurrence with the proposed change.

Voting members are:

Chairperson PMA-275 Program Mgr/Deputy Program Mgr MV IPT MV IPT Co-Leads

CV IPT CV IPT Lead/Deputy Engineering V-22 Chief Engineer/LDAPMSEs or designated rep Logistics V-22 PSM/PSTLs or designated rep Contracts V-22 Procurement Contracting Officers

Full-Time Associates are:

In-Service IPT In-Service IPT Lead/Deputy Test and Evaluation V-22 Test and Evaluation Manager Training V-22 Training IPT Lead/Deputy Finance V-22 Business Financial Manager Configuration Management V-22 Configuration Manager Level 2 IPTs Level 2 IPT Leads/Deputies Production Production Lead/Deputy

5.3.3.2 RESPONSIBILITIES OF THE V-22 DCCB VOTING MEMBERS

5.3.3.2.1 CHAIRPERSON

The Program Manager (PM)/Deputy Program Manager (DPM) or designee is responsible for chairing the DCCB and exercising final approval/disapproval authority for Class 1 ECPs, Supplemental Procurement Requests, RFDs, and RAMECs. The chairperson shall ensure that all DCCB members have an opportunity to review each proposed change. When necessary the chairperson may direct members to provide additional information for full consideration of a proposed change action. The chairperson holds final signature authority for approval and implementation of any proposed change.

5.3.3.2.2 LEVEL 1 IPT LEADS

The MV/CV IPT Leads are responsible for coordinating the development and presentation of information relating to their specific variant, supporting overall program objectives, ensuring retrofit is addressed, and assessing the impacts/benefits to their respective user communities.

The MV IPT Co-Leads are designated to chair the DCCB in the absence of the PM/DPM.

5.3.3.2.3 ENGINEERING

The engineering representative is responsible for ensuring the change is technically sound;

requirements are identified, complete, and well understood; performance/capability will meet the specified requirements; test plan is executable; and appropriate technical reviews are scheduled in accordance with NAVAIRINST 4355.19D. The V-22 Chief Engineer is responsible for the coordination, documentation, and resolution of all engineering issues.

5.3.3.2.4 LOGISTICS

The logistics representative is responsible for ensuring the change is supportable and that all logistics/sustainment requirements have been met. The PSM is responsible for the coordination, documentation, and resolution of all logistics/sustainment issues.

5.3.3.2.5 CONTRACTS

The PCO is responsible for coordinating the necessary Defense Contract Audit Agency audits, reviewing the technical evaluation, and providing contractual expertise/support in executing program requirements as documented on the DCCB approved 4130 forms.

5.3.3.3 RESPONSIBILITIES OF THE V-22 DCCB FULL-TIME ASSOCIATES

5.3.3.3.1 IN-SERVICE IPT

The In-Service IPT is responsible for ensuring the retrofit portion of changes are properly scheduled, executable, and coordinated with the Type Commander/Major Command.

5.3.3.3.2 TEST AND EVALUATION

The Test and Evaluation Manager is responsible for ensuring that each proposed change identifies all flight test requirements, addresses all applicable flight test aircraft, includes adequate funding for required flight test, and addresses impacts to flight test resources.

5.3.3.3.3 TRAINING

The Training IPT Lead/Deputy is responsible for verifying that each proposed change identifies and addresses all impacts to operator/maintenance training and trainers and for the coordination, documentation, and resolution of all training issues.

5.3.3.3.4 FINANCE

The Business Finance Manager is responsible for determining that all funding requirements are in accordance with applicable directives and that adequate funding is available to execute the change.

5.3.3.3.5 CONFIGURATION MANAGER

The V-22 Configuration Manager is responsible for keeping DCCB membership informed of NAVAIR policy and procedures as documented in NAVAIRINST 4130.1 series and for coordinating the review and disposition of changes in accordance with applicable directives. The Configuration Manager shall coordinate the preparation of DCCB documentation and monitor all V-22 changes from initial identification through final disposition. The V-22 Configuration Manager or designee, as the DCCB Secretariat, is responsible for conducting a final review of all items submitted for consideration by the DCCB to ensure a thorough review by all stakeholders has been accomplished, the change package is complete, all issues have been resolved, and the change is suitable for presentation to the DCCB. When necessary, the Secretariat may direct members to provide additional information for clarification or correctness.

5.3.3.3.6 LEVEL 2 IPT LEADS

The Level 2 IPT Leads are responsible for validating the need for the change, verifying that retrofit requirements have been addressed, ensuring the technical evaluation is complete and thorough, and for executing the change throughout it life cycle.

5.3.3.3.7 PRODUCTION

Ensure incorporation of all aircraft ECPs are properly planned, supported, and executed in accordance with the applicable production contract.

5.4 ENGINEERING CHANGE PROPOSALS

ECPs will be the standard method for proposing changes to a CI and associated baseline documentation. ECPs will be prepared and submitted in accordance with the applicable CDRL or Request for Proposal using MIL-HDBK-61A and ANSI/EIA-649 as guidance.

Updates to ECPs that do not result in a change in scope (e.g. effectivity changes, adding retrofit recurring information) may be processed as administrative changes rather than revisions.

5.4.1 CLASSIFICATION OF ECPs

Engineering changes will be classified as Class 1 or Class 2 in accordance with MIL-HDBK- 61A.

5.4.2 REVIEW AND DISPOSITION OF CLASS I CHANGES

All Class 1 changes affecting the V-22 Weapon System, to include support equipment and trainers, must be reviewed and approved by the V-22 DCCB prior to contractual authorization or implementation.

Other PMAs initiating or processing ECPs that affect the V-22 will ensure the change is effective for both the MV and CV variants when applicable. The change will be submitted to the PMA- 275 Configuration Manager via ePower for approval by the PMA-275 DCCB. If production aircraft are impacted PMA-275 will initiate an ECP with Bell Boeing.

5.4.3 REVIEW AND DISPOSITION OF CLASS 2 CHANGES

Proposed Class 2 changes (Contractor and supplier) shall be submitted to the government for review and concurrence with the classification prior to incorporation. Concurrence with Class 2 changes will normally be provided by the local DCMA representative. DCMA shall consider critical characteristic when reviewing Class 2 changes in accordance with NAVAIRINST 4200.25D paragraph 6a(2). If there is disagreement between the contractor and DCMA as to the classification the change will be presented to the PMA-275 L2CB for disposition.

5.5 DEVIATIONS

A deviation is a written authorization, prior to, during, or after the manufacture of a hardware or software CI, to depart from the performance or design requirement of a specification, drawing, ECP, or other contractual document for a specified number of items or period of time.

5.5.1 CLASSIFICATION OF DEVIATIONS

Deviations shall be designated as critical, major, or minor in accordance with the criteria provided in MIL-HDBK-61A.

5.5.2 REVIEW AND DISPOSITION OF DEVIATIONS

The contractor shall submit all critical or major RFDs, including a business case that supports the contractor’s recommended withhold, to PMA-275 for review and disposition by the DCCB.

Minor RFDs will be dispositioned by the local DCMA representative. DCMA shall consider critical characteristic when reviewing minor RFDs in accordance with NAVAIRINST 4200.25D paragraph 6a(2). Any minor RFD disapproved by DCMA may, at the contractor’s discretion, be submitted to PMA-275 as a critical or major RFD.

5.6 AIR FORCE MODIFICATIONS

The Air Force has two types of modification, temporary and permanent, which are described in

AFI 63-131.

5.6.1 TEMPORARY MODIFICATIONS

Temporary modifications change the configuration of an item to enable short-term operational mission accomplishment or to conduct test and evaluation of new and modified equipment.

There are two kinds of temporary modifications: Temporary-1 and Temporary-2 (aka T-1 and T- 2).

5.6.2 PERMANENT MODIFICATIONS

Permanent modifications change the configuration of an asset to effect a lasting improvement in the operational effectiveness, suitability, survivability, safety, and/or ownership costs of a fielded weapon system, subsystem, or item.

5.7 TECHNICAL DIRECTIVES / TIME COMPLIANCE TECHNICAL ORDERS

TDs/TCTOs will be issued to provide direction for implementing and documenting one-time inspections, retrofit changes, and the retrofit parts of combined forward-fit and retrofit changes.

The TD/TCTO process will be accomplished in accordance with NAVAIRINST 4130.1 series, AFI 21-101, NAVAIR 00-25-300, T.O. 00-5-1, T.O. 00-5-2, T.O. 00-5-15, and the MOA (Attachment II).

TDs issued by other PMAs that affect V-22 will include the applicable Unified Numbering System (UNS). If the TD affects CV-22 it will include the TCTO number, data code, and additional Air Force specific information which will be provided by the PMA-275 CM team.

5.8 CHANGE INITIATION AND STAFFING

The process for initiating a change to the V-22 Weapon System is documented in operating instruction PMA275-OI-CM01. Procedures for processing and staffing an ECP are documented in PMA275-OI-CM04. Procedures for processing and staffing RAMECs are documented in PMA275-OI-CM02. These operating instructions are located on the CM Sub-site in SharePoint.

6 CONFIGURATION STATUS ACCOUNTING

6.1 PURPOSE

Configuration Status Accounting (CSA) is the recording and reporting of information required to manage the configuration effectively, including development, production, and retrofit of the approved configuration item, status of proposed changes to the configuration baseline, and the implementation status of approved changes.

6.2 CONFIGURATION STATUS ACCOUNTING SYSTEM

PMA-275 will utilize a Microsoft Access based CSA database to track the status of all DCCB approved ECPs, RFDs, and RAMECs.

6.3 CONTRACTOR(S) CSA SYSTEM

Contractor(s) shall implement/maintain a CSA system. As a minimum, the CSA system shall:

• Identify the current approved configuration documentation.

• Record and report the status of contractor proposed engineering changes from initiation to final approval and contractual implementation.

• Record and report the results of configuration audits to include the status and final disposition of identified discrepancies.

• Record and report the status of all critical and major RFDs.

• Record and report implementation status of authorized changes.

• Provide the traceability of all changes from the original baseline configuration documentation of each CI.

• Provide the above required information to the government upon request.

7 DATA MANAGEMENT

7.1 PURPOSE

Data Management governs and controls the selection, generation, preparation, acquisition, and use of data imposed on contractors.

7.2 OBJECTIVE

To acquire the minimum amount of data that meet the needs of the program.

7.3 DATA REQUIREMENTS

As part of the development of a SOW each functional discipline shall identify and justify their minimum set of data requirements for that contract to the Level 2 IPT Lead. Types of data to be ordered include all the administrative, management, financial, scientific, engineering, and logistics information required to manage, operate, and support the V-22 Weapon System.

Specific delivery and acceptance requirements shall be stipulated on the DD Form 1423.

Data being ordered shall be delivered, accessed, inspected, and accepted per the FAR, DFARS, and the applicable contract requirements. The inspection and acceptance requirements cited in the contract apply regardless of method of delivery.

7.4 DATA DELIVERY

Data will be delivered electronically to the PMA-275 web-based CDRL database in accordance with the applicable contract. The Data Manager will route the deliverable to the appropriate IPT or functional discipline for use, review, or approval/disapproval.

7.5 DATA PROTECTION

All data deliverables shall include distribution statements in accordance with DoDI 5230.24 to aid in proper handling. Data containing information subject to restrictions will be marked in accordance with DFARS Part 252.227-7013. Access to delivered data will be limited to government personnel or PMA-275 support contractors having a valid non-disclosure agreement.

7.6 DATA REQUIREMENTS REVIEW BOARD

The Data Requirements Review Board will be accomplished as part of the Procurement Initiation Document (PID) process. Draft CDRLs will be loaded in the Procurement Management Tool as supporting documents for each applicable PID. For acquisition efforts with a dollar value of less than $10 million this will constitute the Data Requirements Review Board (DRRB). Once the PID is reviewed and approved by all stakeholders the IPTL or Assistant Program Manager responsible for the effort will sign the “APPROVED BY” block of DD Form 1423. A formal DRRB will be held for acquisition efforts greater than $10 million or as directed by the Level 1s due to the complex nature of the effort. The formal DRRB will be chaired by the Level 1 IPTLs or their designees.

Further guidance for conducting a formal and informal DRRB will be captured in operating instruction PMA275-OI-CM06.

A. APPENDIX

CM MAJOR MILESTONES

CM MAJOR MILESTONES

MILESTONE CHART: Major Milestones used in establishing and executing CM for PMA- 275 V-22 Weapon System are listed below as they are determined.

MILESTONES DATE

MV-22 Preliminary Design Review (PDR) December 1997 CV-22 PDR June 2003 MV-22 Critical Design Review (CDR) December 1998 CV-22 CDR March 2004 MV-22 Functional Configuration Audit (FCA) December 1999 MV-22 Physical Configuration Audit (PCA) February 2000 MV-22 Block A PCA November 2004 MV-22 Block B, CV-22 Block 0/10 PCA July 2007 MV-22 Block C FCA TBD MV-22 Block C PCA December 2013 CV-22 Block 20 PCA TBD

B. APPENDIX

ACRONYMS

ACRONYMS

A AFI Air Force Instruction AFPD Air Force Policy Directive AFSOC Air Force Special Operations Command ANSI American National Standards Institue APML Assistant Program Manager Logistics ASCM Authorized Software Configuration Matrix

C CDR Critical Design Review CDRL Contract Data Requirements List CI Configuration Item CM Configuration Management CMP Configuration Management Plan CRB Change Review Board CSA Configuration Status Accounting CV Air Force Variant

D DCCB Decentralized Change Control Board DCMA Defense Contract Management Agency DoD Department of Defense DoN Department of Navy DPM Deputy Program Manager DRRB Data Requirements Review Board

E ECP Engineering Change Proposal

F FCA Functional Configuration Audit FST Fleet Support Team

G GEIA Government Electronics & Information Technology Association

I IPT Integrated Product Team

L L2CB Level 2 Change Board LDAPMSE Lead Deputy Assistant Program Manager Systems Engineering

M MOA Memorandum of Agreement MV Marine Corps Variant MIL-STD Military Standard

N NAVAIR Naval Air Systems Command NAVAIRINST Naval Air Systems Command Instruction

P PCA Physical Configuration Audit PCO Procurement Contracting Officer PDR Preliminary Design Review PID Procurement Initiation Document PM Program Manager PMA Program Manager, Air PSM Product Support Manager PSTL Product Support Team Lead

R RFD Request for Deviation

S SOW Statement of Work

T TCTO Time Compliance Technical Order TD Technical Directive

U USSOCOM United States Special Operations Command

ATTACHMENT I

ATTACHMENT II

10010 Ser PMA275/129-14

MEMORANDUM OF AGREEMENT

BETWEEN

NAVAIR PMA-275

AND

AIR FORCE SPECIAL OPERATIONS COMMAND

Subj: MEMORANDUM OF AGREEMENT FOR V-22 JOINT TD/TCTO PROCESS

Ref: (a) NAVAIR 00-25-300, NAVAL AIR SYSTEMS COMMAND TECHNICAL

DIRECTIVES SYSTEM

(b) TO 00-5-15, AIR FORCE TIME COMPLIANCE TECHNICAL ORDER PROCESS

(c) TO 00-20-2, MAINTENANCE DATA DOCUMENTATION (USAF)

Encl: (l) TD/TCTO Compliance and Transmittal Requirements

(2) TD/TCTO Examples

(3) Process Flow Chart

1. Purpose: To define the roles, responsibilities, and authorities of the Naval Air Systems Command (NAVAIR) V-22 Program Office, Program Manager, Air-275 (PMA-275) MV/CV-22 In-Service Integrated Product Team (IPT), Headquarters, Air Force Special Operations Command (HQ AFSOC), Naval Air Warfare Center Aircraft Division (NAWCAD) Lakehurst, and the V-22 Fleet Support Team (FST) for the authoring and distribution of joint Technical Directives (TD) and Time Compliance Technical Orders (TCTO).

2. Background: The V-22 fleet is comprised of two unique service variants, the MV-22 assigned to the USMC, and the CV-22 assigned to the USAF. It is necessary to provide a TD/TCTO process that meets the needs of both services. A TD is the vehicle for implementing and documenting one-time inspections and/or configuration changes to the V-22 weapon system which includes aircraft, components, engines, trainers, and support equipment. A TCTO is the USAF equivalent to a TD.

3. Scope: A joint format combining the necessary elements of both a TD and TCTO will be authored and distributed to fleet users for common and unique MV/CV-22 modifications or inspections as well as MV/CV-22 modifications or inspections. The Established joint compliance timeframes are shown in Enclosure (1). Joint TD/TCTO example documents are provided in Enclosure (2) and the TD/TCTO Process flow chart are listed in Enclosure (3). Any waivers necessary by the services’ policy organizations will be coordinated and signed to allow this joint format process that will meet the intent of references (a), (b) and (c).

DRAFT

4. Agreement:

a. V-22 Fleet Support Team: V-22 FST TD/TCTO responsibilities include but are not limited to:

(1) Reviewing Federal Aviation Administration (FAA) Airworthiness Directives (ADs), Air Force TCTOs, and Manufacturer Service Bulletins/Advisories for applicability to aircraft systems and related systems. When applicable to aircraft systems, FST shall initiate processing for compliance in accordance with the procedures in the reference (a), with the addition of pertinent Air Force information to make a Joint TD/TCTO.

Documents issued in this manner require the same concurrences and approvals as comparable NAVAIR TDs and shall be issued with NAVAIR TD, Air Force TCTO numbers, and Air Force data codes.

(2) Keeping Program Manager, Air (PMA), Assistant Program Manager for Support Equipment (APMSE), Assistant Program Manager for Logistics (APML), Logistics Managers (LMs), and Naval Aviation Command Management Information System- Optimized Organizational Maintenance Activity (NALCOMIS OOMA)/ Configuration Management Information System-Base Line Manager (CMIS BLM) informed of anticipated and pending bulletins. Preparing proposed bulletins and submitting them to cognizant PMAs or LMs. Releasing bulletins (except grounding or potentially grounding) when authorized and identified as a certified/trusted source by PMA.

(3) Preparing and submitting proposed change TD/TCTOs when requested by PMAs or APMLs/LMs.

(4) Coordinating with the APML, Naval Air Technical Data and Engineering Service Command (NATEC), and NAVAIR Logistics for TD/TCTO numbers, Data Codes, and/or USMC/USAF Kit Identification Number (KIN) assignment.

(5) Coordinating with NAVAIR Logistics Production Data Division, Air Force Sustainment Center (AFSC) or its subordinate units, or other Department of Defense (DoD)/government or Contractor item managers and inventory control points to determine the need for companion and commodity type TD/TCTOs and author, distribute and manage these TD/TCTOs.

(6) Using organizational email boxes to coordinate with the USAF Major Command (MAJCOM) and Wing/Group Technical Order Distribution Office (TODO) and Plans and Scheduling offices to ensure timeliness of compliance and/or rescission of TD/TCTOs and Interim TD/TCTOs.

(7) Coordinating with Reliability and Maintainability Information System (REMIS) Program Management Office to ensure the V-22 FST is provided proper training, and access to utilize the REMIS website to perform necessary TD/TCTO related tasks.

(8) Initiating and supporting any required Navy and Marine Corps Intranet (NMCI) Certification and Accreditation (C&A) process of any hardware/software used in the performance of these tasks including any Air Force software, as required. Utilize existing certified hardware and software and websites or USAF certified websites for these TD/TCTO process tasks.

(9) Ensuring V-22 TD/TCTOs for aircraft/engine/components are loaded in NALCOMIS-OOMA and REMIS.

b. V-22 Support Equipment In-Service Support Center (SE ISSC): V-22 SE ISSC TD/TCTO responsibilities include but are not limited to:

(1) Reviewing FAA Airworthiness Directives (ADs), Air Force Time Compliance Technical Orders (TCTOs), and Manufacturer Service Bulletins/Advisories for applicability to Support Equipment (SE) for aircraft systems and related systems.

When applicable to aircraft systems, ISSC shall initiate processing for compliance in accordance with the procedures in the reference (a), with the addition of pertinent Air Force information to make a Joint TD/TCTO. Documents issued in this manner require the same concurrences and approvals as comparable NAVAIR TDs and shall be issued with NAVAIR TD numbers with addition of USAF assigned TCTO numbers and TCTO Data Codes.

(2) Keeping PMA, APMSEs, APMLs, LMs, and NALCOMIS OOMA/CMIS BLM informed of anticipated and pending bulletins. Preparing proposed bulletins and submitting them to cognizant PMAs or LMs. Releasing bulletins (except grounding or potentially grounding) when authorized and identified as a certified/trusted source by PMA.

(3) Preparing and submitting proposed change TD/TCTOs when requested by PMAs or APMLs/LMs.

(4) Coordinating with the V-22 FST, APML, NATEC, and NAVAIR Logistics for TD/TCTO numbers and/or USMC/USAF KIN assignment.

(5) Initiating procurement of appropriate kits for SE changes and coordinating receipt of kits for tracking control at Lakehurst. Once kits are received at the Lakehurst Staging Facility, they will be sent to the central kitting facility designated by PMA-275 for distribution to the fleet activities.

(6) Coordinating with NAVAIR Logistics Production Data Division, USAF Air Logistics Complexes (ALC), or other DoD/government or Contractor item managers and inventory control points to determine the need for companion and commodity type TD/TCTOs and author, distribute and manage these TD/TCTOs.

(7) Coordinating Validation/Verification of SE by government and fleet individuals prior to PMA 275 approval for release of the TD/TCTO.

(8) Coordinating with the USAF MAJCOM and Wing/Group TODO and Plans and Scheduling offices to ensure timeliness of compliance and/or rescission of TD/TCTOs and Interim TD/TCTOs.

c. HQ AFSOC: HQ AFSOC responsibilities include but are not limited to:

(1) Coordinating with the Wing/Group TODO and Plans and Scheduling offices to ensure timeliness of TD/TCTO verifications.

(2) Providing timely compliance and/or rescission of TD/TCTOs and Interim TD/TCTOs.

(3) Ensuring the V-22 FST is provided proper training and access to utilize the REMIS website to perform necessary TD/TCTO related tasks.

(4) Defining current organizational email boxes necessary to communicate TD/TCTO related activities.

d. PMA-275: PMA-275 responsibilities include but are not limited to:

(1) PMA-275 has overall responsibility for all aspects of the efforts to satisfy the above stated requirements for the joint TD/TCTO process :

(2) Configuration and change management of program office approved V-22 modifications and inspections to include those related to engines, trainers, and Support Equipment.

(3) Identify, as part of the Engineering Change Proposal (ECP), procurement requirements of modification kits with the Contractor through the normal acquisition process with all parties involved.

(4) Perform as the focal point for resolving process problems with appropriate agencies.

(5) Coordinate with the lead Type Commander (TYCOM)/MAJCOM Plans, Programs and Acquisition/Requirements Directorate and the Logistics Directorate to ensure Work Load Agreements are developed and coordinated on at the Wing/Group levels for proper support and scheduling of trial install, kit proof, installs, and formal inspection TD/TCTOs.

(6) Develop, distribute, and maintain a Familiarization Guide to acquaint the USAF CV- 22 community with use of the NATEC system and V-22 joint TD/TCTO processes.

e. No additional funding will be required for tasks in support of this MOA.

5. Effective Date: This agreement will become effective upon approval by all stakeholders.

This agreement shall remain in effect throughout the lifecycle of the V-22 and will be reviewed annually by all signatory agencies. PMA-275 Configuration Management will ensure this review is accomplished by all the necessary parties in advance of expiration of the current document.

Enclosure 1, TD/TCTO Compliance and Transmittal Requirements

TD/TCTO COMPLIANCE AND

TRANSMITTAL REQUIREMENTS

TD/TCTO Category USAF Requirement USN Requirement PMA-275 Requirement

Immediate Action Immediate Prior to next use or flight

Immediately or Prior to next use or flight

Urgent Action 1-10 Days >10 FH but < next scheduled maint period

>10 FH but < next scheduled maint period

Routine Action 90-270 Days Next scheduled maint Period.

(Phase/Calendar, etc)

Next scheduled maint Period.

(Phase/Calendar, etc)

Interim Transmitted immediately via message

Transmitted immediately via message

Transmitted immediately via message

Enclosure 2, Example 1 TD/TCTO Change

ROUTINE ACTION

DEPARTMENT OF THE NAVY

NAVAL AIR SYSTEMS COMMAND

RADM WILLIAM A MOFFETT BUILDING

47123 BUSE ROAD, BLDG 2272

PATUXENT RIVER, MD 20670-1547

Cognizant Code(s): PMA 275/AIR 4.1.1/6.6.1.7 Data Code: XXXXXXX Issue Date: 14 January 2014

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government agencies and their contractors to protect publications required for official use or for administrative or operational purposes only, effective (See Issue Date). Other requests for the document shall be referred to Commander, Naval Air Systems Command, PMA-275, RADM William A Moffett Bldg, 47123 Buse Road, Bldg 2272, Patuxent River, MD 20670-1547.

DESTRUCTION NOTICE: For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

V-22 AIRFRAME CHANGE NO. XXX

(TD CODE 50)

TCTO 1V-22(C)B-XXX

SUBJECT: 13 NACELLE RIBBON HARNESSES WITH CONVENTIONAL HARNESSES,

REPLACEMENT OF (UNS 1000000)

REFERENCES: (a) Bell-Boeing Engineering Change Proposal, ECP V-22-0XXX, Dated XX August 2012

ENCLOSURES: Not Applicable.

DOCUMENTATION AFFECTED:

1. A1-V22AB-TIS-000/T.O. 1V-22(C)B-2-DB-1

of 21 March 2014

V-22 Technical Information System, Organizational Maintenance

PURPOSE OF DIRECTIVE: \

APPLICATION:

1. BASIC EQUIPMENT:

a. The following basic equipment shall be modified by service activities:

QTY TYPE/MODEL/SERIES SERIAL/TAIL NUMBER

Xx MV-22B BUNOs Xx CV-22B Tail Numbers

2. TRAINERS: Not Applicable.

3. SPARES: Not Applicable.

COMPLIANCE:

1. BASIC EQUIPMENT: Compliance by organizational level maintenance activities and above per the following schedules:

a. MV-22B:

Equipment Maintenance Level CY J F M A M J J A S O N D

Basic Organizational 14 00 00 00 00 00 00 00 00 00 00 00 00

b. CV-22B:

Equipment Maintenance Level CY J F M A M J J A S O N D

Basic Organizational 14 00 00 00 00 00 00 00 00 00 00 00 00

MAN-HOURS REQUIRED:

1. BASIC EQUIPMENT:

a. MV-22B:

b. CV-22B:

SUPPLY DATA:

1. REQUIREMENTS FOR BASIC EQUIPMENT:

a. Kits Required:

KIN KIT NO. NO. OF MEN SKILL TOTAL MAN-HOURS

9159LKA145913V2 A1

MOS 6156,

Tiltrotor Airframes

Mechanic

8.0

KIN KIT NO. NO. OF MEN SKILL TOTAL MAN-HOURS

9159LKA145913V2 A1 2 AFSC 2A6X5,

Aircraft Hydraulic Systems

8.0

QTY PART NO. CAGE NOMEN SM&R…