My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Flood DSS Prototype Scope
CWCB
>
Decision Support Systems
>
DayForward
>
Flood DSS Prototype Scope
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/17/2013 10:19:44 AM
Creation date
10/27/2010 11:03:22 AM
Metadata
Fields
Template:
Decision Support Systems
Title
Prototype FloodDSS Project Scope of Work
Description
Project Scope of work
Decision Support - Doc Type
Scope of Work
Date
6/30/2006
DSS
Flood
Basin
Statewide
Prepared By
Riverside
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
6
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Exibit A <br />Scope of Services <br />The following is the scope of work for the Flood DSS prototype. The objectives of this <br />scope of work are: <br />• Implement a Flood DSS web site prototype to organize and disseminate spatial <br />data, via an ArcIMS web site on a State web server. <br />• Provide links to selected non - spatial data, to demonstrate functionality at a <br />prototype level. <br />The prototype will allow CWCB Flood Protection staff to evaluate implementation of a <br />full scale Flood DSS. <br />The following tasks will be completed. Each task indicates deliverables, many of which <br />are working products. The main deliverable is the prototype Flood DSS web site <br />installed on a State web server. <br />1. Project Kickoff. A kickoff meeting should be held at the CWCB offices, attended by key <br />team members, to achieve the following: <br />• Restate the goals of the prototype and vision for a full system, the intended users, and the <br />products to be made available. For example, limiting the prototype to CWCB use (not <br />extensive public use) may allow additional draft quality data to be added to the site, at the <br />expense of other activities. Quality controlling all aspects of the project for public <br />consumption requires more effort. <br />• Define key requirements of the system, which can later be measured to evaluate project <br />success. <br />• Define the working relationship between RTi and the CWCB, including identifying <br />contacts. <br />• Determine initial action items, including data inventory and collection (see below) and <br />support activities for the State (e.g., verifying State web site capabilities). As much as <br />possible, determine priorities for activities, so that early versions of the site meet as many <br />goals, and allow as much feedback, as possible. <br />• Discuss the approach, in particular milestones to allow State review of products. <br />Although the State will be able to view the work in progress at RTi using a web browser, <br />it is recommended that one or more meetings occur at the CWCB to review products <br />before the final delivery. <br />Deliverable RTi will document in a memo the points of discussion and decisions that are <br />reached in the kickoff meeting. The memo will be provided to the State as part of normal <br />correspondence and project management. <br />2. Data Inventory. The data inventory is a list of all data to be included in the Flood DSS <br />system. This inventory can be discussed in the kickoff and follow up correspondence. The <br />primary activity is to identify data types, their sources, and relevance to the project. The As- <br />Needed Engineering Services notice provided a list of data layers, shown in the following <br />table. Data layers are typically grouped into categories to help users find information. An <br />
The URL can be used to link to this page
Your browser does not support the video tag.