R11TMCRB001.pdf

Amber.McCulloch Typewritten Text B001

TM-86-01N 1 April 2009 1 Data Call GULAC-0007

Prepared by: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511

Air Force Technical Manual Contract Requirements (TMCR) for

TRUCK, TANK, 6000 GAL. FUEL SERVICING, A/S32R-11, NSN 2320-00-433-5695

(Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date: 26 APRIL 2012 Amended: 8 June 2012

Amended: 5 December 2012 Amended: 20 December 2012

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 Specifica-tion/Standard Interface Records (SIRs) page 15, has been tailored specifically, for the Truck, Tank, 6000 Gal. Fuel Servicing, A/S32R-11 Program Requirements. Proposals shall be compatible with the Air Force infrastructure and support the Truck, Tank, 6000 Gal. Fuel Servicing, A/S32R-11 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 Man-ager. Any terms or procedures found in this document may be researched there.

2. TO Program Scope (T). The Offeror may recommend tailoring for Section 2 to propose the TO types (Table 1) page 7, to support the Truck, Tank, 6000 Gal. Fuel Servicing, A/S32R-11 program’s objectives.

All recommended tailoring shall be submitted through the Air Force PCO for consideration and/or approv-al/disapproval. No tailoring shall be made to these requirements without prior approval of the TM Manag-er and Primary Contracting Officer (PCO).

3. Commercial Manuals(T). Offerors may propose the use of existing commercial manuals for the en-gine, transmission and chassis to the maximum extent possible without impairing program support ob-jectives. The proposal will describe the method used to recommend and submit specific manuals to the government for review and approval. NOTES: Government activities will use MIL-PRF-32216, Eval-uation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data, as a guide for review and acceptance of all recommended engine commercial manuals. All commercial manuals shall be delivered with either unlimited data rights or as a minimum, Government Purpose License Rights (Sample provided on page 11), Attachment 2, to allow the AF to; electronically store, print, dis-tribute and decollate the commercial manual to allow for postscript printing. COTS Manuals shall be delivered with an Identifying TO Publication Sheet, Attachment 3, (page 12) for all delivered COTS manuals. All IPDF files of commercial data shall be non-password protected to allow the AF to append an Identifying TO Publication Sheet and the GPLA ahead of the title page of the book.

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 (page15), 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.

2 TM-86-01N 1 April 2009

Prepared by: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511

4.1. AF options in some Joint-Service TMSS have been documented in preliminary SIRs included in Section 3 (page 15). These preliminary SIRs provide the starting point for further tailoring. Offe-rors shall complete tailoring of the Joint-Service TMSS SIRs and provide recommended SIRs for other TMSS or NGS 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 un-marked and “(F)” TMSS requirements as modified by the options in paragraph 6.2.

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) to the TO Manager (Mrs. Theresa A. Johnson, 406 SCMS/GUEE, 235 Byron St., Suite 19A, Robins AFB, GA 31098-1670). Deficiencies and suggested improvements shall be submitted to the TMSS Pre-paring Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

5. Subsequent TO/Data Requirements (T). Offerors 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.

6. TO Development (T). The Offeror shall propose TO development practices and procedures that ensure TOs and data are compatible with the Truck, Tank, 6000 Gal. Fuel Servicing, A/S32R-11 Program objec-tives. In addition, TOs shall be written to a scope and depth of coverage sufficient to support the opera-tions 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. Sample AFTO Form 124 attached on page (10).

6.1 (T). 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-38784A 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. (See Graphics Format Rec-ommendations sheet attachment 1 to this document).

6.3(T). NA

6.4(T). NA

6.5(T). NA

7. TO Numbering (T). Offerors shall complete the TO Numbering Worksheet attachment 4, (page 13) to this document for each new MIL-STD-38784A manual being developed. TO numbers are not re-quired for manuals to be used exclusively by the Offerors own personnel. AF procedures for number-ing 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). Offerors shall propose Unlimited Rights for all source data and TOs prepared specif-ically for this contract.

8.1 If some TOs or source data are copyrighted or contain proprietary data or procedures, Offerors may propose Limited Rights or Government Purpose Rights (GPR) only. Proposed commercial

TM-86-01N 1 April 2009 3

Prepared by: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511 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). N/A

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices(T). Offeror shall place the following notices on the title pages of the MIL-SPEC manual(s) developed for this contract requirement. 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 up-on TO content.

DISTRIBUTION STATEMENT C - Distribution authorized to US Government agencies and their contractors for administrative or operational use (DATE TBD). Other requests for this document shall be referred to 406 SCMS/GUEE, Robins AFB, GA 31098-1813. Questions concern-ing technical content shall be directed to AFLCMC/WNZEBA, Robins AFB, GA 31098-1813.

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). The Offeror shall propose a quality assurance program which ensures TOs prepared are : a) 100% technically accurate; 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 IAW this contract. Recommended QA methods include actual per-formance of procedures and use of desk-top analysis for non-procedural data. The Offeror’s proposals shall describe how the government will be allowed to interact with the contractor’s TO development team.

10.1. Conferences and Technical Reviews(T). Offerors shall propose sufficient conferences and re-views to allow insight into TO development processes and ensure contract compliance. Offerors 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). Offerors shall propose their method for documenting certification that TO procedures are accurate, adequate, current, safe and usable for their intended purposes. Offerors shall notify the government at least 180 days prior of the need for any Government Furnished Infor-mation/Government Furnished Equipment (GFI/GFE) required to perform certification tasks.

10.3. Verification Support(T). Offerors 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: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511

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. Offerors shall propose methods for maintaining accuracy, cur-rency and configuration of TOs and source data throughout the contract period of performance. Mainte-nance includes preparation of TO and source data updates to incorporate corrections, equipment config-uration changes, and maintenance and operational concept changes.

12. TO Delivery(T). Offerors shall propose practices and procedures for secure access to or delivery of digital TO files, including those for Preliminary TOs (PTOs), source data, reproduction masters, and program support data. TO file delivery formats shall be according to applicable CDRLs and the tailored TM Delivery Requirements Matrices included in Section 2 of this document. EXCEPTION: For Com-mercial Manuals not available digitally.

12.1. SGML-Tagged Files. The contractor shall parse and compose SGML-tagged TO document 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 contractor 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. N/A

12.3. Interactive Electronic Technical Manuals (IETM(T). NA

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). The Offeror shall include Technical Order program events and schedules in their proposed Integrated Master Plan (IMP) and Integrated Master Schedule (IMS). Update the IMS throughout the period of performance of this contract. NOTE: AF policy requires delivery of verified TOs prior to or concurrently with delivery of operational equipment to the field (AFI 63-101, Ac-quisition and Sustainment Lifecycle Management). This policy will determine TO development and de-livery schedules throughout the acquisition phase of a program.

14. Time Compliance Technical Orders (TCTOs)(T). NA

15. TO Reproduction Management (T). N/A

16. Program Specific Requirements (T).

A. The Offeror shall develop and deliver new MIL-SPEC technical manuals covering the Intermediate Operating and Maintenance Instructions with separate Illustrated Parts Breakdown (IPB), and Depot Overhaul Instructions IAW Section 2, TO types (Table 1) page 7, in SGML format to support the Truck, Tank, 6000 Gal. Fuel Servicing, A/S32R-11 program’s objectives. These manuals shall cover the mounted equipment on the commercial chassis.

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 docu-ments and digital files.

C. The contractor shall provide Commercial Off The Shelf (COTS) manuals for the Intermediate Opera-tion and Maintenance of the vehicle if this coverage is not a part of the “Mitchell On Demand” system.

When required, the contractor shall evaluate each required commercial manual to determine if it meets the criteria set forth in the MIL-PRF-32216, prior to submitting the review copies for the Air Force ap-proval. If the manual(s) does not meet the criteria, the contractor shall prepare supplemental data to meet the requirements of MIL-PRF-32216 for content. Delivery requirements for the COTS manuals will be

TM-86-01N 1 April 2009 5

Prepared by: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511 digital IPDF files, IAW Section 2, Table 2, which are non-password protected and allow for the post-script decollation of the manual for printing.

D. SGML files shall be reviewed. The contractor shall submit copies of their SGML Instance, PDF file of their SGML Instance and separate graphics files for use with the SGML Instance for each In-Process review.

E. For Graphics formats, see “Graphics Format Recommendations” attachment 1to this document, (page 5). 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. In-Process reviews shall be held at the 35% and 70% completion point for each manual under devel-opment. Sample In-Process Completion table is provided on page (14).

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

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.

6 TM-86-01N 1 April 2009

Prepared by: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511

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

TM-86-01N 1 April 2009 7

Prepared by: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS MATRIX

NOTES:

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

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

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

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE

(Truck, Tank, 6000 Gal. Fuel Servicing, A/S32R-11) Program (System/Component)

Title or Type of Manuals Specification Required

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

a. Maintenance Manuals

(1) Intermediate Maintenance

(2) Depot Maintenance

(3) Combined (I&D) Maintenance

(4) On Condition Maintenance

b. Operation & Maintenance Instruction Manuals MIL-DTL-87929C

c. Illustrated Parts Breakdown (see notes) MIL-PRF-38807C MIL-PRF-38807C

2. Commercial Manuals (Evaluate according to MIL-PRF-32216) MIL-PRF-32216 http://dodssp.daps.dla.mil/assist.htm

8 TM-86-01N 1 April 2009

Prepared by: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

NOTES:

• Check all applicable boxes.

• For commercial manual supplemental data only, under the specification heading, enter “Same style and format,” “MIL-

PRF-38807” (for IPB data), or “MIL-STD-38784A.”

• For existing MIL-SPEC 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

Com-mercial Manual

Change/ Revision

Supple-ment

Supple-mental

TM

Source Data

1. Operation & Maint MIL-PRF- 32216

2. Overhaul MIL-PRF- 32216

3. Parts Manual MIL-PRF- 32216

4. Wiring Diagrams MIL-PRF- 32216

5 Troubleshooting MIL-PRF- 32216

TM-86-01N 1 April 2009 9

PART B - TM DELIVERY REQUIREMENTS

FOR TRUCK, TANK, 6000 GAL. FUEL SERVICING, A/S32R-11

TM DATA TYPE DELIVERED NEW MANUALS .

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(G/I) / 2 [Paper/IPDF and SGML / 2 copies]

NOTES:

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

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

DELIVERY SCHEDULE

Event Number of days data required prior to event Technical Review(s) (30 Days)

Verification

(30 Days)

Prepublication Review

(30 Days)

Final TO Delivery (90 Days) Prior to

Hardware Delivery

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

Mrs. Theresa A. Johnson Mil- Spec Manuals

406 SCMS/GUEE

235 Byron St., Suite 19A Robins AFB, GA 31098-1670

M(G/I) / 2 M(G/I) / 2 M(G/I) / 2 M(G/I) / 1

Mrs. Theresa A. Johnson Commercial Manuals

406 SCMS/GUEE

235 Byron St., Suite 19A Robins AFB, GA 31098-1670

M(I) / 1 M(I) / 1

Total Copies Required: 3 2 2 2

10 TM-86-01N 1 April 2009

AFTO FORM 124, 19970401 (IMT-V1) PREVIOUS EDITIONS ARE 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 11

Prepared by: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511

Attachment 2

Sample Government Purpose License Agreement

Contractor’s Letter Head Date

From: Company Name

To: 406 SCMS/GUEE 235 Byron St., Suite 19A Robins AFB, GA 31098-1670

Subject: Government Purpose License Agreement

NAME OF CONTRACTOR assigns to the U.S. Air Force under contract XXXXX-XX-X-XXXX, Gov-ernment Purpose License Rights, which allow the electronically store, use, printing, release and/or dis-closure of the technical data contained herein. These rights extend to U.S. governmental agencies only.

This data is not to be sold, disclosed or otherwise provided to any other entity/entities outside of the U.S.

Government. This license shall remain in effect for as long as the equipment cited in the technical man-ual remains in service and under government control and usage, after which this license is revoked.

Signed and dated by the contractor

12 TM-86-01N 1 April 2009

Attachment 3

PUBLICATION NUMBER

PUBLICATION DATE

IDENTIFYING TECHNICAL PUBLICATION SHEET

FOR COMMERCIAL MANUAL

(Supersedure note, or other special notes, if any)

1. PURPOSE: This technical publication is issued for the purpose of identifying and authorizing the following commercial manual for (Army)(Navy) (Marine Corps) (Air Force) (Defense Logistics Agency) (as appropriate) use.

MANUFACTURER: (Name and address)

PURCHASE ORDER OR CONTRACT NO.

REQUISITION NO. (if furnished by the contracting activity)

EQUIPMENT: (Type, model, part number, nomenclature, Federal Item Name, serial numbers.)

NATIONAL STOCK NUMBER (ff furnished by the contracting activity.)

TITLE: (Operating Instructions, Maintenance Instructions, Parts Lists, as appropriate)

ADDITIONAL IDENTIFICATION: (if any) Volumes, Parts, etc.

DATE: (if any)

2. ADDITIONAL COPIES: Additional copies are available from _______________ (Contracting activity will furnish information, but if no information is furnished, this paragraph will be omitted and the following paragraph moved up into its place.)

3. FILE LOCATION: The above described commercial manual is filed in _________________. (Each library will fill this in if this identifying technical publication sheet is filed separately from the commercial manual.)

4. AUTHORITY NOTICE, DISTRIBUTION STATEMENT, DISCLOSURE NOTICE (as applicable, in accordance with MIL-M-38784).

FOR UNCLASSIFIED MANUALS

NOTICE: Reproduction for non-military use of the information or illustrations contained in this publication is not permitted. The policy for military reproduction is established for the Army in AR 38-4, for the Navy and Marine Corps in OPNAVINST 5510.1, and for the Air Force in AFPD 34-1.

FOR CLASSIFIED MANUALS

NOTICE: This material contains information affecting the national defense of the United States within the meaning of the Espionage Laws, Title 18, U.S.C., Section 793 and 794, the transmission or revelation of which in any manner to an unauthorized person is prohibited by law.

TM-86-01N 1 April 2009 13

Attachment 4

REQUEST FOR TECHNICAL ORDER NUMBER

1. PRIME WEAPON’S SYSTEM (If Applicable)

2. CONTRACT NUMBER (If Applicable)

3. CONTRACT LINE ITEM NUMBER (CLIN):

4. PURCHASE REQUEST (PR) NUMBER:

5. MISSION DESIGN SERIES/ NOMENCLATURE (name of equipment):

6. PART NUMBER:

7. NATIONAL STOCK NUMBER (NSN): MMAC CODE:

7. CLASSIFICATION OF MANUAL: CLASSIFICATION OF TITLE:

8. EQUIPMENT MOTIVATION (electric, hydraulic, mechanical):

9. TYPE OF CURRENT, IF ELECTRIC (AC/DC/AC-DC): N/A

10. KIND OF MANUAL (Ops. & Maint. with IPB,): Ops. & Maint. with IPB, schematics and wiring Dia-grams manuals

11. KIND OF EQUIPMENT (air or ground):

12. COMMERCIAL OFF THE SHELF ITEM

13. SUGGESTED TECH ORDER NUMBER CONTRACT NUMBER:

14. MANUAL FORMAT SPECIFICATION NUMBER:

15. FOREIGN MILITARY SALES

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

17.. CONTRACTOR INFORMATION:

a. NAME OF VENDOR:

b. ADDRESS:

c. TELEPHONE:

d. MANUFACTURER'S CODE :

e. POINT OF CONTACT:

MAIL COMPLETED FORM TO:

ATTN: Mrs. Theresa A. Johnson

406 SCMS/GUEE

235 Byron St., Suite 19A Robins AFB, GA 31098-1670

EQUIPMENT SPECIALIST: Mr. Kenneth Bearden OFFICE SYMBOL: AFLCMC/WNZEBA, ES Phone: 478-222-1792 (Technical Order number assignment may require thirty days)

14 TM-86-01N 1 April 2009

Prepared by: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511

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

TM-86-01N 1 April 2009 15

Prepared by: Theresa A. Johnson 406 SCMS/GUEE (478)327-7511

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

NOTES:

• MIL-STD-38784A 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).

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. Photographs/half tones shall not be allowed in MIL-SPEC manuals. All artwork shall be accomplished in line art.

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

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-DTL-87929C, 1 February 2000

Detail Specification

Technical Manuals, Operation and Maintenance Instructions In Work Package Format

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

6.2d(6) Manual Sets are not applicable.

6.2d(7) Major Accessories not applicable.

6.2e Master List of Containers not applicable.

6.2j Specialized Manuals not applicable for the following sub paragraphs: 6.2j(1), (2), (3), (6), (8), (10), and (11).