Halo Terminology Guide

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

A

Activity - An activity is a manual entry made to the activity feed. You cannot update it or add any images to it. It is simply for recording key activities on any given time or date. It has no lifecycle. 

As a reminder, the Halo System processes data capture in 3 ways; Incidents (re-active data capture via form), Activities (stand-alone data capture) and Tasks (pro-active data capture). See form.

Activity Feed - The activity feed can be found within each Log's dashboard and automatically captures key activities that happen within that Log. Including things like user log-ins to incident & task updates, to mass notifications and document library uploads, all in real-time. 

Manual entries can also be added so key actions are recorded.

Admin Users can download a time-stamped report of the activity feed at any point during or after the Log has ended.

Analytics - This is in the side menu of the Log and allows for incident data to be searched and filtered by a range of options and factors to provide the desired insights. Data can be exported to CSV.

B

-

C

Control Room (UK + EU) or Control Center (US) - A control room, or control center, is a central space that monitors and controls security systems, processes and response. Control Room personnel will typically have Halo Admin permissions, or Halo App & Dashboard permissions. Find out more about access & permissions.

Customisation - This is an area of the HaloHub which allows for new incident types and forms to be created and key parts of the System to be re-labelled. 

D

Dashboard - A 'dashboard' refers to the overview screen that Admins, App & Dashboard Users and Team Leaders can see for each Log. It is where the control personnel have complete oversight of the location, displaying real-time incident, task, activity updates and the geo-location of all consenting app users.

E

Event - We refer to events within the Halo System as planned instances or occasions with a known start and end date, such as a festival or concert. However, some of our customers will use the terms 'event' and 'log' interchangeably. See: Log 

F

Forms - Forms are created in the HaloHub by Admin users to enable re-active and bespoke data capture for incidents or issues. To give incidents or issues a different name, see 'Customisation' and 'Key Labels'

As a reminder, the Halo System processes data capture in 3 ways; Incidents (re-active data capture via form), Activities (stand-alone data capture) and Tasks (pro-active data capture). 

G

Global Security Operations Centre - See 'Control Room' 

H

HaloHub - This is the part of the system that only Admin Users have access to for the creation of Logs, People and Customisations. 

I

Incident/Issue - An incident or issue is anything you want your workforce to actively report against. 

In the Halo System they have a lifecycle of 5 stages; Created, shared, managed/updated, resolved and closed & de-briefed. 

As a reminder, the Halo System processes data capture in 3 ways; Incidents (re-active data capture via form), Activities (stand-alone data capture) and Tasks (pro-active data capture). See form.

Incident Form Analysis - This can be found in the top section of the report and allows for micro-trend analysis of different incident categories and sections. 

J

Joint Operations Centre - See 'Control Room' 

K

L

Location - Because of the wide variety of places the Halo System can protect, including facilities, campuses, venues, arenas, festivals, train stations and more, we use the term 'location' as a catch all in reference to the area you intend to deploy the Halo System. 

Log [noun] - Within the Halo System, a 'Log' refers to the individual instances Admin Users set-up within the HaloHub. For some of our customers, such as yearly festivals, this means they create a single Log for each event they host, which may be called, for example, 'Glastonbury Event Log 2023'. However, for other customers, such as universities and train stations, who use the Halo System for their entire venue operations, they may create a 'daily operations log' which lasts the whole year and has recurring tasks. Other customers, such as arenas and sports stadiums, may use a mixture of Logs to manage their year-round operations and individual events, including, for example; 'health & safety log', 'medical log', 'daytime log', 'evening log' and more...

Admin Users can create, manage and compare individual Log reports, and use our new multi-dashboard mode to monitor multiple logs from one dashboard.

Log [Verb] - Of course, you may also see and use the word 'log' as a verb, meaning to enter [an incident, note or document] in the Halo System.

M

MAL Users - See 'Users'

Main Operations Centre - See 'Control Room' 

N

O

Operations Centre - See 'Control Room'

P

People - Only 2 types of industries have 'Users'; the drugs industry and the software industry. So we think it's nice to call them 'people!'

Q

R

Report - Report refers to the main document which shows all incident, task, activity feed data. This includes incident form analysis.

S

Security Operations Centre - See 'Control Room' 

T

Task - Tasks are pre-set, pro-active things to do at certain times, dates or locations. They can contain images and instructions. In the Halo System they have a lifecycle of 5 stages; Created, assigned, managed/updated, resolved and closed. It is possible to mark a task as 'unable to complete'. Upon completion, a task will display whether it was completed on time or late.

As a reminder, the Halo System processes data capture in 3 ways; Incidents (re-active data capture via form), Activities (stand-alone data capture) and Tasks (pro-active data capture). See form.

Teams/Third Party Users - See 'Users'

U

Users - There are 4 different User Types. These are explained in detail here.

V

Venue - A venue is a fixed location where the Halo System is/will be deployed. 

W

X

Y

Z

Zone Ex - Zone Ex is a term used within the events industry. It refers to the zone immediately outside of an event or arena, where people may gather, either as they arrive to or depart from the event/venue. Monitoring and managing 'Zone Ex' is considered a crucial part of Organisers' crowd safety management plans and whilst there is no universally agreed definition of the end point or boundary, the most practical one we have seen ranges from the zone immediately outside to the first point of dispersal, ie taxi rank, bus or train station. This of course requires stakeholder consultation as the land may belong to a third party, in which case, this definition becomes less practical. Other sources of reference, such as the purple or green guide, should provide further clarity.