CDRLS_2Jul14.pdf

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:

A TDP XXXX TM OTHER

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

Rotary Wing ASIP/MECSIP SES FD2060-14-30815

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

A008 PRODUCT DRAWINGS/MODELS AND ASSOCIATED LISTS

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

DI-SESS-81000E/T SEE BLK 16 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, 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-28 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

Cyle Capelle 6 March 2014

DD Form 1423-1, Feb 2001 STRAWMAN Revision 24 December 2013 PAGE___1_ OF __8___ PAGES EDATS 2014-28

02 Jul 2014

CONTINUATION OF DD FORM 1423-1 (DI-SESS-81000E/T) Dtd 6 March 2014, EDATS 2014-28

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 5:

Contract Reference. SEE PWS paragraphs: 4.1.8, 4.1.12, 4.1.15, 4.1.16, and 4.2.1.

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, 6 March 2014. Other requests for this document shall be referred to

AFLCMC/WIUEC.”

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. When a specific revision of an engineering document has been previously furnished and approved by a USAF Engineering Data Repository in digital form as a result of a government contract, and is required by this DD Form 1423-1, the same revision data shall not be resubmitted providing it meets the requirements in the DD Form 1423-1 for existing data, unless the data is currently available in a single text searchable document. Previously delivered data shall be identified as having been submitted and approved and shall include the document number, revision, and contract number under which the data were submitted. The receiving USAF Engineering Data Repository shall be identified. This action is required concurrent with all submittals.

3. Within 90 days after successful government verification of baseline being stable, a Bill of Materials (BOM) in accordance with Air Force drawing 9579776 (CAGE 98752) shall be delivered.

4. Within 90 days after successful government verification of baseline being stable, 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 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.).

5. 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. Existing data: Use existing data when possible, provided it meets the following requirements:

a. The rights-in-data are consistent with the current contract stipulations;

b. It is furnished at a cost equal to or less than creating new data;

c. It meets the contract requirements for level of design disclosure;

d. It is identified by a CAGE Code, document number, and title.

e. Any nonstandard symbols, drawing or documentation practices used are explained in the document or in a referenced document.

f. It contains a revision scheme which is compatible with the TDP of which it will be a part or can be modified to a compatible revision scheme.

g. It is part of the effort as defined in the tasking document (SOW, PWS, etc.)

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

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

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

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

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

CONTRACT DAT A REQUIREMENTS LIST Form Approved ( 1 Data Item) OMB 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 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 the above organization. Send completed form to the Government IHuing Contracting Officer for the Contract/PR No. listed in Block E.

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

A TOP --- TM x OTHER

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

ASIP/MECSIP Sustaining Eng Support FD-2060-14-30815

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

A009 Technical Manual Contract Requirements

4. AUTHORITY (Data Acquisition Document No.I 6. REQUIRING OFFICE

TM-86-0lN

, 5. CONTRACT REFERENCE

See Blk 16 AFLCMC/WIUB

7. DD 250 REQ 9. DIST STATEMENT 10.FREQUENCY 12. DATE OF FIRST SUBMISSION

REQUIRED

See Blk 16 See Blk 16

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

c SUBMISSION See Blk 16 See Blk 16

16. REMARKS

BLK 4: General and specific technical manuals requirements see attached TM-86-0lN dated 1 April 2009

BLK 5: SEE PWS paragraphs 4.1.17, 4.2.5.1, 4.2.5.1.1, 4.2.5.1.2, 4.2.5.1.4

BLK 7: FINAL WILL BE SUBMITTED WITH A DD FORM 250 to DODAAC FA8552, via Wide Area Work Flow (WA WF) attention: jasmine.allen. l@us.af.mil/ david.pentecost. l@us.af.mil to collectively account for data previously submitted by Letter ofTransmittals. GOVERNMENT WILL APPROVE/DISAPPROVE WITHIN 30

BUSINESS DAYS OF RECEIPT.

BLK 8: Approval IA W TM-86-0lN, see section 2

Block 9: Distribution authorized to U.S. Government Agencies and their contractors (Administrative or Operational use) (DD MMM YYYY) Other request for this document shall be referred to (AFLCMC/WIUBA).

BLK 10-14: See Section 2 to the attached TMCR 86-0lN

G. PREPARED BY H.DATE I. APPROVED BY

~g~f:~~:=~~IAf. 5 Mar 14 SELLE.RICHARDJ. 1088735 GONZALEZ. WILDEN. IO 18233408 m,;

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED.

14. DISTRIBUTION

a. ADDRESSEE jasmine.allen.1

(alus.af.mil david.pentecost.1

@jus.af.mil

AFLCMC/WIUBD

235 Byron St Suite 230

Robins AFB, GA

31098-1670

15. TOTAL

Di111tollyoagno<!OySFLLERICHARD!l~~7''5016

DN~1s • .,..usoov......,m,oo-Do0 • ...,.,.PK1.o..-U&AF.

~!ELLERJC~JIOSll7J'50)6

Page

b. COPIES

Final Draft

Reg Repro

1 1

1 1

I I

3 0 3

J. DATE

02 Jul 2014 of __ i _ Pages

Adobe Professional 8.0

I

I

I

I

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

TM-86-01N 9 April 2009 1

Air Force Technical Manual Contract Requirements (TMCR)

For

___________________ Sustaining Engineering Support for H-60/H-1 Helicopters___________________

Program Name

Attachment TO CDRL Sequence Number Exhibit

Request for Proposal/Contract

___________________5 March 2014___________________

Date

_____________________H009______________________

TMCR Number

AFLCMC/WIUBD TOMA DATE

AFLCMC/WIUBD FMM DATE

AFLCMC/WIUBD TECH DATA SECTION LEAD DATE

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. Vendors must tailor this TMCR document, including the associated tables, matrices and

Specification/Standard Interface Records (SIRs). The tailored TMCR shall be attached to the CDRL for TO delivery, and shall be included in the proposal as a separate exhibit, referenced in the proposal SOW/PWS. Proposals shall be compatible with the Air Force infrastructure and support the (Sustaining Engineering Support for H-60/H-1 Helicopters) Program’s

Integrated Data System (IDS) requirements. Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management. Any terms or procedures found in this document may be researched there.

2. TO Program Scope. The vendor shall tailor Section 2 to propose new TO types (Table 1) and source data, TO updates, commercial manuals, and TOs prepared to Non Government Standards (NGS). (Table 2) is required to support existing TOs for the (Sustaining Engineering Support for H-60/H-1 Helicopters) program’s objectives.

3. Commercial Manuals. Vendors shall propose the use of existing commercial manuals to the maximum extent possible without impairing program support objectives. The proposal will describe the method used to recommend and submit specif-ic manuals to the government for review and approval.

NOTES: a) Contractors may use Data Item Description (DID) DI-TMSS-80067, Technical Manual (TM) Contractor Fur-nished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices (located at http://dodssp.daps.dla.mil/assist.htm), to provide recommendation data.

b) Government activities will use MIL-PRF-32216, Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data, as a guide for review and acceptance of all recommended commercial http://dodssp.daps.dla.mil/assist.htm

2 TM-86-01N 9 April 2009 manuals, and MIL-DTL-7700, Detail Specification: Flight Manuals, Air Refueling Procedures, and Abbreviated

Checklists, as an additional guide for commercial Flight Manual contents.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between options of-fered 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 mandatory requirements which are part of the Document Type Definition

(DTD) structure.

4.1. AF options in some Joint-Service TMSS have been documented in preliminary SIRs included in Section 3. These preliminary SIRs provide the starting point for further tailoring. Vendors shall complete tailoring of the Joint-Service

TMSS SIRs and provide recommended SIRs for other TMSS or NGS as applicable.

NOTE: TMSS requirements marked “(F)” are specifically for Air Force use; “(A)” is for Army, “(M)” is Marine Corps and

“(N)” is Navy. Comply with all unmarked and “(F)” TMSS requirements as modified by the options in paragraph 6.2.

4.2. (T) Questions concerning TMSS requirements may be resolved by written request and justified suggestions for res-olution submitted through the Procuring Contracting Officer (PCO) and AFLCMC/WIU - 235 Byron Street, Suite 19A, Robins AFB, GA 31098-1647. Deficiencies and suggested improvements shall be submitted to the TMSS Preparing Ac-tivity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

5. Subsequent TO/Data Requirements. Vendors shall propose a process for notifying the government when additional TOs or source data requirements are identified subsequent to contract award. This process shall require government review and approval of recommended additional requirements prior to contractual approval.

NOTE: The recommended notification process is to use CFAE/CFE Notices (DI-TMSS-80067).

6. TO Development. The vendor shall propose TO development practices and procedures that ensure TOs and data are compati-ble with the Air Force Technical Order Concept of Operations (CONOPS) and the Enhanced Technical Information Management

System (ETIMS). 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.

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 new TO files (tagged instances) using Standard Gener-alized Markup Language (SGML) according to the DTDs referenced in the appendix to MIL-STD-38784 and each appli-cable military detail or performance specification (MIL-DTL or MIL-PRF). For existing TOs, the contractor shall con-form to the requirements in Section 2 and Table 2 of this document.

6.2. SGML-tagged TO files shall include required illustration (graphics) files in an approved graphics exchange format

(select “Guidelines” and “Graphics” on the Technical Manual Specifications and Standards (TMSS) web page

(https://techdata.wpafb.af.mil/tmss/index.html, or contact the DFSG ESC/HGGI via e-mail at

DFSG.SBPSGMLSUPPORT@WPAFB.AF.MIL). NOTE: Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible.

6.3. The Vendor may propose use of other Non-Government Standards (NGS) for development of TOs, but must justify this choice based on life-cycle cost savings to the government and compatibility with existing systems identified in the

IDS and the System Support Plan.

6.4. The Vendor shall contact DFSG ESC/HGGI for pre-approval before modifying or developing any new DTDs to support use of NGS, canceled TMSS, or undeveloped TMSS DTDs. If permission is granted, the offeror must submit any proposed DTDs through the PCO and TO Manager for validation of TMSS compatibility with approved electronic

TO (eTO) viewing solutions. New DTDs shall not be developed in lieu of existing DTDs, including those for legacy

TMSS. Rules shall be so constructed that TO output complies with the functional requirements of the associated TMSS, and shall be documented in a SIR. DTDs and rule sets submitted and approved in execution of the contract shall become the property of the Government. Direct questions about the application of SGML tagging to digital TO files to DFSG

ESC/HGGI (DFSG.SBPSGMLSUPPORT@WPAFB.AF.MIL).

TM-86-01N 9 April 2009 3

7. TO Numbering. Vendors shall notify the government of manuals which require TO numbers. TO numbers are not re-quired for manuals to be used exclusively by the vendor’s own personnel. (NOTE: DI-TMSS-80067 may be used to pro-vide the notification.) AF procedures for numbering TOs are described in TO 00-5-3 and TO 00-5-18, AF Technical Order

Numbering System.

8. Data Rights. Government rights in data are specified in the Defense Federal Acquisition Regulation Supplement

(DFARS), paragraphs 227-7102 through 227-7104. Vendors shall propose Unlimited Rights for all source data and TOs pre-pared specifically for the contract.

8.1. If some TOs or source data are copyrighted or contain proprietary data or procedures, vendors may propose Limited

Rights or Government Purpose Rights (GPR) only. Proposed commercial manuals should be provided with at least GPR or Limited Rights. Copyrights shall be according to DFARS paragraphs 227-7103, 7105 or 7106.

8.2. Specifically, if an NGS is proposed, the government shall be given unlimited rights for all business rules (tailoring and application methods and procedures) and documented business processes developed for use in TO development.

Government data rights shall extend to the common source database, transformation style sheets, and other tools or products used to author or display NGS technical data.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Vendors shall determine the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification

Guide (SCG) and DOD 5200.1-R, DODD 5230.24, AFIs 21-303, 31-401 and 61-204, and MIL-STD-38784 (available at http://www.e-publishing.af.mil/ or http://dodssp.daps.dla.mil/assist.htm). The markings and notices shall be reviewed during

In-Process Reviews (IPR).

NOTE: Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon TO con-tent.

10. TO Quality. Vendors 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 reserved for those procedures which would activate explosive devic-es or present a hazard to personnel or equipment. Vendors’ proposals shall describe how the government will be allowed to interact with the contractor’s TO development team.

NOTE: Quality requirements for the Joint Nuclear Weapons Publications System (JNWPS) and for Non-nuclear Explosive

Ordnance Disposal (EOD) Data are contained in TO 11N-1-1 and DOD Directive 5160.62, respectively. The government will performance-tests all JNWPS and EOD TOs.

10.1. (T) Conferences and Technical Reviews. Vendors shall propose sufficient conferences and reviews to allow in-sight into TO development processes and ensure contract compliance. Vendors shall host an initial Guidance Confer-ence 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) ensure TOs are being de-veloped according to contract requirements and that open discrepancies are cleared prior to publication. IPRs typically consist of a 40%, 80%, Verification and Final Review. IPRs are set up at the discretion of the TOMA and FMM and will be addressed at the Guidance Conference. The TOMA and FMM assigned to the affected MDS must be notified 30 days prior to any conferences or reviews. For eTO based programs, IPRs subsequent to the initial review need to be accom-plished using the approved viewing presentation system.

10.2. TO Certification. Vendors shall propose their method for documenting certification that TO procedures are accu-rate, adequate, current, safe and usable for their intended purposes. Vendors shall notify the government at least 180 days prior of the need for any Government Furnished Information/Government Furnished Equipment (GFI/GFE) re-quired to perform certification tasks. Certification documentation shall be provided to the government prior to verifica-tion delivery.

10.3. (T) Verification Support. Vendors shall propose the methods, equipment and personnel required to support gov-ernment TO Verification. This support should consist of at least a Lead Technical Writer, knowledgeable on the system and a System Qualified Engineer.

http://www.e-publishing.af.mil/

4 TM-86-01N 9 April 2009

10.4. Technical Data Assessment (TDA - originally called First Article Testing). The program office, with the assistance of

DFSG ESC/HGGI and the contractor, will determine the TDA requirements for each TO type. The contractor will submit an in-work sample of each type of SGML-tagged TO file to the program office concurrent with the first IPR, for TDA to verify compliance of the digital files to Air Force DSSs. Additional TDAs may be required based on initial results. 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 de-liver a representative percentage of Indexed Portable Document Format (IPDF) TO files to verify indexing compliance with the Technical Order Conversion Requirements (TOCR).

11. (T) TO and Source Data Maintenance. Vendors shall propose methods for maintaining accuracy, currency and configu-ration of TOs and source data throughout the contract period of performance. Maintenance includes preparation of TOs and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes. Editorial and Technical Content cut-off of technical data will be the close and acceptance of the Verification minutes and closure of all action items from that Verification (IPR). This requirement is to update to the latest release of

Technical Order changes until the acceptance of the Verification (IPR) minutes and closure of ALL action items from that

Verification (IPR). Offerors/Vendors will establish a TODO account and assign a TODO in accordance with TO 00-5-1, AF

Technical Order System, in order to receive the latest issued TOs through ETIMS.

11.1. (T) In order to maintain accuracy, currency and configuration of Air Force TOs, Vendors must have a TODO ac-count. If an account has not been established, the Vendor must establish a TODO account upon contract award by pro-cessing an AFTO Form 43, USAF Technical Order Distribution Office (TODO) Assignment or Change Request in ac-cordance with TO 00-5-1. The IBM Lotus version of the AFTO Form 43 can be downloaded at http://www.e-publishing.af.mil/. Alternatively, prospective contractor TODOs may download and use the pdf version of the AFTO

Form 43 at https://techdata.wpafb.af.mil/toprac/forms.htm. All versions of the form include detailed completion instruc-tions.

12. TO Delivery. Vendors shall propose practices and procedures for secure access to or delivery of digital TO files, includ-ing those for Preliminary TOs (PTOs), source data, reproduction masters, and program support data. Practices and proce-dures shall be compatible with the program’s IDS. TO file delivery formats shall be according to applicable CDRLs and the tailored TM Delivery Requirements Matrices included in Section 2 of this document. Paper only TO delivery is not acceptable for final delivery of TOs. EXCEPTION: For Commercial Manuals not available digitally.

12.1. SGML-Tagged Files. 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 to the levels provided in the DTD.

NOTE: The government will parse the files prior to acceptance using the public domain “SGMLS Parser.”

12.2. Indexed Adobe™ Portable Document Format (IPDF) Files. The contractor shall validate indexing of PDF TO files using the specifications contained in the Technical Order Conversion Requirements (TOCR).

13. (T) Schedules. Vendors shall include TO program events and schedules in their proposed Integrated Master Plan (IMP) and Integrated Master Schedule (IMS), and update the IMS throughout the period of performance.

NOTE: AF policy requires delivery of verified TOs prior to or concurrently with delivery of operational equipment to the field (AFI 21-303, Technical Orders). This policy will determine TO development and delivery schedules throughout the acquisition phase of a program. Any change to the IMS must be coordinated with the TOMA and FMM assigned to the af-fected MDS. A copy of the updated IMS will be provided to the TOMA and FMM.

14. Time Compliance Technical Orders (TCTOs). Vendors shall propose practices and procedures to develop AF TCTOs and related TO updates when tasked as part of the approval process for Engineering Change Proposals (ECPs) to configured items. Costs for TCTO package development must be included in ECP Costs – not included as direct proposal costs.

NOTE: ECPs are reviewed and approved by the Government’s Configuration Control Board (CCB). When the CCB de-cides that a TCTO is the appropriate method of implementation, the contractor may be requested to develop the TCTO pack-age for Air Force coordination and approval. See TO 00-5-15 (Air Force Time Compliance Technical order Process) for a detailed description of TCTO processes.

http://www.e-publishing.af.mil/ http://www.e-publishing.af.mil/ https://techdata.wpafb.af.mil/toprac/forms.htm

TM-86-01N 9 April 2009 5

15. (T) TO Reproduction Management. Vendors shall propose practices and procedures for managing the program’s Pre-liminary TO reproduction requirements. MIL-HDBK-38790, Printing Production of Technical Manuals, may be used as guidance for TO printing format, paper weights, layout requirements, etc.

NOTE: Reproduction management for formal TO printing includes assembly of a print package (reproduction media, a re-production assembly sheet).

6 TM-86-01N 9 April 2009

SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS FOR ASSIGNED TOMA/FMM CURRENTLY WORKING PACKAGE

NOTES:

Mark the TM Type Selection Tables indicating the applicable TO types and related specifications. For additional interface requirements see the program-specific Government Concept of Operations (GCO).

All page-based TOs developed under this contract must conform to the general style and format requirements of MIL-

STD-38784.

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

Manuals delivered using this table and DI-TMSS-80067, CFAE/CFE Notices, must be reviewed and approved by the Air

Force prior to delivery.

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

All checklists, except aircrew and nuclear weapons checklists, are developed IAW MIL-PRF-5096.

MIL-PRF-83495 requires MIL-HDBK-863 to be levied on engineering data for preparation of end item wiring data and schematic diagrams.

Editorial and Technical Content cut-off will be at the close and acceptance of the Verification minutes and closure of all action items from that Verification (IPR).

Delivery requirements are indicated in the TM Delivery Requirements matrices, Part B.

Change package format deliveries will be with accompanying back-up pages. Source data deliveries will be delivered in change package format without accompanying back-up pages. No manuscript source will be accepted.

FrameMaker 11.0 or earlier version of FrameMaker file format (For FMs – using Government furnished tags).

All change/source pages will be vector art and searchable text format, no raster art accepted. Back-up pages may be raster art.

For further information on the Air Force Vision and TO Concept of Operations (CONOPS), see AF Portal URL https://wwwd.my.af.mil/afknprod/ASPs/DocMan/DocMain.asp?Filter=OO-EN-TO-PI&FolderID=OO-EN-TO-PI-

15&Tab=0.

In addition to delivery requirements stated above, all Technical Data may be dropped off at AFLCMC/WIUBD. (Please make sure that you have a cover page with name of company, what status the publications are at (IPR, 40/80%, Pre-Pub, etc.) what TCTO number affects the manuals and contact information.

https://wwwd.my.af.mil/afknprod/ASPs/DocMan/DocMain.asp?Filter=OO-EN-TO-PI&FolderID=OO-EN-TO-PI-15&Tab=0 https://wwwd.my.af.mil/afknprod/ASPs/DocMan/DocMain.asp?Filter=OO-EN-TO-PI&FolderID=OO-EN-TO-PI-15&Tab=0

TM-86-01N 9 April 2009 7

PART A – TM TYPE SELECTION TABLES.

TABLE 1

TMSS REQUIREMENTS FOR THE (Sustaining Engineering Support for H-60/H-1 Helicopters)

(System/Component)

Title or Type of Manuals Specification Required

1. Inspection TOs MIL-PRF-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. Workcards

e. Inspection Requirements Cards

f. Flow/Sequence Charts

g. Checklists

(1) Maintenance/Operations (Non-Aircrew)

(2) Operations (Aircrew)

2. Cargo Aircraft Loading and Offloading TOs MIL-PRF-5288

a. Manual

b. Checklists

3. Weight and Balance (Aircraft) MIL-PRF-5920

a. Loading Data Manual

b. Sample Basic Weight Checklists

4. Flight Manuals (see notes) MIL-DTL-7700

a. Flight Manual

b. Performance Data Manual

c. Air Refueling Manual

d. Air Refueling Checklist

5. List of Applicable Publications MIL-PRF-8031

6. Structural Repair Manuals (for Aircraft) MIL-PRF-9854

7. Munitions/Weapons Loading Procedures, Non- nuclear and Nuclear MIL-PRF-9977

a. Nuclear Weapons Basic Information and Loading Procedures

b. Nuclear Weapons Loading Procedures

c. Non-nuclear Munitions Basic

d. Non-nuclear Loading Procedures

e. Integrated Combat Turnaround Procedures

f. Non-nuclear Munitions Loading Standard Data Packages (SDPs)

g. Loading Procedures Checklists

h. Integrated Loading Procedures Checklists

i. Nuclear Weapons Loading Procedure Checklists

j. Integrated Combat Turnaround Procedures Checklists

k. NATO Stage B Cross-Servicing Checklists

8. Space Operations and Support Documentation TOs

-- Commercial specification (all space systems & missiles)

-- MILSPEC (Intercontinental Ballistic Missiles)

-- MILSPEC (Space Systems)

ANSI/AIAA-R024-1993

MIL-PRF-38311

MIL-PRF-38314

a. Operations Manual

b. Operations Checklists

c. Technical Manuals and Related Checklists

8 TM-86-01N 9 April 2009

(System/Component)

Title or Type of Manuals Specification Required

9. Nuclear and Non-nuclear Weapon Delivery and Aircrew Procedures Manuals and Checklists

MIL-PRF-38384

a. Non-nuclear Weapon Delivery Manual (Strategic Bomber &

Tactical Aircraft)

b. Nuclear Bomb Delivery Manual (Strategic Bomber Aircraft)

c. Aircrew Nuclear Weapon Delivery Manual (Strategic Bomber

Aircraft)

d. Aircrew Nuclear Weapon Delivery Manual (Tactical Aircraft)

e. Non-nuclear Weapon Delivery Checklist (Strategic Bomber &

Tactical Aircraft)

f. Nuclear Bomb Delivery Checklist (Strategic Bomber Aircraft)

g. Aircrew Nuclear Weapon Delivery Checklist (Tactical Aircraft)

h. Non-nuclear Weapon Delivery Source Data Packages

10. Work Unit Code Manual MIL-PRF-38769

11. Calibration Procedures MIL-PRF-38793

12. Time Compliance Technical Orders (TCTOs) MIL-DTL-38804

13. Aircraft Battle Damage Assessment and Repair TOs MIL-PRF-87158

14. Illustrated Parts Breakdown MIL-PRF-38807

15. On-Equipment Organizational…