Flood DSS Prototype Report

• Title: Prototype FloodDSS Project Summary and Recommendations
• Description: Project Summary and Report document
• Decision Support - Doc Type: Report
• Date: 6/30/2006
• DSS: Flood
• Basin: Statewide
• Prepared By: Riverside

15
ESTIMATED
EFFORT
#
TASK/FEATURE
DESCRIPTION
(STATEWIDE
SYSTEM)
2
Evaluate alternative
Based on requirements, evaluate suitable technologies for
30 days +, depending
technologies.
the full -scale Flood DSS, including ArcServer. This
on the number of
evaluation should occur in conjunction with other CDSS
technologies that are
technology upgrades and focus on meeting system
evaluated
requirements. The evaluation should result in one or more
workable prototype, with limited functionality. Features
deemed high -risk for development should be evaluated
first. A design document should be produced if an
alternative technology is chosen.
Omit this task if the existing ArcIMS implementation meets
user needs (however, ESRI support for ArcIMS will
decrease as ArcServer support increases).
3
Update to new
Convert/update existing Flood DSS Viewer software to use
14 to 30 days
document management
new document management system, to replace Content
system.
Manager features.
4
Automate Flood
Implement data management and automated updates of
14 to 30 days
Outlook Data
Flood Outlook products from HDR (assuming that the
Management/
CWCB will fund such products in 2007). Data
Processing
management will include determining a standard format
and naming convention for data products, and procedures
describing data processing. QC of products will need to be
considered.
5
Update SNODAS Data
Implement data management and automated updates of
14 to 30 days
Management/
SNODAS products. Data management will include
Processing
determining a standard format and naming convention for
data products, and procedures describing data processing.
QC of products will need to be considered.
6
Update SNOTEL Data
Implement data management and automated updates of
14 to 30 days
Management/Processing
SNOTEL products. Data management will include
determining a standard format and naming convention for
data products, and procedures describing data processing.
QC of products will need to be considered.
7
Enable Link to Real-
Implement tools to query and display current streamflow
14 to 30 days
time CDSS Flow Data
conditions (e.g., as percent of historical average). This
layer will provide a current indication of flood threat based
on streamflow. Flow graphs will be accessible using the
hyperlinks to DWR's web site.
8
Enable Link to Satellite
In addition to displaying current streamflow conditions,
14 to 30 days
Monitoring System
locations where flows are exceeding pre- defined thresholds
Alert System
could be indicated on the map. Flow graphs will be
accessible using the h perlinks to DWR's web site.
9
Add Links to Additional
Agencies like NOAA continue to update their web sites to
3 days minimum,
Web Sites
provide useful data products. The full -scale Flood DSS
possibly much more
should at a minimum consider adding links to other useful
if using external web
sites (e.g., federal agencies or perhaps county sites devoted
or map services
to flood information). Some agencies may also offer we
or map services to allow data to be utilized in core features
of the Flood DSS (e.g., streamflow forecast data could be
utilized in addition to observations).
15