TM-86-01N_31aug2012_for_X008.pdf

TM-86-01N 1 April 2009 1 Data Call No: 409-0399CT

Prepared by: Deborah Miles 406 SCMS/GULAC (478) 222-0935

Air Force Technical Manual Contract Requirements (TMCR) For

SUSTAINMENT UPDATES -- TRUCK, AIRCRAFT CARGO LOADING/UNLOADING, 60,000

POUND CAPACITY TYPE A/S 32H-23, P/N 9032950-313/-315/-403/-407/-409/-411/-501/-

503, -505, and -507 NSN 3930-01-409-0339CT

(Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date: 31 August 2012

Technical Manual/Technical Order requirements contained herein have been cleared for use by OMB Paperwork Reduction Project No. 0704-0188.

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS

1. TMCR Tailoring (T). This TMCR document, including the associated tables, matrices and Specifica-tion/Standard Interface Records (SIRs) page 12, have been tailored specifically, for the Truck, Aircraft Cargo Loading/Unloading, 60,000 Pound Capacity Program Requirements. Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Or-der Life Cycle Management. A copy is available upon request from the TO Manager. Any terms or procedures found in this document may be researched there.

2. TO Program Scope (T). The TO types, source data and TO updates (Table 2) have been tailored to support the sustainment of the Truck, Aircraft Cargo Loading/Unloading, 60,000 Pound Capacity pro-gram’s objectives. All recommended tailoring shall be submitted through the Air Force PCO for consider-ation and/or approval/disapproval. No tailoring shall be made to these requirements without prior approv-al 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.

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/GULAC, 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

2 TM-86-01N 1 April 2009

Prepared by: Deborah Miles 406 SCMS/GULAC (478) 222-0935 process shall require government review and approval of recommended additional requirements prior to contractual approval. Contractor format is acceptable.

6. TO Development (T). N/A.

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.

6.2 (T). SGML-tagged TO files, developed under CLIN X007, shall be used for this effort and in-clude 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 illustra-tion files whenever possible. (See Graphics Format Recommendations sheet on page 7, Attach-ment 1.)

6.3 (T). N/A.

6.4 (T). N/A

6.5 (T). N/A

7. TO Numbering (T). N/A.

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.

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 C - Distribution authorized to U.S. Government Agencies and their contractors (Administrative or Operational Use) (xx XXX xxxx). Other request for this document shall be referred to 406 SCMS/GULAC, Robins AFB, GA 31098. Questions concerning technical content 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). Periodic In-Process Reviews (IPRs) ensure TOs are being developed according to contract requirements and that open discrepancies are cleared prior to publication. Offeror shall ensure all sustainment updates are provided at the 100% review level.

TM-86-01N 1 April 2009 3

Prepared by: Deborah Miles 406 SCMS/GULAC (478) 222-0935

10.2. TO Certification. N/A.

10.3. Verification Support (T). N/A.

10.4. Technical Data Assessment (TDA – originally called First Article Testing) (T). N/A.

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

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). 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 sustainment updates for MIL-SPEC technical manuals identified in Section 2, Table 2, to support the Truck, Aircraft Cargo Loading/Unloading, 60,000 Pound Capacity program’s objectives covering:

36M2-3-35-11: Operating Instructions (MIL-STD-38784)

36M2-3-35-11CL-1: Checklist (MIL-PRF-5096)

36M2-3-35-12: Maintenance Instruction Manual (MIL-DTL-87929)

36M2-3-35-14: Illustrated Parts Breakdown (IPB) (MIL-PRF-38807)

36M-3-35-xxx: Time Compliance Technical Orders (TCTOs) (MIL-DTL-38804)

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

16.3. For Graphics formats, see “Graphics Format Recommendations” Attachment 1 to this docu-ment (page 7). These recommendations provide wide latitude for developing and delivering graphics. The Contractor shall select one method from these recommendations to prepare and deliv-er all graphics files. Graphic resolution shall be a minimum of 300 DPI. Graphics files shall be de-livered as separate files regardless whether they are embedded in the documents or not. Digital pho-tographs (halftones) shall NOT be used. All graphics shall be line artwork.

4 TM-86-01N 1 April 2009

Prepared by: Deborah Miles 406 SCMS/GULAC (478) 222-0935

16.4. Conferences and Reviews:

a. In-Process reviews shall be held at the 100% completion point for each manual that is changed or revised.

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 two (4) trips to support these reviews.

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

c. Comments generated during ALL development reviews shall be incorporated before ac-ceptance of the final data.

16.5 Surge Capability. The contractor shall provide for a minimum of one urgent/emergency surge update not to exceed 50 pages per year to cover unforeseen urgent/emergency issues.

TM-86-01N 1 April 2009 5

Prepared by: Deborah Miles 406 SCMS/GULAC (478) 222-0935

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, AIRCRAFT CARGO LOADING/UNLOADING, 60,000 POUND

CAPACITY ) PROGRAM

(System/Component)

Title or Type of Manuals Specification Required

N/A

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

NOTES:

Check all applicable boxes.

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

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

For existing MIL-SPEC manuals not being updated to latest specification requirements, enter “Same style and format” under the specification heading.

TO Number, Title, or Type of Manual

Specification

Com-mercial Manual

Change/ Revision

Supple-ment

Supple-mental

TM

Source Data

1. 36M2-3-35-11 MIL-STD-38784A

2. 36M2-3-35-12 MIL-STD-38784A

3. 36M2-3-35-11CL-1 MIL-STD-38784A

4. 36M2-3-35-14 MIL-STD-38784A

MIL-PRF-38807

6 TM-86-01N 1 April 2009

Prepared by: Deborah Miles 406 SCMS/GULAC (478) 222-0935

PART B - TM DELIVERY REQUIREMENTS

FOR TRUCK, AIRCRAFT CARGO LOADING/UNLOADING, 60,000 POUND CAPACITY

(System/Item)

TM DATA TYPE DELIVERED SUSTAINMENT UPDATES .

(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: I / 2 [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 for development reviews

Technical Review(s) (30 Days)

Verification (30 Days)

Prepublication Review (30 Days)

Final TO Distribution (Annually)

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

406 SCMS/GULAC

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

I / 2 / / I/ 2

Total Copies Required: 2 2

TM-86-01N 1 April 2009 7

Prepared by: Deborah Miles 406 SCMS/GULAC (478) 222-0935

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.

8 TM-86-01N 1 April 2009

Prepared by: Deborah Miles 406 SCMS/GULAC (478) 222-0935

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