5_Exhibit D - Deliverables and Milestones Table_Pre-Solicitation_1.pdf

PDF 236 KB Posted

Attached to
State Water Board - California Wetland and Riparian Area Protection Portal (CalWRAPP)
Solicitation number
0000040884
Issued by
California

About this file

This document is an Exhibit D Deliverables and Milestones Table for Pre-Solicitation Number 0000040884 issued by the State of California State Water Resources Control Board for the California Wetland and Riparian Area Protection Portal (CalWRAPP) project. The solicitation seeks a contractor to design, configure, integrate, and implement a modern system to support all stages of dredge or fill application intake, review, and tracking. The deliverables are organized into 14 groups spanning project management, requirements clarification, design and development, system interfaces, data management, testing, training, configuration and release management, security and data protection, software licensing, maintenance and operations transition, project closeout, and optional Year 1 and Year 2 maintenance and operations support. Bidders must indicate agreement to provide each deliverable by marking "Yes" or "No" in the table. The scope encompasses comprehensive project planning, agile management activities, business process analysis, system architecture and implementation, interface development, data governance, extensive testing across multiple levels, user training, security management, and transition to ongoing support operations.

The document does not provide specific pricing terms, contract duration, response dates, or award dates within this exhibit. No set-asides, incumbent information, or funding sources are identified in this deliverables table. The optional deliverable groups (13 and 14) indicate that Year 1 and Year 2 maintenance and operations support services, including help desk support and monthly reporting, are available as add-ons to the base implementation contract. All deliverables must align with the State Water Board's IT security policies, NIST 800-53 standards, and state security standards as referenced in the corresponding exhibits and statement of work sections.

View the file

Other files

Show all 11

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

State of California State Water Resources Control Board (State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

EXHIBIT D: DELIVERABLES AND MILESTONES TABLE

Bidder must indicate agreement to each of the tasks and deliverables listed in the table below as described in SECTION 17. PROJECT (CONTRACTOR) TASKS AND DELIVERABLE

REQUIREMENTS and includes the following components:

1. Deliverable Name: The name of the Contractor Deliverable.

2. Description: The description as described in Table D-1 below.

3. Contractor Agrees to Provide the Deliverable: The Bidder must indicate its agreement to provide the deliverable by entering "Yes" or "No" for each deliverable in the table.

Table D-1: Deliverables

Deliverable Group #1: Project Management Deliverables Description Contractor Agrees to

Provide the Deliverable (Yes/No)

1.1 Project Management Plans

1.1.1 Project

Management Plan

The plan documents how the project will be executed, monitored, controlled, and completed. It establishes the approach for managing scope, schedule, cost, quality, resources, communications, risks, procurement, and stakeholder engagement. The plan also documents governance, roles and responsibilities, approved baselines, and change control

Yes ☐

No ☐

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table procedures to guide project delivery and achievement of objectives.

1.1.2 Communication

Management Plan

The plan documents how project information will be developed, shared, and maintained to support stakeholder coordination and informed decision-making. It identifies communication needs, audiences, responsible parties, delivery methods, frequency, and escalation procedures. The plan establishes expectations for timely, accurate, and consistent communication throughout the project lifecycle.

1.1.3 Implementation

Management Plan

The plan documents how the solution will be deployed and transitioned into operational use. It establishes implementation activities, roles and responsibilities, timelines, dependencies, readiness criteria, and procedures for cutover, rollback, and post-implementation support. The plan coordinates technical deployment, user readiness, and operational handover to support a controlled implementation and minimize disruption to business operations.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

1.1.4 Project Organization

Chart

The chart illustrates a visual representation of the project’s organizational structure, showing key roles, reporting relationships, and lines of authority. It clarifies how the project team, leadership, and supporting groups are organized to support accountability, coordination, and decision-making.

1.1.5 Schedule

Management Plan

The plan documents how the project schedule will be developed, approved, maintained, and controlled. It establishes scheduling methods, roles and responsibilities, milestones, task dependencies, progress reporting, and procedures for managing schedule changes. The plan also specifies how schedule variances will be monitored, communicated, and addressed to support timely completion of project objectives.

1.1.6 Project Schedule The schedule identifies the activities, milestones, durations, dependencies, and planned start and finish dates required to complete the project. It provides a timeline for coordinating resources, tracking progress, and assessing the impact of delays or changes on project completion.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

1.1.7 Project Schedule

(Weekly Updates)

Records the updates to the Project

Schedule on a weekly basis effective with the delivery and the State’s acceptance and baselining of the initial version of the Project Schedule.

1.1.8 Requirements

Traceability Matrix

(RTM) Management

Plan

Documents how the RTM will be developed, maintained, reviewed, and controlled throughout the project lifecycle. It establishes the matrix structure, traceability relationships, roles and responsibilities, update frequency, and change control procedures to ensure approved requirements remain linked to their sources, solution components, test cases, and acceptance results.

1.1.9 Requirements

Traceability Matrix

Documentation that links each functional and non-functional requirement to its source, associated design or solution components, test cases, and verification results. It supports tracking requirement coverage, assessing change impacts, and confirming that approved requirements have been implemented, tested, and satisfied.

1.1.10 Risk Management

Plan

Documents and defines how project risks will be identified, assessed, rated, Yes ☐

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table prioritized, monitored, and managed throughout the project lifecycle. It establishes roles and responsibilities, assessment criteria, response strategies, reporting requirements, and escalation procedures to reduce threats to project objectives and support informed decision-making.

1.1.11 Risk Register

(Weekly Updates)

The centralized record of identified risks, including their likelihood, potential impact, priority, assigned owners, response strategies, and current status. It supports ongoing monitoring and accountability to manage uncertainty and reduce potential impacts on project objectives.

1.1.12 Issue Management

Plan

Documents how issues will be identified, documented, prioritized, assigned, tracked, and resolved throughout the project lifecycle. It establishes roles and responsibilities, resolution timeframes, reporting requirements, escalation procedures, and closure criteria to address problems promptly and minimize their impact on project objectives.

1.1.13 Issue Log (Weekly

Updates)

The centralized record of issues requiring resolution, including their Yes ☐

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table descriptions, priorities, assigned owners, status, target resolution dates, and resolution actions. It supports tracking, escalation, and accountability to minimize impacts on project

1.1.14 Change

Management Plan

Documents how proposed changes to scope, schedule, cost, and other approved baselines will be submitted, evaluated, approved, implemented, and tracked. It establishes roles and responsibilities, impact assessment criteria, approval authority, and communication procedures to ensure changes are controlled and aligned with project objectives.

1.1.15 Change Log

(Monthly Updates)

The centralized record of changes requiring resolution, including their descriptions, priorities, assigned owners, status, target resolution dates, and resolution actions. It supports tracking, escalation, and accountability to minimize impacts on project

1.1.16 Weekly Status

Meetings

Recurring regularly scheduled project meetings to review progress, upcoming activities, schedule performance, risks, issues, and

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table decisions requiring attention. They support team coordination and accountability by confirming priorities, assigning action items, and escalating concerns that may affect project objectives.

No ☐

1.1.17 Weekly Status

Reports

The report summarizes weekly overall project health, accomplishments, upcoming activities, schedule and budget performance, key risks and issues, and decisions requiring attention. It provides stakeholders with a consistent view of progress, highlights deviations from the approved plan, and identifies corrective actions and support needed to achieve project objectives.

1.1.18 Monthly Status

Meetings

Recurring regularly scheduled project meetings to review progress, upcoming activities, schedule performance, risks, issues, and decisions requiring attention. They support team coordination and accountability by confirming priorities, assigning action items, and escalating concerns that may affect project

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

1.1.19 Monthly Status

Reports

The report summarizes monthly overall project health, accomplishments, upcoming activities, schedule and budget performance, key risks and issues, and decisions requiring attention. It provides stakeholders with a consistent view of progress, highlights deviations from the approved plan, and identifies corrective actions and support needed to achieve project objectives.

1.2 Agile Management

1.2.1 Project Roadmap The project’s Project Roadmap shall

consist of high-level, evolving view of the CalWRAPP product vision, intended outcomes, prioritized capabilities, and anticipated releases over time. It guides stakeholder alignment and delivery planning while allowing priorities and timing to adapt to feedback, learning, and changing business needs.

1.2.2 Product Backlog The project’s Product Backlog shall

consist of an ordered, evolving list of features, enhancements, defects, and other work needed to achieve the product’s goals. The Product Owner manages its priorities, while the project

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table team refines items to support delivery planning and respond to stakeholder feedback and changing business needs.

1.2.3 Sprint Planning

Sessions

Upon the completion and acceptance of the project’s Project Roadmap and

Product Backlog, Sprint Planning

Sessions, which are the meetings in which the project team establishes each Sprint Goal, selects prioritized

Product Backlog items, and develops a plan for completing the work during the subsequent sprint will be mandatory through the lifecycle of the project. The sessions align delivery expectations with project team capacity, dependencies, and the level of effort required.

1.2.4 Sprint Backlog Each Sprint Backlog consists of the

Sprint Goal, selected Product Backlog items, and the team’s plan for delivering them during the sprint. It is maintained and updated by the

Developers as work progresses, providing visibility into the work needed to achieve the Sprint Goal.

1.2.5 Daily Stand-Ups The Daily Stand-Ups are daily

meetings in which team members Yes ☐

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table review progress toward the Sprint

Goal, coordinate upcoming work, and identify impediments. They support timely adjustments to the team’s plan, with detailed discussions and problem-solving handled separately.

1.2.6 Burndown Charts

1.2.7 Testing and

Validation Results

Demonstrate the completed increment to stakeholders, inspect results against the sprint goal, and capture feedback for future work.

1.2.8 Sprint

Retrospectives

Sprint Retrospective meetings shall be held at the end of each Sprint to evaluate team collaboration, processes, tools, and practices. The team identifies what worked well, what needs improvement, and actionable changes to improve quality and effectiveness in subsequent sprints.

Deliverable Group #2: Requirements Clarification/Finalization

Deliverables Description Contractor Agrees to Provide the Deliverable (Yes/No)

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

2.1 Business Process

and Requirements

Analysis

Requirements Clarification and

Finalization sessions shall be performed to resolve ambiguities, confirming stakeholder needs, and refining requirements so they are clear, complete, consistent, feasible, and testable. Results will establish an agreed-upon, approved requirements baseline to guide solution design, development, implementation testing, and acceptance, with subsequent changes managed through the formal change control process.

2.2 Fit Gap Analysis Conducts a Fit-Gap Analysis using

EXHIBIT C: FUNCTIONAL AND NON-

FUNCTIONAL REQUIREMENTS to identify where the proposed

CalWRAPP solution meets or does not meet system requirements, and documents necessary configurations or customizations. Includes collaboration with the State to confirm and refine.

2.3 Requirements

Clarifications

(Functional, Non-

Functional, Transitional)

The Requirements Clarification process will include the structured review, refinement, validation, and approval of business, functional, and nonfunctional requirements to ensure they are clear, complete, consistent, (State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table feasible, and testable before implementation.

2.4

Requirements

Finalization

(Functional, Non-

Functional, Transitional)

The Requirements Finalization process will include reviewing, resolving, and formally approving the requirements that define what the solution must do, how well it must perform, and what constraints it must satisfy. It establishes the approved requirements baseline for design, development, implementation, testing, and solution acceptance.

2.5 Requirements

Traceability Matrix

The document that links each

CalWRAPP system requirement to its business objective or source, associated design components, development deliverables, test cases, and verification results. It provides bidirectional traceability, allowing the project team to track requirements through implementation and testing and confirm that delivered functionality addresses approved requirements.

Deliverable Group #3: Design, Development, and Implementation

Deliverables Description

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

3.1 Business

Requirements

Document

The document defines the CalWRAPP business needs, objectives, scope, and expected outcomes of a system implementation project. It documents stakeholder requirements, business processes, rules, assumptions, constraints, and success criteria, providing an agreed foundation for system design, development, testing, and acceptance.

3.2 System Architecture

Documentation

The document describes the overall structure of the CalWRAPP system, including its major components, technology platforms, interfaces, data flows, security controls, and deployment environments. It defines how these elements work together to meet business and technical requirements and provides a foundation for system design, implementation, integration, and ongoing support.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

3.3 Data Architecture

Documentation

The document defines how the

CalWRAPP data is structured, stored, integrated, and accessed within the system. It describes data models, relationships, sources, flows, and standards, along with security, quality, and retention requirements, providing a foundation for database design, data migration, integration, and ongoing data management.

3.4 Functional and

Technical Design

Documentation

Provides the design of the functionality in scope and associated technical design that addresses how the functional design will be implemented.

Yes ☐

No ☐

3.5 Solution

Implementation

Plan

The document defines the activities, sequence, responsibilities, resources, and schedule required to deploy the

CalWRAPP solution into production. It addresses configuration, integration, data migration, testing, user training, operational readiness, cutover, and post-implementation support, including deployment approval criteria and rollback procedures to support a controlled transition to the new system.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

3.6 System

Environments

(Development, System Integration

Testing, UAT, Training, Production)

Set up and configure the environments:

1. Development (DEV)

2. System Integration Testing (SIT)

3. USer Acceptance Testing ( UAT)

4. Training (TRN)

5. Production (PRD) in accordance with EXHIBIT F: State Water

Board IT SECURITY POLICIES, assisting the State to ensure that all the required software, services, and configurations are aligned with the project’s requirements, including system access controls, security protocols, and software dependencies.

3.7 Development Data

Sets

Development of Test Data Sets shall include creating or preparing representative data to validate system functionality, integrations, performance, and business rules. The data includes valid, invalid, boundary, and exception scenarios aligned with test cases and expected results, using synthetic or appropriately masked data to protect sensitive information.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

3.8 Solution

Implementation

Completion Report

The document summarizes the implementation activities performed and confirms the system’s delivery against approved scope and acceptance criteria. It documents deployment results, testing outcomes, data migration status, outstanding issues, stakeholder approvals, and transition to operational support, providing a formal record of implementation completion and any remaining follow-up actions.

Deliverable Group #4: System Interfaces

Deliverables Description Contractor Agrees to Provide the Deliverable (Yes/No)

4.1 Interface

Management Plan

Captures the integration approach and data design for CalWRAPP, focused on the interfaces to external systems.

Yes ☐

No ☐

4.2 Interface

Development Plan

Code, configure, build, and unit test all interfaces of CalWRAPP in alignment with the State Implementation

Preferences in accordance with the

Project Schedule. The State’s

Implementation Preferences are identified in STATEMENT OF WORK

SECTION 28: SYSTEM

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

IMPLEMENTATION OR

INTEGRATION

4.3 Interface Design

Document

The document defines how interfaces between systems, applications, and external services will be identified, designed, developed, tested, and maintained. It establishes interface requirements, data exchange standards, ownership, dependencies, security controls, and change management procedures to support reliable integration and ongoing operation.

4.4 Interface Control

Documents

The document specifies the technical requirements for interactions and data exchanges between systems or components. It defines data formats, field mappings, communication protocols, security requirements, processing rules, and error handling, providing an agreed baseline for interface development, testing, and change control.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

4.5 Interface

Implementations

Interfaces as identified in Section 26 of the SOW will be designed, developed and implemented for the SIT, UAT, TRN and PRD environments of the

CalWRAPP solution.

Deliverable Group #5: Data Management Deliverables Description Contractor Agrees to

Provide the Deliverable (Yes/No)

5.1 Data Management

Plan

Defines the project’s approach to data governance, ownership, quality, access, retention, issue resolution, and approval. Identifies the data deliverables, responsible roles, and review milestones.

5.2 Data Inventory and

Classification

Register

Identifies in-scope datasets, source systems, owners, sensitivity classifications, and disposition decisions, including any data will be migrated, archived, or retained in place.

5.3 Data Model/

Database Schema

Documents the target data structure, including entities, relationships, keys, and integrity constraints. Includes the physical database schema or platform object model, as applicable.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

5.4 Data Dictionary Defines business and technical data

elements, including their meanings, formats, allowed values, required fields, and applicable validation rules.

Yes ☐

No ☐

Deliverable Group #6: Testing

Deliverables Description Contractor Agrees to Provide the Deliverable (Yes/No)

6.1 Master Test Plan The document defines the strategy, scope, activities, resources, responsibilities, and schedule for verifying and validating a system. It establishes test levels, environments, entry and exit criteria, defect management procedures, and reporting requirements to confirm that the system meets approved requirements and is ready for acceptance and deployment.

6.2 Use Cases and Test

Cases

Documentation

Use Cases and Test Cases

Documentation describes how users interact with a system to accomplish business tasks and how those interactions and system requirements will be verified. Use cases define actors, preconditions, workflows, and expected outcomes; test cases specify test data, execution steps, and

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table expected results to support repeatable testing and requirements traceability.

6.3 Test Scripts Test Scripts document the step-by-

step instructions or automated commands used to execute a test case. They specify prerequisites, test data, actions, and expected results to support consistent, repeatable testing and the recording of actual results, pass/fail status, and identified defects.

6.4 Testing Execution Testing Execution shall be performed

for all planned tests to verify that the implemented system meets approved business, functional, and nonfunctional requirements. It includes executing test scripts, comparing actual results with expected results, documenting evidence and pass/fail status, reporting defects, and conducting retesting and regression testing to

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table support system acceptance and deployment readiness.

6.4.1 System The final solution is the completed, tested, and approved systems delivered by the implementation project. It includes the configured software, integrations, migrated data, documentation, and operational support capabilities required to meet approved business and technical requirements and support production use as well as all lower system environments.

6.4.2 Integration Integration testing shall be managed, performed and results documented by the Contractor throughout the SDLC of the project.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

6.4.3 UAT User Acceptance Testing (UAT) will be

managed and coordinated by

Contractor and performed by the DWQ program staff to confirm that the system supports intended business operations, documents defects and results, and provides evidence for authorized stakeholders to approve system acceptance and deployment readiness.

6.4.4 Performance, Load Performance and load testing shall be performed throughout the SDLC by the

Contractor and once the Production environment build is complete.

6.4.5 Security, Penetration

Security and Penetration testing shall be performed throughout the SDLC by the Contractor and once the

Production environment build is complete.

6.4.6 Interfaces Interface testing will be executed

throughout the SDLC and once the

Production environment build is complete.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

6.5 Test Data Sets The Contractor shall have ownership

of how test data will be identified, created, secured, maintained, and made available to support system testing. The Contractor owns the responsibilities and procedures for data selection, masking or synthetic data generation, loading, refresh, reuse, and disposal to ensure representative, consistent, and protected data across all environments subject to testing.

6.6 Testing Results

Reports

(Development, System Integration, UAT, Performance, Load, Security, Penetration, Interfaces)

Testing results for all testing efforts will be documented and shared with the

CalWRAPP Project Directors and

Project Manager.

Deliverable Group #7: Training

Deliverables Description Contractor Agrees to

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

7.1 Training

Management Plan

The document identifies all the activities and defines the curricula the

State Water Board needs to train the organization and other stakeholders on

CalWRAPP. Audience-specific training efforts shall include Super User

Training, End-User Training, Business

Administrator Training, and IT Staff

Training.

7.2 Training Materials Training Materials will be developed in coordination with the OCM Contractor and utilized including role-specific instructions and learning resources to help users and support staff operate and maintain the implemented system.

They include user guides, presentations, exercises, demonstrations, and quick reference guides aligned with approved business processes and system functionality to support user readiness and adoption.

7.3 Training Execution

Training execution shall be performed in coordination with the OCM

Contractor and include the following user groups:

1. Public facing users

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

2. State Water Boards program staff

3. State Water Boards system administrator staff.

7.4 Training Completion

Report

The document summarizes the training delivered for a system implementation project, including sessions conducted, topics covered, attendance, participant assessments, and feedback. It documents results against training objectives, identifies remaining training needs, and provides evidence of user and support staff readiness for system operation.

Deliverable Group #8: Configuration and Release Management

Deliverables Description Contractor Agrees to Provide the Deliverable (Yes/No)

8.1 Release

Management Plan

Describes the development, integration, testing, data conversion, rollout approach, and methods for each staging and the production release.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

8.2 Configuration

Management Plan

Describes the standardized methods and procedures to be used for efficient and prompt handling of all changes, ensuring that all changes to

CalWRAPP configuration items are recorded as per the plan, and the overall business risk it mitigated.

8.3 Cut-Over Plan The document defines the sequence, timing, responsibilities, and dependencies for transitioning from the existing system to the new production system. It includes final data migration, deployment activities, validation checks, communications, go/no-go criteria, and rollback procedures to support a controlled transition with minimal operational disruption.

8.4 Configuration

Implementation

(Development, QA, Staging, Production, Training)

Configuration Implementation is the process of applying approved system settings, business rules, workflows, security permissions, and other configurable features to meet business and technical requirements. It includes validating and documenting the configuration and deploying it to the appropriate environments through established change control procedures.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

8.5 Pilot Deployment

Report and Signoff

Ensures that the pilot successfully demonstrated improved usability, end user efficiency and stability to both internal and external end-users prior to going live. The pilot will be performed after UAT and will include identifying and resolving any issues identified during the CalWRAPP pilot. The deliverable will be considered complete once the State Water Board confirms CalWRAPP will allow users to perform end-to-end business processes without issues, improving efficiency/usability.

8.6 System Stabilization

Report

The document summarizes system performance, reliability, and operational issues prior to production deployment. It documents incidents, defects, corrective actions, monitoring results, and outstanding risks, providing evidence of progress toward stabilization criteria and readiness for transition to routine maintenance and support.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

8.7 Formal System

Acceptance and

Final Go-Live

Report

The document includes a status report of all system components to ensure

CalWRAPP functions effectively in production. Once CalWRAPP has been migrated to production and rolled out to the entire organization, CalWRAPP must be stabilized to allow support to be migrated from the cut-over support team to the M&O team.

Deliverable Group #9: Security and Data Protection

Deliverables Description Contractor Agrees to Provide the Deliverable (Yes/No)

9.1 System Security

Management Plan

The document describes the data and security protection measures, Security

Risk Assessment and Plan of Action needed for CalWRAPP. It shall include moderate level National Institute of

Standards and Technology (NIST)

800-53 and be compliant with SIMM

22 COTS/SaaS Acquisition, SIMM

5315-B, Cloud Security Standards and

State Water Board’s security standards.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

9.2 Security Test

Management Plan

The document defines the scope, approach, responsibilities, resources, and schedule for testing a system’s security controls and identifying vulnerabilities. It establishes testing methods, environments, acceptance criteria, findings reporting, remediation, and retesting procedures to verify security requirements and support deployment readiness.

Deliverable Group #10: Software/SaaS/Hosting Subscriptions

Deliverables Description Contractor Agrees to Provide the Deliverable (Yes/No)

10.1 List of Software

Licensing

The Contractor shall provide a preliminary list of all the software licenses required for the CalWRAPP solution at the initiation of the project and a final list at the completion of the project.

10.2 List of SaaS

Licensing

The Contractor shall provide a preliminary list of all the SaaS licenses required for the CalWRAPP solution at the initiation of the project and a final list at the completion of the project.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

10.3 List of Hosting

Licensing

The Contractor shall provide a preliminary list of all hosting licenses required for the CalWRAPP solution at the initiation of the project and a final list at the completion of the project.

Deliverable Group #11: System Transition to Maintenance and Operations (M&O) Deliverables Description Contractor Agrees to

Provide the Deliverable (Yes/No)

11.1 M&O Management

Plan

Document includes the resources, services, processes, and procedures necessary to operate, administer, and maintain CalWRAPP at or above the performance requirements defined in

EXHIBIT C: FUNCTIONAL AND NON-

FUNCTIONAL REQUIREMENTS. The plan shall identify both State and

Contractor roles and responsibilities

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

11.2 Transition to M&O

Plan

The document shall define the activities, responsibilities, schedule, and readiness criteria for transferring an implemented system from the project team to the ongoing support organization. It addresses knowledge transfer, documentation, staffing, access, monitoring, incident management, and maintenance procedures to ensure operational continuity and formal acceptance of support responsibilities.

11.3 System

Maintenance

Manual

The document shall include the procedures and technical information needed to maintain and support a production system. It includes routine maintenance, monitoring, troubleshooting, backup and recovery, patching, configuration updates, and escalation procedures to support reliable, secure, and continuous system operation.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

11.4 System

Administration

Guide

The document shall include the documentation of the procedures and technical information required to administer a system. It covers system configuration, user accounts, access permissions, security settings, monitoring, and scheduled processes to support consistent, secure, and reliable operation.

11.5 System

Performance and

Capacity

Management Plan

Guides the development and operation of CalWRAPP from a performance and capacity management perspective.

The plan shall describe how

CalWRAPP can meet performance requirements and meet appropriate

Service Levels and produce performance reports to show compliance with SLAs.

11.6 Technology

Recovery Plan

A recovery plan based on and compliant with SIMM Section 5325-A that clearly identifies all State responsibilities for technology recovery activities as stated in EXHIBIT A, SECTION 21: SECURITY.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

11.7 Help Desk

Management Plan

The document shall define how user support services will be organized, staffed, and delivered. It establishes procedures for receiving, prioritizing, tracking, resolving, and escalating support requests, along with service levels, responsibilities, communications, and performance reporting to support timely issue resolution and reliable system use.

11.8 Help Desk Support

Manual

The document shall the include procedures and reference information used by support staff to assist users and resolve system issues. It includes ticket handling, troubleshooting, common solutions, escalation paths, and communication protocols to support consistent and timely service.

11.9 Help Desk

Implementation

The Contractor shall establish and activate user support services, including staffing, support tools, ticket workflows, escalation procedures, and service levels. It includes training support personnel and validating readiness to receive, track, and resolve user requests and system issues. Activation shall take place with the start of the system stabilization period.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

11.10 Help Desk Statistics

Reporting

Framework

The Help Desk Statistics and

Reporting Framework shall define the metrics, data sources, reporting frequency, and responsibilities used to monitor support performance. It shall include ticket volume, response and resolution times, backlog, service level compliance, recurring issues, and user satisfaction to support management oversight and continuous service improvement.

11.11 System Transition

to M&O

Covers the transfer of M&O functions and activities including Help Desk support to the State or its designee and shall contain the Knowledge

Transfer (KT) approach and documentation necessary to develop the ability of the State (or its designee) to operate CalWRAPP and maintain those system components over which the state will have maintenance responsibility.

Deliverable Group #12: Project Closeout Deliverables Description Contractor Agrees to

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

12.1 Updated

Documentation

The Contractor will have ownership of updating all CalWRAPP project and

M&O documentation at the completion of the project.

Yes ☐

No ☐

12.2 Participation in

Lessons Learned /

Retrospective

Sessions

The Contractor shall participate in the project’s Lessons Learned and

Retrospective sessions at the conclusion of the project to provide input into the project’s Post

Implementation Evaluation Review report to the CDT PAO.

OPTIONAL

Deliverable Group #13: M&O Support – Optional Year 1

Deliverables Description Contractor Agrees to

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

13.1 M&O Support Maintenance and Operations (M&O)

Support shall be comprised of the ongoing services required to keep the

CalWRAPP solution production system reliable, secure, and available. It includes system monitoring, user support, incident resolution, defect correction, routine maintenance, patches, and controlled updates to sustain system performance and meet business needs. The M&O support organization shall also maintain the

CalWRAPP lower environments in order keep them synchronized with the

Production environment for change management purposes.

13.2 Monthly M&O

Report

The report shall summarize system performance, availability, support activities, incidents, and maintenance completed during each reporting month. It documents service level compliance, outstanding issues, risks, and planned activities to support management oversight and ongoing service improvement.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

13.3 Help Desk Support Contractor shall provide services that assist users with system access, functionality, and technical issues. It includes receiving and tracking requests, troubleshooting problems, providing guidance, and resolving or escalating issues to support timely assistance and continued system use.

13.4 Monthly Help Desk

Statistics Report

The report shall summarize user support activities and service performance during the reporting month. It shall include ticket volumes, response and resolution times, outstanding requests, recurring issues, service level compliance, and user satisfaction to support management oversight and service improvement.

Deliverable Group #14: M&O Support – Optional Year 2

Deliverables Description Contractor Agrees to

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

14.1 M&O Support Maintenance and Operations (M&O)

Support shall be comprised of the ongoing services required to keep the

CalWRAPP solution production system reliable, secure, and available. It includes system monitoring, user support, incident resolution, defect correction, routine maintenance, patches, and controlled updates to sustain system performance and meet business needs. The M&O support organization shall also maintain the

CalWRAPP lower environments in order keep them synchronized with the

Production environment for change management purposes.

14.2 Monthly M&O

Report

The report shall summarize system performance, availability, support activities, incidents, and maintenance completed during each reporting month. It documents service level compliance, outstanding issues, risks, and planned activities to support management oversight and ongoing service improvement.

(State Water Board)

Pre-Solicitation Number: 0000040884 Deliverables and Milestones Table

14.3 Help Desk Support The Contractor shall provide services

that assist users with system access, functionality, and technical issues. It includes receiving and tracking requests, troubleshooting problems, providing guidance, and resolving or escalating issues to support timely assistance and continued system use.

14.4 Monthly Help Desk

Statistics Report

The report shall summarize user support activities and service performance during the reporting month. It shall include ticket volumes, response and resolution times, outstanding requests, recurring issues, service level compliance, and user satisfaction to support management oversight and service improvement.

EXHIBIT D: DELIVERABLES AND MILESTONES TABLE

File details come from the government source that posted it. Updated .