TO_00-5-3.pdf

Downloaded from http://www.everyspec.com on 2009-09-10T18:42:02.

TO 00-5-3

INSERT LATEST CHANGED PAGES. DESTROY SUPERSEDED PAGES.

LIST OF EFFECTIVE PAGES

NOTE: The portion of the text affected by the changes is indicated by a vertical line in the outer margins of the page. Changes to illustrations are indicated by miniature pointing hands. Changes to wiring diagrams are indicated by shaded areas.

Dates of issue for original and changed pages are:

Original ........................... 0................. 1 April 2001

TOTAL NUMBER OF PAGES IN THIS PUBLICATION IS 120, CONSISTING OF THE FOLLOWING:

Page *Change Page *Change Page *Change No. No. No. No. No. No.

Title A i - iv 1-1 - 1-11 1-12 Blank 2-1 - 2-6 3-1 - 3-6 4-1 - 4-10 5-1 - 5-3 5-4 Blank 6-1 - 6-5 6-6 Blank 7-1 - 7-6 8-1 - 8-5 8-6 Blank 9-1 - 9-7 9-8 Blank 10-1 - 10-2 11-1 - 11-2 12-1 - 12-5 12-6 Blank A-1 - A-9 A-10 Blank B-1 - B-8 C-1 - C-7 C-8 Blank D-1 - D-3 D-4 Blank E-1 - E-9 E-10 Blank

*Zero in this column indicates an original page

A USAF

TABLE OF CONTENTS

Chapter/Para Page

1 INTRODUCTION AND POLICY................................................................................................... 1-1 1-1 Purpose......................................................................................................................... 1-1 1-2 Concept......................................................................................................................... 1-1 1-3 Policy ............................................................................................................................ 1-1

2 RESPONSIBILITIES...................................................................................................................... 2-1 2-1 General......................................................................................................................... 2-1 2-2 HQ USAF/ILMM ......................................................................................................... 2-1 2-3 HQ AFMC .................................................................................................................... 2-1 2-4 Air Logistics and Product Centers (ALCs and PCs)................................................. 2-2 2-5 Other Acquisition Organizations................................................................................ 2-2 2-6 Single Manager (SM) .................................................................................................. 2-2 2-7 TO Manager................................................................................................................. 2-2 2-8 Using Command/Technology Repair Center (TRC) .................................................. 2-4 2-9 Nuclear Weapons Product Support Center, Air Armament Center

(AAC)/WN .................................................................................................................2-4 2-10 Air Education and Training Command (AETC) ....................................................... 2-5 2-11 USAF Ammunition Control Point (ACP), OO-ALC/LIW, and Tactical

Missile Control Point (TMCP), WR-ALC/LKG.......................................................2-5 2-12 46TH Operations Group (OG)/OGS ........................................................................... 2-5 2-13 412 Test Wing.............................................................................................................. 2-6

3 PLANNING, BUDGETING AND SPECIAL REQUIREMENTS ................................................ 3-1 3-1 General......................................................................................................................... 3-1 3-2 Acquisition Strategy.................................................................................................... 3-1 3-3 Initial Planning ........................................................................................................... 3-2 3-4 TO Development.......................................................................................................... 3-3 3-5 TO Maintenance and System Sustainment............................................................... 3-3 3-6 Special Requirements.................................................................................................. 3-3

4 CONTRACTING.............................................................................................................................. 4-1 4-1 General......................................................................................................................... 4-1 4-2 Continuous Acquisition and Life Cycle Support (CALS).......................................... 4-1 4-3 Government Concept of Operations (GCO) ............................................................... 4-1 4-4 Requests for Proposal and Contracts......................................................................... 4-2 4-5 Statement of Work ...................................................................................................... 4-2 4-6 Statement of Objectives .............................................................................................. 4-3 4-7 Evaluation Criteria ..................................................................................................... 4-3 4-8 Instructions to Offerors (ITO) .................................................................................... 4-3 4-9 Contract Data Requirements List (CDRL) and Data Item Descriptions

(DIDs)........................................................................................................................4-3 4-10 Technical Manual Contract Requirements (TMCR) Document, TM-86-01............. 4-4 4-11 TO Development.......................................................................................................... 4-4 4-12 Deliverables ................................................................................................................. 4-5 4-13 Use of TM Specifications and Standards (TMSS) .................................................... 4-6 4-14 Specification/Standard Tailoring, Interpretation, Deviations and

Waivers .....................................................................................................................4-6 4-15 Source Data for TOs.................................................................................................... 4-6 4-16 Identification of Additional Contract TO Requirements.......................................... 4-6 4-17 Rights in Technical Data ............................................................................................ 4-7 4-18 Quality Assurance ....................................................................................................... 4-8 i

TABLE OF CONTENTS - Continued

Chapter/Para Page

5 PROPOSAL EVALUATION AND NEGOTIATION ..................................................................... 5-1 5-1 General......................................................................................................................... 5-1 5-2 Developing Evaluation Criteria and Checklists........................................................ 5-1 5-3 Technical Evaluation................................................................................................... 5-1 5-4 Contractor Costs .......................................................................................................... 5-2 5-5 Specific TO Proposal Evaluation Guidelines ............................................................ 5-2 5-6 Protecting Proposal Records and Data ...................................................................... 5-3 5-7 Contract Negotiation................................................................................................... 5-3 5-8 Post Contract Award................................................................................................... 5-3

6 CONFERENCES AND REVIEWS ................................................................................................ 6-1 6-1 General......................................................................................................................... 6-1 6-2 TO Planning/Requirements Conference .................................................................... 6-1 6-3 TO Guidance Conference ............................................................................................ 6-1 6-4 Commercial Manual Review....................................................................................... 6-2 6-5 In-Process Reviews...................................................................................................... 6-2 6-6 Pre-Publication Reviews ............................................................................................. 6-3

7 QUALITY ASSURANCE ................................................................................................................ 7-1 7-1 General......................................................................................................................... 7-1 7-2 Reading Grade Level (RGL) ....................................................................................... 7-1 7-3 The Contractor QA Process ........................................................................................ 7-1 7-4 Verification .................................................................................................................. 7-2 7-5 Verification Methodology............................................................................................ 7-4 7-6 Verification Procedures............................................................................................... 7-4

8 REPRODUCTION AND DISTRIBUTION .................................................................................... 8-1 8-1 Reproduction ................................................................................................................ 8-1 8-2 Distribution.................................................................................................................. 8-2

9 TO UPDATES ................................................................................................................................. 9-1 9-1 General......................................................................................................................... 9-1 9-2 Types of Updates ......................................................................................................... 9-1 9-3 Procedures for AFTO Form 27 ................................................................................... 9-1 9-4 Entries on AFTO Forms 27 ........................................................................................ 9-2 9-5 Processing AFTO Forms 27 ........................................................................................ 9-3 9-6 Control and Tracking of PCRs ................................................................................... 9-4 9-7 Classified PCRs ........................................................................................................... 9-4 9-8 Update Distribution and Filing.................................................................................. 9-4 9-9 PCRs and the Innovative Development Through Employee Awareness

(IDEA) Program .......................................................................................................9-4

10 SAFETY AND HEALTH .............................................................................................................. 10-1 10-1 General....................................................................................................................... 10-1 10-2 TO Manager Responsibilities ................................................................................... 10-1 10-3 Ground Safety............................................................................................................ 10-1 10-4 Pollution Prevention.................................................................................................. 10-1 10-5 Weapon Safety ........................................................................................................... 10-1 10-6 Health Guidance........................................................................................................ 10-2

11 SECURITY ASSISTANCE TO PROGRAM ................................................................................ 11-1 11-1 General....................................................................................................................... 11-1 11-2 Responsibilities.......................................................................................................... 11-1 ii

TABLE OF CONTENTS - Continued

Chapter/Para Page

11-3 Types of SATOP Manuals......................................................................................... 11-1

12 SOURCE DATA ............................................................................................................................ 12-1 12-1 General....................................................................................................................... 12-1 12-2 Acquisition of Source Data ....................................................................................... 12-1 12-3 Nonnuclear Weapons Delivery Source Data - Weapons Source Data

Package (Aircraft -34 Series TOS and TO 1-1M-34 Series) ...............................12-1 12-4 Nonnuclear Munitions Loading Source Data - Standard Source Data

Package (Aircraft -33 Series TOS and TO 1-1M-33)...........................................12-2 12-5 Nonnuclear Explosive Ordnance Disposal (EOD)/Render Safe Proce-dures (RSP) Source Data .......................................................................................12-4

A GLOSSARY .....................................................................................................................................A-1 I List of Acronyms..........................................................................................................A-1 II Definitions ...................................................................................................................A-5

B GENERIC TECHNICAL ORDER MANAGEMENT PLAN(TOMP) UNITED

STATES AIR FORCE (WEAPON SYSTEM) TECHNICAL ORDER MANAGEMENT

PLAN ORGANIZATIONAL/INTERMEDIATE/DEPOT...............................................................B-1

B-1 Introduction .................................................................................................................B-3 B-2 Policy ............................................................................................................................B-3 B-3 Purpose.........................................................................................................................B-3 B-4 Program Summary ......................................................................................................B-3 B-5 Reference Material ......................................................................................................B-3 B-6 Definitions ...................................................................................................................B-3 B-7 Responsibilities............................................................................................................B-3 B-8 Scope of Technical Order Requirements....................................................................B-5 B-9 Acquisition Process......................................................................................................B-6

C GENERIC TECHNICAL ORDER VERIFICATION PLAN (TOVP) UNITED

STATES AIR FORCE (MILITARY SYSTEM) (DESIGNATION) TECHNICAL OR-

DER VERIFICATION PLAN (TOVP) ORGANIZATIONAL/INTERMEDIATE/DEPOT...........C-1

C-1 Introduction .................................................................................................................C-3 C-2 Purpose.........................................................................................................................C-3 C-3 Scope.............................................................................................................................C-3 C-4 References ....................................................................................................................C-3 C-5 Annexes ........................................................................................................................C-3 C-6 Verification Plan General Provisions ........................................................................C-3 C-7 Responsibilities............................................................................................................C-4 C-8 Procedures for Verification.........................................................................................C-6 C-9 Administrative Procedures .........................................................................................C-7

D POINTS OF CONTACT..................................................................................................................D-1

E GUIDANCE FOR DEVELOPING REQUEST FOR PROPOSAL (RFP) EVALUA-

TION CRITERIA AND INSTRUCTIONS, CONDITIONS, AND NOTICES TO OF-

FERORS OR QUOTERS ................................................................................................................E-1

E-1 Introduction .................................................................................................................E-1 E-2 Request for Proposal ...................................................................................................E-1 E-3 TO Program Requirements.........................................................................................E-2 E-4 Evaluation Criteria .....................................................................................................E-3 E-5 Instructions to Offerors ..............................................................................................E-5 iii

LIST OF ILLUSTRATIONS

Figure Title Page

1-1 TO Acquisition Sequence Flow Chart .................................................................................... 1-7 1-2 Digital TO Acquisition Matrix .............................................................................................. 1-10 4-1 DD Forms 1423, 1423-1, and 1423-2, Contract Data Requirements List (CDRL) ............. 4-9 4-2 AF Form 585, Contractor Data Requirements Substantiation .......................................... 4-10 7-1 AFTO Form 124, Computation of Technical Order Reading Grade Level .......................... 7-6 8-1 AFTO Form 30, Reproduction Assembly Sheet..................................................................... 8-4 9-1 AFTO Form 27, Preliminary Technical Order (PTO) Publication Change Re-quest (PCR)/TO Verification Record/Approval ..................................................................9-5 9-2 AFTO Form 158, Technical Order Review Comment Sheet................................................. 9-7 E-1 Example of Contract Line Item Numbers (CLINs) for TO Exhibit. ....................................E-9

LIST OF TABLES

Number Title Page

1-1 List of Related Publications .................................................................................................... 1-4 6-1 IPR Completion Percentage Guide. ........................................................................................ 6-3 6-2 Review Evaluation Guide........................................................................................................ 6-4 iv

CHAPTER 1

INTRODUCTION AND POLICY

1-1 PURPOSE.

This Technical Order (TO) provides the TO Manager with guidance and direction for managing acquisition of TOs and updates, to support initial acquisition and modification of system and equipment hardware and software. This TO is to be used in conjunction with the publications listed in table 1-1 (which includes the titles of all publications referenced in this TO).

1-1.1 Terms and Acronyms. Terms and acronyms used in this TO are defined in the Glossary (appendix A).

Addresses for organizations and activities with whom the TO Manager may require direct communication are listed in appendix D.

1-1.2 Supplements and Changes. This TO may be supplemented according to TO 00-5-1. Copies of all supplements will be sent to HQ USAF/ILMM, 1030 Air Force Pentagon, Washington DC 20330-1030; MSG/ MMF, 4375 Chidlaw Rd Ste 6, WPAFB OH 45433-5006; and OC-ALC/TILDT, 3001 Staff Dr Ste 1AB100, Tinker AFB OK 73145-3042. Suggested changes to this TO should be submitted on AFTO Forms 22, Technical Manual Change Recommendation And Reply, according to TO 00-5-1.

1-2 CONCEPT.

The TO System and its operation are covered by this TO and TOs 00-5-1, 00-5-2, 00-5-15, and 00-5-18.

1-2.1 TO acquisition includes the development and/or procurement of technical data and TOs to operate and maintain centrally-acquired and managed military systems and commodities. TOs for individual systems and commodities are acquired by assigned TO Managers (see chapter 2). Flight Manual Managers (FMMs) manage the acquisition of Flight Manual Program (FMP - AFI 11-215) publications under the guidance of the TO Manager.

1-2.2 TO acquisition (f igure 1-1) involves the TO Manager, using command, support agencies and the contractor working together to deliver verified formal TOs prior to or concurrently with hardware delivery to the operational unit (AFPD 21-3). Acquisition and maintenance of TOs must be effectively managed through the life cycle of the military system or commodity that the TOs support, as envisioned by the Air Force TO Concept of Operations (CONOPS) and in accordance with the Integrated Weapon System Management (IWSM) concept.

1-3 POLICY.

TOs to support new acquisition or modification programs for military systems or commodities are acquired on a schedule formally imposed by the contract to meet the requirements for development, review, verification, and delivery of formal TOs. Any manuals developed for the government (at government expense) must be developed to a performance or government-approved non-government specification.

1-3.1 Delivery Requirements. Delivery of PTOs shall be prior to or concurrent with delivery of the hardware for development testing and/or operational need dates. Formal organizational level (on-equipment) TOs and preliminary intermediate level (off-equipment) TOs will be delivered prior to or concurrently with the delivery of the first production configured system or commodity to the first operational unit . Intermedi-ate-level manuals must be formalized by the initial operational capability (IOC) date.

1-3.1.1 For the two-level maintenance concept, f ield level TOs meeting the definitions of ‘‘on-equipment’’ and ‘‘off-equipment’’ must meet the delivery requirements of Organizational and Intermediate-level manu-als, respectively. Preliminary depot level TOs will be delivered prior to depot prototype overhaul and must be verified and formalized prior to depot activation.

1-3.1.2 If TOs cannot be delivered according to this policy, the TO Manager must revise verification schedules, update the TO Management Plan (TOMP), and recommend interim support for the using command {use of verified or partly verified Preliminary TOs (PTOs), Interim Contractor Support (ICS, AFI

1-1

63-111), etc.} until the manuals are delivered (see paragraph 1-3.4). Any such actions must be coordinated with and approved by the appropriate Single Manager (SM) and the using command.

1-3.2 Acquisition Requirements. TOs will be acquired according to DOD 5010.12-M, on a separate Contract Line Item Number (CLIN), using a contract exhibit consisting of a DD Form 1423, Contract Data Requirements List (CDRL), with a program-specific (tailored) TM-86-01, Technical Manual Contract Requirements (TMCR) document (see chapter 4). The TMCR is managed by MSG/MMF in coordination with other acquisition agencies. A copy is available on the Internet through the TO System Information Page at Uniform Resource Locator (URL) address http://www.pdsm.wpafb.af.mil/toprac/to-syste.htm.

1-3.2.1 Digital (Electronic) TOs. Current DoD policy requires ‘‘preference be given to delivery (of all data, including TOs) in machine-readable form rather than paper.’’ RFPs will require the contractor to propose how their technical information system for logistic support can be integrated with the government’s, using Continuous Acquisition and Life-Cycle Support (CALS) standards (DOD 5000.2-R). MSG/MMF may be contacted for assistance prior to developing contractual documents. This will ensure standardization of digital system hardware and software to the maximum extent possible within the Air Force and DoD. See TO 00-5-1 for a description of digital TO formats.

1-3.2.2 Contracts should provide an opportunity for government review and approval of revisions, changes, and supplements to program TOs.

1-3.3 General Policies. Maximum use will be made of existing data. Available manuals from other government departments or agencies will be reviewed to determine adequacy and application to particular programs. TOs which do not conform to existing exempted or military performance (MIL-PRF) specifications will not be acquired or prepared without the prior approval of MSG/MMF (TO 00-5-1). Approval is also required for use of Non-Government (commercial) Standards (NGS) in lieu of MIL-PRF specifications for TO development.

1-3.3.1 Commercial Off-The-Shelf (COTS) Manuals. Existing commercial operating instructions, parts breakdown handbooks, and repair manuals will be acquired instead of developing new TOs if no degradation in system operation, safety, support or reliability will result. This will save money and time for the TO program. COTS manuals will be reviewed and evaluated by the TO Manager, using command and technical content manager (TCM) according to MIL-HDBK-1221.

1-3.3.1.1 Commercial Aircraft Maintenance and Operations (Flight) Manuals (FMP) proposed for use by Air Force personnel must be reviewed by the TCM and FMM against both MIL-HDBK-1221 and MIL-PRF- 7700 requirements.

CAUTION

Air Force and commercial roles and responsibilities for f light crews and ground crews are different. Procedure changes to commercial maintenance manuals could also affect military f light crew manuals. Reviewers must consider this possibility and if it exists, take action to include the appropriate changes in both f light crew and maintenance manuals.

1-3.3.1.2 Approved manuals will be adopted for Air Force use, assigned a TO number and managed within the TO system unless a waiver is approved in accordance with paragraph 1-3.3.4. Manuals which are initially disapproved will be supplemented if possible to make them acceptable; supplements will be written according to the parent manual’s style and format. When supplementing is not adequate, new TOs will be developed to MIL-PRF or approved commercial specifications. Careful consideration of future support costs, incorporation of commercial updates, and ease of use will determine whether military or commercial specifications should be used. Data developed for the system or equipment contractor’s own internal use, if later purchased by the government, will be treated the same as COTS data.

1-3.3.2 Proprietary and Copyrighted Data. When a program acquires proprietary or copyrighted data, the Air Force must receive at least limited rights allowing reproduction and distribution of the data for government purposes, in accordance with Defense Federal Acquisition Regulations Supplement (DFARS) clauses (see chapter 4). Unlimited rights are recommended whenever possible.

1-2

1-3.3.3 Integrating TOs. TOs for the operation and maintenance of end items which are composed of interconnected configuration items will be maintained under the TO system. The agency or contractor who developed the end item will normally develop the integrated operating and maintenance instructions.

1-3.3.4 Numbering COTS Manuals. The decision to number, manage, and use commercial manuals for mixed-support programs (partly organic, partly contractor support) in or outside the TO system will be made jointly by the TO Manager, user and appropriate TCM. Generally, manuals used for organic (Air Force) operations or maintenance will be included in the TO System unless a waiver is approved by HQ USAF/ ILMM. When different user organizations have different operation or maintenance support concepts, manuals will be managed in the TO System unless cost prohibitive.

1-3.3.5 Service Bulletins, Operations Manual Bulletins, FAA Airworthiness Directives, Temporary Revi-sions, and Like Data. SMs must ensure, through the TO Manager, that all contracts issued for procurement or sustainment of commercial or militarized commercial systems and commodities require delivery of applicable FAA, manufacturer’s or vendor’s technical data updates during the entire program life-cycle.

1-3.3.5.1 Use a DID (when available), or ensure the CDRL for TO delivery requires delivery of these updating publications.

1-3.3.5.2 The TCM, depot engineering or technical support activity and FMM will determine if any updates received apply to TO-numbered f light and/or maintenance manuals, and if they will be referenced by their commercial number or will have the information extracted for inclusion in supplements or other TO updates.

1-3.3.6 Exemptions. Technical manuals (TMs) and data used in full Contractor Logistics Support (CLS) programs are exempt from management within the TO system. Manuals to support local purchase items (NOT centrally-procured COTS equipment) are also exempt. The acquiring activity is responsible for acquiring, accepting, maintaining, and distributing these publications.

1-3.3.7 Hazardous Materials (HAZMAT) and Ozone Depleting Substances (ODS). Procedures in TOs must minimize the generation, use and disposal of HAZMAT and ODS according to AFPD 32-70 and associated instructions. Any use of HAZMAT and ODS must be justified by the contractor and approved by appropriate government personnel.

1-3.4 Preliminary TOs (PTOs). TOs are considered ‘‘preliminary’’ from the time they have a number assigned until they are formalized (AFTO Form 27 completed). PTOs must complete the contractor’s quality process before delivery to the government for verification. Formatted PTOs should be used to the maximum extent possible to support Air Force Test and Evaluation (T&E). PTOs are also used for development of training plans and course syllabuses. Air Force personnel may use unverified data during system T&E or for routine maintenance performed in conjunction with the verification effort on new or modified hardware or software. Formalization occurs after the PTOs are successfully verified and all corrections are made.

1-3.4.1 Every effort shall be made to replace organizational-level PTOs with formal TOs prior to or concurrent with delivery of the first production-configured system or commodity to the first operational unit.

See TO 00-5-1 for policy on use of verified PTOs in the operational environment.

1-3.4.2 Verification Status Pages (VSPs) will be included in all TOs and PTOs which contain unverified procedures (MIL-STD-38784). Non-procedural TOs (certain Methods and Procedures TOs such as this one, IPBs, WUC manuals, etc.), do not require VSPs.

1-3.5 TO Quality Assurance (QA). The contractor is responsible for providing adequate, safe and accurate TOs which conform to government requirements. TOs and data must be approved by the contractor’s internal QA process prior to delivery for Air Force verification (this should be one of the ‘‘exit criteria’’ in the contractor’s Integrated Master Plan (IMP - appendix E)). The government will provide necessary Govern-ment Furnished Equipment (GFE) required to enable the contractor to test TO procedures. The government will participate in the contractor’s quality process through the TO IPT, and will perform verification (chapter

7) when PTOs are delivered.

1-3.6 TO Verification. Verification policy requires 100 percent ‘‘hands on’’ performance of all operational, maintenance, and calibration tasks contained in TOs and supplements to commercial manuals. Verification must be performed on production-configured military system and commodity items (or inert versions of explosive items) by using command personnel. Non-procedural data will be verified during IPRs or by Desk- Top Analysis. Verification may be combined with the contractor’s QA process under certain circumstances (chapter 7).

1-3

CAUTION

Use of unverified procedures except under controlled conditions could result in injury to personnel or damage to equipment. Unverified procedures must NOT be used in the operational environment, except during the verification process itself. (See TO 00-5-1 for waiver authority.)

1-3.6.1 The program verification schedule must be developed in conjunction with the Air Force test plan, production schedules and deployment schedules to ensure the availability of hardware, software, and equipment to support the verification effort. The tentative schedule must be provided to offerors in the RFP to allow development of supportive schedules.

1-3.6.2 TO verification will make maximum use of other scheduled events, such as test and evaluation, prototyping, and maintainability demonstrations. Activities should not be duplicated. Use unscheduled events such as equipment failure to verify applicable procedures, when possible.

1-3.7 Source Data. Technical documentation produced during the hardware development or modification process should not be redeveloped for use in program TOs. The government should not pay twice for development of the same data. Source data for TOs may consist of, but is not limited to, supportability analysis data, engineering drawings, test reports, and other technical data. It is up to the contractor to decide which source data to use. See chapter 12.

1-3.7.1 For joint-service acquisition programs, TMs should be developed in a single format usable by all services involved, rather than developing individual manuals for each service. When separate TMs are required, common source data will be used to the maximum extent possible for their development.

1-3.7.2 Acquisition agencies will acquire source data for use in the generic servicing inspection workcards for powered aerospace ground equipment (AGE) (TO 35-1-256WC-1), and for update of other TOs not managed by the TO Manager (i.e., Crash and Rescue, Static Display, EOD, etc., see chapter 3).

1-3.8 Reading Grade Level (RGL). TOs will be written not to exceed a ninthgrade RGL (MIL-STD-38784, AF requirement). Exceptions include: FMP TOs (AFI 11-215); tabular TOs (e.g., -06 Work Unit Code Manuals, -4 Illustrated Parts Breakdown Manuals); abbreviated TOs (e.g., workcards, checklists); MIL-PRF- 83495 maintenance manual sets {e.g., job guides (JG), schematic diagram (SD) and wiring diagram (WD) manuals}; and 00-25-113-series (Precious Metals) TOs.

1-3.9 Computer Program Identification Numbers (CPINs). Software program tapes and control documen-tation will be referenced in TOs using only the basic CPIN (TO 00-5-16). The CPIN compendium provides the version numbers and dates of programs authorized for use.

Table 1-1. List of Related Publications

Number Title

DoD 4120.3-M Defense Standardization Program Policies and Procedures

DoDD 5000.1 Defense Acquisition

DoD 5000.2-R Mandatory Procedures for Major Defense Acquisition Programs (MDAPs) and Major Automated Information System (MAIS) Acquisition Pro-grams

DoD 5010.12-M Procedures for the Acquisition and Management of Technical Data

DoD 5010.12-L Acquisition Management Systems and Data Requirements Control List

(AMSDL)

DoDD 5160.62 Single Manager Responsibility for Military Explosive Ordnance Disposal Technology and Training

DOD 5200.1-R Information Security Program Regulation and Managing the Information and AFI 31-401 Security Program

1-4

Table 1-1. List of Related Publications - Continued

Number Title

DoD 5220.22-R Industrial Security Regulation and Industrial Security Program Manage-and AFI 31-601 ment

DoDD 5230.24 Distribution Statements on Technical Documents

DoD 5230.25-PH Control of Unclassified Technical Data with Military or Space Applica-tion

DoDD 5330.3/ Defense Automated Printing Service (DAPS) AF Supplement

DoDISS DoD Index of Specifications and Standards

FAR/DFARS Federal Acquisition Regulation/Defense Federal Acquisition Regulation Supplement

AFPD 21-3 Technical Orders

AFPD 32-70 series Environmental Quality

AFI 11-215 Flight Manuals Program (FMP)

AFI 16-101 Politico-Military and Security Assistance Management

AFI 21-105 Aerospace Equipment Structural Maintenance

AFPD 21-3 Technical Orders

AFJI 21-301 Interservicing of Technical Manuals and Related Technology

AFI 32-3002 Interservice Responsibility for Explosive Ordnance Disposal

AFI 37-131 Freedom of Information Act Program

AFI 60-114 Management of Contractor Data

AFI 61-204 Disseminating Scientific and Technical Information

AFI 63-101 Acquisition System

AFI 63-104 The Seek Eagle Program

AFI 63-111 Contractor Support for Systems and Equipment

AFI 65-601V1 Budget Guidance and Procedures

AFI 91-301 Air Force Occupational and Environmental Safety, Fire Prevention and Health (AFOSH) Program

AFI 99-101 Developmental Test and Evaluation

AFI 99-102 Operational Test and Evaluation

AFI 99-109 Test Resources Planning

AFMAN 37-139 Records Disposition Schedule

AFMAN 91-201 Explosive Safety Standards

AFMCI 21-301 Air Force Materiel Command Technical Order System Implementing Pol-icies

AFMCI 21-302 Processing Interim Technical Orders

AFMCMAN 21-1 Air Force Materiel Command Technical Order System Procedures

1-5

Table 1-1. List of Related Publications - Continued

Number Title

AFMCPD 33-1/ Receiving, Distributing, and Warehousing Technical Orders (TO)

AFMCI 33-103

AFMCPAM 63-3 Single Manager (SM) Roles and Responsibilities under Integrated Weap-on System Management (IWSM)

TM-86-01 Technical Manual Contract Requirements (TMCR) document

TO 00-5-1 AF Technical Order System

TO 00-5-2 Technical Order Distribution System

TO 00-5-15 AF Time Compliance Technical Order System

TO 00-5-18 USAF Technical Order Numbering System

TO 00-5-19 Security Assistance Technical Order Program

TO 11N-1-1 Joint Nuclear Weapons Publication System (JNWPS)

DAD Defense Acquisition Deskbook, Section 3.7, Continuous Acquisition and Life-cycle Support (CALS)

MIL-HDBK-245 Preparation of Statements of Work (SOW)

MIL-HDBK-1221 Manuals, Commercial Off-The-Shelf (COTS)

MIL-STD-882 System Safety Program Requirements

MIL-STD-1808 System/Subsystem/Sub-subsystem Number (S/S/SN) Numbering System

MIL-STD-1840 Automated Interchange of Technical Information

MIL-STD-38784 Manuals, Technical: General Style and Format Requirements

MIL-PRF-7700 Manuals, Flight

MIL-PRF-9977 Manuals, Technical and Checklists: Munitions/Weapons Loading Proce-dures, Nuclear and Nonnuclear // Packages, Standard Data: Munitions Loading Procedures, Nonnu

MIL-DTL-22202 Manual, Technical: Aircraft Cross-Servicing Guide, Preparationof

MIL-PRF-38384 Manuals, Technical: Weapon Delivery and Aircrew Procedures, Nuclear and Nonnuclear

MIL-PRF-38769 Manuals, Technical: Work Unit Code

MIL-PRF-83495 Manuals, Technical: On Equipment Set, Organizational Maintenance Manuals

MIL-PRF-87158 Manuals, Technical: Aircraft Battle Damage Assessment and Repair

MIL-PRF-87929 Manuals, Technical: Operation and Maintenance Manuals in Work Pack-age Format

DI-TMSS-80067 Contractor Furnished Aeronautical Equipment/Contractor Furnished Equipment (CFAE/CFE) Notices

DI-SAFT-80931 Explosive Ordnance Disposal Data

DI-TMSS-81532 Aircraft Emergency Rescue Information (Fire Protection) Source Data

1-6

Figure 1-1. TO Acquisition Sequence Flow Chart

1-7

I MD Issued - This is the first step in establishing an acquisition program. The PMD is based on a verified need of a Using Command.

II SM Established - A Program office to manage the acquisition is established under the control of a Single Manager. SMs may be System Program Managers, Product Group Managers, or Materiel Group Managers, depending on the system or commodity being acquired (Chapter 2 and Definitions). Most major acquisition programs are managed at an AFMC Product Center. Air Logistics Centers manage acquisition of sustain-ment contracts, modifications, replenishment spares, and some commodities.

III TO Manager Appointed - The SM will appoint a TO Manager, or assign TO management duties to an Integrated Product Team (IPT), early in the program. The TO Manager is responsible for developing TO budgets, Request for Proposal (RFP) inputs and TO Management/Verification Plans. (Chapter 2)

IV GCO Developed - The Government Concept of Operations (GCO) is developed by an IPT including the TO Manager, Data Manager, and Engineering Data Manager, to document and provide guidance on the program?s implementation of Continuous Acquisition and Life-Cycle Support (CALS) principals for data development and delivery. Critical inputs for TO Management include compatibility with the Joint Computer-Aided Acquisition and Logistics Support (JCALS) Joint Technical Manual System (JTMS), TO digital development formats, and delivery options. The GCO is included in the RFP as Government Furnished Information (GFI). (Chapter 4)

V Draft TOMP and RFP - The TO Manager drafts TO-related RFP inputs and a TO Management Plan (TOMP) for consideration by the TO IPT. The TO IPT consists of the TO Manager, system sustainment personnel, using command representatives, training command representatives, and representatives of any special TO requirements. RFP inputs may include a Statement of Objectives (SOO) or Statement of Work (SOW), Evaluation Criteria, Instructions To Offerors (ITO), Contract Data Requirements Lists (CDRLs DD Form 1423), and a Technical Manual Contract Requirements (TMCR) document, TM-86-01. The TOMP documents the overall TO management philosophy for the program. (Chapter 3)

VI TO Planning/Requirements Conference - This conference brings together the members of the TO IPT to review program documentation such as the PMD, Operations and Maintenance Concepts, etc., to determine TO requirements and management plans for the program. The draft RFP inputs and TOMP developed by the TO Manager are used as a starting point for the conference. (Chapter 3)

VII Finalize TOMP and RFP - The TO Manager uses the requirements developed by the planning conference to finalize the TOMP and RFP inputs. The TO data requirements are provided to the program’s Data Requirements Review Board (DRRB) for approval and inclusion in the RFP sent out for bid. (Chapter 3)

VIII Offerors Develop and Submit Proposals - Interested offerors develop specific cost and technical proposals for TO development and delivery based on all information and direction provided in the RFP. Proposals may include a SOW, Work Breakdown Structure (WBS), Integrated Master Plan and Schedule (IMP and IMS), recommended CDRLs, and a fully-tailored TMCR. TO program costs must be shown in a separate Contract Line Item Number (CLIN) of the proposal. (Chapter 4)

IX Source Selection - The government forms a team (or teams) to review, evaluate and compare offerors’ proposals. The number of proposals received may be ‘‘down-selected’’ to a manageable number before going to source selection, using some objective criteria based on program needs and risk areas. (Chapters 4 and 5)

X Issue TO Contract - After source selection, the government will negotiate any areas of dispute with the winning offeror, and a contract will be issued. The contract must include, as a minimum, a separate CLIN, CDRL and tailored TMCR for TO development and delivery. At this point, the ‘‘offeror’’ becomes the ‘‘contractor,’’and becomes part of the TO IPT. (Chapter 4)

XI TO Guidance Conference - A TO Guidance Conference or Technical In-terchange Meeting is held, usually within 60 days of contract award, to discuss the contract, introduce TO program participants, f inalize strategy and schedules, and in general, resolve any issues not specifically detailed in the contract. The contract cannot be changed without Procuring Contracting Officer (PCO) approval. (Chapter 6)

XII TO Quality Process - TO quality is assured through the use of quality processes in the development, testing and delivery of individual manuals. The TO IPT maintains insight into quality through participation in all aspects of the contractor’s process, without interfering or hampering the free accomplishment of tasks.

Quality TOs are adequate, safe and accurate; conform to government requirements; are compatible in depth and scope with maintenance and logistics support concepts; and comply with requirements for Reading Grade Level (RGL) and security classification and distribution restriction marking. Quality processes are on-going for the life of the program. (Chapter 7)

1-8

XIII Start TO Development - After the Guidance Conference, the contractor will begin the TO development process. In some cases, where the program involves acquisition of commercial products, commercial manuals may already exist, in which case they will be reviewed for suitability to support the Air Force’s operations and maintenance concepts. In most cases, however, the TOs must be developed from scratch, using AF-approved Performance specifications (MIL-PRF-xxxxx). All data, including TOs, must be delivered in digital format unless this is proven not economical over the program’s life cycle. TOs should be developed using Standard Generalized Markup Language (SGML) tagging according to the Document Type Definitions (DTDs) attached to the MIL-PRF specs. (Chapter 4)

XIV TO IPRs - In-Process Reviews (IPRs) are held periodically to review preliminary TOs for accuracy, compliance with contract requirements, adequate depth of coverage for Air Force support, and usability.

These reviews may be held at specified percentages complete, or as determined necessary by the TO IPT.

Generally, the more critical and complex a TO is, the more frequent are the reviews. Reviews may be conducted on-line via a telecommunications infrastructure established by a Contractor Integrated Technical Information Services (CITIS) agreement when possible. (Chapter 6)

XV Refine TOMP/Draft TOVP - The TO Manager and TO IPT must continually refine the TOMP to account for changes in schedules, programs, plans, etc. They must draft a TO Verification Plan (TOVP), to cover such areas as the timing, location, support requirements, personnel, etc. for verification of the program’s TOs The TOVP may be an appendix or attachment to the TOMP. (Chapter 3)

XVI Product Baseline - This is not strictly a TO program event, but most of the following TO processes are dependent on having a baseline (or ‘‘production-configured’’) product as a reference.

XVII TOVP Finalized - At least 120 days before the first preliminary TOs are delivered to the government for verification, the TOVP must be finalized and provided to all participants. (Chapter 3)

XVIII TO Verification - Verification should begin as soon as possible after a base-line product is available.

Verification involves the actual performance, under field conditions, of all procedures and processes detailed in TOs. They should be performed by personnel of the same training and experience as personnel expected to use the system. Procedures which present a hazard to personnel or equipment, or which expend items such as explosive devices, may be verified by simulation or desk-top analysis. Non-procedural data may be verified by desk-top analysis or during IPRs. Any errors detected during verification are reviewed and provided to the contractor for correction of the TO. (Chapter 7)

XIX PrePub Reviews - Prepublication Reviews may be required before final izing and formalizing preliminary TOs. The determining factors are TO complexity and the number and complexity of changes resulting from verification. This determination may be made by the TO Review Board (TORB) or Flight TORB, if chartered to review and control configuration after PTO delivery to the government for verification. The TORBs are usually composed of TO IPT members. The TORBs will approve PTOs for formalization. (Chapters 6 and 7)

XX Deliver Formal TOs - The preferred method for TO delivery is via online access to the contractor’s database, using a CITIS agreement (DoD 5000.2-R). Prior to the implementation of JCALS, delivery should be in an indexed Adobe Portable Document Format (PDF) file. After JCALS is implemented, the SGML-tagged files should be delivered. (Chapter 4)

XXI TO Maintenance - Once TOs have been formalized and delivered to the Air Force, they enter the sustainment phase of their existence. Sustainment involves periodically updating TOs to maintain currency and accuracy. Factors driving updates include equipment modification, correction of errors, and im proved methods of performing procedures, among others (Chapter 9, TOs 00-5-1 and 00-5-15). Sustainment also involves managing the requisition, distribution, reproduction and archiving of TOs (AFMCMAN 21-1).

Maintenance begins once the TOs are formalized and continues through rescission of the TOs after the end item or system is retired from the inventory. Most Air Logistics Center acquisition programs fall into the TO sustainment category. Although contracts for sustainment may use abbreviated procedures for contract preparation, basic requirements do not change: there must be a CLIN and contract exhibit (TO CDRL and tailored TMCR document); TO update verification may be required if changes are extensive or complex.

XXII System Retirement - This is the ‘‘grave’’ of cradle-to-grave program management. TOs do not necessarily ‘‘die’’ when a system is retired frequently, TOs must be maintained to support Foreign Military Sales (FMS) programs. In addition, all TOs are maintained in the AF Repository for at least six years after the system is retired for AF use. (AFMCMAN 21-1)

1-9

Figure 1-2. Digital TO Acquisition Matrix (Sheet 1 of 2)

1-10

Figure 1-2. Digital TO Acquisition Matrix (Sheet 2 of 2)

1-11/(1-12 blank)

CHAPTER 2

RESPONSIBILITIES

2-1…