InnerWeb
Skip to main content

Scenario: unattended station round with map checkpoints

The maintenance manager of a network of unstaffed stations knows this question from every audit: how do we know the technician really completed all the checkpoints? Below is an implementation scenario, not a description of a finished project. It is a concept for an operator of distributed stations, presented at the offer stage and based on the Patrols module and location from radio beacons.

20 s
warning after no movement in a working deployment
Source: production deployment (card)
< 2 min
from detecting no movement to notifying the response team
Source: process description (card)
240
checkpoint confirmations per month in the example
Source: sample calculation

Situation: stations where nobody sits permanently

A network operator has dozens of sites spread across the region: transformer stations, pumping stations, small reduction stations. None of them has permanent staff, so the status of a site is reported only by the technician's round, which follows a schedule. The site is fenced, but inside are points that must be checked in person: the switchgear, the tank, the power cabinet, the gate, the lighting and the warning board.

This concept describes a plant of this type. The system has been presented in an offer, not deployed at this company, so all figures concerning the operator itself come from sample assumptions, not from measurements.

Problem: a round that cannot be reconstructed

Today, confirmation of a round is often a signature on a card or a photo sent after returning. Both forms share the same flaw: the manager sees the result but not the route. He does not know whether the technician actually reached the tank or wrote the position from memory. When a failure happens a month later, nobody can say when a checkpoint was last checked.

The second problem is inconsistency. The same round done by two people looks different, because each has their own order and their own idea of what 'checked' means. There is no shared list of questions tied to a specific place on the site.

Successive thresholds for a no-movement response

Successive thresholds for a no-movement responseBar chart: warning after 20 seconds, alarm after 50 seconds, response team notified in under 120 seconds.0255075100125sWarning: 20 s20 sWarningAlarm: 50 s50 sAlarmResponse team notification (upper limit): 120 s120 sResponse team notification(upper limit)
Source: Parameters from a working production deployment and the description of the response process; alarm = 20 s + 30 s

Concept: checkpoints on the map and routes per department

The Patrols module lets you define checkpoints on the map, each with its own checklist, and then group them into routes for a department. In the concept for a station network, each site gets its own map and the checkpoints match real places to inspect. A route is a set of checkpoints, and the round confirms each one separately, so a missing checkpoint is visible instead of disappearing into a general 'done'.

The technician's position comes from pulses sent by the worn device. The device periodically reports which transmitters it hears and the signal strength, and the platform derives the location from these reports. Several transmitters are used at once and the result is averaged on the map, without GPS. Plant roads are covered with transmitters roughly every 100 m, and inside a building one transmitter per 100-200 m2 is assumed.

What a checkpoint definition includes

A checkpoint has a name the technician understands, a place on the map and a checklist of questions. It is worth writing the checklist in terms of actions, for example 'check the seal on the switchgear' instead of 'condition of the switchgear', because then the answer is unambiguous.

What a route definition includes

A route connects the checkpoints of one department in a sensible order of walking. For an unattended site, a route usually has from a few to a dozen checkpoints and corresponds to one service visit.

The round step by step

Below is the concept flow, from departure to report. Each step can be done with the functions described in the product documentation.

  • The technician puts on the watch and starts the route of the site he is travelling to.
  • After entering the grounds, the platform shows him on the site map, thanks to pulses from the transmitters.
  • At each checkpoint the technician confirms it and goes through the assigned checklist.
  • Skipped checkpoints remain open, so the manager sees an incomplete round immediately, not after a week.
  • When the route is closed, a record remains: which checkpoints, in what order and with what answers.

Sample calculation: scale for a network

For the purposes of the concept we assume sample figures that the operator replaces with its own: 40 stations, on average 6 checkpoints per station and one round per station per month. That gives 240 checkpoint confirmations per month. Without a route record the manager has 40 signatures on cards. With the record he has 240 confirmations, with order and answers.

The number of transmitters depends on the geometry of the site. The subscription option for transmitters is 100 units for 700 PLN net per month, i.e. 7 PLN per unit, which typically covers about 20,000 m2. A small unattended station is usually covered by a small number of units, so the cost per site is low. Pricing is always individual.

When a round turns into an incident

A round at a site without people is also work in isolation. If the technician stops moving, the system infers this from the pulses. In a working production deployment, the no-movement alarm warns after 20 s without movement. After a further 30 s without a response it raises an alarm, and an automatic dialer calls the designated people and repeats until someone answers. The time from detecting no movement to notifying the response team is under 2 minutes. These are values from a production deployment, not from the operator's site: for stations the parameters are set separately.

Conclusions for the maintenance manager

The main benefit is not replacing the technician but turning a declaration into evidence. The round with checkpoints delivers what audits ask about: who checked the site, when, and in what order. The duty to ensure safe working conditions results from Article 207 of the Labour Code, and the system provides evidence for an audit, not a guarantee of compliance.

The best start is one route at one station: check the quality of the checklists and only then copy the pattern to other stations.

Video

Frequently asked questions

Does the scenario describe an existing deployment at a station operator?

No. It is a concept for a type of plant, a network of unattended stations, prepared at the offer stage. The figures concerning the operator are sample assumptions.

Does the round require permanent GPS coverage?

No. The position is calculated from signals of many transmitters averaged on the map, so the system works without GPS, including inside buildings.

What happens to a checkpoint the technician does not confirm?

It stays open, so the round is visible as incomplete. The manager sees this without waiting for a paper card.

Does the system guarantee compliance with regulations?

No. It supports meeting the requirement and provides evidence for an audit. The basis of the duty is Article 207 of the Labour Code.

Sources

We will show the round on your site map

Book a call about round concepts for distributed sites. We will prepare a sample route with checkpoints and checklists.

Let's talk