5._EXHIBIT_B_-_DELIVERABLES_TABLE.xlsx

XLSX spreadsheet 27 KB Posted

Attached to
RFP 25-4-002-1 DOC SMARA-4 Project
Solicitation number
0000037279
Issued by
California

About this file

This is an Exhibit B Deliverables Table for RFP 25-4-002-1 SMARA-4 Project, submitted to the California Department of Conservation by the Department of Technology's Office of Statewide Technology Procurement. The document outlines mandatory and project deliverables organized into four phases: Initiate Project, Discover/Design/Develop/Test/Implement, Maintenance and Operations, and Contract Closeout. Initial project phase requirements include a kickoff meeting, insurance certificates, contractor staff training, and confidentiality statements, all due within 30 days of contract start. The implementation phase encompasses a Master Project Plan due within 90 days, followed by design, security controls, system testing, validation, user demonstrations, data conversion, knowledge transfer, training delivery, and documentation of manuals, disaster recovery plans, and requirements traceability matrices, with completion required prior to Go Live scheduled 12 months after contract start. The maintenance and operations phase requires ongoing system maintenance, Help Desk/Tier 2 support, and annual disaster recovery testing. The contract closeout phase includes transition planning and support due 6 months and 90 days before contract end, respectively. The final proposal submission deadline is January 20, 2026 at 10:00 AM PST, with OSTP eVAQ approval required as a non-negotiable condition. Bidders must indicate "Yes" or "No" compliance for each deliverable in the workbook, with blank or negative responses resulting in proposal rejection.

The document does not contain pricing information, set-asides, incumbent details, or funding sources, as it is a deliverables compliance checklist rather than a financial or procurement summary document. Bidders are required to provide detailed responses in their final proposals demonstrating their ability to meet each requirement, with evaluation criteria detailed in RFP Section 7.

View the file

Other files

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 BDOC Contract No. 25-4-002-1

GENERAL INSTRUCTIONS

Worksheet Names
1. Instructions
2. Deliverables

Deliverables Workbook Instructions

ColumnNameDefinition
ASOW section referenceSection in SOW that deliverable is defined
BDeliverable NameDeliverable name as defined in the SOW.
CPriorityThe priority of the deliverable requirement.
DMilestone timingThe expected timeframe for completing the Deliverable, expressed either by a key milestone or days/months from a milestone date.
EContractor Agrees to provide the DeliverableYes/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 referenceDeliverable NamePriorityMilestone timingContractor Agrees to Provide the Deliverable

Yes/No

INITIATE PROJECT
14.0Kickoff Meeting for project planning and coordination.MandatoryWithin 30 days after contract start
32.0Insurance requirements - furnish appropriate insurance certificates to meet required insurance covered defined in Section 32 Insurance Requirements.MandatoryWithin 30 days after contract start
9.0All contractor staff shall complete all standard DOC training.MandatoryWithin 30 days after contract start
16.0All contractor personnel sign a DOC provided confidentiality statement.MandatoryWithin 30 days after contract start
DISCOVER, DESIGN, DEVELOP, TEST, IMPLEMENT
14.0Master 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.Mandatorywithin 90 days after contract start
14.0
20.0Project Documents - Implementation Plan. Project Deployment Plan Narrative and Proposed Service Delivery Schedule.Mandatorywithin 90 days after contract start
14.0Design phase - design capability/functions defined in EXHIBIT A: FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS WORKBOOKMandatoryPrior to Design complete milestone
14.0
18.0Project Documents - Security Controls Report. Appropriate security controls in place and received approval from DOC ISO.MandatoryPrior to any DOC data being stored in the solution environment. Quarterly reviews thereafter.
14.0
18.0Project Documents - System Security Plan. Plan detailing system security requirements.MandatoryPrior to any DOC data being stored in the solution environment
27.0System Testing and Acceptance Procedures - Develop test plan and submit to SMARA-4 PM for review and approval.MandatoryPrior to UAT start
14.0Validation - Each requirement configured according to design. Unit and system testing conducted.MandatoryPrior to UAT complete milestone
14.0Project Documents - Demo. Provide demo of user stories so that feedback can be provided early and often.MandatoryPrior to UAT complete milestone
16.0Data conversion and migration - assist in the conversion and validation into the new system.Mandatory OptionalPrior to UAT complete milestone
14.0
27.0Project Documents - Test Plan and Logs.MandatoryPrior to UAT complete milestone
14.0
27.0Project Documents - Test Status Monthly ReportMandatoryPrior to UAT complete milestone
14.0Knowledge transfer - DOC is provided with documentation and training materialsMandatoryPrior to Go Live
14.0Training - detailed training package has been defined and delivered.MandatoryPrior to Go Live
14.0
21.0Project Documents - SaaS Product AccessMandatoryPrior to Go Live
14.0
29.0Project Documents - Detailed Training PlanMandatoryPrior to Go Live
14.0Project Documents - Manuals and FAQ's. System manuals, SOP's, process flows, technical specs, design and functionality.MandatoryPrior to Go Live
14.0Project Documents - Requirements Traceability Matrix.MandatoryPrior to Go Live
14.0
30.0Project Documents - Monthly Operations Report. Project data dashboard.MandatoryPrior to Go Live
14.0
19.0Project Documents - Disaster Recovery Plan. Plan detailing disastery recovery plan and procedures.MandatoryPrior to Go Live
17.0

14.0 24.0

27.0Reporting - 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.MandatoryPrior to Go Live
14.0Go Live - SMARA-4 is promoted into production and successfully runa mongst the user community.Mandatory12 months after contract start
27.0Acceptance Period - 90 day production validation for maintaining and supporting the released solution.Mandatorhy3 months after Go Live
MAINTENANCE AND OPERATIONS
30.0Maintenance and Operations - Maintaining all configurations, customizations/interfaces, backups, security, incident management, patches, upgrades to the solution while meeting defined Section 34 Service Level Agreements.MandatoryAfter Go Live
31.0Help Desk/Call Center - Provide Tier 2 technical support and service as defined in the Section 31 Help Desk/Call Center.MandatoryAfter Go Live
14.0Project Documents - Release notes. Description of changes, updates and resolved defectsMandatoryas required
19.0Disaster Recovery during M&O- Review Disaster Recovery Plan Annually. Execute annual disaster recovery simulation/test and report outcome.MandatoryAnnual
CONTRACT CLOSEOUT (if applicable)
14.0
28.0Project Documents - Transition Out Plan. Plan for transition to New Contractor or State.Mandatory6 months before end of contract
28.0Transition out supportMandatory90 days before end of contract
9.0Return all DOC property to DOC Contract AdministratorMandatory2 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 .