How Inspections Work

Every secure and reliable organization will have regular inspections of its assets. This may be a dedicated guard patrolling the premises, it may be an inspector collecting data about assets, or it may be an engineer performing a periodic quality check of various systems.

The Tour tab is where we set up these inspection "tours". It's called a tour because these inspections go on a route from one asset or location to another. The locations can be different offices, different customer sites, different rooms, different assets in a room - or even virtual assets on a single computer. At each stop ("checkpoint") the inspector scans a QR code (or taps an NFC tag) and it automatically registers you as visiting that checkpoint.

At this point it would either tell you to go to the next location / asset, or it will present you with a checklist of things to check.

If there's a checklist then it will ask you for each checklist item, one at a time. There you can specify whether the inspection passed or failed, and if failed you can provide details and a photo to backup the issue. The system will automatically create a Service Request if the inspection failed, copying over the details and the photo so it can be sent to an asset supervisor for either further investigation or to create a work order.

A checklist item can also be configured to collect an instrument reading - perhaps you'll enter a temperature reading in there, the fuel level of a car, the estimated crowd size... any variable can be entered and stored against an asset's Instruments area automatically. What's more, if that instrument reading is configured with triggers, then your checklist entry could automatically trigger a notification, work order or other action in the system.

Once all the checklist items are entered, it will tell you what the next checkpoint is. There you will scan the next checkpoint QR code and the process will continue.

After the last checkpoint has been reached, the tour will be marked as complete.