How to use this list
Go through the list in a meeting with someone from IT, health and safety or maintenance, and mark each point as ready or to be completed. A point that cannot be closed before installation should be moved to a date after installation, but record who is responsible for it. The list concerns the readiness of the site, not of the vendor: the vendor is responsible for the hardware, the instance configuration and the server.
The general rule is that the pilot does not change existing systems. InnerWeb is an independent system that complements access control, time and attendance, HR and ERP, so the list has no points about replacing readers or integrating with those systems. It does have points about people, places and data.
Beacon mounting locations
Localisation in InnerWeb results from signals of many beacons averaged on the map. Inside buildings we recommend one beacon per 100-200 m2, on site roads roughly every 100 m, and the system works without GPS. For this reason, before installation it is worth having a placement plan on the map of the pilot area and confirming with maintenance that the chosen locations are available and safe for installers.
The route-patrol pilot is based on one real route with about 100 beacons, that is one per about 200 m2, at the control points. Check therefore whether the route is current: whether the control points have not been moved and whether the patrol staff actually visit them.
Pilot items to check before the start
Devices, accounts and roles
The LTE watch has its own SIM card, so the inactivity detection pilot does not require integration with the site network. However, devices must be assigned to people, and people must be informed about the purpose of wearing the watch. The route-patrol pilot needs 3 mobile devices and an instance with 10 licences.
The flexible licence counts Active Users: accounts with at least one login in a calendar month, with a minimum of 10 licences in billing. The count includes employees with administrator, security and health and safety roles and coordinators from external contractors. Visitors, contractor employees and drivers are not counted. Prepare the list of people and roles before issuing accounts.
Baseline data and indicators
The route-patrol pilot measures the completeness of patrols and the time to respond to a fault. So that there is something to compare after a few weeks, record the baseline values before the start: how many patrols take place today, how often, and how long it takes to fix a reported fault. Without these figures the morning report will be interesting but will not prove an improvement.
Also decide who receives the morning report and what they do with it. The report shows the manager the effect from the first day, but only if someone reads it and reacts.
Checklist
Video
Frequently asked questions
What should I check first?
The placement plan of the beacons on the map of the pilot area and the list of users with their roles. These two elements determine the installation and the issuing of accounts.
Do I need to change the access control system before the pilot?
No. InnerWeb is an independent system that complements the client's existing systems, so the pilot does not require replacing readers or changing the time and attendance system.
Is a list of 10 people enough?
For most pilots, yes: the billing minimum is 10 licences. What counts, however, is Active Users, meaning accounts with at least one login in a calendar month.
Why record baseline data before the start?
Without baseline values for patrol completeness and time to respond to a fault, it is not possible to show an improvement in the final report.
Let's plan a pilot for your site
Book a conversation with InnerWeb: we will help you select the scope, the number of users and the pilot success criteria for your hall or route.
Let's talk