Atch_20_TMCR_for_Bomber_Armament_Test_Set.pdf

TM-86-01N 1 April 2009 1 Data Call No: GUEE-0092

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

Air Force Technical Manual Contract Requirements (TMCR) for

BOMBER ARMAMENT TEST SET

NSN 4920-01-649-0428KV

1 December 2014 12 January 2016

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT_________________

REQUEST FOR PROPOSAL/CONTRACT: _______________________________________________________

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

1. TMCR Tailoring (T). This TMCR document, including the associated tables, matrices and Specification/Standard Interface Records (SIRs) have been tailored specifically, for the BOMBER ARMAMENT TEST SET Program Requirements. Proposals shall be compatible with the Air Force infrastructure and support the BOMBER ARMAMENT TEST SET Program. Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management. A copy is available upon request from the TO Manager. Any terms or procedures found in this document may be researched there.

2. TO Program Scope (T). The Offeror shall develop and deliver new AF technical manuals (Test Set Operation and Maintenance Instructions Manual, Test Set Illustrated Part Breakdown (IPB) Manual, Unit Under Test (UUT) Test Procedures Manuals, and Calibration Procedures) to support the BOMBER ARMAMENT TEST SET program IAW Section 2, Table 1. The Offeror shall also identify change pages and provide source data updates to affected Line Replaceable Unit (LRU) Operations and Maintenance Instructions technical manuals, and aircraft Job Guides IAW Section 2, Table 2. The BOMBER ARMAMENT TEST SET program will follow three planned increments with Increment 1 for B-2A, Increment 2 for B-1B, and Increment 3 for B-52H. No tailoring shall be made to these requirements without prior approval of the TM Manager and Primary Contracting Officer (PCO).

3. Commercial Manuals (T). N/A

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between options offered in paragraph 6.2 of 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 man-datory requirements which are part of the Document Type Definition (DTD) structure.

4.1. (T). N/A.

4.2. (T). Questions concerning TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the Procuring Contracting Officer (PCO) and TO Man-ager (Holly Bolton, 406 SCMS/GUEE, 478-926-0141). Deficiencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

5. Subsequent TO/Data Requirements (T). Offeror shall propose a process for notifying the govern-ment when additional TO or source data requirements are identified subsequent to contract award. This process shall require government review and approval of recommended additional requirements prior to contractual approval. Contractor format is acceptable.

2 TM-86-01N 1 April 2009

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

6. TO Development (T). The Offeror shall development practices and procedures that ensure TOs and data are compatible with the BOMBER ARMAMENT TEST SET program objectives. In addition, TOs and source data 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-38784, Standard Practice for Manuals, Technical: General Style and Format Requirements. See sample AFTO Form 124, Attachment 3, page 26.

6.1. Page-oriented Military Specification (MILSPEC) TOs shall be formatted with text, graphics and delivery according to the TMSS specified in Section 2. The contractor shall develop TO files (tagged instances) using Standard Generalized Markup Language (SGML) according to the DTDs referenced in the appendix to MIL-STD-38784 and each applicable military detail or performance specification (MIL-DTL or MIL-PRF). All deliveries of SGML data shall be in a single file instance. Multiple file instances are not authorized.

6.2 (T). SGML-tagged TO files shall include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible. All delivered graphics shall conform to the approved graphic creation and format guidelines listed in Attachment 1, page 21.

6.3. (T). Source data shall be formatted with text/graphics and delivered according to the require-ments in paragraph 16 and as specified in Section 2.

6.4. (T). N/A.

6.5. (T). N/A.

7. TO Numbering (T). Offeror shall complete the TO Numbering, Attachment 2 to this document for each new manuals being developed. TO numbers are not required for manuals to be used exclusively by the Offeror’s own personnel. AF procedures for numbering TOs are described in TO 00-5-3 and TO 00- 5-18, AF Technical Order Numbering System. A copy is available upon request from TO Manager.

8. Data Rights (T). Offeror shall propose 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 Regulation Supplement (DFARS), paragraphs 227-7102 through 227-7104.

8.1. (T). If some TOs or source data are copyrighted or contain proprietary data or procedures, the offeror may propose Limited Rights or Government Purpose Rights (GPR) only. Proposed commer-cial manuals should be provided with at least GPR or Limited Rights. Copyrights shall be according to DFARS paragraphs 227-7103, 7105 or 7106.

8.2. (T). Specifically, if Non-Government Standards (NGS) are proposed, the government shall be given unlimited rights for all business rules (tailoring and application methods and procedures) and documented business processes developed for use in TO development. Government data rights shall extend to the common source database, transformation style sheets, and other tools or products used to author or display NGS technical data.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices (T). The Offeror shall use the below statements for each TO developed.

DISCLOSURE NOTICE - This information is furnished upon the condition that it will not be released to another nation without the specific authority of the Department of the Air Force of the United States, that it will be used for military purposes only, that individual or corporate rights originating in the information, whether patented or not, will be respected, that the recipient will report promptly to the United States, any known or suspected compromise, and that the information will be provided substantially the same degree of security afforded it by the Department of Defense of the United States. Also, regardless of any other markings on the document, it will not be downgraded or Declassified without written approval of the originating United States agency.

DISTRIBUTION STATEMENT D - Distribution authorized to the Department of Defense and U.S. DoD contractors only (Critical Technology), (XX Month 201X). Other requests shall be referred to 406 SCMS/GUEE, Robins AFB, GA 31098. Questions concerning technical content shall be directed to AFLCMC/WNAAAA, Robins AFB, GA 31098.

TM-86-01N 1 April 2009 3

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

WARNING - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DOD Directive 5230.25

HANDLING AND DESTRUCTION NOTICE - Comply with distribution statement and destroy by any method that will prevent disclosure of contents or reconstruction of the document.

10. TO Quality (T). Offeror shall propose a quality assurance program which ensures TOs are prepared IAW this contract. Recommended QA methods must include actual performance of procedures and use of desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be re-served for those procedures which would activate explosive devices or present a hazard to personnel or equipment. Offeror’s proposals shall describe how the government will be allowed to interact with the contractor’s TO development team. The contractors’ shall ensure TOs or source data prepared are: a) technically accurate and safe; b) written to a scope and depth of coverage sufficient to support the opera-tions and maintenance concepts, and c) properly classified and marked with export control and distribu-tion limitation statements.

10.1. Conferences and Technical Reviews (T). Offeror shall propose sufficient conferences and re-views to allow insight into TO development processes and ensure contract compliance. Offeror shall participate in an initial Guidance Conference or Technical Interchange Meeting (TIM) within 60 days of contract award to ensure mutual understanding of TO contract requirements, schedules, points of contact, etc. Periodic In-Process Reviews (IPRs) and Prepublication Reviews (PPR) ensure TOs are being developed according to contract requirements and that open discrepancies are cleared prior to publication. NOTE: PPRs are required for critical safety and nuclear surety procedures TOs, and may be required for other complex procedures TOs.

10.2. TO Certification. (T) The Offeror shall deliver all 100% review copies with a letter certifying completion and certification that the information has been reviewed by the contractor and is accu-rate. The contractor shall certify that the source data developed to support the program is accurate, adequate, current, and usable for their intended purpose. The Government may witness the certifica-tion activities. The contractor shall correct all comments generated by the certification process into the source data prior to submitting the source for verification. At the completion of the certification, the contractor shall submit a letter to the appropriate TOMA stating that certification has been com-pleted and that any deficiencies identified during the process have been corrected. The contractor will ensure all necessary changes and corrections to affected manuals or source data are accom-plished in time to meet contract delivery schedule requirements. The contractor shall notify the gov-ernment at least 180 days prior to the need date of any Government Furnished Infor-mation/Government Furnished Equipment (GFI/GFE) required to perform certification tasks. Tech-nical order 00-5-1 and 00-5-3 shall be referenced for additional information on TO Certification re-quirements.

10.3. Verification Support (T). Offeror shall propose the methods, equipment and personnel re-quired to support government TO Verification. This support should consist of at least engineering and technical publications personnel available to resolve questions resulting from verification activi-ties.

10.4. Technical Data Assessment (TDA – originally called First Article Testing) (T). The TO Manag-er, will determine the TDA requirements for each TO type. The contractor will submit an SGML-tagged TO file, separate graphics files, and a PDF rendition of the composed SGML File to the program office concurrent with each IPR, for TDA to verify compliance of the digital files to Air Force DSSs. Additional TDAs will be required at each succeeding review. The TDA parsing in no way relieves the contractor from correcting tagging errors that are noted during the composing effort.

Repeat TDAs shall be required whenever new DSS or DTD versions are used for TO development.

4 TM-86-01N 1 April 2009

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

The contractor shall deliver the SGML files, Graphics Files, and the IPDF output from these files for each review.

11. TO and Source Data Maintenance. Offeror shall propose methods for maintaining accuracy, cur-rency and configuration of existing AF TOs and source data throughout the contract period of perfor-mance. Maintenance includes preparation of TO and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes.

12. TO Delivery (T). TO file delivery formats shall be according to applicable CDRLs and the tailored TM Delivery Requirements Matrices included in Section 2 of this document.

12.1. SGML-Tagged Files (T). The contractor shall parse and compose SGML-tagged TO docu-ment files prior to delivery to the government, and verify that content tagging has been accomplished to the levels provided in the DTD. NOTE: The Government will perform completeness checks of all SGML data prior to acceptance. Any data failing final acceptance shall be returned to the con-tractor for correction then returned to the Air Force for additional testing to the Government.

12.2. SGML-Tagged Files for Use with the eTO Viewer (T). N/A.

12.3. Interactive Electronic Technical Manuals (IETM) (T). N/A.

12.4. Indexed Adobe™ Portable Document Format (IPDF) Files (T). The contractor shall validate indexing of PDF TO files using the specifications contained in the Technical Order Conversion Re-quirements. A copy is available upon request from TO Manager.

13. Schedules (T). NOTE: AF policy requires delivery of verified TOs prior to or concurrently with delivery of operational equipment to the field (AFI 63-101, Acquisition and Sustainment Lifecycle Management). This policy will determine TO development and delivery schedules throughout the acquisition phase of a program.

14. Time Compliance Technical Orders (TCTOs) (T). N/A.

15. TO Reproduction Management (T). Offeror shall propose practices and procedures for managing the program’s Preliminary TO reproduction requirements. MIL-HDBK-38790, Printing Production of Technical Manuals, may be used as guidance for TO printing format, paper weights, layout require-ments, etc. NOTE: Reproduction management for formal TO printing includes assembly of a print package (reproduction media, a reproduction assembly sheet , and TO Initial Distribution (ID) labels) and submission of the package for government printing through the Defense Automation and Publica-tion Service (DAPS) TO Distribution and Print System (TODPS). (ID labels or label files are provided by the TO Manager) In some cases, the contractor may perform the printing. Reproduction manage-ment for digital media consists of reproduction of the digital file on magnetic/optical media and distribu-tion according to ID labels. Reproduction Management may also include configuration control and stor-age of reproduction masters.

16. Program Specific Requirements.

A. The Offeror shall develop and deliver new MIL-SPEC technical manuals covering Test Set Operation and Maintenance Instructions, Test Set Illustrated Parts Breakdown (IPB), Unit Under Test (UUT) Test Procedures and Calibration Procedures IAW Section 2, TO types (Table 1) in SGML format to support the BOMBER ARMAMENT TEST SET program’s objectives. A new Depot Overhaul Instructions manual requirements will be determined after the Depot Source of Repair decision is made.

The Offeror shall also identify change pages and provide source data updates to affected Line Replaceable Unit (LRU) Operations and Maintenance Instructions, and aircraft Job Guides IAW Section 2, Addition TM Type (Table 2) in the same style and format. The initial Required Assets Available (RAA) quantity of production deliverables for B-2A Increment 1 shall be fielded not later than 25 September 2020. All

TM-86-01N 1 April 2009 5

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16 production deliverables for B-1B Increment 2 shall be fielded not later than 25 September 2022. All production deliverables for B-52H Increment 3 shall be fielded not later than 25 Spetember 2025.

B. The manual(s) shall be developed using the latest version of the development specifications listed in Table 1 of this document. Data delivered for this contract shall be a combination of paper based documents and digital files.

C. SGML files shall be reviewed by the Air Force during the development process to ensure compliance with the approved DTDs. The contractor shall submit copies of their SGML Instance, PDF file of their SGML Instance and separate graphics files used with the SGML Instance with each In-Process review.

D. The Offeror shall develop and deliver source data covering changes affecting the Technical Orders listed in Table 2. All changes which affect form, fit, function, or interface to the existing Air Force equipment, shall be described and listed in Table 2. Source data text and graphics shall be documented on the attached AF Form 158 (Attachment 5, Page 28) or on attached Unnumbered Supplement Source Data Form (Sample Attachment 6, page 29) for incorporation into the manual. Specific guidelines will be provided during the initial guidance conference.

E. For Graphics formats, see “Graphics Format Recommendations” attachment 1 to this document.

These recommendations provide wide latitude for developing and delivering graphics. The Contractor shall select one method from these recommendations to prepare and deliver all graphics files. Graphic resolution shall be a minimum of 300 DPI. Graphics files shall be delivered as separate files regardless whether they are embedded in the documents or not. Digital photographs (halftones) shall NOT be used. All graphics shall be line artwork.

F. The IPB shall require verification of the data based upon the configuration baseline engineering draw-ings and provisioning documentation if provisioning is accomplished. The contractor shall plan for these events in their technical manual development schedule.

G. All electronic files delivered on this project shall be non-password protected and allow unlimited access to change/modify/or capture the data from the files.

H. Data delivered for this contract shall be a combination of paper based documents and digital files.

I. In-Process reviews shall be held at the 35% and 70% completion point for each manual under devel-opment. Sample In-Process Completion tables are provided on page 27, Attachment 4.

J. Comments generated during ALL development reviews shall be incorporated before scheduling the next development review, for example 35% IPR comments shall be incorporated before scheduling the 70% IPR. The Contractor shall provide technical and engineering personnel to assist Air Force person-nel during the development reviews and Verification.

K. Comments generated during ALL development reviews shall be corrected before re-submittal of the required source data.

6 TM-86-01N 1 April 2009

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

NOTE: Contractors are responsible for selecting SGML and composition tools for this program.

AF DTDs will work with most COTS SGML editing systems (except Framemaker) however, the FOSIs were developed to work with Datalogic Composing software ONLY. If the Contractor wishes to use any other composing software product, the Contractor is responsible for ensuring all formatted outputs are compatible with the DTL specification listed in Section 2, Table 1 of this document. Structured Framemaker files are unacceptable and shall not be submitted as an SGML delivery to the Air Force.

TM-86-01N 1 April 2009 7

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

All page-based TOs developed under this contract must conform to the general style and format requirements of MIL- STD-38784 and the DTL or PRF specification called out on Section 2, Table 1.

Check the ASSIST database, http://dodssp.daps.dla.mil/assist.htm, for updated versions of the required TMSS prior to initiating any work on this proposal/contract.

Manuals delivered using this table and DI-TMSS-80067, CFAE/CFE Notices, must be reviewed and approved by the Air Force prior to delivery.

IPBs are developed IAW MIL-PRF-38807, except that MIL-DTL-87929 will also be used for IPBs combined with work packages.

Delivery requirements are indicated in the TM Delivery Requirements matrices.

A new ATE Operator Test Procedures manual will be delivered in each increment. All other new AF manuals in Table 1 will be delivered in Increment 1.

Deliverance of the Depot Overhaul Instructions Manual is conditioned on the Depot Source of Repair Decision.

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE BOMBER ARMAMENT TEST SET PROGRAM

Title or Type of Manuals Specification Required

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

a. Operation & Maintenance Instructions Manual

b. ATE Operator Test Procedures

MIL-DTL-87929D

MIL-DTL-87929

2. Illustrated Parts Breakdown Manual (see notes) MIL-PRF-38807D

3. Calibration Procedures MIL-PRF-38793

4. Depot Overhaul Instructions Manual (Conditioned on Depot Source of Repair Decision) MIL-PRF-38793

8 TM-86-01N 1 April 2009

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

Notes:

Check all applicable.

For commercial manual supplemental data only, under the specification heading, enter “Same style and format,” “MIL-PRF-38807” (for IPB data), or “MIL-STD-38784.”

For existing MIL-SPEC Manuals not being updates to latest specification requirements, enter “Same style and format” under specification heading.

If any existing SGML-tagged formats are not TMSS compliant and cannot be viewed on the eTO Viewer (eTOV), revision and new TOs which will be converted to HTML and distributed as eTOs must be brought into compatibility with the eTOV.

TO Number, Com- Supple- Title,or Type mercial Change/ Supple- mental Source of Manual Specification Manual Revision ment TM Data TOMA

B-2B Increment 1 Aircraft Job Guide

1. 1B-2A-4-94 Same style Jonathan Morgan (Tinker)

B-2B Increment 1 LRU Operations and Maintenance Instructions Manuals

2. 11B29-3-62-2 Same style Dean Ellison (Robins)

3. 11B29-3-62-2-1 Same style Dean Ellison (Robins)

4. 11B29-3-62-8-1 Same style Dean Ellison (Robins)

5. 11B29-3-66-1 Same style Dean Ellison (Robins)

6. 11B29-3-66-4 Same style Dean Ellison (Robins)

7. 11B29-3-68-3 Same style Dean Ellison (Robins)

8. 11B29-3-70-1 Same style Dean Ellison (Robins)

9. 11B29-3-70-8-1 Same style Dean Ellison (Robins)

10. 11B29-3-72-8-1 Same style Dean Ellison (Robins)

11. 11N-L5008-1 Same style Terry Turner and Lawrance Rozier (Tinker)

12. 11N-T5166-3 Same style Denice Young (Tinker)

TM-86-01N 1 April 2009 9

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

TO Number, Com- Supple- Title, or Type mercial Change/ Supple- mental Source of Manual Specification Manual Revision ment TM Data TOMA

13. 11N-T5166-4 Same style Terry Turner and

Lawrance Rozier (Tinker)

14. 11N-T5167-3 Same style Denice Young (Tinker)

15. 11N-T5168-2 Same style Denice Young (Tinker)

16. 11N-T5168-3 Same style Denice Young (Tinker)

17. 11N-T5169-3 Same style Denice Young (Tinker)

18. 11N-T5178-3 Same style Denice Young (Tinker)

19. 33D5-12-243-1 Same style Holly Bolton (Robins)

20. 33D5-12-243-8-1 Same style Holly Bolton (Robins)

21. 33D9-61-71-21 Same style Paula Schexnayder (Robins)

22. 33D9-61-71-24 Same style Paula Schexnayder (Robins)

23. 11N-L5006-1 Same style Ronald Daggs (Tinker)

24. 11N-L5006-4 Same style Ronald Daggs (Tinker)

25. 11N-T5166-1 Same style Ronald Daggs (Tinker)

26. 11N-T5166-2 Same style Ronald Daggs (Tinker)

27. 11N-T5166-8 Same style Ronald Daggs (Tinker)

28. 11N-T5167-1 Same style Ronald Daggs (Tinker)

29. 11N-T5167-2 Same style Ronald Daggs (Tinker)

30. 11N-T5167-4 Same style Ronald Daggs (Tinker)

31. 11N-T5167-8 Same style Ronald Daggs (Tinker)

32. 11N-T5168-1 Same style Ronald Daggs (Tinker)

33. 11N-T5168-4 Same style Ronald Daggs (Tinker)

34. 11N-T5168-8 Same style Ronald Daggs (Tinker)

10 TM-86-01N 1 April 2009

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

TO Number, Com- Supple- Title, or Type mercial Change/ Supple- mental Source

35. 11N-L5002-2 (change to 11L1-6-3-2WA-1) Same style Jeffrey McBride (Tinker)

36. 11N-L5002-4 (change to 11L1-6-4-4-WA-1) Same style Jeffrey McBride (Tinker)

37. 16W6-33-1 Same style Terry Turner and

38. 16W6-33-4 Same style Terry Turner and

(Tinker)

B-1B Increment 2 Aircraft Job Guides

1. 1B-1B-2-40GS-00-1 Same style Jeffrey McBride (Tinker)

2. 1B-1B-2-40GS-00-15 Same style Jeffrey McBride (Tinker)

3. 1B-1B-2-24JG-50-1 Same style Denice Young (Tinker)

4. 1B-1B-2-94JG-00-10 Same style Joshua Gay (Tinker)

5. 1B-1B-2-94JG-00-14 Same style Joshua Gay (Tinker)

6. 1B-1B-2-94JG-00-17 Same style Joshua Gay (Tinker)

7. 1B-1B-94JG-30-7 Same style Joshua Gay (Tinker)

B-1B Increment 2 LRU Operations and Maintenance Instructions Manuals

8. 11B12-2-9-4 Same style Bailee Brown (Tinker)

9. 11B29-3-55-1 Same style Dean Ellison (Robins)

10. 11B29-3-55-3 Same style Dean Ellison (Robins)

11. 11B29-3-55-4 Same style Dean Ellison (Robins)

12. 11B29-3-56- Same style Dean Ellison (Robins)

13. 11B29-3-59-2 Same style Dean Ellison (Robins)

14. 11N-H5086-2 Same style Jeffrey McBride (Tinker)

15. 11N-L5002-8 Same style Jeffrey McBride (Tinker)

TM-86-01N 1 April 2009 11

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

TO Number, Com- Supple- Title, or Type mercial Change/ Supple- mental Source

16. 33D5-53-15-1 Same style Holly Bolton (Robins)

17. 33D5-53-1-111 Same style Dean Ellison (Robins)

18. 33D7-33-192-1 Same style Bailee Brown (Tinker)

19. 33D7-33-192-4 Same style Amanda Marinelli (Tinker)

B-52H Increment 3 Aircraft Job Guides

1. 1B-52H-2-31GA-1 Same style Vicki Newby (Tinker)

2. 1B-52H-2-31JG-15 Same style Vicki Newby (Tinker)

3. 1B-52H-2-31JG-16 Same style Vicki Newby (Tinker)

4. 1B-52H-2-38GA-1 Same style Vicki Newby (Tinker)

5. 1B-52H-2-38JG-2 Same style Vicki Newby (Tinker)

6. 1B-52H-2-38JG-3 Same style Vicki Newby (Tinker)

7. 1B-52H-2-38JG-7 Same style Vicki Newby (Tinker)

B-52H Increment 3 LRU Operations and Maintenance Instructions Manuals

8. 11B29-3-21-2 Same style Dean Ellison (Robins)

9. 11B29-3-25-2 Same style Dean Ellison (Robins)

10. 11B29-3-25-7-1 Same style Dean Ellison (Robins)

11. 11B29-3-52-2 Same style Vicki Newby (Tinker)

12. 11B38-2-5-1 Same style Dean Ellison (Robins)

13. 11B38-2-5-3 Same style Dean Ellison (Robins)

14. 11L1-2-25-1 Same style Terry Turner and

15. 11L1-2-25-8-4 Same style Terry Turner and

12 TM-86-01N 1 April 2009

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

TO Number, Com- Supple- Title, or Type mercial Change/ Supple- mental Source

16. 11L1-4-2-2 Same style James Jones (Tinker)

17. 16W6-47-2 Same style Vicki Newby (Tinker)

18. 33D5-30-9-1 Same style Holly Bolton (Robins)

19. 33D5-30-9-3 Same style Holly Bolton (Robins)

20. 33D5-30-9-4 Same style Holly Bolton (Robins)

TM-86-01N 1 April 2009 13

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

PART B - TM DELIVERY REQUIREMENTS

FOR BOMBER ARMAMENT TEST SET

(System/Item)

TM DATA TYPE DELIVERED NEW AF MANUALS.

(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 G - Standard Generalized Mark-up Language (SGML).

final delivery) H - Hyper Text Mark-up Language (HTML) M - Mixed paper and digital (G, H or I) I - Indexed Portable Document Format (IPDF) File.

X - Extensible Mark-up Language (XML)

EXAMPLE: M(P/G/I) / 2 [Paper, SGML, and IPDF / 2 copies]

NOTES:

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

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

ATE Operator Test Procedures manual only to each Tinker AFB, OK address in New AF Manuals Part B TM Delivery Requirements.

Calibration Procedures manual only to AFMETCAL.

Table 1 new AF manuals EXCEPT Calibration Procedures delivered to Robins AFB, GA.

DELIVERY SCHEDULE

Event Number of days data required prior to event

Technical Review(s) (60 Days)

Verification (60 Days)

Prepublication Review (60 Days)

Final TO Distribution (60 Days)

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

Attn: Holly Bolton

406 SCMS/GUEE

235 BYRON ST., SUITE 19A

Robins AFB, GA 31098-1670

M(P/G/I) /

M(P/G/I)/

M(P/G/I)/ 2 M(P/G/I)/ 2

Engineering (Draft) Copy/Copies

LCMC/WMNNM

AF Metrology and Calibration Division ATTN: Paul Najdowski 813 Irving Wick Drive West, Bldg 2 Heath, Ohio 43056-1199

I/ 1 I/ 1 I/ 1 I/ 1

Attn: Jeffrey McBride

AFLCMC/WWDNC

3001 Staff Drive Tinker AFB, OK 73145

M(P/G/I)/

M(P/G/I)/

M(P/G/I)/ 2 M(P/G/I)/ 2

Attn: Terry Turner

AFNWC/NDMET 469 2C2

Tinker AFB, OK 73145

M(P/G/I) /

M(P/G/I)/

M(P/G/I)/ 3 M(P/G/I)/ 3

14 TM-86-01N 1 April 2009

Attn: Denice Young

406 SCMS/GUEEB

3001 Staff Dr, STE 1AF1-117 Tinker AFB, OK 73145

M(P/G/I) /

M(P/G/I)/

M(P/G/I)/ 2 M(P/G/I)/ 2

Attn: Ronald Daggs

412 MXLS/WWZL

7180 Reserve Rd Tinker AFB, 73145

M(P/G/I) /

M(P/G/I) /

M(P/G/I) / 2 M(P/G/I) / 2

Total Copies Required: 12 12 12 12

TM-86-01N 1 April 2009 15

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

PART B - TM DELIVERY REQUIREMENTS

INCREMENT 1

TM DATA TYPE DELIVERED SOURCE DATA.

(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 G - Standard Generalized Mark-up Language (SGML).

final delivery) H - Hyper Text Mark-up Language (HTML) M - Mixed paper and digital (G, H or I) I - Indexed Portable Document Format (IPDF) File.

X - Extensible Mark-up Language (XML)

EXAMPLE: M(P/G/I) / 2 [Paper, SGML, and IPDF / 2 copies]

NOTES:

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

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

DELIVERY SCHEDULE INCREMENT 1

Event Number of days data required prior to event

Technical Review(s) (60 Days)

Verification (60 Days)

Prepublication Review (60 Days)

Final TO Distribution

235 BYRON ST., SUITE 19A

Robins AFB, GA 31098-1670

M(P/I) / 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

Attn: Dean Ellison

406 SCMS/GUEE

235 BYRON ST., SUITE 19A

Robins AFB, GA 31098-1670

M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

Attn: Paula Schexnayder

406 SCMS/GUEE

235 BYRON ST., SUITE 19A

Robins AFB, GA 31098-1670

M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

Attn: Jonathan Morgan

AFLCMC/WWZL

Bldg 1083 AFMC/WWZL Tinker AFB, OK 73145

M(P/I) / 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

Attn: Terry Turner and Lawrance Rozier

AFNWC/NDMET 469 2C2

Tinker AFB, OK 73145

M(P/I) / 3 M(P/I)/ 3 M(P/I)/ 3 M(P/I)/ 3

16 TM-86-01N 1 April 2009

3001 Staff Dr, STE 1AF1-117

M(P/I) / 2 M(P/I) / 2 M(P/I)/ 2 M(P/I) / 2

Attn: Ronald Daggs

412 MXLS/WWZL

7180 Reserve Rd Tinker AFB, 73145

M(P/I) / 2 M(P/I) / 2 M(P/I) / 2 M(P/I) / 2

Total Copies Required: 15 15 15 15

TM-86-01N 1 April 2009 17

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

PART B - TM DELIVERY REQUIREMENTS

INCREMENT 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 G - Standard Generalized Mark-up Language (SGML).

final delivery) H - Hyper Text Mark-up Language (HTML) M - Mixed paper and digital (G, H or I) I - Indexed Portable Document Format (IPDF) File.

X - Extensible Mark-up Language (XML)

EXAMPLE: M(P/G/I) / 2 [Paper, SGML, and IPDF / 2 copies]

NOTES:

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

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

DELIVERY SCHEDULE INCREMENT 2

Event Number of days data required prior to event

Technical Review(s) (60 Days)

Verification (60 Days)

Prepublication Review (60 Days)

Final TO Distribution

235 BYRON ST., SUITE 19A

Robins AFB, GA 31098-1670

M(P/I) / 2 M(P/I)/ 2 M(P/G/I)/ 2 M(P/I)/ 2

Attn: Dean Ellison

406 SCMS/GUEE

235 BYRON ST., SUITE 19A

Robins AFB, GA 31098-1670

M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

Attn: Jeffrey McBride

AFLCMC/WWDNC

3001 Staff Drive Tinker AFB, OK 73145

M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

Attn: Joshua Gay

AFLCMC/WWDNC

Bldg 3001 Post 2AB-83A Tinker AFB, 73145

M(P/I) / 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

Attn: Bailee Brown

406 SCMS/GUEEB

Bldg 3001 Post1AG1117 Tinker AFB, 73145

M(P/I) / 2

M(P/I)/ 2

18 TM-86-01N 1 April 2009

3001 Staff Dr, STE 1AF1-117

Attn: Amanda Marinelli

406 SCMS/GUEEB

BLDG 3001 POST 1AG1/117

Total Copies Required: 14 14 14 14

TM-86-01N 1 April 2009 19

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

PART B - TM DELIVERY REQUIREMENTS

INCREMENT 3

(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 G - Standard Generalized Mark-up Language (SGML).

final delivery) H - Hyper Text Mark-up Language (HTML) M - Mixed paper and digital (G, H or I) I - Indexed Portable Document Format (IPDF) File.

X - Extensible Mark-up Language (XML)

EXAMPLE: M(P/G/I) / 2 [Paper, SGML, and IPDF / 2 copies]

NOTES:

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

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

DELIVERY SCHEDULE INCREMENT 3

Event Number of days data required prior to event

Technical Review(s) (60 Days)

Verification (60 Days)

Prepublication Review (60 Days)

Final TO Distribution

235 BYRON ST., SUITE 19A

Robins AFB, GA 31098-1670

M(P/I) / 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

Attn: Dean Ellison

406 SCMS/GUEE

235 BYRON ST., SUITE 19A

Robins AFB, GA 31098-1670

M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

Attn: Vicki Newby

AFLCMC/WWDEC

BLDG 3001 STE.2AB81

Tinker AFB, OK 73145

M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

Attn: Terry Turner and Lawrance Rozier

AFNWC/NDMET 469 2C2

Tinker, AFB, OK 73145

M(P/I) / 3 M(P/I)/ 3 M(P/I)/ 3 M(P/I)/ 3

Attn: James Jones

AF.CMC/WWDEC

BLDG 3001 POST 2AB181A

M(P/I) / 2 M(P/I)/ 2 M(P/I)/ 2 M(P/I)/ 2

20 TM-86-01N 1 April 2009

Total Copies Required: 11 11 11 11

TM-86-01N 1 April 2009 21

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

ATTACHMENT 1

Graphics Format Recommendations

GENERAL GUIDELINES

Single column graphics should not exceed 51 Picas High by 18 Picas Wide.

Full page graphics should not exceed 51 Picas High by 42 picas Wide.

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

Recommend 300 DPI for all graphics to help decrease file/PDF sizes due to there being really no discernible quality difference over 600 DPI.

Directorates must know what graphic file types they can utilize and sustain with software availa-ble on hand and request file types to match.

The 5 most common graphics file types are: EPS, TIFF, CGM, JPEG & DWG. Each is ad-dressed below:

EPS:

Raster based images will not be saved as EPS.

EPS files shall 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.

TIFF:

B&W 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.

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 illustra-tion prior to saving/exporting.

CGM files shall not be a mix of vector and raster images. 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 ex-ported as version 3 to increase cross platform compatibility.

DWG:

Raster based images will not be saved as DWG.

DWG files shall not be a mix of vector and raster images. Vector only.

Any source data used in aiding of creation of DWG (templates, etc.) will be deleted from illustra-tion 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.

JPEG:

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

TIFFs due possible system compatibility issues.

B&W Bitmaps should not be saved as JPEGs.

22 TM-86-01N 1 April 2009

Prepared by Holly Bolton 406 SCMS/GUEE (478) 926-0141 1 Dec 14, 12 Jan 16

Attachment 1 Requirements for CGM Level 4 Vector Graphics

1. All illustrations shall be delivered in Computer Graphics Metafile Level 4 Vector (.cgm) format.

2. Illustrations shall be named as “ab1b-XX-YYYY-

ZZZn.cgm” ab1b lead-in just showing it is a

B1 TO

XX Type of manual (21 means it is a GS, 22 means it is a JG YYYY system, sub system (i.e. 2110 would be 21-10-00) ZZZ specific art file number. Originally, every TO series started with 001, 002 for the next illustration in the TO throughout the series, and so on. The numbers do not need to be sequential through the TO.

n Indicates revision levels for the illustration. Always a lower case alpha character.

(This is no longer supported. The Content Management System now maintains versioning).

Example ab1b-22-3427-116a - The 22 means JG, the 3427 is the system, subsystem of 34-27 (34 is Na-vi- gation, 27 is Attitude and Direction), which puts it in TO 1B-1B-2-34JG-20-3, and 116a is revision A to the 116th illustration in the 34JG series.

3. Illustrations shall consist of two layers: text & standard.

a. Text layers shall consist of text and lead line arrows (see chart for other items).

b. All others shall be in standard (see note for exceptions on schematics).

4. All lead line text shall be 8 pt Arial.

5. Group all elements that make a part (e.g., all lines, ellipses, chamfers, and fillets that make a bracket shall be grouped).

6. Do not group elements that are in different layers.

7. Individual spot illustrations located on the same page shall be sized proportionately to eliminate white space between illustrations.

8. The figure number or illustration control number (icn) shall be located in the lower right corner of the graphic and be 6pt Arial font.

9. All illustrations shall be placed in the appropriate template size.

GS Manuals

JG Manuals

Template Width (inches) Depth (inches) Half page 4 3 Full page 4 6.25 Foldout Page 8.25 6.25

Template Half page

Width (inches)

Depth (inch-es)

Full page 7 8.75 B size 16 ½ 8.75 C size 25 8.75 D size 33 ½ 8.75 E size 42 8.75 F size 50 ½ 8.75 Full horizontal 8 7.0 Single column 3.3 Up to 8.5

TM-86-01N 1 April 2009 23

Attachment 1 Requirements for CGM Level 4 Vector Graphics Continued

24 TM-86-01N 1 April 2009

Attachment 1 Requirements for CGM Level 4 Vector Graphics Continued

TM-86-01N 1 April 2009 25

ATTACHMENT 2

REQUEST FOR TECHNICAL ORDER NUMBER

(15 August 2014)

1. PRIME WEAPON’S SYSTEM (If Applicable)____________________ or N/A *

2. CONTRACT NUMBER: (If Applicable) _______________________________________________

3. PURCHASE REQUEST (PR) NUMBER: (If applicable) ____________________________________

4. MISSION DESIGN SERIES/NOMENCLATURE (Name Of Equipment): ________________________*

5. PART NUMBER(s):________________________________*

6. NSN/FSN:___________________________* (or temp NSN) MMAC CODE:_________

7. LEAD COMMAND: ____________________* PROGRAM ELEMENT CODE (PEC):

8. PROGRAM GROUP: _______________________________* PROGRAM NAME: ______________________*

9. DOES MANUAL EXIST FOR SAME/SIMILAR EQUIPMENT? TO NUMBER: _________________

10. RECOMMENDED TILE OF MANUAL:________________________________________________________*

11. CLASSIFICATION OF MANUAL: ______* CLASSIFICATION OF TITLE: ___________*

12. EQUIPMENT MOTIVATION (electric, hydraulic, mechanical) (If Applicable) ________________________

13. TYPE OF CURRENT, IF ELECTRIC (AC/DC/AC-DC): _______________________________

14. KIND OF MANUAL (Opn & Maint with IPB, Overhaul, etc.):_________________________________*

15. KIND OF EQUIPMENT (air or ground):______________________*

16. COMMERCIAL OFF THE SHELF (COTS) ITEM YES ______ NO _______

17. SUGGESTED TECHNICAL ORDER NUMBER:________________________________________*

18. MANUAL FORMAT: __________________________________ Example – Work Package, WUC, LOAP, etc.

19. CONTRACTOR INFORMATION: (If Applicable)

a. NAME OF VENDOR: __________________________________________________

b. ADDRESS: __________________________________________________________

c. MANUFACTURER'S CODE: _____________________________________________

d. POINT OF CONTACT: _________________________________________________

20. FOREIGN MILITARY SALES (FMS) YES ___ NO ____ (If YES, complete item 20)

20. COUNTRY CODES (For CSTO/FMS manuals): (See TO 00-5-19 if applicable): _______________________

MAIL COMPLETED FORM TO: 406 SCMS/GUEE

235 Byron St., Suite 19A ROBINS AFB, GA 31098-1813 (Technical Order number assignment may require thirty days.)

PROCUREMENT BUYER: _______________________ OFFICE SYMBOL: _________ TELEPHONE EXT.:

ES: ______________________ ES CODE: __________* OFF SYM: _________ ES PHONE: _________________

* = Mandatory Fields

26 TM-86-01N 1 April 2009

ATTACHMENT 3

AFTO FORM 124, 19970401 (IMT-V1) PREVIOUS EDITION IS OBSOLETE.

COMPUTATION OF TECHNICAL ORDER READING GRADE LEVEL

1. T.O. TITLE 2. T.O. NUMBER

3. T.O. DATE

4. NUMBER OF PAGES OF TEXT IN T.O 7. T.O. MANAGER /OFFICE SYMBOL/DSN

5. READING GRADE LEVEL IAW MIL-STD-38784

6. COMPUTED OVERALL GRADE LEVEL OF T.O.

8. TO COMPUTE READING GRADE LEVEL (RGL) OF T.O., USE "READABILITY" CRITERIA PRESCRIBED BY MIL-STD-38784 OR RECORD THE COMPUTER-

DERIVED RGL WHEN AVAILABLE.

SAMPLE NUMBER A

PAGE NUMBER OF

SAMPLE B

NUMBER OF WORDS

IN SAMPLE C

NUMBER OF

SENTENCES IN SAMPLE

D

NUMBER OF

SYLLABLES IN SAMPLE

E

SAMPLE GRADE LEVEL

F

9. PROJECT OFFICER GRADE OFFICE SYMBOL PHONE

10. SIGNATURE DATE

TM-86-01N 1 April 2009 27

ATTACHMENT 4

Sample Work Package Format IPR Completion Chart

TO Section 35% Complete 70% Complete Title Page 100% - Front Matter - 70% Numerical Index 100% - WP 001 00 Alphabetical Index 100% - WP 002 00 Foreword 50% 90% WP 003 00 Master List of Special Tools, Test Equipment and Consumables

35% 70%

WP 004 – WP 997 Technical Work Packages At Least 1 WP 100% 70% of Re-maining WP Complete

WP 998 Illustrated Parts Breakdown (If combined) 35% 80% WP 999 00 Difference Data Sheets (If used) 100% -

Example of some Technical Work Packages (Task Oriented) (List not all inclusive, Vendor may need to expand depending upon equipment being developed.)

Theory of Operation Operating Instructions Receiving and Shipping Instructions Remove and Replace Instructions Troubleshooting Schematic Diagrams Inspection Requirements Corrosion Prevention Instructions Initial Setup Fault Isolation Procedures Lubrication Instructions Disassembly Cleaning Post maintenance Operational Checkout

28 TM-86-01N 1 April 2009

ATTACHMENT 5

AFTO FORM 158

TECHNICAL ORDER REVIEW COMMENT SHEET

TO NUMBER: TITLE: RECEIVED DATE:

TOTAL PAGES:

Name of Reviewer: DATE OF REVIEW:

COMPLETE DATE:

Section

Para/Fig/Page

Comments:

AFTO FORM 158

TM-86-01N 1 April 2009 29

ATTACHMENT 6

30 TM-86-01N 1 April 2009

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

NOTES:

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 and 6.2b. For this contract enter:

6.2a. The title, number and date of each specification will be listed in the heading of the applicable SIR.

6.2b. The issue of the DODISS used in this contract is (enter date).

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) 754 ELSG/ILMT.

Non-government Standards (NGS) shall be provided by the Offeror. The Government will not be responsible for providing NGS.

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-STD-38784A, 25 August 2011

Department of Defense

Standard Practice for Manuals, Technical:

General Style and Format Requirements

4.2.1c(1) Technical manuals shall be 8-1/2 x 11 inches formatted in double column format.

4.6.2 Photographs/line drawings. Delete paragraph.

4.6.4 Continuous Tone Artwork (see 3.2.8). Delete paragraph.

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-DTL-87929D, 20 April 2012

Detail Specification

Technical Manuals, Operation and Maintenance Instructions In Work Package Format

6.2b Technical Manuals shall be formatted in Double Column Format (paragraph 3.1).

6.2c(6) Manual Sets are not applicable.

6.2c(7) Major Accessories not applicable.

6.2d Master List of Containers not applicable.

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-DTL-38807D, 17 September 2012

Detail Specification

Technical Manuals, Illustrated Parts Breakdown

6.2b Technical Manuals shall be formatted as WP 998 00 in a combined manual (paragraph 1.1).

6.2l Manufacturer List is not required (paragraph 3.5.13).

6.2m Reference Designators not applicable (paragraph 3.6.6.9).

6.2n Paragraph 3.6.7 not applicable.

6.2o Multiple SMR columns not required. (Paragraph 3.6.7.7.1).