A2_PWS_CalSimLogic_1.pdf

PERFORMANCE WORK STATEMENT (PWS)

CalSim Logic Modernization

October 6, 2022

1.0 SCOPE

The objective of this contract is to acquire contractor services to improve operational assumptions within the CalSim model, focusing on allocation, export, rescheduling, and Millerton operations logic.

1.2 BACKGROUND

The U.S. Bureau of Reclamation (Reclamation) and the California Department of Water Resources (DWR) have 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 II/3.

The model simulates monthly water operations for CVP, SWP, and local agencies within the Sacramento and San Joaquin Valleys. CalSim logic has continually evolved, 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.

2.0 REFERENCES - The following list of documents are required in the performance of this contract:

Number

Title and Edition

Date

Source

01 Latest CalSim Model Most Recent 800 Division, Bay Delta Office, Bureau of Reclamation

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. Data Management and Documentation

3.1 Project Management, Meetings, and Coordination

The Contractor shall liaise with Reclamation technical staff on an as needed basis, within a week of requested update during the course of the task order to coordinate tasks, resources and activities, and review progress and schedule. Additional communications shall be required to exchange information for billing and invoicing as needed.

3.1.1 Deliverables and Due Dates

• Deliverables: Summaries of requested progress meetings. 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, including forecasts of Sacramento Valley accretions, balancing reservoir storage conditions, and individual inflow forecasts for Trinity, Shasta, and Folsom reservoirs.

• Similarly, explore the basis for identifying an estimate of CVP export capability.

• Implement flexibility in CVP/SWP COA accounting, including debt to project storage or other mechanisms.

• Re-visit the design of Millerton Lake operations with Friant Kern Project allocations. This model logic was based on the old SANJASM model in 1999, and still uses many of those variable names and water balance definitions. These should be updated for better clarity and maintainability.

• 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.

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).

• 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. Documentation shall include comments within the developed code to explain the logic and requested memorandums.

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.

4.0 PERFORMANCE REQUIREMENTS SUMMARY

Task No.

Task Description

Performance

Indicator

Performance

Standard

Minimum Acceptable Quality

Level 01 Project

Management, Meetings, and Coordination

Coordination with Reclamation staff

Meetings within a week of request.

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

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

Support Ongoing Needs for CalSim Model Development

CalSim developments completed and provided to Reclamation

Interim models made available within 2 business days of Reclamation request.

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

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

Data Management and Documentation

Models and documentation made available to Reclamation

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

Model and documentation accessible to Reclamation.

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

Models 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

01 Summaries of progress meetings

See Task 1 Digital Email, MS Word, or

PDF

Email or upload to secure online platform

02 Invoices and Progress Reports

See Task 1 Digital Email, MS Word, or

PDF

Email or upload to secure online platform

03 CalSim Models/WRESL code developed

See Task 2 and 3

Digital WRESL code, DSS output

Upload to secure online platform

04 Memorandums See Task 3 Digital MS Word or

PDF

Email or upload to secure online platform