About this file

Air Force Technical Manual Contract Requirements To accompany CDRL X007

View the file

Other files for this federal contract opportunity

Other files attached to Request for Proposal (RFP) - Halvorsen Contractor Logistics Support (CLS) Aquisition, newest first.
File Type Posted
FA8519-13-R-30382-0003.pdf PDF
Atch_23_Halvorsen_Metrics_Determination_and_Incentive_Fee_Arrangement.pdf PDF
Q A_2.pdf PDF
Q A_1.pdf PDF
FA851913R30382______0002.pdf PDF
Attachment_25 _Contract_Work_Breakdown_Structure_Matrix.pdf PDF
FA8519-13-R-30382-0001.pdf PDF
Atch_28.docx DOCX document
HAL_CDRL_X00A.pdf PDF
Atch_24_Hal_Cross-Reference_Matrix.xlsx XLSX spreadsheet
QASP_OH_PBL.pdf PDF
AFMC_Form_158.pdf PDF
HAL_CDRL_X00B.pdf PDF
HAL_CDRL_X011.pdf PDF
HAL_CDRL_X005.pdf PDF
HAL_CDRL_X010.pdf PDF
Atch_27_GFE.docx DOCX document
Atch_33_Past_Performance_Questionnaire.docx DOCX document
HAL_CDRL_X014.pdf PDF
Appendix_C.pdf PDF
QASP_PES_PBL.pdf PDF
HAL_PES_PWS.pdf PDF
Atch_23_Halvorsen_Metrics_Determination_and_Incentive_Fee_Arrangement.pdf PDF
HAL_CDRL_X003.pdf PDF
FA851913R30382.pdf PDF
Atch_26_Hal_LaborCate_and_Matl_Add-on_r1.xlsx XLSX spreadsheet
Atch_29_-_CHPMSK-30_and_-90_Parts_Kits.xlsx XLSX spreadsheet
HAL_CDRL_X013.pdf PDF
Atch_25_Hal_CWBS_Matrix.pdf PDF
HAL_CDRL_X015.pdf PDF
HAL_OH_PWS.pdf PDF
HAL_CDRL_X007.pdf PDF
HAL_CDRL_X00E.pdf PDF
HAL_CDRL_X009.pdf PDF
HAL_OA_PWS.pdf PDF
Appendix_B.doc DOC document
QASP_MM_PBL.pdf PDF
HAL_CDRL_X00C.pdf PDF
Proposal_Adequacy_Checklist.doc DOC document
HAL_CDRL_X001.pdf PDF
Atch_31_Partner_Consent.doc DOC document
HAL_CDRL_X006.pdf PDF
HAL_CDRL_X00D.pdf PDF
Atch_30_Client_Authorization_Letter.doc DOC document
HAL_CDRL_X012.pdf PDF
HAL_MM_PWS.pdf PDF
Show all 46

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

TM-86-01N 1 April 2009 1 Data Call No: WNZEB-10-19

Prepared by: Deborah Miles 406 SCMS/GUEE (478) ) 926-0296

Air Force Technical Manual Contract Requirements (TMCR) For

TRUCK, HALVORSEN 25,000 POUND CAPACITY AIRCRAFT LOADER,

PART NUMBER 623-4300, NSN 3930-01-480-9519CT

(Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date: 5 November 2012

Updated 7 December 2012

Updated 5 March 2013

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), Section 3, have been tailored specifically, for the Truck, Hal-vorsen 25,000 Pound Capacity Aircraft Loader Program Requirements. Air Force TO Acquisition pro-cedures, 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 proce-dures found in this document may be researched there.

2. TO Program Scope (T). The TO types (Table 1) and source data, TO updates, commercial manuals, and TOs prepared to Non Government Standards (NGS) (Table 2) have been tailored to support the Truck, Halvorsen 25,000 Pound Capacity Aircraft Loader program’s objectives. All recommended tailoring shall be submitted through the Air Force PCO for consideration and/or approval/disapproval. No tailoring shall be made to these requirements without prior approval of the TM Manager and Procuring Contracting Officer (PCO).

3. Commercial Manuals (T). Offerors may propose the use of existing commercial manuals to the max-imum extent possible without impairing program support objectives. 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, Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data, as a guide for review and acceptance of all recommended commercial manuals. All commercial manuals shall be delivered with either unlimited data rights or as a minimum, Government Purpose License Rights (Sample provided on Attachment 3), to allow the AF to; electronically store, print, distribute and decollate the commercial manual to allow for postscript printing. All PDF 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 and to decollate the manual for postscript printing.

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. AF options in some Joint-Service TMSS have been documented in preliminary SIRs included in Section 3. These preliminary SIRs provide the starting point for further tailoring. Offerors may complete tailoring of the Joint-Service TMSS SIRs and provide recommended SIRs for other TMSS

2 TM-86-01N 1 April 2009

Prepared by: Deborah Miles 406 SCMS/GUEE (478) 926-0296 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 unmarked 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) and TO Man-ager (Deborah Miles, 406 SCMS/GUEE, 235 Byron St., Suite 19A, Robins AFB, GA 31098- 1670). 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). 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). TOs shall be written to a scope and depth of coverage sufficient to support the operations and maintenance concepts, and to the Reading Grade Level (RGL) specified in MIL-STD- 38784, Standard Practice for Manuals, Technical: General Style and Format Requirements. Sample AFTO Form 124, Attachment 4.

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

6.3 (T). N/A.

6.4 (T). N/A

6.5 (T). N/A

7. TO Numbering (T). Offerors shall complete the TO Numbering Worksheet Attachment 2, to this document for each new manuals being developed. TO numbers are not required for manuals to be used exclusively by the Offerors own personnel.

8. Data Rights (T). Offerors shall propose Unlimited Rights for all source data and TOs prepared spe-cifically 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, Offe-rors may propose Limited Rights or Government Purpose Rights (GPR) only. Proposed commercial 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). Offerors shall place the below statements on the title page of each new technical manual.

TM-86-01N 1 April 2009 3

Prepared by: Deborah Miles 406 SCMS/GUEE (478) ) 926-0296

DISCLOSURE NOTICE: This information is furnished upon the condition that it will not be released to another nation without the specific au-thority 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 writ-ten approval of the originating United States agency.

DISTRIBUTION STATEMENT B - Distribution authorized to U.S. Government Agencies only (Administrative and Operational Use) (xx XXX xxxx). Other request for this document shall be referred to 406 SCMS/GUEE, Robins AFB, GA 31098. Questions concerning technical con-tent shall be referred to AFLCMC/WNZDA.

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). Offerors’ quality assurance program shall ensure TOs prepared are: a) 100% tech-nically 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 limita-tion statements.

10.1. Conferences and Technical Reviews (T). Offerors shall participate in an initial Guidance Con-ference 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. Offerors shall submit a letter of certification for each new manual with the Verification Review Copies identified in Section 2, Part B, Delivery Matrix, for each manual. This certification shall certify that the 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 Information/Government Furnished Equipment (GFI/GFE) required to perform certification tasks.

10.3. Verification Support (T). Offerors shall provide support consisting of at least engineering and technical publications personnel available to resolve questions resulting from verification activities.

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 first submittal, for TDA to verify compliance of the digital files to Air Force DSSs. Additional TDAs may be required at future reviews. The TDA parsing in no way relieves the contractor from correcting tagging errors that are noted during the composing effort. Re-peat TDAs shall be required whenever new DSS or DTD versions are used for TO development. The contractor shall deliver the SGML files, Graphics Files, and the IPDF output from these files for initial review.

11. TO and Source Data Maintenance (T). N/A.

12. TO Delivery (T). TO file delivery formats shall be according to the tailored TM Delivery Require-ments 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 accom-

4 TM-86-01N 1 April 2009

Prepared by: Deborah Miles 406 SCMS/GUEE (478) 926-0296 plished 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 (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). 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). The Offeror shall propose practices and proce-dures to develop 3 AF TCTOs and related TO updates per year, when tasked from the Program Office.

Costs for TCTO package development must be included in the initial cost. Any additional TCTO (above 3) will be included in ECP Costs. NOTE: ECPs are reviewed and approved by the Program Of-fice. When the Program Office decides that a TCTO is the appropriate method of implementation, the contractor may be requested to develop the TCTO package for Air Force coordination and approval.

See TO 00-5-15, Air Force Time Compliance Technical order Process, for a detailed description of TCTO processes. A copy is available from TO Manager upon request.

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

16. Program Specific Requirements (T).

16.1. The Offeror shall develop and deliver new MIL-SPEC technical manuals in SGML, Work Package format to support the Operation & Maintenance of the Truck, Halvorsen 25,000 Pound Ca-pacity Aircraft Loader program’s objectives. Additionally, a separate IPB shall be developed in SGML format. Final delivered Technical Orders shall be delivered 18 Months after Contract Award.

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

16.3. 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 for initial In-Process review.

16.4. For Graphics formats, see “Graphics Format Recommendations” Attachment 1 to this docu-ment. 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 sepa-rate files regardless whether they are embedded in the documents or not. Digital photographs (half-tones) shall NOT be used. All graphics shall be line artwork.

16.5. Conferences and Reviews:

TM-86-01N 1 April 2009 5

Prepared by: Deborah Miles 406 SCMS/GUEE (478) ) 926-0296

a. In-Process reviews shall be held at the 35% and 70% completion point for each manual under development. Sample In-Process Completion tables are provided, Attachments 5 and 6.

b. All TO Conferences and Reviews shall be held at WR-ALC. Travel shall be the responsibil-ity of the contractor and shall be proposed for at least four (4) trips to support these reviews.

Additional trips may be required based upon the quality of the data delivered during each re-view.

16.6. Comments generated during ALL development reviews shall be incorporated before schedul-ing 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 personnel during the development reviews and Verification.

16.7 The Contractor shall provide separate commercial manuals along with OEM signed Govern-ment Purpose License Agreements for each of the items discussed in TO 36M2-3-45-11: Manufac-turer’s Data (MIL-PRF-32216). Each manual contained in this manual will be reviewed for curren-cy and a separate TO number will be assigned for each COTS item. Any manual deemed to be obso-lete, shall be replaced with the current version of the manual.

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: Deborah Miles 406 SCMS/GUEE (478) 926-0296

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

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.

All checklists, are developed IAW MIL-PRF-5096.

Delivery requirements are indicated in the TM Delivery Requirements matrices.

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE (TRUCK, HALVORSEN 25,000 POUND CAPACITY AIRCRAFT LOADER)

PROGRAM

(System/Component)

Title or Type of Manuals Specification Required

1. Operator Instructions MIL-STD-38784A

2. Operation and Maintenance Manual

Intermediate Maintenance MIL-DTL-87929

3. Illustrated Parts Breakdown (see notes) MIL-DTL-38807

4. Manufacturer’s Data

Intermediate Maintenance MIL-PRF-32216

5.Time Compliance Technical Orders (TCTOs when required) MIL-DTL-38804

6. Commercial Manuals MIL-PRF-32216

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-38784.”

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

N/A

TM-86-01N 1 April 2009 7

Prepared by: Deborah Miles 406 SCMS/GUEE (478) ) 926-0296

PART B - TM DELIVERY REQUIREMENTS

FOR TRUCK, HALVORSEN 25,000 POUND CAPACITY AIRCRAFT LOADER

(System/Item)

TM DATA TYPE DELIVERED NEW 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(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).

DELIVERY SCHEDULE

Event Number of days data required prior to event milestone.

Technical Review(s) (30 Days)

Verification (30 Days)

Prepublication Review (30 Days)

Final TO Distribution (90 Days)

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

406 SCMS/GUEE

Attn: Deborah Miles 235 Byron St., Suite 19A Robins AFB, GA 31098-1670

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

Total Copies Required: 2 2 2 1

NOTE: Only 1 paper copy with each delivery required. 2 digital copies required for development reviews through Prepublication review.

8 TM-86-01N 1 April 2009

Prepared by: Deborah Miles 406 SCMS/GUEE (478) 926-0296

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 available on hand and re-quest file types to match.

The 5 most common graphics file types are: EPS, TIFF, CGM, JPEG & DWG. Each is addressed 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 illustration prior to sav-ing/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 exported 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 illustration prior to sav-ing/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 sys-tem compatibility issues.

B&W Bitmaps should not be saved as JPEGs.

TM-86-01N 1 April 2009 9

Prepared by: Deborah Miles 406 SCMS/GUEE (478) ) 926-0296

Attachment 2

REQUEST FOR TECHNICAL ORDER NUMBER

1. PRIME WEAPON’S SYSTEM (If Applicable)

2. CONTRACT NUMBER: (If Applicable)

3. CONTRACT LINE ITEM NUMBER (CLIN) (If Applicable):

4. PURCHASE REQUEST (PR) NUMBER: (If applicable)

5. MISSION DESIGN SERIES/NOMENCLATURE (Name Of Equipment):

6. PART NUMBER(s):

7. NSN/FSN: MMAC CODE:

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

9. RECOMMENDED TILE OF MANUAL:

10. CLASSIFICATION OF MANUAL: CLASSIFICATION OF TITLE:

11. EQUIPMENT MOTIVATION (electric, hydraulic, mechanical) (If Applicable)

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

13. KIND OF MANUAL (Opn & Maint with IPB, Overhaul, etc.):

14. KIND OF EQUIPMENT (air or ground):

15. COMMERCIAL OFF THE SHELF ITEM YES NO

16. SUGGESTED TECHNICAL ORDER NUMBER:

17. MANUAL FORMAT SPECIFICATION NUMBER: (i.e., General Style & Format MIL-STD-38784 / Work Package

MIL-DTL-87929/Commercial Off The Shelf (COTS) MIL-PRF-32216)

18. CONTRACTOR INFORMATION: (If Applicable)

a. NAME OF VENDOR:

b. ADDRESS:

c. MANUFACTURER'S CODE:

d. POINT OF CONTACT:

19. 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/GULAC

235 Byron St., Suite 19A ROBINS AFB, GA 31098-1813

(Technical Order number assignment may require thirty days.)

PROCUREMENT BUYER OFFICE SYMBOL: TELEPHONE EXT.:

EQUIPMENT SPECIALIST: OFFICE SYMBOL: ES PHONE:

10 TM-86-01N 1 April 2009

Prepared by: Deborah Miles 406 SCMS/GUEE (478) 926-0296

Attachment 3

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

TM-86-01N 1 April 2009 11

Prepared by: Deborah Miles 406 SCMS/GUEE (478) ) 926-0296

Attachment 4

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

12 TM-86-01N 1 April 2009

Prepared by: Deborah Miles 406 SCMS/GUEE (478) 926-0296

ATTACHMENT 5

IPR Completion Percentage Guide General Style & Format Manuals

In-Process Review Level Percent Complete TO Section 35% 70% TO Title Page 100% - Front Matter - 75% Introduction 100% - General Information 50% 90% Installation Instructions 25% 70% Operation Instructions 25% 70% Theory of Operation 50% 100% Maintenance Instructions 25% 75% Checkout and Troubleshooting - 75% Circuit Diagrams/Illustrations 25% 75% Parts List 35% 80%

TM-86-01N 1 April 2009 13

Prepared by: Deborah Miles 406 SCMS/GUEE (478) ) 926-0296

ATTACHMENT 6

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 Procedures Schematic Diagrams Inspection Requirements Corrosion Prevention Instructions Initial Setup Instructions Fault Isolation Procedures Lubrication Instructions Disassembly Instructions Cleaning Instructions Post maintenance Operational Checkout Assembly Instructions

14 TM-86-01N 1 April 2009

Prepared by: Deborah Miles 406 SCMS/GUEE (478) 926-0296

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

NOTES:

All TMSS applicable to this contract shall have an appropriately tailored SIR attached to this section.

MIL-STD-38784 must be included in all contracts/proposals for AF TMSS-developed TOs.

Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from the DoD Single Stock Point (DODSSP), Acquisition Streamlining and Standardization Information System (ASSIST) web page, http://www.dodssp.daps.dla.mil/assist.htm.

TMSS entries designated with A, F, M or N refer to Army, Air Force, Marine Corps or Navy requirements.

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-38804D, 24 May 2012

Detail Specification -Time Compliance Technical Orders – Preparation

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

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

File details come from the government source that posted it. Updated .