TM 86-01P PDF
TM 86-01P PDF
TM 86-01P PDF
Technical Order Concept of Operations. Air Force TO Acquisition procedures, including procedures for
tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management, located
on the Internet at http://www.tinker.af.mil/technicalorders/index.asp.
2. TO Program Scope. The purpose of the Thick-Skin Urgent Spares Kitting (TUSK) program is to
produce replacements for Thick-Skin Wing Assemblies. The goal of the contract is to produce com-
plete wing assemblies consistent with the Enhanced Wing Assembly (EWA) and fuselage modifica-
tion kits to modify the existing fuselages to accept the new wings. The supplied TUSK wing tech-
nical data package (162D610010-1003) shall serve as the engineering baseline for this acquisition.
The geometry of the baseline TDP is defined by Three Dimensional (3-D) Models in Model Based
Definition (MBD). This includes 3-D models and other data mastered in a Product Lifecycle Man-
agement (PLM) system. The PLM data fields needed for manufacturing are also output in a human
readable form that the AF will provide as a “Part Report”. The 3-D Model TDP is an input to the
TUSK and shall be delivered by the Government. For bidding purposes 162D610010-1001 will be
provided with an Attachment A detailing the changes that will constitute the 162D610010-1003.
3. Commercial Manuals. This section is Not Applicable as this effort does not intend to provide any
Commercial Manuals.
4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting
between tailoring options offered in each TMSS. The tailoring is recorded in SIRs and added to Section
3 of this document for each TMSS required. NOTE: Tailoring must not change or delete mandatory
requirements which are part of the Document Type Definition (DTD) structure or XML schema struc-
ture located in Section 2 Table 1.
4.1. AF options in some Joint-Service TMSS have been documented in preliminary SIRs included in
Section 3. These preliminary SIRs provide the starting point for further tailoring. Contractors may
recommend additional tailoring of the Joint-Service TMSS SIRs and provide recommended SIRs for
other TMSS as applicable. NOTE: TMSS requirements marked “(F)” are specifically for Air Force
use; “(A)” is for Army, “(M)” is Marine Corps and “(N)” is Navy. Comply with all unmarked and
“(F)” TMSS requirements as modified by the tailoring options in each TMSS.
Delivered by Document Center Inc., www.document-center.com, under contract.
Single user license only. Copying or Networking prohibited.
2 TM-86-01P 9 Dec 14
4.2. Questions concerning TMSS requirements may be resolved by written request and justified
suggestions for resolution submitted through the Procuring Contracting Officer (PCO) and Mr. Len
Mian, AFLCMC/WWALE, 6067 Box Elder Lane Bldg 1284, Hill AFB, UT 84056 (801) 586-7150.
Deficiencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA).
Approved recommendations, corrections and clarifications will be maintained with contract docu-
mentation.
5. Subsequent TO/Data Requirements. When new TO requirements are identified the Contractor shall
notify the government utilizing DI-TMSS-80067B, Technical Manual (TM) Contractor Furnished Aero-
nautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, or approved contractor
formats. This process shall require government review and approval of recommended additional re-
quirements prior to developing additional data.
6. TO Development. The baseline for the A-10 TUSK effort is the latest available Block Cycle Release
(BCR). The TO development process shall follow the guidelines outlined in the Tech Order Process
Plan (TOPP) document. The Contractor shall propose TO development practices and procedures that
ensure TOs and data are compatible with the Air Force Technical Order Concept of Operations
(CONOPS) (http://www.ide.wpafb.af.mil/toprac/polinfo.htm) and the Air Force Standard TO Manage-
ment System. In addition, TOs shall be written to a scope and depth of coverage sufficient to support
the operations and maintenance concepts, and to the Reading Grade Level (RGL) specified in MIL-
STD-38784A, Standard Practice for Manuals, Technical: General Style and Format Requirements.
6.1. Page-oriented Military Specification (MILSPEC) TOs shall be formatted with text, graphics and
delivery according to the TMSS specified in Section 2, to the maximum extent practical. The con-
tractor shall develop TO source data using Adobe Acrobat or Word.
6.2. Graphic updates shall be delivered as vectorized cgm or tif files. NOTE: Illustration files de-
veloped and delivered for other purposes shall be used in lieu of developing special TM illustration
files whenever possible. For assistance with illustration requirements contact AFLCMC/HIAM via
(e-mail:[email protected]).
6.3. The Contractor may propose use of Non-Government Standards (NGS) for development of TOs,
but must justify this choice based on life-cycle cost savings to the government and compatibility
with existing systems. If proposing the use of NGS, contact the Procuring Contracting Officer
(PCO) and TO Manager to request guidance from the Air Force Preparing Activity (PA), 754
ELSG/ILMT, Technical Order Section, 4375 Chidlaw Rd Suite 6, WPAFB OH 45433-5006.
7. TO Numbering. This section is Not Applicable as this effort does not intend to provide any new
TOs.
8. Data Rights. Contractors shall provide Unlimited Rights for all source data and TOs prepared specif-
ically for the contract. Government rights in data are specified in the Defense Federal Acquisition Regu-
lation Supplement (DFARS), 252.227-7013, Rights in Technical Data, Noncommercial Items, 252.227-
7014. Government data rights shall extend to the common source database, transformation style sheets,
and other tools or products used to author or display technical data.
9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Contractors shall
determine the correct markings and controls for classified and restricted distribution data and TOs IAW
the program’s Security Classification Guide (SCG) and DODM 5200.01, DODI 5230.24, AFI 31-401,
AFI 61-204, and MIL-STD-38784 (available at http://www.e-publishing.af.mil/
or https://assist.dla.mil/online/start/index.cfm ). The markings and notices shall be reviewed during In-
Process Reviews (IPR). NOTE: Distribution limitations will be determined on a case-by-case basis as
TOs are developed, dependent upon TO content.
10. TO Quality. Contractors’ proposals shall describe how the government will be allowed to interact
with the contractor’s TO development team. The contractors’ shall ensure TOs prepared are: a) techni-
cally accurate and safe; b) written to a scope and depth of coverage sufficient to support the operations
and maintenance concepts, and c) properly classified and marked with export control and distribution
limitation statements. The contractor shall maintain a Technical Manual Quality Assurance plan for this
effort and shall be sufficiently detailed to support TO certification to include actual performance of pro-
cedures or desk-top analysis for non-procedural data which shall be available for review at the TO Guid-
ance Conference. Simulation (walk-through/talk-through) should be reserved for those procedures
which would activate explosive devices or present a hazard to personnel or equipment. NOTE: Quality
requirements for the Joint Nuclear Weapons Publications System (JNWPS) and for Non-nuclear Explo-
sive Ordnance Disposal (EOD) Data are contained in TO 11N-1-1 and DODD 5160.62, respectively.
The government will conduct performance-tests all JNWPS and EOD TOs.
10.1. Guidance Conference. Working through the TOMA, the contractor shall co-host and partici-
pate in a guidance conference for this effort to be held within 60 calendar days after award of con-
tract. The Technical Order Status and Schedule (TOSS) will be formalized at this conference. The
contractor shall present a briefing on their interpretation of the basic contract, SOW, CDRLs, Data
Item Descriptions (DIDs), MIL-SPEC, MIL-STD, SIRs, this document and the planned preparation
and delivery of the TOs and related data.
10.2. In-Process Reviews. The contractor shall participate and co-chair In-Process Reviews of the
data developed for this effort. In-Process Reviews may be requested by the TOMA or by the con-
tractor to ensure that data being developed as part of this effort is adequate and accurate and IAW
contract requirements and cited specifications. The contractor shall ensure all comments from pre-
vious IPR’s have been incorporated prior to next scheduled IPR. With the prior approval of the
TOMA the IPRs may be combined.
10.3. TO Delivery Requirements for In-Process Reviews There will be two In-Process Reviews
(IPRs) and a Pre-Publication Review (PPR) to ensure TOs are being developed according to contract
requirements and that open discrepancies are cleared prior to publication. Contractor source data
will be used at the IPRs. The contractor shall ensure all comments from previous IPR’s have been
incorporated prior to next scheduled IPR. With the prior approval of the TOMA the IPRs may be
combined. USAF Preliminary Technical Orders (PTOs) will be used for Verification and Pre-
Publication Review.
10.4. TO Certification. The contractor shall certify that new TO procedures and data developed to
support the program are accurate, adequate, current, and usable for their intended purpose. The Gov-
ernment may witness the certification activities. All procedures shall be validated prior to TO verifi-
cation. The contractor shall notify the government at least 30 days prior of the need for any Gov-
ernment Furnished Information/Government Furnished Equipment (GFI/GFE) required to perform
certification tasks.
The contractor shall incorporate comments generated by the certification process into the TOs prior
to submitting the TOs for verification. At the completion of the certification, the contractor shall
submit a letter to the TOMA stating that certification has been completed and that any deficiencies
identified during the process have been corrected. The contractor will ensure all necessary changes
and corrections to affected manuals are accomplished in time to meet contract delivery schedule re-
quirements. The contractor shall notify the government at least 180 days prior to the need date of any
Government Furnished Information/Government Furnished Equipment (GFI/GFE) required to per-
form certification tasks. Technical order 00-5-1 and 00-5-3 shall be referenced for additional infor-
mation on TO Certification requirements.
10.5. Verification Support Verification Support shall consist of the Lead Technical Writer, engi-
neering support (as required), Equipment Specialist (ES), Flight Manual Manager (FMM) (as re-
quired), TOMA (as required), and MAJCOM/field support personnel. A functional A-10 model air-
craft with the necessary hardware and software, as well as any necessary on aircraft support (load
crew, maintainers, pilots, etc.), will also be required at the verification. This support should be in
accordance with the A-10 Thunderbolt II, TO Verification Plan (TOVP). Contractor source data will
be incorporated into the baseline TOs by the USAF prior to verification of the manuals.
10.6. TO Prepublication Reviews (PPR). PPRs are examinations of TOs to ensure incorporation of
agreed upon changes from IPRs and verification, and to ensure the manual meets style and format
requirements. The Contractor shall prepare and deliver copies of TOs and TO updates in MIL-SPEC
compliance for the PPR as shown in the delivery matrix. The TOs for PPR shall have been approved
by contractor QA, be in compliance with the MIL-SPECs/standards, and incorporate all verification
comments and corrections approved by the TOMA or program management office representative.
The TOMA may waive the PPR depending on number and complexity of changes from verification.
11. TO Delivery The Contractor shall propose practices and procedures for secure access to or delivery
of digital TO files, source data (PDF, Word, CGM, etc.), reproduction masters, and program support
data. TO file delivery formats shall be according to applicable CDRLs and the tailored TM Delivery Re-
quirements Matrices included in Section 2 of this document. Paper TO delivery is not acceptable for
final delivery of TOs.
12. Source Data Maintenance. Contractors shall maintain accuracy, currency and configuration of TO
source data, to include GFI, throughout the contract period of performance. The Contractor is responsi-
ble for updating the TOs to include technically accurate and error free data that explains the new capa-
bilities developed as part of the A-10 TUSK effort including correction of prior technical data that is
found to be in error/inaccurate and affected by this modification. Maintenance includes preparation of
source data updates to incorporate corrections, equipment configuration changes, and maintenance and
operational concept changes. The Contractor shall update the source data to the latest available TO
baseline as of 30 calendar days prior to final delivery of source data.
13. TO Maintenance. Contractors shall maintain TO’s by preparing emergency, urgent, routine chang-
es/revisions or supplements and source data updates to incorporate corrections, equipment configuration
changes, and maintenance and operational concept changes IAW TO 00-5-3.
14. Schedules. Schedule slips shall be communicated to the USAF immediately to resolve any potential
schedule conflicts. NOTE: AF policy requires delivery of verified TOs prior to or concurrently with
delivery of operational equipment to the field (AFI 63-101). This policy will determine TO develop-
ment and delivery schedules throughout the acquisition phase of a program.
The contractor shall develop and maintain an Integrated Master Schedule (IMS), and update the IMS
throughout the period of performance for all TO development activities associated with this order for the
life of the contract. The schedule shall be to the system/book or TCTO level and cover all development
major milestones. Any changes after the guidance conference shall be coordinated with and approved by
program TOMA.
15. Time Compliance Technical Orders (TCTOs). The contractor shall prepare TCTO’s, ITCTO’s and
resulting TO updates as required in support of TUSK TCTO’s will be used to document all permanent
modifications, initiate special “one time” inspections, or impose temporary restrictions on systems or
equipment within specified time limits effecting TUSK. The Contractor shall propose practices and pro-
cedures to develop AF TCTOs and related TO updates when tasked as part of the approval process for
Engineering Change Proposals (ECPs) to configured items. The Contractor shall perform a peer and
engineering technical review prior to submittal to the USAF. Costs for TCTO package development
must be included in ECP Costs – not included as direct proposal costs. NOTE: ECPs are reviewed and
Delivered by Document Center Inc., www.document-center.com, under contract.
Single user license only. Copying or Networking prohibited.
TM-86-01P 9 Dec 2014 5
approved by the Government’s Configuration Control Board (CCB). When the CCB decides that a
TCTO is the appropriate method of implementation, the contractor may be requested to develop the
TCTO package for Air Force coordination and approval.
15.1 The contractor shall deliver certified drafts of routine TCTO’s to meet program office
plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The contractor shall deliver final
drafts with “final” customer comments incorporated, within 10 business days of receipt of com-
ments.
TABLE 1
TMSS REQUIREMENTS FOR THE A-10 Aircraft TUSK Program
TABLE 1
TMSS REQUIREMENTS FOR THE A-10 Aircraft TUSK Program
TABLE 1
TMSS REQUIREMENTS FOR THE A-10 Aircraft TUSK Program
TABLE 2
Com- Supple-
TO Number, Title, or mercial Change/ Supple- mental Source
Type of Manual Specification Manual Revision ment TM Data
MIL-DTL-
14. 1A-10C-4-28
38807
MIL-DTL-
15. 1A-10C-4-51
38807
MIL-DTL-
16. 1A-10C-4-24
38807
17. 1A-10C-36 MIL-DTL-9854
18. 1A-10C-39 MIL-DTL-9854
19. 1A-10C-3-1 MIL-DTL-9854
MIL-DTL-
20. 1A-10C-2-1-1
83495
MIL-DTL-
21. 1A-10C-3-1-1
83495
MIL-DTL-
22. 1A-10C-2-51JG-3
83495
MIL-DTL-
23. 1A-10C-2-51JG-5-1
83495
TABLE 2
NOTES:
• Check all applicable boxes.
NOTES:
• For Paper media delivery indicate required quantity
• For all other media types indicate (Y)es or (N)o
• TCTO requirements are specified in the contract vehicle approving the TCTO.
DELIVERY SCHEDULE
Event Number of days data In Process Verification Prepublication Final TO
required prior to event Review(s) Review Distribution
(10 Working (5 Days) (10 Days)
Days)
Enter physical mailing address, electronic
delivery location or web access point
AFLCMC/WWAEH Paper/ Paper/ Paper/ Paper/
Attn: Tammy Heslop
SGML/ SGML/ SGML/ SGML/
6067 Box Elder Lane, Bldg 1284
Hill AFB, UT 84056-5811 IPDF / 1 IPDF / 1 IPDF / 1 I/1
XML / XML / XML / XML /
Other/ Other/ Other/ C/1
W/ 1
AFLCMC/WWALE Paper/ Paper/ Paper/ Paper/
Attn: Len Mian
SGML/ SGML/ SGML/ SGML/
6067 Box Elder Lane, Bldg 1284
Hill AFB, UT 84056-5811 IPDF / 1 IPDF / 1 IPDF / 1 I/1
XML / XML / XML / XML /
Other/ Other/ Other/ C/1
W/ 1
Delivered by Document Center Inc., www.document-center.com, under contract.
Single user license only. Copying or Networking prohibited.
12 TM-86-01P 9 Dec 14
NOTES:
• All TMSS applicable to this contract shall have an appropriately tailored SIR attached to this section.
• SIRs included in the untailored TMCR format represent the minimum tailoring requirements that must be included in
the final contract, unless the entire SIR is not applicable; e.g., if MIL-DTL-22202D is not required, the entire SIR can
be deleted.
• MIL-STD-38784 must be included in all contracts/proposals for AF TMSS-developed TOs.
• Most specification “Acquisition Requirements” list the same two items for paragraphs 6.2a. For this contract enter:
6.2a. The title, number and date of each specification will be listed in the heading of the applicable SIR.
• Digital requirements shall not be tailored out. Tailoring shall be limited to the options expressed in paragraphs 6.2.
Any requests for tailoring outside of these requirements must be coordinated with the specification Preparing Activity
(PA-16) AFLCMC/HIAM.
• Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from
Acquisition Streamlining and Standardization Information System (ASSIST) web
page, https://assist.dla.mil/online/start/index.cfm.
• TMSS entries designated with A, F, M or N refer to Army, Air Force, Marine Corps or Navy requirements.
• Comments (recommendations, additions, deletions) and any pertinent data which may be in use in improving Air Force
TMSS documents should be submitted to AFLCMC/HIAM, 4170 Hebble Creek Road, Bldg. 280, Door 15, Area A,
Wright-Patterson AFB, Oh 45433-5653 or by email to; [email protected]. Do not include the street address, a
building number or a zip+4.