6._EXHIBIT_B_-_DELIVERABLES_TABLE.xlsx
XLSX spreadsheet 27 KB Posted
- Attached to
- Pre-Solicitation RFP 25-4-002-1 SMARA-4
- Solicitation number
- 0000036842
- Issued by
- California
About this file
This document is an Excel-based Deliverables Table for a state government contract (Contract No. 25-4-002-1) involving the California Department of Corrections (DOC). The file outlines a comprehensive project lifecycle for what appears to be a technology implementation, specifically a system called SMARA-4, with detailed deliverables across four primary phases: Initiate Project, Discover/Design/Develop/Test/Implement, Maintenance and Operations, and Contract Closeout. The project timeline spans 12 months from contract start, with critical milestones including a kickoff meeting within 30 days, master project plan development within 90 days, design and implementation phases, user acceptance testing, go-live, and a 90-day acceptance period.
The deliverables are categorized as mandatory and include comprehensive requirements such as insurance documentation, staff training, confidentiality agreements, security controls, system security plans, testing procedures, data migration, knowledge transfer, training materials, reporting capabilities, disaster recovery planning, and ongoing maintenance and support. The contract includes specific technical requirements like developing a requirements traceability matrix, monthly operational reports, project documentation, and establishing a help desk/call center support function. Each deliverable is assigned a priority level and specific timing within the project lifecycle, with explicit expectations for contractor compliance and detailed documentation submission.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 7._EXHIBIT_C_-_COST_WORKBOOK.xlsx | XLSX spreadsheet | |
| 2._Pre-Solicitation_RFP_25-4-002-1_SMARA-4.pdf | ||
| 8._EXHIBIT_G_-_TO-BE-PROCESS_DIAGRAMS.zip | ZIP file | |
| 3._ATTACHMENT_12_-_BIDDER_QUALIFICATIONS_WORKBOOK.xlsx | XLSX spreadsheet | |
| 9._Exhibit_H_-_DELIVERABLES_ACCEPTANCE_DOCUMENT_TEMPLATE.pdf | ||
| 4._ATTACHMENT_14_-_KEY_STAFF_QUALIFICATIONS_WORKBOOK.xlsx | XLSX spreadsheet | |
| 10._Exhibit_I_-_DELIVERABLES_EXPECTATION_DOCUMENT_TEMPLATE.pdf | ||
| 1._Pre-solicitation_Instructions_SMARA4.docx | DOCX document | |
| 11._eVAQ-Manual_for_Vendors.pdf | ||
| 5._EXHIBIT_A_-_FUNCTIONAL_AND_NON-FUNCTIONAL_REQUIREMENTS.xlsx | XLSX spreadsheet |
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
1. Instructions Enter full name of Bidder in row #2 (Example: ABC Corporation).
| <enter company name> | |
| Exhibit B | DOC Contract No. 25-4-002-1 |
GENERAL INSTRUCTIONS
| Worksheet Names |
| 1. Instructions |
| 2. Deliverables |
Deliverables Workbook Instructions
| Column | Name | Definition |
| A | SOW section reference | Section in SOW that deliverable is defined |
| B | Deliverable Name | Deliverable name as defined in the SOW. |
| C | Priority | The priority of the deliverable requirement. |
| D | Milestone timing | The expected timeframe for completing the Deliverable, expressed either by a key milestone or days/months from a milestone date. |
| E | Contractor Agrees to provide the Deliverable | Yes/No. Bidder must indicate compliance and confirmation with each of the deliverables. |
The Bidder must complete and submit as part of its Proposal, Exhibit B: Deliverables Workbook. The Bidder must indicate compliance and confirmation with each of the deliverables by marking “Yes” or “No” in the column labeled “Contractor Agrees to provide the Deliverable Yes/No”. A blank or “NO” response will be deemed non-responsive and will be the basis for rejection of the Bidder’s proposal.
Tasks and deliverables are described in ATTACHMENT 1: APPENDIX A - STATEMENT OF WORK and summarized in tab "2. Deliverables".
Note: If any discrepancy is identified between the Deliverables Workbook and the Statement of Work, the Statement of Work will take precedence over the two.
The following provides a description of each column and the responsibility of the Bidder for completing the Deliverables Workbook:
The Bidder is reminded that in order to be considered responsive and responsible to the requirements, the Bidder must provide enough detail in Final Proposal in order for the State to evaluate the Bidder’s ability to meet the requirement. Refer to RFP Section 7: Evaluation for details on how the requirement will be scored as part of the overall evaluation.
2. Deliverables
| Exhibit B: Deliverables Table | ||||
| <enter company name> | ||||
| SOW section reference | Deliverable Name | Priority | Milestone timing | Contractor Agrees to Provide the Deliverable |
Yes/No
| INITIATE PROJECT | ||||
| 14.0 | Kickoff Meeting for project planning and coordination. | Mandatory | Within 30 days after contract start | |
| 32.0 | Insurance requirements - furnish appropriate insurance certificates to meet required insurance covered defined in Section 32 Insurance Requirements. | Mandatory | Within 30 days after contract start | |
| 9.0 | All contractor staff shall complete all standard DOC training. | Mandatory | Within 30 days after contract start | |
| 16.0 | All contractor personnel sign a DOC provided confidentiality statement. | Mandatory | Within 30 days after contract start | |
| DISCOVER, DESIGN, DEVELOP, TEST, IMPLEMENT | ||||
| 14.0 | Master Project Plan - plan outlining timelines for delivering system functionality and deliverables. Define key milestone dates such as Design start/end, Development start/end, UAT start/end, Training start/end, Go-Live. | Mandatory | within 90 days after contract start | |
| 14.0 | ||||
| 20.0 | Project Documents - Implementation Plan. Project Deployment Plan Narrative and Proposed Service Delivery Schedule. | Mandatory | within 90 days after contract start | |
| 14.0 | Design phase - design capability/functions defined in EXHIBIT A: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS WORKBOOK | Mandatory | Prior to Design complete milestone | |
| 14.0 | ||||
| 18.0 | Project Documents - Security Controls Report. Appropriate security controls in place and received approval from DOC ISO. | Mandatory | Prior to any DOC data being stored in the solution environment. Quarterly reviews thereafter. | |
| 14.0 | ||||
| 18.0 | Project Documents - System Security Plan. Plan detailing system security requirements. | Mandatory | Prior to any DOC data being stored in the solution environment | |
| 27.0 | System Testing and Acceptance Procedures - Develop test plan and submit to SMARA-4 PM for review and approval. | Mandatory | Prior to UAT start | |
| 14.0 | Validation - Each requirement configured according to design. Unit and system testing conducted. | Mandatory | Prior to UAT complete milestone | |
| 14.0 | Project Documents - Demo. Provide demo of user stories so that feedback can be provided early and often. | Mandatory | Prior to UAT complete milestone | |
| 16.0 | Data conversion and migration - assist in the conversion and validation into the new system. | Mandatory Optional | Prior to UAT complete milestone | |
| 14.0 | ||||
| 27.0 | Project Documents - Test Plan and Logs. | Mandatory | Prior to UAT complete milestone | |
| 14.0 | ||||
| 27.0 | Project Documents - Test Status Monthly Report | Mandatory | Prior to UAT complete milestone | |
| 14.0 | Knowledge transfer - DOC is provided with documentation and training materials | Mandatory | Prior to Go Live | |
| 14.0 | Training - detailed training package has been defined and delivered. | Mandatory | Prior to Go Live | |
| 14.0 | ||||
| 21.0 | Project Documents - SaaS Product Access | Mandatory | Prior to Go Live | |
| 14.0 | ||||
| 29.0 | Project Documents - Detailed Training Plan | Mandatory | Prior to Go Live | |
| 14.0 | Project Documents - Manuals and FAQ's. System manuals, SOP's, process flows, technical specs, design and functionality. | Mandatory | Prior to Go Live | |
| 14.0 | Project Documents - Requirements Traceability Matrix. | Mandatory | Prior to Go Live | |
| 14.0 | ||||
| 30.0 | Project Documents - Monthly Operations Report. Project data dashboard. | Mandatory | Prior to Go Live | |
| 14.0 | ||||
| 19.0 | Project Documents - Disaster Recovery Plan. Plan detailing disastery recovery plan and procedures. | Mandatory | Prior to Go Live | |
| 17.0 |
14.0 24.0
| 27.0 | Reporting - solution generated reporting requirements. Provide report deliverables defined in sections 14 Project (Contractor) Tasks and Deliverable Requirements, Section 34 Service Level Agreements (SLAs) and Section 27 System Testing and Acceptance Procuedures. | Mandatory | Prior to Go Live | |
| 14.0 | Go Live - SMARA-4 is promoted into production and successfully runa mongst the user community. | Mandatory | 12 months after contract start | |
| 27.0 | Acceptance Period - 90 day production validation for maintaining and supporting the released solution. | Mandatorhy | 3 months after Go Live | |
| MAINTENANCE AND OPERATIONS | ||||
| 30.0 | Maintenance and Operations - Maintaining all configurations, customizations/interfaces, backups, security, incident management, patches, upgrades to the solution while meeting defined Section 34 Service Level Agreements. | Mandatory | After Go Live | |
| 31.0 | Help Desk/Call Center - Provide Tier 2 technical support and service as defined in the Section 31 Help Desk/Call Center. | Mandatory | After Go Live | |
| 14.0 | Project Documents - Release notes. Description of changes, updates and resolved defects | Mandatory | as required | |
| 19.0 | Disaster Recovery during M&O- Review Disaster Recovery Plan Annually. Execute annual disaster recovery simulation/test and report outcome. | Mandatory | Annual | |
| CONTRACT CLOSEOUT (if applicable) | ||||
| 14.0 | ||||
| 28.0 | Project Documents - Transition Out Plan. Plan for transition to New Contractor or State. | Mandatory | 6 months before end of contract | |
| 28.0 | Transition out support | Mandatory | 90 days before end of contract | |
| 9.0 | Return all DOC property to DOC Contract Administrator | Mandatory | 2 weeks before end of contract |
&"Century Gothic,Regular"State of California Caltrans &"Century Gothic,Regular"Contract No. 65A1118
&"Century Gothic,Regular"Page &P of &N
File details come from the government source that posted it. Updated .