Appendix F - Deliverables Schedule Project Initiation Phase.docx
DOCX document 23 KB Posted
- Solicitation number
- 25DPP01188
- Issued by
- New Jersey
About this file
This document is a deliverables schedule for the New Jersey Department of Health's Women, Infants, and Children (WIC) System cloud migration and modernization project (Bid T2904). The schedule outlines comprehensive deliverables across six project phases: Project Initiation, Project Execution (Design, Development, and Integration Testing), Cloud Migration, User Acceptance Testing (UAT), Transition, and System Operations and Maintenance. During the Project Initiation Phase, the contractor must submit a kickoff meeting within 15 calendar days of contractor engagement start (CES), followed by the Project Work Plan, Contract Schedule, and Risk Management Plan within 45 calendar days. The Project Execution Phase requires the contractor to develop business requirement documents, functional and detailed design documents, interface control documents, system test plans and cases, and monthly and weekly status reporting, with all items subject to mutual agreement and approval by the State Contract Manager (SCM). The Cloud Migration Phase, with deliverables due within 90 calendar days of CES, includes cloud infrastructure, security, network, capacity, and disaster recovery plans; data migration plans; system architecture diagrams; and weekly and monthly status reporting, culminating in a Cloud Migration Validation Result at least three weeks before phase completion and a Cloud Migration Completion Certificate at least two weeks prior to phase end.
The UAT Phase requires the contractor to develop training plans, readiness certificates, release notes, and production implementation plans, with manuals and training materials transferred from the incumbent contractor and delivered 20-30 calendar days before UAT commencement. The Transition Phase deliverables, due within 45 calendar days of CES, include transition and staffing plans, with operations manuals and handoff certificates delivered 90 and 20 calendar days respectively before phase completion. The System Operations and Maintenance Phase requires ongoing monthly status reports, maintenance plans, daily end-of-day process reports, quarterly resource utilization reports, weekly operations meetings, and continuous system issue tracking, with transition planning for contract closeout beginning 300 calendar days before contract end and finalized 240 calendar days prior to expiration. The file does not contain pricing information, set-asides, incumbent vendor details, or funding amounts; these specifications are referenced in the broader bid solicitation T2904 for a five-year base contract with potential five-year extensions.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Appendix B - System Functions to be Preserved~1.docx | DOCX document | |
| T2904 Price Sheet 9.4.25.xlsx | XLSX spreadsheet | |
| T2904 Standard Procurement Forms.pdf | ||
| T2904 Revised Bid Solicitation 11.14.25~1.docx | DOCX document | |
| Appendix A - MIS_Features_and_Functions_Catalog.xlsx | XLSX spreadsheet | |
| Appendix D- NJWIC MIS Executive Summary DEC 2024.pdf | ||
| T2904 Bid Solicitation 9.4.25.docx | DOCX document | |
| T2904 Third Party Security Questionnaire.pdf | ||
| Appendix C- NJWIC MIS Executive Summary NOV 2024.pdf | ||
| T2904 Pre-Quote Conference 9.4.2025.pptx | PPTX presentation | |
| T2904 State Standard Terms and Conditions.pdf | ||
| Bid Amendment 2 11.14.25~2.docx | DOCX document | |
| T2904 Bid Amendment 1 11.7.25~1.docx | DOCX document | |
| Appendix G -Server Specifications.xlsx | XLSX spreadsheet | |
| Appendix E FNS-WIC Federal Procurement Clauses.pdf |
Show all 15
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
The following deliverables are scheduled for the project initiation phase.
| ID # |
| Deliverable Name |
| Due Date/ Frequency |
| 1. |
| Kickoff meeting |
| 15 Calendar Days after Contractor Engagement Start (CES) |
| To be scheduled. |
| 2. |
| Project Work Plan – Final |
| 45 Calendar Days after CES |
| To be created and maintained by new contractor |
| 3. |
| Contract Schedule – Final |
| 45 Calendar Days after CES |
| To be created and maintained by new contractor |
| 4. |
| Risk Management Plan |
| 45 Calendar Days after CES |
| To be created by new contractor |
| 5. |
| Risk Register |
| 45 Calendar Days after CES |
| To be created and maintained by new contractor |
| 6. |
| Project Issue Log |
| 45 Calendar Days after CES |
| To be created and maintained by new contractor |
The following deliverables are scheduled for the project execution phase, including Design, Development and Integration Testing.
| ID # |
| Deliverable Name |
| Due Date/ Frequency |
| 1. |
| Business Requirement Document (BRD) |
| Mutually agreed by the SCM and the Contractor, and approved by the SCM. |
| To be created by new contractor |
| 2. |
| Requirements Traceability Matrix (RTM) |
| Mutually agreed by the SCM and the Contractor, and approved by the SCM. |
| To be created and maintained by new contractor |
| 3. |
| Detailed Functional Design Document (DFDD) |
| Mutually agreed by the SCM and the Contractor, and approved by the SCM. |
| To be created by new contractor |
| 4. |
| Detailed Design Document (DDD) |
| Mutually agreed by the SCM and the Contractor, and approved by the SCM. |
| To be created by new contractor |
| 5. |
| Interface Control Document (ICD) |
| Mutually agreed by the SCM and the Contractor, and approved by the SCM. |
| To be created and maintained by new contractor |
| 6. |
| System Test Plan |
| Mutually agreed by the SCM and the Contractor, and approved by the SCM. |
| To be created by new contractor |
| 7. |
| System Test Case and Test Data |
| Mutually agreed by the SCM and the Contractor, and approved by the SCM. |
| To be created by new contractor |
| 8. |
| System Test Summary |
| Upon system test completion |
| To be created by new contractor |
| 9. |
| Monthly Project Status Report |
| Monthly |
| To be created by new contractor |
| 10. |
| Project Weekly Meeting |
| Weekly |
| To be created by new contractor |
| 11. |
| Project Weekly Status Report |
| Weekly |
| To be created by new contractor |
| 12. |
| Project Monthly Status Summary |
| Monthly |
| To be created by new contractor |
The following deliverables are scheduled for the cloud migration phase.
| ID # |
| Deliverable Name |
| Due Date/ Frequency |
| 1. |
| Cloud Infrastructure Plan – Final |
| 90 Calendar Days after CES |
| To be created by new contractor if not available at the time of contract award |
| 2. |
| Cloud Security Plan - Final |
| 90 Calendar Days after CES |
| To be created by new contractor if not available at the time of contract award |
| 3. |
| Cloud Network Plan – Final |
| 90 Calendar Days after CES |
| To be created by new contractor if not available at the time of contract award |
| 4. |
| Cloud Capacity Plan – Final |
| 90 Calendar Days after CES |
| To be created by new contractor if not available at the time of contract award |
| 5. |
| Cloud System Cutoff Plan – Final |
| 90 Calendar Days after CES |
| To be created by new contractor if not available at the time of contract award |
| 6. |
| Cloud Risk Management Plan – Final |
| 90 Calendar Days after CES |
| To be created by new contractor if not available at the time of contract award |
| 7. |
| Cloud Disaster Recovery Plan – Final |
| 90 Calendar Days after CES |
| To be created by new contractor if not available at the time of contract award |
| 8. |
| Data Migration Plan |
| 90 Calendar Days after CES |
| To be created by new contractor |
| 9. |
| System Logical Architecture Diagram |
| 90 Calendar Days after CES |
| To be transferred from incumbent contractor to new contractor and maintained by new contractor |
| 10. |
| System Physical Architecture Diagram |
| 90 Calendar Days after CES |
| To be transferred from incumbent contractor to new contractor and maintained by new contractor |
| 11. |
| Cloud Migration Weekly Status Report |
| Weekly |
| To be created by new contractor |
| 12. |
| Cloud Migration Monthly Status Summary |
| Monthly |
| To be created by new contractor |
| 13. |
| Cloud Migration Weekly Meeting |
| Weekly |
| To be created by new contractor |
| 14. |
| Cloud Platform Operations Manual/Helpdesk Guide |
| 210 Calendar Days after CES |
| To be created by new contractor if not available at the time of contract award |
| 15. |
| Cloud Migration Validation Result |
| At least three (3) weeks before the end of the cloud migration phase. |
| To be created by new contractor |
| 16. |
| Cloud Migration Completion Certificate |
| At least two (2) weeks before the end of the cloud migration phase. |
| To be created by new contractor |
The following deliverables are scheduled for the UAT phase.
| ID # |
| Deliverable Name |
| Due Date/ Frequency |
| 1. |
| Report Manual |
| 20 Calendar Days before the start of UAT. |
| To be transferred from incumbent contractor to new contractor and maintained by new contractor |
| 2. |
| User Manual |
| 20 Calendar Days before the start of UAT. |
| To be transferred from incumbent contractor to new contractor and maintained by new contractor |
| 3. |
| Training Plan |
| 30 Calendar Days before the start of UAT. |
| To be created by new contractor |
| 4. |
| UAT Readiness Certificate |
| At least 3 Calendar Days before the start of UAT release. |
| To be created by new contractor |
| 5. |
| Production Readiness Certificate |
| At least one (1) week before the start of production release. |
| To be created by new contractor |
| 6. |
| Release Notes (for UAT, and Production only) |
| One (1) week before the deployment of changes to UAT or production. |
| To be created by new contractor |
| 7. |
| Production Implementation Plan |
| 20 Calendar Days before the deployment of changes to production. |
| To be created by new contractor |
| 8. |
| Project Monthly Status Report |
| Monthly |
| To be created by new contractor |
| 9. |
| Project Weekly Meeting |
| Weekly |
| To be created by new contractor |
| 10. |
| Project Weekly Status Report |
| Weekly |
| To be created by new contractor |
| 11. |
| UAT Issue Log |
| Daily |
| To be created by new contractor |
The following deliverables are scheduled for the transition phase.
| ID # |
| Deliverable Name |
| Due Date/ Frequency |
| 1. |
| Transition Plan (Incoming) - Final |
| 45 Calendar Days after CES |
| To be created by new contractor |
| 2. |
| Staffing Plan – Final |
| 45 Calendar Days after CES |
| To be created by new contractor |
| 3. |
| Business Continuity Plan – Final |
| 45 Calendar Days after CES |
| To be transferred from incumbent contractor to new contractor and maintained by new contractor |
| 4. |
| Operations Manual/ Helpdesk Guide |
| At least 90 Calendar Days before the end of the transition phase. |
| To be transferred from incumbent contractor to new contractor and maintained by new contractor |
| 5. |
| System Handoff Certificate |
| At least 20 Calendar Days before the end of the transition phase. |
| To be created by new contractor |
| 6. |
| Monthly System Operations Status Report |
| Monthly |
| To be created by new contractor |
The following deliverables are scheduled for the system operations and maintenance phase.
| ID # |
| Deliverable Name |
| Due Date/ Frequency |
| 1. |
| Monthly System Operations Status Report |
| Monthly |
| To be created by new contractor |
| 2. |
| Monthly Maintenance Plan |
| Monthly |
| To be created by new contractor |
| 3. |
| End-of-Day (EOD) Processes Report |
| Daily |
| To be created by new contractor |
| 4. |
| Quarterly Resource Utilization Report |
| Quarterly |
| To be created by new contractor |
| 5. |
| Weekly Operations Meeting |
| Weekly |
| To be created by new contractor |
| 6. |
| System Issue Tracker |
| Ongoing |
| To be created and maintained by new contractor |
| 7. |
| Transition Plan (Outgoing) – Draft |
| 300 Calendar Days before the Contract ends |
| To be created by new contractor |
| 8. |
| Transition Plan (Outgoing) – Final |
| 240 Calendar Days before the Contract ends. |
| To be created by new contractor |
File details come from the government source that posted it. Updated .