Attch_0019_ACWS_CDRL_List_Delivery_Dates_2016_05_06.xlsx
XLSX spreadsheet 17 KB Posted
- Attached to
- IT AND TELECOM- OTHER IT AND TELECOMMUNICATIONS
- Solicitation number
- W52P1J16R0058
About this file
Attachment 0019 ACWS CDRL LIST DELIVERY DATES
View the file
Other files
Show 40 more
Latest 50 of 97 listed here. See the rest on GovTribe.
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
ACWS CDRL List
| CDRL No. | Title | SOO Paragraph | Frequency | |
| Block 10 | 1st Submit |
(days = calendar days unless specified) Block 12 Subsequent Submittal (days = calendar days unless specified) Block 13 CLIN No. FAR 52.227-21 / DFAR 252.227-7030 Applies?
(Task Order Success Deliverable)
| Exhibit A - Acquisition / Program Management | ||||||
| A001 | Program Management Plan (PMP) | 6.1 | AsReq | Sixty (60) DAC | Thirty (30) days after PDR, following subsequent submissions as required to document changes. | 001 |
| A002 | Contractor Work Breakdown Structure (CWBS) | 6.1 | Annly | Thirty (30) days prior to SFR | Thirty (30) days prior to each CDR | 001 |
| A003 | Integrated Master Schedule (IMS) | 6.1 | AsReq | Thirty (30) Days prior to PDR | Thirty (30) days prior to each CDR for each build | 001 |
| A004 | Program Status Reports | 6.1 | MTHLY/ ASREQ | Monthly Status Reports due NLT fifth (5th) working day of the subsequent month. |
Presentation Materials due two (2) Government working days prior to the scheduled review.
Meeting Minutes due NLT two (2) Government working days post meeting. Monthly Status Reports due NLT fifth (5th) working day of the subsequent month.
Presentation Materials due two (2) Government working days prior to the scheduled review.
| Meeting Minutes due NLT two (2) Government working days post meeting. | 001 | |||||||
| A005 | Risk Management Plan (RMP) | 6.1 | AsReq | Forty (40) DAC | As required to document changes | 001 | ||
| A006 | Risk Management Status Report | 6.1 | MTHLY | Forty (40) DAC | NLT ten (10) Government working days after the end of the month reported on. | 001 | ||
| A007 | Quality Assurance Program Plan (QAPP) | 6.1 | AsReq | Sixty (60) DAC | Revisions may be periodically required for changes in the Quality processes, methods or tools. | 001 | ||
| A008 | Configuration Management Plan (CMP) | 6.1 | AsReq | Thirty (30) days prior to SFR | Thirty (30) days prior to PDR; then 30 days prior to each CDR | 001 | ||
| A009 | Reserved for Future Use | |||||||
| A010 | Reserved for Future Use | |||||||
| A011 | Contract Funds Status Report (CFSR) | 6.1 | MTHLY | NLT ten (10) Government working days after the end of the month reported on (4th month). | NLT ten (10) Government working days after the end of the month reported on. | 001 | ||
| A012 | Phase-Out Transition Plan | 6.1 | AsReq | Thirty (30)days prior to the end of the period of performance of the Risk Reduction phase | Thirty (30) days prior to end of follow-on Build Task Orders | 010 | ||
| A013 | Cost Data Summary Report (CSDR) | |||||||
| (DD Form 1921) | 6.1 | AsReq | Ten (10) days before the end of Task Order 0001 PoP | Ten (10) days before the end of each task | ||||
| order PoP / date of final product acceptance, after 95% or more of total contract costs have been incurred. | 001 | |||||||
| A014 | Software Resource Data Report (SRDR) | 6.1 | AsReq | Thirty (30) days prior to each CDR | Within sixty (60) days after each build task order LDD | 001 | ||
| A015 | Functional Cost Hour Report | |||||||
| (DD Form 1921-1) | 6.1 | Annly | Sixty (60) days following as of date | Sixty (60) days following final product acceptance, after 95% or more of total contract costs incurred | 001 | |||
| A016 | Contractor Business Data Report | |||||||
| (DD Form 1921-3) | 6.1 | Annly | Within sixty (60) days end of contractor FY | Within sixty (60) days end of contractor FY | 001 | |||
| Exhibit B - Systems Engineering | ||||||||
| B001 | Systems Engineering Management Plan (SEMP) | 6.2 | AsReq | Ninety (90) DAC | Thirty (30) days prior to SFR, PDR and each Build Task Order CDR; thirty (30) days after any future SEP change is approved | 002 | ||
| B002 | System Performance Reports | 6.2 | AsReq | Ninety (90) days prior to PDR | Thirty (30) days prior to each CDR, and AsReq thereafter | 002 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B003 | Hosting Analysis Reports | 6.2 | Mnthly | Thirty (30) days after the stand up of each hosting environment | NLT the tenth (10th) day after the following month | 002 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B004 | Operating Environment Requirements and Design | 6.2 | AsReq | Ninety (90) days prior to PDR | Thirty (30) days prior to each CDR, and as changes are required to meet system requirements | 002 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B005 | Technical Review Package | 6.2 | Ea Tech Rvw | Thirty (30) days prior to each scheduled formal Technical Review | Thirty (30) days prior to each build formal Technical Review | 002 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B006 | Fit/Gap Report | 6.3.1 | AsReq | Work in process drafts shall be provided bi-weekly during Global Analysis and Requirements Analysis during the Risk Reduction phase. First submission is due thirty (30) days prior to SFR. | Subsequent submission is due thirty (30) days prior to PDR. Updates will be due thirty (30) days prior to each subsequent Build Task Order CDRs. Work-in-process drafts delivered upon request. | 003 | ||
| B007 | Business Process Design (BPD) | 6.3.1 | AsReq | Thirty (30) days prior to PDR. Work-in-process drafts delivered upon request. | BPDs will be maintained throughout all Task Orders. Sixty (60) days prior to each CDR. Work-in-process drafts delivered monthly during each Build Task Order. | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B008 | Requirements Traceability Matrix (RTM) | 6.3.1 | AsReq | Forty-five (45) days prior to SFR | Forty-five (45) days prior to PDR, then thirty (30) days prior to the end of the Risk Reduction phase. The RTM shall be maintained throughout all Task Orders. Subsequent submissions will be forty-five (45) days prior to each CDR or AsReq based on approved changes. Work-in-process versions shall be made available to the government upon request. | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B009 | System Provisioning Document | 6.3.1 | AsReq | Ninety (90) days prior to PDR | Thirty (30) days prior to each CDR. Revisions to the updates ten (10) days prior to the release of each build | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B010 | Interface Control Document (ICD) | 6.3.1 | AsReq | Thirty (30) days prior to PDR | NLT fifteen (15) days prior to the close of the Risk Reduction phase. thirty (30) days prior to each CDR with final NLT fiftenn (15) days prior to close of each Build Task Order. | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B011 | Interface Requirements Specification (IRS) | 6.3.1 | AsReq | Thirty (30) days prior to PDR | Thirty (30) days prior to each CDR | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B012 | Architecture Viewpoints & Plan | 6.3.1 | AsReq | a. The Architecture Development Plan shall be delivered to the government NLT sisty (60) DAC award. |
b. DoDAF architecture viewpoints as stated in the PWS shall be due in time to support acquisition milestones and solution development efforts in accordance with the Integrated Master Schedule (IMS). The contractor shall make available work-in-process versions of all viewpoints in development on a monthly basis. Viewpoints and any related work products shall be delivered NLT thirty (30) days prior to any technical reviews.
c. The PMO will have ten (10) Government working days after receiving DoDAF Viewpoints and Architecture Development Plan to review and comment.
d. Revise and submit the updated viewpoints and/or related work products for PMO approval ten (10) Government working days after receiving comments. All subsequent submissions shall conform to the approved format(s). a. Updates to the Architecture Development Plan shall be delivered to the Government sixty (60) days after the start of each subsequent Task Order.
b. DoDAF architecture viewpoints as stated in the PWS shall be maintained throughout the course of all Task Orders. Updates to viewpoints and related work products shall be due in time to support acquisition milestones and solution development efforts in accordance with the Integrated Master Schedule (IMS) across all Task Orders. The contractor shall make available work-in-process versions of all viewpoints in development on a monthly basis. Delivery of updated versions of viewpoints and related work products shall be delivered NLT thirty (30) days prior to any technical reviews.
c. The PMO will have ten (10) Government working days after receiving DoDAF Viewpoints and Architecture Development Plan to review and comment.
| d. Revise and submit the updated viewpoints and/or related work products for PMO approval ten (10) Government working days after receiving comments. All subsequent submissions shall conform to the approved format(s). | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | ||||||
| B013 | Software Requirements Specification (SRS) | 6.3.1 | AsReq | Thirty (30) days prior to PDR | Thirty (30) days prior to each CDR | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B014 | Build Plan | 6.3.1 | AsReq | Thirty (30) days prior to SFR | Thirty (30) days prior to PDR. Updates shall be due no later than thirty (30) days after subsequent Build Task Order award | 003 | ||
| B015 | Software Design Description (SDD) | 6.3.1 | AsReq | SDD through section 4 (architecture) delivered thirty (30) days prior to PDR | Thirty (30) days prior to each CDR | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B016 | Interface Design Description (IDD) | 6.3.1 | AsReq | Thirty (30) days prior to PDR | Thirty (30) days prior to each CDR | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B017 | Database Design Descriptioin (DBDD) | 6.3.1 | AsReq | Thirty (30) days prior to PDR | Thirty (30) days prior to each CDR | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B018 | Human Engineering Design Approach Document | 6.3.1 | ONE/R | Ninety (90) DAC | N/A | 003 | ||
| B019 | Computer Software Baseline | 6.3.2 | AsReq | Ninety (90) DAC | Thirty (30) days prior to subsequent Task Order build release | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B020 | Configuration Status Accounting Information | 6.3.2 | AsReq | Beginning of Risk Reduction phase, concurrent with initial installation of OOTB solution | NLT fifteen (15) days prior to the close of the Risk Reduction phase. Monthly delivery during each Build Task Order beginning on the tenth (10th) calendar day as of the last calendar day of the previous month. | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B021 | Software Version Description (SVD) | 6.3.2 | AsReq | Thirty (30) days prior to the release of the initial Build | Thirty (30) days prior to the release of each subsequent Build | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B022 | Configuration Audit Summary Report (FCA and PCA) | 6.3.2 | AsReq | Delivery of Functional Configuration Audit (FCA) Report NLT ten (10) days after completion of FCA. | ||||
| Delivery of Physical Configuration Audit (PCA) Report NLT ten (10) days after completion of PCA. | NLT ten (10) days after completion of subsequent FCAs and PCAs | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |||||
| B023 | Risk Management Framework (RMF) Package | 6.3.3 | AsReq | Security Plan: sixty (60) DAC | Subsequent RMF Package deliveries to be negotiated after Contract Award | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B024 | Program Protection Implementation Plan (PPIP) | 6.3.3 | AsReq | Sixty (60) DAC | Thirty (30) days prior to PDR and, for each Build Task Order, delivered no later than thirty (30) days after each formal Technical Review. | 003 | ||
| B025 | Critical Functional Analysis | 6.3.3 | AsReq | Thirty (30) days prior to SRR/SFR | Thirty (30) days prior PDR, 30 days prior to each CDR, and 30 days after each Build Task Order DT | 003 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| B026 | Studies, Analyses, Assessments, and Improvements Report | 6.11 | AsReq | Three-hunderd (300) DAC | AsReq | 011 | ||
| Exhibit C - Test and Evaluation | ||||||||
| C001 | Requirements Testability Analysis Report | 6.4 | AsReq | Forty-five (45) days prior to SFR | Forty-five (45) days prior to PDR, then thirty (30) days prior to the end of the Risk Reduction phase. The Requirements Testability Analysis Report shall be maintained throughout all Task Orders. forty-five (45) days prior to each CDR or AsReq based on approved changes. Work-in-process versions shall be made available to the government upon request. | 004 | ||
| C002 | Software Test Descriptions (STD) | 6.4 | AsReq | Ninety (90) days before TEMP update for the first Build Task Order | Ninety (90) days before each TEMP update in subsequent Build Task Orders (if necessary) | 004 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| C003 | Software Test Report | 6.4 | AsReq | Fifteen (15) days after completion of each Software Test Event(s) | Fiftenn (15) days after completion of subsequent Software Test Events | 004 | ||
| C004 | Coordinated Test Plan | 6.4 | AsReq | Thirty (30) days prior to SFR | Ninety (90) days before each TEMP update in subsequent Build Task Orders (if necessary) | 004 | ||
| C005 | Software Test Plan (STP) | 6.4 | AsReq | Ninety (90) DAC | Ninety (90) days before each TEMP update in subsequent Build Task Orders (if necessary) | 004 | ||
| C006 | Operational Availability Plan | 6.4 | AsReq | Thirty (30) days prior to SFR | Ninety (90) days before each TEMP update in subsequent Build Task Orders (if necessary) | 004 | ||
| Exhibit D - Operations and Sustainment | ||||||||
| D001 | Training Management Plan | 6.5 | AsReq | One-hundred-eighty (180) DAC | Thirty (30) days prior to CDR for each Task Order Build | 005 | ||
| D002 | Training Materials | 6.5 | AsReq | Deliver existing (commercial) Training Materials for COTS no later than 60 DAC | Deliver ACWS (tailored) Training Materials thirty (30) days prior to the commencement of Limited User Test training and Deployment training for each Task Order Build. Deliver ACWS (tailored) Training Materials thirty (30) days prior to the commencement of Deployment Training for each Task Order Build. | 005 | FAR 52.227-21 / DFAR 252.227-7030 (Yes) | |
| D003 | Deployment Plan | 6.6 | AsReq | Ninety (90) DAC | Two-hundred-seventy (270) days prior to commencement of Training/Deployment activities for subsequent Build | 005 | ||
| D004 | Change Management Plan | 6.7 | AsReq | Ninety (90) DAC | Thirty (30) days prior to end of RR. Subsequent submissions as required based on additional capabilities provided during each build. | 005 | ||
| D005 | Product Support Plan | 6.8 | Annly | One-hundre-twenty (120) DAC | One (1) year after first submission | 005 |
&"-,Bold"&18ACWS Contract Data Requirements List (CDRL) See: DD Form 1423-1 &"-,Bold"RFP# W52P1J-16-R-0058
ATTACHMENT 0019
&P of &N
File details come from the government source that posted it. Updated .