Home > WebEOC > Admin Guide > Getting Started > An Overview of WebEOC

An Overview of WebEOC

WebEOC® Professional is Crisis Information Management Software (CIMS) developed over a decade ago to meet the needs of emergency management agencies (EMAs) at the federal, state, and local levels.

Today, WebEOC is used by government agencies such as the U.S. Departments of Agriculture, Defense, Energy, Homeland Security (CDP, FEMA, ICE, TSA, and USCG), Health and Human Services, EPA, and NASA. It is also used by corporations, public utilities, universities, and more.

Although WebEOC and its product suite provide specialized tools for managing crisis information and emergency response, WebEOC can also be used to manage any and all events, agencies, organizations, and more.

WebEOC includes a default set of boards and plugins that enable any agency to begin using it almost immediately. Agencies can use any or all of the boards as-is, or they can build an unlimited number of boards and forms tailored to local requirements. Within the context of WebEOC, a board is an electronic display that allows you to transmit and share information in real-time with other WebEOC users. WebEOC boards are the equivalent of large, chronological, or topical paper-based boards that, for years, dominated every EOC and command center around the world.

Background

WebEOC was one of the first web-enabled, commercial-off-the-shelf CIMS systems developed for emergency management. As a web-based product, WebEOC ushered in the era of “virtual” EOCs, making it possible to monitor and manage an emergency response from anywhere in the world. With WebEOC, crisis information is immediately and universally available to authorized users everywhere. It can be configured based on local requirements, and it gives agencies and organizations the ability to link to a wide assortment of different systems.

WebEOC can be used during the planning, mitigation, response, and recovery phases of any emergency. It can also be used by agencies and organizations during day-to-day activities to manage routine, nonemergency operations.

WebEOC’s design is based on the following tenets of emergency information management systems. CIMS should:

  • Be affordable.

  • Be user-friendly.

  • Be easy to maintain by existing EMA staff with access to the vendor’s technical support.

  • Be easy to configure and tailor to the conditions of the agency.

  • Allow for remote access by authorized users located outside the local area network (LAN).

  • Comply with the provisions for the National Incident Management System (NIMS).

  • Comply with the provisions for the Incident Command System (ICS).

  • Support users who implement both the ICS and Emergency Support Functions (ESF) structure.

  • Integrate with other systems, such as mapping, and other CIMS and telephonic alert notification systems.

  • Integrate public health into emergency management.

  • Operate within a variety of network configurations.

  • Have a wide range of features consistent with the four phases of emergency management.

  • Have help desk support on a 24-hour basis.

As a tool, WebEOC can be configured locally and tailored to almost any process. The default status boards that come with WebEOC are summarized and detailed in the WebEOC User Guide section. These status boards can be implemented as-is or they can be modified locally. Status boards can also be built using standard tools within WebEOC or external HTML editors.

Audience 

The articles in the Admin Guide section are written for WebEOC administrators and not intended for the average user. WebEOC users without any administrative privileges should refer to the WebEOC User Guide section

Time Conventions

WebEOC stamps all entries with a time and date. It also tracks and displays who entered the information.

Entries appear in status boards in the order in which they are entered into the system. For example, a telephonic report is received at 10:00 p.m., and it is entered into WebEOC at 10:01 p.m. The system time is 10:01 p.m.

Agencies can determine whether to show system times as part of the displayed entry. During setup, administrators can add additional time fields to status boards that can be user-modified; these times could represent a time the incident occurred, actual time of receipt, and so forth. These additional time fields, if used, are separate from the unalterable system time. Normally, agencies enter a time of receipt and time of occurrence in the narrative description.

You must to post a comment.
Last modified

Tags

Classifications

This page has no classifications.