TMCR.pdf

TM-86-01P 9 Dec 2014

DATA CALL: GUEE-16-014 1

Air Force Technical Manual Contract Requirements (TMCR) for

LITENING Targeting Pod System (LTPS) AN/AAQ-28 Sustainment Program) (Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date: 26 August 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 (LITENING Targeting Pod System (LTPS) AN/AAQ-28 Sustainment Program) program’s objectives.

3. Commercial Manuals. (T) NA

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting be-tween tailoring options offered in 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 re-quirements which are part of the Document Type Definition (DTD) structure or XML schema structure located in Section 2, Table 1.

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. Contractors may recommend additional tailoring of the Joint-Service TMSS SIRs and provide recommended SIRs for other TMSS as applicable. No formal Contractor action on the recommended change shall begin until formal written approval is received from the government. NOTE: TMSS requirements marked “(F)” are specifically for Air Force use; “(A)” is for Army, “(M)” is Marine Corps and “(N)” is Navy. Com-ply with all unmarked and “(F)” TMSS requirements as modified by the tailoring options in each

TMSS.

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 Technical Or-der Management Agency (TOMA) (Cindy Lewis, 406 SCMS/GUEE, 235 Byron St., Suite 19A, Robins AFB, GA 31098-1670 (478-222-3774). 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. When new TO requirements are identified the Contractor shall notify the government utilizing DI-TMSS-80067B, Technical Manual (TM) Contractor Furnished Aero-nautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, or approved contractor formats. This process shall require government review and approval of recommended additional require-ments prior to developing additional data.

2 TM-86-01P 9 Dec 14

DATA CALL: GUEE-16-014

6. TO Development. (T) TOs shall be written to a scope and depth of coverage sufficient to support the LITENING Targeting Pod System (LTPS) AN/AAQ-28 Sustainment Program) operations and mainte-nance concepts.

6.1. (T). NA

6.2. (T). NA

6.3. Page-oriented Military Specification (MILSPEC) TOs shall be formatted with text, graphics and delivered according to the TMSS specified in Section 2, Table 1.

7. TO Numbering. NA

8. Data Rights. Contractors shall provide Unlimited Rights for all source data and TOs prepared specifi-cally for the contract. Government rights in data are specified in the Defense Federal Acquisition Regula-tion 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.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. 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 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 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 written approval of the originating United States agency.

DISTRIBUTION STEMENT B - Distribution authorized to U.S. Government Agencies only (Administrative or Operational) ((7 January 2011).

Other request for this document shall be referred to 406 SCMS/GUEE, Robins AFB, GA 31098. Questions concerning technical content shall be referred to AFLCMC/WNYBAA.

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. The contractors’ shall ensure TOs prepared are: a) technically accurate and safe; b) writ-ten 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 limitation statements.

10.1. 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 re-served for those procedures which would activate explosive devices or present a hazard to personnel or equipment.

10.2. Guidance Conference (T). As required, working through the TOMA, the contractor shall co-host and participate 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 conference. 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. 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

DATA CALL: GUEE-16-014 3

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 accordance with TO 00-5-3 or as defined by the program office. During the IPRs the contractor will be responsible 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 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. TO Delivery Requirements for In-Process Reviews. (T) IPR TO data shall be 100% complete and accurate for revision IPR’s. IPR TO data shall be 100% complete and accurate for source data IPR’s. 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 new TO procedures and data developed to support the program are accurate, adequate, current, and usable for their intended purpose. The Gov-ernment may witness the certification activities. The contractor shall incorporate comments generated by the certification 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 contractor 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. TO 00-5-1 and TO 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 manual meets style and format requirements. The Contractor shall prepare and deliver copies of TOs and TO updates in MIL-SPEC compliance for the PPR as shown in the delivery matrix. The TOs for PPR shall have been approved by contractor QA, be in compliance with the MIL-SPECs/standards, and incorporate all verification comments and corrections approved by the TOMA or program management office representative. The TOMA may waive the PPR depending on number and complexity of changes from verification.

10.8. Technical Data Assessment (TDA). (T) NA

10.8.1. SGML TO Data. (T) NA

10.8.2. S1000D TO data. (T) NA

10.8.3. Error Resolution. (T) NA

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

11.1. SGML Tagged Files. (T) NA

11.2. SGML Tagged Files for Use with the eTO Viewer. NA

11.3. Interactive Electronic Technical Manuals (IETM)(T). NA.

4 TM-86-01P 9 Dec 14

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 revisions or supplements and source data updates to incorporate corrections, equipment configuration changes, and maintenance and opera-tional concept changes IAW TO 00-5-3.

14. Schedules. The contractor shall develop and maintain an Integrated Technical Order Status and Sched-ules (TOSS) throughout the period of performance for all TO development activities associated with this order for the life of the contract. The schedule shall be to the system/book or TCTO level and cover all development major milestones. Any changes to the TOSS after the guidance conference shall be coordi-nated with and approved by program TOMA. NOTE: DI-TMSS-81812, Technical Manual Schedule and Status Report, may be used as a guide to prepare the TOSS.

15. Time Compliance Technical Orders (TCTOs) (T). When required by the government, the contractor shall prepare TCTO’s, ITCTO’s and resulting TO updates as required in support of (LITENING Targeting Pod System (LTPS) AN/AAQ-28 Sustainment Program). TCTO’s will be used to document all permanent modifications, initiate special “one time” inspections, or impose temporary restrictions on systems or equipment within specified time limits effecting (LITENING Targeting Pod System (LTPS) AN/AAQ-28 Sus-tainment Program). Costs for TCTO package development must be in accordance with AFI 65-601Vol.1.

15.1. The contractor shall deliver certified drafts of Immediate Action TCTO’s to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The contractor shall deliver drafts with comments incorporated within 24 hours of receipt of comments.

15.2. The contractor shall deliver initial certified drafts of Urgent Action TCTO’s to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The contractor shall deliver final drafts with “final” customer comments incorporated, within 96 hours of receipt of comments.

15.3. The contractor shall deliver initial certified drafts of routine safety TCTO’s to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The contractor shall deliver final drafts with “final” customer comments incorporated, within 5 business days of receipt of comments.

15.4. The contractor shall deliver certified drafts of routine TCTO’s to meet program office plans to satisfy requirements outlined in TO 00-5-3/00-5-15. The contractor shall deliver final drafts with “final” customer comments incorporated, within 10 business days of receipt of comments.

16. PROGRAM SPECIFIC REQUIREMENTS.

a. The offeror shall develop and deliver quarterly updates to the technical manual IAW Section 2, Table 2 in the form of revisions to existing published manual.

b. As required, the contractor shall develop quarterly updates for aircraft platform manuals identified in Section 2, Table 2, in the form of source data to existing published manual.

c. In the event the AF issues an interim supplement, a copy of the supplement will be for-warded to the contractor for incorporation into the next revision.

d. For Graphics formats, see “Graphics Format Recommendations” attachment 1 to this document. These recommendations provide wide latitude for developing and delivering graphics. The Contractor shall select one method from these recommendations to pre-pare 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

DATA CALL: GUEE-16-014 5

in the documents or not. Digital photographs (halftones) shall NOT be used. All graphics shall be line artwork.

e. Contractor shall provide 100% IPR copy of revisions and source data to be delivered for pre pub review for the government.

f. Data delivered for review shall be sent in the form of digital files from a secure website called LIVE LINK.

g. Formal delivery of quarterly updates shall be in the form of Indexed Portable Document Format (IPDF).

h. In-process deliveries shall be 45 days prior to formal delivery for revisions and source data.

i. Government review comments documented on AFTO Form 158 during ALL quarterly reviews shall be incorporated and approved before formal delivery (See attachment 3).

j. Contractor shall not deliver another 100% IPR until the previous delivery has been ap-proved and delivered to the government.

k. If no quarterly update is needed, the contractor will send via email a transmittal letter to Equipment Specialist (ES) and TOMA stating that no update is needed for the quarter.

6 TM-86-01P 9 Dec 14

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

TMSS REQUIREMENTS FOR THE (LITENING Targeting Pod System (LTPS) AN/AAQ-28 Sustainment Program) Program

(System/Component)

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-DTL-5096

a. Inspection and Maintenance Requirements (-6) Manual

b. Acceptance and Functional Check Flight (FCF) Procedures (-6CF) Manual

c. Acceptance and Functional Check Flight (-6CL) Checklist

d. Inspection Workcards (-6WC)

e. Maintenance/Operations Checklists

2. List of Applicable Publications MIL-DTL-8031

3. Work Unit Code Manual

a. Standard WUC Manual

b. Two Chapter Manual

c. Three Chapter Manual

MIL-DTL-38769

4. Calibration Procedures MIL-DTL-38793

5. Time Compliance Technical Orders (TCTOs)

a. TCTO

b. TCTO Supplement

MIL-DTL-38804

6. Illustrated Parts Breakdown MIL-DTL-38807

DATA CALL: GUEE-16-014 7

TABLE 1

TMSS REQUIREMENTS FOR THE (LITENING Targeting Pod System (LTPS) AN/AAQ-28 Sustainment Program) Program

(System/Component)

Title or Type of Manuals Specification Required

7. 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. Special Manuals

(1) Aircraft Engine Testing and Trending Procedures

(2) Aircraft Power Package Testing Procedures

(3) Static Firing of Missile Motors

(4) System Peculiar Corrosion Control

(5) Nondestructive Inspection (NDI)

(6) Aircraft Structural Integrity Program (ASIP)

(7) ATE Operator Test Procedures

(8) Special Requirements for Storage and Maintenance Procedures;

AUR Munitions/Launchers and Associated Support Equipment, Conventional Components and CMBR Agents

(9) Parachute Packing Procedures

(10) Operators Instructions (Hand-Held Flight Computers)

(11) Installation-Engineering Facility (Ground C-E Equipment)

d. Checklists (IAW MIL-DTL-5096)

e. With Illustrated Parts Breakdown

8 TM-86-01P 9 Dec 14

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. 11F1-AAQ28-

EXISTING

STYLE AND

FORMAT

2. Applicable source data for aircraft Fault Isolation:

F-16 blk 30/40/50, F-15E, A-10, B-

3. Applicable source data for aircraft flight manuals:

F-16 blk 30/40/50, F-15E, A-10, B-

4. Applicable source data for training: F-16 blk 30/40/50, F-15E, A-10, B-

5. Applicable source data for SIL Testing: F-16 blk 30/40/50, F-15E, A-10, B-

6. Applicable source data for Operation and Maintenance Technical Order and Training source data: F-16 blk 30/40/50, F- 15E, A-10, B-

DATA CALL: GUEE-16-014 9

TABLE 3 - TM DELIVERY REQUIREMENTS

FOR LITENING TARGETING POD SYSTEM (LTPS) AN/AAQ-28 SUSTAINMENT PROGRAM

(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: ________________

DELIVERY SCHEDULE

Event Number of days data required prior to event In Process Review(s) (45 Days)

Verification

( Days)

Prepublication Review

( Days)

Final TO Distribution

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

Attn: Cindy Lewis

406 SCMS/GUEE

235 Byron St., Suite 19A Robins AFB, GA 31098 cindy.lewis.ctr@us.af.mil

Paper/

SGML/

IPDF / 1

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF / 1

XML /

Other/

Kenneth Franklin

AFLCMC/WNYBAA

235 Byron St., Suite 19A Robins AFB, GA 31098 kenneth.franklin.1@us.af.mil

IPDF / 1

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF / 1

XML /

Other/

AFLCMC/WNYBP

1981 Monahan Way, Bldg. 12 Wight-Patterson AFB, OH 45431-7424

Paper/ 1

SGML/

IPDF / 1

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/ 1

SGML/

IPDF / 1

XML /

Other/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Total Electronic and Paper Copies Required:

1 paper and 3 electronic

1 paper and 3 electronic

10 TM-86-01P 9 Dec 14

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 included in the final contract, unless the entire SIR is not applicable; e.g., if MIL-DTL-22202D is not required, the entire SIR can be deleted.

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. For this contract enter:

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

Digital requirements shall not be tailored out. Tailoring shall be limited to the options expressed in paragraphs 6.2.

Any requests for tailoring outside of these requirements must be coordinated with the specification Preparing Activity

(PA-16) AFLCMC/HIAM.

Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from Acquisition Streamlining and Standardization Information System (ASSIST) web page, https://as-sist.dla.mil/online/start/index.cfm.

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.1.c (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 un-til 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.2.j (1), (2), (3), (6), (8), (10), and (11).

DATA CALL: GUEE-16-014 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).

12 TM-86-01P 9 Dec 14

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.

DATA CALL: GUEE-16-014 13

Attachment 2

MIL-PRF-32216

PUBLICATION NUMBER

PUBLICATION DATE

IDENTIFYING TECHNICAL PUBLICATION SHEET

FOR COMMERCIAL MANUAL

(Supersedure note, or other special notes, if any)

1. PURPOSE: This technical publication is issued for the purpose of identifying and authorizing the following commercial manual for (Army)(Navy) (Marine Corps) (Air Force) (Defense Logistics Agency) (as appropriate) use.

MANUFACTURER: (Name and address)

PURCHASE ORDER OR CONTRACT NO.

REQUISITION NO. (if furnished by the contracting activity)

EQUIPMENT: (Type, model, part number, nomenclature, Federal Item Name, serial numbers.)

NATIONAL STOCK NUMBER (if furnished by the contracting activity.)

TITLE: (Operating Instructions, Maintenance Instructions, Parts Lists, as appropriate)

ADDITIONAL IDENTIFICATION: (if any) Volumes, Parts, etc.

DATE: (if any)

2. ADDITIONAL COPIES: Additional copies are available from _______________ (Contracting activity will furnish infor-mation, but if no information is furnished, this paragraph will be omitted and the following paragraph moved up into its place.)

3. AUTHORITY NOTICE, DISTRIBUTION STATEMENT, DISCLOSURE NOTICE (as applicable, in accordance with MIL-M-38784).

FOR UNCLASSIFIED MANUALS

NOTICE: Reproduction for non-military use of the information or illustrations contained in this publication is not permitted.

The policy for military reproduction is established for the Army in AR 38-4, for the Navy and Marine Corps in OPNAVINST 5510.1, and for the Air Force in AFPD 34-1.

FOR CLASSIFIED MANUALS

NOTICE: This material contains information affecting the national defense of the United States within the meaning of the Espionage Laws, Title 18, U.S.C., Section 793 and 794, the transmission or revelation of which in any manner to an unauthorized person is prohibited by law.

14 TM-86-01P 9 Dec 14

Attachment 3

Sample Government License Agreement

Contractor’s Letter Head Date

From: Company Name

To: 406 SCMS/GUEE 235 Byron St., Suite 19A Robins AFB, GA 31098-1670

Subject: Government License Agreement

NAME OF CONTRACTOR assigns to the U.S. Government under contract XXXXX-XX-X-XXXX, Government License Rights, which allow for the electronic storage, use, printing, release and/or disclo-sure of the technical data contained herein. These rights extend to U.S. governmental agencies only and may not to be sold, disclosed or otherwise provided to any other entity/entities outside of the U.S. Gov-ernment without written permission from the Original Equipment Manufacturer (OEM). This license shall remain in effect for as long as the equipment cited in the technical manual remains in service and under government control and usage, after which this license is revoked.

Signed and dated by the contractor

Sample: Unlimited Rights GPLA

NAME OF CONTRACTOR assigns to the U.S. Government under contract XXXXX-XX-X-XXXX, Unlimited License Rights to, use, modify, reproduce, release, perform, display, or disclose technical data for (xxxxx enter hardware item or PN). This license shall remain in effect for as long as the equipment cited in the technical manual remains in service and under USG control and usage, after which this li-cense is revoked.

Signed and dated by the contractor

(NOTE: Limited Rights license may be tailored to include FMS customers if OEM has no objections.)

DATA CALL: GUEE-16-014 15

ATTACHMENT 4

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