InnerWeb
Skip to main content

Safety walk with pins on a hall floor plan without 3D: an inspector's scenario

An OHS inspector at a maintenance plant does not have a 3D model of the hall, but has the plan as a file. They set up an audit, walk the hall and pin defects on the floor plan, and the system counts the progress of removing them. We describe this scenario step by step, together with the pitfalls worth knowing before the first walk.

34 min
maximum age of a BLE reading for the location suggestion
Source: feature card
3
audit statuses calculated on read: open, in progress, closed
Source: feature card

Starting point: the floor plan exists, the 3D model does not

This is a deployment scenario for a repair plant, not a description of a finished project. The plant has a hall floor plan in an SVG or raster file, but has not yet built the 3D geometry of the building. This often stops a project from starting, because the team concludes that audits make no sense without a model.

Meanwhile, when a hall has a background plan but no building with 3D geometry, the list of audit buildings returns the non-technical areas of the hall. This means an audit can be set up without a 3D model. The inspector does not wait for a drafter or a supplier, but starts the walk on material the plant already has.

How the audit works: header, reports, plan

An audit groups the reports from a single walk. It has a name, a date, a hall or building, and an auditor. As a result, the findings from Monday's walk do not mix with those from Friday, and in a conversation with the department manager there is no need to reconstruct which defect came from which route.

A report can have a pin on the hall floor plan, and the audit plan shows all reports of that audit with photo thumbnails. This solves the classic problem of a paper list: the description of a machine in the third column from the entrance is read differently by everyone, while a pin points to one place.

Location suggestion from a transmitter

The system can suggest the location of a report from a transmitter, but only under strictly defined conditions. The suggestion fills in the report location when the user's last BLE reading is no older than 34 minutes and comes from the same hall as the one selected in the form. If the inspector changed the hall in the form or stayed in the office for a long time, the suggestion does not appear and the pin is placed by hand.

Progress and status calculated on read

Audit progress is calculated as resolved plus rejected, divided by all reports. The audit status (open, in progress, closed) is calculated on every read and is not stored. An audit that is closed but still has at least one report in progress has the status in progress, so it cannot be treated as finished until the last defect is resolved or rejected.

Time to compile a safety walk report

Time to compile a safety walk reportBefore and after comparison: 90 minutes to compile a report from a paper list versus 15 minutes to review an audit with pins.020406080100minPaper list and spreadsheet: 90 min90 minPaper list and spreadsheetAudit with pins: 15 min15 minAudit with pins
Source: Sample calculation; assumptions of 90 minutes to transcribe the list and 15 minutes to review the audit plan with pins

The course of a single walk

The inspector creates the audit before entering the hall: a name with the date and the name of the department, the selected hall, and their own account as the auditor. Then they follow the route and, for each defect, add a report with a description and a photo and place a pin. At the end they open the audit plan and see the whole picture: the distribution of pins shows whether the defects cluster around one line or are spread evenly.

Such a distribution has analytical value. A cluster of pins at one workstation is a signal to talk about the cause, not only about cleaning. Conversely, an audit where all the pins stand at the entrance usually means the inspector did not get to the depth of the hall, and this is also visible on the plan.

Result: one place that tells the truth about the walk

After the walk the plant has one list with location, photo, status and person responsible, and the progress changes as reports are closed. For the OHS manager it is material for a weekly review, and for the director it is an indicator that does not require manual compilation in a spreadsheet.

The example calculation below shows how much time it takes to compile a report from a paper walk and from an audit with pins. The assumptions are illustrative and should be replaced with measurements from a specific plant.

Pitfalls to know before you start

The first pitfall is a floor plan with too low a resolution: a pin placed on a poor-quality raster loses accuracy, so prepare the background file at a legible scale. The second is changing the hall in the form during a walk, which switches off the transmitter suggestion. The third is confusing rejection with resolution: a rejected report also raises the progress, so the reason for rejection should be recorded.

  • Prepare the hall floor plan at a legible resolution before the first audit.
  • Name audits consistently: department, date, type of walk.
  • Record the reason for every rejected report, because it affects progress.
  • Remember that the transmitter suggestion works only for a fresh reading from the same hall.
Example calculation

Compiling a walk report: paper versus an audit with pins

Assumptions
ParameterValue
Walks per month8 walks
Time to write a report from a paper list90 min
Time to review an audit with pins15 min

Result: 8 walks x (90 - 15) min = 600 min, that is 10 hours a month less work on the report alone.

Note: Sample calculation; the times should be replaced with the plant's own measurements.

Checklist

Video

Frequently asked questions

Can an audit be done without a 3D model?

Yes. When a hall has a background plan but no building with 3D geometry, the list of audit buildings returns the non-technical areas of the hall, so the audit can be set up without a model.

When does the system suggest a location from a transmitter?

When the user's last BLE reading is no older than 34 minutes and comes from the same hall as the one selected in the form. Otherwise the pin is placed by hand.

How is audit progress calculated?

As reports resolved plus rejected, divided by all reports in the audit. The status is calculated on every read.

Let's run a trial walk on your hall plan

Send us the plan as a file and we will show an audit with pins without building a 3D model.

Let's talk