Healthcare 11 min read

The part of the quote that decides whether it works.

Indoor location is not hard to buy and is easy to install badly. This is the engineering layer nobody publishes — sight lines, spacing, mounting height, cable versus battery, and what a survey has to measure before anyone quotes.

By Frank Guo · Technology & Product Leadership, addanode

TL;DR — Four things decide whether an indoor location system produces a record you can rely on. Line of sight: the accuracy figures on any datasheet assume an unobstructed path between tag and reference point, and every wall, bulkhead and stacked trolley degrades it — which is why the honest design target is room and door certainty, not centimetres. Geometry: reference points want to be spread around the space rather than clustered, at a similar height, generally mounted high, and kept clear of walls; long thin arrangements and tight angles produce unstable positions. Power and cable: cabled points are cheaper where a ceiling is already open, battery points with multi-year cells are what make an occupied or heritage building feasible at all. South African reality: it has to keep recording through an outage, survive being wiped with disinfectant, and the radios have to be legal to supply. Get these right and the software is straightforward. Get them wrong and no amount of software fixes it.

Line of sight is the whole game

Every accuracy number you will be shown for an indoor positioning system — including ours — is measured with a clear path between the tag and the reference point. That condition is called line of sight, and in a real building it is the exception rather than the rule. A radio pulse that reaches a receiver after reflecting off a wall has travelled further than the straight-line distance, so the calculated position is pulled away from the truth. This is not a defect to be fixed by better firmware; it is geometry.

The practical consequence is a design rule rather than a disclaimer: place reference points so that the tags you care about can usually see them, and then set your expectations to what survives when they cannot. A worn badge sits at chest height on a moving person who is often turned away, often behind a trolley, often through a door frame. Designing for that reality — and targeting certainty about which room rather than a position within it — produces a system whose record holds up. Designing to the datasheet produces one that disagrees with itself at the worst moment.

At survey we simulate this deliberately: walk the route wearing a tag the way a carer would, and note every point where something solid comes between it and a proposed mounting position. Bulkheads, lift shafts, steel fire doors, sluice rooms, plant enclosures, stacked linen trolleys and the lead-lined walls around imaging are the usual offenders.

Geometry: where the points go

For presence — knowing a tag is in a zone — one reference point is enough and geometry barely matters. For boundaries, two points along the line of travel let the sequence of detections reveal direction. It is only full area coverage where arrangement starts to decide quality, and the principles are consistent:

  • Spread, do not cluster. Points arranged around a space produce stable positions; points bunched along one edge produce positions that are confident in one axis and vague in the other. A roughly square arrangement is the ideal, and long thin rectangles are where accuracy degrades first — as a working rule, keep the covered area's length within about twice its width, and the angles subtended at the middle of the space wide rather than shallow.
  • Keep heights consistent. Mixing a point at 2.4 m with one at 5 m in the same group introduces a vertical ambiguity the system has to resolve from weaker information. Where a building forces it, record every height precisely.
  • Mount high, within reason. Higher points see over people and equipment, which is the main enemy of line of sight. Four to five metres is a good target where a ceiling allows it; in a domestic-scale retirement cottage, above door height is usually the practical answer.
  • Stand off the walls. A unit pressed flat against a wall, or tucked into a corner, gets reflections from the surface immediately behind it. Half a metre of clearance is a reasonable minimum and costs nothing at design time.
  • Respect spacing. Reference points that are too far apart leave gaps; too close together and you have paid for overlap. Tens of metres between points is the normal working range indoors, set at survey against the ceiling height and what is in the way.

These are planning rules of thumb, not universal constants — the right spacing for a 2.6 m domestic ceiling and for a 6 m atrium are not the same number, which is exactly why the survey exists.

Cabled or battery: the decision that sets the price

Cabled (Power over Ethernet) Battery-powered
InstallOne cable per point back to a switchMount and go; one gateway serves many points
Where it winsNew wings, refurbishments, ceilings already openOccupied wards, heritage fabric, cottages across a site, outdoor boundaries
OngoingNo batteries to manageMulti-year sealed cells; plan the replacement cycle up front
Outage behaviourNeeds the switch and its UPS to be aliveUnaffected at the point; the gateway still needs backup
Hidden costContainment, ceiling access, ward downtime, making goodBattery replacement labour at end of life

The mistake is treating this as one decision for the whole building. Most real projects are mixed: cabled where a ceiling is open anyway, battery where the disruption of cabling costs more than the equipment. In a retirement village spread across cottages and gardens, battery points are usually what makes the project quotable at all — there is no trench to dig and no occupied unit to close.

Four South African constraints

  • It has to record through an outage. Reference points, gateways, switches and the server all need backup power, and the system must keep writing locally rather than dropping the shift. This is a specification item at survey, sized against your actual outage pattern — not an accessory sold afterwards. See load shedding protection.
  • It has to survive cleaning. Wearables and any equipment in a clinical area get wiped with whatever the infection prevention and control programme specifies. Sealed housings rated IP67 or better are the practical floor; anything that cannot take disinfectant will either be cleaned improperly or taken off.
  • The radios have to be legal to supply. Two separate things, often confused. Equipment of this class falls within the licence-exempt schedule of the radio frequency spectrum regulations, so no per-site spectrum licence is needed to operate it. Separately, and regardless of that exemption, the Electronic Communications Act requires radio apparatus supplied and used in South Africa to hold ICASA type approval. Write it into the supply agreement rather than assuming it, whoever you buy from.
  • The server is part of the building, not the cloud. A modest on-premises machine runs the positioning engine and the event database — in practice a current multi-core processor, ample memory and a disk sized to your retention policy, on the backed-up side of the comms room. Keeping processing on site is also what makes the POPIA position straightforward, as our POPIA guide explains.

What a survey must actually produce

A survey that produces only a quantity of reference points is not a survey. The output should be six things:

  • The sentences. Area by area, the statements the system must be able to produce. These set the resolution tier, and the resolution tier sets the cost — see the scenario map.
  • Ceiling heights per area, measured rather than assumed, because height decides coverage per point and whether a mounting method is possible at all.
  • An obstruction map from walking the route with a tag — including the trolleys, screens and equipment that are not on any floor plan.
  • The cable line: which areas can take a cable, which cannot, and what the disruption would cost in each.
  • A coordinate reference. An origin, and every planned position recorded against it including height above floor. Commissioning depends on these numbers being right; a point installed 1.5 m from where the system believes it is will quietly bias every position near it.
  • Acceptance criteria, written before installation, in the client's words: which room, which boundary, how quickly, how reliably. Prove them in the first area before the rollout continues.
Six things a survey has to hand over A survey that produces only a quantity of reference points is not a survey. The output is the sentences each area has to be able to produce, measured ceiling heights, an obstruction map walked with a tag, an honest cable line, a coordinate reference every planned position is recorded against, and acceptance criteria written in the client's words before anything is installed. A quantity of reference points is not a survey output The sentences Area by area, the statements the system must be able to produce. → Sets the resolution tier Ceiling heights Measured rather than assumed: height decides coverage per point. → Per area Obstruction map Walked with a tag, including the trolleys and screens on no floor plan. → What the plan omits The cable line Which areas can take a cable, which cannot, and what the disruption costs in each. → Where the price moves A coordinate reference An origin, and every planned position against it, including height above floor. → Commissioning needs it Acceptance criteria Written before installation, in the client's words, and proven in the first area. → Before the rollout
Six things a survey has to hand over Sentences, heights, obstructions, the cable line, coordinates, acceptance criteria. A point count is not a survey output The sentences Area by area, the statements the system must be able to produce. → Sets the resolution tier Ceiling heights Measured rather than assumed: height decides coverage per point. → Per area Obstruction map Walked with a tag, including the trolleys and screens on no floor plan. → What the plan omits The cable line Which areas can take a cable, which cannot, and what the disruption costs in each. → Where the price moves A coordinate reference An origin, and every planned position against it, including height above floor. → Commissioning needs it Acceptance criteria Written before installation, in the client's words, and proven in the first area. → Before the rollout
The six outputs described in the section above. A survey that produces only a quantity of reference points is not a survey — and the acceptance criteria have to be written before anything is installed, not agreed after it.

How installations go wrong

  • The unrecorded move. A point is relocated a metre during installation because of a beam, and nobody updates the coordinate record. Every position in that area is now biased, and the symptom — occasional wrong-room readings — looks like a software fault for months.
  • The ceiling void. Mounting a unit above a suspended ceiling to hide it puts a layer of tiles and services between it and every tag. It is neat, and it is the commonest self-inflicted accuracy problem.
  • Designing for an empty building. Surveys done on a quiet Sunday miss the trolleys, screens, visitors and stacked equipment that fill the space on a Tuesday. Walk it busy.
  • Forgetting the outdoor boundary. In a village the real perimeter is a garden gate or a path. Indoor-rated equipment on an outdoor boundary fails in the first serious weather.
  • Promising centimetres. Quoting line-of-sight accuracy as a delivery commitment sets up a dispute at handover that the physics will win. Commit to what the use case needs — room and door certainty — and specify it that way in the acceptance criteria.

See how this is put together on our nurse call and staff safety page, or the buying comparison in nurse call vs location systems.

FAQ

Deployment — common questions

Can a location system go into a building we cannot rewire?

Yes, and it is the normal case rather than the exception. Battery-powered reference points with multi-year sealed cells mount on a wall or a gatepost and report over a long-range radio link to a single gateway, so no conduit is run, no ceiling is opened and no ward or unit has to close. Most real projects end up mixed: cabled Power-over-Ethernet points where a ceiling is open anyway because one cable per point is cheaper and simpler to maintain, and battery points everywhere the disruption of cabling would cost more than the equipment.

How far apart do reference points go?

It depends on ceiling height, what is in the way and what resolution the area needs, which is why a survey exists rather than a table. Indoors, tens of metres between points is the normal working range. For presence — knowing a tag is in a zone — one point per zone is enough. For a boundary, two along the line of travel let the detection sequence reveal direction. Only full area coverage needs three or more spread around the space, and there the arrangement matters as much as the spacing.

How high should they be mounted?

High enough to see over people and equipment, which is the main enemy of accuracy. Four to five metres is a good target where the ceiling allows; in a domestic-scale cottage or a low-ceilinged ward, above door height is usually the practical answer. Two things matter as much as the number: keep heights consistent within a group, because mixing a point at 2.4 m with one at 5 m introduces ambiguity the system must resolve from weaker information, and keep units about half a metre clear of walls so the surface immediately behind them does not reflect.

Why does the installer need to measure coordinates?

Because the system calculates a tag's position from where it believes each reference point is. If a point was moved a metre during installation to clear a beam and nobody updated the record, every position calculated near it is biased by that error. The symptom is intermittent wrong-room readings that look like a software fault and get chased for months. Set an origin, record each installed position against it including height above floor, and treat the coordinate record as part of the commissioning deliverable rather than paperwork.

Can reference points be hidden above a suspended ceiling?

They can be, and it is the commonest self-inflicted accuracy problem we see. Putting tiles, cable trays and services between a reference point and every tag beneath it attenuates the signal and adds reflections, so a system that would have been dependable becomes erratic in exactly the areas where it was tidied away. If appearance matters, the answer is a discreet housing mounted in the room rather than a standard unit hidden above it — decided at survey, because it changes the bill of materials.

What happens to the system during load shedding?

Properly specified, it keeps recording. Reference points, gateways, switches and the server sit behind backup power sized against your actual outage pattern, and the system continues writing events locally rather than losing the period — which matters because emergencies do not avoid outages. Battery-powered reference points are unaffected at the point itself, though their gateway still needs backup. This belongs in the specification at survey; treating it as an accessory afterwards is how facilities end up with a record that has holes exactly where the difficult hours were.

Does the data have to go to a cloud service?

No, and we would argue it should not. A modest on-premises server runs the positioning engine and the event database: a current multi-core processor, ample memory, and a disk sized to your retention policy, sitting on the backed-up side of the comms room. Keeping processing on site keeps personal information inside the institution, simplifies the security measures POPIA requires, and avoids engaging the Act's restrictions on transfers outside South Africa. You should also get documented access to your own event data, so your reporting is never dependent on a supplier.

How long does an installation take?

The honest answer is that survey and commissioning take longer than mounting hardware. Physical installation of a ward or a wing is measured in days, particularly with battery points where there is no cabling. What sets the timeline is everything around it: agreeing the sentences the system must produce, recording coordinates properly, configuring rules and escalation, and then proving the first area live against acceptance criteria before the rest follows. A supplier promising a whole campus in a week is describing hardware mounting, not a working system.

Primary sources

Spacing, height and geometry figures in this article are planning rules of thumb for design discussion, not guarantees — the correct values for a specific building come from its survey.

The survey is the deliverable that matters.

We walk the building busy, measure the heights, map the obstructions and write the acceptance criteria — before anyone quotes a quantity of hardware.