Live pages

The live pages: what is in the building at this moment, and what has just gone wrong.

These pages read live data and are current to within seconds. Reports read summary tables that are rebuilt every five minutes, so a report and a live page can differ for the most recent minutes; both are correct. The ingestion diagram shows the two paths.

NOTE

Most pages in this chapter require a permission. A user who cannot see a page lacks that permission in their role. Roles are edited under System > Roles; see Administration.

Dashboard

Menu path: Choose Dashboard (/admin/dashboard).

The landing page: headline counts for the organisation, recent activity, and the tiles chosen to keep.

Application scenario: A quick check that nothing needs attention, before a specific page is opened.

Prerequisites: Gateways online, or every tile is zero. Two tiles are easy to misread — Entry / Exit Today counts crossings, not people inside, and Visitors Today counts devices, not people. The System dashboard is shared: only admins whose role has Manage General Config can rearrange or reset it, and a change is seen by everyone. Set as My Default chooses the dashboard that opens first for the signed-in administrator only.

Related documents: The dashboard, tile by tile

Monitor

Live Monitor

Menu path: Choose Monitor > Live Monitor (/admin/monitor).

Every gateway and every device, live: which are online, stale or offline, what each gateway hears, and where each device has been placed. Five tabs: Gateways (with the predictive health strip, which warns before a gateway fails), Sensors, Floor Plan, Rules (today by rule, and anything that did not go through) and Temperature (each sensor now, with today's low and high). The longer history is on its own reports: Environment for temperature, Enter/Exit, and Sensor Trail for one device over time; old links to those tabs open them.

Application scenario: Checking the hardware behind a strange answer: whether the gateway in that room is online, what a tag's signal looks like, and — through a device's Why here? button — why Omaya has placed it where it has.

Prerequisites: Gateways registered and reporting. Devices appear as soon as a gateway hears them; the Floor Plan tab needs a plan uploaded for the venue.

Related documents: A tag shows in the wrong room

Right Now & Live Alerts

Menu path: Choose Monitor > Right Now & Live Alerts (/admin/monitoring/right-now).

Every zone with how many are in it now, how full it is against its capacity (Empty, Normal, Busy, At or Over capacity) and the trend against the window before, with the live alert feed beside it. Click a zone for who is in it, its last 24 hours, its forecast for the next 24, and a comparison with another zone.

Application scenario: The page to leave open on a wall screen. It answers "which zones have someone in them, how full are they, is that more or less than a moment ago, and what has just fired" without a date picker.

Prerequisites: Zones drawn, and something in them that counts — a radar, a counting sensor, or tags on the people to be counted. A zone with none of those reports nothing. The page needs the View Monitor (overall) permission; the live alert feed and the Alerts (last hour) tile also need View Anomalies, and a role without it gets the zones and no alerts.

Related documents: Occupancy: which number is which

Entity Tracker

Menu path: Choose Monitor > Entity Tracker (/admin/monitor/entity).

Every tracked person and asset on one page: where each one is now and for how long, on-site first and offline below. Click one for its detail and a five-day Timeline, zone by zone; play a whole day back on the floor plan with Movement Replay.

Application scenario: Answering "where is this forklift?" or "was this contractor in the plant room?" — the single-subject view, as opposed to the whole-floor view of the Live Monitor.

Prerequisites: An entity with a tag assigned to it. Without that there is only a MAC address and no name to search for.

Related documents: Watching people and assets

Outside

Menu path: Choose Monitor > Outside (/admin/monitor/outside).

Everyone outside the organisation's buildings right now, on one street map, from GPS trackers and phones running Omaya Scout. Tiles count who is Outside now, On the move, Stopped, At a geofence and Not heard 15+ min; click one to list only them. Each row says where they are (the geofence, a stop with the nearest place, or travelling), how long they have been out, their distance and time outside today, how old the last position is, and whether a tracker or a Scout phone placed it. Click a row for their route today. Someone stopped where they spend the night shows as At home, never where. People who came back in within the hour are listed underneath.

Application scenario: Answering "who is out right now, and where?" — field staff on client visits, a driver between sites, a guard on patrol — without opening each person. Filter by label, or by the field-staff label when one is set on Reports > Attendance. Details opens the person on the Entity Tracker and Replay plays today back on GPS Replay.

Prerequisites: Tags that report GPS: a GPS tracker, or a tag carried by someone whose phone runs Omaya Scout. The page appears in the menu once the organisation has GPS positions from the last 30 days, and needs View Monitor (overall) (view-monitor).

Related documents: Indoor and outdoor tracking

Scout (phones)

Menu path: Choose Monitor > Scout (phones) (/admin/monitor/scout).

Outdoor coverage per tag holder: whether each person or asset with a tag has a phone of their own, running Omaya Scout, that keeps their tag working outside the organisation's sites where no gateway hears it. Only holders whose tag a Scout phone has heard in the last 30 days are listed, each Outside now, Covered, Phone gone quiet or Seen at a site only; the rest are one count. The map shows where covered holders were last outside, and clicking one draws their trail.

Application scenario: Rolling Scout out: work down No phone yet and ask those people to install the app, and check Phones gone quiet when someone's coverage stops. "Their phone" is worked out over the last 30 days as the phone that places their tag away from the organisation's sites; at a site every phone hears every tag nearby, so a phone heard there carries nobody. A site is a geofence, or within 300 m of a location's pin.

Prerequisites: Omaya Scout switched on for the organisation, tags bound to people or assets on the Entity page, and the app on each holder's phone. Person tags count only where the Omaya contact has published them to Scout.

Related documents: Phones as trackers: Omaya Scout

Anomalies

Menu path: Choose Monitor > Anomalies (/admin/manage/device/anomalies).

Devices that have gone silent, are heard in far fewer hours than they usually are, or are draining their battery faster than a cell should: four findings, each with its threshold on the page.

Application scenario: The maintenance queue. Work down it and the rest of the platform stays honest, because almost every "the numbers look wrong" question upstream starts with a device that went quiet. A silent device closes its own finding as recovered when it is heard again. Acknowledging and clearing need manage-devices (shown in the role editor as Bulk Import Devices); everyone else can read the list, without the tick boxes or the Acknowledge selected bar.

Prerequisites: Silence needs only the device's own threshold; "heard less" needs three reporting days in the last month, and is not scored for tags, which are legitimately off site; battery drain needs a fortnight of levels. Tags are given a three-day silence threshold, because a tag that is genuinely not moving is not a fault. With the Facility app switched on, a silent or misbehaving device also opens a work order, unless that source is unticked under Work orders opened automatically in the Facility app's settings.

Smart checks

Menu path: Choose Monitor > Smart checks (/admin/monitor/smart-checks).

The catalogue of every check Omaya runs on the organisation's data, grouped as People safety, Devices and network, Spaces, Energy and plant, Work and compliance and Outdoors, with what each check watches and what it found in the last 30 days. Checks that belong to an app that is not enabled are not counted.

Application scenario: To see in one place what Omaya is watching and which checks have findings, and to switch a check off or on where it has a setting. Findings themselves are shown on each check's own page and in Central Alerts. The Weekly digest card replaces alerts with one email listing every check and its findings: Email me every Monday creates it (Monday 08:00, PDF, to the signed-in administrator), and Choose recipients and time or Manage opens System > Schedule Report.

Prerequisites: The view-monitor permission to open the page. Switching a check needs manage-settings-general; creating the digest needs manage-report-subscriptions. Nothing is emailed until the digest is set up.

Central Alerts

Menu path: Choose Monitor > Central Alerts (/admin/report/alerts).

Every alert the platform raises, from every module, in one feed: rule triggers and panic emergencies, anomalies, battery, button presses, gateway outages and positioning coverage, connector failures and failed webhook deliveries, Toilet Hygiene and Security Watch incidents, Data Centre and Warehouse alerts, rooms over capacity, OAIA findings, compliance findings, radar reflections and maintenance requests past their SLA.

Application scenario: It opens on Needs a look: what is still open, or was raised in the last 24 hours with nothing to close it. The counts at the top (Needs a look, Critical, Repeating, Done) and a bar per day open their part of the list. The same alert raised three times or more from the same place folds into one row, ×N since when, with why it usually repeats and where to change it (a rule that fires on every crossing: raise its repeat at most every). Each row links to where it is handled; anomalies and battery alerts can be acknowledged here, singly, a repeat at a time, or everything shown. Search, a device, a date range and a chip per source narrow it; Export gives what is shown as CSV.

Prerequisites: Alerts depend on rules existing and sensors reporting, so an empty feed can mean nothing is wrong or that nothing is watching. It is worth knowing which. A rule whose only actions are email, SMS or a webhook leaves no row here, only its own "last fired" time. Connector failures are also kept, as system events, in the Activity Log.

OAIA

Menu path: Choose OAIA (/admin/oaia).

The Omaya AI assistant: a periodic written briefing on what changed, plus a place to ask questions of the organisation's data in plain language.

Application scenario: Instead of reading six reports to find the one thing that moved. It writes only when something has actually changed, so a quiet day produces a short note.

Prerequisites: Nothing, to start: the detectors run and notify with or without an AI provider. A key for the organisation adds the prose and the chat. The interval is set by the organisation: 2, 4, 6, 8, 12 or 24 hours.

Related documents: OAIA — the AI assistant

NOTE

This chapter is generated from the admin menu itself, so it lists every menu item.