Laserfiche WebLink
3.3.4 Implement Link to Real -time CDSS Flow Data <br />The prototype Flood DSS included a snapshot of current flow conditions, using real -time and historical <br />data from HydroBase. The full -scale Flood DSS should include features to automatically process current <br />(or suitably recent) flow data to create current data products (e.g., update products every hour). <br />Procedures to develop the products should be documented to allow for additional enhancements and <br />maintenance of the system. For example, a similar product is produced by the USGS (United States <br />Geological Survey), and the USGS web site includes a description of the procedure. Links to real -time <br />streamflow data (e.g., the State's web site) should be enabled to allow users to evaluate changing <br />conditions. <br />3.3.5 Implement Link to Satellite Monitoring System Alert System <br />The prototype Flood DSS did not include a link to the Satellite Monitoring System Alert System. This <br />system has been developed by DWR to analyze flow data for change in rate and threshold conditions, <br />with a capability to notify users when critical conditions occur. Experience with this system as part of the <br />Instream Flow DSS and other similar systems has shown that a map -based interface that indicates current <br />alarm conditions can be an effective tool to summarize system conditions. A basic level of <br />implementation involves querying the Alert System database and displaying suitable symbols to indicate <br />alarm conditions. A more advanced implementation may involve coordinating system enhancements with <br />DWR or developing new capabilities within the Flood DSS (e.g., to issue alarms only when flow rate of <br />change and flow are both above critical levels). Alert features may only be suitable for internal use. <br />3.3.6 Add Links to Additional Web Sites <br />The prototype Flood DSS implemented limited links to external web sites. Feedback from the CWCB <br />was that this capability was not critical. However, further evaluation of user needs may indicate that <br />useful external data should be made available from the Flood DSS web site. Links to additional sites <br />should therefore be evaluated during implementation of the full -scale Flood DSS. <br />3.3.7 Implement Internal and Public Versions of Flood DSS Web Site <br />The prototype Flood DSS includes some sensitive information that may not be suitable for a public web <br />site. The full -scale Flood DSS may include additional sensitive information (e.g., current Alert System <br />warnings). The needs assessment should identify if both internal and external versions of the site are <br />needed and an appropriate system design should be developed. The eventual solution may utilize two <br />web sites, or a single site that requires a login for extended features. <br />3.4 Level of Effort Estimates for Full -scale Flood DSS Implementation <br />The previous sections provided background for significant tasks recommended to implement a full -scale <br />Flood DSS. The following tables summarize estimates for the level of effort necessary for specific <br />activities. These estimates have been made based on experience gained in the prototype Flood DSS and <br />other DSS projects. However, the actual effort that is required will vary, based on additional information <br />that is gained during full implementation. It is recommended that the needs analysis be performed first <br />(see Table 2, item 1) in order to fully understand requirements for the full system. This analysis may <br />indicate that some data layers are more important than others, or that certain areas within the state are <br />more critical. The analysis may also indicate that additional software /system features are required. <br />Consequently, resources can be devoted to high - priority tasks that have a large return on investment. <br />12 <br />