Site setup

Overview

This chapter sets up a whole building once, from start to finish. The order of the steps matters more than any single step: almost every "nothing is showing up" question comes from a step done before the step it depends on.

Steps 3 and 6 are the ones that decide accuracy, and both are about the same thing: making the plan's coordinates mean real metres, then making the gateways' positions and hearing true in those metres. Everything else is bookkeeping that the reports hang off.

The result is this hierarchy:

Location → [Building] → Venue → Zone. Building is optional and disappears when you have none, so a single-site deployment reads Location → Venue → Zone. Everything that positions, ingests or reports hangs off the venue, which is why the venue — not the building — is where a floor plan and its calibration live.

SPECIFICATION

• Space pages need view-spaces, and the matching manage permission to change anything.
• Device pages need view-devices (Device > Sensor) and view-gateways (Device > Gateway); Bulk Import needs create-devices.
• The positioning settings need manage-settings-general.
• A user who cannot see a page lacks the permission in their role; see Administration.

Two shortcuts are available. After the venues are created, Start from an industry pack creates a typical set of zones, rules and reports in one operation. When the hardware is registered, Registering many devices at once loads a whole delivery of tags from one CSV file.

Requirements

Northwind Tower has three floors, Level 1, Level 2 and Level 3, each with meeting rooms and a pantry; the Boardroom is on Level 3 and the Server Room on Level 2. Aisha Rahman (Facilities Manager) sets up the spaces, Daniel Lim (Technician) mounts the hardware and walks the floors, and Ravi Kumar (Operations Lead) checks the result.

• One location, three venues, and a zone for every room people name.
• Every gateway and badge registered, placed and calibrated.
• Staff badges shown in the right room on the Live Monitor.

Configuration roadmap

(1) Create the location.

(2) Create a venue for each floor, then optionally apply an industry pack.

(3) Add the floor plan and set its scale.

(4) Register the gateways and sensors.

(5) Draw the zones and place the hardware and walls on the plan.

(6) Calibrate each floor with a walk.

(7) Attach tags to entities.

(8) Check the result.

Creating the location

A location is a site or campus, and it is the top of the hierarchy: every venue, gateway and report rolls up to one.

1. Choose Space > Location.
2. Create the location, for example Northwind Tower.

Buildings are optional and live inside a location. With one building, skip them: the level hides itself and the hierarchy reads Location > Venue > Zone. Add buildings when several exist and venues must be grouped by building: click Add Building at the top of the Location page and choose the location it belongs to.

Creating a venue for each floor

Overview

A venue is a space with a floor plan, usually one floor of one building. Two floors are two venues. A floor is not a level of the hierarchy of its own; it is two fields on the venue, Floor label and Floor level.

Restrictions

• Parent Location and Venue Name are required.
• Floor level orders the floors and tells positioning which floors are next to each other. A tag is moved between floors more reluctantly the further apart their levels are, so a wrong level makes every floor change wrong.
• The Advanced Settings below are needed by later features; set them now.

Procedure

1. Choose Space > Venue and add a venue.

2. Set the main fields as follows.

   Configuration Item	Value	Note
   Parent Location	Northwind Tower	Required. The location created first.
   Building	None	Leave at None unless buildings were created. Grouping only.
   Floor label	L2	A short name, such as L1, B1, Mezzanine. Shown in the hierarchy and on the floor pickers.
   Floor level	2	A number: ground = 0, basement = −1.
   Venue Name	Level 2	Required. What people call it.
   Labels	—	Optional labels for the venue.

3. Under Advanced Settings, set the following.

   Configuration Item	Value	Note
   Description	—	Optional.
   Floor Plan Image	—	Optional here; the plan is usually added in the Map Editor (next sections).
   RSSI — WiFi, Min (weak) and Max (strong)	defaults	The signal range in which a Wi-Fi device counts as present here.
   RSSI — BLE, Min (weak) and Max (strong)	defaults	The signal range in which a Bluetooth device counts as present here. Leave the defaults unless there is a known reason to change them.
   Dwell Engaged (minutes)	default	How long a device must stay before a visit counts as engaged in the visit reports.
   Operating days and operating hours	Use the organisation default	Utilisation is a share of operating hours, and per-day figures are averaged over open days. Without them a room looks idle all night and every figure is diluted. Tick Use the organisation default unless this floor keeps a different week.
   Cost of space per m² (or ft²) per month	—	The money column on Space Utilisation: what an empty room costs. Per square foot when System > Configuration > General > Area Unit says so.
   Rented area (m² or ft²)	—	The area the lease charges for. Empty: the floor plan's size is used, which is a rectangle around the whole floor and often larger. Rent on Space Utilisation is this area times the cost of space.
   Capacity (people)	—	How many people the whole floor is meant to hold at once: the fire certificate or design figure. Footfall shows most inside as a share of it, and a location's capacity is its venues' added up. Empty: the venue holds the sum of its zones' capacities (the box says Sum of its zones); set it when that sum is not the real figure, for example because corridors and open floor have no zone capacity.
   Every way in and out of this venue is counted	off	Whether Omaya may use the net of the doorway counters (in minus out) as this venue's occupancy. Tick it only when a counter covers every entrance, exit, fire door and stairwell; Coverage note and Daily reset at then appear.

4. Click Save.

CAUTION

Tick Every way in and out of this venue is counted only when every door is covered. With one door missed, the occupancy figure is wrong in one direction and stays wrong.

Verification

The venue appears on Space > Venue. Northwind Tower ends up with three venues: Level 1 (label L1, level 1), Level 2 (L2, 2) and Level 3 (L3, 3), all on the organisation's Monday-to-Friday week.

Start from an industry pack

Overview

A starter pack sets up a site the way an organisation of its kind usually runs it: the rules written first, the reports asked for, a dashboard, and the settings that suit the industry. There is one for every industry on the organisation profile. A pack is optional, nothing changes until it is set up, and it can be taken back later.

The preview shows exactly what would be created for this organisation. Zones it creates are empty until you draw them, and rules that page people wait until you choose who.

What a pack sets up

Everything is shown in a preview first, worked out against what the organisation has today, and any line can be unticked.

Part	Content
Apps that fit	The apps that suit the industry, marked on or off for the organisation. Apps are switched on by the Omaya provider, so the pack only recommends them; a step that needs an app that is off is offered greyed out (ask your provider)
Places and groups	The rooms and groups its rules watch: a checkout, a cold room, a ward, the staff label, a depot geofence. Each is matched to one of the organisation's own by name. Pick another, or for a room, Create an empty zone to draw on the floor plan later
Settings	Suggestions such as who counts as staff on Footfall, fall detection with its rest places, detection speed or trip speed. Each shows its current value and the new one. A setting already changed by the organisation is never ticked automatically
Rules	Each one says where it watches, with its value and hours ready to change. A rule that needs a device the organisation does not have (a temperature sensor, an energy meter, a GPS tracker) is unticked and says what it needs; ticked anyway, it is created switched off. Rules that page people (a fall, a panic button, a hall at capacity) are always created off
Scheduled reports	Emailed to the first administrator until recipients are chosen
Dashboard	A dashboard for the industry, shared with every administrator. Tick Make it the organisation's default dashboard to have it open first

Every pack also includes the basics: Gateway offline, Tag battery low, a Panic button pressed rule if none exists yet, a monthly Gateway Availability report and a weekly Alert Digest.

Pack	For	What its rules watch
Retail	Shops and malls	Checkout queues, footfall well below a normal day, the store near capacity, the stockroom after closing and its door, power after closing
Warehousing & Logistics	Warehouses, depots, fleets	Cold room out of 2–8 °C and its door, leaks, a fall on the floor, a vehicle leaving the yard after hours, vehicles stopped away from a site, drivers not heard
Manufacturing	Factories and plants	A fall on the floor, the hazard area out of shift, a hot plant room, power after hours, leaks
Smart Building	Offices, mixed use	A crowded pantry, an underused or empty meeting room, a hot server room, leaks, power after hours
Healthcare	Hospitals, clinics	Patient falls (wards are rest places), the medicine fridge out of 2–8 °C, a crowded waiting area, the pharmacy after hours
Aged Care	Care homes, assisted living	Resident falls (rooms and lounge are rest places), a resident out of their home area, the main exit at night
Education	Schools, universities	Classrooms occupied after hours, a crowded canteen, underused rooms, power after hours
Hospitality	Hotels, resorts	A busy lobby, an empty function room, the kitchen fridge, a crowded pool and gym, leaks
Transportation	Stations, depots, fleets	A crowded concourse, footfall well above a normal day, vehicles leaving the depot after hours or stopped away, drivers not heard, over-speed (created off)
Events & Exhibition	Halls, event venues	A hall near capacity (pages people), a crowded stage area, footfall well above usual
Government	Offices, public counters	A busy public counter, the restricted area after hours, underused rooms, power after hours
Construction, Mining & Energy	Sites, mines, plants	A fall, a worker not heard or stopped away, the hazard area out of shift, a tracker leaving the site after hours
Data Centre	Data centre floors (where the Data Centre app is installed)	Inlet heat in the colo hall and AI pod, humidity, a warm electrical room, more than one person in the mantrap, leaks
General	Any other organisation	The basics only, and a general dashboard

Applicable versions / plans

SPECIFICATION

• Permission: manage-tenant-settings (Admin, as shipped). Preview, apply and remove all check this permission only.
• The Data Centre pack is offered where the Data Centre app is installed.

Requirements

At Northwind Tower, Aisha Rahman applies the Smart Building pack to Level 1. The pack's Server room is the building's Comms room, there is no pantry zone yet, and the pantry holds 25 people.

• The pack's rooms are matched to the building's own zones.
• Pantry crowded fires above 25 people.

Restrictions

• At least one venue must exist. Without one the preview says Create a building or floor first (Location > Venues). The pack sets things up for one of them.
• A pack is set up for one venue at a time.
• Footfall against a normal day needs a few weeks of history. Capacity rules need a capacity on the zone (Space > Zone). People Count and Space Utilisation reports need something that counts heads; Environment needs fixed temperature or air sensors. See How many were here.

Configuration roadmap

(1) Open the pack's preview.

(2) Choose the venue and match the places.

(3) Review the lines, and set the pack up.

(4) Draw the new zones, switch on the paging rules, and choose report recipients.

Procedure

1. Choose System > Configuration and click the Starter Packs card.
2. The pack for the organisation's industry is first, marked For your industry. Click Preview on the pack (Review on a pack already applied).
3. With several venues, choose the venue under Set it up for.
4. Go down the preview: pick the places, untick unwanted lines, and change any value or hours. Changing a place updates the rules that depend on it.
5. Click Set up N items.

Verification

• The message is Set up N items. (or Nothing new to set up.). The result lists everything created, each linked to where it is changed, and anything that could not be created, with the reason.
• If applying fails, the message is The pack could not be applied, and nothing was changed.

Then complete the setup:

1. Choose Space > Zone. Draw any zones the pack created (the Not drawn tab lists them) and set a Capacity.
2. Choose Rules > All rules. Open the rules created off, choose who is paged or the devices they watch, and switch them on.
3. Choose System > Schedule Report and choose who receives each new schedule.

CAUTION

Until a zone created by a pack is drawn, nothing is placed in it and its rules cannot fire. Rules that page people stay off until someone is chosen to be paged and the rule is switched on.

Removing a pack

1. Click Remove on the pack's card and confirm Remove what <pack> added?.
2. The pack takes back the rules, schedules, dashboard and empty zones it created and puts its settings back as they were. Anything changed since is kept and listed: a rule that was edited or switched on, a zone that was drawn or has devices, a setting that was changed again. The message is Removed N., followed by Kept N that have been changed or used since. when anything was kept.

Opening a pack already applied shows what it set up as Made by this pack, so applying it again offers only what is left.

Adding the floor plan and its scale

Overview

On Space > Venue, Floor plan on a floor's card opens the Map Editor for that floor: the plan in the middle, one floor list on the left with a group each for Rooms, Gateways, Sensors and Walls, doors and furniture (each with a show/hide eye and one search box over them all), and a details panel on the right while something is selected. At the top are the floor chip (the floor's size, ceiling and north, or Finish floor setup), Import, 3D view and Calibrate gateways.

A new floor opens in Floor setup: three numbered steps, each ticked once it is done. Floor setup can be reopened at any time by clicking the floor chip or pressing F.

Restrictions

• Floor plan picture: JPG, PNG or WebP, up to 20 MB. A high-resolution top-down view works best.
• The scale line is what metres mean on this floor: every position, zone area and wall length is measured from it, not from the typed width and depth. Once the line is set, Width and Depth are read-only and measured from it.
• Use the longest line possible: a 2 cm slip on a 3 m line is a 0.7 % error everywhere; on a 20 m line it is 0.1 %.

Procedure

1. Choose Space > Venue and click Floor plan on the floor's card.

2. Floor plan picture. Click the box (Drop a picture here or click to browse) and choose the plan. The editor uploads it and reloads.

3. Scale line. Click Set the scale line. Drag A and B onto two points that can be physically measured (opposite corners of a room, a wall that can be taped), type the real distance in A to B above the plan, and click Save.

4. Size, heights and north. Set the fields as follows and click Save size, heights and north.

   Configuration Item	Value	Note
   Width × Depth	measured	The floor's real size in metres. Read-only once the scale line is set.
   Ceiling height	3.2	Storey height. Used by the 3D view and radar heights.
   Tags carried at	1.1	How high tags are carried, roughly 1.1 m for a badge. See How high each gateway is.
   North	—	Which way the plan faces. Drag the dial, or type a bearing.

5. Click Done, back to the floor.

Verification

All three steps show a tick, and the floor chip shows the floor's size instead of Finish floor setup. The whole procedure, with the messages each step can show, is in Setting the scale.

No plan image at all?

The wall designer is a drawing tool for that case: open the Walls, doors and furniture group and click the layout icon in its heading. Lay out walls and furniture, let it find the rooms, then click Save as the floor plan picture. What is drawn becomes real walls and zones, not a picture of them.

Registering the hardware

Overview

Gateways are registered on Device > Gateway and sensors and tags on Device > Sensor. This comes before placing anything on the plan: the Map Editor's Gateways and Sensors groups list what is already assigned to the venue so it can be positioned; they are not where devices are created.

Restrictions

• A gateway with no venue has nowhere to report; one with the wrong zone sends everyone near it to the wrong room. When Omaya can only say which gateway hears a tag loudest, it reports the tag in that gateway's zone.

• The model chosen for a sensor decides how its packets are decoded and what the device can contribute; Devices and what they report is the list. A model that is not listed can be added: Sensor onboarding.

• There is no fixed minimum number of gateways, but each count gives something different:

  Gateways on a floor	What Omaya can tell
  One	Which floor, and the gateway's own room.
  One or more, with Room estimation on	Rooms without a gateway of their own too, worked out from what every gateway did and did not hear. See Rooms settings.
  Three or more, placed on the plan	A position in metres (triangulation), drawn on the plan.

  Spread gateways out rather than lining them up along one wall; see Gateways for where to mount them.

Procedure

1. Choose Device > Gateway. For each gateway, enter its MAC Address and choose its Location, Venue and Zone (the room it hangs in).
2. Choose Device > Sensor and register each sensor and tag with its model. For many devices, click Bulk Import at the top of the page; see Registering many devices at once.
3. Optionally put labels ("Fridges", "Night shift", "Tools") on devices now. A label is what lets one rule later cover all of them, and new devices given the label are covered without editing the rule. Labels are kept on System > Labels.

Badges that scan instead of broadcast

Most tags send a signal for the gateways to hear. A few devices, such as cellular badges set to a Bluetooth or Wi-Fi fix, work the other way round: they report the beacons and access points they heard. Those need anchors, fixed beacons or access points tied to a zone, on Device > Beacon & Wi-Fi Anchors. See Beacon and Wi-Fi anchors. Ordinary tags do not need them.

Verification

Each gateway and sensor is listed on its page with the venue and zone given.

Registering many devices at once

Overview

/admin/manage/device/import: the Bulk Import button at the top of Device > Sensor.

Bulk Import takes a CSV file, one row per sensor, tag or beacon, checks every row, and creates the devices together. It replaces typing many MAC addresses into a form one at a time, which is how one or two of them end up wrong. It is for sensors and tags; gateways are still added one at a time on Device > Gateway.

Steps 1 to 3 change nothing, so you can upload, map and validate as often as you like. Only Commit creates devices.

Applicable versions / plans

SPECIFICATION

• Permission: create-devices for the Bulk Import button and its page. As shipped, Admin and Manager have it.

Requirements

At Northwind Tower, Daniel Lim receives the first delivery of badges and sensors and registers them from one file.

• Staff badges and two climate sensors are created in one import.
• A spare badge is registered inactive, ready to hand out later.

Restrictions

• Venues and zones named in the file must exist. Venue and zone names are looked up when the import is committed; a name that does not exist fails that row. Create the venues and zones first, or leave those columns empty and assign the devices later.
• The model column takes the model slug, such as minew_mwc01, not the name MWC01. Every slug is in the Slug column of Devices and what they report.
• CSV only. Excel workbooks (.xlsx) are not accepted. In Excel use File > Save As > CSV UTF-8 (Comma delimited).
• The file is at most 5 MB, UTF-8, separated by commas, tabs or semicolons. One commit takes at most 5,000 rows.
• Bulk Import never changes an existing device: a MAC already registered is skipped.

CSV file format

Row 1 is the header row; every following row is one device. Column order does not matter, and the header names below are matched automatically (case does not matter). Any header can also be mapped by hand on the Map columns step.

Column	Required	Content	Accepted values	Also recognised as
mac_address	Yes	The device's MAC address, printed on it or its box	AA:BB:CC:DD:EE:FF, AA-BB-CC-DD-EE-FF or AABBCCDDEEFF, upper or lower case. Saved as AA:BB:CC:DD:EE:FF	mac, mac address, macaddress, ble mac, device mac
name	Yes	What people call it	Any text	device name, label, tag name
device_type	Yes	The kind of device	Exactly one of sensor, tag, asset_tag, beacon, tracker, actuator, other, in lower case	type, device type, devicetype, kind
device_model	Yes	The model, so its packets are decoded	A slug from Devices and what they report, for example minew_mwc01, milesight_am307, moko_h5	model, device model, devicemodel, hardware
venue	No	The venue it belongs to	A venue name exactly as on Space > Venue (case does not matter). Empty: taken from the zone, if a zone is given	venue name, venue_uid, location name, building
zone	No	The zone it is in now	A zone name. If two venues have a zone of that name, fill in venue too so the right one is picked	zone name, zone_uid, area
home_zone	No	Where it belongs, for a device that moves	A zone name. If zone is empty, the home zone is used for both	home zone, home, default zone
description	No	A note shown on the device	Any text	desc, note
firmware_version	No	For the organisation's records	Any text	firmware, fw, fw version
tx_power	No	The device's transmit power setting, in dBm	A whole number, for example 4 or -8. Anything that is not a number is ignored	tx power, txpower, tx
notes	No	Free notes	Any text	comment, comments
is_active	No	Whether the device starts active	N, No, False, 0, inactive or disabled make it inactive. Anything else, or empty, makes it active	active, enabled

Download sample CSV on the page gives a file with these headers (all but notes), five example rows with made-up MACs, and the organisation's first venue and zone names already filled in. Replace the example rows; do not keep them.

Example file for the first Northwind delivery (the MACs are made up):

mac_address,name,device_type,device_model,venue,zone,home_zone,description,firmware_version,tx_power,is_active
AA:BB:CC:00:10:01,Badge – Facilities Manager,tag,minew_mwc01,Level 1,,,Facilities Manager badge,,,Y
AA:BB:CC:00:10:02,Badge – Operations Lead,tag,minew_mwc01,Level 1,,,Operations Lead badge,,,Y
AA:BB:CC:00:10:03,Boardroom air,sensor,milesight_am307,Level 3,Boardroom,,CO2 and temperature,,,Y
AA:BB:CC:00:10:04,Server Room climate,sensor,milesight_em300_th,Level 2,Server Room,,Rack-height temperature,,,Y
AA:BB:CC:00:10:05,Wheelchair 1,asset_tag,moko_m2,Level 1,,Pantry,Lives by the pantry,,,Y
AA:BB:CC:00:10:06,Spare badge,tag,minew_mwc01,,,,Kept in the facilities office,,,N

Row 5 has a home zone but no zone, so Pantry is used for both, and its venue comes from that zone. Row 6 names no venue and starts inactive.

Configuration roadmap

(1) Prepare the CSV file.

(2) Upload it and map the columns.

(3) Validate, and commit.

Procedure

1. Choose Device > Sensor and click Bulk Import at the top. The page is headed Bulk Import · Sensors, with four steps along the top: Upload, Map columns, Validate, Done.
2. Without a file yet, click Download sample CSV, fill it in, and save it as CSV.
3. Upload. Click the box (Click to choose or drag a CSV file here) and choose the file, or drag it onto the box. A progress bar runs, then the page moves on.
4. Map columns. Each column of the file is a row here: its header, a list of fields, and an example value from the first data row (e.g. …). Recognised headers are already set. Check each one; set any that read — skip — but should be imported, and leave — skip — on unwanted columns. The four required fields are marked with a red star: MAC address *, Name *, Device type *, Device model *.
5. Click Validate →. Nothing is saved yet.
6. Validate. Four figures (Total rows, Will create, Will skip, Errors) and a table with Row, Status, MAC and Message for every row. The row number is the line in the file, counting the header as row 1. Status is pending (message OK: will be created), skipped or error.
7. To fix errors, correct the file, reload the page and start again from step 3. Rows with errors are not imported, but they do not stop the others.
8. Click Commit (N new), where N is the number that will be created. The button reads Committing…. It is greyed out when nothing would be created.

Verification

1. The page says Import complete with Created, Skipped, Errors and Total processed. Click View device list to see the devices, or Import another file.
2. On Device > Sensor, search for one of the names from the file: it is there, with the model, venue and zone given.
3. If Errors on the Done screen was more than 0, compare the list with the file. The Done screen gives counts only, not which rows failed; rows that fail at this point almost always named a venue or zone that does not exist (see below).
4. Within a minute or two of a device being switched on near a gateway, its Last Seen column changes from Never to a time. A device that stays at Never usually has a mistyped MAC.

Messages

On the Upload step

Message	Cause	Action
File too large (max 5 MB)	The file is over 5 MB	Split it into two files
Parse failed	The file is not a CSV or text file, usually an Excel workbook	Save it as CSV UTF-8 and upload that
CSV is empty or unparseable	No rows could be read	Open it in a text editor: it should be lines of values separated by commas
Network error: …	The page lost contact with Omaya	Check the connection and try again

On the Map columns step

Message	Action
Required columns not mapped: mac_address, name, …	Map a column to each field listed, then click Validate → again

In the Validate table

Status and message	Cause	Action
error · Invalid MAC	Not six pairs of hexadecimal digits	Correct the MAC; the letters O and I are often typed for 0 and 1
error · Missing name	The name cell is empty	Give it a name
error · device_type "…" not valid	Not one of the seven types, or not in lower case	Use sensor, tag, asset_tag, beacon, tracker, actuator or other
error · device_model "…" not recognised	Not a model slug; often the model name was used instead	Use the slug from Devices and what they report. For a model that is not listed, see Sensor onboarding
skipped · Duplicate MAC in file (row N)	The same MAC appears twice; the first one is kept	Remove the repeat
skipped · Already in fleet	A device with this MAC is already registered	None; it is left as it is. Edit it on Device > Sensor

On Commit

Message	Cause	Action
A message box with The import could not be saved (error N). Please try again., The import could not be finished. Please try again., or a message naming a field	Nothing was created. A named field says which part of the request was refused	Check the file against the columns above, upload it again and commit; nothing from the failed attempt needs undoing
Import aborted: …	Something went wrong part-way, and the whole import was rolled back	Nothing was created. Try again; if it repeats, send the message to the Omaya provider
Errors above 0 on the Done screen	A row named a venue (venue '…' not found), a zone (zone '…' not found), or a zone that is not in that venue (zone '…' not found in venue)	Check the spelling against Space > Venue and Space > Zone, fix those rows, and import only them again

Zones, hardware positions and walls

Overview

Back in the Map Editor, the zones are drawn and the registered hardware and walls are placed. Each group's count says what is left, for example 4 to place or 2 to draw, and the line under the plan totals what is drawn and placed on the floor.

Restrictions

• A zone is created first and drawn second. A zone needs a boundary of at least three points; a room cannot overlap another.
• Zones should cover the floor without gaps: a tag whose position falls outside every zone has no room to be reported in.
• Draw the areas named in conversation (this meeting room, the sales floor, the loading bay), not every architectural subdivision. Zones are what almost everything is reported against, so a zone nobody would mention is a row nobody reads.
• A room's capacity is set on its zone and nowhere else; the Meeting Room app reads this value, and without it "busy" and "over capacity" have nothing to compare against. 0 means unlimited. The venue's own Capacity (people) is for the floor as a whole and never replaces a room's.
• Position is computed from which gateways hear a tag and how strongly, so a gateway placed in the wrong spot is worse than one that is missing: it pulls every nearby estimate towards a spot nothing is at.

Procedure

1. Create each zone, in either place:

   • In the Map Editor. At the bottom of the Rooms group, type a New room name, choose its type and click Add room and draw it. The room opens ready to draw.
   • On Space > Zone. Click Add Zone and fill in Parent Location, Parent Venue, Zone Name, Zone Type and Kind of space; Capacity is under Advanced Settings. Click Save, then click Draw it in the zone's Floor plan column to open it in the Map Editor ready to draw.

2. Draw the zone: click the plan at each corner, then click the first corner or click Save outline in the bar above the plan. Undo removes the last corner. To change a drawn room, select it and click Edit outline. Details are in Zones are the rooms.

3. Set Capacity on each zone on Space > Zone.

4. Gateways. In the Gateways group, click each gateway (one not yet on the plan shows Place) and click the plan where it physically hangs, or drag its pin. Set the values in the bar above the plan and click Save.

   Configuration Item	Value	Note
   Tx	default	Signal at one metre. Leave the default until the calibration walk sets it.
   Height	2.7	Mounting height in metres.
   Rx	empty	Leave blank for now.

5. Sensors. In the Sensors group, place each fixed sensor the same way and click Save. A radar needs one more step: calibrate it from its device page, so that what it reports lines up with the plan (Radars).

6. Walls. In the Walls, doors and furniture group, add and draw the walls, and the solid furniture where the detail matters. Walls stop a position estimate from placing someone inside a lift shaft, and they feed the 3D view.

Let the plan propose the rooms

Import > Find rooms in the picture, at the top of the Map Editor, reads the plan picture and proposes walls and rooms for review before anything is saved. See Detecting the walls automatically. With the architect's drawing, Import > CAD drawing (DXF) reads it and sets the floor's picture and scale from it; see Importing the architect's drawing.

Verification

On Space > Zone, the Not drawn on the plan tile counts down, and each drawn zone shows Drawn in its Floor plan column.

Calibrating the floor with a walk

Overview

Placing gateways by eye gets close. A calibration walk gets it right: someone carries a tag around the floor, stops at a handful of points and marks each one on the plan, and Omaya works out from what every gateway heard where the gateways really are, how quickly signal fades on this floor, and a radio map of each room.

Restrictions

• Walk after the heights are set and the gateways are where they will stay. Moving a gateway afterwards means walking again.
• A floor works without a walk, on the gateways' default figures, but a floor nobody walked cannot build a radio map. The walk is worth doing once, properly, on any floor where the room matters rather than just the floor.

Procedure

1. In the Map Editor, click Calibrate gateways.
2. On the Calibrate gateways page, choose the tag under Pick the tag you will carry.
3. Click Start walk here (the walk is named by date; nothing needs typing). To carry a phone instead of a laptop, click Continue on a phone.
4. Walk the floor once, covering every room and all four corners.
5. Click Finish walk.

Verification

Omaya calibrates the floor on its own and writes a report of what it did and what it declined. The report shows on the phone and under Last walk report at the top of the Calibrate gateways page. The whole procedure is in The calibration walk.

Naming entities

A tag is a MAC address; an entity is the forklift, the contractor, the wheelchair. Until a device is attached to an entity on the Entity page, every report about it is a report about hardware rather than about something people talk about.

• An entity can hold more than one tag over time, which is how a vehicle keeps its history when its tag is replaced. See People and assets for what an entity is and how to swap a tag without losing where it has been.
• Give entities labels too ("Contractors", "Wheelchairs"). The Label Fields button on the Entity page lets a label carry custom fields, such as a service date or an asset number, filled in on each person or asset with that label.

Checking the result

Check four places, in this order, because it isolates a fault fastest:

1. Choose Device > Gateway: is every gateway online? One offline gateway explains an entire floor of missing data.
2. In the Map Editor, click Coverage above the plan. Rooms that can be shown says how many of the zones Omaya can ever name; each room is marked has a gateway, by room estimation or cannot be shown, and the plan shades them green or red. See The coverage check.
3. Choose Monitor > Live Monitor: do devices appear on the plan, roughly where expected? Click one and click Why here? to see what placed it.
4. Choose Monitor > Right Now & Live Alerts: does each zone report a count, and does the source badge say what is expected?

A zone reading tags where a radar is fitted means the radar is not reporting; a zone reading zero from tags means nobody in it is carrying one, which is not the same as empty. Read Occupancy: which number is which before drawing a conclusion from any of it.

A final check is a walk with a badge: five minutes in one room, then another, while watching the badge's dot on the Live Monitor. If a room is wrong, see Troubleshooting room placement.

What to set up next

• Indoor positioning. Choose System > Configuration and click the Indoor Positioning card. Its Overview tab reads the organisation's own floors and the last 24 hours and says, switch by switch, what it recommends, with an Apply button where it disagrees with what is set. See The settings that tune it.
• The rest of the organisation's settings: timezone, opening hours, how long data is kept, the AI model. See Organisation settings.
• Capacity on every zone that will ever be asked "is this room big enough?".
• Rules, for the things that would otherwise have to be watched for.
• A scheduled report, under System > Schedule Report, so the weekly figure arrives without anyone running it. A schedule with nobody chosen goes to the organisation's first administrator, so give that account an email address. See How many were here.
• Who is told. Things that have no recipient of their own (a new maintenance request, a request past its review target) go to the people on the Notifications list: choose System > Configuration and click the Notifications card, which opens the list on the Organisation page. Left empty, every active admin is told, and the card reads Every active admin. Apps with their own lists keep them: Security Watch escalation, a rule's email action, the visitor notification grid.
• Lifts and stairs, if visitors are given directions between floors: the Floor connections in the Mobile App settings.

Troubleshooting

Symptom	Cause	Action
The Gateways group says No gateways on this floor yet	The gateways were registered without this venue, or under another one	Open each under Device > Gateway and set its Venue
A device is on the plan, but outside the building	The gateway it is placed near is placed wrong, or the scale line is wrong. The Gateways group shows each gateway's position in metres from the top-left corner; a negative number or one larger than the floor is shown in amber	Correct the gateway's position or the scale line
Floor setup says the scale line and the typed size disagree (These disagree, and positioning follows the line)	The scale line and the typed width and depth describe different floors. Every distance is out by the difference shown	Re-measure the line, or correct the typed size, whichever is wrong
Every tag is on the right floor, but always in the gateway's room	Room estimation is off, or the zones are not drawn. With it off, a tag is reported in the zone of the gateway that hears it loudest	Turn on Room estimation (System > Configuration > Indoor Positioning > Rooms) and run the coverage check again
A drawn zone does not appear in reports	The zone has no boundary of at least three points	The Not drawn tab on Space > Zone lists every zone with no boundary; in the Map Editor its row shows a pencil instead of a tick
Unsure whether the walk is needed	—	A floor works without one, on the gateways' default figures; the walk is what makes it right. A permanently mounted sensor marked as a positioning reference in the Sensors group adds to the radio map and to the next walk, but does not calibrate a floor on its own (Calibrating from fixed sensors)