A01_12_PWS_CalSimLogic_2026_1.docx

PERFORMANCE WORK STATEMENT (PWS)

CalSim Model Development and Operations Analysis

1.0 SCOPE

1.1 Objective

The objective of this contract is to acquire contractor services to support improvements to operational assumptions within the CalSim model and support the Bureau of Reclamation (Reclamation) in related operations analysis; focusing on allocation, export, rescheduling, model efficiency, Cooperating Operations Agreement (COA) considerations, and Millerton operations logic.

1.2 Background

Reclamation and the California Department of Water Resources (DWR) have a collaboratively developed version of the California Simulation (CalSim) model of the Central Valley Project (CVP) and the State Water Project (SWP) operations, known as CalSim. CalSim simulates monthly operations for the CVP, SWP, and local agencies within the Sacramento and San Joaquin Valleys, and it is the central model for long-term planning for the Bay-Delta watershed system which is a vital water source for municipal, agricultural, and environmental purposes. By modeling hypothetical operations, CalSim provides information on the impaired hydrology of the system, a necessary component for analyzing proposed changes to operations, regulations, infrastructure or to determine the effects of weather variability. Outputs are used in various secondary modeling which includes models for power generation, temperature, water quality, and the effects on the biological resources reliant on the Bay-Delta system.

CalSim logic has constantly been developing from the first release of benchmark studies in 2002 through the present. New and/or improved capabilities in modeling physical and operational aspects of CVP/SWP management have been developed, as time and budgets have allowed, and as growing the application spectrum has highlighted issues to address. Efforts have included incorporation of an ANN for delta water quality, updates to Colusa Basin demand representation, conveyance facilities, and connectivity to enable implementation of Sites Reservoir, daily disaggregation of Sacramento River flows to better simulate Fremont Weir spills and gated structures, and ongoing work to craft logic as regulatory criteria is tested, implemented, and modified via multiple processes. The modeling needs, available expertise, and technology is continually evolving, and Reclamation is in need of additional support to respond to rapid changes in internal priorities and the regulatory environment in a timely manner while continuing to improve the capabilities and accuracy of CalSim.

2.0 CONTRACT DETAILS

2.1 Type of Contract

Time and Materials (T&M) Service Contract

2.2 Period of Performance

This contract shall be for a Base Year and 4 Option Years. The Option Years will be exercised based on the performance of the Contractor and the existing need for the services by the Government. The period of performance will be as follows:

2.3 Recognized Holidays:

The Federal Government recognized Holidays are as follows:

Independence Day

2.4 Place of Performance

The work to be performed under this contract shall be performed at the Contractor’s facility and other places appropriate for meetings.

3.0 TASKS

The contractor shall perform the following tasks:

1. Project Management, Meetings, and Coordination

2. Support Ongoing Needs for CalSim Model Development

3. Support Operations and Modeling Staff on an as needed basis Comment by Johnson, Levi E: For COA support we may or may not need support in our educational process on COA, I see this resource more as a potential support for actual technical analysis, review, documentation etc. Trying to capture this throughout

4. Data Management and Documentation

3.1 Project Management, Meetings, and Coordination

The Contractor’s designated Point of Contact (POC) and the Reclamation Contracting Officer’s Representative (COR) shall, at a minimum, establish and maintain a recurring weekly meeting. The purpose of these meetings is to facilitate regular progress updates from the Contractor and to ensure effective coordination with Reclamation technical personnel. These meetings are particularly important due to the potential for unforeseen technical challenges and shifting project priorities.

Reclamation technical staff reserve the right to cancel or reschedule any meeting based on necessity or logistical considerations. Additional meetings or communications may be initiated by either party on an as-needed basis to address emergent issues or time-sensitive matters.

The Contractor and Reclamation will determine project schedules jointly, and it is the Contractor’s responsibility to manage their resources to meet the schedule after it has been set. The schedule can be adjusted to provide additional time at the Reclamation COR’s discretion.

3.1.1 Deliverables and Due Dates

· Deliverables:

· Summaries of progress meetings as requested.

· Invoices and progress reports on an agreed upon schedule, no less than quarterly.

· Due Date: Performance period of the task order.

3.2 Ongoing Needs for CalSim Model Development

The Contractor shall provide CalSim development support, which may include, but are not limited to:

· Explore perspectives on setting CVP allocation that directly reflect the decision process used by Central Valley Operations Office. The goal is to create an allocation procedure in CalSim which is repeatable and not iterative.

· Implement flexibility in CVP/SWP COA accounting, including debt to project storage or other mechanisms and explore alternative coordinated operations.

· Support staff on the current Cooperating Operations Agreement implementation in CalSim, and analysis of COA balance from CalSim results.

· Examine opportunities to improve model efficiency: cycle structure, San Joaquin groundwater simulation, transfer-type operations, ect.

· Redesign logic of Millerton Lake operations with Friant Kern Project allocations.

· Implement CVP operations of the Delta Mendota Canal and Joint Use Branch of the California Aqueduct include water user rescheduling of allocated supplies, which has influence on San Luis operations and Jones exports. Furthermore, well-established water user practices for groundwater pumping, sales, and tradeoffs with San Joaquin supplies affect the timing of CVP facility operations. A template should be developed which allows these operations to affect model results, propagating from Jones and intertie use to delta conditions and north of Delta storage operations.

· Create a database of historical water sources, water uses, and data source for individual contractors represented in CalSim.

· Create post-processing tools for QAQC, model diagnostics, and analyzing system efficiency.

Tasks shall be prioritized and assigned at the discretion of Reclamation. Level of effort will be coordinated between Reclamation and the Contractor, but expected to include: WRESL code development, comments in the code to explain logic, quality assurance checks, and Reclamation staff walk-through of implementation.

3.2.1 Deliverables and Due Dates

· Deliverables:

· Interim copies of WRESL code being developed under this contract to be made available within 2 business days of Reclamation request for review.

· Interim and final code shall be made available to Reclamation via secure online platform (like SharePoint).

· Post-processing scripts and spreadsheets created under this contract to be made available within 2 business days of Reclamation request for review.

· Due Date: Performance period of the task order; within 2 business days for interim copies of WRESL code

3.3 Data Management and Documentation

The Contractor shall provide final models and documentation on all code developed under this contract by the end of the contract. Documentation shall include comments within the developed code to explain the logic and requested memorandums. Comment by KITECK, ELIZABETH G: Might be good to give a deadline to ensure delivery of documentation. and final models.

The Contractor shall provide a secure online platform for Reclamation to access the final models. Final models shall be available on the shared drive through the end of the contract period.

3.3.1 Deliverables and Due Dates

· Deliverables:

· Contractor will provide final copies of the WRESL code developed for the requested refinements on or before the termination of this contract. Final WRESL code shall include comments and output DSS files. Requested memorandums to be made available to Reclamation via secure online platform (like SharePoint).

· Due Date: Performance period of the task order.

3.4 Support Operations and Modeling Staff

The Contractor shall provide modeling and training support to both Central Valley Operations and the Bay-Delta Office Modeling Division on an as needed basis to support unforeseen and time sensitive tasks. These may include but are not limited to: CalSim modeling support that is not covered in Task 2, providing educational sessions and materials, technical analyses of CalSim models, gathering and processing relevant data, and review of draft CalSim models.

3.4.1 Deliverables and Due Dates

· Deliverables:

· Interim copies of WRESL code being developed under this contract to be made available within 2 business days of Reclamation request for review.

· Interim and final code shall be made available to Reclamation via secure online platform (like SharePoint).

· Post-processing scripts and spreadsheets created under this contract to be made available within 2 business days of Reclamation request for review.

· Support educational sessions in coordination with Reclamation.

· Perform technical analysis and relevant documentation

· Due Date: Performance period of the task order; within 2 business days for interim copies of WRESL code

4.0 PERFORMANCE REQUIREMENTS SUMMARY

Task No.

Task Description

Performance Indicator

Performance Standard Minimum Acceptable Quality Level

Regular (no less than quarterly) invoices and progress reports.

95% meeting requested meetings, invoices, and progress reports.

Support Ongoing Needs for CalSim Model Development

Product should be free from technical errors and contain accurate data.

Logical interpretation of the data from the resulting product must be possible.

Product should be free from technical errors and contain accurate data.

Plan and conduct training sessions and provide training materials All documents have been reviewed by Reclamation staff and any requested edits have been addressed

Logical interpretation of the data from the resulting product must be possible.

Models and Documentation accessible to Reclamation.

Model and documentation accessible to Reclamation.

Logical interpretation of the data from the resulting product must be possible.

Models and Documentation accessible to Reclamation.

5.0 DATA AND REPORTS - The contractor shall provide the following data and reports as follows:

Item No.

Description

Content

Format

Medium

Delivery