This glossary describes words and acronyms used frequently in WebEOC and WebEOC help documentation. Words are defined in general and then, where appropriate, described in relation to WebEOC.

A

Admin Profile

Set of administrative functions and permissions that can be assigned to users. Users can perform only those administrative tasks defined in the profile.

Agency Template

Default template that contains your agency's name, logo, font, and color scheme. The agency template can also be used to configure login policy statements and messages that appear to users when they log in to WebEOC.

Archive

Data from an incident that has ended. Administrators can retrieve and view archived board/plugin data and query for data. An archive can be turned into a simulation.

Audit Log

Tracks and records administrative events that occur in WebEOC. The log supports monitoring and assessment of administrator/user activities and can aid in troubleshooting.

B

Board

Customizable system component designed to transmit and share incident information between system users in real-time. Boards are also referred to as status boards.

C

Checklist

Automated procedures and lists of steps used to track the progress of tasks. Administrators can indicate when a task is due.

CIMS

Crisis Information Management System

Control Panel

Window that contains all of the features and functions to which the logged in user has access. These can include boards, menus, tools, plugins, links, and more.

D

Data Link

Enables posting of the same data to multiple status boards at once. One- and two-way linking are supported.

Display View

Configuration of how a board displays data to users. Administrators can design and configure display views.

Dual Commit

Means of setting up servers so that they can communicate and share information across and among agencies that use WebEOC. Users with access to shared boards can view and post information from within WebEOC.

E

ETime

Amount of time necessary to complete a step or task in a checklist. Configuring an ETime sets when the task is due to be completed. For both actual incidents and simulations, the ETime is calculated from the start of the incident or simulation. For an actual incident, if the task has not been marked as Completed or Not Applicable when the ETime is reached, the status appears in red to indicate it is past due. For a simulation, when the ETime is reached, the task is automatically posted to the simulation's status board.

F

File Library

Means by which WebEOC users can upload and share files and documents with other WebEOC users.

G

Group

Set of privileges that grants board, plugin, link, and menu access to the users assigned to the group. A user's group governs the tools and functions available to them in their control panel. The group profile can also grant other user permissions, including read and write privileges. Groups are generally based on user roles and positions assigned during an incident or on information the users require during an incident. 

H

HTML

Hypertext Markup Language. In WebEOC, an experienced administrator can use HTML code to build and maintain boards.

I

ICS

Incident Command System

Incident

Any unplanned or planned event, emergency, or other occurrence that requires a response.

Input View

Space in a board where the user can enter new data or update existing information. Administrators can design these data entry views.

L

List

Related items presented to users as options from which they can select when updating a field on boards and forms. A list can also be used as a filter on a status board. A multi-tiered list contains two or more levels of sublists.

List View

Set or subset of data for a board that allows the user to view only the data that is immediately necessary. List views can be used to create a high-level view of a particular area or subject.

M

MapTac

Plugin used to publish image files, including maps and dispersion models. Administrators can place markers, labels, and shapes on the map or image. These elements on the map can be used to brief members of the response team and other users on aspects of the incident.

Master View

Option to track multiple incidents simultaneously; selected incidents are "rolled up" into the master view.

Menu

Group of boards, plugins, and links appearing in the control panel as a single link; clicking the link opens the menu, providing access to each item in the list.

Message

Internal mechanism for transmitting incident or other information to users via the control panel and Messages tool.

P

PAC

Position Access Code; serves as a layer of password protection for a position. Administrators create PACs as a way of controlling the users who can register for a position.

Plugin

Set of features and functions that can be added to or enabled within your WebEOC system. Checklists, File Library, MapTac, and Messages are examples of standard plugins.

Position

Defines the user's role in the response organization. A single user can be assigned multiple positions. If assigned to more than one position, the user is prompted to select the appropriate position upon logging in to WebEOC.

R

Remote Board

Feature that allows users in one agency to access boards hosted by another agency for the purpose of sharing information across agencies. All WebEOC installations that use this feature view the same sets of data on the same boards.

Report

Means of retrieving and reporting on specific sets of data, such as an incident. WebEOC has preformatted reports but also offers ad hoc reporting capabilities.

S

Session

Period of time in which a user is logged in to WebEOC.

Simulation

Scenarios that can be added to WebEOC and run as needed for trainings, drills, and exercises. Simulations can be designed to simulate inputs that would occur during an actual incident while minimizing the number of support personnel needed to participate in the scenario.

U

User

Individual who has credentials to log in and use WebEOC. Some users are administrators or have a subset of administrative rights.

User, Group, Position, Incident

Each user must be assigned to at least one position. Each position must be assigned to at least one group. Each group must be assigned to at least one incident