(CUI) ATTCH 4 - TMQ53 CLS Exhibit A CDRL.docx

DOCX document 1 MB Posted

Attached to
AN/TMQ-53 Tactical Meteorological Observing System (TMOS) Contractor Logistics Support (CLS)
Solicitation number
FA2330-26-R-B006
Issued by

About this file

This file is a Contract Data Requirements List (CDRL) Exhibit A that outlines the data deliverables required for the AN/TMQ-53 Tactical Meteorological Observing System (TMOS) Contractor Logistics Support (CLS) contract. The CDRL specifies the documentation, reports, and technical materials that the contractor must produce and submit throughout the contract performance period from FY26 to FY31, including program management plans, logistics support documentation, performance metrics reports, configuration control records, technical manuals, and engineering change proposals. Each CDRL item identifies the data requirement title, frequency of submission, deliverable format, distribution requirements, and applicable contract line item numbers (CLINs) to ensure comprehensive tracking and reporting of all contractual deliverables.

The file serves as the primary mechanism for establishing contractor accountability in delivering the required data products that support worldwide sustainment of TMQ-53 systems. The CDRL requirements align with the overarching CLS effort, which encompasses helpdesk support, maintenance operations, spares and repair management, OSS&E impact analysis, cybersecurity compliance, technical manual maintenance, and system upgrades. As a data requirements template document, this CDRL Exhibit A is essential for contract administration and ensures both the contractor and the Air Force Life Cycle Management Center (AFLCMC) maintain visibility into all required deliverables and their delivery schedules throughout the contract performance period.

View the file

Other files

Show all 17

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Aerospace Management Systems Division Air Force Life Cycle Management Center Weather Systems / Weather Systems Branch (AFLCMC/ESAW)

Contract Data Requirements List (CDRL) Exhibit A Contract Number:

Tactical Meteorological Observing System (TMOS) Contractor Logistics Support (CLS) 14 February 2026 Prepared by: AFLCMC/ESAW, 75 Vandenberg Drive, Building 1630 Hanscom AFB MA 01731 Distribution Statement C: Distribution authorized to U.S. Government Agencies and their Contractors (Administrative or Operational Use) (February 2026). Other requests shall be referred to AFLCMC/ESAW, 75 Vandenberg Drive, Building 1630, Hanscom AFB, MA 01731-2103.

HANDLING AND DESTRUCTION NOTICE. For classified documents, DoD civilians or military personnel will follow procedures outlined in DoDM 5200.01, Volume 3, and Enclosure 3: DoD Contractors will follow procedures outlined in DoDM 5220.22, Sections 11-19. For sensitive unclassified documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Exhibit A

THIS PAGE INTENTIONALLY LEFT BLANK.

Approval Page

The DD Forms 1423-1 (A001 through A031) included in this package have been approved and digitally signed by the following individuals. This replaces the need to digitally sign Block G and Block I on Forms 1423-1.

Prepared by: Travis Demmer CM/DM Manager

Approved by: Lt Mark Jackson TMQ-53 Program Manager

REVISION HISTORY

Revision
Date
Description
Pages / Sections Affected
Initial
14 Feb 2026
Exhibit A – Final
All

EXHIBIT A

Contract Data Requirements List (CDRL)

Name
Email Address
CDRL

AFLCMC/ESAW

All

Travis Demmer, CM/DM
Travis.demmer.ctr@us.af.mil
All
Lt Mark Jackson, PM
Mark.jackson.26@us.af.mil
All

Additional distribution requirements:

For CDRL #A009 TM-86-01P/T Technical Order and Associated Supplemental Data deliverables, please email the following contacts:

Jarail SmithJarail.smith@us.af.mil Rodney EbachRodney.ebach.2@us.af.mil
Samuel WilliamsSamuel.williams.3@us.af.mil

CDRL PREPARATION INSTRUCTIONS

1. Document of Data Requirements. Except for data requirements in the DOD Federal Acquisition Regulation Supplement (DFARS) clauses, DD Form 1423-1 must be used as the sole contractual list of data to be delivered under the contract.

2. Instructions for Completing Items A through J:

A. CONTRACT LINE ITEM NO. Enter the contract line item number (CLIN) that is associated with the CDRL.

B. EXH/ATCH NO. Enter the exhibit or attachment number for the Contract Data Requirements List (CDRL).

C. CATEGORY: TDP, TM OTHER . Check the appropriate category for Technical Data Package (TDP), Technical Manual, or Other Types of data which comprise a TDP, as defined in attachment 1. Acquisition of TMs is covered by AFR 8-2, Air Force Technical Order System. Other data may be further categorized, such as provisioning, configuration management, etc. If the CDRL does not contain a specific category of data requirements, simply enter “Miscellaneous”.

D. SYSTEM/ITEM. Identify the system, item, or project by designator or name.

E. CONTRACT/PR NO. If known, enter the actual contract number: if not, enter the number of the PR or other appropriate designator.

F. CONTRACTOR. Enter the contractor’s name or acronym (inserted at award). G and H. PREPARED BY, DATE: Enter the name, title, and office symbol of the DMO responsible for preparation of the contract data requirements list. Normally, these items are completed only on the first page of each exhibit or attachment.

I and J. APPROVED BY, DATE: Enter the name, title, and office symbol of the program manager or the designee responsible for approving the CDRL. Normally these items will be filled in only on the first page of each exhibit or attachment.

3. Instructions for Completing Items 1 through 16:

1) DATA ITEM NO. Enter the CDRL sequence number (i.e. for exhibits, enter the Exhibit Line Item Number (ELIN); for attachments, enter the data item sequence number). Reference DFARS 4.7106.) NOTE: When the CDRL contains less than 1,000 data line items, the last three digits of the exhibit line may be numbered numerically.

2) TITLE OF DATA ITEM. Enter the exact title as it appears in item 1 of the DD Form 1664.

3) SUBTITLE. If the title requires further identification, enter a subtitle. (If necessary, use item 16 for further identification of the data item).

4) AUTHORITY (Data Acquisition Document Number). Enter the number as it appears in item 2 of the DD FORM 1664. Add/T if the DID has been tailored.

5) CONTRACT REFERENCE. Enter document and paragraph numbers that identify the task or requirement from which the data flows (contract clause, statement of work paragraph, Integrated Master Plan paragraph, etc.) to help identify the data item authorized by item 4 (see item 4 above).

6) REQUIRING OFFICE. Enter the activity responsible for advising on the technical adequacy of the data. This may be the first addressee in item 14. When data require approval (see item 8 below), this activity is responsible for determining if the data submitted should be approved as submitted, or revised to meet contract requirements.

7) DD FORM 250 REQ:

a. DD Form 250 will only be required for data listed on the CDRL, which requires government inspection and acceptance. These are:

(1) Final Air Force technical Orders.

(2) Engineering drawings, which are delivered to an Air Logistics Center Engineering Data Service Center.

(3) Data which will be used by Air Force personnel for operation, installation, or maintenance, even though equipment and/or software will not be transferred to AFLC (AFR 800-4).

b. Designate the location (contractor’s facility, or destination) for performance of government inspection and acceptance, by entering the applicable code for inspection and acceptance, as shown below:

Code
Inspection
Acceptance
SS
Source (DD Form 250)
Source (DD Form 250)
DD
Destination (DD Form 250)
Destination (DD Form 250)
SD*
Source (DD Form 250)
Destination (DD Form 250)
DS
Destination (DD Form 250)
Source (DD Form 250)
LT
Letter of Transmittal Only
NO
No Inspection or Acceptance Required
XX
Inspection and Acceptance Requirements Specified Elsewhere in the Contract
Sindicates the contractor’s facility.
Dnormally indicates the primary distribution point.

*SD will be used for all engineering data that are to be delivered to an Engineering Data Service Center.

8. APPROVAL CODE. Items of critical data requiring specific advance written approval prior to distribution of the final data item, such as test plans, are identified by an "A" placed in this item. Most of these data items require submission of a preliminary draft prior to publication of a final document. When block 8 is blank, approval is not required, although the Government has the inherent right to disapprove any data item.

9. DIST STATEMENT REQUIRED. References the distribution statement to be affixed to the deliverable in accordance with DODD 5230.24, Marking Technical Data Prepared By or For the Department of Defense.

All data deliverables in this Exhibit A shall contain the following Distribution Statement and Destruction Notice:

DISTRIBUTION STATEMENT C: Distribution authorized to U.S. Government Agencies and their contractors (Administrative or Operational Use) (February 2026) Other requests for this document shall be referred to AFMC/AFLCMC/ESAW, Weather Systems Branch, 75 Vandenberg Drive, Building 1630, Hanscom AFB, MA 01731 DESTRUCTION NOTICE. For classified documents, DoD civilians or military personnel will follow procedures outlined in DoDM 5200.01, Volume 3, and Enclosure 3: DoD Contractors will follow procedures outlined in DoDM 5220.22, Sections 11-19. For sensitive unclassified documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

10. FREQUENCY. The following are the codes used in this block:

Code
Frequency
DAILY
Daily
WEKLY
Weekly
BI-WE
Each 2 Weeks
MTHLY
Monthly
BI-MO
Each 2 Months
QRTLY
Quarterly
ANNLY
Annually
SEMIA
Each 6 Months
OTIME
One Time
ONE/R
One Time and Revisions
R/ASR
Revisions as Required
*ASREQ
As Required
DFDEL
Deferred Delivery
ONE/P
One Time Preliminary Draft
2TIME
Two OCTarate Submittals

* When ASREQ is used in Items 10, 11, 12, or 13, an explanation of the requirement will be entered in Item 16.

11. AS OF DATE (AOD). If the data will be submitted only once, enter the as of date (the cut-off date) as follows: year/month/day. If the data will be input on a recurring basis, which has been set by item 10, show the number of days between the cut-off date and the end of the input period. For instance, if the data are to be submitted 15 days before the end of the input period enter 15. If the data are to be submitted at the end of the input period enter 0. If necessary, use item 16 to explain further.

12. DATA OF FIRST SUBMISSION. Enter the date of submission as follows: year/month/day. If the delivery of the data depends on the initiation of a specific event or milestone, identify this event or milestone. If you do not know the contract start date, enter the number of days the data is due after the contract start for example, 30 DAC (Days after Contract). If this data is not known nor needs more clarification, explain in item 16. If the data are subject to deferred delivery enter

“DFDEL”. If an acronym is created to identify an event or milestone, define the acronym in item 16. NOTE: Do not insert classified dates.

13. DATE OF SUBSEQUENT SUBMISSION. If the data item will be submitted more than once, enter the dates of subsequent submission. If a draft was required, enter the date the final document is to be submitted.

14. DISTRIBUTION. Identify each addressee and give the number of copies (regular and reproducible) to be received by each one (for example, TIC-320/0). If appropriate, use office symbols, contractor initials, or DID Handbook E-4 code numbers and command initials: in this case, attach a list explaining these codes. If reproducible copies are required, give the type of reproduction request here or in item 16 (offset, mat, vellum, negative, floppy disk, magnetic tape, etc.). If the data are not actually to be delivered to the Government or to associated contractors, enter the appropriate instruction.

15. TOTAL. Enter the total number of copies (regular or reproducible) for one delivery; this number should be the sum of all the copies specified in item 14. If distribution fluctuates, use a not to exceed number.

16. REMARKS: Use this space to explain the following:

a. Tailored features of the DID.

b. Items 1 through 15

c. Any re-submittal schedule or special conditions involved in updating data submitted for government approval.

CDRL GENERAL INSTRUCTIONS

1. The Data Items on the DD Forms 1423 are cross-referenced thereon in Block 5, to the associated Integrated Master Plan (IMP) tasks under which the basic information is generated. These data items shall be prepared in accordance with the applicable Data Item Descriptions (DIDs) set forth in DOD 5010.12-L, AMSDL, as tailored, or one-time DIDs.

a) Standard DIDs. These are identified in DOD 5010.12-M, and the “Assist Quick CDRL Search” Website: http://assistdocs.com/search/search_basic.cfm

b) Tailored DIDs. These are standard DIDs which have specific modifications or tailoring applied to them. These are identified with the suffix “/T” at the end of the DID number in Block 4 (e.g., DI-MISC-80711/T).

c) One-Time DIDs. These are DIDs approved for one-time acquisition use which is associated with a unique data requirement applicable to a single contract (e.g., OT-97-xxxxx).

d) Marking of Data. DODD 5230.24, OCTust 2012.

2. Block 10 of DD Form 1664 (DID) together with any tailoring of the DIDs contains instructions which shall be followed by the contractor in the preparation of data for delivery under this contract.

3. Data submitted in this contract shall be accompanied by a Letter of Transmittal (L\T) and be identified with the following elements:

a) Contractor

b) Contractor’s Transmittal Letter Number, including a running serial number and date

c) Contract Number

d) CDRL Data Item (Sequence) Number

e) DID number and Title

f) Revision Identification, if any

g) Block 14 (or modified) distribution list

4. Data shall be submitted for receipt by the customer in accordance with the delivery schedule specified on the individual DD Form 1423, except those due dates falling on non-working days (Saturdays, Sundays, and recognized national {legal} holidays) shall be construed to mean the next regular working day. All due dates (e.g. 30 DAC) are calendar days unless specified differently otherwise.

5. Existence of an “A” in Block 8 on the DD Form 1423 indicates written approval by the Procuring Contracting Officer (PCO) is required. Unless a different time period for approval is specified on the DD Form 1423, the Government will have 30 calendar days from the date of receipt on the data for notifying the contractor of the approval/disapproval disposition of a data submission. In the event that a data submission is disapproved, the PCO will advise the contractor of the reasons for disapproval and a resubmission shall be accomplished within thirty (30) days unless specified differently otherwise. Approval indicates Government concurrence to proceed to the next event.

In the absence of an “A” in Block 8, the Government has the inherent right to disapprove any data item. Approval does not ensure compliance with DID format and content requirements, since the Contractor is obligated to meet these requirements under the terms of the contract.

6. DD250s will be required upon completion of the last deliverable of each CDRL Exhibit.

7. Appropriate DODD5230.24 Distribution Statements identified in Block 9 on the DD Form 1423, and further defined in the CDRL “Remarks” Block, shall be placed on the document cover page.

8. Appropriate AFI61-204 documents shall be marked with the appropriate destruction notice and placed on the cover page under the distribution statement.

9. The contractor shall apply export control warning statements IAW MIL-STD-1806 to CDRL items identified as “TDP” in item C of each DD Form 1423-1.

10. The contractor shall address all letters of transmittal to the Procuring Contracting Officer.

11. Increases or decreases to CDRL quantities shall be in accordance with the Special Provision titled “Modification of Data Requirements”.

12. Data should be delivered by electronic media whenever possible. All data, electronic or otherwise specified, must comply with the distribution statements indicated in Block 9 of the DD Form 1423.

13. Requirements for periodic revisions to data, where no changes have occurred since the last submission, shall be satisfied by a record transmittal letter/form from the Contractor stating that “no changes have occurred since the last submission”. In such cases, the Contractor shall identify the data in question, the reporting period, and the transmittal letter and number of the prior data transmittal. Government disposition will not be provided for record transmittals; however, the Government reserves the right to non-concur with the reported negative status.

EXHIBIT A

Contract Data Requirements List (CDRL) Introduction AFLCMC/ESAW has determined documentation required to support the AN/TMQ-53 TMOS Performance Work Statement (PWS).

CDRL Tailoring The Data Item Descriptions (DIDs) associated with the CDRLs have been reviewed and tailored as specified in the attached DD Form 1423s.

Distribution Statements Distribution statements, export control notices and destruction notices will be included on the title page of each deliverable in accordance with DoDD 5230.24.

Delivery of Data Items Deliverable documentation must be submitted via the instructions included on each DD Form 1423. In addition, the Contractor must email a signed Letter of Transmittal to the Program Office at Hanscom AFB. The products must be compatible with MS Office Products, Adobe Acrobat and/or web browsers in accordance with direction located in Block 16 of each DD Form 1423.

CDRL No.
DID
CDRL Title
A001
DI-ADMN-81249B
Conference Agenda
A002
DI-ADMN-81250B
Conference Minutes
A003
DI-ADMN-81373
Presentation Material
A004
DI-SESS-80639D/T
Engineering Change Proposal (ECP)
A005
DI-SESS-80642D
Notice of Revision (NOR)
A006
DI-SESS-80640D/T
Request for Variance (RFV)
A007
DI-SESS-81253C/T
Configuration Status Accounting Information (CSAI)
A008
DI-MGMT-80368A
Status Report (Monthly Status Report)
A009
TM-86-01P/T
Technical Order and Associated Supplemental Data
A010
DI-MGMT-81797
Program Management Plan (PMP)
A011
DI-MGMT-81804A
Item Unique Identification (IUID) Marking Activity, Val/Ver Report
A012
DI-MGMT-81803
Item Unique Identification (IUID) Marking Plan
A013
DI-QCIC-81794A
Quality Assurance Program Plan (QAPP)
A014
DI-MGMT-80501/T
Contractor’s Corrective Action Plan (CCAP)
A015
DI-MGMT-81453B
Data Accession List (DAL)
A016
DI-SESS-80858C
Supplier’s Configuration Management Plan (CMP)
A017
DI-ILSS-80483
Spare Parts Usage Report (SPUR)
A018
DI-NDTI-80603A/T
Test Procedure
A019
DI-NDTI-80809B
Test Inspection Report
A020
RESERVED
A021
DI-MGMT-80441C
Government Property Inventory Report
A022
DI-MGMT-80368A/T
Status Report (Finance Report)
A023
DI-MGMT-80259/T
Physical Inventories Report (CFO Report)
A024
DI-MGMT-82001A/T
D.O.D. Risk Management Framework (RMF) Package
A025
DI-SAFT-81563
Accident/Incident Report
A026
DI-SAFT-81626
System Safety Program Plan (SSPP)
A027
DI-MGMT-81948
Management Plan (Transition Plan)
A028
DI-QCIC-80125B
Government Industry Data Exchange Program (GIDEP) Alert/Safe-Alert Report
A029
DI-QCIC-80126B
Government Industry Data Exchange Program (GIDEP) Alert/Safe-Alert Response
A030
DI-ADMN-81306
Program Protection Implementation Plan (PPIP)
A031
DI-MGMT-81948/T
Diminishing Manufacturing Sources and Material Shortages (DMSMS) Management Plan

CONTRACT DATA 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 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 the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO.

All Applicable CLINs

B. EXHIBIT

A

C. CATEGORY

ADMN

TDP TM OTHER

D. SYSTEM/ITEM

E. CONTRACT/PR NO.

F. CONTRACTOR

AN/TMQ-53 TMOS

1. DATA ITEM NO.

2. TITLE OF DATA ITEM

3. SUBTITLE

A001 Conference Agenda

Agenda

4. AUTHORITY (Data Acquisition Document No.)

5. CONTRACT REFERENCE

6. REQUIRING OFFICE

DI-ADMN-81249B

PWS Para: 6.2.1, 6.3.1, 6.3.2, 6.3.3, 6.3.5

AFLCMC/ESAW

AN/TMQ-53 TMOS Program Office

7. DD 250 REQ

9. DIST STATEMENT REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

LT

See Blk 16

a. ADDRESSEE

b. COPIES

8. APP CODE

C

11. AS OF DATE

13. DATE OF SUBSEQUENT SUBMISSION

DRAFT

FINAL

A

Reg Repro

16. REMARKS

AFLCMC/ESAW

BLOCKS 10, 11, 12 & 13: Agendas due no later than (NLT) seven (7) calendar days prior to meetings. The Government will review and provide comments within 3 (three) calendar days. The Contractor shall incorporate Government comments and resubmit the document within two (2) calendar days.

Revisions as required.

BLOCK 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to: (See CDRL POCs and Distribution Requirements List).

15. Total

G. PREPARED BY

H. DATE

I. APPROVED BY

J. DATE

AFLCMC/ESAW Data Management

18. ESTIMATED TOTAL PRICE

17. PRICE GROUP

DD FORM 1423-1, FEB 2001

PREVIOUS EDITION MAY BE USED.

Page of Pages , Exhibit A

17. PRICE GROUP

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 the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

All Applicable CLINs

B. EXHIBIT

A

C. CATEGORY

ADMN

TDP TM OTHER

A002 Conference Minutes

Minutes

DI-ADMN-81250B

AFLCMC/ESAW

AN/TMQ-53 TMOS Program Office

7. DD 250 REQ

9. DIST STATEMENT REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

8. APP CODE

C

BLOCKS 10, 11, 12 & 13: Minutes due NLT ten (10) calendar days after conclusion of meetings and/or government directed travel. The Government will review and provide comments within three (3) calendar days.

BLOCK 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to: (See CDRL POCs and Distribution Requirements List).

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 the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

All Applicable CLINs

B. EXHIBIT

A

C. CATEGORY

ADMN

TDP TM OTHER

A003 Presentation Material

DI-ADMN-81373

AFLCMC/ESAW

AN/TMQ-53 TMOS Program Office

7. DD 250 REQ

9. DIST STATEMENT REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

8. APP CODE

C

BLOCKS 10, 11, 12 & 13: Submit hard copy materials NLT the day meeting with electronic material NLT ten (10) calendar days after scheduled event.

BLOCK 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to: (See CDRL POCs and Distribution Requirements List).

The data shall be in a format compatible with Microsoft Office 2024.

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 the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

All Applicable CLINs

B. EXHIBIT

A

C. CATEGORY

SESS

TDP TM OTHER

A004 Engineering Change Proposal

ECP

DI-SESS-80639D/T

PWS Paras: 8.1, 8.1.1, 8.1.2, 8.2.1, 8.3.1, 8.3.2, 8.4.1

AFLCMC/ESAW

AN/TMQ-53 TMOS Program Office

7. DD 250 REQ

9. DIST STATEMENT REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

8. APP CODE

C

DD Form 1664, BLOCK 10 is tailored as follows:

Paragraph 2. Format and Content – Add item “H CDRL A007, provide update CSAI master list.

BLOCKS 10, 11, 12 & 13: Submittal due NLT fifteen (15) calendar days after identification of proposed change.

The Engineering Change Proposal (ECP) will be processed through the formal Government Configuration Control Process, and a response provided to the Contractor once a decision has been determined to accept or decline the proposed engineering change.

BLOCK 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to: (See CDRL POCs and Distribution Requirements List).

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

, Exhibit A

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 the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

All Applicable CLINs

B. EXHIBIT

A

C. CATEGORY

SESS

TDP TM OTHER

A005 Notice of Revision

NOR

DI-SESS-80642D

PWS Para: : 8.1, 8.1.1, 8.1.2, 8.2.1, AFLCMC/ESAW

AN/TMQ-53 TMOS Program Office

7. DD 250 REQ

9. DIST STATEMENT REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

8. APP CODE

C

BLOCKS 10, 11, 12, and 13: Submit Concurrently with Engineering Change Proposals (ECPs) – (A004).

BLOCK 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to: (See CDRL POCs and Distribution Requirements List).

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

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 the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

All Applicable CLINs

B. EXHIBIT

A

C. CATEGORY

SESS

TDP TM OTHER

A006 Request for Variance

RFV

DI-SESS-80640D/T

PWS Para: : 8.1, 8.1.1, 8.1.2, 8.2.1, AFLCMC/ESAW

AN/TMQ-53 TMOS Program Office

7. DD 250 REQ

9. DIST STATEMENT REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

8. APP CODE

C

DD Form 1664, BLOCK 10 is tailored as follows:

Paragraph 2. Format and Content – Add item “H CDRL A007, provide update CSAI master list.

BLOCKS 10, 11, 12 & 13: Submittal due NLT thirty (30) calendar days after identification of proposed variance.

The RFV shall be processed through the formal Government Configuration Change Control process. A response shall be provided to the Contractor once a decision has been determined to accept or decline the proposed RFV. Revisions as required.

BLOCK 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to: (See CDRL POCs and Distribution Requirements List).

Page of Pages

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 the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

All Applicable CLINs

B. EXHIBIT

A

C. CATEGORY

SESS

TDP TM OTHER

A007 Configuration Status Accounting Information

CSAI

DI-SESS-81253C/T

PWS Para: 8.3.1, 8.3.2, AN/TMQ-53 TMOS Program Office

7. DD 250 REQ

9. DIST STATEMENT REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

8. APP CODE

C

BLOCK 4: DD For 1664 tailored as follows:

Requirements paragraph 2 is changed to read as follows: “The following information (fields) shall be prepared and updated in ELMS”.

· Site Location

· Hardware Item Description

· Prime Contractor Part Number

· Original Equipment Manufacturer/Vendor Name

· Original Equipment Manufacturer Part Number and Serial Number

· Total quantities

· Firmware Item Description

· Firmware Manufacturer/Vendor Name

· Firmware nomenclature, version number, and release date

· License requirements/quantity

· Total quantity of licenses

· Item Unique Identifications (IUIDs)

· Peculiar Support Equipment (PSE)

· Test Equipment

· Spares

· On Site Spares

· Government Furnished Equipment (GFE) BLOCKS 10, 11, 12, & 13: All information shall be entered into ELMS NLT ninety (90) calendar days after Contract Award. Subsequent updates due NLT seven (7) calendar days after changes are made to any items. The Contractor shall make updates and notify the Government. The Government will review and provide comments within seven (7) calendar days. The Contractor will incorporate Government comments and update ELMS within seven (7) calendar days. Any and all proposed change(s) shall first be passed through the formal Government ECP/CCB Process with updates to be made in ELMS. See CDRL A004 (ECP).

CONTRACT DATA REQUIREMENTS LIST

A. CONTRACT LINE ITEM NO.

A007

B. EXHIBIT

A

C. CATEGORY:

X

TDP TM OTHER

D. SYSTEM/ITEM

AN/TMQ-53 TMOS

E. CONTRACT/PR NO.

F. CONTRACTOR

16. REMARKS (Continued)

BLOCK 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to: (See CDRL POCs and Distribution Requirements List).

DD FORM 1423-1, FEB 2001Reset

Page of Pages

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 the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

All Applicable CLINs

B. EXHIBIT

A

C. CATEGORY

MGMT

TDP TM OTHER

A008 Status Report

Monthly Status Report

DI-MGMT-80368A

PWS Para: 3.1, 3.2, 6.1.1, 6.3.1, 6.4, 6.5.1, 6.5.2, 7.2, 7.4, 7.4.1, 7.4.2, 7.4.6, 7.5.2.1, 7.6, 8.1.3, 8.2.1, 9.1.1, 9.1.2, 9.2

AFLCMC/ESAW

AN/TMQ-53 TMOS Program Office

7. DD 250 REQ

9. DIST STATEMENT REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

8. APP CODE

C

N/A

BLOCKS 10, 11, 12, & 13: Initial submittal NLT thirty (30) calendar days after contract award. The Government will review and provide comments NLT seven (7) calendar days. The Contractor shall incorporate Government comments and resubmit NLT seven (7) calendar days.

Subsequent submittals shall be delivered on the fifteenth day of each month thereafter.

BLOCK 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to: (See CDRL POCs and Distribution Requirements List).

Page of Pages

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 the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

All Applicable CLINs

B. EXHIBIT

A

C. CATEGORY

TDP TM OTHER

A009 Technical Order and Associated Supplemental Data

TO

TM-86-01P/T

PWS Para: 6.3.1, 6.3.2, 6.3.3, 8.1, 8.1.1, 8.1.2, 8.4.1.1, 10, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8, 10.9

AFLCMC/ESAW

AN/TMQ-53 TMOS Program Office

7. DD 250 REQ

9. DIST STATEMENT REQUIRED

10. FREQUENCY

12. DATE OF FIRST SUBMISSION

14. DISTRIBUTION

8. APP CODE

C

BLOCKS 10, 11, 12, & 13: Refer to TM-86-01P for this information (pages 25-30 of Exhibit A).

BLOCK 14: Initial and subsequent submittals (to include all revisions) shall be provided electronically via email to:

(See CDRL POCs and Distribution Requirements List).

Air Force Technical Manual Contract Requirements (TMCR) for

TMQ-53

(Program/Modification/Military System)

ATTACHMENT , TO CDRL SEQUENCE NUMBER , EXHIBIT REQUEST FOR PROPOSAL/CONTRACT:

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. This TMCR has been tailored by the program office, including the associated tables, matrices and Specification/Standard Interface Records (SIRs). The Contractor may propose and submit, in writing additional tailoring to the TO Manager Agency/Agent (TOMA) and Procuring Contracting Officer (PCO) for consideration. The tailored TMCR shall be attached to the CDRL for TO delivery, and shall be included in the proposal as a separate exhibit, referenced in the proposal SOW. Proposals shall be compatible with the TMQ53 Technical Order Concept of Operations. Air Force TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management, located on the Internet at http://www.tinker.af.mil/Home/TechnicalOrders.aspx. A copy may also be obtained from the Program TO Manager. Any terms or procedures found in this document may be researched there.

2. TO Program Scope. The Contractor may recommend additional Section 2 tailoring to propose new TO types (Table 1) and source data and TO updates (Table 2) required to support the TMQ-53 program’s objectives.

3. Commercial Manuals. Contractors shall recommend the use of existing commercial manuals to the maximum extent possible without impairing program support objectives. All proposed commercial manuals are subject to government review and approval.

NOTE: a) Contractors shall use Data Item Description (DID) DI-TMSS-80067, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, to provide recommendation data. A copy is available from the TOMA upon request. 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 manuals.

3.1. All commercial manuals shall be delivered with either unlimited data rights or as a minimum, Government Purpose License, to allow the AF to electronically store, print, distribute and decollate the commercial manual to allow for printing.

3.2. Approved COTS Manuals shall be delivered with an Identifying TO Publication Sheet, IAW MIL-PRF-32216. All PDF files of commercial data shall be non-password protected.

3.3. If the proposed COTS data is found to be insufficient after review by the government, the contractor shall prepare supplemental data for the COTS manual as required IAW MIL-STD-38784. If the COTS data cannot be supplemented sufficiently the contractor may be tasked to develop new TM data IAW the applicable TMSS listed in Section 2 Table 1. All symbols will be NEMA or ANSI compliant.

4. Technical Manual Specifications and Standards (TMSS) Tailoring. TMSS are tailored by selecting between tailoring options offered in each TMSS. The tailoring is recorded in SIRs and added to Section 3 of this document for each TMSS required. NOTE: Tailoring must not change or delete mandatory requirements which are part of the Document Type Definition (DTD) structure or XML schema structure located in Section 2 Table 1.

4.1. AF options in some Joint-Service TMSS have been documented in preliminary SIRs included in Section 3. These preliminary SIRs provide the starting point for further tailoring. Contractors may recommend additional tailoring of the Joint-Service TMSS SIRs and provide recommended SIRs for other TMSS as applicable. 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 tailoring options in each TMSS.

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 TOMA, 3580 D Avenue bldg. 201W post 74 Tinker AFB OK 73145. Deficiencies and suggested improvements shall be submitted to the TMSS

, Exhibit A

Preparing Activity (PA). Approved recommendations, corrections and clarifications will be maintained with contract documentation.

5. Subsequent TO/Data Requirements. When new TO requirements are identified the Contractor shall notify the government utilizing DI-TMSS-80067B, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or Contractor Furnished Equipment (CFAE/CFE) Notices, or approved contractor formats. This process shall require government review and approval of recommended additional requirements prior to developing additional data.

6. TO Development. TOs shall be written to a scope and depth of coverage sufficient to support the TMQ53 operations and maintenance concepts developed by the government.

6.1. TO Data shall be developed to the specifications listed in table 1. Approved COTS Manuals shall be delivered with an Identifying TO Publication Sheet, IAW MIL-PRF-32216.

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

8. Data Rights. Contractors shall provide Unlimited Rights for all source data and TOs prepared specifically for the contract. Government rights in data are specified in the Defense Federal Acquisition Regulation Supplement (DFARS), 252.227-7013, Rights in Technical Data, Noncommercial Items, 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, and 252.227-7015, Technical Data- Commercial Items. 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 technical data.

9. Classification, Distribution, Destruction, Disclosure, and Export Control Notices. Contractors shall determine the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide (SCG) and DODM 5200.01, DODI 5230.24, AFI 31-401, AFI 61-204, and MIL-STD-38784 (available at http://www.e-publishing.af.mil/ or https://assist.dla.mil/online/start/index.cfm ). 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 content.

10. TO Quality. Contractors’ proposals shall describe how the government will be allowed to interact with the contractor’s TO development team. The contractors’ shall ensure TOs prepared are: a) technically accurate and safe;

b) written to a scope and depth of coverage sufficient to support the operations and maintenance concepts, and c) properly classified and marked with export control and distribution limitation statements. The contractor shall maintain a Technical Manual Quality Assurance Program (TMQAP) plan for this effort. The TMQAP shall be available for review at the TO Guidance Conference. The TMQAP shall be sufficiently detailed to support TO certification to include actual performance of procedures or desk-top analysis for non-procedural data. Simulation (walk-through/talk-through) should be reserved for those procedures which would activate explosive devices or present a hazard to personnel or equipment.

10.1. Guidance Conference. Working through the TOMA, the contractor shall co-host and participate in a guidance conference for this effort to be held within 60 calendar days after award of contract. The Technical Order Status and Schedule (TOSS) will be formalized at this conference. The contractor shall present a briefing on their interpretation of the basic contract, SOW, CDRLs, Data Item Descriptions (DIDs), MIL-SPEC, MIL-STD, SIRs, this document and the planned preparation and delivery of the TOs and related data.

10.3. TO Delivery Requirements for In-Process Reviews. IPR TO data shall be technically edited and reviewed according to the TMQAP. Manuscript (handwritten) data is not acceptable for any data to be reviewed. All tech data must be in the correct TO format. At each review, all TOs must be delivered in order to perform a full PPR. The TMQAP checklists shall be available for review by the government during the PPRs.

10.4. TO Certification. The contractor shall certify that new TO procedures and data developed to support the program are accurate, adequate, current, and usable for their intended purpose. The Government may witness the certification activities. The contractor shall incorporate comments generated by the certification process into the TOs prior to submitting the TOs for verification. At the completion of the certification, the contractor shall submit a letter to the TOMA stating that certification has been completed and that any deficiencies identified during the process have been corrected. The contractor will ensure all necessary changes and corrections to affected manuals are accomplished in time to meet contract delivery schedule requirements. The contractor shall notify the government at least 180 days prior to the need date of any Government Furnished Information/Government Furnished Equipment (GFI/GFE) required to perform certification tasks. Technical order 00-5-1 and 00-5-3 shall be referenced for additional information on TO Certification requirements.

10.5. Verification Support. The contractor shall support USAF verification activities as required by the TOMA and the program Verification Plan. Contractor verification support will consist of on station technical writing or engineering support and maintain a master mark-up of the document and record minute items during the Air Force verification process. The contractor shall also support all post verification reviews.

10.6. TO Prepublication Reviews (PPR). PPRs are examinations of TOs to ensure incorporation of agreed upon changes and to ensure the manual meets style and format requirements. The Contractor shall prepare and deliver copies of TOs and TO updates in MIL-SPEC compliance for the PPR as shown in the delivery matrix. The TOs for PPR shall have been approved by contractor QA, be in compliance with the MIL-SPECs/standards, and incorporate all verification comments and corrections approved by the TOMA or program management office representative. The TOMA may waive the PPR depending on number and complexity of changes from verification.

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

12. TO Maintenance. Contractors shall maintain TO’s by preparing emergency, urgent, routine changes/revisions or supplements and source data updates to incorporate corrections, equipment configuration changes, and maintenance and operational concept changes IAW TO 00-5-3.

12.1 TO Sustainment. The contractor shall receive all changes AFTO 252 and AFTO 22s for each system on a form 158 to be incorporated into the manuals from the TOMA/Program Office bi-annually each year. The contractor will have the time allotted per the 00-5-3 to incorporate the changes and deliver the complete updated manuals to the government. The government shall do a PPR to determine if all changes have been incorporated. If the contractor fails to incorporate all changes or if any changes have been incorporated incorrectly, the contractor shall correct the manual. Once the manual is corrected, the contractor shall re-deliver the manual for another PPR. The same process shall occur until all changes have been correctly incorporated. If the government has an out of cycle urgent change to be incorporated, the contractor shall incorporate and deliver an updated complete manual within 40 days. If the government has an out of cycle rapid action change or emergency change, the contractor shall incorporate and deliver this within 48 hours and deliver a complete up to date manual.

At the same time the form 158s AFTO 252s and AFTO 22s, are delivered for incorporation the contractor shall also make any necessary updates to the manuals for any system modifications or changes.

The contractor shall incorporate any out of cycle urgent and emergency changes AFTO 252s and AFTO 22s within the timeline specified in the 00-5-3.

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

14. Time Compliance Technical Orders (TCTOs). The contractor shall prepare TCTO’s, ITCTO’s and resulting TO updates as required in support of TMQ-53. TCTO’s will be used to document all permanent modifications, initiate special “one time” inspections, or impose temporary restrictions on systems or equipment within specified time limits effecting TMQ-53. Costs for TCTO package development must be in accordance with AFI 65-601Vol.1.

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

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

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

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

Section 2. TM Type and Delivery Requirements

NOTES:

· Mark the TM Type Selection Tables indicating the applicable TO types and related specifications.

· For COTS manuals the MIL-PRF-32216 will be used along with the below specifications.

PART A – (NEW…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .