# Operations ## 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](https://docs.cw.crisisworks.com/concepts-and-fundamentals/concepts-and-fundamentals#events-users-positions-and-duty) and what users with them can do according to their default [security policies](https://docs.cw.crisisworks.com/system-administration/configuring-the-system/positions#security-policies):

Position	Description	Examples
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.

Position

Description

Examples

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](https://docs.cw.crisisworks.com/system-administration/configuring-the-system/positions) can establish positions with [custom security policies](#security-policies). {% if visitor.claims.platform.cw === true && visitor.claims.topics.councilVic === true %} For Victorian councils, refer to: [Positions Access Summary](https://docs.cw.crisisworks.com/security-and-support/practice-notes/playbooks-crisisworks-better-practice-guides/positions-access-summary). {% endif %} ### Access Access to the module and certain registers is limited to positions working in operations. To access *Operations:* 1. [Sign in](https://docs.cw.crisisworks.com/concepts-and-fundamentals/on-a-computer/getting-access#signing-in) with an [Operations position](#information-editinganexistinginformationitem) 2. In the [Modules Menu](https://docs.cw.crisisworks.com/concepts-and-fundamentals/on-a-computer/navigation#modules-menu) select *Operations* {% hint style="info" %} If your account doesn't have access to this module and you need to use it, contact your [System Administrator](https://docs.cw.crisisworks.com/system-administration/configuring-the-system). Your administrator will need to have [setup and configured](#finding) the module in such a way that you can access it. {% endhint %}

View of the Operations module showing the main register: Requests

### Setup and Configuration Administrators can configure [Operations positions](#positions) to control access to parts of the Operations module. Additionally [security policies](#security-policies) can be set per register. #### Security Policies Refer to: [Positions: Security Policies](https://docs.cw.crisisworks.com/system-administration/configuring-the-system/positions#security-policies)

Security Policy explanations

The following security policies apply to Operations:

Security Policy	Use
Operations Admin	Access items in participating events, can update all but not assign or move.
Operations Coordination	Full read/write access to operations data within involved events, with the ability to manage assignments and moving records between events.
Operations Limited	Limited read/write access to operations registers for assigned items. Cannot assign or move.
Operations Officer	Can create items. Can edit all Operations registers for records assigned to them or they have created. Cannot assign or close.
Operations Read Only	Can view all operations items in participating events but cannot update.
Operations Read Only Assigned	Limited read-only access to operations records within involved events only where the data is assigned or shared.
Operations Resource Assignment	Can assign resources within the request form

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

Register	Sub-register of	Uses
Requests		For actionable tasks that require coordination and resources Requests is the default Operations register
Request Tasks	Requests	For managing individual tasks related to a request
Information		For recording information that is disseminated to team/s including Situation Reports, Briefings and Incident Action Plans
Logs		For recording observations, intentions, actions and decisions
Contacts		A directory of key contacts which can also be users
Permits		For processing compliance applications
Resources		For managing cost tracking, recovery and allocation of resources

## Reports {% content-ref url="../system-administration/reporting/running-reports" %} [running-reports](https://docs.cw.crisisworks.com/system-administration/reporting/running-reports) {% endcontent-ref %} See [Operations Reports](https://docs.cw.crisisworks.com/modules/reports/operations-reports) for the reports available for Operations data.