Cloud Migration District Checklist

The following are major District milestones and due dates associated with them. This list should be used as a checklist and guide when tracking and reporting District Cloud Migration Preparations. 

At least on monthly basis, please fill out your office's status in the corresponding checklist tracking spreadsheet:  District Cloud Migration Checklist Tracking

This is a living document, there may be additional tasks identified moving forward. 


Task 1 - Server Side Script Updates - Using the Script Update Decision Flow Chart 

  • Task1a - Determine update requirements for specialized SQL scripts
    • Due Date - 1 November 2024
    • Identify CDA enhancements necessary to the CDA team
    • If your District has any specialized SQL scripts, they need to be assessed by the District using the Script Update Decision Flow Chart.  If the specialized SQL script(s) does not fall into one of those categories, then the District needs to work with the CDA team to see if a new endpoint in CDA can be created.
  • Task1b - Categorize Server side scripts to CCP/Web/Python
    • Due Date - 22 November 2024
    • The flowchart will take you step by step through (CCP or Web or Python) categorizing  a server side script.  Make a list of all of your server side scripts, then work your way through the flowchart and identify a way forward for each one.  Additionally, identify any exceptional situations of scripts that do not fall on the flow chart, and contact HEC to discuss options for those exceptional situations.  
  • Task 1c - Data Sources and Computations
    • Due Date - 30 November 2024 
      • Fill out the Spreadsheet located here: District Data Sources.xlsx
        • Identify new data sources and computations your District uses 
        • Identify data sources and/or computations shared with other districts and coordinate with them
          • Ensure that there is a Lead Development POC for each data source your district requires
  • Task 1d - Convert or decommission Server side scripts to CCP/Python or have timeline mapped out and identified 
    • Due Date - 1 Aug 2025
    • Following the  Script Update Decision Flow Chart, Districts should take a hard look at the scripts on their server and those in the Data Acquisition spreadsheet.  They should then ensure that all scripts are either converted to a form of CCP or python, decommissioned and work with other districts to ensure there is only a single source of each data source.

Task 2 - Set up a Local CDA instance on the local server

  • Due Date - 22 November 2024
  • Each district has the ability to set up a local instance of CDA on their own T7 to help test and finalize scripts updates before implementation against the CWMS database in the cloud.  Local installation directions are available  on GitHub under the CWMS Data API Wiki.
  • Use directions to Read/Write to the local instance of CDA and the database directly, rather than to a data stream.  Instructions for this can be found on the Setting up CDA writes and cwms-python on T7s page. 
  • Any issues or questions should be posted to the GitHub page CWMS DATA API Issues.

Task 3 - CWMS-Python on the server

  • Due Date - 22 November 2024
  • cwms-python is a library that will allow users to use the new USGS python script and other improvements.
  • Instructions for setting up cwms-python on the T7s can be found on the lower part of the Setting up CDA writes and cwms-python on T7s page. 

Task 4 - Convert any OPENDCS or other processes saving to data streams to save directly to the database 

  • Task 4a - All processes saving directly to the database
    • Due Date - 10 January 2025
    • If you have anything on your server saving to a DataStream, it needs to be updated to save directly to the database
  • Task 4b - Update CCP schema to latest schema
    • Due Date - 10 January 2025

Task  5 - Use the CWMS Data API (CDA)

  • Due Date - 31 January 2026 
  • Once the National Database becomes available for Extract lists in the CAVI (CWMS 3.5), begin using them in CAVI and CWMS-Vue extracts and scripts. 
  • This can be done with local T7 instances of CDA prior to this deadline in preparation. 

Task  6 - Database Cleanup

  • Task 6a - Period-of-Record update for A2W (July 2025)
    • Due Date - 30 June 2025
    • Ensure entire Period-of-Record for TimeSeries shown in Access to Water are in the database
  • Task 6b - Add additional desired records from local archives directly into the database (July 2025)
    • Due Date - 30 June 2025
    • Import any Time Series that do no reside in the database into the database
  • Task 6c - Database Cleanup (Dec 2026)