TOPP10Mar2015Rev52.pdf

UNITED STATES AIR FORCE

A-10

TECHNICAL ORDER PROCESS PLAN (TOPP)

FOR SOURCE DATA DELIVERIES

NOTE

The Technical Order Process Plan (TOPP) outlines the development process for all A-10 modifications making source data deliveries of technical data. This plan assumes Contractor source data will be used at verification and that the Contractor will support verification activities. This plan outlines the roles and responsibilities of the United States Air Force (USAF) and all Contractors who develop Technical Orders (TOs) for the A-10 aircraft. This plan is meant to be a guide to Contractors who develop TOs for the A-10 aircraft. Variations to the plan are authorized at the discretion of the A-10 TO Program Manager.

PREPARED BY: Len Mian/AFLCMC/WWAL/586-7150 DATE: 10 March 2015 Rev. 5.2

Technical Order Process Plan for Source Data Rev 5.1 23 Jan 2015

Table of Contents ……………………………………………………………………………………………………………..2 1 Technical Order Process

1.1 Scope

1.1.1 Introduction

1.1.2 Purpose

2 Reference Documents

2.1 Military Standards

3 Technical Order Development Process

3.1 TO Process Milestones

3.2 Technical Order Review Team (TORT)

3.2.1 TORT Membership

3.2.2 TORT Chairperson

3.3 Technical Order Process Descriptions

3.3.1 Proposal Phase

3.3.1.1 Planning Requirements

3.3.1.2 Process Description

3.3.2 Prior to Guidance Conference

3.3.2.1 Planning Requirements

3.3.2.2 Process Description

3.3.3 TO Guidance Conference

3.3.3.1 Planning Requirements

3.3.3.2 Process Description

3.3.3.3 Entrance Criteria

3.3.3.4 Exit Criteria

3.3.4 Technical Manual Launch (Internal Contractor Process)

3.3.4.1 Entrance Criteria

3.3.4.2 Process Description

3.3.5 Source Data Requirements

3.3.5.1 Text Updates

3.3.5.2 Graphic Updates

3.3.5.2.1 Communication

3.3.6 First Look In-Process Review (IPR)

3.3.6.1 Planning Requirements

3.3.6.2 Process Description

3.3.6.3 Entrance Criteria

3.3.6.4 Exit Criteria

3.3.7 Interim Development Cycle 1st Look (Internal Contractor Process)

3.3.7.1 Process Description

3.3.8 Second Look In-Process Review (IPR)

3.3.8.1 Planning Requirements

3.3.8.2 Process Description

3.3.8.3 Entrance Criteria

3.3.8.4 Exit Criteria

3.3.9 Interim Development Cycle 2nd Look (Internal Contractor Process)

3.3.9.1 Process Description

3.3.10 Validation/Certification

3.3.10.1 Planning Requirements

3.3.10.2 Process Description

3.3.10.3 Entrance Criteria

3.3.10.4 Exit Criteria

3.3.11 Verification

3.3.11.1 Planning Requirements

3.3.11.2 Process Description

3.3.11.3 Entrance Criteria

3.3.11.4 Exit Criteria

3.3.12 Dedicated Operational Test & Evaluation (OT&E) Support (As Required)

3.3.12.1 Planning Requirements

3.3.12.2 Process Description

3.3.12.3 Entrance Criteria

3.3.12.4 Exit Criteria

3.3.13 Verification Updates

3.3.13.1 Planning Requirements

3.3.13.2 Process Description

3.3.13.3 Entrance Criteria

3.3.13.4 Exit Criteria

3.3.14 Technical Order Formalization (USAF and TO Sustainment Contractor Process)

3.3.14.1 Planning Requirements

3.3.14.2 Process Description

3.3.14.3 Entrance Criteria

3.3.14.4 Exit Criteria

3.3.15 Prepublication Review

3.3.15.1 Planning Requirements

3.3.15.2 Process Description

3.3.15.3 Entrance Criteria

3.3.15.4 Exit Criteria

3.3.16 Prepublication Updates

3.3.16.1 Planning Requirements

3.3.16.2 Process Description

3.3.16.3 Entrance Criteria

3.3.16.4 Exit Criteria

3.3.17 Final Delivery

3.3.17.1 Planning Requirements

3.3.17.2 Process Description

3.3.17.3 Entrance Criteria

3.3.17.4 Exit Criteria

3.3.18 Lessons Learned

3.3.18.1 Planning Requirements

3.3.18.2 Process Description

Acronym List ………………………………………………………………………………………………………………... 22

Appendix A ………………………………………………………………………………………………………………….. 26

Appendix B ……………………………………………………………………………………………………………..…… 26

Appendix C ……………………………………………………………………………………………………………..…… 26

Appendix D ……………………………………………………………………………………………………………..…… 26

Change Page ……………………………………………………………………………………………………………….. 26

Figure 1: Contractor Technical Order Development Process

Rev 5.0 12 December 2014

1 TECHNICAL ORDER PROCESS

1.1 SCOPE

1.1.1 INTRODUCTION

The TOPP outlines the development process for all A-10 modifications making source data deliveries of technical data. This plan assumes Contractor source data will be used at verification and that the Contractor will support verification activities. This plan outlines the roles and responsibilities of the USAF and all Contractors who develop TOs for the A-10 aircraft. This plan is meant to be a guide to Contractors who develop TOs for the A-10 aircraft. Variations to the plan are authorized at the discretion of the A-10 TO Program Manager.

1.1.2 PURPOSE

The purpose of this document is to identify and document each step of the TO development process.

Within each step of the process this plan will outline the activity to take place, the requirements of each activity, and the roles and responsibilities for each party involved. A Technical Order Review Team (TORT) will be set up for each modification that deals with TO changes. This team will be made up of both USAF and Contractor members and will be chaired by a USAF member to ensure continuity during the development and review of TO changes.

1.1.3 INFORMATION EXCHANGE

Various opportunities for contractors to familiarize themselves with this process as well as provide the government with insight about their capabilities.

• Industry Day

• Unsolicited Proposal

• RFI

• White Paper

• Examples from the contractor (Schematics, job guides, IPBs, and other various TO examples)

This information exchange will be performed as necessary prior to or NLT at the TO Guidance Conference (TOGC). Prime contractors are ultimately responsible that all subcontractors are familiar with this process and that their data meets government’s requirements. Data reviews will be done with the prime contractors.

2 REFERENCE DOCUMENTS

2.1 MILITARY STANDARDS

• TM 86-01, Technical Manual Contractual Requirements (TMCR)

• TO 00-5-1, Air Force Technical Order System

• TO 00-5-3, Air Force Technical Order Life Cycle Management

• TO 00-5-15, Air Force Time Compliance Technical Orders

3 TECHNICAL ORDER DEVELOPMENT PROCESS

The TO process as outlined below is the method that the Contractor and the USAF will use to develop, review, and publish TOs to support each separate modification. The following paragraphs break down the process and define it so that it can be understood by the TORT and program team. The TORT will be defined at the Technical Order Guidance Conference (TOGC).

3.1 TO PROCESS MILESTONES

• TOGC held no later than (NLT) 60 calendar days after contract award.

• USAF verified source data submitted to TO sustainment contractor 153 calendar days prior to the fielding of the modification (see Appendix A).

o For expedited efforts (less than 50 pages) USAF verified source data submitted to TO sustainment contractor 111 calendar days prior to the fielding of the modification (see Appendix B).

3.2 TECHNICAL ORDER REVIEW TEAM (TORT)

The TORT is set up at the TOGC to establish efficiency in the TO process so that, wherever possible, the designated team will be at each of the reviews. This allows consistency across the review process so that there is the maximum number of reviewers knowledgeable with the material being presented.

3.2.1 TORT MEMBERSHIP

The TORT will be made up of USAF and Contractor members who will have the likelihood of staying on the program throughout the TO development process. This is important so that lessons learned and history from previous reviews will play a vital role in the development of new Tech Data.

3.2.2 TORT CHAIRPERSON

The chairperson will be a USAF individual who will lead the TORT and will be the point of contact (POC) for each TO review during the process. The chairperson is the TO Program Manager or their designate.

They will make sure all entrance and exit criteria are met. They will make sure all requirements are met with regard to the development of source data. They will supply leadership to the team and keep the process on track.

3.3 TECHNICAL ORDER PROCESS DESCRIPTIONS

3.3.1 PROPOSAL PHASE

3.3.1.1 Planning Requirements

• Provided with Performance Work Statement (PWS):

o Draft TM-86-01.

3.3.1.2 Process Description

The process starts during the PWS phase where the government supplies a draft TM-86-01 with a list of TOs to be proposed. The Contractor reviews the TM-86-01 and refines it during the developmental phase. As requirements change and TOs are added and removed from the TM-86-01, a revised TM-86- 01 shall be submitted to the Contractor thru the contracting office within 30 calendar days of a revision.

3.3.2 PRIOR TO GUIDANCE CONFERENCE

3.3.2.1 Planning Requirements

• USAF:

o Reviews TM-86-01 that was submitted with the proposal.

o Develops draft Technical Order Life Cycle Verification Plan (TOLCVP).

12 December 2014 o Develops and distributes an agenda for the TOGC.

• Contractor:

o Reviews TM-86-01 that was submitted with the proposal.

o Creates Integrated Master Schedule (IMS) in accordance with (IAW) contract requirements and this document.

o Starts initial planning to support TO development.

3.3.2.2 Process Description

When the contract is issued, the TM-86-01 will be delivered to the Contractor along with the contract. The Contractor then conducts their initial planning and reviews the TM-86-01 in preparation for the TOGC.

3.3.3 TO GUIDANCE CONFERENCE

The TOGC is where the TM-86-01 is revised, the TO schedule is reviewed, the TORT is set up, and the chairperson is identified. Following the TOGC, the USAF shall submit the revised TM-86-01 to the Contractor via a contract modification NLT 30 calendar days following the TOGC. The TOGC begins the Technical Order Development Process.

3.3.3.1 Planning Requirements

• USAF personnel:

o TO Program Manager.

o Technical Order Manager (TOMA).

o Flight Manual Manager (FMM)/Equipment Specialist(s) (ES).

o Air Force Modification Program Manager(s).

o Contracting Office Representative.

o ACC/A4 Representative(s) for Maintenance.

o ACC/A3 Representative(s) for Operations.

• Contractor support:

o Lead Logistics Engineer.

o Lead Technical Writer.

o Modification Program Manager.

o Engineering Support (as required).

3.3.3.2 Process Description

• USAF develops and distributes meeting agenda NLT 10 working days prior to the TOGC.

• Establish a TORT:

o USAF personnel:

TO Program Manager.

ACC/A3 Representative(s) for Operations

ACC/A4 Representative(s) for Maintenance.

TOMA.

FMM/ES(s).

Maintenance Subject Matter Expert(s).

Operations Subject Matter Expert(s).

o Contractor support:

Lead Logistics Engineer.

Lead Technical Writer.

• Review draft TOLCVP.

• Review program IMS and TO IMS.

• Revise TO requirements and TM-86-01.

• Submit revised TM-86-01 to contracting office.

• Government will discuss with contractor purpose of TCM assessment worksheet

• Minutes resulting from the TOGC are reviewed and concurred. The Contractor is responsible for developing and distributing the meeting minutes IAW CDRL requirements.

3.3.3.3 Entrance Criteria

• Agenda established and distributed.

• Draft TOLCVP established.

• Program IMS established.

• Original TM-86-01 that was submitted with the PWS.

3.3.3.4 Exit Criteria

• TORT established.

• Review draft TOLCVP.

• Program IMS and TO IMS content agreement.

• Revised TM-86-01.

• Minutes resulting from the TOGC are reviewed and concurred. The Contractor is responsible for developing and distributing the meeting minutes IAW CDRL requirements.

3.3.4 TECHNICAL MANUAL LAUNCH (INTERNAL CONTRACTOR PROCESS)

3.3.4.1 Entrance Criteria

• Revised TM-86-01 received thru contracting office.

3.3.4.2 Process Description

The Contractor TO development team shall develop the source data IAW the contract and TM-86-01.

Peer, technical, and quality reviews shall be completed by cognizant engineers, safety engineering (as required), and the Lead Logistics Engineer to ensure compliance with the contract and TM-86-01.

The source data development cycle is an internal process to the Contractor. The Contractor is responsible for ensuring the source data is technically accurate and meets all requirements as identified in the contract, TM-86-01, and applicable TO specification prior to submittal to the USAF. The following sections identify how the source data must be developed for the USAF.

3.3.5 SOURCE DATA REQUIREMENTS

3.3.5.1 Text Updates

When developing source data as text updates, the Contractor shall ensure the following requirements are met:

• The Contractor shall develop the data IAW the appropriate specification for each TO.

• Deliveries shall be IAW Part B – TM Delivery Requirements of the TM-86-01.

• Deliveries shall resemble an actual TO when delivered for reviews and final source data delivery (see Appendix C).

• Text updates made to the baseline TO shall be identified with red text to indicate the changes that were made (see Appendix C).

If uncertain with the requirements, the Contractor shall contact the TO Program Manager for direction on how to proceed.

3.3.5.2 Graphic Updates

When developing source data as graphic updates, the Contractor shall ensure the following requirements are met:

• The Contractor shall develop the data IAW the appropriate specification for each TO.

• Deliveries shall be IAW Part B – TM Delivery Requirements of the TM-86-01.

• The figure naming convention should indicate the modification, TO number, and a control number. For example, a figure created for the Wing Replacement Program modification that impacts the 1A-10C-2-34JG-1 should be named something similar to WRP-34JG1-001.

• The Contractor shall ensure that lines remain consistent when the file is zoomed to 300 percent.

An example includes making certain the lines connect at intersections.

• The Contractor shall submit a first article test for each type of manual (JG, TS, IPB, etc.) to the TO Program Manager prior to first look In Process Review (IPR) to ensure the file is compatible with electronic TOs and SGML. The Contractor shall work with the TO Program Manager to resolve any issues with graphics that fail the first article test.

• Deliveries shall resemble an actual TO when delivered for reviews and final source data delivery (see Appendix C). Red line graphics are not acceptable at reviews and for final delivery.

• All graphics are to be submitted as vectorized level 4 CGM files. If a Contractor impacts a graphic that has not been converted to vectorized level 4 CGM, the Contractor is responsible for redrawing the entire graphic to the vectorized level 4 CGM format.

• Graphic updates made to the baseline TO shall be identified with red text to indicate the changes that were made (see Appendix C).

If uncertain with the requirements, the Contractor shall contact the TO Program Manager for direction on how to proceed.

3.3.5.3 Communication

Weekly communication meetings between the Contractor and the USAF will be established to discuss progress and any potential roadblocks.

• As early as 30 days post TOGC, government may request samples of text and vectorized CGM files for all TOs prescribed in the TM-86-01. These may include schematics, job guides, checklists, and troubleshooting manuals.

3.3.5.3 Sample Source Data Delivery

• Minimum of 30 days prior to 1st Look IPR, the contractor will deliver A-10 specific samples of text and vectorized CGM files for all TOs prescribed in the TM-86-01 to the Program Manager. These may include schematics, job guides, checklists, and troubleshooting manuals.

• These files will be used in the pre-IPR assessment to determine readiness for 1st Look IPRs (MX and FM).

3.3.6 PRE IN-PROCESS REVIEW (IPR) ASSESSMENT

3.3.6.1 Process Description

• PMs will provide TCMs contractor samples of source data

• TCMs will provide TOMA a completed TCM assessment (Govt) worksheet

3.3.6.2 Exit Criteria

• TORT will decide if contractor is ready for IPR based on TCM assessment worksheet

3.3.7 FIRST LOOK IN-PROCESS REVIEW (IPR)

3.3.7.1 Planning Requirements

For planning purposes, maintenance and flight manual reviews may occur at different times and venues.

• USAF personnel:

o TORT members.

o Minimum of two USAF Subject Matter Experts [(4 preferred) funded by program].

• Contractor support:

o TORT Members.

o Graphics technician (At government discretion).

o Engineering/Technical Support (as required).

o Technical Writer

• To occur no earlier than the availability of 100 percent of the TOs identified in the TM-86-01.

3.3.7.2 Process Description

• Contractor and USAF review of technical document updates.

• TORT verification that the baseline TOs used to develop source data matches the latest released TOs.

• The Contractor will maintain a single master copy of each TO containing all comments captured at the review and provide the USAF a copy at the end of the review.

• Material shall be posted to a USAF approved internet based information storage location (i.e.

TeamCenter, SharePoint) IAW TM-86-01 requirements. The Contractor shall contact the TO Program Manager for information regarding USAF approved internet storage locations.

• Attendance and formal action items will be taken.

• AFTO Form 158(s) shall be generated.

12 December 2014

• Agenda and Minutes will be distributed IAW CDRL requirements.

3.3.7.3 Entrance Criteria

• Revised TM-86-01 received thru contracting office.

• Meeting agenda developed and distributed by the Contractor NLT 10 working days prior to the

IPR.

• Minimum of 35% of data required at time of scheduled review.

• Review material quantities provided IAW TM-86-01.

• Minimum of two USAF Subject Matter Experts.

3.3.7.4 Exit Criteria

• 100% percent of presented data reviewed.

• Agreed upon TO baseline for documentation updates.

• AFTO Form 158s resulting from First Look IPR are reviewed for concurrence:

o Each TO will have an AFTO Form 158, even if no corrections are needed.

• Review of scheduled Second Look IPR date for staffing conflicts.

• Minutes resulting from First Look IPR are reviewed and concurred. The Contractor is responsible for developing and distributing the meeting minutes IAW CDRL requirements.

3.3.7.5 Post IPR Government Assessment

• Draft AFTO Form 158 review

Government team consists of government only TORT members (PM, PK, TCM, TOMA, Engineer)

If in the team’s review, the IPR had minimal issues, this assessment can be done via email notification from the TCM

If in the team’s review, the IPR had multiple issues, the assessment team will exercise contract performance/remedies

3.3.8 INTERIM DEVELOPMENT CYCLE 1ST LOOK (INTERNAL CONTRACTOR PROCESS)

3.3.8.1 Process Description

• Disposition of AFTO Form 158 comments from First Look IPR.

• Incorporation of all remaining software and hardware material following the procedures outlined in section 3.3.5 of this document.

3.3.9 PRE-IN PROCESS REVIEW (IPR) ASSESSMENT

3.3.9.1 Process Description

• PMs will provide TCMs contractor samples of source data

• TCMs will provide TOMA a completed TCM assessment worksheet

12 December 2014

3.3.9.2 Exit Criteria

• TORT will decide if contractor is ready for IPR based on TCM assessment worksheet

3.3.10 SECOND LOOK IN-PROCESS REVIEW (IPR)

3.3.10.1 Planning Requirements

For planning purposes, maintenance and flight manual reviews may occur at different times and venues.

• USAF personnel:

o TORT Members.

o Minimum of two USAF Subject Matter Experts [(4 preferred) funded by program].

• Contractor support:

o TORT members.

o Graphics technician (At government discretion).

o Engineering/Technical Support (as required).

o Technical Writer

3.3.10.2 Process Description

• Contractor and USAF review of source data updates.

• TORT verification that the baseline TOs used to develop source data matches the latest released TOs.

• The Contractor will maintain a single master copy of each TO containing all comments captured at the review and provide the USAF a copy at the end of the review.

• Material shall be posted to a USAF approved internet based information storage location (i.e.

Windchill, TeamCenter, SharePoint) IAW TM-86-01 requirements. The Contractor shall contact the TO Program Manager for information regarding USAF approved internet storage locations.

• Attendance and formal action items will be taken.

• AFTO Form 158(s) shall be generated.

• Agenda and minutes will be distributed IAW CDRL requirements.

3.3.10.3 Entrance Criteria

• Meeting agenda developed and distributed by the Contractor NLT 10 working days prior to the

IPR.

• Minimum of 75% of data required at time of scheduled review.

• First Look AFTO Form 158 comments are dispositioned.

• Review material quantities provided IAW TM-86-01.

• Minimum of two USAF Subject Matter Experts.

3.3.10.4 Exit Criteria

• 100% percent of presented data reviewed.

• Agreed upon TO baseline for documentation updates.

• Incorporation of AFTO Form 158s from First Look IPR are verified.

• AFTO Form 158s resulting from Second Look IPR are reviewed for concurrence:

o Each TO will have an AFTO Form 158, even if no corrections are needed.

• Review of scheduled Verification date for staffing/equipment conflicts.

• Minutes resulting from Second Look IPR are reviewed and concurred. The Contractor is responsible for developing and distributing the meeting minutes IAW CDRL requirements.

3.3.10.5 Post IPR Government Assessment

• Draft AFTO Form 158 review

Government team consists of government only TORT members (PM, PK, TCM, TOMA, Engineer)

If in the team’s review, the IPR had minimal issues, this assessment can be done via email notification from the TCM

If in the team’s review, the IPR had multiple issues, the assessment team will exercise contract performance/remedies

3.3.11 INTERIM DEVELOPMENT CYCLE 2ND LOOK (INTERNAL CONTRACTOR PROCESS)

3.3.11.1 Process Description

• Disposition of AFTO Form 158s comments from Second Look IPR.

• Incorporation of all remaining software and hardware material following the procedures outlined in section 3.3.5 of this document.

3.3.12 VALIDATION/CERTIFICATION

3.3.12.1 Planning Requirements

• Notify Government of validation/certification event.

• TORT Members (as needed).

3.3.12.2 Process Description

To the greatest extent possible, validation/certification is to be done on field representative assets. The Contractor shall perform TO validation/certification on all affected manuals and TCTO validation/certification of all TCTO requirements during the Contractor’s integration and ground/flight test activities. Updates may be done real time but shall be performed IAW Contractor established processes to ensure appropriate disposition and incorporation.

3.3.12.3 Entrance Criteria

• Completion of Second Look IPR.

• Second Look IPR AFTO Form 158s comments are dispositioned.

• A single master copy will be maintained for red line comments.

3.3.12.4 Exit Criteria

• Incorporation of all AFTO Form 158s from Second Look IPR is verified.

• 100% percent of affected manuals validated/certified.

• Validation/certification status/results reported to TORT Chairperson.

• Corrections, if required, incorporated into source data prior to Verification data delivery.

3.3.13 PRE-VERIFICATION REVIEW ASSESSMENT

3.3.13.1 Process Description

• PMs will provide TCMs contractor samples of source data

• TCMs will provide TOMA a completed TCM assessment worksheet

3.3.13.2 Exit Criteria

• TORT will decide if contractor is ready for IPR based on TCM assessment worksheet

3.3.14 VERIFICATION

3.3.14.1 Planning Requirements

For planning purposes, maintenance and flight manual verifications may occur at different times and venues.

• USAF support:

o TORT Members.

o Minimum of two USAF Subject Matter Experts [(4 preferred) funded by the program].

o Memorandum of Agreement (MOA) in place for verification with host unit.

o Maintenance Requirements:

Applicable AFSC technicians (minimum one 3 level and one 5 level of each identified AFSC as required).

USAF Quality Assurance representation.

Aircraft in correct configuration including hardware and software available for the entire verification timeframe.

All required support equipment available as needed.

• Contractor support:

o TORT Members.

3.3.14.2 Process Description100

• Draft AFTO Form 158s resulting from Verification are created, reviewed and approved:

o Copy of draft AFTO Form 158s provided to the Verification Team Manager (VTM).

12 December 2014

• The Contractor will maintain a single master copy containing all comments and provide a copy to the TO Program Manager at the end of the review.

• Each TO will have an AFTO Form 27/82 completed and signed:

o If no corrections are needed, annotate “No corrections required, ready for TO Formalization” in block 17 and 18.

o If corrections needed, annotate “See attached AFTO Form 158” in block 17 and 18.

• Agenda and minutes will be distributed IAW CDRL requirements.

3.3.14.3 Entrance Criteria

• Memorandum of Agreement (MOA) in place for verification with host unit.

• Meeting agenda developed and distributed by the USAF NLT 10 working days prior to the verification. (At government discretion)

• Review material quantities provided IAW TM-86-01.

• TOMA will supply PTO revision/change level PDF files to support review.

• Applicable Air Force Specialty Code (AFSC) technicians (Maintenance):

o Minimum one 3 level and one 5 level for each identified AFSC as required.

• USAF Quality Assurance representation (Maintenance).

• Aircraft in correct configuration including hardware and software available for the entire verification timeframe (Maintenance).

• All required support equipment available as needed (Maintenance).

• Applicable Subject Matter Expert(s) (Operations).

• 100% of data available at time of scheduled review.

3.3.14.4 Exit Criteria

• 100% percent of presented data reviewed.

• Minutes resulting from verification are developed by the USAF and reviewed with the Contractor prior to distribution.

• AFTO Form 158s (for manuals requiring corrections) resulting from verification are reviewed and approved:

o AFTO Form 158s need to be created for all manuals including manuals with no comments. Then the comment is “No corrections required”.

o Copy of AFTO Form 158s provided to the VTM and Contractor lead.

• Each TO will have AFTO form 27/82 completed and signed by the VTM.

• Aircraft configuration returned to approved baseline (Maintenance).

3.3.15 DEDICATED OPERATIONAL TEST & EVALUATION (OT&E) SUPPORT (AS

REQUIRED)

3.3.15.1 Planning Requirements

• USAF personnel:

o OT&E Test Personnel.

o TO Program Manager.

o TOMA.

o TODO.

o ACC.

o TCM .

• Contractor support (as needed):

o Engineering/Technical Support.

o Technical Writer.

3.3.15.2 Process Description

• Approved AFTO Form 158s for all manuals resulting from verification are provided by the USAF to the TODO at the testing agency for OT&E.

• The TORT chairperson provides a copy of all redlined TOs to the TOMA for marking.

• TOMA shall watermark all TOs indicating that that the TOs are to be used for OT&E only and that all TOs shall be destroyed once the final TOs are released.

• TOMA creates CD and sends to TODO at testing agency.

o TOMA shall work with testing agency to ensure the least amount of people have access to the CD.

• OT&E Test Personnel shall document all comments not already captured on an existing AFTO Form 158 on a new AFTO Form 158 and submit to the TO Program Manager for incorporation in a future Block Cycle Release (BCR).

3.3.15.3 Entrance Criteria

• All TOs from the modification shall be verified prior to the start of OT&E.

• TODO at testing agency has downloaded and has a copy of all TOs on a CD.

• TODO at testing agency has a copy of all approved AFTO Form 158s from verification.

3.3.15.4 Exit Criteria

• All preliminary TOs used for OT&E shall be destroyed as soon as final TOs are made available.

• All comments captured by the OT&E Test Personnel shall be submitted to the TO Program Manager for incorporation in a future BCR.

3.3.16 VERIFICATION UPDATES

3.3.16.1 Planning Requirements

• USAF personnel:

o TO Program Manager.

o ES/FMM.

o TOMA.

• Contractor support (as needed):

o Lead Logistics Engineer.

o Lead Technical Writer.

3.3.16.2 Process Description

• The Contractor shall provide the TO Program Manager with a list of impacted manuals with page and graphic counts.

• The TO Program Manager shall provide the list of impacted manuals with page and graphic counts to the TO sustainment contractor for a Rough Order of Magnitude (ROM).

• The Contractor shall disposition all AFTO Form 158s from verification for each manual.

• The Contractor shall update the TO source data as required prior to submittal to the USAF.

• The Contractor shall formally submit the TO source data to the USAF as a CDRL.

• The USAF shall review the CDRL and accept or reject as required.

o If the CDRL is rejected, the TO Program Manager shall work with the Contractor to resolve any discrepancies.

3.3.16.3 Entrance Criteria

• Completion of verification.

• Verification AFTO Form 158s comments supplied.

3.3.16.4 Exit Criteria

• Incorporation of all AFTO Form 158s from verification are verified and dispositioned.

• Contractor formally submits TO source data as a CDRL to the USAF and the CDRL is approved.

• Delivery Order (DO) in place for TO sustainment contractor to incorporate source data into TO baseline.

3.3.17 TECHNICAL ORDER FORMALIZATION (USAF AND TO SUSTAINMENT

CONTRACTOR PROCESS)

NOTE

The USAF and the TO sustainment contractor are responsible for the TO formalization process. The Contractor responsible for developing the TO source data is not responsible for any of the tasks outlined in this section.

SOURCE DATA

DELIVERY TO

SUSTAINMENT CTR

(0 DAYS)

TO UPDATES

(60 DAYS)

END

DELIVERY TO USAF

FOR PRE-PUB

(0 DAYS)

ES/FMM PRE-PUB

REVIEW

(12 DAYS)

UPDATES TO

SUSTAINMENT CTR

(0 DAYS)

TO UPDATES

(5 DAYS)

DELIVERY TO USAF

FOR FINAL LOOK

(0 DAYS)

ES/FMM REVIEW

(3 DAYS)

USAF APPROVAL

OF TOs

(0 DAYS)

FINAL TO

PACKAGE

DEVELOPED

(12 DAYS)

DELIVERY TO USAF

(0 DAYS)

TOMA

DISTRIBUTES TO

TODOs

(5 DAYS)

DAPS PRINTING

(26 DAYS)

USAF ACCEPTS/

REJECTS CDRL

(30 DAYS)

CALENDAR

DAYS

Figure 2: TO Formalization Timeline

3.3.17.1 Planning Requirements

• The TO Program Manager shall work with the TO sustainment contractor to develop a schedule and prioritized list of TOs.

• The TO Program Manager submits a disk(s) containing all source data to the TO sustainment contractor.

3.3.17.2 Process Description

• The TO sustainment contractor logs the delivery order into their tracking system.

• The TO sustainment contractor performs a review of the source data. If the data is not useable, the TO Program Manager is contacted for clarification.

• Once the data has been rolled into the TO baseline, a quality check is performed on each manual.

• If the manual passes the quality check, a PDF of each manual is created and delivered to the TO Program Manager in preparation for prepublication review.

• The TOMA posts the PDFs to SharePoint for ES/FMM review.

• The appropriate ES/FMM reviews the prepublication copy for format and content.

3.3.17.3 Entrance Criteria

• Completion of verification.

• Contractor source data CDRL approved by USAF.

• Delivery Order (DO) in place for TO sustainment contractor to incorporate source data into TO baseline.

3.3.17.4 Exit Criteria

• 100% of presented data is reviewed.

• Incorporation of comments from prepublication review are verified.

3.3.18 PREPUBLICATION REVIEW

3.3.18.1 Planning Requirements

• USAF support:

o TO Program Manager.

o TOMA.

o ES/FMM.

• TO sustainment contractor.

3.3.18.2 Process Description

• TOMA and ES/FMM reviews each PDF to confirm the following:

o TO contains all comments from verification.

o TO meets AF specification.

o TO is at the correct revision level.

o For change pages, confirms that the new changes fit into the existing baseline manual.

• An email from the ES/FMM will be provided to the TOMA identifying concurrence and approval with the changes. If additional changes are required, the ES/FMM shall redline the PDF and provide a copy to the TOMA. The TOMA will then forward the email identifying concurrence and approval or the redlined PDF to the TO sustainment contractor for their action.

3.3.18.3 Entrance Criteria

• Contractor TO source data has been incorporated into the TO baseline in preparation for prepublication review.

• TO sustainment contractor posts the TOs to SharePoint for ES/FMM review.

3.3.18.4 Exit Criteria

• All comments from prepublication review are incorporated and verified.

• 100% percent of presented data reviewed and approved (TOMA/ES/FMM).

3.3.19 PREPUBLICATION UPDATES

3.3.19.1 Planning Requirements

• USAF support:

o TO Program Manager.

o ES/FMM.

o TOMA.

• TO sustainment contractor.

3.3.19.2 Process Description

• The TOMA shall provide the TO sustainment contractor an email identifying concurrence and approval with the changes. If additional changes are required, the ES/FMM shall redline the PDF and provide a copy to the TOMA. The TOMA shall then forward the redlined PDF to the TO sustainment contractor for their action.

• The TO sustainment contractor logs the action into their tracking system.

• As needed, the TO sustainment contractor performs a review of the redlined PDF for each manual. The TO sustainment contractor incorporates and dispositions all comments:

o The TO sustainment contractor works with the ES/FMM on issues regarding technical assistance.

• Once the data has been rolled into the TO baseline, a quality check is performed on each manual.

• If the manual passes the quality check, an IPDF of each manual is created and delivered to the TOMA in preparation for final delivery.

• The TOMA and ES/FMM reviews the final copy for format and content.

3.3.19.3 Entrance Criteria

• Prepublication redlined PDF comments dispositioned.

3.3.19.4 Exit Criteria

• All comments from prepublication review are incorporated and verified.

• The TOMA provides an email approval to the TO sustainment contractor that the TOs are ready for final delivery.

3.3.20 FINAL DELIVERY

3.3.20.1 Planning Requirements

• USAF support:

o TORT Members.

• TO sustainment contractor.

3.3.20.2 Process Description

• The TO sustainment contractor transforms the SGML source data and graphics to IPDF output.

• The TO sustainment contractor performs a quality check of the IPDF using the eTOV GPS (C2+).

• The TO sustainment contractor views one IPDF of each doctype using the government provided

Toughbook to ensure the IPDF is compatible with the USAF common desktop.

• The TO sustainment contractor compiles the data (SGML, IPDF, graphics, etc.) in preparation for final delivery.

• The TO sustainment contractor creates the TO sets for distribution.

• The TO sustainment contractor performs a quality check of the delivery.

• The TO sustainment contractor submits the delivery to the TO Program Manager as a CDRL.

3.3.20.3 Entrance Criteria

• All comments from prepublication review are incorporated and verified.

3.3.20.4 Exit Criteria

• Formal delivery of TOs in accordance with TM-86-01.

• Acceptance of CDRL.

o If the CDRL is rejected, the TO Program Manager shall work with the TO sustainment contractor to resolve any discrepancies.

3.3.21 LESSONS LEARNED

3.3.21.1 Planning Requirements

• USAF personnel:

o TO Program Manager.

o TOMA.

o ES/FMM.

o Air Force Program Manager.

o ACC/A4 Representative for Maintenance.

o ACC/A3 Representative for Operations.

• Contractor support:

o Lead Logistics Engineer.

o Lead Technical Writer.

o Program Office representative.

o Engineering Support (as required).

• TO sustainment contractor.

3.3.21.2 Process Description

• Each member of the TORT is to provide a document to the TORT chairperson that highlights the accomplishments and challenges of the program.

• The TORT chairperson is to compile and review all comments from the TORT and arrange a meeting to discuss the results.

• The results are then to be formalized and used to develop an action plan to improve the TO development process.

12 December 2014

Acronym List ACC Air Combat Command

AF (United States) Air Force

AFSC Air Force Specialty Code

AFTO Air Force Technical Order

BCR Block Cycle Release

CD Compact Disk

CDRL Contract Data Requirements List

CPS Command Publishing System

CRM Candidate Review Meeting

ES Equipment Specialist eTO Electronic Technical Order eTOV Electronic Technical Order Viewer

FMM Flight Manual Manager

IAW In Accordance With

ILS Integrated Logistics Support

IMS Integrated Master Schedule

IPDF Indexed Portable Document Format

IPR In Process Review

LOE Level of Effort

MOA Memorandum of Agreement

OT&E Operational Test and Evaluation

PDF Portable Document Format

POC Point of Contact

PP Pre Publication

PTR Problem Tracking Report

PWS Performance Work Statement

RFP Request for Proposal

ROM Rough Order of Magnitude

SGML Standard Generalized Mark-up Language

SIL Systems Integration Lab

SOW Statement of Work

SPO System Program Office

SRD Suite Release Date

TCM Technical Content Manager

TD Technical Data

12 December 2014

TDV Technical Data Verification

TM Technical Manual

TMCR Technical Manual Contractual Requirements

TO Technical Order

TODO Technical Order Distribution Office

TOGC Technical Order Guidance Conference

TOMA Technical Order Manager

TOLCMP Technical Order Life Cycle Management Plan

TOPP Technical Order Process Plan

TORT Technical Order Review Team

TOLCVP Technical Order Life Cycle Verification Plan

TRB Technical Review Board

USAF United States Air Force

VTM Verification Team Manager

WDD Work Description Document

3.3.5.3 Sample Source Data Delivery