Laserfiche WebLink
PROJECT APPROACH <br />' 4. Project Approach <br />The Riverside Team has developed a project approach that will deliver a comprehensive, fully <br />' functional, user-friendly Flood DSS at the end of Phase I. Riverside envisions producing a <br />system that contains the important data layers, and also synthesizes and summarizes the data for <br />ease of use by decision makers. Emphasis will be placed on the development of a DSS <br />' infrastructure that supports all of the data types in a manner designed for the different categories <br />of Flood. DSS users (i.e., developers, insurance industry, government agencies, public, Flood <br />. Task Force, and emergency managers). Data collection efforts will be planned to include as <br />much statewide data as possible, but areas most impacted by floods will be given the highest <br />priority. To the extent possible, the system will be designed to be extendable to .support <br />additional data types and categories of users that maybe addressed in Phase II. Potential Phase <br />' II activities are presented in Section 4.14. The Riverside approach to each task identified in the <br />RFP is described in the following sections. <br />4.1 Project Kickoff <br />Goals <br />' Hold a kickoff meeting at the CWCB offices, attended by key team members, to review project <br />scope and identify measures of project success. <br />Approach <br />The Riverside Team will: <br />• Review the Flood DSS prototype and recommendations from that effort. Because Riverside <br />' developed the prototype, the Riverside Team is well prepared to provide an overview of the <br />Flood DSS and to discuss the lessons learned in the process. The goals of the Flood DSS <br />will be restated based on this discussion. <br />• Lead a discussion of the extent and level of data collection effort. The Riverside Team will <br />present. an assessment of the overall data collection effort and recommend an approach that is <br />geared towards statewide collection, but focuses initial efforts on the most flood-prone areas. <br />' Data collection priorities will be discussed and established. <br />• Discuss mayor categories of users of the Flood DSS. These discussions will be used to <br />' identify the different -types of users of the system who will be contacted as part of the User <br />Needs Assessment. A summary of the DSS products will be reviewed and updated based on <br />feedback from the CWCB. <br />' • Identify portions of required data that are available from the CWCB. It has been estimated <br />that 75% of the data needed for the Flood DSS is available from the CWCB. The data <br />inventory developed as part of the prototype project will be presented and discussed. Based <br />on input from the CWCB, the estimate of the portion of data available from the CWCB will <br />be updated as appropriate. Plans will be discussed for obtaining these data. <br />• Determine if ArcIMS is still the appropriate platform for the Flood DSS. The Riverside <br />.Team will present. the plan for evaluating alternative technologies for the Flood DSS. The <br />plan will be revised based on input from the CWCB. <br />• Lead a discussion on the look and feel of the Flood DSS user interface. It is the intent of the <br />CWCB that the Flood DSS Map Viewer prototype "look and feel" be maintained in the <br />DNR RFP PDA-923 25 R ~ V E R S ~ ~ E <br />