Appendix_A_-_Technical_Order_Process_Plan_(TOPP).pdf

APPENDIX A

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. It 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.

PREPARED BY: Len Mian/OO-ALC/GHAEH/586-7150

DATE: 17 April 2012

Rev. 3.0

Technical Order Process Plan for Source Data Rev 3.0 17 April 2012

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.1.1 Update to Existing Material

3.3.5.1.2 Creation of New Material

3.3.5.1.3 Communication

3.3.5.2 Graphic Updates

3.3.5.2.1 Update to Existing Material

3.3.5.2.2 Creation of New Material

3.3.5.2.3 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 1

st 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 2

nd

Look (Internal Contractor Process)

3.3.9.1 Process Description

3.3.10 Validation

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 Technical Order Formalization

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 Verification

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 Dedicated Operational Test & Evaluation (OT&E) Support

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 Verification Updates

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 ……………………………………………………………………………………………………………..…. 23 Change Page ……………………………………………………………………………………………………………….. 25

GENERATE DRAFT

TMCR

RFP REVIEW

PROPOSAL KICKOFF

MEETING

CONTRACT LAUNCH TM PLANNING

T.O. GUIDANCE

CONFERENCE

START

RECEIVE TMCR

THRU

CONTRACTS

TM LAUNCH /

KICKOFF

PRIME WRITING AND

GRAPHICS UPDATES

PRIME REVIEW OF

T.O. UPDATES

PRIME WRITING AND

GRAPHICS UPDATES QA REVIEW

TEXT GRAPHICS (CGM) TEXT GRAPHICS (CGM)

ENGINEERING

TECHNICAL REVIEW

FIRST LOOK IN

PROCESS REVIEW

PRIME

DEVELOPMENT

CYCLE

SECOND LOOK IN

PROCESS REVIEW

PRIME

DEVELOPMENT

CYCLE

T.O.

VALIDATION /

CERTIFICATION

SOURCE DATA

DELIVERY TO USAF

SOURCE DATA

DELIVERY TO T.O.

SUSTAINMENT

CONTRACTOR

T.O.

SUSTAINMENT

CONTRACTOR

T.O. UPDATES

T.O.

SUSTAINMENT

CONTRACTOR

T.O. UPDATES

T.O. VERIFICATION

T.O.

SUSTAINMENT

CONTRACTOR

T.O. UPDATES

T.O. SUSTAINMENT

CONTRACTOR

DELIVERY TO USAF

CORRECTIONS

DELIVERED TO T.O.

SUSTAINMENT

CONTRACTOR

END

FINAL DELIVERY

TO USAF

LESSONS

LEARNED

USAF

REVIEW

PRE PUB

REVIEW

PEER REVIEW AND

UPDATES

PRIME LOE SUPPORT

PRIME TO DEVELOPMENT CYCLE

CORRECTIONS

DELIVERED TO T.O.

SUSTAINMENT

CONTRACTOR

T.O. SUSTAINMENT

CONTRACTOR

DELIVERY TO USAF

Figure 1 Technical Order Development Process

1 TECHNICAL ORDER PROCESS

1.1 SCOPE

1.1.1 INTRODUCTION

The Technical Order Process Plan (TOPP) outlines the development process for all A-10 modifications. It 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.

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.

2 REFERENCE DOCUMENTS

2.1 MILITARY STANDARDS

TM 86-01, Technical Manual Contractual Requirements (TMCR) for each delivery order

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 delivery order. 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

Source data to TO sustainment contractor for Verification Publications [Tech Data Verification (TDV) minus 60 calendar days].

TDV, all data [Modification Release Date (MRD) minus 120 calendar days].

Final data submittal to TO sustainment contractor (MRD minus 90 calendar days).

Modification/Technical Order Release (Fielding) Date (MRD):

o Note the above are start dates.

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 chair 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 Request for Proposal (RFP):

o Draft TMCR.

o Technical Order Management Plan (TOMP).

3.3.1.2 Process Description

The process starts during the RFP phase where the government supplies a draft TMCR with a list of TOs to be proposed. The contractor reviews and updates the TMCR, submits it with the proposal, and refines it during the developmental phase. As requirements change and TOs are added and removed from the TMCR, a revised TMCR shall be submitted to the USAF through contracts prior to TO verification.

3.3.2 PRIOR TO GUIDANCE CONFERENCE

3.3.2.1 Planning Requirements

USAF:

o Reviews TMCR that was submitted by the contractor with the proposal.

o Reviews the notional list of candidates for suite release or engineering technical data for hardware modifications.

o Develops draft Technical Order Verification Plan (TOVP).

Contractor:

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

o Start initial planning to support TO development.

3.3.2.2 Process Description

When the contract is issued, the TMCR will be delivered to the contractor along with the contract. The contractor then conducts their initial planning and updates the TMCR in preparation for the TOGC.

3.3.3 TO GUIDANCE CONFERENCE

The TOGC is where the TMCR is finalized, the TO plan and schedule are reviewed, the TORT is set up, and the chairperson is identified. Following the TOGC, the USAF will submit the finalized TMCR to the contractor via a contract modification (no later than 30 calendar days following the TOGC). The TOGC begins the Technical Order Development Process.

3.3.3.1 Planning Requirements

USAF personnel:

o Technical Order Program Manager.

o Technical Order Management Activity (TOMA) representative.

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

o Air Force Modification Program Manager(s).

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 Program Office representative.

o Engineering Support (as required).

3.3.3.2 Process Description

Establish a TORT:

o USAF personnel:

ACC/A4 Representative(s) for Maintenance.

TOMA representative(s).

FMM/ES(s).

Maintenance Subject Matter Expert(s).

Operations Subject Matter Expert(s).

o Contractor support:

Lead Logistics Engineer.

Lead Technical Writer.

Review TOVP.

Review program IMS and TO integrated IMS.

Finalize TO requirements and TMCR.

Submit TMCR to contracting office.

3.3.3.3 Entrance Criteria

Draft TOVP.

Program IMS.

Updated TMCR.

Initial Candidate List for suites and engineering technical data for hardware modifications.

3.3.3.4 Exit Criteria

TORT established.

TOVP content agreement.

Program IMS and TO integrated IMS content agreement.

TMCR content agreement.

Minutes generated per applicable Statement of Work (SOW).

3.3.4 TECHNICAL MANUAL LAUNCH (INTERNAL CONTRACTOR PROCESS)

3.3.4.1 Entrance Criteria

TMCR received through contracts.

3.3.4.2 Process Description

The Lead Technical Writer working with the Lead Logistics Engineer, Hardware Engineers, Systems Engineers, and Installation Engineers shall develop the source data in accordance with the contract and

TMCR.

Peer, technical, and quality reviews shall be completed by cognizant engineers, safety engineering (as required), and the Technical Data Manager to ensure compliance with the contract and TMCR.

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 indentified in the contract and TMCR 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, there are two categories: updates to existing material and creation of new material.

3.3.5.1.1 Update to Existing Material

When developing source data that updates existing material, the contractor shall ensure the following requirements are met:

Deliveries shall be in Adobe Acrobat PDF, Microsoft Word, and/or Microsoft Excel.

Annotation of updates shall be marked with blue text. Annotations that precede the update shall be marked with red text and identify why the update is being made (modification, legacy, 158 comment).

Updates shall be clear enough to understand the updates required. Examples would be “Replace step 7 with the following….”, “Change the following sentence to read…..”. and “Replace section

1.1 with the following….”.

If uncertain with the requirements, the contractor shall contact the TO program manager for direction on how to proceed.

3.3.5.1.2 Creation of New Material

When developing source data that involves the development of new material, the contractor shall ensure the following requirements are met:

New text updates shall be developed by creating a Microsoft Word document and identifying where the new material should be inserted. For example, “Create a new section 1.8 by inserting document xxx.doc after section 1.7”.

New table updates shall be made by creating a Microsoft Excel file and identifying where the new material should be inserted. For example. “Create new table 1.9 with file xxx.xls”.

Bold and italic shall not be used in any file.

The font type shall be Arial 10 point.

If uncertain with the requirements, the contractor shall contact the TO program manager for direction on how to proceed.

3.3.5.1.3 Communication

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

3.3.5.2 Graphic Updates

When developing source data as graphic updates, there are two categories: updates to existing material and creation of new material.

3.3.5.2.1 Update to Existing Material

When developing source data that updates existing material, the contractor shall ensure the following requirements are met:

Updates shall be made directly in the PDF using the comment function in Adobe Acrobat.

Annotation of updates shall be marked with blue text. Annotations that precede the update shall be marked with red text and identify why the update is being made (modification, legacy, 158 comment.

Updates shall be clear enough to understand the updates required. Examples would be “Change callout 7 to callout 8”, and “Add callout 9 to show new radio”.

If uncertain with the requirements, the contractor shall contact the TO program manager for direction on how to proceed.

3.3.5.2.2 Creation of New Material

When creating source data that involves the development of new material, the contractor shall ensure the following requirements are met:

New graphic updates shall be vectorized CGM files.

The figure naming convention should indicate the modification and a control number. For example, a figure created for the Wing Replacement Program modification should be named something similar to WRP001.

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.

Font style and size must be consistent throughout the image.

Bold and italic shall not be used in any file.

The contractor shall submit a first article test for each type of manual (JG, TS, IPB, etc.) to the TO program manager 60 calendar days prior to TO verification to ensure the file is compatible with electronic TOs and SGML.

If uncertain with the requirements, the contractor shall contact the TO program manager for direction on how to proceed.

3.3.5.2.3 Communication

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

3.3.6 FIRST LOOK IN-PROCESS REVIEW (IPR)

3.3.6.1 Planning Requirements

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 (As required).

o Engineering support (As required).

To occur no earlier than System Integration Lab (SIL) software drop X.2 start date plus 30 calendar days for suite releases.

To occur no earlier than the release of preliminary engineering drawings plus 30 calendar days for hardware modifications.

3.3.6.2 Process Description

Contractor review of technical document updates.

TORT verification that the baseline TOs used to develop documentation updates matches the latest released TOs.

A single master copy containing all comments will be maintained and provided to the contractor 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 TMCR requirements.

Agenda will be established, 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.6.3 Entrance Criteria

TMCR received through contracting office.

Meeting agenda developed and distributed.

100% of data available at time of scheduled review:

o Graphics may be redline representations.

Review material quantities IAW TMCR.

Minimum of two USAF Subject Matter Experts.

3.3.6.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.

Draft minutes resulting from First Look IPR are reviewed and concurred.

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

3.3.7.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.8 SECOND LOOK IN-PROCESS REVIEW (IPR)

3.3.8.1 Planning Requirements

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 (As required).

o Engineering support (As required).

To occur no earlier than SIL software drop X.3 start date plus 30 calendar days for suite releases.

To occur no earlier than the release of revised engineering drawings plus 30 calendar days for hardware modifications.

3.3.8.2 Process Description

Contractor review of technical document updates.

TORT verification that the baseline TOs used to develop documentation updates matches the latest released TOs.

A single master copy containing all comments will be maintained and provided to the contractor at the end of the review.

Material (Dispositioned AFTO Form 158s) shall be posted to a USAF approved internet based information storage location (i.e. Windchill, TeamCenter, SharePoint) IAW TMCR requirements.

Agenda will be established, 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.8.3 Entrance Criteria

Meeting agenda developed and distributed.

100% of data available at time of scheduled review:

o Graphics may be redline representations.

o Note: X.4 is a clean up release only for suites. Impact assessments will be performed by the Lead Logistics Engineer and Lead Technical Writer to determine TO impact for all X.4 updates and to determine if the update can be made without impacting cost or schedule.

Updates impacting cost and schedule will be communicated to the contractor Program Office and TORT chairperson.

First Look AFTO Form 158 comments are dispositioned.

Review material quantities IAW TMCR.

Minimum of two USAF Subject Matter Experts.

3.3.8.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.

Draft Minutes resulting from Second Look IPR are reviewed and concurred.

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

3.3.9.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.10 VALIDATION

3.3.10.1 Planning Requirements

Notify Government of Validation event.

TORT Members (as needed).

3.3.10.2 Process Description

To the greatest extent possible, validation is to be done on field representative assets. The contractor shall perform TO validation on all affected manuals and TCTO validation of all TCTO requirements during the contractor’s integration and ground/flight test activities. Updates may be done real time but shall be tracked by the Technical Writer using AFTO Form 158s to ensure appropriate disposition and incorporation. Technical Writer participation in Kit Proof and Fit Check shall be done whenever appropriate.

3.3.10.3 Entrance Criteria

SIL hardware and software at correct configuration.

Completion of Second Look IPR.

Second Look IPR AFTO Form 158s comments dispositioned.

A single master copy (paper based) will be maintained for red line comments.

3.3.10.4 Exit Criteria

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

100% percent of affected manuals validated.

Validation status/results reported to TORT Chairperson.

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

3.3.11 TECHNICAL ORDER FORMALIZATION

3.3.11.1 Planning Requirements

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

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.11.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 source data is good, the source data is processed. If the data is not useable, the TO Program Manager is contacted for clarification.

Once the data has been rolled into the Technical Manual 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 verification.

As identified in the TMCR, the TOMA posts the PDFs to SharePoint the specified number of days prior to verification.

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

As identified in the TMCR, the TOMA prints the required number of copies and ships the hardcopies to the location specified.

3.3.11.3 Entrance Criteria

Completion of Validation.

Validation AFTO Form 158s comments are provided.

3.3.11.4 Exit Criteria

100% of presented data is reviewed.

Incorporation of AFTO Form 158s from validation are verified.

3.3.12 VERIFICATION

3.3.12.1 Planning Requirements

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.12.2 Process Description

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

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

A single master copy containing all comments will be maintained and provided to the TO Program Manager and contractor lead at the end of the review.

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

o If no corrections are needed, annotate “No corrections required, ready for Pre-Pub review” in block X.

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

3.3.12.3 Entrance Criteria

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

Meeting agenda developed and distributed.

Second Look IPR AFTO Form 158s comments dispositioned.

100% of data in USAF publication format.

Job Guides, Work Cards and Checklists will be printed on letter sized paper.

Review material quantities IAW TMCR.

TOMA will supply current TO 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.

Applicable Subject Matter Expert(s) (Operations).

3.3.12.4 Exit Criteria

All AFTO Form 158s from Second Look IPR are incorporated and verified.

100% percent of presented data reviewed.

Draft Minutes resulting from Verification are reviewed and concurred.

Draft 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 draft AFTO Form 158s provided to the Verification Team Manager (VTM) and contractor lead.

Each TO will have AFTO form 27/82 completed and signed (VTM).

Aircraft configuration returned to approved baseline (Maintenance).

Review of scheduled Pre-Publication date for staffing conflicts.

3.3.13 DEDICATED OPERATIONAL TEST & EVALUATION (OT&E) SUPPORT

3.3.13.1 Planning Requirements

USAF personnel:

o OT&E Test Personnel.

o TO Program Manager.

o TOMA.

o TODO.

o ACC.

o ES/FMM.

Contractor support (as needed):

o Lead Logistics Engineer.

o Lead Technical Writer.

3.3.13.2 Process Description

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

Prime team shall provide 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.13.3 Entrance Criteria

All TOs from the modification/suite 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.13.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.14 VERIFICATION UPDATES

3.3.14.1 Planning Requirements

USAF personnel:

o TO Program Manager.

o TOMA.

Contractor support (as needed):

o Lead Logistics Engineer.

o Lead Technical Writer.

TO sustainment contractor.

3.3.14.2 Process Description

The TO Program Manager provides the TO sustainment contractor with AFTO Form 158s from Verification for each manual, even those not requiring any updates.

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

The TO sustainment contractor performs a review of the AFTO Form 158s for each manual. The TO sustainment contractor incorporates and dispositions all AFTO Form 158 comments:

o The TO sustainment contractor to work with TO Program Manager on issues regarding technical assistance.

o TO Program Manager to work with contractor on issues regarding technical assistance.

Once the data has been rolled into the Technical Manual 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.

As identified in the TMCR, the TOMA posts the PDFs to SharePoint the specified number of days prior to prepublication review.

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

3.3.14.3 Entrance Criteria

Completion of Verification.

Verification AFTO Form 158s comments supplied.

3.3.14.4 Exit Criteria

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

PDF copies of the TOs are posted to SharePoint in preparation for prepublication review.

3.3.15 PREPUBLICATION REVIEW

3.3.15.1 Planning Requirements

USAF support:

o TO Program Manager.

o TOMA representative.

o FMM/ES(s).

o Operations Subject Matter Expert(s).

Contractor support (as needed):

o ILS Lead.

o Lead Technical Writer.

TO sustainment contractor.

3.3.15.2 Process Description

TOMA representative, FMM/ES(s), and Operations Subject Matter Expert(s) reviews each PDF to confirm the following:

o Technical Manual contains all comments from Verification.

o Technical Manual meets AF specification.

o Technical Manual is at the correct revision level.

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

An AFTO Form 158 will be created for each manual, even if no changes are required.

3.3.15.3 Entrance Criteria

Verification AFTO Form 158s comments dispositioned.

Review Material quantities IAW TMCR.

3.3.15.4 Exit Criteria

All AFTO Form 158s from Verification are incorporated and verified.

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

Each TO will have an AFTO Form 158, even if no corrections are needed (ES/FMM).

3.3.16 PREPUBLICATION UPDATES

3.3.16.1 Planning Requirements

USAF support:

o TO Program Manager.

o TOMA representative.

Contractor support (as needed):

o Lead Logistics Engineer.

o Lead Technical Writer.

TO sustainment contractor.

3.3.16.2 Process Description

The TO Program Manager provides the TO sustainment contractor and prime contractor lead with AFTO Form 158s from Prepublication review for each manual, even those not requiring any updates.

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

The TO sustainment contractor performs a review of the AFTO Form 158s for each manual. The TO sustainment contractor incorporates and dispositions all AFTO Form 158 comments:

o The TO sustainment contractor to work with TO Program Manager on issues regarding technical assistance.

o TO Program Manager to work with prime contractor on issues regarding technical assistance.

Once the data has been rolled into the Technical Manual 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 TOMA in preparation for final delivery.

The TOMA reviews the final copy for format and content.

3.3.16.3 Entrance Criteria

Prepublication AFTO Form 158s comments dispositioned.

3.3.16.4 Exit Criteria

All AFTO Form 158s from prepublication review are incorporated and verified.

The TO Program Manager provides approval to the TO sustainment contractor that the Technical Manuals are ready for final delivery.

3.3.17 FINAL DELIVERY

3.3.17.1 Planning Requirements

USAF support:

o TORT Members.

Contractor support (as needed):

o TORT Members.

TO sustainment contractor.

3.3.17.2 Process Description

The TO sustainment contractor transforms the SGML source data and graphics to eTO output using Government Provided Software (GPS).

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

The TO sustainment contractor uses GPS to create a cabinet file (.cab) version of the eTO.

The TO sustainment contractor views one eTO of each doctype using the government provided Toughbook to ensure the eTO is compatible with the USAF common desktop.

The TO sustainment contractor compiles the data (SGML, PDF, graphics, and .cab files) 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.

3.3.17.3 Entrance Criteria

All AFTO Form 158s from prepublication review are incorporated and verified.

3.3.17.4 Exit Criteria

Formal delivery of technical manuals in accordance with TMCR.

Acceptance of CDRL.

3.3.18 LESSONS LEARNED

3.3.18.1 Planning Requirements

USAF personnel:

o TO Program Manager.

o TOMA representative.

o FMM/ES.

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.18.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.

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

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

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

TD Technical Data

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 Management Activity

TOMP Technical Order Management Plan

TOPP Technical Order Process Plan

TORT Technical Order Review Team

TOVP Technical Order Verification Plan

TRB Technical Review Board

USAF United States Air Force

VTM Verification Team Manager

WDD Work Description Document