Robins_TM-86-01N 1 .pdf

TM-86-01N 4 December 2009 1 Data Call GUEE-0039

Air Force Technical Manual Contract Requirements (TMCR) For

FUEL CONTROL TEST STAND

ATTACHMENT __________ TO CDRL SEQUENCE NUMBER A003, EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date: 18 FEBRUARY 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) have been tailored specifically, for the FUEL CONTROL TEST STAND Program Requirements. Proposals shall be compatible with the Air Force infrastructure and support the FUEL CONTROL TEST STAND Program. Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management. A copy is available upon request from the TO Manager. Any terms or procedures found in this document may be re-searched there.

2. TO Program Scope (T). The Offers shall develop and deliver a new AF technical manual (Operation and Maintenance Instructions with Illustrated Part Breakdown (IPB) and Calibration Manual to support the FUEL CONTROL TEST STAND (IAW) Section 2, Table 1. No tailoring shall be made to these requirements without prior approval of the TM Manager and Primary Contracting Officer (PCO).

3. Commercial Manuals(T). Commercial manuals shall not be used for this program.

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 mandatory requirements which are part of the Document Type Definition (DTD) structure.

4.1. (T). N/A.

4.2 (T). Questions concerning TMSS requirements may be resolved by written request and justified sugges-tions for resolution submitted through the Procuring Contracting Officer (PCO) and TO Manager. Deficien-cies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA). Approved rec-ommendations, corrections and clarifications will be maintained with contract documentation.

5. Subsequent TO/Data Requirements (T). Offers shall propose a process for notifying the government when additional TO or source data requirements are identified subsequent to contract award. This process shall re-quire government review and approval of recommended additional requirements prior to contractual approval.

Contractor format is acceptable.

6. TO Development (T). The Offers shall development practices and procedures that ensure TOs and data are compatible with the FUEL CONTROL TEST STAND program objectives. In addition, 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 3

6.1. Page-oriented Military Specification (MILSPEC) TOs shall be formatted with text, graphics and deliv-ery according to the TMSS specified in Section 2. The contractor shall develop TO files (tagged instanc-

es) using Standard Generalized Markup Language (SGML) according to the DTDs referenced in the

Prepared by Dwight McGhee/406 SCMS/GUEE (478)327-5294 / 18 FEBRUARY 2014

TM-86-01N 4 December 2009 2 Data Call GUEE-00139 appendix to MIL-STD-38784 and each applicable military detail or performance specification (MIL- DTL or MIL-PRF). All deliveries of SGML data shall be in a single file instance. Multiple file in-stances 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 de-veloping special TM illustration files whenever possible. (See Graphics Format Recommendations sheet attachment 1 to this document)

6.3. (T).N/A.

6.4. (T).N/A.

6.5. (T).N/A.

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

8. Data Rights (T). Offers shall propose Unlimited Rights for all source data and TOs prepared specifically for the contract. Government rights in data are specified in the Defense Federal Acquisition Regulation Supple-ment (DFARS), paragraphs 227-7102 through 227-7104, copies available from TO Manager upon request.

8.1 (T). NA

8.2 (T). NA

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

DISCLOSURE NOTICE - This information is furnished upon the condition that it will not be released to another nation without the specific authority of the Department of the Air Force of the United States, that it will be used for military purposes only, that individual or corporate rights originating in the infor-mation, 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, re-gardless of any other markings on the document, it will not be downgraded or Declassified without written approval of the originating United States agency.

DISTRIBUTION STATEMENT D - Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or operational use), (18 February 2014). Other requests shall be referred to 406 SCMS/GUEE, Robins AFB, GA 31098. Questions concerning technical content shall be directed to AFLCMC/WNAAA, Robins AFB, GA 31098.

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 penal-ties. 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). Offers shall propose a quality assurance program which ensures TOs are prepared IAW this contract. Recommended QA methods must include actual performance of procedures and use of desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be reserved for those proce-dures which would activate explosive devices or present a hazard to personnel or equipment. Offers’ 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). Offers shall propose sufficient conferences and reviews to allow insight into TO development processes and ensure contract compliance. Offeror shall participate in an initial Guidance Conference or Technical Interchange Meeting (TIM) within 60 days of contract award to ensure mutual understanding of TO contract requirements, schedules, points of contact, etc. Periodic In- Process Reviews (IPRs) and Prepublication Reviews (PPR) ensure TOs are being developed according to contract requirements and that open discrepancies are cleared prior to publication. NOTE: PPRs are re-

Prepared by Dwight McGhee/406 SCMS/GUEE (478)327-5294/ 18 FEBRUARY 2014

TM-86-01N 4 December 2009 3 quired for critical safety and nuclear surety procedures TOs, and may be required for other complex proce-dures TOs.

10.2. TO Certification. (T) The Offers shall deliver all 100% review copies with a letter certifying comple-tion and certification that the information has been reviewed by the contractor and is accurate.

10.3. Verification Support (T). Offers shall propose the methods, equipment and personnel required to support government TO Verification. This support should consist of at least engineering and technical pub-lications personnel available to resolve questions resulting from verification activities.

10.4. Technical Data Assessment (TDA – originally called First Article Testing) (T). The TO Manager, 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 concur-rent 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. 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, currency and configuration of TOs and source data throughout the contract period of performance. Maintenance includes preparation of TO and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes.

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

12.1. SGML-Tagged Files (T). 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 pro-vided 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 Requirements. A copy is available upon request from TO Manager.

13. Schedules. NOTE: AF policy requires delivery of verified TOs prior to or concurrently with delivery of operational equipment to the field (AFI 63-101, Acquisition and Sustainment Lifecycle Management).

This policy will determine TO development and delivery schedules throughout the acquisition phase of a pro-gram.

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

15. TO Reproduction Management(T). NA

16. Program Specific Requirements.

A. The Offers shall develop and deliver a new MIL-SPEC technical manual covering (Operation and Service Manual with Illustrated Part Breakdown (IPB) and a Calibration manual to support the FUEL CONTROL TEST STAND IAW Section 2, TO types (Table 1) in SGML format to support the FUEL CONTROL TEST STAND program’s objectives.

TM-86-01N 4 December 2009 4

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

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

D. For Graphics formats, see “Graphics Format Recommendations” attachment 1to this document. These recommendations provide wide latitude for developing and delivering graphics. The Contractor shall se-lect one method from these recommendations to prepare and deliver all graphics files. Graphic resolu-tion 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.

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

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

G. In-Process reviews shall be held at the 35% and 70% completion point for each manual under develop-ment. Sample In-Process Completion tables are provided on, Attachment 4.

H. 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 personnel 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 com-patible 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 4 December 2009 5

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

• All page-based TOs developed under this contract must conform to the general style and format requirements of MIL-STD-38784;

IETMs must conform to MIL-PRF-87268 and MIL-PRF-87269.

• 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

Program

Title or Type of Manuals Specification Required

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

a. Maintenance Manuals

(1) Intermediate Maintenance

(2) Depot Maintenance

(3) Combined (I&D) Maintenance

(4) On Condition Maintenance

b. Operation & Maintenance Instruction Manuals

c. With Illustrated Parts Breakdown (see notes)

2. Calibration Procedures MIL-PRF-38793

TM-86-01N 4 December 2009 6

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

NOT APPLICABLE

TM-86-01N 4 December 2009 7

PART B - TM DELIVERY REQUIREMENTS

FOR

(System/Item)

TM DATA TYPE DELIVERED NEW AF MANUAL.

(TMSS/Change/Supplement/etc.)

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.

N – Native Format X - Extensible Mark-up Language (XML)

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

NOTES:

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

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 Distribution (45 Days)

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

Attn: Dwight McGhee

406 SCMC/GUEE

235 BYRON ST., SUITE 19A

Robins AFB GA. 31098-1670

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

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

Total Copies Required: 2 2 2 1

TM-86-01N 4 December 2009 8

ATTACHMENT 1

Graphics Format Recommendations

GENERAL GUIDELINES

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

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

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

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

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

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

EPS:

• Raster based images will not be saved as EPS.

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

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

will be deleted from illustration prior to saving/exporting.

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

TIFF:

• B&W raster images should only be saved as Bitmap and not Grayscale, RGB or CMYK.

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

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

Group 4 compression when saving/exporting.

CGM:

• Raster based images will not be saved as CGM.

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

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

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

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

DWG:

• Raster based images will not be saved as DWG.

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

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

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

JPEG:

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

TIFFs due possible system compatibility issues.

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

TM-86-01N 4 December 2009 9

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-HDBK-1221)

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/GUEE

406 SCMS/GUEE 235 BYRON ST., Suite 19A ROBINS AFB, GA 31098-1670

(Technical Order number assignment may require thirty days.)

PROCUREMENT BUYER OFFICE SYMBOL: TELEPHONE EXT.:

EQUIPMENT SPECIALIST: OFFICE SYMBOL: ES PHONE:

TM-86-01N 4 December 2009 10

Attachment 3

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

COMPUTATION OF TECHNICAL ORDER READING GRADE LEVEL

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

3. T.O. DATE

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

5. READING GRADE LEVEL IAW MIL-STD-38784

6. COMPUTED OVERALL GRADE LEVEL OF T.O.

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

DERIVED RGL WHEN AVAILABLE.

SAMPLE NUMBER A

PAGE NUMBER OF

SAMPLE B

NUMBER OF WORDS

IN SAMPLE C

NUMBER OF

SENTENCES IN SAMPLE

D

NUMBER OF

SYLLABLES IN SAMPLE

E

SAMPLE GRADE LEVEL

F

9. PROJECT OFFICER GRADE OFFICE SYMBOL PHONE

10. SIGNATURE DATE

TM-86-01N 4 December 2009 11

ATTACHMENT 4

Sample Work Package Format IPR Completion Chart

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

35% 70%

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

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

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

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

TM-86-01N 4 December 2009 12

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

NOTES:

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

• Most specification “Acquisition Requirements” list the same two items for paragraphs 6.2a and 6.2b. For this contract enter:

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

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

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

Department of Defense

Standard Practice for Manuals, Technical:

General Style and Format Requirements

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

4.6.2 Photographs/line drawings. Delete paragraph.

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

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

Detail Specification

Technical Manuals, Operation and Maintenance Instructions In Work Package Format

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

6.2c(6) Manual Sets are not applicable.

6.2c(7) Major Accessories not applicable.

6.2d Master List of Containers not applicable.

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

Section 1. Technical Order (TO) Program Requirements