Operations

This section outlines the Operations Module which contains registers for managing the Emergency Management Operations and Response phase.

Overview

The Operations Module contains registers for Emergency Management Operations and Response phase.

The module contains functions for recording staff logs, managing requests and tasks, information and operational resources as well as time sheeting and expense tracking.

Operations is designed to broadly align with the objectives and functions of incident management systems such as the Australasian Inter-Service Incident Management System (AIIMS) and Incident Command System (ICS). This makes it effective in an Emergency Operations Centre (EOC) for electronic management of emergencies of any size using an all agencies approach.

Positions

The following table outlines Operations positions and what users with them can do according to their default security policies:

Position
Description

Operations Officer

Supports operations.

Users on duty with this position can add and update items.

Operations Coordinator

Provides overall operations coordination.

Users on duty with this position can add and update events and operations items. They can update Operations costs and resources. They can assign, close and move items. They can also view reports.

Operations Support

Provides data entry support.

Users on duty with this position can view and update items assigned to them.

Other positions may have similar security policies. A System Administrator can establish positions with custom security policies.

Access

Access to the module and certain registers is limited to positions working in operations.

To access Operations:

  1. In the Modules Menu select Operations

If your account doesn't have access to this module and you need to use it, contact your System Administrator.

View of the Operations module showing the main register: Requests

Registers

Access to each of the listed registers is based on your system's configuration and license.

Register
Sub-register of
Uses

For actionable tasks that require coordination and resources Requests is the default Operations register

Requests

For managing individual tasks related to a request

For recording information that is disseminated to team/s including Situation Reports, Briefings and Incident Action Plans

For recording observations, intentions, actions and decisions

A directory of key contacts which can also be users

For processing compliance applications

For managing cost tracking, recovery and allocation of resources

For managing staff work times and expenses

Reports

Running Reports

There are around 8 Built-in Operations Reports which can be used to extract summary and detailed information.

Last updated