TMCR.pdf

TM-86-01R 10 AUG 2022 1-01: AF TMSS LinearTMs

Air Force Technical Manual Contract Requirements (TMCR) for

Progam

AC-130J PRECISION STRIKE PACKAGE (PSP) TECHNICAL DOCUMENT PROJECT (TDP)

FOLLOW ON

(Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT: , CLIN

Date:

Date: xx March 2023

TMCR Number: 512

AFLCMC/WIU TOMA DATE

AFLCMC/WIU TOMA DATE

AFLCMC/WIU FMM DATE

AFLCMC/WIU FMM DATE

AFLCMC/WIU PROGRAM MANAGER DATE

AFLCMC/WIU TECH DATA SECTION CHIEF DATE

Technical Manual/Technical Order requirements contained herein have been cleared for use by OMB

Paperwork Reduction Project No. 0704-0188.

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS – TMSS LINEAR TMS

1. TMCR Tailoring. Air Force (AF) TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management, located at https://www.tinker.af.mil/Resources/Technical-Orders/. Any terms or procedures found in this document may be researched at this website. The Contractor may propose and submit, in writing, additional tailoring to the Technical Order Manager Agency/Agent (TOMA), Government Program

Manager (PM) and Procuring Contracting Officer (PCO) as required by Section L or the RFP.

Modifications to contracts can continue to utilize the existing format until renegotiated/replaced. The acceptance of any contractor tailored TMCR will be at the discretion of the government and is not in effect until accepted in writing by the PCO or specified in the contract.

2. TO Program Scope. The Contractor must develop and deliver technical manuals in accordance with

(IAW) this TMCR that support the AC-130J Precision Strike Package (PSP) Technical Document Project

(TDP) Follow On requirements for technically usable manuals concurrent with the program’s TO

CONOPS. The Contractor may propose and submit, in writing to the PCO, additional Section 2 tailoring to propose new TO types (Table 1) and source data and TO updates (Table 2) required to support the

AC-130J Precision Strike Package (PSP) Technical Document Project (TDP) Follow On program’s objectives and as defined by the TMSS. The acceptance of any additionally tailored TMCR will be at the discretion of the government and is not in effect until accepted in writing by the PCO.

3. Commercial Manuals. Contractors must recommend the use of existing commercial manuals to the maximum extent possible without impairing program support objectives. All proposed commercial manuals are subject to Government review and approval. Contractors must use Data Item Description

(DID) DI-TMSS-80067C, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or

Contractor Furnished Equipment (CFAE/CFE) Notices, to provide recommendation data. A copy is available through ASSIST at http://quicksearch.dla.mil/qsSearch.aspx.

3.1. The Contractor must provide the ability to electronically store, print, distribute, update and decollate the commercial manual to allow for printing. Commercial manuals must be delivered as

Portable Document Format (PDF) unless otherwise specified.

3.2. Approved Commercial-Off-The-Shelf (COTS) Manuals must be delivered with an Identifying

TO Publication Sheet (ITPS), IAW MIL-PRF-32216, Performance Specification: Evaluation Of

Commercial Off-The-Shelf (COTS) Manuals And Preparation Of Supplemental Data. All PDF files of commercial data must be non-password protected to allow the AF to decollate the manual for printing.

3.3. If the proposed COTS data is found to be insufficient after review by the Government, the

Contractor must prepare supplemental data for the COTS manual as required IAW Military Standard

(MIL-STD)-38784. If the COTS data cannot be supplemented sufficiently the Contractor will develop new TM data IAW the applicable TMSS listed in Section 2, Table 1.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. AF TMSS tailoring options and some Joint Service TMSS have been documented in preliminary Specification/Standard Interface Records

(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. Tailoring must not change or delete mandatory requirements which are part of the Document Type Definition (DTD) located in Section 2, Table 1.

https://www.tinker.af.mil/Resources/Technical-Orders/ http://quicksearch.dla.mil/qsSearch.aspx

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.

4.1. Questions concerning TMSS requirements may be submitted in writing with suggestions for resolution and supporting information to the PCO and William Rector, AFLCMC/WIU, 370 Richard

Ray Blvd Bldg 300E, Robins AFB, GA 31098, 478-222-9700 (DSN 472-9700) and Timothy Bullock, AFLCMC/WIU, 370 Richard Ray Blvd Bldg 300E, Robins AFB, GA 31098, 478-327-4102 (DSN

497-4102). Deficiencies and suggested improvements may be submitted to the TMSS Preparing

Activity (PA). Recommendations, corrections and clarifications approved by the PCO, if any, will be maintained with contract documentation.

5. Subsequent TO/Data Requirements. When new TO requirements are identified the Contractor must notify the Government utilizing DI-TMSS-80067C, Technical Manual (TM) Contractor Furnished

Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, or approved

Contractor formats. This process requires Government review and approval of recommended additional requirements prior to developing additional data.

6. TO Development. TOs must be written to a scope and depth of coverage to support the AC-130J

Precision Strike Package (PSP) Technical Document Project (TDP) Follow On operations and maintenance concepts.

6.1. Standard Generalized Markup Language (SGML) tagged TO files must include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes must be used in lieu of developing special TM illustration files whenever possible. All delivered graphics must conform to the approved graphic creation and format guidelines listed in Attachment 1, Graphics Format Guidelines. For assistance with illustration requirements contact AF TMSS via (e-mail: SGMLSupport@us.af.mil).

6.2. Page-oriented Military Specification (MIL-SPEC) TOs must be formatted with text, graphics and delivered according to the TMSS specified in Section 2. The Contractor must develop TO files (tagged instances) using SGML according to the DTDs referenced in the appendix to MIL-STD-38784 and each applicable military detail specification (MIL-DTL). Multiple SGML file instances for a single

TO document are not authorized.

7. TO Numbering. Contractors must notify the Government, in writing, of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by the Contractor’s own personnel. Requests for new TO numbers must be submitted to the TOMA utilizing the TO numbering worksheet.

8. Data Rights. Contractors must comply with 10 U.S.C. 2320 and Defense Federal Acquisition

Regulation Supplement (DFARS) provisions and clauses. The Government’s rights in technical data are specified in DFARS 252.227-7013, Rights in Technical Data-Noncommercial Items, 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, and 252.227-7015, Technical Data-Commercial Items and other applicable provisions and clauses from

DFARS 227, 252.227 and DFARS 252.227-7018 Rights in Noncommercial Technical Data and Computer

Software – Small Business Innovation Research (SBIR). In accordance with those clauses and provisions, the Contractor grants the Government Unlimited Rights, as defined therein, in all source data, TO publications, TO updates and TO-related documents prepared specifically for the contract. The Contractor also grants the Government Unlimited Rights in all Government-funded business rules (tailoring, and application methods and procedures) and documented business processes developed under the contract for the purpose of TO development. The contractor is required to deliver TO data with the data rights mailto:SGMLSupport@us.af.mil license required by the applicable DFARS clauses. Contractor must identify any data to be delivered to the Government with other than Unlimited Rights IAW DFARS 252.227-7017, Identification and

Assertion of Use, Release, or Disclosure Restrictions and must mark such data only in accordance with the applicable DFARS clause. The Contractor must pass through and enforce all requirements in this

TMCR to all sub-Contractors.

9. Classification, Distribution, Destruction, Disclosure, Export Control Notices, and Cyber Security.

Contractors must recommend the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide (SCG) and Department of Defense

Manual (DODM) 5200.01V2_AFMAN 16-1404V2, Department of Defense Instruction (DODI) 5230.24, Department of Defense Directive (DODD) 5230.25, DoDI 5200.48, Controlled Unclassified Information, DAFI 61-201, Management of Scientific and Technical Information (STINFO) and MIL-STD-38784

(available at http://www.e-publishing.af.mil/ https://www.esd.whs.mil/DD/admin_inst/,or https://assist.dla.mil/online/start/index.cfm). The markings and notices must be reviewed during In-

Process Reviews (IPR). The Contractor must also apply policy and procedures for Cybersecurity Program

Management IAW AFI 17-130, AFMAN 17-1301, Computer Security (COMPUSEC) NOTE:

Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon

TO content.

10. TO Quality The Contractors must ensure prepared TOs are: a) technically accurate and safe; b) written to a scope and depth of coverage to support the operations and maintenance concepts; c) properly classified and marked with export control and distribution limitation statements. The Contractor must maintain a

Technical Manual Quality Assurance (TMQA) Program Plan for this effort. The TMQA Program Plan must be available for review at the TO Guidance Conference. The TMQA Program Plan must be sufficiently detailed to support TO certification to include actual performance of procedures or desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be reserved for those procedures which would activate explosive devices or present a hazard to personnel or equipment.

10.1. Initial Technical Order Guidance Conference (TOGC). Working through the TOMA, the

Contractor must co-host and participate in a guidance conference for this effort. The TOGC will be held within 60 calendar days after contract award. The Technical Manual Schedule and Status will be formalized at this conference. The Contractor must present a briefing on their interpretation of the basic contract, SOW/Performance Work Statement (PWS), CDRLs, DIDs, MIL-SPEC, MIL-DTL, MIL-STD, SIRs, this document and the planned preparation and delivery of the TOs and related data.

10.2. In-Process Reviews. The Contractor must participate and co-chair In-Process Reviews (IPR) of the data developed for this effort. In-Process Reviews are to ensure that data being developed as part of this effort is adequate and accurate and IAW contract requirements and cited specifications. The

Contractor must ensure that all appropriate personnel required to execute a successful TO program will either attend or participate in the IPR. IPRs will be held IAW TO 00-5-3 or as defined by the program office. During the IPRs the Contractor will be responsible to maintain a master markup of the document being reviewed. The Contractor must develop meeting minutes after each review documenting all approved changes and concurrent agreements for Government review and approval.

This master markup will be made available at the next scheduled review. A copy of the markup will be provided to the TOMA or designated individual at the conclusion of the review. The Contractor must ensure all comments from previous IPRs have been incorporated prior to the next scheduled IPR.

With prior approval of the TOMA, IPRs may be combined.

10.3. TO Delivery Requirements for In-Process Reviews. IPR TO data must be technically edited and reviewed according to the TMQA Program Plan. Manuscript (handwritten) data is not acceptable http://www.e-publishing.af.mil/ https://www.esd.whs.mil/DD/admin_inst/ https://assist.dla.mil/online/start/index.cfm for any data to be reviewed. The TMQA Program Plan checklists must be available for review by the

Government during the IPRs. Delivery requirements are contained in Section 2, Table 3 of the TMCR.

10.4. TO Certification. The Contractor must certify that new TO procedures and data developed to support the program are accurate, adequate, current, safe, and usable for their intended purpose. The

Government may witness the certification activities. The Contractor must 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 must submit a letter to the TOMA through the

Government PCO and PM stating that certification has been completed, the certification method used, 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 requirements. The Contractor must notify the Government, as identified in the contract, at least 180 days prior to the need date, of any Government Furnished Property (GFP), Government Furnished Information, and/or Government Furnished Equipment (GFI/GFE) as required, to perform certification tasks. TO 00-5-1 and TO 00-5-3 must be referenced for additional information on TO Certification requirements.

10.4.1. The Contractor must propose opportunities to perform TO certification activities in conjunction with Government verification IAW TO 00-5-3, where applicable.

10.5. Verification Support. The Contractor must support Government verification activities as required by the TOMA and the program Technical Order Life Cycle Verification Plan (TOLCVP).

Contractor verification support will consist of on station technical writing and engineering support.

The Contractor must maintain a master mark-up of the document and record minute items during the

Government verification process. The Contractor must also support all post verification reviews and ensure availability until 100% task verification is attained by the Government.

10.6. TO Prepublication Reviews (PPR). PPRs are examinations of TOs that ensure incorporation of agreed upon changes from previous reviews and verification activities. The Contractor must 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 must be approved by the Contractor’s QA, be in compliance with the MIL-SPECs/DTLs/STDs, and incorporate all verification comments and corrections approved by the TOMA or program management office representative.

10.7. Technical Data Assessment (TDA). The Contractor must submit in-work samples of each specified TM type deliverable to the Government for specification and standardization compliance review. TDAs may be accomplished by using organic TO sustainment environments with the assistance of AFLCMC/HIAM (AF TMSS Office, SGMLSUPPORT@us.af.mil).

10.7.1. MIL-SPEC (SGML) TO Data. The Contractor must submit an SGML tagged TO file, associated graphics files, a PDF rendition of the SGML tagged TO file composed by the Contractor and any associated companion files necessary for PDF composition. During assessment, the SGML tagged TO file will be parsed against the appropriate TMSS DTD (and optionally run through the

Tagging Utilization Tool (TUT)) to determine DTD compliance and correct tag usage. The SGML tagged TO file and associated graphics will be composed by the program office and the rendered

PDF will be compared with the submitted PDF to check for completeness, indexing, and MIL-

SPEC/DTL/STD compliant formatting.

10.7.2. Error Resolution. The Contractor must correct any errors found during the TDA prior to each IPR. Additional TDAs may be necessary based on the amount of errors found during the initial

TDA. Completion of a TDA in no way relieves the Contractor from the requirement to fix errors found during future reviews.

11. TO Delivery. TO file delivery requirements are located in Section 2, Table 3 of this document.

11.1. MIL-SPEC (SGML) Tagged Files. The Contractor must parse all SGML files required for the

TOs prior to Government delivery and must verify the SGML is compliant with the appropriate DTD.

NOTE: The Government will parse the files prior to acceptance using the SGML parser agreed upon prior to submission. Additional resources can be obtained via AFMC AFLCMC/LZP by submitting a request to AFLCMC.PDSS.TOAPVIPR@us.af.mil.

12. Source Data Maintenance. Contractors must maintain accuracy, currency and configuration of TO source data, to include GFI, throughout the contract period of performance. The Contractor must provide the Government a Configuration Control Management Plan. The Contractor will provide a minimum of annual updates throughout the life of the contract as directed in writing from the PCO. Maintenance includes preparation of source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes. Additionally, the Contractor must ensure the accuracy, currency, and configuration of applicable data provided by their sub-Contractors as it effects the technical baseline.

NOTE: Contractors will protect GFI provided for the purposes of TO development IAW DFARS

252.204-7000 Disclosure of Information and DFARS 252.227-7025, Limitations on the Use or Disclosure of Government Furnished Information Marked with Restrictive Legends.

12.1. In order to maintain accuracy, currency and configuration of Air Force TOs, Vendors must have a TODO account. If an account has not been established, the Vendor must establish a TODO account upon contract award by processing an AFTO Form 43, USAF Technical Order Distribution Office

(TODO) Assignment or Change Request in accordance with TO 00-5-1. The AFTO Form 43 can be downloaded at http://static.e-publishing.af.mil/production/1/afto/form/afto43/afto43.pdf. All versions of the form include detailed completion instructions.

13. TO Maintenance. Contractors must maintain TOs by preparing emergency, urgent, routine changes/revisions or supplements and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes IAW TO 00-5-3. The

Contractor must assist the Government, where applicable, by incorporating and delivering approved changes to the technical data in the field NLT the specified time limits within TO 00-5-3 for Urgent, Work

Stoppage, or Emergency changes originating from an approved Recommended Change (RC) process and/or Publication Change Request (PCR) in the Enhanced Technical Information Management System

(ETIMS). In the event of non-ETIMS access AFTO FORM 22, 252 policy or other approved change request forms processes will be adhered to. The specified time limits upon receipt of specified change requests is 40 calendar days for urgent changes/revisions, 72 hours for work stoppage changes/revisions, and 48 hours for emergency changes/revisions.

14. Schedules. The Contractor must develop and maintain an Integrated Technical Manual Schedule and

Status throughout the period of performance for all TO development activities associated with this order for the life of the contract. The schedule must be to the system/book or TCTO level and cover all major milestones of development. Any changes to the TM Schedule and Status after the TO Guidance

Conference must be coordinated with and approved by program TOMA and PCO.

15. Time Compliance Technical Orders (TCTOs). The Contractor must prepare TCTOs, ITCTOs and resulting TO updates as required in support of AC-130J Precision Strike Package (PSP) Technical

Document Project (TDP) Follow On IAW TO 00-5-15 and MIL-DTL-38804 content requirements.

TCTOs 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 AC-130J

Precision Strike Package (PSP) Technical Document Project (TDP) Follow On. Costs for TCTO package development must be IAW with AFI 65-601Vol.1.

mailto:AFLCMC.PDSS.TOAPVIPR@us.af.mil

15.1. The Contractor must deliver certified drafts of Immediate Action TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor must deliver drafts with comments incorporated within 24 hours of receipt of comments.

15.2. The Contractor must deliver initial certified drafts of Urgent Action TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor must deliver final drafts with “final” customer comments incorporated, within 96 hours of receipt of comments.

15.3. The Contractor must deliver initial certified drafts of routine safety TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor must deliver final drafts with “final” customer comments incorporated, within 5 business days of receipt of comments.

15.4. The Contractor must deliver certified drafts of routine TCTOs to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The Contractor must deliver final drafts with

“final” customer comments incorporated, within 10 business days of receipt of comments.

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

• Mark the TM Type Selection Tables indicating the applicable TO types and related specifications.

(NEW DEVELOPMENT) TM TYPE (PUBLICATION) SELECTION TABLES.

Table 1

TMSS Requirements for the

AC-130J PRECISION STRIKE PACKAGE (PSP) TECHNICAL DOCUMENT PROJECT

(TDP) FOLLOW ON

Program

(System/Component)

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-DTL-5096

a. Inspection and Maintenance Requirements (-6) Manual ☐

b. Acceptance and Functional Check Flight (FCF)

Procedures (-6CF) Manual

c. Acceptance and Functional Check Flight (-6CL)

Checklist

d. Inspection Workcards (-6WC) ☐

e. Maintenance/Operations Checklists ☐

2. Cargo Aircraft Loading and Offloading TOs MIL-DTL-5288

a. Loading Instructions Manual ☐

b. Nuclear Weapon Cargo Loading Manual ☐

c. Checklists ☐

3. Flight Operation Manuals MIL-DTL-7700

Flight Manuals

a. Flight Manual ☐

b. Performance Data Manual ☐

c. Mission Crew Manual and Associated Checklists ☐

d. Fanfold Checklists ☐

e. Supplemental Manual ☐

f. Abbreviated Flight Crew Checklist ☐

g. Non-nuclear Weapon Delivery Manual ☐

h. Aircrew Nuclear Bomb Delivery Manual (Strategic

Bomber Aircraft)

i. Aircrew Nuclear Missile Delivery Manual (Strategic

Bomber Aircraft)

j. Aircrew Nuclear Bomb Delivery Manual (Tactical

Aircraft)

k. Non-nuclear Weapon Delivery Checklist ☐

l. Nuclear Weapon Delivery Checklist (Strategic Bomber

Aircraft)

m. Aircrew Nuclear Bomb Delivery Checklist (Tactical

Aircraft)

n. Non-nuclear Weapon Delivery Source Data Packages ☐

TMSS Requirements for the

AC-130J PRECISION STRIKE PACKAGE (PSP) TECHNICAL DOCUMENT PROJECT

(TDP) FOLLOW ON

Program

(System/Component)

Title or Type of Manuals Specification Required

Weight and Balance (Aircraft)

a. Loading Data Manual ☐

b. Sample Basic Weight Checklists ☐

4. List of Applicable Publications MIL-DTL-8031 ☐

5. Structural Repair Manuals (for Aircraft) MIL-DTL-9854 ☐

6. Munitions/Weapons Loading Procedures, Non-nuclear and Nuclear TOs MIL-DTL-9977

a. Nuclear Weapons Basic Information and Loading

Procedures

b. Nuclear Weapons Loading Procedures ☐

c. Non-nuclear Munitions Basic Information ☐

d. Non-nuclear Loading Procedures ☐

e. Non-nuclear Munitions Loading Standard Data Packages

(SDPs)

f. Loading Procedures Checklist ☐

g. Single Loading Procedures Checklist ☐

h. Integrated Loading Procedures Checklists ☐

i. Family Group Loading Procedures Checklist ☐

j. Nuclear Weapons Loading Procedure Checklists ☐

k. Functional Check Procedures Checklist ☐

l. NATO Stage B Cross-Servicing Checklists ☐

m. End of Runway (EOR) Procedures Checklist ☐

7. Space Operation and Support Documentation (Intercontinental Ballistic

Missiles)

MIL-PRF-38311 ☐

8. Work Unit Code Manual MIL-DTL-38796

a. Standard WUC Manual ☐

b. Two Chapter Manual ☐

c. Three Chapter Manual ☐

9. Calibration Procedures MIL-DTL-38793 ☐

10. Time Compliance Technical Orders (TCTOs) MIL-DTL-38804

a. TCTO ☐

b. TCTO Supplement ☐

11. Aircraft Battle Damage Assessment and Repair TOs MIL-DTL-87158 ☐

12. Illustrated Parts Breakdown MIL-DTL-38807 ☐

13. On-Equipment Organizational Maintenance Manual Set MIL-DTL-83495

a. General Equipment (GE) Manual ☐

b. General System (GS) Manuals ☐

c. Combined GE & GS Manual ☐

TMSS Requirements for the

AC-130J PRECISION STRIKE PACKAGE (PSP) TECHNICAL DOCUMENT PROJECT

(TDP) FOLLOW ON

Program

(System/Component)

Title or Type of Manuals Specification Required

d. Job Guide (JG) Manuals ☐

e. Fault Reporting (FR) Manual ☐

f. Fault Isolation (FI) Manual ☐

g. Wiring Data (WD) Manual ☐

h. Schematic Diagram (SD) Manual ☐

14. Operation and Maintenance Instructions in Work Package Format MIL-DTL-87929

a. Maintenance Manuals ☐

(1) Organizational Maintenance ☐

(2) Intermediate Maintenance ☐

(3) Depot Maintenance ☐

(4) Combined (I&D) Maintenance ☐

(5) On Condition Maintenance ☐

b. Operation & Maintenance Instruction Manuals ☒

c. Special Manuals ☐

(1) Aircraft Engine Testing and Trending Procedures ☐

(2) Aircraft Power Package Testing Procedures ☐

(3) Static Firing of Missile Motors ☐

(4) System Peculiar Corrosion Control ☐

(5) Nondestructive Inspection (NDI) ☐

(6) Aircraft Structural Integrity Program (ASIP) ☐

(7) ATE Operator Test Procedures ☐

(8) Special Requirements for Storage and Maintenance

Procedures; AUR Munitions/Launchers and Associated

Support Equipment, Conventional Components and CMBR

Agents

(9) Parachute Packing Procedures ☐

(10) Operators Instructions (Hand-Held Flight Computers) ☐

(11) Installation-Engineering Facility (Ground C-E

Equipment)

d. Checklists (IAW MIL-DTL-5096) ☐

e. With Illustrated Parts Breakdown ☐

15. Commercial Manuals (Evaluate according to MIL-PRF-32216) ☐

16. Aircraft Cross-servicing Guide MIL-DTL-22202 ☐

TABLE 2

SUSTAINMENT/MODIFICATION UPDATES TM TYPE SELECTIONS

NOTES:

• Check all applicable boxes.

• For existing manuals not being updated to latest specification requirements, enter “Same style and format” under the specification heading.

TO Number, Title, or

Type of Manual

Specification

Change

Revision

Supple-ment

Supple-mental

TM

Source

Data

1. 11W1-12-17-2 Same Style and

Format ☒ ☐ ☐ ☐ ☐

2. 11W1-12-19-2 Same Style and

Format ☒ ☐ ☐ ☐ ☐

3. 11W1-12-21-2 Same Style and

Format ☒ ☐ ☐ ☐ ☐

4. 11W1-15-21-2 Same Style and

Format ☒ ☐ ☐ ☐ ☐

5. 11W1-15-23-2 MIL-STD-38784B NEW ☐ ☐ ☐ ☒

6. 11W1-25-2 Same Style and

Format ☒ ☐ ☐ ☐ ☐

7. 11W1-33-10-2 Same Style and

Format ☒ ☐ ☐ ☐ ☐

8. 1C-130(A)J-1* Same Style and

Format ☒ ☐ ☐ ☐ ☐

9. 1C-130(A)J-1CL-2* Same Style and

Format ☒ ☐ ☐ ☐ ☐

10. 1C-130(A)J-1-43* Same Style and

Format ☒ ☐ ☐ ☐ ☐

11. 1C-130(A)J-34* Same Style and

Format ☒ ☐ ☐ ☐ ☐

12. 1C-130(AHM)J-06 Same Style and

Format ☒ ☐ ☐ ☐ ☐

13. 1C-130(AHM)J-6 Same Style and

Format ☒ ☐ ☐ ☐ ☐

14. 1C-130(AHM)J-6WC-10 Same Style and

Format ☒ ☐ ☐ ☐ ☐

15. 1C-130(AHM)J-6WC-14 Same Style and

Format ☒ ☐ ☐ ☐ ☐

16. 1C-130(AHM)J-33-1-2 Same Style and

Format ☒ ☐ ☐ ☐ ☐

17. 1C-130(AHM)J-33-1-2CL-2 Same Style and

Format ☒ ☐ ☐ ☐ ☐

TO Number, Title, or

Type of Manual

Specification

Change

Revision

Supple-ment

Supple-mental

TM

Source

Data

18. 1C-130(AHM)J-33-1-2CL-3 Same Style and

Format ☒ ☐ ☐ ☐ ☐

19. 1C-130(AHM)J-33-1-2CL-4 Same Style and

Format ☒ ☐ ☐ ☐ ☐

20. 1C-130(AHM)J-33-1-2CL-6 Same Style and

Format

21. 1C-130(AHM)J-4-94-1 Same Style and

Format ☒ ☐ ☐ ☐ ☐

22. 1C-130(AHM)J-2-94JG-00-1 Same Style and

Format ☒ ☐ ☐ ☐ ☐

23. 1C-130(AHM)J-2-94GS-00-1 Same Style and

Format ☒ ☐ ☐ ☐ ☐

24. 1C-130(AHM)J-2-94FI-00-1 Same Style and

Format ☒ ☐ ☐ ☐ ☐

25. 1C-130(AHM)J-2-94JG-30-1 Same Style and

Format ☒ ☐ ☐ ☐ ☐

26. 1C-130(AHM)J-2-94JG-50-1 Same Style and

Format ☒ ☐ ☐ ☐ ☐

27. 1C-130(AHM)J-2-94JG-50-2 Same Style and

Format ☒ ☐ ☐ ☐ ☐

19.

Same Style and

Format ☐ ☐ ☐ ☐ ☐

19.

Same Style and

Format ☐ ☐ ☐ ☐ ☐

*-FLIGHT MANUALS

(T) PART B - TM DELIVERY REQUIREMENTS

FOR

AC-130J PRECISION STRIKE PACKAGE (PSP) TECHNICAL DOCUMENT PROJECT (TDP) FOLLOW ON

Program Name

(System/Item)

TM DATA TYPE DELIVERED (SEE TABLE 2).

(TMSS/Change/Supplement/etc.)

(Replicate form for each TM type required.)

Delivery Format Requirements Codes

Digital delivery only:

P - Paper (draft or manuscript only. Cannot be used for final delivery)

F - FrameMaker version 2020 preferred or 12.0 thru 15.0 file format. All Flight Manuals – use Government furnished tags. Deliver files in SAFE.

M - Mixed paper and digital (F, G, H, I, N or X). Non- G - Standard Generalized Mark-up Language (SGML).

TYPE II IETM Format H - Hyper Text Mark-up Language (HTML) (Helicopters only)

E – IETM in IDET format I - Indexed Portable Document Format (IPDF) File (IPDF

- new/complete TOs or PDF - change/source package(s)). Deliver files in SAFE.

N - Native Format (i.e. – PageMaker, FrameMaker (FM), Adobe Illustrator CS6 or earlier version (AI), Portable

Document Format (PDF))

X - Extensible Mark-up Language (XML) file format

S – Encapsulated PostScript (EPS) file format

PAPER/ELECTRONIC PAPER TYPE - All Final Delivery(s) with graphic(s) in digital format (excluding E -

(IETM) format delivery(s)) will be delivered as instructed on the delivery schedule. (See page 18) All Flight Manual

Final Deliver of graphics will be individual Adobe Illustrator 2020 preferred - no earlier than CS3 or later files. All change(s)/source page(s) will be 100% vector art that includes searchable text, no raster art accepted. Back-up pages may be raster art.

EXAMPLE: M(G/P)/2 [Paper and SGML/2 copies each]

IETM - All Deliveries with graphic(s) will be done in Arbortext IsoDraw 7.3 or earlier version and delivered as a

Computer Graphic Metafile (CGM/4) 100% vector art that includes searchable text. If the graphic(s) exist within the IETM, the vendor shall extract and update current graphic(s) and return the updated graphic(s) back into the IETM via the IDET tool saved as a Computer Graphic Metafile (CGM/4) 100% vector art that includes searchable text.

EXAMPLE: E/P/2 [IETM and Paper/2 copies each]

• Delivery format requirements codes indicate the media/file format to be delivered for each program event.

• TCTO requirements are specified in the contract vehicle approving the TCTO.

• When on-line access is a contractual requirement, copy quantity will normally be (zero).

• AFTO Form 158s will be provided by the Contractor after every In-Process Review (IPR) within 10 working days of said review.

• TO Updates. From each IPR, will be provided to the TOMA/FMM 30 days prior to the next IPR.

• Editorial and Technical Content cut-off will be the close and acceptance of the Verification minutes and closure of all action items from that Verification Review (IPR).

• For NGS or non-standard TMSS instances, delivery shall include the associated DTDs, FOSIs/Style Sheets, XML schemas, etc.

Each FM Delivery will be based on Mission Design Series (MDS) for C-130s. (See page 13 for all affected Flight Manuals on the

C-130s, excluding FMS.)

TABLE 3 – LINEAR TM DELIVERY REQUIREMENTS

FOR

AC-130J PRECISION STRIKE PACKAGE (PSP) TECHNICAL DOCUMENT PROJECT (TDP)

FOLLOW ON

(System/Item)

DELIVERY SCHEDULE

Event/Number of days data required prior to event

Technical

Review(s)

_____30____ Days

Verification

_____30____

Final TO

Distribution

_____45____

Office Symbol and Address Enter delivery requirements code/copy quantities required

Attn: TOMA William Rector

(Maintenance Only)

AFLCMC/WIU

370 Richard Ray Blvd, Bldg 300E

ROBINS AFB GA 31098

I/1 I/1 I/1

Attn: TOMA Timothy Bullock

(Commodity Only)

AFLCMC/WIU

370 Richard Ray Blvd, Bldg 300E

ROBINS AFB GA 31098

I/1 I/1 I/1

Attn: Henry Starks (IETMs Only)

AFLCMC/WIU

370 Richard Ray Blvd, Bldg 300E

ROBINS AFB GA 31098

N/A N/A X/1

Attn: FMM Phil Aldridge

(Flight Manuals Only)

AFLCMC/WIU

370 Richard Ray Blvd, Bldg 300E

ROBINS AFB GA 31098

I/1

P/F/I/1

F/I/N/1

Attn: FMM William Mason

(Flight Manuals Only)

AFLCMC/WIU

370 Richard Ray Blvd, Bldg 300E

I/1

P/F/I/1

F/I/N/1

Attn: ES Helmuth Ramster

(All Manuals)

AFLCMC/WIU

370 Richard Ray Blvd, Bldg 300E

ROBINS AFB GA 31098

I/1 I/1 I/1

Attn: Chief ES Andy Devlin

(All Manuals)

AFLCMC/WIU

370 Richard Ray Blvd, Bldg 300E

I/1 I/1 I/1

AFLCMC/WISM

(All Manuals)

2640 Loop Road West, Wright Patterson AFB, OH 45433

I/1 I/1 I/1

Total Copies Required: I/7 I/5

P/F/I/2

I/5

X/1

F/I/N/2

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

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

• Utilize the TMSS Tailoring Tool located at https://techdata.wpafb.af.mil/tmss/index.html by selecting all applicable

TMSS requirements, and the desired tailoring options expressed in paragraphs 6.2. Attach the TMSS Tailoring Tool spreadsheet output in the specified section listed below.

• 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/HIS, 4170 Hebble Creek Road, Bldg. 280, Door 15, Area A, Wright-Patterson AFB, Oh 45433-5653 or by email to; SGMLsupport@us.af.mil. Do not include the street address, a building number or a zip+4.

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-DTL-22202D, 31 March 1999

Supplement 1, 31 March 1999

Manual, Technical, Aircraft Cross-Servicing Guide, Preparation of

The requirements of 6.2 are met in this SIR (see below).

1.1 In addition to paper delivery, when this specification is used to develop digital delivery files (document type definitions – DTDs) contact the PA for additional instructions.

2.3 Ensure the listing for STANAG/ASCC Air Standard Documents is current. List applicable STANAG/ASCC Air

Standards below.

(List STANAG/ASCC Air Standard Documents here.)

2.2.1 (Added) “Other Government documents, drawings, and publications.”

DEPARTMENT OF DEFENSE

DODM 5200.01_AFMAN 16-1404 DOD Information Security Program

DOD 5220.22-M National Industrial Security Program Operating Manual

4. Replace with: “4. VERIFICATION.”

“All cross-servicing guides must meet the requirements of sections 3 and 5 of this specification, as required by the acquiring activity. The requirements set forth in this specification must become a part of the Contractor’s overall inspection system or quality program. The absence of any requirements in this specification must not relieve the Contractor of the responsibility of ensuring that all products or supplies submitted to the Government for acceptance comply with all requirements of the contract. Use of sampling inspections must be at the discretion of the Contractor, and in accordance with commercially acceptable quality assurance procedures. However, use of sampling in QA procedures does not authorize submission of known defective material, either indicated or actual, nor does it commit the Government to accept defective material.”

https://techdata.wpafb.af.mil/tmss/index.html https://assist.dla.mil/online/start/index.cfm mailto:SGMLsupport@us.af.mil

5. Replace with: “5. PACKAGING.”

“5.1 Packaging Requirements. For acquisition purposes, the packaging requirements must be as specified in the contract or order. When the actual packaging of material is to be performed by DoD personnel, these personnel need to contact the responsible packaging activity to determine packaging requirements. Packaging requirements are maintained by the Inventory Control Point’s packaging activity within the Military Department’s System

Command. Packaging data retrieval is available from the Military Department’s or Defense Agency’s automated packaging files, CD-ROM products, or the responsible packaging activity.”

“5.1.1 Encoded Computer Products. Packaging of encoded computer products for delivery must be in accordance with the requirements of MIL-STD-1840C, Automated Interchange of Technical Information.”

“5.1.2 Classified Material. Classified material must be packaged and identified in accordance with DODM

5200.01_AFMAN 16-1404, DOD 5220.22-M, and the implementing Service regulations.”

6.2a Title, number, and date of the specification are listed above.

6.2b Issue of DODISS: (fill in issue of DODISS applicable to this contract)

6.2c Packaging requirements (see above).

6.2d Verification requirements (see above).

Specification/Standard Interface Record for

PROJECT SIR REQUIREMENTS

ATTACHMENT 1

Graphics Format Guidelines

GENERAL GUIDELINES:

• Single column graphics should not exceed 51 Picas High by 20 Picas Wide. (Paper only)

• Full page graphics should not exceed 51 Picas High by 42 picas Wide. (Paper only)

• Fold Out graphics should not exceed 51 Picas High (width on foldouts is not important). (Paper only)

• PNG graphics will not run with the Air Force software utilized to parse SGML files.

• Avoid creating art as PNG and saving in various formats which will fail.

Encapsulated Post Script (EPS):

• Raster based images will not be saved as EPS.

• EPS files must not be a mix of vector and raster images. Vector only.

• Any source data (photos used for tracing etc.); used in aiding of creation of EPS (templates, etc.)

will be deleted from illustration prior to saving/exporting.

• If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

Tagged Image File Format (TIFF):

• Black and white raster images should only be saved as Bitmap and not Grayscale, RGB or

CMYK.

• Grayscale or Color images (screenshots, etc.) will be saved as such (Grayscale, RGB or CMYK) and will not be bitmap converted using a halftone screen.

• To further aid in file size reduction for storage purposes, images should be compressed using

Group 4 compression when saving/exporting.

Computer Graphics Metafile (CGM):

• Raster based images will not be saved as CGM.

• Any source data used in aiding of creation of CGM (templates, etc.) will be deleted from illustration prior to saving/exporting.

• CGM files must not be a mix of vector and raster images. 100% Vector only.

• If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

• Unless Version 4 is specifically required for hotspots and/or hyper linking, CGMs should be exported as version 3 to increase cross platform compatibility.

DWG File Format:

• Raster based images will not be saved as DWG.

• DWG files must not be a mix of vector and raster images. 100% Vector only.

• Any source data used in aiding of creation of DWG (templates, etc.) will be deleted from illustration prior to saving/exporting.

• If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

Joint Photographic Expert Group (JPEG): (Caution: JPEG 2000 files are not to be used at all due to platform display issues.)

• JPEG File format should be used as last resort. Color screenshots/photos should be saved as

TIFFs due to possible system compatibility issues.

• B&W Bitmaps should not be saved as JPEGs.

Portable Network Graphics (PNG):

• Used for raster graphics

• Supports lossless data compression

• PNG files do not run thru the parser for the SGML files.

Bitmap (BMP):

• Used for raster graphics

Scalable Vector Graphic (SVG)

• Two-dimensional vector and mixed vector/raster graphics