Laserfiche WebLink
<br />ooons <br /> <br />~ - -., I <br /> <br />1.,' <br /> <br />III. Constraints on a Flash Flood Warning System - Planni~g Implications <br /> <br />A.Time -"the Warning DileJlUDa" <br />timeliness v. accuracy <br />detection lead time v. warning response time <br /> <br />IMPLICATIONS: <br />Phased mobil ization during detection, process <br />Commitment of Public' Safety system to' detection and <br />warning process <br />Acceptance of repeated prel iminary mobil ization " <br /> <br />B. Institutions, Policy, and Responsibilities <br />Who makes the warning decision? <br />Where are the decisions made? <br />Who else needs to know? be involved? approve?' <br />What about neighboring (affected) jurisdictions? <br /> <br />IMPLICATIONS: , <br />System must be configured to support the decision maker <br />--"non-technical" outputs may be needed <br />--ability to identify the "bottom line" <br /> <br />System must provide information, where and to whom needed <br />--compatible with current public safety operations <br />--new organization should build on existing lines <br />oJ res pons I bil ity , <br /> <br />A System planning approach is needed <br />-.to integrate multiple disciplines: <br />public safety <br />emergency 'management <br />hydrology and flood control <br />pUblic works and utilities <br />--to integrate multiple Jutisdjcit,iolJs'in'v.ohed <br />municipalities <br />counties, <br />COG's, Regional districts <br />State, DODES <br />Federal, FEMA <br /> <br />C. Infrequent Recurrence of Major Floods <br /> <br />Loss of trained personnel <br />Loss of interest due to'inactivity <br />Failure to maintain system in full readiness <br /> <br />IMPLICATIONS: <br />System should have day to day value and visibility <br />--provide information that would be missed <br /> <br />System should be designed as a critical application <br />