TM-86-01P_MHU196_(v1)_00.pdf

TM-86-01P 9 DEC 2014

DATA CALL GUEE-16-005 1

Prepared by James Brown/406 SCMS/GUEE/(478) 222-0934

Air Force Technical Manual Contract Requirements (TMCR) for

MHU-196

ENGAGEMENT FORCE & USER EVALUATION

FEEDBACK IMPLEMENTATIONS

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date: 4 February 2016 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 has been tailored by the program office, including the associated tables, matrices and Specification/Standard Interface Records (SIRs). The Contractor may recommend and submit, in writing additional tailoring to the TO Manager Agency/Agent (TOMA) and Procuring Contracting Officer (PCO) for consideration. 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 proposal SOW.

2. TO Program Scope (T). The Contractor may recommend additional Section 2 tailoring to the list of new TO types (Table 1) and source data and TO updates (Table 2) required to support the MHU-196 Engagement force & user evaluation feedback implementations program’s objectives.

3. Commercial Manuals (T). N/A

3.1. (T) N/A

3.2. (T) N/A

3.3. (T) N/A

4. Technical Manual Specifications and Standards (TMSS) Tailoring (T). N/A

4.1. (T) N/A

4.2. Questions concerning TMSS requirements may be resolved by written request and justified sug-gestions for resolution submitted through the Procuring Contracting Officer (PCO) and TO Manager, James Brown (406 SCMS/GUEE, 235 Byron Street, Ste. 19A, Robins AFB, GA 31098-1670, Phone

(478) 222-0934). Deficiencies and suggested improvements shall be submitted to the TMSS Prepar-ing Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

5. Subsequent TO/Data Requirements. When new TO requirements are identified the Contractor shall notify the government utilizing DI-TMSS-80067B, Technical Manual (TM) Contractor Furnished Aer-onautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, or approved contractor formats. This process shall require government review and approval of recommended additional re-quirements prior to developing additional data.

2 TM-86-01P 9 Dec 14

DATA CALL GUEE-16-005

Prepared by James Brown/406 SCMS/GUEE/(478) 222-0934

6. TO Development (T). Source Data shall be written to a scope and depth of coverage sufficient to sup-port the MHU-196 operations and maintenance concepts.

6.1. (T). N/A

6.2 (T). All delivered graphics shall conform to the approved graphic creation and format guidelines listed in attachment 1.

6.3 (T). Source data shall be formatted with text/graphics and delivered according to the require-ments in paragraph 16 and as specified in Section 2.

7. TO Numbering (T). N/A

8. Data Rights. Contractors shall provide Unlimited Rights for all source data and TOs prepared specif-ically for the contract. Government rights in data are specified in the Defense Federal Acquisition Regu-lation Supplement (DFARS), 252.227-7013, Rights in Technical Data, Noncommercial Items, 252.227- 7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documen-tation, and 252.227-7015, Technical Data-Commercial Items. The government shall be given unlimited rights for all business rules (tailoring and application methods and procedures) and documented business processes developed for use in TO development. Government data rights shall extend to the common source database, transformation style sheets, and other tools or products used to author or display tech-nical data.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices (T). N/A

10. TO Quality (T). The contractors’ shall ensure TOs prepared are: a) technically accurate and safe;

b) written to a scope and depth of coverage sufficient to support the operations and maintenance con-cepts, and c) properly classified and marked with export control and distribution limitation statements.

10.1(T) The contractor shall maintain a Technical Manual Quality Assurance Program (TMQAP) plan for this effort. The TMQAP shall be available for review at the TO Guidance Conference. The TMQAP shall be sufficiently detailed to support TO certification to include actual performance of procedures or 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.

10.2. Guidance Conference (T). Working through the TOMA, the contractor shall co-host and par-ticipate in an Initial TO Guidance Conference for this effort to be held within 60 calendar days after award of contract. The Technical Order Status and Schedule (TOSS) will be formalized at this con-ference. The contractor shall present a briefing on their interpretation of the basic contract, SOW, CDRLs, Data Item Descriptions (DIDs), MIL-SPEC, MIL-STD, SIRs, this document and the planned preparation and delivery of the TOs and related data.

10.3. In-Process Reviews (T). The contractor shall participate and/or co-chair In-Process Reviews of the data developed for this effort. In-Process Reviews may be requested by the TOMA or by the contractor to ensure that data being developed as part of this effort is adequate and accurate and IAW contract requirements and cited specifications. The contractor shall support IPRs with the technical writers, engineers and QA personnel as required or needed. IPRs will be held in accord-ance with TO 00-5-3 or as defined by the program office. During the IPRs the contractor will be re-sponsible to maintain a master markup of the document being reviewed. This master markup will be made available at the next scheduled review. A copy of the markup will be provided to the TOMA

DATA CALL GUEE-16-005 3

or designated individual at the conclusion of the review. The contractor shall ensure all comments from previous IPR’s have been incorporated prior to next scheduled IPR.

10.4 (T). TO Delivery Requirements for In-Process Reviews. IPR TO data shall be technically ed-ited and reviewed according to the TMQAP. Manuscript (handwritten) data is not acceptable for any data to be reviewed. The TMQAP checklists shall be available for review by the government during the IPRs.

10.5. TO Certification. The contractor shall certify that source data developed to support the pro-gram are accurate, adequate, current, and usable for their intended purpose. The Government may witness the certification activities. The contractor shall incorporate comments generated by the certi-fication process into the TOs prior to submitting the TOs for verification. At the completion of the certification, the contractor shall submit a letter to the TOMA stating that certification has been completed and that any deficiencies identified during the process have been corrected. The contrac-tor will ensure all necessary changes and corrections to affected manuals are accomplished in time to meet contract delivery schedule requirements. The contractor shall notify the government at least 180 days prior to the need date of any Government Furnished Information/Government Furnished Equipment (GFI/GFE) required to perform certification tasks. Technical order 00-5-1 and 00-5-3 shall be referenced for additional information on TO Certification requirements.

10.6. Verification Support. The contractor shall support USAF verification activities as required by the TOMA and the program Verification Plan. Contractor verification support will consist of on sta-tion technical writing or engineering support and maintain a master mark-up of the document and record minute items during the Air Force verification process. The contractor shall also support all post verification reviews.

10.5.1. Verification of IETMs. NA

10.7. TO Prepublication Reviews (PPR). PPRs are examinations of TOs to ensure incorporation of agreed upon changes from IPRs and verification, and to ensure the source data provided is accurate and usable for incorporation into an existing Air Force technical manual. The TOMA may waive the PPR depending on number and complexity of changes from verification.

10.8. Technical Data Assessment (TDA) (T). TDA’s may be accomplished using organic TO sus-tainment environments (ATOS, IDM, etc.) or with the assistance of AFLCMC/HIAM. The TO Man-ager, will determine the TDA requirements for each TO type.

10.8.1. SGML TO Data (T). N/A

10.8.2. S1000D TO Data (T). N/A

10.8.3. Error Resolution. Errors found during the TDA shall be addressed and completed prior to each IPR. Additional TDAs may be necessary based on the amount of errors found during the ini-tial TDA. Successful TDAs in no way relieves the contractor from fixing errors found during fu-ture reviews.

11. TO Delivery. TO file delivery requirements are located in Section 2 Table 3 of this document.

11.1. SGML Tagged Files (T). N/A

11.2. SGML Tagged Files for Use with the eTO Viewer. N/A

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

4 TM-86-01P 9 Dec 14

Prepared by James Brown/406 SCMS/GUEE/(478) 222-0934

12. Source Data Maintenance. Contractors shall maintain accuracy, currency and configuration of TO source data provided by the government, to include GFI, throughout the contract period of performance.

Maintenance includes preparation of source data updates to incorporate corrections, equipment configu-ration changes, and maintenance and operational concept changes.

13. TO Maintenance. Contractors shall maintain TO’s by preparing emergency, urgent, routine chang-es/revisions or supplements and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes IAW TO 00-5-3.

14. Schedules (T). N/A

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

15.1 (T) N/A

15.2 (T) N/A

15.3 (T) N/A

15.4 (T) N/A

16 PROGRAM SPECIFIC REQUIREMENTS.

A. The Offeror shall develop and deliver source data covering changes effecting TOs 11N-H5083-2, 11N-H5083-2-1, and 11N-H5083-4, resulting from the MHU-196 Engagement force & user evaluation feedback implementations program. All changes which affect form, fit, function, or interface to the existing Air Force equipment, shall be described in TOs 11N-H5083-2, 11N-H5083-2-1, and 11N- H5083-4. Source data text and graphics shall be documented on the attached AF Form 158 (Attachment 3, Page 11) for incorporation into the manual.

B. Data delivered for this contract shall be a combination of paper based documents and native files saved to CD.

C. For Graphics formats, see “Graphics Format Recommendations attachment 1 to this document, (page 9). These recommendations provide wide latitude for developing and delivering graphics. The Contrac-tor 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.

D. In-Process reviews shall be held as determined by the TO manager and equipment specialist to ensure all source data submitted for this contract is accurate and suitable for use in the existing Air Force man-ual.

E. Comments generated during ALL development reviews shall be corrected before re-submittal of the required source data. The Contractor shall provide technical and engineering personnel as needed to as-sist Air Force personnel during the development reviews and Verification.

DATA CALL GUEE-16-005 5

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS

NOTES:

• Mark the TM Type Selection Tables indicating the applicable TO types and related specifications.

PART A – (NEW DEVELOPMENT) TM TYPE SELECTION TABLES.

TABLE 1

N/A

6 TM-86-01P 9 Dec 14

Prepared by James Brown/406 SCMS/GUEE/(478) 222-0934

TABLE 2

SUSTAINMENT/MODIFICATION UPDATES TM TYPE SELECTIONS

NOTES:

• Check all applicable boxes.

• For existing 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

Change

Revision

Supple-ment

Supple-mental

TM

Source Data

1. 11N-H5083-2 Same Style and Format

2. 11N-H5083-2-1 Same Style and Format

3. 11N-H5083-4 Same Style and Format

DATA CALL GUEE-16-005 7

TABLE 3 - TM DELIVERY REQUIREMENTS

FOR MHU-196 ENGAGEMENT FORCE & USER EVALUATION

(System/Item)

NOTES:

• For Paper media delivery indicate required quantity

• For all other media types indicate (Y)es or (N)o

• TCTO requirements are specified in the contract vehicle approving the TCTO.

If “Other” is selected, define media type and quantities: Native Files on CD, 2 copies

DELIVERY SCHEDULE

Event Number of days data required prior to event

In Process Review(s) (30 Days)

Verification

(30 Days)

Prepublication Review

(30 Days)

Final TO Distribution (60 Days)

Enter physical mailing address, electronic delivery location or web access point

ATTN: James Brown 235 Byron Street, Ste. 19A Robins AFB, GA 31098-1670

Final delivery due 60 days prior to produc-tion hardware delivery to USAF.

Paper/ 2

SGML/

IPDF /

XML /

Other/ Y

Paper/ 2

SGML/

IPDF /

XML /

Other/ Y

Paper/ 2

SGML/

IPDF /

XML /

Other/ Y

Paper/ 2

SGML/

IPDF /

XML /

Other/ Y

Total Paper Copies Required: 2 2 2 2

8 TM-86-01P 9 Dec 14

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

DATA CALL GUEE-16-005 9

ATTACHMENT 1

Graphics Format Recommendations

GENERAL GUIDELINES

• Single column graphics should not exceed 51 Picas High by 18 Picas Wide. (Paper only)

• Full page graphics should not exceed 51 Picas High by 42 picas Wide. (Paper only)

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

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-01P 9 Dec 14

ATTACHMENT 2

REQUEST FOR TECHNICAL ORDER NUMBER

DATA CALL GUEE-16-005 11

ATTACHMENT 3

AFTO FORM 158

TECHNICAL ORDER REVIEW COMMENT SHEET

TO NUMBER: TITLE: RECEIVED DATE:

TOTAL PAGES:

Name of Reviewer: DATE OF REVIEW:

COMPLETE DATE:

Section

Para/Fig/Page

Comments:

AFTO FORM 158

12 TM-86-01P 9 Dec 14

Section 1. Technical Order (TO) Program Requirements