Where the time loss comes from
When someone asks where exactly a job under a permit is taking place, the dispatcher looks in the paper plan, calls the contractor, asks for a description of the place and only then knows where to send help or an inspection. Each of these steps is short, but together they take several minutes.
The online map shows permits and employees as layers. A permit covering several locations is drawn as one outline, and the employee preview gives the distance to the place of work in metres. Reading the map replaces the phone call.
Calculation assumptions
We adopt working assumptions, which the client replaces with their own measurements: 15 work location confirmations per shift, 6 minutes per confirmation from the paper plan and phone call, and 1.5 minutes to read it from the map. We assume 250 shifts per year for one workstation.
These are not results measured at a specific plant, only a starting point for discussion. It is best to time 20 real confirmations before the deployment and 20 after it.
Time to establish a work location
- Paper plan and phone
- Online map
Result per shift and per year
The saving per confirmation is 4.5 minutes. With 15 confirmations this gives 67.5 minutes per shift, and over 250 shifts about 281 hours per year for one dispatcher workstation.
More important than the hours is that a shorter time to establish the location shortens the response time in an emergency. During an incident what counts is not the yearly total, but the first minutes.
What the calculation does not cover
It does not include errors caused by mixing up locations or the time a contractor spends waiting for a decision. It also does not assume that the map is accurate everywhere: the employee position comes from BLE signals averaged across several transmitters, and its quality depends on transmitter density.
If the paper plan is current and readable, the saving will be smaller. If there are more than 15 work locations per shift, it will be larger.
How to measure your own times before deployment
Choose a week of typical work and, for 20 consecutive queries, record two values: the moment of the query and the moment the dispatcher knows the work location. Also record whether the time included a phone call, because that is usually what lengthens the reading the most.
After the map goes live, repeat the measurement on the same number of queries. A comparison of two series of 20 measurements is enough for a discussion with management, and for a plant director it is a harder argument than any calculation from outside.
It is worth separating simple queries, that is a single work point, from complex ones, such as a permit for a pipeline run or a set of valves. For complex ones the permit outline shows the extent of the work, so the expected saving is the largest.
How the result changes with other assumptions
If there are 8 confirmations per shift instead of 15, the saving falls to 36 minutes per shift, or about 150 hours per year per workstation. If the paper time is 4 minutes and the map time is 1.5, the saving per confirmation is 2.5 minutes.
These variants show that the result is proportional to the number of queries and the difference in times. That is why we do not give one promised figure: we give a way of counting that the controlling department can repeat on its own data.
Dispatcher time saving
| Parameter | Value |
|---|---|
| Work location confirmations per shift | 15 pcs |
| Time from paper plan and phone | 6 min |
| Time to read from the map | 1.5 min |
| Shifts per year | 250 shifts |
Result: 4.5 min per confirmation; 67.5 min per shift; about 281 hours per year per workstation
Note: Sample calculation on working assumptions; the client replaces them with their own measurements.
Video
Frequently asked questions
Where do the 6 and 1.5 minutes come from?
They are working assumptions of the calculation; the client replaces them with their own measurements.
Does the map work for large permits covering many locations?
Yes, a permit covering several locations is drawn as one outline with a 5 m margin around the points.
Is the saving guaranteed?
No, this is a sample calculation. The result depends on the number of queries and the quality of data in your plant.
Let us talk about the map of your plant
We will arrange a short presentation of the isometric map on a sample plant and go through the data that has to be collected in your case.
Let's talk