InnerWeb
Skip to main content

Location terms to define before the statement of requirements

Tender requests for employee location diverge in offers, because vendors understand the same words differently: zone, location, accuracy, alarm. Procurement can stop this with one step: require the vendor to provide written definitions of a few terms before the statement of requirements is drafted. Below is the list of those terms and the control questions.

30 chars
limit on the length of a location name in the system
Source: spec sheet
100 m
recommended spacing of transmitters on roads
Source: spec sheet

Why a glossary before the request

If the statement of requirements speaks of a zone, and one vendor understands it as an area on the map while another understands a hazardous explosive atmosphere zone, the offers cannot be compared. A glossary in writing is the cheapest protection against such differences and the basis for later acceptance.

The recommendation is simple: the vendor describes each term in its own words, and procurement compares the definitions before it starts comparing prices.

Five terms to define

For each term we give what the vendor should write, and how this description looks in the InnerWeb system, so that procurement has a pattern to compare against.

Beacon

The vendor should state whether the beacon is a fixed transmitter or a worn device, what certificates it holds and where it is mounted. The industrial InnerWeb beacon has an industrial design registration, a CE declaration and an ATEX construction for zones 2/22. Recommended layout: roads about every 100 m, inside a building one transmitter per 100-200 m².

Heartbeat

Ask for the list of fields in the message and its frequency. In InnerWeb, the worn device cyclically sends which beacons it hears, the signal strength, the battery level and the status. From this the system knows the employee's position in real time and feeds presence, joining the permit and safety signals.

Zone

Ask for a distinction between a zone as an area in the system and a hazardous zone in the meaning of regulations. These are two different things. The legal requirement is described by the person responsible for the plant, while the system shows visualization and data.

Work area outline

A permit covering several locations is drawn on the map as one work area outline. It is a visualization, not a hazardous zone. The vendor should state whether its outline has the same meaning and whether it changes permissions.

Floor

Ask how the system marks floors and how it shows the employee in a multi-storey building. In InnerWeb, a double-click on a building enters the interior, the floor selector (P, 1, 2 and up) shows the floors, and a double-click on the employee opens the building at the floor of their location.

Recommended transmitter density

Recommended transmitter densityHorizontal bar chart: one transmitter per 100 m² in the denser variant and per 200 m² in the sparser one.050100150200m² per beaconMinimum densityMinimum density: 100 m² per beacon100Maximum densityMaximum density: 200 m² per beacon200
Source: Layout recommendation: one transmitter per 100-200 m² in a building

Questions to add to every term

Beyond the definition, add three control questions: how the term is measured, who is responsible for its correctness and how it is confirmed at acceptance. These three questions turn the glossary into a tool for assessing offers.

Also add the constraints: the name of a location in the system has a limit of 30 characters, and the plant map is isometric (2.5D view). Such details affect how the plant names its halls and buildings, and it is better to know them before implementation than after.

How to use the glossary in the procurement

Attach the glossary to the request as an annex, asking the bidder to confirm or correct it. Differences between definitions then become questions to be clarified, not a dispute after the contract is signed. It is also good to set a deadline by which the bidder returns the confirmed glossary, and a person on the plant side who settles discrepancies. Without such an owner, definitions drift apart already at the clarification stage, and acceptance ends in a discussion about words instead of the operation of the system. The glossary is also worth updating after the pilot, when concepts nobody named earlier come to light. A single sentence in this step helps too: the offered system complements the plant's existing systems (access control, time and attendance, HR, ERP) and does not replace them.

Checklist

Video

Frequently asked questions

Does a glossary lengthen the procedure?

Usually it shortens it, because it reduces the number of additional questions. One annex replaces many rounds of clarification.

Should the definitions go into the contract?

Yes, as an annex. Acceptance is then assessed against the same terms that were the basis of the offer.

Who writes the definition of a hazardous zone?

The person responsible for safety in the plant. The system provides visualization and data, not the legal determination.

We will prepare a glossary for your request

On request we will provide written definitions of location terms, which can be attached to the statement of requirements and used at acceptance.

Let's talk