TMCR_12MAY2015.pdf

TM-86-01P 9 Dec 2014 1 Data Call No: GUEE-15-007

Prepared by Anthony Reagan\406 SCMS/GUEE (472-0934)/4/14/2015

Air Force Technical Manual Contract Requirements (TMCR) for

A-10 HOIST SLING, NSN 1730-01-087-7148

(Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT

REQUEST FOR PROPOSAL/CONTRACT:

Date: 12 May 2015

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 (A-10 HOIST SLING, NSN 1730-01-087-7148) program’s objectives.

3. Commercial Manuals. N/A.

3.1. N/A.

3.2. N/A.

3.3. N/A

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between 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 requirements which are part of the Document Type Definition (DTD) structure or XML schema struc-ture 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 un-til 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 Na-

vy. Comply 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 (Anthony Reagan, 406 SCMS/GUEE, 235 Byron St., Suite 19A, Robins AFB GA, 31098-1670, Comm. 478- 222-0934, DSN 472-0934). Deficiencies and suggested improvements shall be submitted to the TMSS Preparing Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

2 TM-86-01P 9 Dec 14

Prepared by Anthony Reagan\406 SCMS/GUEE (472-0934)/4/14/2015

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.

6. TO Development. TOs shall be written to a scope and depth of coverage sufficient to support the (A- 10 HOIST SLING, NSN 1730-01-087-7148) operations and maintenance concepts.

6.1. (T). Parts shall be identified by the part number of the manufacturer, or by a commercially available part number.

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. All delivered graphics shall be 300 dpi and shall conform to the approved graphic creation and format guidelines listed in attach-ment 1. For assistance with illustration requirements, contact the TO Manager or AF Contracting Officer.

6.3. Page-oriented Military Specification (MILSPEC) TOs shall be formatted with text, graphics and delivered 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 specification (MIL-DTL). Multiple SGML file instances for a single T.O. document are not authorized.

7. TO Numbering. Contractors shall notify the government of manuals which require TO numbers. TO numbers are not required for manuals to be used exclusively by the Contractor’s own personnel. Re-quests for new TO numbers shall be submitted to the TOMA utilizing the TO numbering worksheet.

(Attachment 2)

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.

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 De-partment 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 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/GUEE, Robins AFB, GA 31098. Questions concerning technical content shall be referred to WR-ALC/WNZEAC.

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

TM-86-01P 9 Dec 2014 3

Prepared by Anthony Reagan\406 SCMS/GUEE (472-0934)/4/14/2015

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.

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 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 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 generat-ed by the certification process into the TOs prior to submitting the TOs for verification. At the com-pletion 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 Fur-nished 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.5.1. Verification of IETMs. NA

10.6. Verification Support. N/A.

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.

4 TM-86-01P 9 Dec 14

Prepared by Anthony Reagan\406 SCMS/GUEE (472-0934)/4/14/2015

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

10.8.1. SGML TO Data. The contractor shall submit an SGML tagged TO file, associated graphics files, a PDF rendition of the SGML tagged TO file composed by the contractor and any associated companion files necessary for PDF composition. During assessment, the SGML tagged TO file will parsed against the appropriate TMSS DTD (and optionally run through the Tagging Utilization Tool (TUT)) to determine DTD compliance and correct tag usage. The SGML tagged TO file and associated graphics will be composed by the program office and the rendered PDF will be com-pared with the submitted PDF to check for completeness, indexing, and MIL-SPEC/STD compli-ant formatting.

10.8.2. S1000D TO data. 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). 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 in compliance with the appropriate DTD. NOTE: The government will parse the files prior to ac-ceptance using the public domain “SGMLS Parser” (http://jclark.com/sp/). The Government will perform completeness checks of all SGML data prior to acceptance. Any data failing final ac-ceptance shall be returned to the contractor for correction then returned to the Air Force for addition-al testing to the Government.

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

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

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

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

15.1 N/A.

15.2 N/A.

15.3 N/A.

15.4 N/A

TM-86-01P 9 Dec 2014 5

Prepared by Anthony Reagan\406 SCMS/GUEE (472-0934)/4/14/2015

16 PROGRAM SPECIFIC REQUIREMENTS.

a. The Offeror shall develop and deliver new MIL-SPEC Combined Operation and Maintenance In-structions Manual with combined IPB in work package format IAW Section 2, Table 1, covering the A-10 HOIST SLING, NSN 1730-01-087-7148

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 pa-per based documents and digital files.

c. SGML files shall be reviewed by the Air Force during the development process to ensure com-pliance 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 10). 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 development. Sample In-Process Completion tables are provided in Attachment 3.

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 personnel 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. The Air Force DOES NOT profess to recommend one software product over another. Contractor’s are solely responsible for software selection.

6 TM-86-01P 9 Dec 14

Prepared by Anthony Reagan\406 SCMS/GUEE (472-0934)/4/14/2015

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 (A-10 HOIST SLING, NSN 1730-01-087-7148) Program (System/Component)

Title or Type of Manuals Specification Required

1. Operation and Maintenance Instructions in Work Package Format MIL-DTL-87929

a. Operation & Maintenance Instruction Manuals

b. With Illustrated Parts Breakdown

TM-86-01P 9 Dec 2014 7

TABLE 3 - TM DELIVERY REQUIREMENTS

FOR A-10 HOIST SLING, NSN 1730-01-087-7148

(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

(45 Days)

Prepublication Review

(45 Days)

Final TO Distribution

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

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

Paper/ 2

SGML/ Y

IPDF / Y

XML /

Other/

Paper/ 2

SGML/ Y

IPDF / Y

XML /

Other/

Paper/ 2

SGML/ Y

IPDF / Y

XML /

Other/

Paper/ 1

SGML/ Y

IPDF / Y

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Other/

Paper/

SGML/

IPDF /

XML /

Total Paper Copies Required: 2 2 2 1

8 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://assist.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.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-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).

TM-86-01P 9 Dec 2014 9

Prepared by Anthony Reagan\406 SCMS/GUEE (472-0934)/4/14/2015

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

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

TM-86-01P 9 Dec 2014 11

ATTACHMENT 2

REQUEST FOR TECHNICAL ORDER NUMBER

1. *PRIME SYSTEM APPLICATION (If Applicable or N/A)_______________________________

2. *CONTRACT NUMBER/ PURCHASE REQUEST (PR) NUMBER: _____________________

3. *MISSION DESIGN SERIES/NOMENCLATURE (Name Of Equipment) __________________

4. *FEDERAL STOCK CLASS:_______________________________________________________

5. *PART NUMBER(s):______________________________________________________________

6. *NSN/FSN: (or temp NSN) __________________________________________________________

7. *PUBLICATION TYPE (Opn & Maint with IPB, Overhaul, WUC, IPB, LOAP, etc.)

8. *SUGGESTED TECHNICAL ORDER NUMBER:_____________________________________

9. *RECOMMENDED TITLE OF MANUAL (Leave Blank if Classified) ____________________

10. *CLASSIFICATION OF MANUAL: ________________________________________________

11. *CLASSIFICATION OF TITLE: ___________________________________________________

12. *KIND OF EQUIPMENT (Airborne / Ground / Not Applicable):___________________________

13. *TEST EQUIPMENT? Yes / No

14. PROGRAM ELEMENT CODE (PEC): ________________________________________________

15. LEAD COMMAND: _______________________________________________________________

16. DOES MANUAL EXIST FOR SAME/SIMILAR EQUIPMENT? Yes / No

17. EXISTING MANUAL TO NUMBER: _________________________________________________

18. COMMERCIAL OFF THE SHELF (COTS) ITEM: Yes / No

19. CONTRACTOR INFORMATION: (If Applicable)

a. NAME OF VENDOR: _____________________________________________________

b. ADDRESS: _____________________________________________________________

c. MANUFACTURER'S CODE: ______________________________________________

d. POINT OF CONTACT: ____________________________________________________

20. FOREIGN MILITARY SALES (FMS) YES ___ NO ____ (If YES, complete item 20)

20. COUNTRY CODES (For CSTO/FMS manuals): (See TO 00-5-19) __________________________

21. COMMENTS:______________________________________________________________________

* = Mandatory Fields

12 TM-86-01P 9 Dec 14

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