RFP_-_Attachment_2_CDRLs.pdf

FA3047-15-R-0034

Demountable Noise Suppressor System

ATTACHMENT 2

Contract Data Requirements List

Product Drawings/Models and Associated Lists

[DI-SESS-81000E/T]

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved QMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services and Communications Directorate (0704- 0188), Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP XXXX TM OTHER

D. SYSTEM / ITEM E. CONTRACT / PR NO. F. CONTRACTOR

T38 Sound Suppressor

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

PRODUCT DRAWINGS/MODELS AND ASSOCIATED LISTS

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

DI-SESS-81000E/T (SOW) PARAGRAPH 1.2.3. AFLCMC/LZPEM

7. DD 250 REQ 9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

DD QRTLY SEE BLK 16 b. COPIES

8. APP CODE SEE BLOCK 16 11. AS OF DATE 13. DATE OF

SUBSEQUENT

SUBMISSION

a. ADDRESSEE FINAL

A SEE BLOCK

SEE BLK 16 Draft Reg Repro

16. REMARKS AFLCMC/LZPEM

285 Cochran Street

1. Air Force drawings 9626025 rev F, 9579776 rev L and 9579777 rev A (CAGE 98752) are a part of this CDRL ROBINS AFB, GA.

A copy of the drawings may be requested through the Procurement Contracting officer. 31098-1669

2. METADATA SHALL BE IN ACCORDANCE WITH 9579776 PARAGRAPH 10 OPTION

ONE

3. Please reference EDATS control number 2014-82 on all correspondence related to this effort.

PAPER COPY 1

SEE CONTINUATION SHEETS DIGITAL DATA 1

(CLASSIFIED)

DIGITAL 1

15. TOTAL 1 0 2

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Harold Banks 13 August 14

DD Form 1423-1, Feb 2001 STRAWMAN Revision 22 July 2014 PAGE___1_ OF __8___ PAGES EDATS 2014-82

CONTINUATION OF DD FORM 1423-1 (DI-SESS-81000E/T) Dtd August 13,2014 EDATS 2014-82

BLOCK 4: DI-SESS-81000E is tailored as follows:

Requirements: (the below paragraph numbering corresponds with the numbering in the DID)

1. Reference Documents. Delete paragraph 1. in its entirety and replace with “1. Reference Documents. The documents apply as cited in the DD Form 1423-1 and continuation sheets. Unless otherwise noted, the latest revision of the ASME Standard at the time of solicitation shall apply.”

3. Format. Delete in its entirety and replace with “3. Format. Product Drawings/Models and Associated Lists shall be in the format as specified on this DD Form 1423-1 and continuation sheets, and shall meet the requirements of ASME Y14.1."

4. Content. Delete in its entirety and replace with “4. Content. Product Drawings/Models and Associated Lists shall conform to the requirements of ASME Y14.100-2013, Appendix B, sections B6 through B9.1 and Appendices C,D, E, and F (F-3.5, F-3.6, F-3.7) in conjunction with ASME Y14.24-2012, ASME Y14.34, ASME Y14.35M and ASME Y14.41. They shall document directly or by reference the following (items a through q), as applicable:”

6. CAGE code. Delete “TDP Option Selection Work Sheet incorporated in the contract or purchase order.” and replace with “DD Form 1423-1 and continuation sheets.”

7. Selection of drawings. Delete “The TDP Option Selection Work Sheet incorporated in the contract or purchase order will specify whether the contractor or the Government is responsible for selecting the types of drawings and associated lists.” and replace with “The contractor shall comply with ASME Y14.24, Types and Applications of Engineering Drawings”.

BLOCK 7:

“D”—Inspection is at destination and is to ensure this product meets this CDRL and its tasking document.

Shipping list must accurately reflect the shipped product.

“D”—Acceptance is at destination. Acceptance of final data will be by approval of the Engineering Data Management Specialists.

BLOCK 9:

DISTRIBUTION STATEMENT. Distribution statements shall be in accordance with DoD Instruction

5230.24 and included on the first sheet of each drawing near the title block, and shall be as follows:

“DISTRIBUTION STATEMENT C. Distribution authorized to U.S. Government Agencies and their contractors (CRITICAL TECHNOLOGY) (13 AUG 14). Other requests for this document shall be referred to (AFLCMC/WNZEA).”

EXPORT CONTROL WARNING LABEL. All engineering data shall be marked with Export Control Warning Labels in accordance with DoD Instruction 5230.24, dated August 23, 2012 as follows:

“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 (Title 50, U.S.C., App. 2401 et seq.), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25.”

DESTRUCTION NOTICE. Mark documents with one of the following:

a. For unclassified limited documents: “DESTRUCTION NOTICE. Destroy by any method that will prevent disclosure of contents or reconstruction of the document.”

b. For classified documents: “DESTRUCTION NOTICE. Follow the procedures in DoD 5220.22- M, National Industrial Security Program Operating Manual, Chapter 5, Section 7, or DoD 5200.1R, Information Security Program, Chapter 6.”

BLOCK 10: Revisions/changes to the final delivered data shall be furnished quarterly, commencing the first quarter after destination acceptance of the final reproducible data and continue until the contract is closed. Quarterly updates shall include an updated BOM, reference A.F. Drawing 9579776. Negative reports shall be submitted to AFLCMC/LZPEM.

BLOCK 11: 15 days before end of quarter.

BLOCKS 12 AND 13:

1. All data submittals shall contain a delivery letter and a shipping list. The letter shall contain at a minimum the contract number, delivery order, CLIN, and EDATS number (located on the bottom right corner of the DD Form 1423). The shipping list shall include as a minimum, the document number, revision level, and number of sheets/pages. The data delivered shall be in the same sequence as the shipping list.

Shipments of data must be for a complete Technical Data Package (TDP) that accurately depicts the final product as defined in the tasking document (SOW, PWS, etc.). Shipping list shall specify whether the shipment is updates, final or make-up.

2. Within 90 days after successful signed completion of Physical Configuration Audit (PCA), a Bill of Materials (BOM) in accordance with Air Force drawing 9579776 (CAGE 98752) shall be delivered.

3. Within 90 days after successful signed completion of final PCA, one set of paper copies of all “final reproducible data” (reference Block 14 of the DD 1423-1) shall be delivered. A letter of transmittal shall accompany submittal. Paper copy submittal will be reviewed within 120 days after receipt of data, unless additional time is required, at which time the contractor will be notified. When the submittal does not meet the contractual requirements a discrepancy letter will be submitted through Government Contracting Officer with a suspense date for the contractor to resubmit the TDP with corrections incorporated.

a. Submittal of programming files, in accordance with Air Force drawing 9579776 (CAGE 98752), Software and memory Device Data is not required for this paper submission.

b. Concurrent with the paper copies the contractor shall submit four (4) representative samples of each digital data format of data for this project in accordance with Air Force drawing 9579776 (CAGE 98752), (Native, Neutral, HPGL, Metadata Spreadsheet, Gerber, Software/memory Device Data, etc.).

4. Within 60 days after approval of paper copy, one set of all “final reproducible digital data” to include Native, Neutral, HPGL, Metadata Spreadsheet, Gerber, Software/Memory Device Data, etc. (reference Block 14 of the DD 1423-1) shall be delivered to AFLCMC/LZPEM, 450 Third Street, Bldg. 323, Robins AFB GA 31098-1813. If changes have been required to the BOM since delivery in paragraph 3 above, resubmittal shall be required. The final digital submittal will be reviewed within 60 days after receipt of data, unless additional time is required, at which time the contractor will be notified. In the event the submittal does not meet the contractual requirements, a discrepancy letter will be submitted through the Government Contracting Officer with a suspense date for the contractor to resubmit the final digital TDP with corrections incorporated.

BLOCK 16:

1. Government Activity and Part Identification: The contractor shall comply with Air Force drawing 9626025 (CAGE 98752), titled “Air Force Drawing Requirement”. This requirement defines format requirements for the generation of Air Force drawings. The contractor shall use the Government activity identifier Commercial and Government Entity (CAGE) code and Air Force drawing numbers. The contractor shall contact the AFLCMC/LZPEM EDMS to obtain the drawing numbers.

1.1. Engineering Change Orders (ECOs): When an existing Air Force CAGE code drawing is revised, all

ECOs shall be incorporated prior to the paper submittal for review.

1.2. Concurrent with the final submittal, all ECO’s against existing Air Force CAGE code drawings shall be incorporated and a copy of the ECO shall be delivered for Air Force revision documentation.

2. Content, format, and media requirements for delivery of Digital Engineering Data: The contractor shall comply with Air Force drawing 9579776 (CAGE 98752).

3. Product Drawings/Models and Associated Lists: Product drawings/models and associated lists shall be prepared to provide the design, engineering, and manufacturing information necessary to enable the procurement or manufacture of an item essentially identical to the original item. The product shall be defined to the extent necessary for a competent manufacturer to produce an item, which duplicates the physical, interface, and functional characteristics of the original product, without additional design engineering effort or recourse to the current design activity. Product data shall reflect the approved, tested and accepted configuration of the defined delivered item. This includes but is not limited to special tooling, interface hardware, special test equipment, and support equipment.

4. Engineering Drawing Practices: The contractor shall use the practices described in ASME Y14.100- 2013. For clarification, the documents listed in section 2 of ASME Y14.100-2013 shall be considered first tier and shall apply. The contractor may find it useful to incorporate the concepts of MIL-HDBK-288 into the preparation of the TDP. MIL-HDBK-288 refers to Engineering Drawing Package (EDP); this term shall be considered synonymous with TDP. In instances where the ASME standards do not fully define requirements concerning preparation of engineering drawings, the contractor may use the guidance provided in the Drawing Requirements Manual (DRM) 11th Edition available from IHS, Inc. copyright 2008.

5. Commercial Off-the-Shelf (COTS): Definition for a COTS item can be found in the Federal Acquisition Regulation (FAR SUBPART 2.1-Definitions) Part 2.101 and (FAR) Part 12. The technical data requirement for commercial items is at DFARS 252.227-7015. For clarification of this effort, any modification/tailoring of the COTS item shall require a modifying drawing be prepared and delivered to the Air Force documenting the comparison of the COTS item and the item after modification.

6. Control Drawings: Control drawings shall be created in accordance with DI-SESS-81000E and ASME Y14.24-2012 to depict engineering criteria used in selecting purchased or vendor developed items. Control drawings shall disclose engineering form, fit, function and performance requirements for the acquisition of interchangeable purchased items of existing designs, or of items specially developed by vendors to the control drawing requirements. When COTS/purchased items are used by the contractor and are part of this effort as defined in the tasking document (SOW, PWS, etc.), control drawings shall be developed and delivered. Control drawings not developed for this contract that are part of the deliverable TDP shall be updated, to show current information (i.e., performance/qualification requirements, vendors/sources names and part numbers.)

6.1. Control drawings are not required for items which are Government directed purchases or for Government Furnished Material/Government Furnished Equipment (GFM/GFE). Such items shall be identified using the GFE/GFM notation on the parts list, etc. The use of a flag note is acceptable.

7. Contract Numbers: When a TDP document is prepared under a Government contract, the Government contract number under which it is prepared shall appear on the first sheet of the document original. When a TDP document is delivered under a Government contract other than the one under which it was prepared, the Government contract number under which it is delivered shall also appear on the first sheet of each copy submitted. If the document is prepared and submitted under the same contract, only the entry for the contract under which it is prepared is required.

8. Application Data: All new and revised drawings shall contain Application Data. The Application Data is mandatory for all drawings. The Application Data shall show the “Next Assembly” and “Used On”. The application data shall be located near the title block on sheet 1, placed on a separate referenced document, or provided on a separate parts list. When the application data appears on a separate referenced document, a cross reference note shall be included on each parent drawing to indicate that a separate referenced document is available. When an item is used in more than three applications, the entry “general usage” may be entered in the “Used On” column.

9. Reference Documents: Documents referenced in a TDP shall be furnished as part of the TDP with the exception of those specified in referenced documents available in Acquisition Streamlining and Standardization Information System (ASSIST) and non-Government standardization documents available from the issuing non-Government standards body, such as the American Society of Mechanical Engineers (ASME). The following types of documents shall not be referenced in a TDP: technical manuals, procedural manuals, maintenance manuals, company drafting manuals, management plans, uncontrolled documents or unreleased documents. However, when information essential to meeting the content of a TDP (such as default surface texture values) is contained within such prohibited documents, that information shall be extracted from the reference document and included in the TDP.

9.1 Prohibited Documents, References, and Phrases: Technical Orders (TOs), Time Compliance Technical Orders (TCTO), pamphlets, recordings, National Stock Numbers (NSNs), To Be Determined (TBD), Statement of Work ((TASKING DOCUMENT)), Performance Work Statement (PWS), Statement of Objectives (SOO), and Contract Data Requirements List (CDRL), shall not be referenced within the TDP.

10. Traceability: The contractor shall prepare the TDP in such a manner to insure that all applicable documents and part or identifying numbers (PINS) i.e., Artwork, Schematics, Software/Programming Data, Test Criteria, etc., are referenced within the TDP for traceability.

10.1 If the contractor is the original equipment manufacturer (OEM), impacted engineering data that are part of the effort as defined in the tasking document (SOW, PWS, etc.) shall be revised to include changes to reflect the delivered item’s configuration.

10.2 If the contractor is not the OEM, the contractor shall ensure impacted engineering data that are part of the effort as defined in the tasking document (SOW, PWS, etc.) are updated and delivered to reflect the delivered items configuration.

11. Preparation Method: American English language shall be used in the preparation of this TDP.

Dimensioning and Tolerancing shall be Decimal Inch in accordance with ASME Y14.5-2009. Size and format of drawings shall be Decimal Inch per ASME Y14.1. All drawings shall be prepared using Third Angle Orthographic Projection method of presentation. The symbol for angle of projection shall be delineated in the Title Block of newly prepared or revised engineering data. (ASME Y14.3-2003 figure 2)

12. TDP Validation: The contractor shall validate that the TDP conforms to the contractual requirements, and that they accurately depict the item(s) developed, modified, or produced under the contract.

13. Clarification of Detailed Test Criteria for Electrical and Avionics Items: Test criteria for items designed or developed with Government funds is an inherent part of the TDP. Test criteria shall be incorporated, either directly on each TDP document or by reference, for each end item, top assembly item, configured item, and lowest assembled item IAW Air Force drawing 9579777 (CAGE 98752), titled “Clarification of Detailed Test Criteria for Electrical and Avionics Items.”

14. Associated Lists: Parts Lists per ASME Y14.34 are required. Parts Lists are required at assembly level. Parts Lists for Contractor Activity identifier CAGE code may be an integral part of a document or it may be a separate document. The identification and quantity of parts shown on the assembly drawing shall agree with the parts list.

15. Marking: Drawings shall specify requirement for marking part number identification on items as required by MIL-STD-130 and other applicable documents referenced therein. Item unique identification (IUID) marking is mandatory for applicable items as determined by the Program Office. (See DFARS 252.211-7003 Item Identification and Valuation) The drawings shall identify the content, method of application, material and location of marking on the part.

16. Printed Board Artwork Master Drawing. The printed board artwork master drawing shall include images of all artwork required to manufacture the printed board. These images will serve as a reference to those images produced from the Gerber data files IAW Air Force drawing 9579776 (CAGE 98752) titled “Product Data Specification”. Also, this drawing shall reference a unique part or identifying number (PIN) with revision data for the digital file set which includes the Gerber, test, and drill data files. The PIN number format structure and characters shall meet the same requirements as for the part number. These requirements are in addition to those in ASME Y14.24 and other related standards.

17. Printed Board Artwork Master, Test, and Drill NC Data. The printed board artwork master, test, and NC drill data shall be delivered IAW Air Force drawing 9579776 (Cage 98752). These requirements are in addition to those in ASME Y14.24 and other related standards.

18. Legacy Stable Base Media (Mylars, undimensioned drawings, master patterns, etc.). Data originally produced on stable base drawing media that has been redrawn/converted/reproduced in a digital format or developed on a CAD platform shall be delivered.

19. Legibility and Reproducibility: All documents prepared or submitted shall meet the legibility and reproducibility requirements of the specification or standard controlling the media in which the data is to be delivered. As a minimum, all lines, symbols, letters, and numerals shall be readable.

20. Protecting Classified Information: TDPs or parts thereof, containing classified information shall be protected and marked in accordance with the Department of Defense National Industrial Security Program Operating Manual for Safeguarding Classified Information, DoD Manual 5220.22-M. When 3D TDP data is used, the solid models shall display classification marking clearly visible when the solid model is first opened.

21. Software and Memory Device Data: Software and Memory Device drawings shall be selected per ASME Y14.24 and CAD/CAM data files shall be delivered per Air Force drawing 9579776 (CAGE 98752).

22. Inspection of TDP: The TDP shall be inspected for the following:

a. Compliance with the requirements of this contract.

b. Inclusion of all documents, including sub-tier references, required to meet the design disclosure requirements of the TDP.

c. Accuracy of the assignment and identification of security markings, restriction statements (for example distribution statements), export control notices, rights-in-data legends, and other special markings.

d. Inclusion of contract numbers and contractor identifications.

e. Legibility and reproducibility.

f. TDP components have not been prepared for requirements, which could be met by existing standardization documents.

g. Completeness and accuracy of the TDP documents, including required quality assurance information, in describing design of the item, its subassemblies, and component parts. The design to be described by the TDP documents is that configuration of the item the Government has approved, tested, or accepted.

h. Both Type 2D and Type 3D TDPs shall open in the appropriate software without regeneration errors or warnings.

23. Source Control Drawing (SOCD) Approval Request. Source control drawing approval requests (as referenced in MIL-STD-31000A and corresponding Appendix A) shall be prepared and submitted to the requiring office in Block 6 of this DD Form 1423-1 prior to the preparation or use of a source control drawing. Each potential source control item shall be approved by the Air Force System Engineer prior to inclusion of the source control drawing in the TDP. SOCD approval requests are used to ensure that only valid source qualification requirements are included in the TDP. Under Public Law, the Government will actively seek multiple sources for any item for which source qualification is a requirement. Air Force engineering will evaluate each request and notice will be promptly given regarding approval/disapproval.

Requests shall be by letter and shall be prepared and submitted as follows:

a. Format - The Source Control Drawing Approval Request shall be in the contractor’s format.

b. Content - The request shall specify the following:

(1) Nomenclature and description of the item.

(2) The critical application(s) for which the item is to be used.

(3) Number of applications per end item.

(4) System performance requirements requiring source qualification.

(6) Procedures and criteria required to qualify a source.

(7) Sources of supply and manufacturers’ part numbers.

(8) Cost of the item involved.

(9) Estimated cost to qualify a source.

Technical Manual Contract Requirement (TMCR)

[TM-86-01N]

TM-86-01N 1 April 2009 1 Data Call No: GUEE-0078

Air Force Technical Manual Contract Requirements (TMCR) for

T-38 - A-18 NOISE SUPPRESSOR

NSN: 4920-00-431-4246

ATTACHMENT A, TO CDRL SEQUENCE NUMBER: DI-SESS-81000E/T, EXHIBIT_________________ REQUEST FOR PROPOSAL/CONTRACT:_______________________________________________________

Date: 7 August 2014

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

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS

1. TMCR Tailoring (T). This TMCR document, including the associated tables, matrices and Specification/Standard Interface Records (SIRs) have been tailored specifically, for the A-18 NOISE SUPPRESSOR Program Requirements. Proposals shall be compatible with the Air Force infrastructure and support the A-18 NOISE SUPPRESSOR Program. Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management. A copy is available upon request from the TO Manager. Any terms or procedures found in this document may be researched there.

2. TO Program Scope (T). The Offers shall develop and deliver a new AF technical IAW Section 2, Table 1. No tailoring shall be made to these requirements without prior approval of the TM Manager and Primary Contracting Officer (PCO).

3. Commercial Manuals (T). Commercial manuals shall not be used for this program.

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

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). Offers shall propose a process for notifying the government when additional TO or source data requirements are identified subsequent to contract award. This pro-cess shall require government review and approval of recommended additional requirements prior to contractual approval. Contractor format is acceptable.

6. TO Development (T). The Offers shall development practices and procedures that ensure TOs and data are compatible with the A-18 NOISE SUPPRESSOR program objectives. In addition, TOs shall be written to a scope and depth of coverage sufficient to support the operations and maintenance concepts, and to the Reading Grade Level (RGL) specified in MIL-STD-38784, Standard Practice for Manuals, Technical: General Style and Format Requirements. Sample AFTO Form 124, Attachment 3

Prepared by Dwight McGhee/406 SCMS/GUEE (478)327-5294 7/7/14

2 TM-86-01N 1 April 2009

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). All deliveries of SGML data shall be in a single file instance. Multiple file instances are not authorized.

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. (See Graphics Format Rec-ommendations sheet attachment 1 to this document)

6.3. (T). N/A.

6.4. (T). N/A.

6.5. (T). N/A.

7. TO Numbering (T). Offers shall complete the TO Numbering, Attachment 2 to this document for each new manuals being developed. TO numbers are not required for manuals to be used exclusively by the Offers own personnel. AF procedures for numbering TOs are described in TO 00-5-3 and TO 00-5- 18, AF Technical Order Numbering System. A copy is available upon request from TO Manager.

8. Data Rights (T). Offers shall propose 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 Regu-lation Supplement (DFARS), paragraphs 227-7102 through 227-7104, copies available from TO Man-ager upon request.

8.1. (T). N/A.

8.2. (T). N/A.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices (T). The Offers shall use the below statements for each TO developed.

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 STATEMENT D - Distribution authorized to the Department of Defense and U.S. DoD contractors only (Administrative or op-erational use), (15 June 1985). Other requests shall be referred to 406 SCMS/GUEE, Robins AFB, GA 31098. Questions concerning tech-nical content shall be directed to AFLCMC/WNZEC, Robins AFB, GA 31098.

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 con-tents or reconstruction of the document.

10. TO Quality (T). Offers shall propose a quality assurance program which ensures TOs are prepared 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 re-served for those procedures which would activate explosive devices or present a hazard to personnel or equipment. Offers’ 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). Offers shall propose sufficient conferences and re-views to allow insight into TO development processes and ensure contract compliance. Offeror shall

Prepared by Dwight McGhee/406 SCMS/ GUEE (478)327-5294 7/7/14

TM-86-01N 1 April 2009 3 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 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. (T) The Offers shall deliver all 100% review copies with a letter certifying completion and certification that the information has been reviewed by the contractor and is accu-rate.

10.3. Verification Support (T). Offers shall propose the methods, equipment and personnel required to support government TO Verification. This support should consist of at least engineering and technical publications personnel available to resolve questions resulting from verification activities.

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 will be required at each succeeding review. The TDA parsing in no way relieves the contractor from correcting tagging errors that are noted during the composing effort.

Repeat TDAs shall be required whenever 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. Offers shall propose methods for maintaining accuracy, curren-cy and configuration of existing AF TOs and source data throughout the contract period of performance.

Maintenance includes preparation of TO and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes.

12. TO Delivery (T). TO file delivery formats shall be according to applicable CDRLs and the tailored TM Delivery Requirements Matrices included in Section 2 of this document.

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 returned to the con-tractor for correction then returned to the Air Force 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. A copy is available upon request from TO Manager.

13. Schedules (T). NOTE: AF policy requires delivery of verified TOs prior to or concurrently with delivery of operational equipment to the field (AFI 63-101, Acquisition and Sustainment Lifecycle Management). This policy will determine TO development and delivery schedules throughout the acquisition phase of a program.

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

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

16. Program Specific Requirements.

4 TM-86-01N 1 April 2009

A. The Offers shall develop and deliver a new AF technical manual (Operation and Maintenance Instruction with Illustrated Part Breakdown (IPB) in Work Package Format to support the A-18 NOISE

SUPPRESSOR.

B. The manual(s) shall be developed using the latest version of the development/detail specifications listed in Table 1 of this document. Data delivered for this contract shall be a combination of paper based documents and digital files.

C. SGML files shall be reviewed by the Air Force during the development process to ensure compliance with the approved DTDs. The contractor shall submit copies of their SGML Instance, PDF file of their SGML Instance and separate graphics files used with the SGML Instance with each In-Process review.

D. For Graphics formats, see “Graphics Format Recommendations” attachment 1to this document.

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. The IPB shall require verification of the data based upon the configuration baseline engineering draw-ings and provisioning documentation if provisioning is accomplished. The contractor shall plan for these events in their technical manual development schedule.

F. All electronic files delivered on this project shall be non-password protected and allow unlimited ac-cess to change/modify/or capture the data from the files.

G. In-Process reviews shall be held at the 35% and 70% completion point for each manual under devel-opment. Sample In-Process Completion tables are provided on page, Attachment 4.

H. 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 person-nel 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.

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 and the DTL or PRF specification called out on Section 2, Table 1.

• Check the ASSIST database, http://dodssp.daps.dla.mil/assist.htm, for updated versions of the required TMSS prior to initiating any work on this proposal/contract.

• IPBs are developed IAW MIL-PRF-38807, except that MIL-DTL-87929 will also be used for IPBs combined with work packages.

• Delivery requirements are indicated in the TM Delivery Requirements matrices.

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE A-18 NOISE SUPPRESSOR

Program

Title or Type of Manuals Specification Required

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

a. Operation & Maintenance Instruction Manuals MIL-DTL-87929D

b. With Illustrated Parts Breakdown (see notes) MIL-PRF-38807D

c. Depot Maintenance MIL-DTL-87929D http://dodssp.daps.dla.mil/assist.htm

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 A-18 NOISE SUPPRESSOR

(System/Item)

TM DATA TYPE DELIVERED NEW AF MANUAL.

(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(P/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.

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

• When on-line access is a contractual requirement, copy quantity will normally be Ø (zero).

• For NGS or non-standard TMSS instances, delivery shall include the associated DTDs, FOSIs/Style Sheets, XML schemas, etc.

DELIVERY SCHEDULE

Event Number of days data required prior to event

Technical Review(s) (30 Days)

Verification (30 Days)

Prepublication Review (30 Days)

Final TO Distribution (60 Days)

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

Attn: Dwight McGhee

406 SCMS/GUEE

235 BYRON ST., SUITE 19A

Robins AFB, GA 31098-1670

M(P/G/I) /

M(P/G/I)/

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

Total Copies Required: 2 2 2 1

8 TM-86-01N 1 April 2009

ATTACHMENT 1

Graphics Format Recommendations

GENERAL GUIDELINES

• Single column graphics should not exceed 51 Picas High by 18 Picas Wide.

• Full page graphics should not exceed 51 Picas High by 42 picas Wide.

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

• Recommend 300 DPI for all graphics to help decrease file/PDF sizes due to there being really no discernible quality difference over 600 DPI.

• Directorates must know what graphic file types they can utilize and sustain with software availa-ble on hand and request file types to match.

• The 5 most common graphics file types are: EPS, TIFF, CGM, JPEG & DWG. Each is ad-dressed below:

EPS:

• Raster based images will not be saved as EPS.

• EPS files shall not be a mix of vector and raster images. Vector only.

• Any source data (photos used for tracing etc.), used in aiding of creation of EPS (templates, etc.)

will be deleted from illustration prior to saving/exporting.

• If multiple layers are used, then image is to be flattened into 1 single layer before exporting to minimize file size and reduce possible printing issues.

TIFF:

• B&W raster images should only be saved as Bitmap and not Grayscale, RGB or CMYK.

• Grayscale or Color images (screenshots, etc.) will be saved as such (Grayscale, RGB or CMYK) and will not be bitmap converted using a halftone screen.

• To further aid in file size reduction for storage purposes, images should be compressed using

Group 4 compression when saving/exporting.

CGM:

• Raster based images will not be saved as CGM.

• Any source data used in aiding of creation of CGM (templates, etc.) will be deleted from 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-01N 1 April 2009 9

Attachment 2

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

406 SCMS/GUEE 235 BYRON ST., Suite 19A ROBINS AFB, GA 31098-1670

(Technical Order number assignment may require thirty days.)

PROCUREMENT BUYER OFFICE SYMBOL: TELEPHONE EXT.:

EQUIPMENT SPECIALIST: OFFICE SYMBOL: ES PHONE:

10 TM-86-01N 1 April 2009

Attachment 3

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

TM-86-01N 1 April 2009 11

ATTACHMENT 4

Sample Work Package Format IPR Completion Chart

TO Section 35% Complete 70% Complete Title Page 100% - Front Matter - 70% Numerical Index 100% - WP 001 00 Alphabetical Index 100% - WP 002 00 Foreword 50% 90% WP 003 00 Master List of Special Tools, Test Equipment and Consumables

35% 70%

WP 004 – WP 997 Technical Work Packages At Least 1 WP 100% 70% of Re-maining WP Complete

WP 998 Illustrated Parts Breakdown (If combined) 35% 80% WP 999 00 Difference Data Sheets (If used) 100% -

Example of some Technical Work Packages (Task Oriented) (List not all inclusive, Vendor may need to expand depending upon equipment being developed.)

Theory of Operation Operating Instructions Receiving and Shipping Instructions Remove and Replace Instructions Troubleshooting Schematic Diagrams Inspection Requirements Corrosion Prevention Instructions Initial Setup Fault Isolation Procedures Lubrication Instructions Disassembly Cleaning Post maintenance Operational Checkout

12 TM-86-01N 1 April 2009

SECTION 3. SPECIFICATION/STANDARD INTERFACE RECORDS (SIRS)

NOTES:

• 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 and 6.2b. For this contract enter:

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

6.2b. The issue of the DODISS used in this contract is (enter date).

• 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) 754 ELSG/ILMT.

• Non-government Standards (NGS) shall be provided by the Offers. The Government will not be responsible for providing NGS.

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.

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.

TM-86-01N 1 April 2009 13

6.2o Multiple SMR columns not required. (Paragraph 3.6.7.7.1).