C001_TMCR.pdf

C001

SOW 3.3.1

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

Prepared by Carol Coleman/406 SCMS/GUEE/(478) 327-4907

Air Force Technical Manual Contract Requirements (TMCR) For

TANKS, COLLAPSIBLE,

10,000, 50,000 & 210,000 U.S. GALLONS,

FUEL,

5430-01-511-2125RN (10K)

5430-01-517-8580RN (50K)

5430-01-511-4293RN (210K)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date: 25 February 2014

Updated 12 May 1014

Updated 24 July 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 TANKS, COLLAPSIBLE

Program Requirements. Proposals shall be compatible with the Air Force infrastructure and support the

TANKS, COLLAPSIBLE 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.

2. TO Program Scope(T). Offeror shall develop and deliver 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 TANKS, COLLAPSIBLE program’s objectives. All recommended tailoring shall be sub-mitted 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 Primary Contracting Officer

(PCO).

3. Commercial Manuals (T). N/A

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between options offered in paragraph 6.2 of each TMSS. The tailoring is recorded in SIRs and added to

Section 3 of this document for each TMSS required. NOTE: Tailoring must not change or delete man-datory requirements which are part of the Document Type Definition (DTD) structure.

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

2 TM-86-01N 1 April 2009

Prepared by Carol Coleman/406 SCMS/GULAC/(478) 327-4907

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. 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 attached, Attachment 3.

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 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. N/A

6.4. N/A

6.5. N/A

7. TO Numbering (T). Offerors shall complete the TO Numbering Worksheet attachment , Attachment

2, to this document for each new manual 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. 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 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. 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.

DISTRIBUTION STATEMENT C – Distribution authorized to U.S. Government Agencies and their contractors (Administration or Operational Use) (25 February 2014). Offer requests for this document shall be referred to 406 SCMS/GUEE, Robins AFB, 31098. Questions concerning technical content shall be referred to AFLCMC/WNZEC.

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

TM-86-01N 1 April 2009 3

Prepared by Carol Coleman/406 SCMS/GUEE/(478) 327-4907 operations and maintenance concepts, and C) properly classified and marked with export control and distribution limitation 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 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. 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 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 correc-tion 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). N/A

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

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

16. Program Specific Requirements.

4 TM-86-01N 1 April 2009

Prepared by Carol Coleman/406 SCMS/GULAC/(478) 327-4907

A. The Offeror shall develop and deliver a new MIL-SPEC technical manual in work package format combining the Operating and Maintenance with Illustrated Parts Breakdown (IPB), IAW Section 2, TO types (Table 1) in SGML format to support the TANKS, COLLAPSIBLE program’s objectives.

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. 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 use with the SGML Instance for each In-Process review.

D. For Graphics formats, see “Graphics Format Recommendations” attachment 1 to this document, (page 7). 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.

E. In-Process reviews shall be held at the 35% and 70% completion point for each manual under devel-opment. Additional reviews will be required at the verification level and a pre-publication review. Sam-ple In-Process Completion table provided on, Attachment 4 to this document.

F. 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 Carol Coleman/406 SCMS/GUEE/(478) 327-4907

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 (TANKS, COLLAPSIBLE) Program

(System/Component)

Title or Type of Manuals Specification Required

1. Operation and Maintenance Instructions in Work Package Format

MIL-DTL-87929

a. Combined Operation & Maintenance Instruction Manual MIL-DTL-87929

b. with Illustrated Parts Breakdown (see notes) MIL-PRF-38807

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

N/A http://dodssp.daps.dla.mil/assist.htm

6 TM-86-01N 1 April 2009

Prepared by Carol Coleman/406 SCMS/GULAC/(478) 327-4907

PART B - TM DELIVERY REQUIREMENTS

FOR TANKS, COLLAPSIBLE

(System/Item)

TM DATA TYPE DELIVERED NEW MANUAL .

(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

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

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

Total Copies Required: 2 2 2 1

TM-86-01N 1 April 2009 7

Prepared by Carol Coleman/406 SCMS/GUEE/(478) 327-4907

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.

8 TM-86-01N 1 April 2009

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/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 1 April 2009 9

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

10 TM-86-01N 1 April 2009

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 1 April 2009 11

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

NOTES:

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

SIRs included in the untailored TMCR format represent the minimum tailoring requirements that must be includ-ed in the final contract, unless the entire SIR is not applicable; e.g., if MIL-DTL-22202D is not required, the en-tire SIR can be deleted.

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

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

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