The story is on the main page. This one is the full surface — what Omaya senses, what it works out from that, what it will tell you, and what it will do about it on its own. Written for the reader who wants to check a specific thing rather than be persuaded.
Omaya reads the signals your building already emits, plus whatever you choose to add. Nothing here requires an app on anyone's phone.
Anonymous by default; identified only where you deliberately bind a tag to a person or asset.
Conditions that decide whether a space is usable, comfortable and compliant.
The equipment already installed, brought into the same picture as everything else.
Signals arrive over Bluetooth, Wi-Fi, Matter and LoRaWAN, and over wired links where the equipment provides one. Device families are decoded individually rather than reduced to a lowest common denominator, so a counter reports counts and a meter reports consumption.
Raw signal is not an answer. Between the sensor and the report, Omaya resolves where something is, how long it stayed and what that means for the space.
Three methods, chosen per venue by what the site can actually support.
A device on a boundary should not flicker between two rooms all afternoon.
Derived measures, computed continuously rather than at report time.
Twenty-eight report types, each answering one question. Grouped here by the question rather than by where they sit in the menu.
Every report filters by location, venue, zone and date range, converts timestamps to the site's own timezone, and exports to CSV. Readings that could not be placed in a room are attributed to their venue rather than dropped, so a total never quietly loses rows.
A rule watches a measure, decides whether a condition holds, and acts. Fifteen measures can be watched, combined in a condition tree with and/or groups, time-of-day and day-of-week windows.
Rules can be tested against real history before you arm them, so you find out what a threshold would have done last month rather than next month. The assistant's daily review proposes rules too — you accept one and it opens pre-filled in the rule editor.
The assistant works from what the platform already knows — every zone, device, rule and reading of one organisation — and is built to explain and propose rather than to act on its own.
Switched on per organisation from the A.I Model card; off by default.
/compact and /new keep it cheapEach app you switch on plugs into the assistant; an app you have not switched on is never mentioned.
The only way the assistant ever changes anything without a person clicking Apply. Off by default.
Inside the Security Watch app, for the guard on duty.
The parts that let a customer's security team say yes.
Each of these is the sensing, the judgement, the person and the record from the sections above, joined up. None needs a script; all of them are in the product today.
Cleaning by traffic, not by clock — and the evidence writes itself.
A route on the real plan, across floors, on the visitor's phone.
Bookings check themselves in from real presence — or release.
Environment, security and facilities in one chain.
The assistant tells you what, why and what to do — you approve.
Habit is the permission — nobody maintains a list of who may enter where.
Occupancy drives the lights, the air-conditioning and the blinds through the smart-home bridge.
One press, the right people, a record of who came and when.
A head count from the badges already in the building, not a clipboard.
Ten kinds of place, one platform. Each card is what a site of that kind actually asks for on day one, what Omaya does about it, and one moment from an ordinary day.
Tenants ask for footfall you cannot prove, washrooms are cleaned by the clock, and security sees cameras but not patterns.
For exampleSaturday 15:10 — Level 2 food court at 92% of capacity, the L2 washroom score hits 80 and a cleaner is dispatched, the security board stays green.
Crowds move faster than radios, queues overflow into walkways, and a missing child is a park-wide search.
For example14:40 — the coaster queue crosses 85% and the plaza reads 34 °C; the ride team is paged, misting is switched on, and the operations log shows both.
Meeting rooms are booked and empty, desks look full on the plan and are not, and the air-con runs for nobody.
For example10:15 — Training Room booked since 10:00 and still empty, so it is released; at 18:20 its lights and AC switch off on their own.
Guest flow is felt, not measured; function rooms run climate for empty hours; housekeeping and security learn of problems late.
For example22:30 — the ballroom emptied at 22:05, so its air-con dropped to setback; a housekeeper's panic press in the L8 corridor reached the guard app in four seconds.
Equipment is searched for instead of used, visitors get lost, waiting areas overflow, and compliance evidence is assembled after the fact.
For example09:20 — Clinic B waiting area at 28 with an average wait of 41 minutes, so a second counter opens; a wheelchair leaving Ward 3 without a porter is flagged.
Sales are counted; the people who did not buy are not. Layout changes are argued about instead of measured.
For exampleWeek 37 — the new endcap raised dwell in Zone C by 38% with no change in entries; the compare report goes to the merchandising meeting as-is.
Lecture halls are timetabled at capacity and half full, labs are used after hours unseen, and a fire drill is a clipboard.
For exampleTuesday 11:00 — Hall A timetabled for 200 holds 68 for the fourth week; the space report proposes moving the class and freeing the hall.
Headcount is a turnstile total, not who is in which hall now; exhibitors want dwell they cannot get; navigation is signage.
For example13:05 — Hall 3 at 96% and rising, so entry is paused at the north door and the flow report shows the crowd coming from the keynote.
Tools and trolleys go missing, lone workers are out of sight, and heat and noise limits are checked on a form once a year.
For example02:10 — a pallet trolley leaves Bay 4 after hours and the night guard is dispatched; the noise report for Line 2 is ready for the audit.
Many sites, many dashboards, and energy spent on rooms nobody is in.
For exampleMonday 08:00 — the assistant reports a gateway swapped overnight, two rooms cooled while empty last week, and a draft rule to fix it awaiting approval.
Gateways and bridges speak to Omaya over whichever transport they support.
Alerts, exports and events, to where your team already works.
The platform underneath is the same. These are pre-built for problems common enough to be worth solving once.
Booked against actually occupied — find the rooms held and never used, and free them.
Cleaning triggered by traffic rather than by clock, with supply levels and leak detection.
Consumption per circuit against occupancy, so waste is visible as waste.
Button and app requests routed to whoever handles them, tracked to completion.
A screen showing live occupancy, air quality or availability, without a login — including a live 3D floor plan.
For the security team: armed hours, restricted zones, panic buttons, heat that looks like fire, coverage lost, and out-of-habit presence judged by AI. Guards get a phone app with a one-glance board; escalation goes to named people by email, SMS or WhatsApp.
Emergency muster: a snapshot of everyone on site, who has reached the gathering point, and who is missing.
Registration, check-in and check-out, host notification, and a visitor app the organisation brands as its own.
Evidence against a required standard, collected as it happens rather than reconstructed later.
Most sites start with one question — a floor that feels crowded, rooms nobody can book, a cleaning round on the wrong schedule — and grow from there.