Laserfiche WebLink
16 <br />ESTIMATED <br />EFFORT <br /># <br />TASK/FEATURE <br />DESCRIPTION <br />(STATEWIDE <br />SYSTEM) <br />10 <br />Implement protected <br />Some Flood DSS data layers should not be viewable to the <br />2+ days <br />and public versions of <br />public. The needs assessment will identify layers and <br />Depends on <br />the Flood DSS web site. <br />features that should only be available to CWCB staff. <br />approach <br />Implementation of a suitable solution may involve <br />duplicating the site (with minor layer differences) or <br />developing a single site with login capabilities to turn on all <br />data/features. Note that this task is for the full -scale Flood <br />DSS, whereas Task 1 is for the prototype Flood DSS. <br />1 I <br />Evaluate Overall Data <br />The prototype Flood DSS included a few statewide layers <br />5 days <br />Presentation <br />but focused on Larimer County. The full -scale Flood DSS <br />will present county-based data for the entire state. An <br />evaluation of organization within the ArcIMS interface <br />must occur to determine whether layers should be listed as <br />statewide or by county. The results of this evaluation <br />should be considered in data processing tasks. <br />12 <br />Flood DSS <br />Documentation for the full -scale Flood DSS should be <br />14 days <br />Do cumentation <br />created for users and developers. <br />13 <br />Flood DSS Training <br />Training materials for the full -scale Flood DSS should be <br />7 days <br />Materials <br />created to allow self-paced training by web site users. <br />14 <br />Flood DSS Training <br />On -site training using the training materials and Flood DSS <br />1 day each location <br />Sessions <br />web site. <br />15 <br />Flood DSS Support <br />Troubleshooting, support, and minor enhancements of the <br />At an acceptable <br />system. <br />level (e.g., 2 <br />days /month). <br />16 <br />