RFP_Attachment_18-TOLCMP_A-10.pdf

A-10C

TECHNICAL ORDER LIFE CYCLE MANAGEMENT PLAN

(TOLCMP)

UNITED STATES AIR FORCE

A-10

THUNDERBOLT II

TECHNICAL ORDER MANAGEMENT PLAN (TOLCMP)

ORGANIZATIONAL/INTERMEDIATE/DEPOT

NOTE

The TOLCMP is an important management tool which is mandatory for major programs (TO 00-5-3) and should be considered for ALL programs. The TOLCMP provided herein may be tailored and used for any program. A-10 program-specific TOLCMP containing these requirements may be developed separately.

PREPARED BY: Len Mian/AFLCMC/WWAL/586-7150

DATE: 25 Feb 2014

Rev. 1.0

TABLE OF CONTENTS

PARAGRAPH NUMBER TITLE

1 INTRODUCTION

2 POLICY

3 PURPOSE

4 PROGRAM SUMMARY

4.1 Description

4.2 Operational Concept

4.3 Maintenance Concept

5 REFERENCE MATERIAL

6 DEFINITIONS

7 RESPONSIBILITIES

7.1 Technical Order (TO) Manager

7.2 Using Commands

7.3 Air Logistics Centers (ALCs)

7.4 Air Education and Training Command (AETC)

8 SCOPE OF TECHNICAL ORDER REQUIREMENTS

8.1 General

8.2 Technical Orders To Be Developed

9 ACQUISITION PROCESS

9.1 Segment Efforts

9.2 Delivery Options

9.3 Technical Order Preparation

9.3.1 Development Flow

9.3.2 Specification Interpretation, Deviations, and Waivers

9.3.3 Reviews

9.3.4 Quality Assurance

9.3.5 Verification

9.3.6 TO Security and Information Assurance

9.3.7 Configuration Control

9.3.8 Updates and Update Information

9.3.9 Formalization

9.4 Maintenance of TOs

9.5 Management of TCTOs

9.6 Schedules

9.7 Financial Plan

Attachments:

Attachment 1 Technical Order Life Cycle Verification Plan

(To be added at least 120 days prior to the first TO verification event)

Attachment 2 TO Listing

1 INTRODUCTION. This plan describes the management approach to acquire Technical Orders (TOs) for the A-10C program. The plan amplifies the TO portions of the Life Cycle Management Plan (LCMP). The plan outlines management responsibilities, program establishment, program guidelines, implementation procedures and initiatives. This plan was developed by the TO Manager, (Len Mian, AFLCMC/WWAL) and is based on the most current information available at the time of publication.

2 POLICY. The A-10C program TOs will be acquired in the most economical manner without sacrifice of accuracy, quality or adequacy. All TOs will be developed and tailored to meet the needs of the user. The TO Manager (Len Mian) is the

Program Manager (PM) focal point on all TO matters.

3 PURPOSE. This plan provides management policy, assigns responsibilities, defines terminology and specifies procedures for the A-10C program. This plan provides basic instructions for development, contractor Quality Assurance (QA), verification and formalization of A-10C program TOs during the program acquisition phase, and maintenance of the TOs after formalization. This plan applies to all acquisition activities, including those at using command bases, Product Centers, ALCs and contractor/subcontractor facilities. This plan was developed in accordance with requirements of TO 00-5-3.

4 PROGRAM SUMMARY.

B.4.1 Weapon System Description. The A-10 Thunderbolt II is a single-seat, twin-engine, straight-wing jet aircraft developed by Fairchild-Republic. The A-10 was designed for a United States Air Force requirement to provide close air support (CAS) for ground forces by attacking tanks, armored vehicles, and other ground targets with a limited air interdiction capability.

B.4.2 Operational Concept. The A-10 is an essential component of successful air operations, and represents a significant percentage of the CAF force structure with over 350 aircraft in service. The weapon system’s attributes include excellent low speed maneuverability, high weapons payload, long loiter time, very high tolerance to battle damage, and the lowest cost per flying hour of any CAF fighter. As demonstrated during the Persian Gulf War, it is the USAF’s most effective CAS and anti-armor platform. The A-10’s primary mission elements are close air support (CAS), forward air controller (airborne)

(FAC(A)), air interdiction (AI), counterair (CA), and combat search and rescue (CSAR). The A-10 will remain in service to the year 2040.

B.4.3 Maintenance Concept. Maintenance support for the A-10 aircraft was originally designed around the three-level maintenance concept. It is currently a mixture of two and three levels of maintenance depending on the skills required, support equipment required, and complexity of the item.

5 REFERENCE MATERIAL:

A-10 Technical Order Life Cycle Verification Plan (TOLCVP)

A-10 Technical Order Process Plan (TOPP)

Integrated Master Schedule (IMS)

6 DEFINITIONS: Update as needed.

7 RESPONSIBILITIES:

7.1 TO Manager: The TO Manager will:

7.1.1 Prepare and distribute a draft TOLCMP and TO program inputs to the RFP to all organizations associated with the A-

10C program system acquisition program as required by TO 00-5-3.

7.1.2 Call and chair the TO Planning/Requirements Conference with representatives from the using command, ALC, and other affected agencies to finalize and approve the TOLCMP and initial RFP/contract inputs for TO acquisition. These participants constitute the initial membership in the TO Integrated Product Team (IPT). After contract award, the contractor representatives will become part of the team. Review TM performance specifications and standards (TMSS) for operational compatibility and adequacy to support program acquisition. Ensure special or unique requirements (TO 00-5-3, Chapter 4) are included in the contract. Following the conference, provide input as required to the program Statement of Objectives

(SOO), Instructions to Offerors (ITO) and Evaluation Criteria, partly-tailored TMCR and CDRL for the RFP.

7.1.3 Participate in source selection and proposal reviews, and contract negotiations if required. Ensure the final contract meets all requirements of the RFP regarding TOs.

7.1.4 Conduct and chair all TO conferences, meetings, reviews, and other joint agency efforts related to the program during acquisition. Ensure all participating organizations are invited as far in advance of scheduled reviews as possible.

Request organizations to provide the same personnel to participate in reviews, thus ensuring continuity of effort.

(Requirements for AF review team personnel are prescribed in TO 00-5-3, Chapter 9 and Chapter 11.) Arrange for

Contracting Officer representation during guidance conferences and meetings where matters which could affect the scope of the contract will be discussed. Ensure copies of specifications, exhibits, directives, policy documents, and other references are furnished in sufficient time to allow familiarization by the participants prior to the review.

7.1.4.1 Develop an event-phased schedule with the contractor for review of TOs.

7.1.4.2 Ensure that the contractor records and distributes minutes of meetings, noting all required actions and responsible agency action, and takes necessary action to effect required changes.

7.1.4.3 At IPRs, ensure manuals being reviewed comply with all contractual requirements, applicable specifications, standards, exhibits, maintenance plans, provisioning and source coding actions. Clarity, reading grade level of writing, consistency, adequacy, and accuracy will be stressed.

7.1.5 Arrange for government participation in the contractor QA program.

7.1.6 Establish and chair the Technical Order Review Board (TORB).

7.1.7 Establish and manage a verification program by (or “IAW the TO Verification Plan”):

7.1.7.1 Requiring identification and submission of those organizational level operational and maintenance tasks on mission equipment that must be verified prior to releasing the TOs to the operating command. This same procedure shall also be followed on intermediate and depot level TOs making use of complex support equipment on advanced technology subsystems/commodities.

7.1.7.2 Developing, coordinating, and publishing, in conjunction with all participating commands and affected agencies, a detailed verification plan not later than 120 days prior to the start of the first scheduled verification. The coordinated and approved plan will become an appendix to this document.

7.1.7.3 Developing basic requirements and schedules to ensure that TOs are verified, corrected, and published in time to permit the distribution of verified preliminary or formal TOs to operating units before or concurrent with delivery of the system/commodity.

7.1.7.4 Requesting technically qualified personnel from the operating and supporting commands to accomplish the verification. Coordinate the verification effort with the contractor and arrange for contractor support as required.

7.1.7.5 Informing all activities directly concerned with verification as far in advance as possible when each verification effort will begin.

7.1.7.6 Appointing a Verification Team Manager to ensure that:

7.1.7.6.1 Support equipment is available to support the verification.

7.1.7.6.2 Necessary hardware (i.e., test equipment, support equipment, consumables and inert munitions) is available to support the verification.

7.1.7.6.3 Instructions can be used to operate and maintain the system and/or commodity.

7.1.7.6.4 Information reflects the latest configuration of the system and/or commodity delivered to the user.

7.1.7.6.5 Current safety criteria are met.

7.1.7.6.6 Updates are accomplished on a “fast reaction” basis (TO 00-5-3, Chapter 11) and restricted to those of a technical nature which affect accuracy of operations and maintenance procedures. Editorial updates will be made only when the errors affect understandability.

7.1.8 Conduct post-publication reviews as determined necessary.

7.1.9 Place follow-on requirements on contract.

7.1.10 Provide a status report of scheduled TO events.

7.2 Using Commands. Using Command(s) (specify) will:

7.2.1 Assist the TO Manager by verifying that arrangement of material and method of presentation are commensurate with the established maintenance concept, and the skills and training of personnel planned to operate and maintain the equipment.

7.2.2 Provide qualified personnel as requested by the TO Manager to support TO reviews and verifications. Personnel must have signatory authority for on-site decisions. The MAJCOM may delegate the authority to the TO Manager or to command assets assigned to the test activity or operating wing to preclude delays in TO development. During early contractor guidance conferences and first look in-process reviews, support should be 7-9 level enlisted personnel or civilian equivalent. For second look IPR and membership on the verification team, personnel should be of the lowest grade and skill level (5-level minimum) expected to operate the equipment, as well as the representative(s) attending the other reviews.

7.2.3 Provide other support required for verification of TOs in accordance with plans and schedules established by the TO

Manager.

7.2.4 Report safety or personnel hazard conditions to the TO Manager.

7.2.5 Continually review preliminary TOs to detect errors, deficiencies, and obsolete or nonessential material and report problems to the TO Manager.

7.2.6 Identify TOs which require post publication reviews to the TO Manager.

7.3 Air Logistics Centers. Air Logistics Centers (ALCs) will:

7.3.1 When NOT the acquisition agency, assist the acquisition TO Manager as requested to ensure adequacy of established TO development program.

7.3.2 Attend in-process reviews, verification and pre-publication reviews in accordance with jointly-established schedules, providing guidance throughout the development cycle to facilitate transition of adequate, timely, economical and operationally suitable TOs at system maturity.

7.3.3 Continually review preliminary TOs to detect errors, deficiencies, and obsolete or nonessential material and report problems to the TO Manager.

7.3.4 Perform using command functions for depot manuals.

7.3.5 Identify TOs which require post-publication reviews to the TO Manager.

7.4 Air Education and Training Command (AETC). Air Education and Training Command (AETC) will:

7.4.1 Continually review preliminary TOs to detect errors, deficiencies, and obsolete or nonessential material and report problems to the TO Manager.

7.4.2 Furnish necessary assistance to the TO Manager for review efforts and verification of TOs.

7.4.3 Perform using command functions for TOs on training systems or commodities acquired for AETC.

7.5 Other Affected Units. Add other affected units as required: see TO 00-5-3, Chapter 4 and Chapter 16.

8 SCOPE OF TECHNICAL ORDER REQUIREMENTS:

8.1 General. The TO Manager establishes overall TO program guidance through coordination with users and support agencies, and retains TO management responsibilities until program transition to the ALC (if applicable) at system maturity.

TO management decisions will be based on operational needs and budget constraints.

8.2 TOs To Be Developed: There are different families of TOs to be developed for the A-10C program. The general characteristics and structure are as follows:

8.2.1 Operations Manuals: Manuals providing operation and use instructions, such as Flight Manuals.

8.2.2 Organizational Level Manuals: The organizational level manuals provide instructions in Job Guide format for on-equipment maintenance at the field level.

8.2.3 Intermediate/Depot Level and Engine Maintenance Manuals: These manuals contain instructions in Work Package format for off-equipment maintenance to be performed in the field and at the ALCs. In those instances where depot level instructions are identical, the intermediate level will not be duplicated in depot level work packs.

8.2.4 Illustrated Parts Breakdowns (IPB): IPB manuals provide instructions for identifying and requisitioning of parts and for illustrating assembly and disassembly relationships.

8.2.5 Support Equipment (SE) Manuals: The SE manuals contain operation and maintenance instructions for all levels of maintenance. When the page count is less than 800 page units, these manuals will also contain the IPB.

8.2.6 Training Equipment Manuals: The training equipment manuals contain the instructions for all levels of maintenance and operation of training systems.

8.2.7 Software Manuals: These manuals provide instruction on operation, troubleshooting, loading, etc. for installed

Software.

8.2.8 Commercial Off-The-Shelf (COTS) Manuals: These commercial-format manuals are provided by venders in support of their equipment used to support the overall W/S program.

9 AQUISITION PROCESS.

9.1 Segment Efforts. The A-10C program TO effort is segmented as follows: (Tailor as required).

NOTE

The below examples are for a typical aircraft program using discrete TOs. For commodities or programs using

IETM databases, other divisions (or none at all) would be used depending on the program.

Segment TO Effort

PHASE I Flight-Test-Required TOs

PHASE II Remaining OM Manuals

PHASE III Illustrated Parts Breakdown

PHASE IV Depot Level Manuals

9.2 Delivery Options: See TM-86-01.

9.3 TO Preparation.

9.3.1 Development Flow. The TOs will be developed from data in Supportability Analysis Reviews, design data specifications, schematics, engineering drawings, engineering reports, vendor data, engineering assembly and test procedures, manufacturing engineering procedures, support equipment procedures, and other TOs. At the TO Guidance Conference, all agencies involved in the TO program must ensure the contractor understands Air Force needs and requirements. The basis for requirements will be the IMP, SOW, TMCR, CDRLs, MILSPECs and standards, maintenance concept, skill levels of personnel using the TMs and support capabilities.

9.3.2 Specification Interpretations, Deviations, and Waivers. Approved Specification Interpretation Documents (SID) and requests for deviations or waivers (TM-86-01) will be made a part of the contract by modifying the Specification/Standard

Interface Record (SIR) for the applicable MILSPEC. Deviations and waivers can only be approved by HQ AFMC/A4U, with the concurrence of the PM and Lead Command.

9.3.3 Reviews: All reviews will be chaired by the TO Manager or a designated representative, with participation by all affected agencies as determined by the TO Manager. The prime contractor will host reviews when directed by the TO

Manager, including those for any subcontractor-prepared manuals.

9.3.3.1 In-Process Reviews (IPR) are conducted to evaluate contractor progress, understanding of contractual requirements and to make sure TOs are being prepared in accordance with applicable specifications. In addition, guidance may be given concerning TO technical content, data that requires amplification, missing data and standardization of data. IPRs will be conducted as specified in the TMCR. The objective of IPRs will be to:

9.3.3.1.1 Minimize deficiencies in delivered data resulting from failure of the preparing activity to fully and clearly understand contract/program requirements, the Air Force maintenance concept, Air Force policy and user capabilities/needs.

9.3.3.1.2 Identify deficiencies while corrective action is economical and can be accomplished without adverse effects to delivery schedules.

9.3.3.1.3 Assure the completion of manuals which meet quality requirements in terms of accuracy, adequacy, completeness, usability and compatibility with approved maintenance plans and support equipment.

9.3.3.2 Pre-publication Reviews will be conducted prior to preparation of the TO masters for formal delivery to verify inclusion of verification comments and as a final check on contract compliance.

9.3.3.3 Post-Publication Reviews are conducted after TOs have been delivered to the using command to evaluate and correct the instructions contained in the TOs. The need to conduct a Post-Publication Review will be determined by the TO

Manager based upon equipment modifications, AFTO Forms 22 or 847 received, and using command or PM

Recommendations.

9.3.3.4 Results of all reviews will be documented by minutes and a master markup copy of the TOs.

9.3.4 Quality Assurance: TO QA is the responsibility of all personnel involved in the development effort. The government will participate in the contractor QA program through the TO IPT, and vice versa.

9.3.4.1 The contractor QA program will be in accordance with the contract.

9.3.4.2 Schedules for QA checks must provide for sufficient time to incorporate any corrections or comments prior to the scheduled start of verification on the procedures or TOs checked.

9.3.4.3 When allowed in the contract, the contractor may certify manuals and source data instead of performing more detailed Quality Assurance checks.

9.3.5 Verification : Verification is the Air Force evaluation of TO adequacy and accuracy. All agencies and organizations involved must provide the support required. The general guidelines for verification are:

9.3.5.1 The initial effort will concentrate on TOs required for flight test (priority listing in TO 00-5-3, Chapter 9).

9.3.5.2 All PTOs (except non-procedural TOs) will contain a VSP to identify unverified functions, tasks, or procedures, and provide warnings about use. The VSP will be continuously updated by annotating the page in the master mark-up TO copy following each verification effort. The contract will require updated VSPs with each change or revision issued.

9.3.5.3 The process of verification will be accomplished on a scheduled basis in accordance with the TOLCVP (TO 00-5-3, Appendix C) developed by the TO Manager in conjunction with the using and supporting commands and the contractor. The verification activities will be scheduled far enough in advance (minimum of 30 days) to allow participation by all agencies.

9.3.5.4 Verification can begin only after a procedure/data has been contractor certified. Notification of manual or procedure completion will be provided by the respective contractors to the TO Manager. The TO Manager or VTM will coordinate availability of required assets to support the verification.

9.3.5.5 The contractor will provide on-site engineering and technical publication representation during all verification efforts in accordance with the contract. The representative will maintain a master copy of the procedure/data being verified.

The master copy will be used to record recommended changes during verification. A copy of the corrected master will be retained by the verification team and a copy will be sent to the TO Manager.

9.3.5.6 Concurrent contractor testing and verification will be permitted IAW TO 00-5-3.

9.3.5.7 The manuals will remain PTOs until determined both accurate and adequate by the TORB, and formalized by the

TO Manager. During the period after verification TO discrepancies will be reported as specified by the TO Manager (TO 00-

5-3).

9.3.6 TO Security and Information Assurance:

9.3.6.1 Classified Data Control. Classified material and equipment will be handled in accordance with DOD 5200.1-

R/AFI 31-401, Information Security Procedures Regulation, and DOD 5220.22-R/AFI 31-601, Industrial Security

Procedures. If any Air Force activity has reason to believe that security considerations support the reclassification or declassification of a specific TO, the activity will report the discrepancy in accordance with procedures outlined in AFI 31-

401.

9.3.6.2 Controlled, Unclassified Information (CUI). Unclassified technical data and TOs will be marked and controlled

IAW DODD 5230.24, 5230.25, DOD 5400.7-R, AFI 61-204, and TO 00-5-3.

9.3.7 Configuration Control. To ensure that the user is provided both accurate and adequate information to operate and maintain the A-10C program and support equipment, the following measures must be applied.

9.3.7.1 The contractor shall continuously monitor and provide information to the TO Manager on all configuration changes to the military system and support/test equipment.

9.3.7.2 The TO Manager will work closely with the contractor(s) to ensure TO QA and verification are accomplished on production configured systems and commodities.

9.3.7.3 Deviations will be permitted only where like systems/commodities do not effect operations and maintenance procedures being checked or verified. In these cases approval to use other than production configured systems or commodities must be coordinated between the TO Manager, using command and supporting agencies.

9.3.8 Updates and Update Incorporation.

9.3.8.1 Updates resulting from In-Process Reviews will be incorporated prior to the next scheduled review.

9.3.8.2 Updates resulting from contractor QA procedures will be incorporated prior to delivery of PTOs for verification.

9.3.8.3 Updates resulting from Air Force verification will be incorporated by the contractor(s) prior to preparation of formal TO reproduction media.

9.3.9 Formalization. When verification is completed, the Verification Team will complete an AFTO Form 158 to document any TO discrepancies and recommend either further verification or formalization of the TO. The AFTO Form 158 will be sent to the TO Manager (or TORB/FTORB) for review, coordination and approval. Approved AFTO Forms 158 will be sent to the contractor for update of the TO, and if applicable, preparation of formal copies. Upon formalization of the

PTO, the VSP will be removed unless some portion of the TO could not be verified (example: wing removal and replacement). The VSP for formal TOs must identify all procedures/tasks/paragraphs within the TO that have not been verified and must contain instructions for accomplishing and reporting verification by field units in accordance with TO 00-

5-1.

9.4 Maintenance of TOs. The maintenance of TO accuracy is the responsibility of the TO Manager. During the acquisition phase, this is usually through a contract with the prime contractor. The update schedule will be specified in the

TMCR.

9.5 Management of Time Compliance TOs (TCTOs). TCTOs required in support of the (program) will be managed by the TO Manager according to TO 00-5-15 and AFMCI 21-301.

9.6 Schedules. The schedules for the TO acquisition process are dependent upon overall program schedules and the availability of support equipment, hardware, and personnel needed for TO development, review and acceptance.

9.7 Financial Plan. The A-10C program PMs will budget for TO support from other organizations in accordance with AFI

65-601V1. All organizations must project budget requirements by developing and submitting a TO Requirements Plan

(TORP) according to the TO Requirements Guide (TORG, CAFTOP Handbook).