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

• * Note: Estimates are for collection of each data type individually. In most cases, several data types will
be held in one or both of the County Seat and primary municipality offices of the 64 counties in Colorado.
Collection of all required data simultaneously will reduce data collection costs considerably.
Table 2 — Flood DSS Software /System Tasks Level of Effort Estimates
#
TASK/FEATURE
DESCRIPTION
ESTIMATED
EFFORT
(STATEWIDE
SYSTEM)
TOTAL
Evaluate full -scale
#
TASK/
DATA
INVENTORY/
PROCESSING
ESTIMATED
COMMENTS
TYPE
COLLECTION
EFFORT
describes needed functionality and rationale for including
(STATEWIDE)
7
SNODAS,
I day /state
See Table 2.
See Table 2
See Table 2. Inventory is needed
functionality.
Flood
The existing prototype must be updated to allow public
to confirm current availability of
Outlook,
viewing of the site without making sensitive data available.
data from various sources.
SNOTEL,
Real -time
flow
8
Verify
4 hrs/ county
32 days
Need to confirm links for
scanned
community and other data in
document
spatial data and scanned document
link.
system (e.g., "Fort Collins" vs. "Ft
Collins "). This may be a CWCB
task.
9
CRS
2 days
2 days
4 days
Effort should be minimal — update
of existing data with CWCB
assistance.
Task may be required to be
repeated every 6 months.
10
Other Data
4 -8 his /county
6 -10
80 -144 days
User needs assessment may
hrs /county
identify additional categories and
sources of previously unidentified
data that should be incorporated
into the DSS.
• * Note: Estimates are for collection of each data type individually. In most cases, several data types will
be held in one or both of the County Seat and primary municipality offices of the 64 counties in Colorado.
Collection of all required data simultaneously will reduce data collection costs considerably.
Table 2 — Flood DSS Software /System Tasks Level of Effort Estimates
#
TASK/FEATURE
DESCRIPTION
ESTIMATED
EFFORT
(STATEWIDE
SYSTEM)
1
Evaluate full -scale
Evaluate Flood DSS user needs through review of
20 to 30 days
Flood DSS needs;
prototype Flood DSS, interaction with the CWCB, Flood
develop requirements.
Task Force, etc. Develop a requirements document that
describes needed functionality and rationale for including
the functionality. In particular, document whether the
prototype must be enhanced to include additional
functionality.
The existing prototype must be updated to allow public
viewing of the site without making sensitive data available.
14