B001.pdf

Brandi.Moody Typewritten Text B001

TM-86-01N 1 April 2009 1

Air Force Technical Manual Contract Requirements (TMCR) for

TTU-205 Test Set, NSN 4920-00-931-1457RN (Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date:24 February 2009

Updated 12 June 2009 to add Overhaul Manual

Updated 9 June 2011 to convert to TM-86-01N

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). Offerors may tailor this TMCR document, including the associated tables, ma-trices and Specification/Standard Interface Records (SIRs). The tailored TMCR shall be attached to the CDRL for TO delivery, and shall be included in the proposal as a separate exhibit, referenced in the pro-posal SOW/SOO/PD. Proposals shall support the TTU-205 Test Set, NSN 4920-00-931-1457RN pro-gram objectives.

2. TO Program Scope. The offeror shall develop and deliver a new AF technical manual (Operation and Maintenance Instructions with Illustrated Parts Breakdown (IPB) and a Depot Overhaul manual to support the TTU-205 Test Set program IAW Section 2, Table 1 of this document.

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 shall 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. 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). The offeror shall propose TO development practices and procedures that ensure TOs and data are compatible with the TTU-205 Test Set Program objectives. In addition, TOs shall be writ-ten to a scope and depth of coverage sufficient to support the operations and maintenance concepts, and

2 TM-86-01N 1 April 2009 to the Reading Grade Level (RGL) specified in MIL-STD-38784, Standard Practice for Manuals, Tech-nical: General Style and Format Requirements.

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-38784 and each applicable military detail or performance specification (MIL-DTL or MIL-PRF).

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.

6.3. Interactive Electronic Technical Manuals (IETMs)(T): N/A

6.4. N/A.

6.5. N/A

7. TO Numbering (T). Offerors shall complete the TO Numbering Worksheet attached to this docu-ment for each new manuals being developed.

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

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 ma-nuals 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). The offeror shall use the below statements for each TO developed.

DISTRIBUTION STATEMENT C - Distribution authorized to U.S. Government Agencies and their contractors (Administrative or Operational Use) (XX Month XXXX). Other requests for this document shall be referred to 406 SCMS/GULAC, Robins AFB, GA 31098. Questions concerning technical content shall be referred to WR-ALC/GRVCBA

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 are pre-pared 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 procedures which would activate explosive devices or present a hazard to personnel or equipment. Offerors’ 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). Offerors shall propose sufficient conferences and reviews to allow insight into TO development processes and ensure contract compliance. Offerors 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

TM-86-01N 1 April 2009 3 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 propose their method for documenting certification that 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 Infor-mation/Government Furnished Equipment (GFI/GFE) required to perform certification tasks.

10.3. Verification Support (T). Offerors shall propose the methods, equipment and personnel re-quired to support government TO Verification. This support should consist of at least engineering and technical publications personnel available to resolve questions resulting from verification activi-ties..

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 may be required based on initial results. Additional TDAs will be required at each succeeding review. The TDA parsing in no way relieves the contractor from correct-ing tagging errors that are noted during the composing effort. Repeat TDAs shall be required whenev-er 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, cur-rency and configuration of TOs and source data throughout the contract period of performance. Main-tenance includes preparation of TO and source data updates to incorporate corrections, equipment confi-guration changes, and maintenance and operational concept changes.

12. TO Delivery (T). Offeror shall propose delivery of digital TO files IAW Section 2, Part B, Delivery Matrix, contained herein.

12.1. SGML-Tagged Files (T). The contractor shall parse and compose SGML-tagged TO docu-ment files prior to delivery to the government, and verify that content tagging has been 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 corrected and returned 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. Copy available upon request from TO Manager. For questions concerning (IPDF) files contact Kimberly Slocum at (kimberly.slocum.ctr@robins.af.mil).

13. Schedules (T). Offerors shall include TO program events and schedules in their proposed Integrated Master Plan (IMP) and Integrated Master Schedule (IMS), and update the IMS throughout the period of performance. NOTE: AF policy requires delivery of verified TOs prior to or concurrently with deli-very of operational equipment to the field (AFI 63-101, Acquisition and Sustainment Lifecycle Man-agement). This policy will determine TO development and delivery schedules throughout the acquisi-tion phase of a program.

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

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

4 TM-86-01N 1 April 2009

16. Program Specific Requirements. The offeror shall develop and deliver a new AF technical manual (Operational and Maintenance Instructions with Illustrated Parts Breakdown (IPB) and a Depot Over-haul Manual (MIL-DTL-87929, work pack format)) to support the TTU-205 Test Set, NSN 4920009311457RN program. Data delivered for this contract shall be a mixture of both paper based documents during the development and both a paper copy and digital files in native formats for final de-livery.

a) SGML format is required for all new AF manuals. The details of the SGML effort shall be dis-cussed and refined during the TO Initial Guidance Conference.

b) Native format refers to graphics system used to develop the documents i.e., Autocad, Adobe Illu-strator etc. All Graphics files shall be delivered as either Group 4 compressed TIF format for raster graphics or, Encapsulated Postscript (EPS) or Autocad (DWG) for vector graphics.

Graphic resolution shall be a minimum of 600 DPI. Graphics files shall be delivered as separate files and linked to the documents by reference. Digital photographs (halftones) shall NOT be used. All graphics shall be line artwork.

c) The IPB shall require verification of the data based upon the production engineering drawings and provisioning documentation if provisioning is accomplished. The contractor shall plan for these events in their technical manual development schedule.

d) All electronic files delivered on this project shall be unprotected and allow unlimited access to change/modify/or capture the data from the files.

e) In-Process reviews shall be held at the 35% and 70% for the manual under development. Com-ments generated during ALL development reviews shall be incorporated before scheduling the next development review, for example 35% IPR comments shall be incorporated before schedul-ing the 70% IPR. The Contractor shall provide technical and engineering personnel to assist Air Force personnel during the development reviews and Verification if required.

f) Completion Percentage Guide –See below table for detailed breakout of completion require-ments.

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.

TM-86-01N 1 April 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.

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.

Delivery requirements are indicated in the TM Delivery Requirements matrices.

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE (TTU-205 Test Set, NSN 4920-00-931-1457RN) Program (System/Component)

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 W/IPB

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

6 TM-86-01N 1 April 2009

TABLE 2

ADDITIONAL TM TYPE SELECTIONS

NOT APPLICABLE

TM-86-01N 1 April 2009 7

PART B - TM DELIVERY REQUIREMENTS

FOR TTU-205 TEST SET, NSN 4920-00-931-1457RN

(System/Item)

TM DATA TYPE DELIVERED NEW MANUALS .

(TMSS/Change/Supplement/etc.)

(Replicate form for each TM type required.)

Delivery Format Requirements Codes

Digital delivery only:

P - Paper (draft or manuscript only. Cannot be used for G - Standard Generalized Mark-up Language (SGML).

final delivery) H - Hyper Text Mark-up Language (HTML) M - Mixed paper and digital (G, H or I) I - Indexed Portable Document Format (IPDF) File.

X - Extensible Mark-up Language (XML)

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

NOTES:

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

DELIVERY SCHEDULE

Event Number of days data required prior to event

Technical Review(s)( Days)

Verification ( Days)

Prepublication Review( Days)

Final TO Distribution( Days)

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

406 SCMS/GULAC

Attn: Kim Slocum 460 Richard Ray Blvd. Ste 200 Robins AFB, GA 31098-1813

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

Total Copies Required: 2 2 2 1

8 TM-86-01N 1 April 2009

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

460 Richard Ray Blvd. Suite 200 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:

TM-86-01N 1 April 2009 9

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

Work Package

Title Work Package

Number 35%

Percent Complete 75%

Percent Complete Title Page 100% 100%

Alphabetical Index 001 00 100% 100% Forward 002 00 100% 75%

Master List of Special Tools, Test Equipment, and Consumables

003 00 100% 75%

Technical Work Pack-ages

004 00 through 997 00

At least 1 com-plete and 35 % completion of the remaining WPs

75% At least 2 or more technical work packages complete and the remaining work packages must have the front matter for the technical work package and 75% of the information.

Illustrated Parts Breakdown

998 00 35% 80%

TM-86-01N 1 April 2009 11

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

NOTES:

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

SPECIFICATION/STANDARD INTERFACE RECORD FOR MIL-STD-38784, 2 July 1995 Notice 1, 15 November 2000 Notice 2, 1 December 2000

Standard Practice for Manuals, Technical: General Style and Format Requirements

Global: Change references to “MIL-STD-1806” to read “DODD 5230.24.”

3.2.8 Continuous Tone Artwork. Delete paragraph.

3.2.9 Copy Freeze Date. Delete paragraph.

3.2.10 Cutline. Delete paragraph.

3.2.20 Layout Page. Delete paragraph.

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

4.2.1.2.1 Oversize Reproducible Copy. Delete paragraph.

4.2.7.1 Table Cutline (see 3.2.10). Delete paragraph.

4.2.8.1 Illustration Cutline (see 3.2.10). Delete paragraph.

4.2.8.3 Amend as follows: “4.2.8.3 Illustration legends (see 3.2.23). Legends shall be headed by the word “Le-gend” followed by the number of the figure to which it is applicable (see Figure 6). The entire legend shall be indented 5 spaces. If the legend is continued, the figure number and title shall be repeated, followed by a dash and the word “Continued.” Only that information which is necessary to clearly identify the items shall be included in the legend. Where methods such as the tabular presentation technique (as in an Illu-strated Parts Breakdown/Repair Parts and Special Tools List) are used, no legends are required.”

NOTE: The <figtable> element, if included in the DTD, shall not be used in maintenance manuals.

* 4.5.1.10 Disclosure Notice. Change 1st sentence to read: “…except those with Distribution Statement A, IAW AFI 21-303 (F):”

* 4.5.1.11 Distribution Statement. Replace the last sentence with: “Include both the distribution statement letter (“A,” “B,” etc.) and wording from DODD 5230.24. Include the “Reason,” “Controlling DoD office,” and “Date of Determination” when required. If the reason is “Proprietary Data,” then each TM page containing pro-prietary data must be marked with the company name and the word “Proprietary” (e.g., “Boeing Proprie-tary”).”

4.5.1.13 Destruction Notice. Change the existing sentence to read: "...or X shall be marked with Handling and De-struction Notice "a" (below) on the cover/title..." Add a new second sentence as follows: "Unclassified TOs authorized for Public Release (Distribution Statement "A") shall be marked with disposition notice "b" (be-low) on the title or T-2 page."

4.5.1.13.a. Designate existing paragraph as "a. HANDLING AND DESTRUCTION NOTICE..."

Add: "See TO 00-5-1 for specific destruction procedures."

4.5.1.13.b (Added) b. “DISPOSITION NOTICE - Refer to TO 00-5-1 for disposition instructions.”

* 4.5.1.14 Copyright Credit Line. Add “If a copyright credit line is required, include a statement of government rights to publish, reproduce, and distribute the TM.”

4.5.3 List of Effective Pages. Change the first sentence to read: “A List of Effective Pages shall be prepared in ac-cordance with Figure 13. Page borders shall be optional.”

4.6.2 Photographs/line drawings. Delete paragraph.

4.6.3.1 Retouching. Delete paragraph.

4.6.3.2 Prescreened photographs. Delete paragraph.

12 TM-86-01N 1 April 2009

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

4.6.5 Combination Artwork. Delete paragraph.

4.6.12 Color in Illustrations. Delete the first sentence: “Unless otherwise specified (see 6.2), color shall not be used.”

4.6.12.1 Separation of Colors. Delete paragraph.

4.6.12.2 Register Marks. Delete paragraph.

4.6.20 Crop and Size Marks. Delete.

4.6.21 Mounting of Artwork. Delete paragraph.

4.6.22 Identifying Artwork. Delete paragraph.

4.6.23 Covering of Artwork. Delete paragraph.

4.6.24 Review of Illustrations. Delete paragraph.

4.7.1 Advanced Change Pages. Delete paragraph.

4.7.2 Changes to Cover and Title Page. In the first sentence, delete the phrase “Except for silk screened or otherwise expensive covers”.

4.7.3.4 Transmittal Cover Sheets. In the last sentence, delete the phrase “i.e. reproducible copy, negatives, magnetic tape, disk, etc.”.

4.7.3.5 Changes to Illustrations. Delete paragraph.

4.9.2 Safety Supplements (see Figure 37). Change first sentence to read: Safety supplement “SS” borders and the words “SAFETY SUPPLEMENT” at the top and bottom of the supplement shall be in red. Other text, letter-ing, numbering, etc, shall be in black.”

Figure 5, Example Typical RDC Page. Delete.

Figure 25 Cropping and Sizing of Illustrations. Delete.

Figure 26, Identification, Marking, and Protective Covering of Artwork. Delete.