Exhibit_A_CDRLs.pdf

CONTRACT DATA REQUIREMENTS LIST (CORL)

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 comm ents regarding this burden estimate or any other aspect of this collection of inform ation, including suggestions for reducing this burden to Departm ent of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports .

1215 Jefferson Davis Highway, Suite 1204. Arlington. VA 22202-4302. and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington DC 20503. 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. in Block E.

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

TOP __ TM --- OTHER NI~ R!iF: DQD 5Q1Q 12-M

D. SYSTEMllTEM IE. CONTRACT/PR NO. F. CONTRACTOR

ESAS 2

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

A0001 STATUS REPORT

4. AUTHORITY (Data Acqu1srtion Document No.) , 5. CONTRACT REFERENCE 6. REQUIRING OFFICE Dl-MGMT-80368A PWS Para 1.1THRU1.10.1 AFTACfTTXM

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION LT REQUIRED MTHLY SEE BLK 16 b. COPIES

8. APPCODE SEE BLK 16 11. ASOFDATE 13. DATE IF SUBSEQUENT SUBM. a. ADDRESSEE final N/A SEE BLK 16 SEE BLK 16 draft eg epr

16. REMARKS 16.FTACfTTXM 1

25AF/PK T

SLK 4 • DID PARAGRAPH 3.3 APPENDICES SHALL INCLUDE A COPY OF THE INVOICES FOR THE

~CCOUNTING PERIOD.

SLK 9 - DISTRIBUTION STATEMENT B: ADMINISTRATIVE OR OPERATIONAL PURPOSES. FURTHER

REQUEST FOR DISSEMINATION SHOULD BE REFERRED TO AFTACITTXM.

BLK 11 -THE CLOSE OF THE ACCOUNTING PERIOD(S) FOLLOWING CONTRACT AWARD THAT BEST

ALIGNS WITH THE CALENDAR MONTH. THE REPORT WILL DOCUMENT ACTIVITIES PERFORMED

DURING THE CORRESPONDING INVOICE/REPORTING PERIOD, WHICH MAY BE A MONTH OR A

'°OUR WEEK CYCLE.

BLK 12 & 13 - CONTRACTOR SHALL DELIVER THE FIRST AND SUBSEQUENT REPORT WITHIN 15

CALENDAR DAYS AFTER THE CLOSE OF THE MONTHLY ACCOUNTING CYCLE.

BLK 14 & 15- SUBMISSION SHOULD BE IN MICROSOFT OFFICE (2007 OR GOVERNMENrS CURRENT

VERSION) COMPATIBLE FORMAT AND BE PROVIDED ELECTRONICALLY OR ON A CD.

15. TOTAL ·----- - --> 2

G. PREPARED BY r· DATE I'- APPROVED BY J . DATE

DD Form 1423-1. JUN 90

Previous ed1t1ons are obsolete Page 1 of 1 Pages

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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 this burden to Department of Defense. Washington Headquarters Services. Directorate for Information Operations and Reports .

1215 Jefferson Davis Highway, Suite 1204. Arlington. VA 22202-4302, and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188). Washington DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the government Issuing Contracting Officer for the Co~tract/PR No. in Block E.

A. CONTRACT LINE ITEM NO. ,B. EXHIBIT r· CATEGORY:

TOP_ TM --- OTHER NIA REF: DQD 5010.12-M

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

ESAS 2

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

A0002 FUNDS AND MAN-HOURS EXPENDITURE REPORT

4. AUTHORITY (Data Acquisition Document No.) 15. CONTRACT REFERENCE 6. REQUIRING OFFICE Dl-FNCL-80331A PWS Para 1.8. THRU 1.10.2 AFTACITTXM

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14 DISTRIBUTION LT REQUIRED MTHLY SEE BLK 16 b. COPIES

8 APP CODE SEE BLK 16 11. AS OF DATE 13. DATE IF SUBSEQUENT SUBM. a ADDRESSEE final NIA SEE BLK 16 SEE BLK 16 Id raft res epr

16. REMARKS ~FTACITTXM 1

5AF/PK 1

BLK 4 - REPORT SHALL BE INCORPORATED WITH DATA ITEM NUMBER A0001 . DID PARAGRAPH 4.1

CLARIFICATION - MAN HOURS SHALL BE REPORTED BY LABOR CATEGORY AND GROUPED BY

bRIMARY PWS TASKS OUTLINED IN SECTION 1.0. ADDITIONAL TRACEABILITY TO TASK REQUEST

MAY BE REQUIRED. AS IDENTIFIED BY THE GOVERNMENT PROGRAM OFFICE.

BLK 9 - DISTRIBUTION STATEMENT B: ADMINISTRATIVE OR OPERATIONAL PURPOSES. FURTHER

REQUEST FOR DISSEMINATION SHOULD BE REFERRED TO AFTACITTXM.

BLK 11 ·THE CLOSE OF THE ACCOUNTING PERIOD(S) FOLLOWING CONTRACT AWARD THAT BEST

!ALIGNS WITH THE CALENDAR MONTH. THE REPORT WILL DOCUMENT ACTIVITIES PERFORMED

)DURING THE CORRESPONDING INVOICE/REPORTING PERIOD. WHICH MAY BE A MONTH OR A

ll=OUR WEEK CYCLE.

BLK 12 & 13 - CONTRACTOR SHALL DELIVER THE FIRST AND SUBSEQUENT REPORT WITHIN 15

lcALENDAR DAYS AFTER THE CLOSE OF THE MONTHLY ACCOUNTING CYCLE.

BLK 14 & 15 - SUBMISSION SHOULD BE IN MICROSOFT EXCEL (2007 OR GOVERNMENrS CURRENT

WERSION) COMPATIBLE FORMAT AND BE PROVIDED ELECTRONICALLY OR ON A CD.

15. TOTAL---------> 1

G PREPARED BY ,H. DATE 11. APPROVED BY J . DATE

DD Form 1423-1. JUN 90 Previous editions are obsolete Page 1 of 1 Pages

17. PRICE GROUP

CONTRACT DATA REQUIREME TS LIST (CORL)

Public reporting burden for this collection of information is estimated to average 11 O 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 this burden to Department of Defense. Washington Headquarters Services. Directorate for Information Operations and Reports , 1215 Jefferson Davis Highway. Suite 1204, Arlington. VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188). Washington DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the government Issuing Contracting Officer for the ContracVPR No. in Block E.

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

TOP _ _ TM --- OTHER NIA REF· QQQ 5010 1Z-M

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

ESAS2

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

A0003 CONTRACT FUNDS STATUS REPORT (CFSR)

4. AUTHORITY (Dara Acquisition Document No.) , 5. CONTRACT REFERENCE 6. REQUIRING OFFICE Dl-MGMT-81468 PWS Para 1.8- 1.9, 1.10.1, & 1.10.2 AFTACITTXM

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION LT REQUIRED QTRLY SEE BLK 16 b. COPIES

8. APP CODE SEE BLK 16 11. ASOFOATE 13. DATE IF SUBSEQUENT SUBM. a. ADDRESSEE final NIA SEE BLK 16 SEE BLK 16 draft eg epr

16. REMARKS ""FTACITTXM 1

125 AF/PK 1

13LK 4 - PARAGRAPH 10.2.11 .1 SHALL REFLECT THE TASK AREAS.

aLK 9 - DISTRIBUTION STATEMENT B: ADMINISTRATIVE OR OPERATIONAL PURPOSES. FURTHER

REQUEST FOR DISSEMINATION SHOULD BE REFERRED TO AFTACITTXM.

'3LK 11 - THE CLOSE OF THE ACCOUNTING PERIOD(S) FOLLOWING CONTRACT AWARD THAT BEST

""LIGNS WITH THE CALENDAR MONTH. THE REPORT WILL DOCUMENT ACTIVITIES PERFORMED

PURING THE CORRESPONDING INVOICEIREPORTING PERIOD, WHICH MAY BE A MONTH OR A

FOUR WEEK CYCLE.

'3LK 12 & 13 - CONTRACTOR SHALL DELIVER THE FIRST AND SUBSEQUENT REPORT WITHIN 15

K'.;ALENDAR DAYS AFTER THE CLOSE OF THE MONTHLY ACCOUNTING CYCLE.

13LK 14 & 15 - SUBMISSION SHOULD BE IN MICROSOFT OFFICE (2007 OR GOVERNMENrS CURRENT

~ERSION) COMPATIBLE FORMAT AND BE PROVIDED ELECTRONCIALLY OR ON A CO.

15. TOTAL······ ···> 1

G. PREPARED BY ,H. DATE 11. APPROVED BY J. DATE

DD Form 1423-1 . JUN 90

Previous ed1t1ons are obsolete Page 1 of 1 Pages

17. PRICE GROUP

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 this burden to Department of Defense. Washington Headquarters Services. Directorate for Information Operations and Reports.

1215 Jefferson Davis Highway, Suite 1204. Arlington, VA 22202-4302. and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188). Washington DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the government Issuing Contracting Officer for the ContracUPR No. in Block E.

A. CONTRACT LINE ITEM NO. IB. EXHIBIT IC. CATEGORY:

TOP __ TM --- OTHER NIA RfiiF · QQD 5010 1z-M

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

ESAS2

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

A0004 CONFERENCE MINUTES

4. AUTHORITY (Data Acquis111on Document No.) 15. CONTRACT REFERENCE 6. REQUIRING OFFICE D l-ADMN-81250A PWS Para 1.1. 1.8. & 1.9 AFTACITTXM

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION LT REQUIRED ASREO SEE BLK 16 b COPIES

8. APP CODE SEE BLK 16 11 . AS OF DATE 13. DATE IF SUBSEQUENT SUBM. a . ADDRESSEE final N/A SEE BLK 16 SEE BLK 16 ~raft reg epr

16. REMARKS AFTAC/TTXM 1

15AF/PK T

BLK 9 - DISTRIBUT ION STATEMENT B· ADMINISTRATIVE OR OPERATIONAL PURPOSES. FURTHER

REQUEST FOR DISSEMINATION SHOULD BE REFERRED TO AFTACITTXM.

BLK 11 - DATE OF THE MEETING.

BLK 12 & 13 - THE MINUTES SHALL BE SUBMIITED 5 WORKING DAYS AFTER THE

MEETING/REVIEW.

BLK 14 & 15 - SUBMISSION SHOULD BE IN MICROSOFT OFFICE (2007 O R GOVERNMENT'S CURRENT

VERSION) COMPATIBLE FORMAT AND BE PROVIDED ELECTRONICALLY OR O N A CD.

15. TOTAL -- -- - - - --> 1

G. PREPARED BY IH DATE 11. APPROVED BY J . DATE

DD Form 1423-1. JUN 90

Previous editions are obsolete Page 1 of 1 Pages

17. PRICE GROUP

CONTRACT DATA REQUIREMENTS LI ST (CORL)

Public reporting burden for this collection of information is estimated to average 110 hours per response. including the lime for reviewing instructions. searching existing data sources. gathering and maintaining the data needed. and completing and revieYling the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information. including suggestions for reducing this burden to Department of Defense. Washington Headquarters Services, Directorate for Information Operations and Reports.

1215 Jefferson Davis Highway, Suite 1204, Arlington. VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the government Issuing Contracting Officer for the ContracVPR No. in Block E.

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

TDP_X_ TM --- OTHER

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

ESAS 2

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

A0005 TECHNICAL REPORT - STUDY/SERVICES

4. AUTHORITY (Data Acquisition Document No.) , 5. CONTRACT REFERENCE 6 . REQUIRING OFFICE Dl-MISC-80508B PWS Para 1.1THRU1.9 AFTACITTXM

7. DD 250 REQ 9. D IST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION DD REQUIRED ASREQ SEE BLK 16 b. COPIES

8. APPCODE SEE BLK 16 11. AS OF DATE 13. DATE IF SUBSEQUENT SUBM a . ADDRESSEE final A NIA SEE BLK 16 ~raft reg epr

16. REMARKS AFTACITTXM 1 1

25 AF/PK LT

BLK 8 - THE GOVERNMENT HAS TEN (10) WORKING DAYS TO REVIEW THE PRELIMINARY DRAFT.

THE CONTRACTOR HAS FIVE (5) WORKING DAYS. AFTER RECEIPT OF GOVERNMENT COMMENTS.

TO PREPARE AND DELNER THE FINAL SUBMISSION. CRITERIA FOR APPROVAL SHALL BE

CORRECT CONTENT AND FORMAT

BLK 9 - DISTRIBUTION STATEMENT B: ADMINISTRATIVE OR OPERATIONAL PURPOSES. FURTHER

REQUEST FOR DISSEMINATION SHOULD BE REFERRED TO AFTAC/TTXM.

BLK 10 - FIRST WORKDAY FOLLOWING THE TECHNICAL INTERCHANGE MEETING IDENTIFYING THE

REQUIREMENT.

BLK 12 & 13-SUBMISSION DATES TO BE DEFINED IN THE TECHNICAL INTERCHANGE MEETING

AND REPORTED IN THE MONTHLY STATUS REPORT (A0001)

BLK 14 & 15 -ADDITIONAL DISTRIBUTION REQUIREMENTS MAY BE IDENTIFIED IN THE TECHNICAL

INTERCHANGE MEETING. DELIVERIES SHOULD BE IN MICROSOFT OFFICE (2007 OR

K;OVERNMENT'S CURRENT VERSION) COMPATIBLE FORMAT AND BE PROVIDED ELECTRONICALLY

K>R ONA CD.

15. TOTAL - - - - - - - - -> 1 1

G . PREPARED BY ,H. DATE 11 APPROVED BY J . DATE

DD Form 1423-1, JUN 90

Previous edrtrons are obsolete Page 1 of 1 Pages

17. PRICE GROUP

CONTRACT DATA REQUIREMENTS LIST (CDRL}

Public reporting burden for this collection of information is estimated to average 11 O 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 this burden to Department of Defense. Washington Headquarters Services. Directorate for Information Operations and Reports.

1215 Jefferson Davis Highway. Suite 1204, Arlington. VA 22202-4302. and to the Office of Management and Budget. Paperwork Reduction Project (0704-0188), Washington DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the government Issuing Contracting Officer for the ContracUPR No. in Block E.

A. CONTRACT LINE ITEM NO. IB. EXHIBIT I c. CATEGORY:

TOP _ TM - - - OTHER N/A R!;F· DQD 501Q 1~-M

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

ESAS 2

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

A0006 INTEGRATED MASTER SCHEDULE (IMS)

4, AUTHORITY (Data Acquisition Document No.) 15. CONTRACT REFERENCE 6. REQUIRING OFFICE 01-MISC-81183A PWS Para 1.1THRU1 .10.2 AFTACITTXM

7. 00 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION 00 REQUIRED SEE BLK 16 SEE BLK 16 b. COPIES

8. APP CODE SEE BLK 16 11. ASOFOATE 13. DATE IF SUBSEQUENT SUBM. a. ADDRESSEE final A SEE BLK 16 SEE BLK 16 draft eg epr

16. REMARKS AFTACITTXM 1

25AF/PK T

BLK 4 - PARAGRAPH 2 CONTENT SHALL CONTAIN EVENTS ANO MILESTONES, ACCOMPLISHMENTS.

~RITERIA, CORL DELIVERY DATES, ANO ACTIVITIES.

BLK 9 - DISTRIBUTION STATEMENT B: ADMINISTRATIVE OR OPERATIONAL PURPOSES. FURTHER REQUEST FOR DISSEMINATION SHOULD BE REFERRED TO AFTACfTTXM.

BLK 11 - THE CL0SE OF THE ACCOUNTING PERIOO(S) FOLLOWING CONTRACT AWARD THAT BEST

ALIGNS WITH THE CALENDAR MONTH.

BLK 12 & 13 - CONTRACTOR SHALL DELIVER THE FIRST ANO SUBSEQUENT REPORT WITHIN 15

CALENDAR DAYS AFTER THE CLOSE OF THE MONTHLY ACCOUNTING CYCLE.

BLK 14 & 15 - ADDITIONAL DISTRIBUTION REQUIREMENTS MAY BE IDENTIFIED IN THE TECHNICAL

NTERCHANGE MEETING DELIVERIES SHOULD BE IN MICROSOFT OFFICE (2010 OR

GOVERNMENrS CURRENT VERSION) COMPATIBLE FORMAT (PDF IS ACCEPTABLE WITH

GOVERNMENT PROGRAM MANAGER APPROVAL) ANO BE PROVIDED ELECTRONICALLY OR ON A

CD.

15. TOTAL- -·-- -- --> 1

G. PREPARED BY IH DATE 11. APPROVED BY J . DATE

DD Form 1423-1. JUN 90

Previous ed1t1ons are obsolete Page 1 of 1 Pages

17. PRICE GROUP

Public reporting burden for this collection of information is estimated lo average 110 hours per response. including the lime 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 this burden to Department of Defense. Washington Headquarters Services. Directorate for Information Operations and Reports , 1215 Jefferson Davis Highway, Suite 1204. Arlington. VA 22202-4302. and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188). Washington DC 20503. Please DO NOT RETURN your form to etther of these addresses. Send completed form lo the government Issuing Contracting Officer for the Contract/PR No . in Block E.

A. CONTRACT LINE ITEM NO. IB. EXHIBIT ,C. CATEGORY:

TOP TM -- OTHER NIA REF: OQO 5Q1Q.02-M

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

ESAS2

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

A0007 AF TECHNICAL MANUAL CONTRACT REQUIREMENTS

4. AUTHORITY (Data Acquisition Document No.) , 5. CONTRACT REFERENCE 6. REQUIRING OFFICE TM-86-01N PWS Para 1.4 THRU 1.8 AFTACITTXM

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION DD REQUIRED ASREQ SEE BLK 16 b COPIES

8. APPCODE SEE BLK 16 11. ASOFDATE 13. DATE IF SUBSEQUENT SUBM. a. ADDRESSEE final A SEE BLK 16 SEE BLK 16 ~raft eg epr

16. REMARKS ~FTACITTXM 1 1

25 AF/PK LT

SLK 4 - SEE ATTACHMENT TM-86-01 N FOR SPECIFIC TAILORING.

SLK 8 - THE GOVERNMENT HAS TEN (10) WORKING DAYS TO REVIEW THE PRELIMINARY DRAFT.

trHE CONTRACTOR HAS FIVE (5) WORKING DAYS, AFTER RECEIPT OF GOVERNMENT COMMENTS, tro PREPARE AND DELIVER THE FINAL SUBMISSION. CRITERIA FOR APPROVAL SHALL BE

CORRECT CONTENT ANO FORMAT

BLK 9 - DISTRIBUTION STATEMENT B: ADMINISTRATIVE OR OPERATIONAL PURPOSES. FURTHER

REQUEST FOR DISSEMINATION SHOULD BE REFERRED TO AFTACITTXM.

BLK 10 & 11 - FIRST WORKDAY FOLLOWING THE TECHNICAL INTERCHANGE MEETING IDENTIFYING trHE REQUIREMENT.

SLK 12 & 13 ·SUBMISSION OATES TO BE DEFINED IN THE TECHNICAL INTERCHANGE MEETING

[AND REPORTED IN THE MONTHLY STATUS REPORT (A0001)

BLK 14 & 15 · ADDITIONAL DISTRIBUTION REQUIREMENTS MAY BE IDENTIFIED IN THE TECHNICAL

NTERCHANGE MEETING. DELIVERIES SHOULD BE IN MICROSOFT OFFICE (2007 OR

GOVERNMENT'S CURRENT VERSION) COMPATIBLE FORMAT AND BE PROVIDED ELECTRONICALLY

bR ONA CD.

15. TOTAL·········> 1 1

G, PREPARED BY IH. DATE 11. APPROVED BY J . DATE

DD Form 1423·1. JUN 90

Previous ed1t1ons are obsolete Page 1 of 1 Pages

17 PRICE GROUP

TM-86-0lN 1 April 2009

Air Force Technical Manual Contract Requirements (TMCR) for

(Program/Modification/Mi litary System)

ATTACHMENT______, TO CORL SEQUENCE NUMBER _____ ____, EXHIBIT _______ _ _

REQUEST FOR PROPOSAUCONTRACT:

Date:

Technical Manualffechnical Order requirements contained herein have been cleared for use by OMB Paperwork Reduction Project No. 0704-0 188.

NOTE: Items in italics must be tailored by the TO Manager before placing the 1MCR in an exhibit to the RFP. sys tem performance specification or in the proposal technical library. The TMCR must be referenced in RFP section J. If some or all of the TO program requirements are included in RFP Section L (Instructions to Ojferor), remove them from the TMCR. URls are either public access sites, or are on the Air Force Portal - contractors may access the Portal using an External Certificate Alllhority (ECA) when sponsored by a DoD activity. Delete this note prior to placing the T!v!CR in the RFP.

SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREM ENTS

1. TMCR Tai loring. Offerors must tailor thi s TMCR document, including the associated tables, matri ces and Specification/Standard Interface Records (SIRs). The tailored TMCR shall be attached to the CORL for TO delivery, and shall be included in the proposal as a separate exhibit, referenced in the pro posal SOW. Proposals sha ll be compatible with the Air Force infrastructure and support the {program name) Program 's Integrated Data System (IDS) requirements located (enter RFP location of IDS). Air Force TO Acquisition procedures. including procedures for tailoring thi s document. are found in TO 00- 5-3. AF Technical Order Life Cycle Management. located on the Internet at http://www.tinker.af.mi l/ library/ factsheets/ factsheet.asp?id=6082. Any terms or procedures found in this document may be researched there.

2. TO Program Scope. The offeror shall tailor Section 2 to propose the TO types (Table I) and source data, TO updates, commercial manuals, and TOs prepared to Non Government Standards (NGS) (Table 2) required to support the (nrogram name) program's objectives.

3. Commercial Manuals. Offerors shall propose the use of existing commercial manuals to the max i mum extent possible without impairing program support objectives. The proposal wi ll describe the method used to recommend and submit specific manuals to the government for review and approval.

NOTES: a) Contractors may use Data Item Description (DID) Dl-TMSS-80067, Technical Manual (IM) Contractor Furnished Aeronautical Equipmenl or Contraclor Furnished Equipmenl (CF AEICFE) Notices (located at htlp ://dodssp.daps .dla.mil/ass ist.hlm), to provide recommendation data. b) Govern ment activities will use MIL-PRF-322 I 6, Evaluation of Commercial Off-The-Shelf (COTS) Manuals and Preparation of Supplemental Data, as a guide for review and acceptance of all recommended commer cial manuals, and M IL-DTL-7700, Detail Spec(fication: Flight Manuals. Air Refueling Procedures, And Abbreviated Checklists, as an additional guide fo r commercial Fl ight Manual contents.

4. Technical Manual Specifications and Standards CTMSS) 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. AF options in some Joint-Service TMSS have been documented in preliminary SIRs included in Section 3. These preliminary SlRs provide the starting point for further tailoring. Offerors shall complete tailoring of the Joint-Service TMSS SIRs and provide recommended SI Rs for other TMSS or NGS as applicable. NOTE: TMSS requirements marked ·'(F)'' are specifically fo r Air Force use;

2 TM-86-0lN 1 April 2009

·'(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. Questions concerning TMSS requirements may be resolved by written request and justified suggestions for resolution submitted through the Procuring Contracting Officer (PCO) and (enter name, office symbol, address and phone number of TO Manager). Deficiencies and suggested im provements shall be submitted to the TMSS Preparing Activity (PA). Approved recommendations, corrections and clarifications wi ll be maintained with contract documentation.

5. Subsequent TO/Data Requirements. Offerers shall propose a process fo r noti fy ing the government when add itional TO or source data requirements are identified subsequent to contract award. Th is pro cess shall require government rev iew and approval of recommended additional requirements prior to contractual approval. NOTE: The recommended notification process is to use CF AE/CFE Notices (DI

TMSS-80067).

6. TO Development. The offeror shall propose TO development practices and procedures that ensure TOs and data are compatible with the Air Force Technical Order Concept of Operations (CONOPS) (on the AF Portal at https://wwwd.my.af.mil/atknprod/DocView.asp?DoclD=I689861) and the Enhanced Technical Information Management System (ETIMS). In addition, TOs shall be written to a scope and depth of cov erage su fficient 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-ori ented Military Specification (MILSPEC) TOs shal l be formatted with text, graphics and de livery accord ing 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 mi litary detail or performance specification (MIL-DTL or MIL-PRF).

6.2. SGML-tagged TO files shall include required illustration (graphics) files in an approved graphics exchange fo rmat (select "Guidelines" and "Graphics" on the Technical Manual Specifica tions and Standards (TMSS) web page (https://techdata.wpafb.af.m il/tmss/ index.html, or contact the 754 ILMT via e-mail at SGMLSupport@wpafb.af.mil). NOTE: Illustration fi les developed and de li vered for other purposes shall be used in lieu of developing special TM illustration fi les whenever possible.

6.3. Interactive Electronic Technical Manuals (IETMs) shall be developed IA W ASD/AJA S I OOOD, International Specification for Technical Publications Utilizing a Common Source Database, Ver sion 4 or higher. Business rules fo r use of S I OOOD are included in the SIR found in Section 3 of this document. Contact the Procuring Contracting Officer (PCO) and TO Manager to request guidance from the Air Force Preparing Activity (PA), 754 ELSG/ ILMT, Technical Order Section, 4375 Chidlaw Rd Suite 6, WPAFB OH 45433-5006.

6.4. The offerer may propose use of other Non-Government Standards (NGS) for development of TOs, but must justify this choice based on life-cycle cost sav ings to the government and compatibil ity with existing systems identified in the IDS and the System Support Plan.

6.5. The contractor shall contact 754 ELSG/ ILMT for pre-approval before modifying or developing any new DTDs to support use ofNGS, canceled TMSS. or undeveloped TMSS DTDs. If permission is granted, the offeror must submit any proposed DTDs through the PCO and TO Manager to 754 ELSG/ILMT for validation of TMSS compatibil ity with approved electronic TO (eTO) viewing so lutions. New DTDs shall not be developed in lieu of existing DTDs, including those for legacy TMSS. Rules sha ll 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 ap-

TM-86-0lN 1 April 2009 3 proved in execution of the contract shall become the property of the Government. Direct questions about the application of SGML tagging to digital TO fil es to 754 ELSG/ ILMT (SGMLSup port@ wpafb.af.m i I).

7. TO Numbering. Offerors shal l notify the government of manuals wh ich require TO numbers. TO numbers are not required for manuals to be used exclusively by the offeror's own personnel. (NOTE:

Dl-TMSS-80067 may be used to provide the notification.) AF procedures fo r numbering TOs are de scribed in TO 00-5-3 and TO 00-5- 18, AF Technical Order Numbering System, (avai lable at http://www. tinker .af. mi I/I i brary/ factsheets/ factsheet.asp? id=6082/).

8. Data Rights . Government rights in data are specified in the Defense Federal Acquisition Regulation Supplement (DFARS), paragraphs 227-7102 through 227-7104, located (enter the RFP location con taining the applicable DFARS paragraphs). Offerors shall propose Unlimited Rights fo r all source data and TOs prepared specifically for the contract.

8. 1. If some TOs or source data are copyrighted or contain proprietary data or procedures, o fferors 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 or7106.

8.2. Specifically, if an NGS is proposed, the government shall be given unlimited rights for a ll busi ness 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. Offerors shall de termine the correct markings and controls for classified and restricted distribution data and TOs LAW the program's Security C lassification Guide (SCG) and DOD 5200. 1-R, DODD 5230.24, AFis 21-303, 3 1- 40 1 and 6 1-204, and Ml L-STD-38784 (avai lable at http://\\"\\.c-publishinc.af.mil/ or http: dodssp.daps.dla.mil/ass ist.htm). The markings and notices shall be rev iewed during In-Process Reviews (IPR). NOTE: Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon TO content.

I 0. TO Quality. Offerors shal l propose a quality assurance program which ensures TOs are prepared IA W 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 wou ld activate explosive devices or present a hazard to personnel or equ ipment. Offerors' proposals shall describe how the government wi ll be a llowed to interact with the contractor's TO development team. NOTE: Quality requirements for the Joint Nuclear Weapons Pub lications System (JNWPS) and for Non-nuclear Explosive Ordnance Disposal (EOD) Data are contained in TO 11 N-1-1 and DOD Directive 5 160.62, respectively. The government performance-tests all JNWPS and EOD TOs.

I 0.1. Conferences and Technical Rev iews. Offerors shall propose suffic ient conferences and re views to a llow insight into TO development processes and ensure contract compliance. Offerors should host an initia l Guidance Conference or Technical Interchange Meeting (TIM) within 60 days of contract award to ensure mutual understanding of TO contract requirements, schedules, po ints of contact, etc. Periodic In-Process Reviews (lPRs) and Prepublication Reviews (PPR) ensure TOs are being developed according to contract requirements and that open discrepancies are c leared prior to publication. For eTO based programs, IPRs subsequent to the initial review need to be accom pli shed using the approved viewing presentation system. NOTE: PPRs are required for critical safety and nuclear surety procedures TOs, and may be required for other complex procedures TOs.

4 TM-86-01 N 1 April 2009

I 0.2. TO Certification. Offerers shall propose their method for documenting certification that TO procedures are accurate, adequate, current, safe and usable for their intended purposes. Offerers shall notify the government at least 180 days prior of the need for any Government Furnished Infor mation/Government Furnished Equipment (GFl/GFE) required to perform certification tasks.

I 0.3. Verification Support. Offerors shall propose the methods. equipment and personnel required to support government TO Verification. This support should cons ist of at least (insert minimum program requirements, such as writers and/or engineers to resolve problems during verification, program-peculiar equipment and supplies, maintenance of TO configuration, incorporation of gov ernment comments. and participation on TO Review Boards (TORBs) and Flight TORBs).

I 0.4. Technical Data Assessment CTDA - originally called First Article Testing). The program office, w ith the assistance of 754 ELSG/JLMT and the contractor. will determine the TOA 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 TOA to verify compliance of the digital files to Air Force DSSs. Additional TDAs may be required based on initial results. The TOA 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 OTO versions are used for TO development.

The contractor shall deli ver a representative percentage of Indexed Portable Document Format (IPDF) TO files to verify indexing compliance with the Technical Order Conversion Requirements (TOCR) (on the AF Portal at https://wwwd.my.af.mil/afknprod/DocView.asp?DoclD=S I 53963).

11 . TO and Source Data Maintenance. O fferers shall propose methods for maintaining accuracy, cur rency and configuration of TOs and source data throughout the contract period of perfonnance. Mainte nance includes preparation of TO and source data updates to incorporate corrections, equipment config uration changes. and maintenance and operational concept changes.

12. TO Delivery. Offere rs shall propose practices and procedures for secure access to or delivery of digital TO fi les, including those for Preliminary TOs (PTOs), source data, reproduction masters, and program support data. Practices and procedures shall be compatible with the program's IDS (found in (specify RFP location of IDS)). TO file delivery fo rmats shall be accordi ng to applicable CDRLs and the tai lored TM Delivery Requirements Matrices included in Section 2 of this document. Paper TO deliv ery is not acceptable for final delivery of TOs. EXCEPTION: For Commercial Manuals not avai lable digitally.

12.1. SGM L-Tagged Files. The contractor shal I parse and compose SGM L-tagged TO document files prior to delivery to the government, and verify that content tagging has been accomplished to the levels prov ided in the OTO. NOTE: The government wi ll parse the files prior to acceptance us ing the public domain " SGMLS Parser" ( ftp://Hp.jclark .com/pub/SGMLS).

12.2. SGML-Tagged Files fo r Use with the eTO Viewer. The contractor shall use the GFE ETIMS eTO Viewer/Transformer and Digital Formatted Output Specification Instance (DFOSI) to convert tagged instances to Hypertext Markup Language (HTML) files compatible with the eTO viewer, and certify the output complies with TMSS requirements.

12.3. Interactive Electronic Technical Manuals CI ETM). IETM data base deli very shall be accord ing to the bus iness rules fo r SI 0000 in Section 3 of this document.

• 12.4. Indexed AdobeTM Portable Document Format CIPDF) Fi les. The contractor shall vali date indexing of PDF TO ti les using the specifications contained in the Technical Order Conversion Requirements (TOCR) found on the Air Force Portal at https://wwwd.my.af.mil/afknprod/DocView.asp?DoclD=S l 53963.

13. Schedules. Offerers 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 o f

TM-86-0lN 1 April 2009 5 performance. NOTE: AF policy requires del ivery of verified TOs prior to or concurrently w ith deliv ery of operational equ ipment to the field (AFI 21-303, Technical Orders). This policy will determine TO development and delivery schedules throughout the acquisition phase of a program.

14. Time Compliance Technical Orders CTCTOs). Offerors 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 decides that a TCTO is the appro priate method of implementation. the contractor may be requested to develop the TCTO package for Air Force coordination and approval. See TO 00-5-15, Air Force Time Compliance Technical order Pro cess, (avai lable at http://www.tinker.af.mil/library/factsheets/ factsheet.asp?id=6082/00-5- I 5-W A- I /00- 5- 15.PDF) for a detailed description of TCTO processes.

15. TO Reproduction Management. Offerors shall propose practices and procedures for managing the program's Prel iminary TO reproduction requirements. MIL-HDBK-38790, Printing Production of Technical Manuals, may be used as guidance for TO printing format, paper weights, layout require ments, etc. NOTE: Reproduction management for formal TO printing includes assembly of a print package (reproduction media, a reproduction assembly sheet , and TO Initial Distribution (ID) labels) and submission of the package for government printing through the Defense Automation and Publica tion Service (DAPS) TO Distribution and Print System (TODPS). (ID labels or label files are prov ided by the TO Manager) In some cases, the contractor may perform the printing. Reproduction manage ment for digital media consists of reproduction of the digital file on magnetic/optical media and distribu tion accord ing to ID labels. Reproduction Management may also include configuration control and stor age of reproduction masters.

6 TM-86-0lN 1 April 2009

SECTION 2. TM TYPE AND D EUVERY REQUIREMENTS

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 sryle and format requirements ofMIL STD-38784; IETMs must conform to S IOOOD and its business rules.

• Check the ASSIST database, hnp: 1dodssp.dap!>.dla.mil/assis1.h1m, for updated versions of the required T MSS prior to initiating any work on this proposal/contract.

• Manuals delivered using this table and Dl-TMSS-80067, CFAE/CFE otices, must be reviewed and approved by the Air Force prior to delivery.

• fPBs are developed IA W MIL-PRF-38807, except that M IL-DTL-87929 will also be used for IPBs combined with work packages.

• All checklists, except aircrew and nuclear weapons checklists, are developed IA W MlL-PRF-5096.

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

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

• For further information on the Air Force Vision and TO Concept of Operations (CONOPS), see AF Portal URL hllps:llwwwd. my.a/ millajknprodl ASPs!DocMan/DocMain. asp? Filter=OO-EN-TO-P I & Folder/ D=OO-EN-TO-P 1- 15& Tab -= O.

• Fo //\<' the.fi//- 111 hOXl'.\ i11 tht' tahfl!, a111/ 111t1/l'KI!.\ tfouhfe-l llc~ lll!XI /II Cl ho.r a11c/ cflallg<' thl' f>e/011/t /l!XI .. or /Jeft111lt rnl11t' ·· 111 the pop-up dialog hox as n•1111irecl (Ddetc thi\ 11otc prior to placi111: T\/CR 011 co111ract.)

PART A - TM T YPE SEL ECTIO . T ABLES.

TADLE I

TMSS REQUIREMENTS FOR TH E L__) Program (System!C omponent)

Title or Type of Manuals

I . Inspection TOs

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

(I) Maintenance/Operations (Non-Aircrew)

(2) Operations (Aircrew)

2. Cargo Aircraft Loading and Offloading TOs

a. Manual

b. Checklists

3. Weight and Balance (Aircraft)

a. Loading Data Manual

b. Sample Basic Weight Checklists

4. Flight Manuals (see notes)

a. Flight Manual

b. Perforn1ance Data Manual

c. Air Refuel ing Manual

d. Air Refueling Checklist

Specification

MJL-PRF-5096

MIL-PRF-5288

MIL-PRF-5920

MIL-DTL-7700

Required

D

D

D D D D

D D

D D

D D

D D D

TM-86-0lN 1 April 2009

TABLE I

TMSS R EQUIREMENTS FOR T llE (_) Program (System Component)

Title or Type of Manua ls

5. List of Applicable Publications

6. Structural Repair Manuals (for Aircraft)

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

a. N uclear Weapons Basic Information and Loading Procedures

b. uclear Weapons Loading Procedures

c. 'on-nuclear Munitions Basic

d. Non-nuclear Loading Procedures

e. Integrated Combat Turnaround Procedures

Specification

MlL-PRF-803 1

MIL-PRF-9854

MIL-PRF-9977

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

g. Loading Procedures Checklists

h. Integrated Loading Procedures Checklists

i. uclear Weapons Loading Procedure Checklists

j. Integrated Combat Turnaround Procedures Checklists

k. NA TO 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)

a. Operations Manual

b. Operations Checklists

c. Technical Manuals and Related Checklists

A Sl/AIAA-R024-1993

MIL-PRF-38311

MIL-PRF-383 14

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

a. Non-nuclear Weapon Del ivery Manual (Strategic Bomber & Tac1ica Aircraft)

b. Nuclear Bomb Delivery Manual (Strategic Bomber Aircraft)

c. Aircrew uclear 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. uclear Bomb Delivery Checklist (Strategic Bomber Aircraft)

g. Aircrew N uclear Weapon Delivery Checklist (Tactical Aircraft)

h. Non-nuclear Weapon Delivery Source Data Packages

I 0. Work Unit Code Manual

11. Calibration Procedures

12. Time Compliance Technical Order~(TCTOs)

13. Ai~raft Banle Damage Assessment and Repair TOs

14. Jllustrated Parts Breakdown

15 . On-Equipment Organizational Maintenance Manual Set (see notes)

a. General Equipment (GE) Manual

b. General System (GS) Manuals

c. Combined GE & GS Manual

d. Job Guide (JG) Manuals

e. Fault Reporting (FR) Manual

f. Fault Isolation {Fl) Manual

g. Wiring Data (WO) Manual

h. Schematic Diagram (SD) Manual

MIL-PRF-38769

MIL-PRF-38793

MlL-PRF-38804

MIL-PRF-87 158

MIL-PRF-38807

MIL-PRF-83495

Required

D D

D D D

D

D

D D D

D D D

16.

17.

18.

19.

TM-86-0lN I April 2009

T ABLE 1

TM SS REQUIREMEl'iTS FOR THE L__) Program (System/Component)

Title or T ype of Manuals Specification

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

a. Maintenance Manuals

(I) Intermediate Maintenance

(2) Depot Maintenance

(3) Combined ( l&D) Maintenance

(4) On Condilion Maintenance

b. Operation & Maintenance Instruction Manuals

c. Special Manuals

( I) Aircraft Engine Testing and Trending Procedures

(2) Aircraft Power Package Testing Procedures

(3) Static Firing of Missile Motors

(4) System Peculiar Corrosion Control

(5) ondestructive Inspection (NOi)

(6) Aircraft Structural Integrity Program (ASIP)

(7) ATE Operator Test Procedures

(8) Special Requirements for Storage and Maintenance Procedures;

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

(9) Parachute Packing Procedures

(I 0) Operators Instructions (Hand-Held Flight Computers)

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

d. Checklists (IA W MIL-PRF-5096)

e. With Illustrated PartS Breakdown (see notes)

Commercial Manuals (Evaluate according to MIL-PRF-322 16)

Aircraft Cross-servicing Guide MJL-DTL-22202

Interactive Electronic Technical Manuals ( IETM - Contact 754 ELSG/ILMT ASD-S I 0000 -for guidance.) International

Specification for Technical Publications Utilizing a Common Source Data Base

Required

D

D D D D

TM-86-0lN 1 April 2009 9

T ABLE 2

ADDITIONAL TM TYPE SELECTIONS

NOTES:

• Check all applicable boxes .

• For commercial manual supplemental data only, under the specification heading, enter "Same style and format," "M IL- PRF-38807" (for IPB data), or "M l L-STD-38784."

• For existing MIL-SPEC manuals not being updated to latest specification requirements, enter "Same style and format" under the specification heading.

• For manuals proposed to GS, list the type of manual in the appropriate column and the GS in the Specification column. Manuals proposed to an approved NGS shall meet the functional requirements of the approved TMSS for the TO type, e.g., OMMS prepared to SI 0000 shall meet the requirements ofMIL-PRF-83495 (which serves as business rules for manual style, format, and content).

Com- Supple- TO Number, T itle, or mercial C hangel Supple- mental Source

Trl?e of Manual Seecifi cation Manual Revision ment TM Data

I. D D D D D

2. D D D D D

3. D D D D D

4. D D D D D

5. D D D D D

6. D D D D D

7. D D D D D

8. D D D D D

9. D D D D D

10. D D D D D I I. D D D D D

12. D D D D D

13. D D D D D

14. D D D D D

15. D D D D D

16. D D D D D

17. D D D D D

18. D D D D D

19. D D D D D

10 TM-86-0lN 1 April 2009

PART B -TM D ELIVERY REQUIREMENTS

FOR ----

(Sys1eml/1em)

TM D ATA T YPE D ELIVERED _ ___ ____..

(TMSSIChange/Supplementletc.} (Replicate fonn for each TM type required.)

Delivery Format Requirements Codes

Digital delivery onlv:

f. - Paper (draft or manuscript only. Cannot be used for final delivery) g - Standard generalized Mark-up Language (SGML).

!L- Hyper Text Mark-up Language (HTML)

M - Mixed paper and digital (G. Hor I) ! - Indexed Portable Document Format (IPDF) File.

K - Extensible Mark-up Language (XML)

EXAM PLE: M(G) I 2 [Paper and SGML / 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 0 (zero).

• For GS or non-standard TMSS instances, delivery shall include the associated DTOs, FOSls/Style Sheets, XML schemas, etc.

DELIVERY SCHEDULE

Event ¢Number of days data required prior to Technical Verification Prepublication Final TO event¢ Review(s)( ( Days) Review( Distribution( Days) Days) Days)

Enter Office Symbol and Address<> .{l. Enter delivery requirements code/copy quantities required .{l. .{l. .{l. .{l.

I I I I

I I I I

I I I I

I I I I

I I I I

I I I I

I I I I

Total Copies Required :

TM-86-01 N 1 April 2009 11

S ECTION 3. SPECIFICATION/STANDARD I NTERFACE R ECORDS (SIRS)

NOT ES:

• All TMSS applicable to this contract shall have an appropriately tailored SIR attached to this section.

• SI Rs included in the untailored TMCR fonnat represent the minimum tailoring requirements that must be includ ed in the final contract, unless the entire S IR is not applicable; e.g., if MIL-DTL-222020 is not required, the en tire SIR can be deleted.

• MIL-STD-38784 must be included in all contracts/proposals for AF TMSS-developed TOs.

• Most specification ·'Acquisition Requirements" list the same two items for paragraphs 6.2a 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.

• Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available from the DoD Single Stock Point (DODSSP), Acquisition Streamlining and Standardization Jnfonnation System (ASSIST) web page, hllp: \\ \\" .dodssp.daps.dla.mil assist.him.

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

• TMSS entries designated with A, F, M or N refer to Army, Air force, Marine Corps or .t{avy requirements.

• Beneficial comments, recommendations, additions, data etc. which may be of use in improving any Air Force TMSS should be addressed to "Air Force Technical Manual Specifications and Standards Office, 754 ELSGflLMT, Wright Patterson AFB, OH 45433". Do not include the street address, a building number, or a zip+4.

SPECIFICATIO;';/STA~DARD INTERFACE RECORD FOR MIL-DTL-222020,

Supplement I, Manual, Technical, Aircraft Cross-Servicing Guide, Preparation of

The requirements of 6.2 are met in this SIR (see below).

3 I March 1999 3 I March 1999

I. I In addition to paper delivery, when this specification is used to develop digital delivery files (document type defi nitions - DTDs) contact the PA for additional instructions.

2.3 Ensure the listing for STANAG/ASCC Air Standard Documents is current. List applicable STANAG/ASCC Air Standards below.

(List STANAG/ASCC Air Standard Documents here.)

2.2. I (Added) "Other government documents, drawings, and publications.

DEPARTMENT OF DEFENSE

DOD 5200. 1-R DoD Information Security Program Regulation DOD 5220.22-M National Industrial Security Program Operating Manual

4. Replace with: "4. VERIFICATION .

.. All cross-servicing guides shall meet the requirements of sections 3 and 5 of this specification, as re quired by the acquiring activity. The requirements set forth in this specification shall become a part of the contractor's overall inspection system or quali ty program. The absence of any requirements in this specification shall not relieve the contractor of the responsibili ty of ensuring that all products or supplies submitted to the government for acceptance comply with all requirements of the contract. Use of sam pling inspections shall be at the discretion of the contractor, and in accordance with commercially ac ceptable quality assurance procedures. However, use of sampling in QA procedures does not authorize submission of known defective material, either indicated or actual, nor does it commit the government to accept defective material.., 12 TM-86-0IN 1 April 2009

5. Replace wilh: "5. PACKAG ING .

··5.1 Packaging Requirements. For acquisition purposes, the packaging requirements shall be as spec ified in the contract or order. When the actual packaging of material is to be performed by DoD per sonnel, these personnel need to contact Lhe responsible packaging activity to determine packaging re quirements. Packaging requirements are maintained by the Inventory Control Point's packaging activ ity within the Military Department's System Command. Packaging data retrieval is available from the Military Department's or Defense Agency's automated packaging files, CD-ROM products, or the re sponsible packaging activity.

"5.1. 1 Encoded Computer Products. Packaging of encoded computer products for delivery shall be in accordance with the requirements of M IL-STD-1840.

''5. 1.2 Classified Material. Classified material shall be packaged and identified in accordance with DOD 5200.1-R, DOD 5220.22-M, and the implementing Service regulations."

6.2a T itle, number, and date of the specification are listed above.

6.2b Issue of DODISS: (fill in issue of DOD/SS applicable to this contract) 6.2c Packaging requirements (see above).

6.2d Verification requirements (see above).

SPECIFICATION/STANDARD I NTERFACE RECORD FOR M I L-STD-38784,

Notice I, Notice 2, 2 July 1995 15 November 2000

I December 2000 Standard Practice fo r Manua ls, Technical: Genera l Style and Format Req uirements

Global: Change references to "MIL-STD-1806" to read "DODD 5230.24."

3.2.8 Continuous Tone Artwork. Delete paragraph.

3.2.9 Copv Freeze Date. Delete paragraph.

3.2. I 0 Cut line. Delete paragraph.

3.2.20 Layout Page. Delete paragraph.

4.2.1.2.1 Oversize Reproducible Coov. Delete paragraph.

4.2.7.1…