Getting started
For a new customer and the person on site who receives the sensors. It covers unpacking, powering on, placement, the decisions to make before go-live and signing in to the portal.
The sensors
| Model | Connects by | What it is for |
|---|---|---|
| ModelB | Wired Ethernet or Wi-Fi | Tests the service path from the office: application response, DNS, the network path and Wi-Fi link and signal |
| ModelC | As ModelB, plus a Wi-Fi 7 adapter | As ModelB, for sites with Wi-Fi 7 access points |
| ModelA | Wi-Fi only (Wi-Fi 6, 2.4 and 5 GHz) | A small probe that measures Wi-Fi where people sit |
Each sensor carries a Device ID on a label at the back. Your administrator uses it to assign the sensor to a site and floor, so keep a note of which Device ID goes where.
What's in the box
ModelB and ModelC
- The sensor
- A power supply with a USB-C cable (output 5.1 V, 3 A)
- Two L-shaped brackets
- An R-type cable clip
- Two hex socket button-head screws, 4 mm and 8 mm long
- A 2 mm hex key
- Two wood screws
- A small piece of self-amalgamating tape, for the cable grip
[PLACEHOLDER: confirm whether the ModelC kit differs, and how its Wi-Fi 7 adapter is supplied and fitted]
Mounting and powering on
- Fit the brackets. Screw the two L-shaped brackets to the sensor with the hex key. They let you fix the sensor under a desk or table, or on a wall or panel, using the wood screws.
- Connect the network (ModelB and ModelC on a wired desk). Plug the sensor into a live port on the user network.
- Connect the power. Plug the USB-C cable into the sensor and the power supply into the mains.
- Secure the cable. Hold the power cable against the sensor with the R-type cable clip, wrapping a little self-amalgamating tape round the cable for grip, so it can't be pulled out by accident. If you fit the cable clip together with a bracket, use the longer 8 mm screw.
- Record the position. Note the Device ID and the desk on your floor plan. Your administrator needs it for the floor map.
[PLACEHOLDER: how a new sensor first joins the network (pre-configured before delivery, or wired first), and how long it takes to show as online in the portal]
Status lights
| Light | When it is on |
|---|---|
| Red | At start-up, and if a critical system error occurs |
| Green | At start-up, and during processor activity |
If the red light comes on after start-up, the sensor has hit a critical error: contact support with its Device ID.
Where to place sensors
The aim is for sensors to experience the network the way your staff do: at their desks, spread across the floor, including the worst spots.
- ModelB on a wired desk. Choose a desk with a live port on the user network, mid-row or mid-room, and mount the sensor under it.
- ModelA where people sit. At desk height, on every other desk, staggered across back-to-back rows. Not inside metal pedestals or cabinets.
- Cover the edges, not just the centre. Include row ends, room corners and the desks furthest from access points.
- Don't cluster under access points. A sensor directly beneath one reports best-case Wi-Fi. Spread sensors across each area.
- Record every position. Mark each sensor and its desk on the floor plan when you install it. The floor maps depend on it.
- Keep each group in one zone. Keep the sensors that work together within one room or desk row, so results map cleanly to a place.
How many sensors a floor needs depends on its layout: see Sensors.
Five decisions before go-live
Your administrator sets these up in the portal, normally in this order. The first three place the sensors; the last two decide what they test and who hears about problems. Gather the information early.
| Step | What you decide | What to have ready |
|---|---|---|
| 1. Sites | Each office being monitored | A short site code, the address and the public IP address of each internet or WAN circuit (up to two per site) |
| 2. Sensors | Which sensor goes where, and how it connects | Each Device ID with its site, floor and desk; the Wi-Fi networks and security type, or the wired network details |
| 3. Wireless maps | Where each sensor sits on each floor | A floor plan image for each floor, ideally showing desks, wired ports and access points |
| 4. Applications | What the sensors test | The applications your people can't work without, with a URL for each |
| 5. Alerts | Who is told, and when | The people or mailboxes for each alert, and what "too slow" means for each application and site |
Step by step: IoT administration.
Signing in to the portal
[PLACEHOLDER: portal sign-in address, provided at onboarding]
- Single sign-on. If your organisation signs in through its identity provider, such as Okta or Entra ID, use your usual work account. Your password is managed there, not in CNA.
- CNA account. Otherwise, sign in with the user name and password you were given, and change the password from your profile.
If your organisation has restricted the portal to its own network or VPN, sign in from there.
Next steps
- Portal user guide: find your way round the views.
- IoT administration: set up sites, sensors, maps, applications and alerts.
- Network requirements: what the sensors need from your network.
- Frequently asked questions.