Exhibit A - MDA Mandatory CDRLs.docx
DOCX document 2 MB Posted
- Attached to
- MDA IT Operations & Engineering Solutions (MIOES) - CANCELED Federal contract opportunity
- Solicitation number
- HQ0857-MIOES-ZA
- Issued by
- DOD Missile Defense Agency
View the file
Other files for this federal contract opportunity
Show all 50
MDA IT Operations & Engineering Solutions (MIOES) - CANCELED has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
H95001-15-R-0001 Exhibit A Exhibit A – IRES Contract Data Requirements List (CDRL), MDA Mandatory CDRLs The Contract Data Requirements List (CDRLs) is comprehensive but not exhaustive; the CDRLs identified on this list may be ordered under individual task orders without review / approval of the MDA/DAP.
CDRLs not on this list may be determined necessary; a DD Form 1423 for these CDRLs, if deemed necessary, will be developed / processed through the MDA/DAP CDRL Approval Process.
MDA MANDATORY CDRLS (3 June 2015)
| CDRL # |
| DID Number |
| DID Title |
| Subtitle |
| Applicability |
| A001 |
| DI-FNCL-81565C |
| Cost Data Summary Report DD Form 1921 |
| [Insert Task Order #]: Cost Data Summary Report DD Form 1921 |
| Mandatory on task orders above $50M, or between $20M & $50M and is a high-risk or has high-technical-interest based on the discretion of the PM |
| A002 |
| DI-FNCL-81566C |
| Functional Cost-Hour Report DD Form 1921-1 |
| [Insert Task Order #]: Functional Cost-Hour Report DD Form 1921-1 |
| Mandatory on task orders above $50M, or between $20M & $50M and is a high-risk or has high-technical-interest based on the discretion of the PM |
| A003 |
| DI-FNCL-81567C |
| Progress Curve Report DD Form 1921-2 |
| [Insert Task Order #]: Progress Curve Report (DD Form 1921-2) |
| Mandatory on task orders above $50M, or between $20M & $50M and is a high-risk or has high-technical-interest based on the discretion of the PM |
| A004 |
| DI-FNCL-81765B |
| Contractor Business Data Report DD Form 1921-3 |
| [Insert Task Order #]: Contractor Cost Data Reporting (CCDR) |
| Mandatory on task orders above $50M, or between $20M & $50M and is a high-risk or has high-technical-interest based on the discretion of the PM |
| A005 |
| DI-FNCL-81831 |
| Contractor Sustainment Report DD Form 1921-4 |
| [Insert Task Order #]: Contractor Sustainment Report DD Form 1921-4 |
| Mandatory on task orders above $50M, or between $20M & $50M and is a high-risk or has high-technical-interest based on the discretion of the PM |
| A006 |
| DI-MGMT-80441/T |
| Government Property Physical Inventory Count or Custodial Balance Report |
| [Insert Task Order #]: Initial Government Property Inventory Report |
| Mandatory on all task orders where GFP is provided |
| A007 |
| DI-MGMT-80441 |
| Government Property Physical Inventory count or Custodial Balance Report |
| [Insert Task Order #]: Physical Inventory Plan/Schedule and Reports for GFP; Final |
| Mandatory on all task orders where GFP is provided |
| A008 |
| DI-MGMT-81334D |
| Contract Work Breakdown Structure (CBWS) |
| CBWS |
| Mandatory on task orders above $50M, or between $20M & $50M and is a high-risk or has high-technical-interest based on the discretion of the PM |
| A009 |
| DI-MGMT-81468 |
| Contract Funds Status Report (CFSR) |
| [Insert Task Order #]: Contract Funds Status Report (CFSR) |
| Applicable to contracts over 6 months in duration. No specific application thresholds are established, but application to contracts of less than $1,000,000 (constant fiscal year dollars) should be evaluated carefully to ensure only the minimum info necessary for effective management control is required. Not applicable for FFP contracts (as defined in FAR 16.202) unless unusual circumstances require specific funding visibility. |
| A010 |
| DI-MGMT-81739B |
| Software Resources Data Report (SRDR) And Data Dictionary |
| SRDR Initial Report: [Insert Software Title] |
| Required when projected software effort at task order completion is greater than $20M |
| A011 |
| DI-MGMT-81740A |
| Software Resources Data Report (SRDR) And Data Dictionary |
| SRDR Final Report: [Insert Software Title] |
| Required when projected software effort at task order completion is greater than $20M |
| A012 |
| DI-MGMT-81861A/T |
| Integrated Program Management Report (IPMR) |
| [Insert Task Order #]: Integrated Program Management Report (IPMR) - Full EVM |
| EVM Reporting Threshold: Mandatory on all Cost or Incentive Contractor => $20M. Mandatory for each Task Order on an IDIQ Contract if the TO will be => $20M. A partial requirement may exist for other contracts. If in doubt, refer to the DOV Data Manager. |
| A013 |
| DI-MGMT-81861A/T |
| Integrated Program Management Report (IPMR) |
| [Insert Task Order #]: Integrated Program Management Report (IPMR) - Reduced EVM |
| Required for all task orders in when CDRL A012 is not ordered. |
| A014 |
| DI-MISC-80508B/T |
| Technical Report–Study/Services |
| SB Subcontractor Report, IRES Contract |
| Mandatory, SE/PI Task Order |
| A015 |
| DI-MISC-80508B |
| Technical Report–Study/Services |
| [Insert Company Name]: Cybersecurity Controls Statement of Compliance |
| Mandatory, SE/PI Task Order and all subcontracts. |
| A016 |
| DI-MISC-80508B |
| Technical Report–Study/Services |
| [Insert Company Name], [Insert Report ID]: Cyber Incident or Compromise Report |
| Mandatory, SE/PI Task Order and all subcontracts. |
EXPLANATION OF NUMBERED BLOCKS ON THE DD FORM 1423-1
(Unnumbered blocks are for Government internal office use) Block 1: Data Item Number:
CDRL sequence number.
Block 2: Title of Data Item:
The title listed on an authorized DD Form 1664, Data Item Description.
Block 3: Subtitle:
Amplification of DID title, if it requires more descriptive identification. Also used to identify the specific title of a deliverable document.
Block 4: Authority:
Reflects the exact DID identification number. A trailing, upper case alpha character indicates a revision. If project-specific modification is required to limit either the scope or clarify usage of a DID, a “/t” will follow the number to indicate tailoring of the DID has been made. Any DID tailoring is explained in Block 16.
Block 5: Contract Reference:
Reference(s) in a contract exhibit (e.g. SOW, SOO, Specification) which generates the requirement for the data item.
Block 6: Requiring Office:
This is the office that called for or ordered the data and it will advise the contracting officer on the currency and adequacy of the Contractor’s data submission.
Block 7: DD Form 250 Required:
The activity to perform the inspection and or acceptance. Only the code “LT” (Letter of Transmittal) is used in this CDRL, indicating that the DD Form 250 is not required for delivery of data items.
Block 8: Approval Code:
The following codes are applicable to this CDRL:
| A | Used when the data is critical (such as a specification) or of a technical nature, or when the Contractor requires Government concurrence on the document in order to implement a plan or proceed to the next event (for example, test plans must be approved prior to testing). |
| (BLANK) | Acceptance/Approval is not required. |
| Block 9: | Distribution Statement Required: |
The following distribution codes are used here:
| A | Approved for public release; distribution is unlimited. |
| B | Distribution authorized to US Government agencies only. |
| C | Distribution authorized to US Government agencies and their contractors. |
| D | Distribution authorized to Department of Defense and US DoD contractors only. |
| E | Distribution authorized to DoD components only. |
| F | Further dissemination only as directed by controlling DoD office or higher DoD authority. |
| X | Distribution authorized to US Government agencies and private individuals or enterprises authorized to obtain export-controlled technical data IAW regulations implementing 10 U.S.C. 130. |
| Block 10: | Frequency: |
The following codes are used in this block:
| Code |
| Description |
| DAILY |
| Daily |
| WEKLY |
| Weekly |
| BI-WE |
| Each 2 Weeks |
| MTHLY |
| Monthly |
| BI-MO |
| Each 2 Months |
| QRTLY |
| Quarterly |
| ANNLY |
| Annually |
| SEMIA |
| Each 6 Months |
| ASGEN |
| As Generated |
| ONE/R |
| One Time with Revisions |
| R/ASR* |
| Revisions as Required |
| ASREQ* |
| As Required |
| DFDEL |
| Deferred Delivery |
| ONE/P |
| One Time Preliminary Draft |
| XTIME |
| Specific Number of Submittals (substitute a digit for the “X”) |
| SEE 16* |
| Refer to Block 16 for an explanation |
Block 11: As of Date:
If the data will be submitted only once, the “as of” date (or cut-off date) is entered as follows: Day/Month/Year. If the data is of a recurring type, the number of days prior to the end of the report period is entered; for example, “15” places the “as of” date for this report at 15 days before the end of each month, quarter, or year, depending upon the frequency established in Block 10: “0” places the “as of” date at the end of each month, quarter, etc. (Block 16 is used for further explanation.)
Block 12: Date of First Submission:
The date of submission is entered as follows: Day/Month/Year. If data is constrained by a specific event or milestone, this constraint is entered. If contract start date is not known, the number of days after contract start is entered (Example: 30 DAC). If the date is not known or requires further clarification, Block 16 is used.
Block 13: Date of Subsequent Submission:
If data is submitted more than once, the dates of subsequent submissions are entered. If data is constrained by a specific event or milestone, the constraint is entered. (Block 16 is used for further explanation.)
*When used in Block 10, 11, 12 or 13, further explanation of the requirement is entered in Block 16 to provide the Contractor with the guidance necessary to adequately scope and schedule delivery of the data item.
Block 14: Distribution:
Entered here, or in Block 16, are the addresses and the number of copies to be received by each office. Office symbols and command initials are used. The media to be used for distribution to each office is explained in Block 16.
Block 15: Total:
The total number of copies for one delivery; this number should be the sum of all the copies specified in Block 14.
Block 16: Remarks.
Used to explain:
· Tailored features of the DID;
· Items 1 through 15;
· Any resubmittal schedule or actions involved in updating data submitted for Government acceptance/approval.
Block 17:
Not used in this contract.
Block 18:
Not used in this contract.
CONTRACT DATA REQUIREMENTS LIST (CDRL) NOTES
1. The DD Forms 1423, Contract Data Requirements List (CDRL), The DD Forms 1423, Contract Data Requirements List (CDRL), are cross-referenced in Block 5 to the associated SOO tasks under which the data is generated. Format, preparation and submission instructions for each data item are contained in the individual DD Form 1423 and the associated DD Form 1664, Data Item Description (DID), referenced in the CDRL. Any comments, explanations, clarification or limitations with respect to an individual DD Form 1664 will appear in Block 16 of the DD Form 1423. In any case, the information in Block 16 of the DD Form 1423 shall be considered part of the data item preparation instructions.
2. In the context of this CDRL, a “/t” following the DID number in Block 4 of the DD Form 1423 In the context of this CDRL, a “/t” following the DID number in Block 4 of the DD Form 1423 is to be interpreted as indicating deviations from, or clarification of, the DID, and an explanation of the deviation or clarification is given in Block 16. When a “/t” is not present, the data shall comply fully with the DID requirements for both format and content. Relief from format requirements of the DID—such as through the statement, “Contractor format is acceptable”—does not relieve the contractor of the responsibility to meet the content requirements of the DID.
3. The DD Form 250 shall not be used for CDRL deliveries.
The DD Form 250 shall not be used for CDRL deliveries. All submissions shall be by letter of transmittal. (“LT” code in Block 7 of the DD Form 1423.)
| a. | Transmittal letters shall be addressed to the contracting office for this contract but all copies of data items for the IRES shall be delivered to the IRES Data Management Office. |
| b. | When data is to be delivered to more than one office in an organization outside the MDA, the data may be packaged or sent together. When data for more than one office is packaged or sent together, the data for each office shall be separated and suitably identified to facilitate correct distribution. |
| c. | Unless called for on the DD Form 1423, data items shall initially be submitted only to the MDA; complete distribution, as indicated on the DD Form 1423, shall be made only after receipt of Government acceptance/approval without comment, or expiration, without comment, of the Government’s review cycle. |
| d. | The point of delivery for all CDRL deliverable products (up to and including SECRET classification) is the MDA E-CaRT system. The Contractor shall deliver all such products by saving and profiling them to E-CaRT, with the appropriate notification of delivery letter transmitted electronically to the Government’s Data Management Office. |
| 4. | Government acceptance/approval |
When the DD Form 1423, Block 8, indicates Government acceptance/approval is required, it shall be construed to mean acceptance/approval by the KO or their designated representative. Unless a different time period for acceptance/approval is specified elsewhere in this contract, the Government will have up to 30 days to notify the Contractor concerning the acceptance/approval/rejection/disapproval of a data item. If the Contractor does not receive notice of Government acceptance/approval/rejection/disapproval within the 30-day period, the data item shall be considered accepted/approved as written. The Government reserves the right to accept/approve, reject/disapprove, or comment on any data item, regardless of the acceptance/approval code indicated on the DD Form 1423.
| a. | After receipt of government response with comments, the Contractor shall make corrections as directed and resubmit the corrected data item for Government acceptance/approval. Upon resubmission, a new acceptance/approval period will commence. If there are no additional Government comments provided, the data item shall be considered accepted/approved as written. If other Government direction is provided, the Contractor shall follow that direction. |
| b. | When rejecting/disapproving a data item, the Government will stipulate the reasons for rejection/disapproval and may grant additional time without derogating any rights the Government may have in any other clause of this contract. For periodic submissions, comments/changes shall be incorporated in the next regular submittal unless otherwise stated by the Government. Upon resubmission, a new acceptance/approval period will commence. |
| 5. | Cover and title page |
Unless otherwise specified in the CDRL, data items shall have a cover and title page (Contractor’s design) which clearly identify the data item. The title page shall contain the:
· Contract Number
· Contractor’s Name/Cage Code
· DD Form 1664 Number
· Data Item Number
· Data Item Title or Subtitle
· Signature of Contractor’s Release Authority
| a. | Concurrent with an acceptance/approval letter, the Government may direct the Contractor to remove its identifying markings from a data item and reissue a final version with a cover, title page and identifying markings of Government design. In these cases, the Contractor shall distribute and archive only this final Government version. |
| b. | All data items produced as standard text documents shall be printed (or, in the case of soft copy delivery, formatted for printing) head-to-head, utilizing both sides of common white paper. Exceptions are allowed for title pages, foldout pages and color reproductions. Heavy stock and colored or glossy paper shall not be used unless specifically requested by the Government (as, for example, in a brochure). |
| c. | Unless otherwise specified by the Government, or required by a DID, all data items shall be prepared using standard MDA desktop productivity tools (latest versions). Where a previous submittal has been made by the Contractor, and accepted/approved by the Government, the Contractor shall, to the maximum extent possible, retain the format and styles used in making revisions or resubmittals of follow-on or like data items. |
| 6. | If no changes have occurred since the last submission |
Requirements for data items, where no changes have occurred since the date of last submission, shall be satisfied by a letter from the Contractor stating, “no changes have occurred since the last submission.” In such cases, the Contractor shall identify the title and document number of data item in question, the reporting period, and the date of the prior data transmittal.
7. Submission date / times Data shall be submitted for receipt by the Government not-later-than 0800 hours (MST/MDT) on the morning after the scheduled delivery date specified in the DD Form 1423, except that due dates falling on non-working days (Saturday, Sunday, and Government and Contractor official holidays) shall be construed to mean the next regular working day following such non-working days. All due dates (e.g., 30 DAC) are calendar counted.
8. Data Management The Contractor shall maintain a single authority for Data Management to insure compliance with CDRL requirements.
May 10, 2016 Page 4 Exhibit A 19May2015.zip image1.emf
File details come from the government source that posted it. Updated .