CDRLs.pdf

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

Prepared by David Gilbert AFLCMC/WNYC DSN 472-4614

Air Force Technical Manual Contract Requirements (TMCR) for

(AN/ALQ-172 LRU-4 REDESIGN)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT: FD 2060-15-00019

Date: 28 OCTOBER 2014

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) has been tailored specifically, for the (AN/ALQ-172 LRU-4 REDESIGN) Program Requirements. Program shall be compatible with the Air Force infrastructure and support the (AN/ALQ-172 LRU-4 REDESIGN) Program. Air Force TO Acquisition procedures, in-cluding procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management.

2. TO Program Scope. The TO types (Table 1) and source data, TO updates, commercial manuals, and TOs prepared to Non- Government Standards (NGS) (Table 2) required to support the (AN/ALQ-172 LRU-4 REDESIGN) 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 require-ments 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. (T) N/A.

4.1. (T) N/A.

4.2 (T). N/A.

5. Subsequent TO/Data Requirements (T). Offerors shall notify the government when additional TO or source data requirements are identified following to contract award. This process shall require govern-ment review and approval of recommended additional requirements prior to contractual approval. Con-tractor format is acceptable.

6. TO Development (T). The preferred method is to use the TMSS specified in Section 2, Table 1 to pro-duce TO files (instances) tagged using Standard Generalized Markup Language (SGML) according to the DTDs referenced in the appendix to MIL-STD-38784 and each applicable detail or performance specifica-tion.

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-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 in-stance. 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 Recom-mendations sheet attachment 1 to this document) for approved file formats.

2 TM-86-01N 1 April 2009

Prepared By David Gilbert AFLCMC/WNYC DSN 472-4614

6.3. (T) The TO Manager, will determine the first article testing (FAT) requirements for each TO type. The contractor will submit required sample files to the TO Manager, who will then conduct first article testing to ensure the AF standards requirements are met. Repeat FAT evaluations when-ever new DSS or DTD versions are used for TO development.

6.4. (T) N/A.

6.5. (T) N/A.

7. TO Numbering (T). Offerors shall complete and submit a Request for TO Number Worksheet at-tached to this TMCR for each new TO Number required for the program. These requests shall be sub-mitted to the following address ATTN: (To Manager Name):

AFLCMC/WNYC

265 Byron St.,Suite 19A

Robins AFB, GA 31098-1813

8. Data Rights (T). Offerors shall provide Unlimited Rights for all source data and TOs prepared spe-cifically for the contract.

8.1. (T) N/A.

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.

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 De-partment 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 con-tractors only (Reason) (Date Month Year). Other requests for this document shall be referred to 406 SCMS/GUEE, Robins AFB, GA 31098. Questions concerning technical con-tent shall be referred to AFLCMC/XXX.

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 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. Offerors’ proposals should describe how the government will be al-lowed to interact with the contractor’s TO development team.

10.1. Conferences and Technical Reviews (T). Offerors shall participate in an initial Guidance Confer-ence or Technical Interchange Meeting (TIM) within 60 days of contract award to ensure mutual under-standing 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 re-quirements and that open discrepancies are cleared prior to publication.

10.2. TO Certification. Offerors shall submit a letter of certification for each new manual with the Ver-ification Review Copies identified in Section 2, Part B, Delivery Matrix, for each manual. This certifi-

TM-86-01N 1 April 2009 3

Prepared by David Gilbert AFLCMC/WNYC DSN 472-4614 cation shall certify that the TO procedures are accurate, adequate, current, safe and usable for their in-tended purposes. Offerors shall notify the government at least 180 days prior of the need for any Gov-ernment Furnished Information/Government Furnished Equipment (GFI/GFE) required to perform certi-fication 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 pro-gram office concurrent with each IPR, for TDA to verify compliance of the digital files to Air Force DSSs. Additional TDAs may be required at each succeeding review. The TDA parsing in no way re-lieves 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 or when errors and discrepancies are noted during the initial TDA. 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. (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, perform completeness checks and com-pose 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 ac-ceptance shall be returned to the contractor for correction then returned to the Air Force for addition-al testing to the Government.

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

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

12.4. Indexed Adobe™ Portable Document Format (IPDF) Files (T). N/A.

13. Schedules (T). N/A

14. Time Compliance Technical Orders (TCTOs) (T). Offerors shall develop AF TCTOs and related TO updates when tasked as part of this contract in Section 2, Table 1 of the TMCR. The contractor shall prepare TCTO packages including the required forms for Air Force coordination and approval as de-scribed in the following directives. See TO 00-5-15, AFMCI 21-302 and AFMCMAN 21-1 (available under the links to “Digital Technical Orders” and “Publications” at http://www.ide.wpafb.af.mil/toprac/to-syste.htm) for a detailed description of the TCTO system..

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

16. Program Specific Requirements.

A. The Offeror shall develop and deliver new MIL-SPEC technical manuals covering the Operating In-structions, Service or Maintenance Manual, Illustrated Parts Breakdown (IPB), Inspection Requirement Manual, and Work Unit Code Manual IAW Section 2, TO types (Table 1) in SGML format to support the (AN/ALQ-172 LRU-4 REDESIGN) program’s objectives. All final deliveries shall consist of the a merged basic document in paper PDF format and all native files used to develop the manual(s). The manual(s) shall be developed using the latest version of the development specifications listed in Table 1

4 TM-86-01N 1 April 2009

Prepared By David Gilbert AFLCMC/WNYC DSN 472-4614 of this document. Data delivered for this contract shall be a combination of paper based documents and digital files.

C. The Offerors shall develop and deliver updates in the form of Redline change pages for the (ALQ- 172 LRU-4) TOs listed in Section 2, Table 2. All final deliveries shall consist of the individual changes and a merged basic document through the newest change in paper and PDF format. The Offeror shall also develop and deliver TCTOs when required in accordance with Section 2, Table 1 for all modifica-tions to hardware and software items affecting “Form, Fit, or Function”.

D. SGML files shall be reviewed by the Air Force during the development process to ensure compli-ance with the approved DTDs. The contractor shall submit copies of their SGML Instance, PDF file of their SGML Instance and separate graphics files use with the SGML Instance for each In-Process re-view.

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 600 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 tables are provided on pages (17 & 18), Attachments 6 & 7.

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.

TM-86-01N 1 April 2009 5

Prepared by David Gilbert AFLCMC/WNYC DSN 472-4614

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 (ALQ-172 LRU-4 REDESIGN) Program (System/Component)

Title or Type of Manuals Specification Required

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

2. Illustrated Parts Breakdown MIL-PRF-38807

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

a. Maintenance Manuals

(1) Intermediate Maintenance

(2) Depot Maintenance

6 TM-86-01N 1 April 2009

Prepared By David Gilbert AFLCMC/WNYC DSN 472-4614

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

1. 12P3-2ALQ172-44

Same/Style Format

2. 12P3-2ALQ172-48-1

3. 12P3-2ALQ172-218-1

4. 12P3-2ALQ172-42

5. 12P3-2ALQ172-42-1

6. 12P3-2ALQ172-2 Same/Style

7. 12P3-2ALQ172-2-1

8. 12P3-2ALQ172-2-2

9. 12P3-2ALQ172-8-1

10. 12P3-2ALQ172-8-3 Same/Style

11. 33D7-13-227-1 Same/Style

12. 33D7-13-227-1-1 Same/Style

13. 33D7-13-227-4

14. 12P3-2ALQ172-3 Same/Style

TM-86-01N 1 April 2009 7

Prepared by David Gilbert AFLCMC/WNYC DSN 472-4614

TO Number, Title, or Type of Manual

Specification

Com-mercial Manual

Change/ Revision

Supple-ment

Supple-mental

TM

Source Data

15. 1C-130(M)-4 Same/Style

16. 1C-130(M)E-4

17. 1C-130(A)H-4 Same/Style

18. 1C-130(A)H-4-2 Same/Style

19. 33D7-38-215-1 Same/Style

20. 33D7-38-215-8-1

21. 33D7-50-1-288-1

8 TM-86-01N 1 April 2009

Prepared By David Gilbert AFLCMC/WNYC DSN 472-4614

PART B - TM DELIVERY REQUIREMENTS

FOR ALQ-172 LRU-4 REDESIGN

(System/Item)

TM DATA TYPE DELIVERED SGML/REDLINES .

(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) / 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

Event Number of days data required prior to event

Technical Review(s) (45 Days)

Verification (45 Days)

Prepublication Review(45 Days)

Final TO Distribution (60 Days)

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

406 SCMS/GUEE

235 BYRON ST.SUITE 19A

ROBINS AFB GA 31098-1813

P/I / 2 P/I/ 2 P/I/ 2 M/P/G/I/ 2

AFLCMC/WIUEG

235 BYRON ST. SUITE 19A

ROBINS AFB GA 31098-1813

P/I / 2 P/I/ 2 P/I/ 2 M/P/G/I/ 2

Total Copies Required: 4 4 4 4

TM-86-01N 1 April 2009 9

Prepared by David Gilbert AFLCMC/WNYC DSN 472-4614

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.

10 TM-86-01N 1 April 2009

Prepared By David Gilbert AFLCMC/WNYC DSN 472-4614

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: _______________________________* AN/ALQ-172 LRU-4 REDESIGN:

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

EQUIPMENT SPECIALIST: ______________________ OFFICE SYMBOL: _________ ES PHONE:

* = Mandatory Fields

TM-86-01N 1 April 2009 11

MIL-PRF-32216

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.

12 TM-86-01N 1 April 2009

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

TM-86-01N 1 April 2009 13

ATTACHMENT 6

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%

14 TM-86-01N 1 April 2009

Prepared By David Gilbert AFLCMC/WNYC DSN 472-4614

ATTACHMENT 7

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

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.

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. Delete paragraph.

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

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-DTL-38804D, 20 May 2012

Time Compliance Technical Orders – Preparation

NOTE: Entries marked with an asterisk (*) will have to be manually entered and tagged in SGML files until the specification and its associated DTD and FOSI have been updated to incorporate the changes. The rescission date and statement will continue to appear in paragraph 3 of SGML-tagged TCTO files until the DTD and FOSI are updated.

16 TM-86-01N 1 April 2009

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.

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

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.2f Manual will be in Work Package format (paragraph 3.2.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).

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-STD-3048 (USAF), 24 July 2013

Department of Defense

Standard Practice Air Force Business Rules for the Implementation of S1000D

6.2a. Title, number, and date of this standard.

6.2b. Title, number, and date of S1000D.

6.2c. Completed functionality matrix.

6.2d. Project specific business rules (see Appendix A).

C