Abstract
ABSTRACT Over the years, many organizations have attempted to automate the Incident Command System (ICS). These attempts have ranged from computerizing T-cards to a nationwide spill operations system. Over time, these systems have had varying degrees of success. While certain inherent reasons exist for not automating ICS, they are outweighed by the tremendous potential of successful automation. The need to produce documentation, the integration of ICS sections, and the rapid change of information all lend themselves to automation. Successful ICS automation does not start with computerizing ICS forms. The hey to automating ICS is to automate both ICS and response processes. In a response effort, many separate and distinct processes occur daily. The requisitioning of resources, the planning and application of the response organization, cost accounting, and the development of an Incident Action Plan (IAP) occur many times during an incident. This paper describes a framework for automating and integrating these processes. This framework offers organizations a road map for successful ICS automation. The poster presentation includes a software demonstration that illustrates the benefits of integrated automation.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
