Draft RFP Release LMTF ARES Test Stand CDRL Package - Industry 5 Dec 25.docx
DOCX document 576 KB Posted
- Solicitation number
- FA820726R0001
About this file
This is a Contract Data Requirements List (CDRL) package for the LMTF ARES Test Stand program, establishing technical data delivery obligations for contractors supporting the Air Force Nuclear Weapons Center's Intercontinental Ballistic Missile (ICBM) systems. The document provides comprehensive instructions and requirements for 37 separate data items (A001-A237) that contractors must deliver throughout contract performance.
The CDRL specifies detailed submission procedures, approval processes, and distribution requirements for diverse deliverables including the Integrated Program Management Data and Analysis Report (monthly submissions within 15 business days), Product Engineering Design Data and Associated Lists (with specific ASME standards compliance), Software Quality Assurance Reports, Cybersecurity Implementation Plans, Risk Management Framework packages, and financial reports including Cost and Hour Reports and Contractor Business Data Reports. All deliverables require Distribution Statement D markings (Department of Defense and U.S. DoD contractors only) with export control warnings and CUI (Controlled Unclassified Information) designations. Unclassified CDRLs must be submitted through TopVue (https://icbm.topvue.com/topvue-icbm/), while classified materials follow separate protocols via physical delivery to AFNWC/NIS Security Office. Government approval authority (ORG1, typically AFNWC/NIM Program Manager) has 20 business days for initial review, with contractors providing revisions within 5-30 business days depending on the data item. Specific technical standards include MIL-STD-31000B for Technical Data Packages, ASME Y14.100 for engineering drawings, NIST 800-53 for cybersecurity controls, and various DOD and Air Force instructions governing configuration management, program protection, and supply chain risk management. The organizational cross-reference list identifies 39 distribution recipients across AFNWC, DCMA, OSD CAPE, and base-level organizations responsible for specialized functions including cost management, software, security, safety, and cybersecurity oversight.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| LMTF ARES SOW_Industry_Draft.docx | DOCX document | |
| ARES Sources Sought_v1.docx | DOCX document |
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
Contract Data Requirements List (CDRL) Program: LMTF ARES Test Stand – Industry Date: 4 December 2025 Version: .01 Date of Determination: (Contract Award Date unless otherwise specified on the CDRL)
1. Introduction This document was developed in accordance with DOD MIL-STD 31000C and DODM 5010.12 Procedures for the Acquisition and Management of Technical Data. This represents the general requirements for the Technical Data Package (TDP) for this program.
The purpose of this Attachment, Technical Data Package, is to define the data deliverables due for this program, including the instructions for their development, and delivery. All specific delivery instructions are specified on the CDRL forms or its digital (word, excel, pdf) equivalent.
2. General Guidelines The CDRL form, Department of Defense (DD) Form 1423, specifies the data required to be delivered to the Government, as well as the frequency and approval requirements. The Data Item Descriptions (DIDs), listed on the CDRL form, were selected from the Acquisition Streamlining and Standardization Information System (ASSIST) and provide additional direction for data preparation.
3. Communications Any correspondence related to requests for data delivery deviations and/or amendments, additions or deletions to the CDRL form shall be addressed to the Procuring Contracting Officer (PCO) with a courtesy copy to the Data Management Officer (DMO) (Air Force Nuclear Weapons Center (AFNWC)/NIMED) and the cognizant Program Manager (PM). Copies of all forms and templates noted in this file are available as requested from PM, DMO, or PCO.
4. Codes used in the DD Form 1423 All CDRLs require Government approval. The directions for submittal and approval of data are indicated in Blocks 7, 8, 9, 10, 11, 12, 13, 14, 15, and 16 of the DD Form 1423. Usually, the direction is in the form of a code (explained below). The following abbreviations/codes are common usage within AFNWC.
4.1 Block 7, DD Form 250 Requirements
Block 7 of the CDRL form indicates whether Procurement Quality Assurance (PQA) inspections and acceptance of deliverable data by DD Form 250 is required. “Draft” copies submitted for advance approval and “Preliminary Draft” copies submitted are exempt from the DD Form 250 requirements. Information copies of DD Form 250 to accompany each letter of transmittal for this category of data.
| Code |
| Inspection |
| Acceptance |
| SS |
| Source (DD Form 250 or equivalent document) |
| Source (DD Form 250 or equivalent document) |
| DD |
| Destination (DD Form 250 or equivalent document) |
| Destination (DD Form 250 or equivalent document) |
| SD |
| Source (DD Form 250 or equivalent document) |
| Destination (DD Form 250 or equivalent document) |
| DS |
| Destination (DD Form 250 or equivalent document) |
| Source (DD Form 250 or equivalent document) |
| LT |
| Letter of Transmittal only |
| NO |
| No inspection or acceptance required |
4.2 Block 8, Approval Code (for PRE-Approval items)
When items of critical data requiring specific advanced approval or draft is required before distribution of final data item should be identified as (code “A”), the approval authority (ORG) for that 1423 is designated in Block 14. When document pre-approval or draft is not required (code “N/A”). When the data item requires submission of a draft document prior to publication of a final document, block 16 of the DD Form 1423 shall show the length of time required for Government approval and/or disapproval and subsequent turn-around time for the contractor to resubmit the data after Government approval and/or disapproval has been issued.
| Code |
| Description |
| A |
| PRE-Approval Required prior to Final Submission |
| N/A |
| PRE-Approval prior to Final Submission Not Required |
4.3 Block 10, Frequency of Submittals
| Code |
| Description |
| ANNLY |
| Annually |
| ASGEN |
| As generated |
| ASREQ |
| As required* |
| BI-MO |
| Each 2 months |
| BI-WE |
| Each 2 weeks |
| DAILY |
| Daily |
| DFDEL |
| Deferred delivery |
| EOQ |
| End of Quarter |
| MTHLY |
| Monthly |
| ONE/P |
| One-time preliminary draft |
| ONE/R |
| One time and revisions |
| OTIME |
| One time |
| QRTLY |
| Quarterly |
| R/ASR |
| Revisions as required |
| SEMIA |
| Each 6 months |
| WEKLY |
| Weekly |
| XTIME |
| Multiple separate submittals (i.e., 2Time, 3Time) |
* When ASREQ is used in Blocks 10, 11, 12 or 13 an explanation of the requirements must be entered in Block 16.
4.4 Block 11, 12 and 13, Dates of As of, Initial and Subsequent Submissions
| Code |
| Description |
| ASGEN |
| As generated |
| ASREQ |
| As required* |
| CDR |
| Critical Design Review |
| CD |
| Calendar Day(s) |
| DFDEL |
| Deferred delivery |
| EOC |
| End of contract |
| EOM |
| End of month |
| FQT |
| Formal Qualification Test |
| FCA |
| Functional Configuration Audit |
| PCA |
| Physical Configuration Audit |
| PDR |
| Preliminary Design Review |
| TRR |
| Test Readiness Review |
* When ASREQ is used in Blocks 10, 11, 12 or 13 an explanation of the requirements must be entered in Block 16.
Indicate SEE BLK 16 if submission requirements are listed in Block 16.
5. Supplemental Data Preparation Instructions:
5.1 Data Item Description (DID) Version
The most current version of the DID at the time of the award of the contract or Task Order, whichever date is most current, specified in Block 4, is to be used when submitting data. The most current version can be found at http://quicksearch.dla.mil/.
5.2 DID Tailoring
The DID is a specification for the preparation of data. A DID may only be tailored down, never added to. DID tailoring is reflected in Block 16 of the CDRL form. “T” entered after the DID number in Block 4, means that the DID has been tailored. Block 4 tailoring is made to either relax preparation instructions or to tailor the DID to be in consonance with the source document tailoring contained in the Statement of Work (SOW), Performance Work Statement (PWS) or Contractor Statement of Work (CSOW).
5.3 Scientific and Technical Information (STINFO) Distribution Statement Markings The designation in Block 9 of the CDRL form indicates that one of the following six (6) authorized distribution statements from Department of Defense Instruction (DoDI) 5230.24 and Department of the Air Force Instruction (DAFI) 61-201 shall be annotated on that technical data. Distribution statements will be selected to denote the audience for which the data is intended. A distribution statement marking is distinct from and in addition to a security classification marking assigned in accordance with (IAW) Department of Defense of Air Force 5200.01 Volume 2, Department of the Air Force Manual 16-1404, Volume 2. Should Block 9 of the CDRL form and the DID be in conflict, Block 9 of the CDRL form shall take precedence. The following distribution statements are authorized for use in marking of all documents:
Distribution Statement A:
Approved for public release. Distribution is unlimited.
Distribution Statement B:
Distribution authorized to U.S. Government Agencies (category), (date of determination). Other requests for this document must be referred to MMIII SPO (AFNWC/NIM), 6014 Dogwood Ave, Hill AFB UT 84056
Distribution Statement C:
Distribution authorized to U.S. Government Agencies and their contractors (category), (date of determination). Other requests for this document must be referred to MMIII SPO (AFNWC/NIM), 6014 Dogwood Ave, Hill AFB UT 84056.
Distribution Statement D:
Distribution authorized to Department of Defense and U.S. DoD contractors only (category), (date of determination). Other requests must be referred to MMIII SPO (AFNWC/NIM), 6014 Dogwood Ave, Hill AFB UT 84056.
Distribution Statement E:
Distribution authorized to DoD Components only (category), (date determination). Other requests must be referred to MMIII SPO (AFNWC/NIM), 6014 Dogwood Ave, Hill AFB UT 84056.
Distribution Statement F:
Further dissemination only as directed by MMIII SPO (AFNWC/NIM), 6014 Dogwood Ave, Hill AFB UT 84056 (date of determination) or higher DOD authority.
5.4 Other Notices
All technical documents marked with Distribution Statements B, C, D, E, or F will also be marked with the following notices:
Export Control Warning Statement:
This document contains technical data whose export is restricted by the Arms Export Control Act (Section 2751 of Title 22, United States Code) or the Export Control Reform Act of 2018 (Chapter 58 Sections 4801-4852 of Title 50, United States Code). Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25 and DoD Instruction 2040.02.
When the data is export controlled, include Export Control as one of the reasons IAW DoDI 5230.24 Section 3. Paragraph 3.4.i.
DoDD 5230.25 is available online at https://www.esd.whs.mil/DD/.
NOTE: The CDO Program Manager (PM) may remove the “Export Control Warning” if “critical technology” is not a reason annotated in the distribution statement and if the CDO PM can verify the technical report/document is not export control.
Note – When distributing export-controlled data, include the “Notice to Accompany…” IAW DoDD 5230.25 Enclosure 5, by paper copy or read-me-file.
Destruction Notice:
(destruction notices are now optional on Scientific/Technical information documents.)
Documents designated as Distribution B, C, D, E, or F shall be marked with one of the following statements:
For classified documents:
DESTRUCTION NOTICE: Follow the procedures in National Industrial Security Program Operating Manual (NISPOM) Title 32 § 117.15(g) and Title 32 § 2001.47, DoDM 5200.01, Volume 3,_DAFMAN 1404, Volume 3 Information Security Program: Protection of Classified Information , Enclosure 3, Paragraph 17.
For unclassified, limited documents: (destruction notices are now optional on Scientific/Technical information documents.
DESTRUCTION NOTICE: Record and non-record copies of CUI documents will be disposed of IAW Chapter 33 of Title 44, U.S.C. and the DoD Components’ records management directives. When destroying CUI, including in electronic form, agencies must do so in a manner making it unreadable, indecipherable, and irrecoverable.
Controlled Unclassified Information (CUI) Markings IAW DoDI5200.48_DAFI16-1403, Controlled Unclassified Information, mark all applicable documents with the appropriate CUI markings and CUI designation indicator block. Place the CUI designation indicator block at the bottom-right side of the first page or cover page when using the Limited Dissemination Control (LDC) marking and if using a distribution statement place CUI designation indicator block above the distribution statement Note - CUI marking requirements do not affect STINFO requirements, All CUI documents determined to warrant the use of a distribution statement must contain Controlled Technical Information (CTI).
5.5 Pricing CDRL Items Separately
If blocks 17 and 18 of the DD form 1423 documents are marked as "N/A" and "NSP" respectively, then the Government does not want to separately group or price CDRL items. If blocks 17 and 18 are left blank, the Government intends to seek separate pricing for the development costs of each CDRL. This pricing is for development costs of the data items and is considered separate from data rights costs.
6. Supplemental Data Delivery Instructions:
6.1 Due Dates
Due dates for delivery of data are to be construed as receipt at destination. Due dates are based on calendar days unless otherwise noted. If due date falls on a non-business day, i.e. weekend or holiday, due date is pushed to the next business day.
6.2 Late Delivery
Delivery of data is considered late if it does not arrive at its destination by 1530 hours (3:30 PM) Mountain Time on the date specified in Blocks 12, 13, or 16 of the CDRL.
6.3 Submittal Procedures:
6.3.1 CDRL Submittal Procedure
For the purposes of data submittal, unclassified CDRLs are submitted to the government via TopVue https://icbm.topvue.com/topvue-icbm/. For access to CDRLvue, the contractor must obtain and maintain T-1 eligibility, National Agency Check with Inquiries (NACI).
THIS IS FOR UNCLASSIFIED CDRL SUBMITTALS ONLY.
(See below for Classified CDRL submittals (6.3.2)) Each data submittal shall be accompanied by a CDA form (please request current version from ORG1). If for any reason a CDA form is not available, a cover letter shall contain the following information:
1. Contract number
2. CDRL sequence number (e.g., A001)
3. Exact title and subtitle (if applicable) of the document being transmitted
4. Line item or CLIN number
5. Modification Number or Order Number
6. Document date, number, and revision information (if applicable)
7. Data delivery method and date of delivery
8. Whether the document is a draft or final submittal
9. For approval data: State “For Approval”
10. If the document is a re-submittal, reference the Government letter CDA requesting re-submittal or disapproval of previous submittal
11. For periodic reports: The report period that the document covers
12. Distribution: Information disclosing the total contractual distribution being made per Block 14 or Block 16 of the CDRL Form
6.3.2 Classified CDRL Submittal Procedure
If any deliverables contain classified information, contractor must obtain and maintain T-3 eligibility, National Agency Check with Law and Credit (NACLC). Classified CDRLs and classified documentation are submitted IAW this instruction and are never to be emailed.* Classified CDRLs or portions of a CDRL, as applicable, shall be forwarded IAW Appendix B of the DD254 and 32 CFR Part 117, National Industrial Security Program Operating Manual (NISPOM). For Classified Disks send two (2) copies.
Outer Envelope:
Address ATTN: AFNWC/NIS MMIII Security Office
Inner Envelope:
Address ATTN: Name of person for whom the document should be delivered
*A letter of delivery shall be submitted to TopVue https://icbm.topvue.com/topvue-icbm/csswb/login , when classified data is delivered via the instructions above.
7. Supplemental Data Review and Approval Process:
7.1 CDRL Approvals
Government must approve/disposition each data item. In addition, Block 16 of the form may contain additional directions. Types of dispositioning that occur are as follows:
| Written Approval |
| “Written Approval” indicates agreement or concurrence with the contractor furnished data only and shall not be construed as changing any of the terms or conditions of the subject contract. The approval authority shall be ORG 1 as outlined in section 9 of this document. Approval shall take the form of concurrence using the CDA form, signed and dated by the representative stated in ORG 1. Data items submitted for approvals are NOT automatically approved without government approval. |
Approved with Comment or Disapproved The Contractor shall revise data items “Approved with Comments or Disapproved” IAW the specific written comments transmitted with the CDA or PCO/DMO letter and resubmit not later than 30 calendar days (unless otherwise directed) from receipt of the “Approved with Comments or Disapproved”, unless otherwise directed. The resubmitted data will require a new approval cycle as indicated in Block 16 of the DD Form 1423.
Draft Versions of the CDRL If a DD Form 1423 directs the Contractor to submit a “draft” version of an approval CDRL in advance of the final version, the draft will be considered an information only submission. However, the PM/DMO still retains the right to disapprove a draft data item that does not comply with the contract requirements. Unless otherwise directed by the PCO, the Contractor shall incorporate the Government’s comments in the final submission and shall not resubmit the draft version of the data item.
7.2 Contractual Document Action (CDA)
After the Government receives a data item submission, a Temporary Data Identification (TDID) number, a unique identifier to that submission, will be assigned by the DMO. The Government’s review of that data item will result in a coordinated CDA form, or PCO letter, indicating the data item’s approval or disapproval. Should the Government have comments on the data item, the CDA will include either comments on the CDA form itself or a Comment Resolution Matrix (CRM). Comments will be provided to the submitter IAW the format and timeline noted in block 16. Comments will be assigned one of the following codes:
| COMMENT CODE |
| CODE DESCRIPTION |
| C |
| Critical |
| Comments of a very serious nature that will preclude final approval and publication of the document. You are willing to elevate the comment or issue to senior organization leadership (e.g., General Officer) and recommend they non-concur. These are the "show-stoppers". Convincing rationale for critical comments must be provided. The individual making the comment and the document writer will reconcile the comment. |
| S |
| Substantive |
| Comments of a less serious nature that have noticeable impact on the document’s quality or content. The document appears to be incorrect, misleading, confusing, or inconsistent with other sections. |
| A |
| Administrative |
| Comments that address minor items such as typographical, format and/or grammatical errors. |
7.3 Information Only CDRLs
When an “A” is not indicated in Block 8 of the DD Form 1423, the PM/DMO still retains the right to disapprove any data that does not comply with contract requirements. The Contractor shall revise the disapproved data IAW with the specific written comments transmitted with the CDA form or PCO letter and resubmit not later than 30 calendar days, unless otherwise directed, from receipt of the disapproval. The resubmitted data will require a new approval cycle as indicated in Block 8 of the DD Form 1423.
8. Data Accession List (DAL) During performance of the contract, requests from the PCO for data ordered from the Data Accession List (DAL) (with the application of the current version, for DID DI-MGMT-81453) shall be provided at no increase in contract price. Requests for quantities greater than two each per document shall be honored upon receipt of PCO direction and with Contractor concurrence that such request can be filled at no increase in contract price.
9. Organizational Cross Reference List The following Organizational Cross Reference List shall be used in conjunction with the CDRLs to determine actual addressees for distribution of data. The ORG number will be entered in lieu of an address on the CDRL and will be a part of the CDRL package. Changes to the list will be identified by an asterisk next to the ORG number and a revision date to the list. Any changes to the Attention/To or Contract Info list will not require a contract mod.
| ORG#/ Name |
| Address |
| Attention/To |
| Contact Info |
ORG1/AFNWC/NIM
Hill AFB UT 84056
| Program PM |
| PM’s email |
ORG2/AFNWC/NIM
Hill AFB UT 84056
| Program Engineer |
| Program Engineer’s email |
ORG3/AFNWC/NIM
Hill AFB UT 84056
| Alt Program Manager |
| Alt PM’s email |
| ORG4/AFNWC/NIMED |
| 6054 Dogwood Ave Bldg 1255 |
Hill AFB UT 84056
| CM |
| afnwc.nies.icbm.conm@us.af.mil |
| ORG5/AFNWC/NIMED |
| 6054 Dogwood Ave Bldg 1255 |
Hill AFB UT 84056
| Software |
| afnwc.nies.icbm.conm@us.af.mil |
| ORG6/AFNWC/NIMED |
| N/A |
| ORG7/AFNWC/NIML |
| N/A |
| ORG8/AFNWC/NIME |
| 6054 Dogwood Ave Bldg 1255 |
Hill AFB UT 84056
| Risk Management |
| afnwc.nies.riskmgmt@us.af.mil |
| ORG9/AFNWC/NIMES |
| 6054 Dogwood Ave Bldg 1255 |
Hill AFB UT 84056
| Safety |
| afnwc.niev.safetymanager@us.af.mil |
| ORG10/AFNWC/NIS |
| 6014 Dogwood Ave Bldg 1258 |
Hill AFB UT 84056
| Security |
| AFNWC.MMIII.Security@us.af.mil |
| ORG11/AFNWC/NIMES |
| N/A |
| ORG12/AFNWC/NIMES |
| N/A |
| ORG13/AFNWC/NIMES |
| N/A |
| ORG14/AFNWC/NIML |
| N/A |
| ORG15/AFNWC/NIME |
| N/A |
| ORG16/AFNWC/NIME |
| N/A |
| ORG17/AFNWC/NIMES |
| N/A |
| ORG18/AFNWC/NIMET |
| N/A |
| ORG19/AFNWC/NIMES |
| N/A |
| ORG20/AFNWC/NIME |
| N/A |
| ORG21/AFNWC/NIMET |
| N/A |
| ORG22/AFNWC/NIML |
| 6014 Dogwood Ave Bldg 1258 |
Hill AFB UT 84056
| Program Protection |
| afnwc.cyberppp@us.af.mil |
| ORG23/AFNWC/NMASF |
| N/A |
| ORG24/AFGSC/A3TT |
| N/A |
| ORG25/AFNWC/NMLA |
| N/A |
| ORG26/406 SCMS/GULAB |
| N/A |
| ORG27/406 SCMS/GULAA |
| N/A |
| ORG28/419 SCMS/GUBA |
| N/A |
| ORG29/75 ABW/SE |
| 7290 8th St Bldg 383 |
Hill AFB UT 84056 Base Safety
75abw.se.workflow@us.af.mil
| ORG30/DCMA/ACO |
| N/A |
| ORG31/AFNWC/NIMF |
| 6008 Wardleigh Rd Bldg 1580 |
Hill AFB UT 84056
| Cost/Funds |
| AFNWC.MMIII.Cost@us.af.mil |
| ORG32/AFNWC/PZ |
| 6008 Wardleigh Rd Bldg 1580 |
Hill AFB UT 84056
| Program CO |
| Program CO Email |
| ORG33/AFNWC/NIMED |
| 6054 Dogwood Ave Bldg 1255 |
Hill AFB UT 84056
| Data Management |
| afnwc.nies.datamgmtoffice@us.af.mil |
| ORG34/AFNWC/NIMES/SIV |
| 6054 Dogwood Ave Bldg 1255 |
Hill AFB UT 84056
| SIV |
| afnwc.nie.siv@us.af.mil |
| ORG35/AFNWC/AEDC |
| N/A |
| ORG36/AFNWC/NIS |
| 6014 Dogwood Ave Bldg 1258 |
Hill AFB UT 84056
| MMIII Security |
| afnwc.MMIII.security@us.af.mil |
| ORG37/406 SCMS/GULAA |
| N/A |
| ORG38/AFNWC/NIMH |
| N/A |
| ORG39/OSD CAPE |
| OSD CADE |
| Cost/Funds |
| https://dcarc.cape.osd.mil |
10. CDRL Master Listing Index
Full 1423’s for CDRL’s applicable to this program are included in section 11 of this document.
| CDRL# |
| Title |
| DID# |
| CDRL# |
| Title |
| DID# |
| A001 |
| Integrated Program Management Data and Analysis Report (IPMDAR) - FULL no tailoring |
| DI-MGMT-81861C/T |
| A002 |
| Meeting Agenda |
| DI-ADMN-81249C |
| A003 |
| Briefing Material - to include Quick Looks |
| DI-MGMT-81605 |
| A006 |
| Contract Work Breakdown Structure |
| DI-MGMT-81334D |
| A008 |
| Work Management Plan - Associate Contractor Agreements |
| DI-MGMT-81911/T |
| A008-1 |
| Work Management Plan - Design Review |
| DI-MGMT-81911/T |
| A027 |
| Product Engineering Design Data and Associated Lists |
| DI-SESS-81000F/T |
| A031 |
| Engineering Change Proposal (ECP) |
| DI-SESS-80639E |
| A037 |
| Request for Variance (RFV) |
| DI-SESS-80640E |
| A054 |
| Computer Program Identification Number (CPIN) Catalog Information |
| DI-MISC-81454D |
| A059-1 |
| Technical Report - Study/Services - Vulnerability Attacks |
| DI-MISC-80508B/T |
| A059-2 |
| Technical Report - Study/Services - Root Cause Analysis |
| DI-MISC-80508B/T |
| A071 |
| Accident/Incident Report - Mishap Report |
| DI-SAFT-81563 |
| A105 |
| Information Systems Accreditation Documentation |
| DI-ADMN-80239 |
| A106 |
| Program Protection Implementation Plan (PPIP) |
| DI-ADMN-81306 |
| A108 |
| Government Property (GP) Inventory Report |
| DI-MGMT-80441D |
| A112 |
| Report of Receipts, Inventory, Adjustments, and Shipments of Government Property |
| DI-MGMT-80442 |
| A114 |
| DOD Risk Management Framework (RMF) Package Deliverables |
| DI-MGMT-82001A |
| A115 |
| Cybersecurity Implementation Plan |
| DI-MGMT-82002B |
| A116 |
| Supply Chain Risk Management (SCRM) Plan |
| DI-MGMT-82256A |
| A117 |
| Cybersecurity Vulnerability Report |
| DI-MGMT-82191 |
| A118 |
| Software Quality Assurance Report |
| DI-QCIC-81795 |
| A126 |
| Small Business Subcontractor Report |
| DI-MGMT-81642 |
| A141 |
| Operations Security (OPSEC) Plan |
| DI-MGMT-80934C |
| A171 |
| Software Documentation |
| DI-IPSC-81756 |
| A172 |
| Software Transition Plan (STRP) |
| DI-IPSC-81429A |
| A173 |
| Software Sustainability Package |
| DI-IPSC-82134 |
| A201 |
| Program-Unique Specification Documents |
| DI-SDMP-81493A |
| A223 |
| Contractor's Standard Operating Procedures (SOP) |
| DI-MGMT-81580 |
| A227 |
| Anti-Tamper Plan |
| DI-SCRE-82399 |
| A231 |
| Cost and Hour Report (Flex File) |
| DI-FNCL-82162 |
| A235 |
| Contractor Business Data Report (CBDR) |
| DI-FNCL-81765C |
| A237 |
| Technical Data Report |
| DI-MGMT-82165 |
11. DD Form 1423s (full 1423’s) *1423’s, block A Reference Number: CLIN number to be added at time of award **1423’s block E Reference Number: Contract and Mod/TO number to be added at time of award ***1423’s block G & I will be signed at time of award ****1423’s Reference Blk G for status of CDRL package.
Prepared by Approved by
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
Form Approved 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 this burden, to the Department of Defense, Executive Services and Communications Directorate (07040188). 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.
TBD
B. EXHIBIT
A
C. CATEGORY
TDP
TM
OTHER
X
D. SYSTEM/ITEM
LMTF ARES Test Stand
E. CONTRACT/PR NO.
TBD
F. CONTRACTOR
TBD
1. DATA ITEM NO.
A001
2. TITLE OF THE DATA ITEM
See Block 16
3. SUBTITLE
FULL no tailoring
4. AUTHORITY
(Data Acquisition Document No.)
DI-MGMT-81861C/T
5. CONTRACT REFERENCE
See Block 16
6. REQUIRING OFFICE
AFNWC/NIMF
17. PRICE GROUP
18.
ESTIMATED TOTAL PRICE
7. DD 250 REQ
LT
8. APP CODE
A
9.
DIST STATEMENT REQUIRED
D
10. FREQUENCY
Monthly
12.
DATE OF FIRST SUBMISSION
SEE BLK 16
11. AS OF DATE
N/A
13.
DATE OF SUBSEQUENT SUBMISSION
SEE BLK 16
14.
DISTRIBUTION
a. ADDRESSEE
b. COPIES
Draft
Final Reg Repro
LM
25-07
EVM-CR
ORG 31 (LODO)
ORG 1 (LODO)
ORG 2 (LODO)
ORG 32 (LODO)
ORG 33 (LODO)
16. REMARKS: Changes to office symbols, when necessary, shall be made by the CO/ACO without revisions to the CDRL.
Block 2: Integrated Program Management Data and Analysis Report (IPMDAR)
Block 5: SOW Para 3.2.1.8.1, 3.2.1.10, 3.2.4.2, 7.15.1, 7.15.2
BLOCK 9:
Distribution Statement D: (see paras 5.3 & 5.4 of instructions for distribution statement, warning, and destruction notices, and CUI marking requirements).
BLOCK 4 TAILORING: Data Item Description (DID) DI-MGMT-81861C/T is the authoritative source for the IPMDAR requirement. Items contained within this CDRL represent only tailored items; refer to the DID for all other requirements.
1.4 Direct Reporting Contractor Role
1.4.1 A Direct Reporting Contractor is any contractor required to provide the IPMDAR directly to the Government. This includes prime contractors, subcontractors, intra-company work orders (IWOs), and other agreements, based on the contract type, value, duration, nature of the work scope, and the criticality of the information. In this document, instances of "Contractor" are synonymous with "Direct Reporting Contractor."
1.4.2 Subcontractor/IWO Reporting: Prime contractors are responsible for flowing down IPMDAR requirements contained in their prime contracts to all subcontractor/IWO's who meet the reporting thresholds specified in the DAU AAFDID EVMS Reporting Requirements Table, or as required by the program office. This includes requiring subcontractor/IWO's to electronically report directly to the Government per BLOCK 14 of this CDRL.
1.6 Electronic Submission and Files
1.6.2.2 The Contractor shall deliver the schedule file in the Contractor's native file format and a validated .xer (Oracle Primavera P6) file for each delivery. The .xer file dates, logic, critical path, driving path, columns, resource loading, etc., must match the internal schedule executes to. The Government will use the .xer file as the Source of Truth. The native schedule file shall be consistent with the Contractor’s schedule tool for all other Direct Reporting Contractors. The Data Dictionary shall be included as part of the Contractor’s native schedule file, or in human-readable file format (e.g., .pdf, .xlsx, .docx), containing searchable text, in accordance with the Contractor’s internal system description.
1.6.3 The Performance Narrative Report (Executive Summary and Detailed Analysis) shall be provided electronically in the contractor's human-readable file format (e.g., DOCX, PDF), containing searchable text. Variance analysis shall be provided in Excel format using a consistent template; all template changes shall be identified in the Executive Summary.
2.3 Contract Performance Dataset (CPD) shall:
2.3.2 Performance Data – All data provided in the CPD shall be reported in both whole dollars and hours.
2.3.2.1.4 Work Packages – The contractor shall provide data at the work package (WP) level, work packages shall be traceable to the associated control accounts. A work package is the point at which work is planned, progress is measured, and earned value is computed. (Refer to CPD FFS 2.2.15)
2.3.2.5.1 Cost Variance Adjustments. If the contractor adjusts or eliminates variances applicable to completed work, the adjustments made to the cost variances shall be provided by work package. Note: adjustments made shall be See continuation sheet...
15. TOTAL
G. PREPARED BY
H. DATE
I. APPROVED BY
J. DATE
DD FORM 1423-1, FEB 2001
PREVIOUS EDITION MAY BE USED.
Page 1 of 3 Pages
A. CONTRACT LINE ITEM NO.
TBD
B. EXHIBIT
A
C. CATEGORY
TDP
TM
E. CONTRACT/PR NO.
TBD
F. CONTRACTOR
TBD
16. REMARKS (Continued) reported as amounts added to the old variances to reach the new variances (or to eliminate the variances, as applicable).
2.3.2.5.2 Schedule Variance Adjustments. If the contractor adjusts the schedule variances for completed work, the adjustments made to the schedule variances shall be provided by work package. Note: adjustments made shall be reported as amounts added to the old variances to reach the new variances (or to eliminate the variances, as applicable).
2.4 Schedule (Native Schedule File and Schedule Performance Dataset (SPD)) shall:
2.4.2.21 Schedule Risk Assessment (SRA). SRAs are required 45 business days prior to any IBR, implementation of an OTB or OTS, major program review, or major milestone. In addition, an SRA is required anytime there is a 10% estimated slip to any major milestone, program review, or program completion. The inputs (e.g., three-point estimates) from the most recent SRA shall be provided in the Native Schedule File submission. Results of the SRA shall be discussed in the Performance Narrative Report.
2.4.3.1 Custom/User-Defined Fields. Custom/user-defined fields may be required for specific information not otherwise included in the Schedule. (Refer to SPD FFS 2.2.4, 2.2.5, 2.2.11, and 2.2.12)
Columns:
1. Driving Path Indicator – Should indicate primary, secondary, & tertiary driving paths for all major program milestones
2. Earned Value Technique – Task’s assigned Earned Value Technique in accordance with the contractor’s Earned Value System Description
3. SRA Uncertainty Risk Profile – Indicates the assigned uncertainty bin in accordance with the contractor’s SRA Methodology
4. IMP Cross-reference – Indicates the IMP Element ID associated with the activity
5. SOW Cross-reference – Indicates the SOW Paragraph ID associated with the activity
6. Risk ID Cross-reference – Indicates the discrete risk ID associated with the activity from the contractor’s risk management system software
7. WBS Path – Indicates the WBS number associated with the activity
8. OBS – Indicates which team owns the activity in accordance to the contractor's Organizational Breakdown Structure
9. Work Package Type – Indicates the activity’s associated work package type i.e. Labor, LOE, Subcontractor, IWO, Material, or Planning Package (Nullable for Milestones)
10. GFE Indicator – Indicates if the activity is dependent on Government Furnished Equipment
11. Control Account Number – Indicates the activity’s associated Control Account ID
12. CAM – Indicates the CAM who owns the work for the activity
13. Constraint Justification – Text field that clearly justifies the use of hard and soft constraints. Applicable to Task-Dependent and Milestone activities.
14. Lag Justification – Text field that clearly justifies the use of lag between two activities. Applicable to Task-Dependent and Milestone activities.
15. Comments – Any comments associated with the activity that the contractor would like to share with Gov’t reviewers.
Activity Codes
1. Baseline Change Request Number – Indicates the BCR Number associated with any changes to the activity’s baseline values
2. Company (SubK/IWO) – Indicates which SubK/IWO company is associated with the activity
3. Earned Value Technique – Tasks’ assigned Earned Value Technique in accordance with the contractor’s Earned Value System Description (LOE, Milestone, Planning Package or Labor)
4. Task Planning Level – Indicating if the activity is in a work package or planning package (Nullable for Milestones)
5. Resource Type – Indicating if task resources are Labor, ODC, Material, SubK or IWO 2.4.3.2 Resources – Resource loading is required as part of the Schedule in both the SPD and Native Schedule File. (Refer to SPD FFS 2.2.16, 2.2.17, 2.2.18, and 2.2.19) Refer to section 1.6.2.2 of this CDRL for additional guidance
2.5 Performance Narrative Report shall:
2.5.1 Performance Narrative Report – The Performance Narrative Report is comprised of the Executive Summary and the Detailed Analysis. The Executive Summary and the Detailed Analysis shall reflect both whole dollars and hours where applicable. The Government may request additional specific and/or clarifying information in the following month’s report.
2.5.1.2 Single Delivery – The Executive Summary and Detailed Analysis reports shall be delivered as defined in BLOCK 12, 13, & 14 of this CDRL
2.5.3 Detailed Analysis
2.5.3.4 Variance Analysis Selection
2.5.3.4.2 Government Specified Variance Analysis Thresholds
i. Variance Analysis Thresholds:
1 ) Current Period Cost and Schedule Variances +/-$20K and +/-10 %
2) Cumulative Cost and Schedule Variances +/-$50K and +/-10%
3) At Complete Variances (BAC-EAC) +/-$100K and +/-10%
4) The Government or contractor may identify additional variances beyond those that exceed the above thresholds to cover emerging trends. Items shall be reviewed monthly for continued applicability.
ii. Variance analysis thresholds will be reviewed periodically and adjusted as necessary to ensure they continue to provide appropriate insight and visibility to the Government. Adjustments will be made by contract modification with no
Page 2 of 3 Pages
A. CONTRACT LINE ITEM NO.
TBD
B. EXHIBIT
A
C. CATEGORY
TDP
TM
E. CONTRACT/PR NO.
TBD
F. CONTRACTOR
TBD
16. REMARKS (Continued) change in contract price.
iii. Refer to Section 1.6.3 of this CDRL for additional guidance Table 2.1 – Detailed Analysis Table (tailored changes): frequency is monthly unless otherwise annotated.
i. Variances At Control Account (CA) Level
1. Provide the root cause, impact (to include impact to EAC), mitigation plan/corrective actions, and expected recovery dates for variance analyses at the control account level.
2. Discuss any schedule variance in terms of float and the impact to the program critical path or driving paths, if any and identify significant missed milestones, impact to major milestones, and expected recovery dates.
3. If there are no changes to the reportable element issue description, the expected impacts, or corrective action plans, then specify, “No changes since the last reported analysis” and reference the IPMDAR date when the original narrative was reported.
4. Refer to Section 1.6.3 of this CDRL for additional guidance.
ii. Baseline Changes
1. Changes to cost/schedule baseline; shifts in time phasing, changes in total budget, retroactive changes, and content changes shall be traced to the CA level
iii. UB Analysis
1. Identify the components of the UB as of the current reporting period and the estimated data month the components will be distributed from UB. UB changes shall be traced to the CA level. Discuss changes, if any, from the previous IPMDAR.
iv. MR Analysis
1. Identify the changes to or the allocation of MR during the reporting period by control account and provide a brief explanation for MR value change or allocation.
Table 2.2 – Detailed Analysis Table (Tailored Changes): frequency is monthly unless otherwise annotated.
i. Staffing Changes
1. Staffing changes of +/- 5% from prior reporting period by organization and traced to a CA with reason for changes, major risks in staffing projection with explanation of impact(s).
ii. Major Subcontractors/Supplier
1. Identification of major subcontractors with EVM flow down requirements to include those not yet definitized.
iii. Rates
1. Identify impact of rates changes to EAC and/or MR at the contract level.
iv. Schedule Health
1. Results of any internal schedule health analysis plus one using the DCMA 14 point. The government will continue to monitor and research the metrics used for schedule health and may update the metrics used beyond the DCMA 14 point assessment if it is deemed valuable for program health tracking.
2. Data delivered must pass Government functional validation that data complies with DID( Reference Block 4)
BLOCK 10, 11, 12 & 13: BLOCK 9: See paragraph 5.3 & 5.4 of instructions for distribution statement warning, and destruction notices.
BLOCK 12 – Date of First Submission & BLOCK 13 – Date of Subsequent Submissions
1.8 Delivery Timing 1.8.1 Monthly Submission Requirement – IPMDAR data shall be required monthly, no later than 15 business days after the close of the contractor's accounting period. All reports shall reflect data from the same accounting period.
1.8.1.1 Monthly Submission Requirement – Contractor shall submit subsequent IPMDAR, containing the required Formats, NLT 15th business day of each month thereafter. Final submissions are due when the last significant milestone/deliverable as defined by the contract has been achieved and remaining risk areas have been mitigated. Government will be allowed 20 business days, after receipt from contractor, to review approval/disapproval/comments. Contractor shall submit revised IPMDAR incorporating Government comments, if applicable, NLT 5 business days after receipt from Government. If the Government does not provide written approval/disapproval/comments for a deliverable within the allotted time, the CDRL will be automatically approved.
BLOCK 14:
The native schedule shall be submitted electronically in accordance with the DoD-approved schemas and guidelines located on the AAP EVM website. All IPMDAR files must be electronically forwarded to the EVM-CR at the EVM AAP website https://evm.acq.osd.mil. Contractor shall a submit letter of delivery of IPMDAR to TopVue https://icbm.topvue.com/topvue-icbm/.
Page 3 of 3 Pages
Form Approved 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 this burden, to the Department of Defense, Executive Services and Communications Directorate (07040188). 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.
TBD
B. EXHIBIT
A
C. CATEGORY
TDP
TM
E. CONTRACT/PR NO.
TBD
F. CONTRACTOR
TBD
1. DATA ITEM NO.
A002
2. TITLE OF THE DATA ITEM
Meeting Agenda
3. SUBTITLE
4. AUTHORITY
(Data Acquisition Document No.)
DI-ADMN-81249C
5. CONTRACT REFERENCE
SOW Para 3.2.4.1, 3.2.4.2
AFNWC/NIMET
8. APP CODE
A
9.
DIST STATEMENT REQUIRED
D
10. FREQUENCY
As Reqd
12.
DATE OF FIRST SUBMISSION
N/A
11. AS OF DATE
N/A
13.
DATE OF SUBSEQUENT SUBMISSION
N/A
Reg Repro
LM
25-07
16. REMARKS: Changes to office symbols, when necessary, shall be made by the CO/ACO without revisions to the CDRL.
BLOCK 9:
Distribution Statement D: (see paras 5.3 & 5.4 of instructions for distribution statement, warning, and destruction notices, and CUI marking requirements).
BLOCKS 10, 11, 12 & 13:
Contractor shall submit Meeting Agenda, if applicable, NLT 5 business days prior to scheduled meetings or meetings deemed necessary by the Government.
Government will be allowed 2 business days, after receipt from contractor, to review for approval/disapproval/comments. Contractor shall submit revised Meeting Agenda incorporating Government comments, if applicable, NLT 2 business days after receipt from Government.
BLOCK 14:
For unclassified deliverables, contractor shall submit Meeting Agenda to TopVue https://icbm.topvue.com/topvue-icbm/ as per instructions (see paragraph 6.3.1).
For classified deliverables, contractor shall submit Meeting Agenda via instructions (see paragraph 6.3.2), and a letter of delivery to TopVue.
15. TOTAL
Page 1 of 1 Pages
Form Approved 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 this burden, to the Department of Defense, Executive Services and Communications Directorate (07040188). 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.
TBD
B. EXHIBIT
A
C. CATEGORY
TDP
TM
E. CONTRACT/PR NO.
TBD
F. CONTRACTOR
TBD
1. DATA ITEM NO.
A003
2. TITLE OF THE DATA ITEM
Briefing Material
3. SUBTITLE
to include Quick Looks
4. AUTHORITY
(Data Acquisition Document No.)
DI-MGMT-81605
5. CONTRACT REFERENCE
SOW Para 3.2.4.1, 3.2.4.2
8. APP CODE
A
9.
DIST STATEMENT REQUIRED
D
10. FREQUENCY
As Reqd
12.
DATE OF FIRST SUBMISSION
SEE BLK 16
11. AS OF DATE
N/A
13.
DATE OF SUBSEQUENT SUBMISSION
N/A
Reg Repro
LM
16. REMARKS: Changes to office symbols, when necessary, shall be made by the CO/ACO without revisions to the CDRL.
Distribution Statement D: (see paras 5.3 & 5.4 of instructions for distribution statement, warning, and destruction notices, and CUI marking requirements).
BLOCKS 10, 11, 12 & 13:
Contractor shall submit Briefing Materials, to include Quick Looks (Quick looks may be emailed) NLT 5 business days prior to each scheduled meeting and/or any other meeting deemed necessary by the Government and as requested by the Government. Government will be allowed 2 business days, after receipt from contractor, to review for comments. Contractor shall present corrected Briefing Materials incorporating Government comments, if applicable, NLT 2 business days after receipt from Government. Quick Looks may be submitted via email to the Government Program Manager.
BLOCK 14:
For unclassified deliverables, contractor shall submit Briefing Materials to TopVue https://icbm.topvue.com/topvue-icbm/ as per instructions (see paragraph 6.3.1).
For classified deliverables, contractor shall submit Briefing Materials via instructions (see paragraph 6.3.2), and a letter of delivery to TopVue.
15. TOTAL
Form Approved 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 this burden, to the Department of Defense, Executive Services and Communications Directorate (07040188). 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.
TBD
B. EXHIBIT
A
C. CATEGORY
TDP
TM
E. CONTRACT/PR NO.
TBD
F. CONTRACTOR
TBD
1. DATA ITEM NO.
A006
2. TITLE OF THE DATA ITEM
Contract Work Breakdown Structure
DI-MGMT-81334D
5. CONTRACT REFERENCE
SOW Para 7.9.1
8. APP CODE
A
9.
DIST STATEMENT REQUIRED
D
10. FREQUENCY
As Reqd
12.
DATE OF FIRST SUBMISSION
SEE BLK 16
11. AS OF DATE
N/A
13.
DATE OF SUBSEQUENT SUBMISSION
SEE BLK 16
Reg Repro
LM
16. REMARKS: Changes to office symbols, when necessary, shall be made by the CO/ACO without revisions to the CDRL.
Distribution Statement D: (see paras 5.3 & 5.4 of instructions for distribution statement, warning, and destruction notices, and CUI marking requirements).
BLOCKS 10, 11, 12 & 13:
Contractor shall submit Contract Work Breakdown Structure (CWBS) NLT 30 business days after award of contract. Contractor shall submit updated CWBS annually per option period. Government will be allowed 30 business days, after receipt from the contractor, to review for comments. Contractor shall submit revised CWBS incorporating Government comments, if applicable, NLT 15 business days after receipt from Government.
BLOCK 14:
For unclassified deliverables, contractor shall submit CWBS to TopVue, https://icbm.topvue.com/topvue-icbm/ as per instructions (see paragraph 6.3.1).
For classified deliverables, contractor shall submit CWBS via instructions (see paragraph 6.3.2), and a letter of delivery to TopVue.
15. TOTAL
Form Approved 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 this burden, to the Department of Defense, Executive Services and Communications Directorate (07040188). 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.
TBD
B. EXHIBIT
A
C. CATEGORY
TDP
TM
E. CONTRACT/PR NO.
TBD
F. CONTRACTOR
TBD
1. DATA ITEM NO.
A008
2. TITLE OF THE DATA ITEM
Work Management Plan
3. SUBTITLE
Associate Contractor Agreements
4. AUTHORITY
(Data Acquisition Document No.)
DI-MGMT-81911/T
5. CONTRACT REFERENCE
SOW Para 7.6
AFNWC/NIMES/SIV
8. APP CODE
A
9.
DIST STATEMENT REQUIRED
D
10. FREQUENCY
As Reqd
12.
DATE OF FIRST SUBMISSION
SEE BLK 16
11. AS OF DATE
SEE BLK 16
13.
DATE OF SUBSEQUENT SUBMISSION
SEE BLK 16
Reg Repro
LM
ORG 34 (LODO)
16. REMARKS: Changes to office symbols, when necessary, shall be made by the CO/ACO without revisions to the CDRL.
Distribution Statement D: (see paras 5.3 & 5.4 of instructions for distribution statement, warning, and destruction notices, and CUI marking requirements).
BLOCKS 10, 11, 12 & 13:
Contractor shall submit Work Management Plan (Associate Contractor Agreements) NLT 30 business days after request from Government.
Government will be allowed 20 business days, after receipt from contractor, to review for approval/disapproval/comments. Contractor shall submit revised Work Management Plan (Associate Contractor Agreements) incorporating Government comments, if applicable, NLT 20 business days after receipt from Government.
BLOCK 14:
For unclassified deliverables, contractor shall submit Work Management Plan (Associate Contractor Agreements) to TopVue https:
//icbm.topvue.com/topvue-icbm/ as per instructions (see paragraph 6.3.1).
For classified deliverables, contractor shall submit Work Management Plan (Associate Contractor Agreements) via instructions (see paragraph 6.3.2), and a letter of delivery to TopVue.
15. TOTAL
Form Approved 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 this burden, to the Department of Defense, Executive Services and Communications Directorate (07040188). 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.
TBD
B. EXHIBIT
A
C. CATEGORY
TDP
TM
E. CONTRACT/PR NO.
TBD
F. CONTRACTOR
TBD
1. DATA ITEM NO.
A008-1
2. TITLE OF THE DATA ITEM
Work Management Plan
3. SUBTITLE
Design Review
4. AUTHORITY
(Data Acquisition Document No.)
DI-MGMT-81911/T
5. CONTRACT REFERENCE
SOW Para 3.2.1.8.1, 3.2.1.10, 3.2.4.2
AFNWC/NIMES/SIV
8. APP CODE
A
9.
DIST STATEMENT REQUIRED
D
10. FREQUENCY
As Reqd
12.
DATE OF FIRST SUBMISSION
SEE BLK 16
11. AS OF DATE
SEE BLK 16
13.
DATE OF SUBSEQUENT SUBMISSION
SEE BLK 16
Reg Repro
LM
16. REMARKS: Changes to office symbols, when necessary, shall be made by the CO/ACO without revisions to the CDRL.
Distribution Statement D: (see paras 5.3 & 5.4 of instructions for distribution statement, warning, and destruction notices, and CUI marking requirements).
BLOCKS 10, 11, 12 & 13:
Contractor shall submit Work Management Plan (Design Review) NLT 30 business days after request from Government. Government will be allowed 20 business days, after receipt from contractor, to review for approval/disapproval/comments. Contractor shall submit revised Work Management Plan (Design Review) incorporating Government comments, if applicable, NLT 20 business days after receipt from Government.
BLOCK 14:
For unclassified deliverables, contractor shall submit Work Management Plan (Design Review) to TopVue https://icbm.topvue.com/topvue-icbm/ as per instructions (see paragraph 6.3.1). For classified deliverables, contractor shall submit Work Management Plan (Design Review) via instructions (see paragraph 6.3.2), and a letter of delivery to TopVue.
15. TOTAL
Form Approved 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.
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 .