GB2597826A

GB2597826A - Geofencing based visitor tracking and notification system

Info

Publication number: GB2597826A
Application number: GB2107764.9A
Authority: GB
Inventors: Jenke Steven; Evans David
Original assignee: Vistrak Pty Ltd
Current assignee: Vistrak Pty Ltd
Priority date: 2020-06-01
Filing date: 2021-06-01
Publication date: 2022-02-09
Also published as: GB202107764D0; AU2021103006A4; AU2021203581A1

Abstract

A computer implemented system for managing, communicating and tracking visits by a plurality of visitors to a plurality of worksites stores information regarding a plurality of registered visitors who each have a visitor application on a mobile device, visitor information relevant to each worksite, and a worksite identifier for each worksite. A first check-in geofence 820 is defined for a worksite as well as a second allowable movement geofence 830 which encompasses the first check-in geofence zone. The visitor is only permitted to check-in to a worksite if they are detected as within the first check-in geofence zone; and once checked-in, their position is monitored and if they are detected outside the second allowable movement geofence zone the visitor is checked out. As part of the check-in process the visitor has their accreditation checked, or an accreditation process is performed, and is presented with worksite information relevant to their visit. A worksite contact is notified of both arrival and departure of the visitor. The worksite contact is notified of arrival with respect to the first geofence and departure via the second geofence. Further geofences may define subzones of the worksite.

Description

Intellectual Property Office Application No GI321077649 RTM Date:1 December 2021 The following terms are registered trade marks and should be read as such wherever they occur in this document:

BLUETOOTH QR CODE MEACON

Intellectual Property Office is an operating name of the Patent Office www.gov.uk/ipo

GEOFENCING BASED VISITOR TRACKING AND NOTIFICATION SYSTEM

PRIORITY CLAIM

[0001] The present application claims priority from Australian Provisional Patent Application No. 2020901 799 titled "Geofencing Based Visitor Tracking and Notification System" and filed on 1 s' June 2020, the content of which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to managing, communicating and tracking visitors during visits to worksites. In a particular form the present disclosure relates to safely managing, communicating and tracking visitors such as supplier representatives to worksites such as retail stores.

BACKGROUND

[0003] Sales representatives have a key role when visiting stores or worksites to ensure that their products and ranges are supported. Retailers are primarily focussed on best serving customers, and site visits whilst important in supporting the in-store customer experience, create administrative issues in managing visitors. Many sites require the visitor to sign-in, perform induction procedures (e.g. read and acknowledge safety procedures), and indicate who they are visiting. However when visiting large retail stores (e.g. supermarkets and the like) it is not uncommon that a sales representative will have to wait between 2 to 15 minutes to sign in and out. As sales representatives may visit between 8 and 30 stores per week, then waiting around at a store impacts their overall productivity. In some stores, the visitor book is left out to allow visitors to self-sign in but, this provides no confirmation that the visitors have completed visitor induction processes, and in any event many visitors skip over induction and safety procedures to speed up the sign in process. As sales representatives may be visiting 10-15 stores per day, they will not typically remember the store specific emergency points so if an emergency occurs whilst they arc instorc, they will typically be unsure of exactly what they am supposed to do, or where to go, not to mention being aware of their surroundings and the expectations of day to day communication.

[0004] Further, once inside the store, representatives often have navigate through many areas within the store to find their products (e.g. to check stock levels and/or displays), and often must track down their nominated contact person to identify if there are any issues of if there is any information to be passed on. Large retails store (and workplaces) may receive many visitors through the day, and thus when a sales representative arrives, the nominated contact person may not be immediately available. Thus it can take up to 20 min to for the sales representative to make contact with their nominated in-store contact. Alternatively they must wait for the staff contact to arrive and escort them through the store. Further, as the staff contact is often involved with serving customers (or managing the customer experience), such visits can be a distraction to the retail staff, and/or impact store customers. Further in many cases the contact may have no information to pass on, or may be busy with customers or other tasks and be disinclined to engage with the sales representative.

100051 For example one study of almost 500 visitors to 20 retailers identified that: * 46% of visitors did not sign in or out; * 57% of visitors did not make their attendance known to staff; * 38% of visitors were unaware of what areas of the store they were allowed to access and which areas were out of bounds; * 82% of visitors were not aware of safety requirements of the site * 65% of visitors retailer inductions had been expired for more than 3 months; * 20% of visitors did not complete their required work whilst on site; and * 8% intended to not attend (i.e. skip) a scheduled site visit.

[0006] Thus there considerable deficiencies with current systems. From a supplier point of view there is thus substantial wasted time and effort, as well as a lack of visibility of when sales team members are actually visiting a store. From a retailer point of view, they have poor visibility of stores visits, as well as the ability to structure preferred times for supplier and retail staff meetings. Additionally there are significant safety and legal risks associated for both suppliers and retailers with poor compliance to sign-in and sign out procedures, and navigation within stores.

[0007] There is thus a need to provide improved technical solution to manage site visits to retail stores and workplaces, or to at least provide a useful alternative to existing sign-in systems

SUMMARY

[0008] According to a first aspect, there is provided a computer implemented system for managing, communicating and tracking visits by plurality of visitors to a plurality of worksites from comprising: a server system configured to store information on a plurality of registered visitors, a plurality of worksite identifiers, and visitor information relevant to each worksite associated with a worksite identifier, wherein for each worksite a first check-in geofence, and a second allowable movement geofence arc stored, wherein the second allowable movement geofence is the same or encompasses the first check-in geofence zone; a plurality of visitor applications, each configured to execute on a mobile device and registered to a visitor; wherein the visitor applications and server system are configured such that: the visitor is only permitted to check-in to a worksite if a position estimate of the mobile device the visitor application is executing on is within the first check-in geofence zone; and once checked-in, their position is monitored and if they are detected outside the second allowable movement geofence zone the visitor is checked out: on check-in, the system checks that the visitor is accredited to visit the site, and if not, the visitor performs a visitor accreditation using the visitor application, a worksite contact is notified of the arrival of the visitor, and the visitor can access any information relevant to the worksite for the visitor via the visitor application; at the end of the visit the visitor either signs out using the app or the system detects the visitor is outside the second allowable movement geofence zone and signs the visitor out; and on sign-out, the worksite contact is notified the visitor has left the worksite.

[0009] In one form, the second allowable movement geofence is larger than the first check-in geofence zone.

[0010] In one fonn, the visitor application further comprises a check out timer which is configured to start when the visitor is first detected as outside the second allowable movement geofence, and once a pre-defined time out period expires, the visitor's location is checked again, and the visitor is only checked out if they are still outside the outside the second allowable movement geofence. In a further form the pre-defined time out period is 15 minutes or less.

[0011] in one form, each visitor application is configured to send a periodic heartbeat signal to the server, and the site manager is notified if a heartbeat signal is not received a predetermined number of times in a row, or a heartbeat signal is not received for a predetermined time period. In a further form, the pre-defined time period is 15 minutes or less.

[0012] In one fonn, the system is configured to allow a site operator to further define one or more subsitc geofences within the second allowable movement geofence, wherein the system is configured to record a visitor application entering and leaving the respective subzone. In a further form one or more forms for collecting or displaying visitor information are geolocked to one or more of the one or more subsites, and a visitor of a visitor application is prevented from viewing or filling in the form until they are detected as at or within the subsitc. In a further form, the system further comprises one or more visitor registration devices, each located at one of the subsites and configured to store or encode a worksite identifier, and when the visitor is proximal to a visitor registration device the system is configured to record visitor attendance at the subsite by the visitor application detecting the worksite identifier, the visitor application interacting with visitor registration device to obtain the worksite identifier, or the visitor providing a visitor identifier to the visitor registration device.

[0013] According to a second aspect there is provided a computer implemented method for managing, communicating and tracking visits by plurality of visitors to a plurality of worksites from comprising: registering a plurality of visitors and associating a visitor identifier and a visitor application with each registered visitor; registering a plurality of worksites, and associating a worksite identifier with each worksite; storing a first check-in geofence, and a second allowable movement geofence for each worksite, wherein the second allowable movement geofence is the same or encompasses the first check-in geofence zone storing visitor information relevant to each worksite associated with a worksite identifier; checking-in a visitor to a website via the respective visitor's visitor application, where checking-in comprises: obtaining a position estimate of a mobile device the visitor application is executing on, and the visitor is only allowed to check-in if they are within the first check-in geofence zone; checking if the visitor is accredited to visit the site, and if not, the visitor performs a visitor accreditation process using the visitor application, notifying a worksite contact of the arrival of the visitor; providing information relevant to the worksite for the visitor via the visitor application whilst the visitor s at the worksite; monitoring, by the visitor application, the visitor's position, and if the visitor is detected outside the second allowable movement geofence zone the visitor is checked out of the worksite; and notifying the worksite contact that visitor has left the worksite.

[0014] in one fonn, the second allowable movement geofence is larger than the first check-in geofence zone.

[0015] In one form, the visitor application further comprises a check out timer which is configured to start when the visitor is first detected as outside the second allowable movement geofence, and once a pre-defined time out period expires, the visitor's location is checked again, and the visitor is only checked out if they are still outside the outside the second allowable movement geofence. In a further form, the pre-defined time out period is 15 minutes or less [0016] In one form, each visitor application is configured to send a periodic heartbeat signal to the server, and the site manager is notified if a heartbeat signal is not received a predetermined number of times in a row, or a heartbeat signal is not received for a predetermined time period. In a further from the pre-defined time period is 15 minutes or less.

[0017] In one form, the system is configured to allow a site operator to further define one or more subsite gcofences within the second allowable movement geofence, wherein the system is configured to record a visitor application entering and leaving the respective subzone. in a further form, one or more forms for collecting or displaying visitor information are geolocked to one or more of the one or more subsites, and a visitor of a visitor application is prevented from viewing or filling in the form until they are detected as at or within the subsite. In a further form, the method further comprises one or more visitor registration devices, each located at one of the subsites and configured to store or encode a worksite identifier, and when the visitor is proximal to a visitor registration device the system is configured to record visitor attendance at the subsite by the visitor application detecting the worksite identifier, the visitor application interacting with visitor registration device to obtain the worksite identifier, or the visitor providing a visitor identifier to the visitor registration device.

[0018] in one form, the worksite identifier is a two dimensional bar code, such as PDF417 barcode, and the visitor registration device comprises the two dimensional bar code printed on a surface, and the visitor application obtains the worksite identifier by scaiming the two dimensional bar-code. In a further embodiment the visitor's mobile device further comprises a location estimation service, such as a GPS receiver, and on registration of a visitor's attendance and receipt of the worksite identifier by the visitor application, such as by scanning the two dimensional bar code, the location estimation service is activated to log the visitor's location until the visitor signs out, for example by rescanning the two dimensional bar code.

[0019] in one form, on registration any communication is provided to the visitor by use of the visitors registered device allowing the visitor to swipe the communication once to reveal a confirmation acceptance, and pressing a confirmation acceptance communicates the acceptance of the communication to the system [0020] According to a second aspect there is provided a computer apparatus comprising: At least one memory: At least one processor, wherein the processor is configured to perform the method of the second aspect [0021] in one form the computing apparatus the computing apparatus is a mobile computing apparatus configured to execute the visitor application.

BRIEF DESCRIPTION OF DRAWINGS

[0022] Embodiments of the present disclosure will be discussed with reference to the accompanying drawings wherein: [0023] Figure IA is a schematic representation of the system for tracking visits by a plurality of visitors to a plurality of worksites according to an embodiment; [0024] Figure 1B is a flowchart of the operation of the system of Figure IA according to an embodiment; [0025] Figure IC is a workflow diagram for the different components in the system of Figure 1A; [0026] Figure 2 is an representation of the system architecture according to an embodiment; [0027] Figure 3A is a representation of a user interface for a supplier representative according to an embodiment; [0028] Figure 3B is schematic diagram of the interdependencies between the user interfaces of various components of a system for tracking visits by supplier representatives to retail sites according to an embodiment; [0029] Figure 3C is a schematic diagram showing the benefits for the RETAILER and how the interface will support managing, communicating and tracking of visitors; [0030] Figure 3D is a schematic diagram showing the benefits for the SUPPLIERS and how the interface will support managing, communicating and tracking of visitors; [0031] Figure 4A is a representation of information relevant for a supplier representative when making a store visit according to an embodiment; [0032] Figure 4B is a representation of the relevance and dependencies of the information in Figure 4A according to an embodiment; [0033] Figure 5A is a representation of input interfaces for recording arrival of a supplier representative at a retail site according to an embodiment; [0034] Figure 5B is a representation of information provided at store entry for recording arrival of a supplier representative at a retail site according to an embodiment; [0035] Figure GA is a representation of a reporting data cube according to an embodiment; [0036] Figure GB is a representation of the architecture of the reporting system according to an embodiment; and [0037] Figure 7A is a representation of the notification screen on the mobile device showing the process to read, slide and confirm notifications relating to task, commutation and safety requirements according to an embodiment; [0038] Figure 7B is a representation of the tasks screen on the mobile device showing the process to read, comment, add photos and documents, complete and save tasks communication and safety requirements according to an embodiment; [0039] Figure 8 illustrates a map showing a first chcck-in zone (first geofence) and a second allowable movement zone (second geofence) according to an embodiment.

[0040] Figure 9A illustrates a first part of the check-in process according to an embodiment; [0041] Figure 9B illustrates a second part of the check-in process according to an embodiment; [0042] Figure 9C illustrates a first part of the operation process of the app once checked in until checkout according to an embodiment; [0043] Figure 9D illustrates a second part of the operation process of the app once checked in until check-out according to an embodiment; [0044] Figure 9E illustrates a first part of the process when the user closes the app when on site according to an embodiment; [0045] Figure 9F illustrates a second part of the process when the user doses the app when on site according to an embodiment; [0046] Figure 90 illustrates a first part of the process when the user turns off location services when on site according to an embodiment; [0047] Figure 9H illustrates a second part of the process when the user tums off location services when on site according to an embodiment; [0048] Figure 10A illustrates the architecture of an incident report according to an embodiment; [0049] Figure 10B illustrates the architecture of a Health Safety Environment and Quality (HSEQ) audit report according to an embodiment, [0050] In the following description, like reference characters designate like or corresponding parts throughout the figures.

DESCRIPTION OF EMBODIMENTS

[0051] Referring now to Figures IA, IB and IC there is shown a schematic representation, a flowchart and a workflow diagram of a system 1 for managing, communicating and tracking visits by a plurality of visitors to a plurality of worksites. For ease of understanding we will consider the case of a single supplier 70, with multiple supplier representatives (e.g. sales representatives) who visit a plurality of retail sites 82, 84, 86, of a single retailer 80, such as a supermarket retailer with a geographic network of supermarkets (worksites). However it is to be understood that this system can be extended to multiple suppliers and/or multiple retailers 92, and to a range of visitor types and worksite types. For example the worksites could be building sites, childcare centres, industrial sites, hospitals, pharmacies, prisons, etc. Visitors could also be government union, or safety inspectors, parents (for childcare centres), contracted maintenance or repair staff, or even members of the public (for prisons) where it is desirable to register visitors and a site induction is required (or to ensure compliance with safety requirements).

[0052] Referring to Figure 1A, the system 1 is implemented using a plurality of computing apparatus (also referred to as devices, the terms will be used interchangeably) such as a server 10, and computing devices located at supplier headquarters 70, retailer headquarters 80, retail stores 82, 84, 86, 92 and mobile computing apparatus 72, 74, 76, 78, such as mobile phones, smartphones, tablets, and laptops used by supplier representatives and/or retail staff contacts. Each computing apparatus one or more central processing units (CPU) 20, a memory 30, an Input/Output interface 40 for interfacing with input and output devices 50, and a Communications interface 60. Each CPU 10 may comprise an Arithmetic and Logic Unit (ALU) 22 and a Control Unit and Program Counter element 24. The computing apparatus may comprise a single CPU (core) or multiple CPU's (multiple core), or multiple processors. The computing apparatus may be a server system 10, a desktop computer 70, 80, or a portable computer 72, 74, 76, 78, and may use a parallel processor, a vector processor, or be may be part of a distributed (cloud) computing apparatus. In one embodiment the server 10 is a cloud based server apparatus.

[0053] The memory 30 is operatively coupled to the processor(s) 20 and may comprise RAM and ROM components 32, and secondary storage components such as solid state disks and hard disks 34, which may be provided within or external to the device. The memory 30 may be used to store the operating system, databases and additional software modules, services, or instructions to cause the processor to execute a method described herein. The processor(s) 20 may be configured to load and execute the software modules or instructions stored in the memory 30. The various software modules are configured to interface with sensors, process data, query databases, and generate notifications and reports.

[0054] The input and output interface 40 enables connections to input and output devices 60 over wired or wireless connections. Input and output devices 50 may comprise a keyboard, a mouse, and a display apparatus such as a flat screen display (e.g. LCD, LED, plasma, touch screen, etc.), a projector, CRT, etc., including integrated input/output devices such as touch screens. The communications Interface 60 may comprise a network interface and/or communications module for communicating with an equivalent communications module in another apparatus using a predefined communications protocol (e.g. Bluctooth, Zigbee, IEEE 802.15, IEEE 802.11, TCP/IP, UDP, etc.) over wired or wireless links, including 3G/4G/56 links.

[0055] The various computing devices and server 10 are configured to generate notifications, exchange data and generate reports which are sent via the communications interface 60 in each device. The server apparatus 10 is configured to store information on a plurality of registered visitors (i.e. supplier representatives), a plurality of worksite identifiers for each of the retail sites the suppliers may visit, and visitor information relevant to each worksite associated with a worksite identifier (i.e. the information a supplier may need to know when at a particular worksite). The server logs arrivals and departures of visitors to worksitcs, can store and forward messages between store contacts (which we will also refer to as worksite contacts) and visitor representatives, and send notifications to visitors and/or store contacts. The server may also generate reports (scheduled or on demand) which are sent to computing apparatus located at suppliers 70 and retailers 80 for display in user interfaces running on the local computing apparatus.

[0056] A visitor application 214 runs on mobile devices 72, 74, 76 used by supplier representatives and is configured to interface with other devices in the system 1. A store (or worksite) contact application run on mobile devices 78 used by store (worksite) contacts, and similar to the visitor application 214, is also configured to interface with the system 1. The visitor application and store contact application may be separate applications or they may be part of the same mobile user application which provides the different functionality based on the login credentials of the visitor (which for simplicity we will refer to as the user). The communication interface 40 in each device coordinates exchange of data between devices within the system 1. Similarly visitor application 214 may notify the server 10 when they arrive at a worksite, and notifications may be sent to the supplier representative devices 72 for display in the visitor application 214.

[0057] The various computing apparatus, such as the server apparatus 10, visitor registration devices located at worksitcs 82, 84, 86, and mobile devices 72, 74, 76, 78, used by supplier representatives and store contacts to implement an embodiment of the method shown in Figure 1B of Figures 9A to 9H. One or more suppliers 70 and one or more retailers 80 create an account with the system and these details are stored on the server 1. The retailer 80 creates a store profile that includes store specific information for each store 82, 84, and 86. Figure 4A illustrates a range of store specific information that may be included in the store profile and will be relevant to visitor. The store profile also includes the location of the store, and the system assigns a unique worksite identifier. The retailer may also register store contacts and the system may link mobile user devices and/or store contact application to the retailer to enable store contacts to exchange messages and to send/receive notifications. Similarly the supplier creates a profile including visitor specific information. This may include a list of visitor representatives, and the system may link mobile user devices and/or visitor applications to the supplier to enable the exchange of messages with store contacts, and to send/receive notifications such as when a visitor arrives or leaves a store 100581 In one embodiment a visitor registration device 240 is located at each worksite and is configured to store or encode a worksite identifier. Figure 5A illustrates various visitor registration devices 240, and may be a computing apparatus (including a microprocessor or microcontroller based device) or electronic device such as a Near Field Chip (NFC) 510, a keypad for entering a pin number 520, a biometrie (e.g. fingerprint) reader 530, or combined device 532 (keypad and biometric), in this embodiment the visitor provides a visitor identifier to the apparatus such as a pin code, a fingerprint, or an REID or NFC code of the mobile device which can then be provided to the system, such as to a local computing apparatus at the site, and/or back to the server 10. Alternatively the visitor registration device may be a passive (or static) device such as panel with a printed barcodes, including ID and 2D barcodes, RFID tag, text code or other information which the mobile device used by the visitor can scan, sense or interact with to obtain the worksite identifier which can then be either used by the visitor application running on the mobile device and/or sent back to the server 10. Printed 2D barcodes, such as QR codes, Data Matrix, Aztec, Codablock-F, MaxiCode, PDF417, MicroPDF4I7, Han Xin, Dot Codes, and variants such as SnapCodes, and High Capacity Colour Barcodes (e.g. Microsoft Tag) are particularly suitable, as they can typically store (or encode) hundreds and typically a few thousand characters, which is generally sufficient for uniquely identifying the worksite. Further they can be cheaply printed on a panel, and do not require a power supply, enabling 24/7 useability. In one embodiment a PDF417 barcode (ISO standard 15438) is used as the worksite identifier printed on a flat panel (the visitor registration device). PDF417 barcodes have high data capacity (1100 bytes, 1800 characters or 2710 digits), include error correction, and can be relatively compact (and printed in a range of sizes provided the format is adhered to), and can be easily read with a simple linear scan.

100591 Figure 5B shows an embodiment of a visitor registration device 240 comprising a NFC tag and PDF417 code located at a retail store (e.g. near the store entrance). The NFC and PDF417 code 560 encode the worksite identifier which encodes or allows determination of the details 570 such as the company, store name, company number, address, suburb, state, and postcode. When a visitor is proximal to the visitor registration device they can tap the NFC or scan the PDF417 code, the visitor application detects the worksite identifier encoded by the NFC or PDF417 code and sends this to the server 10, which looks up the store information from the store profile, in another embodiment the visitor application interacts with the visitor registration device to obtain the worksite identifier, and sends this to the server 10, which looks up thc store information from thc store profile. Alternatively the store information may be directly encoded in the worksite identifier (e.g. PDF417 can store 1800 characters), in which case the scanner extracts the store details and sends this to the server, or be provided by the visitor registration device to the visitor application over a wireless link. in other embodiments the visitor may provide a visitor identifier (stored with the visitor profile) such as by entering a PIN code on a keypad and/or provide a fingerprint to a biometric scanner. The system then records or logs the visitor attendance (using the visitor identifier) at the worksite including details such as time of entry. The system checks the visitor is accredited and can provide safety information and other messages to the visitor. In some embodiments the visitor must approve or acknowledge receipt of this information. If the visitor is not accredited then they must perform a visitor accreditation using the visitor application.

100601 A photograph of the visitor may also be taken using the visitor application or the visitor registration device to verify the visitor is actually at the retail store (and can be sent back to the server with the worksite identifier). In one embodiment the worksite identifier (e.g. PDF417 code) stores (or encodes) the location of the worksite. In another embodiment the user device includes a location estimation service such as a Global Navigation System (GNS, such as GPS) receiver and provides the user location with the worksite identifier (e.g. PDF417 code) to the server. The server can compare the user location to the worksite location (either known to the system or encoded in the worksite identifier) to verify the visitor is actually at the store. In one embodiment, once the user obtains the worksite identifier as part of the sign-in, for example by scanning a 2D barcode, the location estimation service (e.g. UPS receiver) is turned on, and stays on to log the visitor's location until the visitor signs out, for example by rescaiming the two dimensional bar code. A continuous time series of location estimates could be obtained, or they could be obtained at regular periods (e.g. every minute or every 5 minutes) or at random times during the visit.

[0061] Once the system records arrival of a visitor, a store contact is notified of the arrival of the visitor, and the visitor can access any information relevant to the worksite for the visitor via the visitor application whilst they are in store. Any relevant messages (e.g, safety information) or messages stored for the visitor by the store contact may be forwarded to the visitor, so the visitor can reply or the visitor and store contact can meet face to face and discuss. These messages can be shown in a screen of the visitor's mobile device, or a screen of a visitor registration device. Similarly whilst the visitor is in store they may send messages to the store contact. Notifications can be used to send a request for a meeting or provide the location of the meeting. Geofencing can be used whilst the visitor is on site to prevent entry into prohibited areas, and may notify the visitor and/or store contact if the visitor strays into a prohibited area. This may be implemented using wireless beacons such as Bluetooth based iBeacons or similar technology, and or using GNS based gcolocation.

[0062] Whilst at the store the visitor can perform any tasks in line with the supplier and retailer expectations (check stock levels and restock as required, view presentations and displays, etc.). The visitor application stores and/or allows the visitor to access store information during a site visit, for example to allow them to check safety procedures or relevant locations (e.g. loading bays, amenities). This can be stored by the device, or could be downloaded once a visitor arrives at a store, or served on demand during a store visit. At the end of the visit the visitor either signs out using the visitor registration device or via the visitor application, and on sign-out the store contact is notified the visitor has left the worksite.

[0063] As mentioned above a visitor must be accredited to visit a store. This may require them to log in and review store specific information. Figure 3A is a representation of a user interface of the visitor application 214 for a supplier representative performing accreditation, such as answering questions confirming they are aware of safety requirements for a site visit. Examples of the information they must be aware of for a site visit is displayed in Figure 4A. They may then attend the store and report to a store contact to seek fonvial store accreditation. This may involve reviewing the material, showing the visitor relevant locations/areas (e.g. where to park, loading areas, out of bound areas, evacuation points, etc.). Once the visitor has performed the accreditation the store contact can record the accreditation into the system, and approve future visits by the visitor. The accreditation details may be stored by the visitor application. A visitor schedule can also be stored. The store may also register the phone and biometric information of the visitor for local storage by the visitor registration device to enable offline access. For example retail sites could operate in a local mode, where they locally store accredited visitors, locally record visits and provide notifications locally. The information could be periodically provided to the server as an end of day or end of week aggregated reporting job.

[0064] Figure 1C is a workflow diagram 110 for the different software components in the system of Figure 1A, Figure 2 is a representation of the system architecture according to an embodiment. The system architecture comprises user interface layer 210, the retail visitor management business layer 220 and the infrastructure layer 230, and the visitor registration devices 240. The business layer 220 sits on the infrastmcture layer 230, arid may be a cloud based Software as a Service (SaaS) business layer.

[0065] The user interface layer 210 sits over the business layer 220 and comprises the retailer admin module 150, the retail store module 160 for individual stores and store contacts, a system administrator (V1STRAK Super admin) module 170, the supplier or brand user module 120, and the visitor application 130. The supplier (brand) admin module 120 will typically be used by the headquarters of the stores to record and manage the visitor profiles of their sales representatives. Similarly the retailer admin module is used to record and manage the store profiles for individual stores. The system administrator module 170 is used to manage the set of suppliers and retailers. The visitor application 130 manages visits to retail sites and handles logic of site visits as shown in Figure 1C, in coordination with system application 140. In one embodiment web based user interfaces are provided on supplier devices, retailer devices and mobile (visitor) device, and these are used to interact with the server 10 and core business layers 220. Figure 3B is schematic diagram of the interdependencies between the user interfaces of various components of a system for tracking visits by supplier representatives to retail sites according to an embodiment.

100661 As shown in Figure IC the visitor application 130 records completion of accreditation of a store, records attendance at a store, and manages visitor (REP) check-in at a store with a visitor registration device 240. The system detects the visitor attempting to check in at a store, and checks if their accreditation is valid, and if so creates a new store visit, and queries whether there are any required actions such as acknowledge they are aware of safety details, or specific actions or tasks to be performed during the visit. Figure 4B is a representation of the relevance and dependencies of the information in Figure 4A according to an embodiment. For example this identifies critical information (K) and the relevance (e.g. safety, customer, or operational). This can be used to detemfine which information is displayed to the visitor at site entry as a refresher, or to be explicitly acknowledged.

100671 A store action may be proposed 161 by a store contact using the retail store module 160 prior to visit by a retailer representative. For example they may ask them to restock certain goods, take away returned products, etc. Similarly the retail administrator could propose tasks for the sales representative, such as to check stock levels and in store displays. Next the system manages notifications, such as sending a notification to the store contact that the visitor has arrived, and providing any notifications to the visitor. The visitor then performs store actions and performs a checkout once required tasks are performed. The system logic records the checkout, closes the visit record (i.e. in a database) and manages any notifications, such as a visitor exit alert to the store contact.

100681 The system administration module 140 collects and stores data (in databases or similar data storage) on store visits including time at a store, frequency, schedules, accreditation status and communications, represented in Figure 6A as a data cube 600. Figure 6B is a representation of the architecture of a reporting system 610 according to an embodiment. The trusted data (data cube 600) sits below the business intelligence platform 220 and allows the various uses provide a variety of reports, analysis, dashboards and visualisations. Report can be generated on demand, or provided at scheduled times such as end of month, end of quarter and end of financial year. Various levels of detail can be provided in the reports.

100691 Figure 7A is a representation of the notification screen 710 on the mobile device showing the process to read, slide and confirm notifications relating to task, commutation and safety requirements according to an embodiment. As shown on the notification screen 710, any communication is provided to the visitor by use of the visitors registered device. The visitor can swipe the communication once to reveal a confirmation acceptance 712. Pressing a confintion acceptance communicates the acceptance of the communication to the system, which can trigger a notification to the store contact. Similarly Figure 7B is a representation of the tasks screen 720 on the mobile device showing the process to read, comment, add photos and documents, complete and save tasks, communication and safety requirements according to an embodiment.

100701 in another embodiment, fixed visitor registration devices are not used, and instead the visitor uses an app on a mobile computing apparatus 72 such a smartphonc or tablet, and geo-location and geofencing arc used to check-in a visitor. Figure 8 illustrates a map 810 showing a first check-in zone (first geofence) 820 and a second allowable movement zone (second geofence) 830. A visitor is only permitted to check-in using their app when they are within the first check-in zone 820. Once they are then checked in, they arc allowed to roam the allowed movement zone 830. The second allowable movement geofence zone 830 is the same or encompasses the first check-in geofence zone 820. Typically the allowed movement zone (second geofence) 830 is larger than the first check-in zone (first geofence) 820. If the user exits the allowed movement zone (second geofence 830) they are automatically checked out of the site. This two level geo-fence enables the site administrator to set up a tight first geofence 820 so the user can only check-in when they are at, or very close to the site or very close to a specific location (e.g. a specific office or entrance) but once checked in, they are allowed to walk around the larger site or to walk to a nearby car to pick up additional equipment or farther stores without being automatically checked out (and force to recheck in).

[0071] The geofences may be defined using a central latitude and longitude and radius, or they may define a polygon area by defining latitude and longitude of the vertices of the polygon. The two zones could share the same central latitude and longitude with different radii (e.g. 10m for the first geofence and 100m for the second geofence), or have different centroid locations. When entering geofences the system may perform a check to ensure the first geofence 820 is coincident or wholly contained within the second geofence 830. A user interface may allow the user to select a geometrical shape (circle, square, rectangle, hexagon, etc.) and place it on a map. The user interface may then allow the user to move the shape, adjust the size, and edit the shape by adding or deleting boundary points. Additionally or alternatively a form based interface may be used to allow the user to specify centroids, vertices, radii, etc. In one embodiment the visitor is automatically checked out once they are detected outside the allowed movement zone (second geofence) 830. In another embodiment a check out timer is used, which is started when the user is first detected as outside the allowed movement zone (second geofence) 830. Once the timer expires, their location is again checked, and they are only checked out if they are still outside the allowed movement zone (second geofence) 830. This can prevent an inadvertent checkout due to a poor position estimation, or due to a brief excursion outsidc of thc allowed movement zone (second geofence) 830. In one embodiment, the time out period of the checkout timer is set to a time between 10 seconds and 15 minutes (e.g. 10 seconds, 30 seconds, 1 minute, 2 minutes, 3 minutes, 4 minutes, 5 minutes, 10 minutes or 15 minutes). The GPS almanac takes 12.5 minutes to download, thus a time out period of 15 minutes allows sufficient time for a GPS receiver to perform a cold start and download the full almanac, and reacquire GPS signals to enable position estimation. A time out period of up to 15 minutes would also allow a brief excursion outside of the second checkout zone, for example to visit a nearby shop for food or equipment. In some embodiments the site operator can configure the length of the time out period.

[0072] Estimation of the location of the user mobile device may be performed using the location services on the mobile device (e.g. GPS). In one embodiment locations are obtained using Assisted GPS (AGPS) services to provide faster and/or improved position accuracy. This may include a request to network infrastructure for an A-GPS position or data to assist in obtaining an A-GPS position.

[0073] System operation is further illustrated in Figures 9A to 9H. Figure 9A illustrates a first part of the check-in process 910 and Figure 9B illustrates a second part of the check-in process 912; Figure 9C illustrates a first part of the operation process 920 of the app once checked in until check-out and Figure 9D illustrates a second part of the process 922; Figure 9E a first part of illustrates the process 930 when the user closes the app when on site and Figure 9F illustrates a second part of the process 932; and Figure 9G a first part of illustrates the process 940 when the user turns off location services when on site and Figure 9H illustrates a second part of the process 942, in these embodiments the App 72 is the user app and CRIV1 is the server 10. As illustrated in Figures 9A and 9B, when the user is at a site they open the app and app obtains the user's (or their devices') location, for example by the app making an AGPS request to the device or network. The App then notifies the user of possible sites to check-in to and the user selects a site to check-into. They are then provided a series of forms providing business information, site induction, conditions of entry, reason and purpose for the visit and any check-in actions. When the user has responded to all questions and actions the user is checked in and may now move aroimd the site. Once check-in the site administrator or any other relevant personnel may also notified the visitor is checked-in an onsite. Figures 9C and 9D illustrate the options when the user is checked in. This may include showing their ID, any alerts or tasks, or allow the user to record any notes about their site visit, view and fill out any e-forms, perform hazard reporting, view emergency diagrams, as well as review past site visits and location history. The user can also manually check out, or they will be automatically checked out when the leave the second geofence 830.

[0074] Additionally when on-site, the app sends a periodic heartbeat signal to the server 10. This may be every minute, 2 minutes, event 2.5 minutes, every 5 minutes, etc. If this heartbeat is not received, for example because the user app crashed or was closed by the user, a set number of times in a row, or for a predefined time period (e.g. 10 or 15 minutes) then the site manager is notified the person is on site but is not using the app. This is illustrated in Figures 9E and 9F. As illustrated in Figures 9G and 9H, the app may also be configured to check if location services or the GPS is turned off Similarly if location services are turned off for a predefined time period (or after a predetermined number of checks) then the site manager is notified the person is on site but is not using the app.

[0075] In this embodiment a site may define further subsites (or subzones) within the allowable movement zone (i.e. a site within the site). These sub-sites (or sites within a site) may be a specific point (e.g. a desk or meeting point), a specific room (e.g. a bathroom to be re-supplied or a stock room), a specific floor, or other point of interest. Whilst a GPS location may be used to determine a visitor is at a sub-site location, a visitor registration device 240 as described above, including a PDF417 barcode, or an NFC chip, may be placed at the sub-site to allow the user to check-in when they visit these sub-sites. This avoids issues with poor GPS positioning when indoors. The visitor registration devices could be placed adjacent doorways for rooms or adjacent stairs or elevators for a floor. These then allow the system to verify the visitor has visited specific sites within the overall site e.g. for a cleaner this could be to verify they have checked each bathroom, or a visited a supply room (to restock). Whilst a barcode, or NFC chip may be used, the system could also use GPS positions, or short range wireless beacons such as Bluetooth based i Beacons or similar short range wireless technology, and optical and audio based beacons for sub-sites.

[0076] In some embodiments forms are made available off-site. In other embodiments some forms, or even all forms, are be geo-locked to the check-in zone 820, and/or the allowed movement zone (second geofence) 830, in some embodiments forms and tasks are further limited to specific subsites (a subzone), for example if there are additional hazards and safety requirements associated with a subsitc. In these embodiments the visitor will be presented and required to complete bespoke electronic forms and tasks that are locked to the site (or sub-site) via the location services, and can only be completed whilst they are present. These electronic forms and task are not presented to the visitor if they are not checked-in and are away from the site (or subsitc). That is the user can only fill them out or view them (or confirm viewing them) when in the relevant zone or zones (including subsite zones).

[0077] Forms which may be geolocked include site inductions forms, site visit report forms, incident report forms, and Health Safety Environment and Quality (HSEQ) audit forms. Figure 10A illustrates the architecture of an incident report according to an embodiment. The app provides a form which can be used by a site manager or contractor to report an incident. In one embodiment the form captures data such as site details, author (reporter), incident type, contact details, incident details, comments and photos. Some data may be prefilled by the app such as the author, and contact details, and the form can be configured by the site operator to specify what data is required (e.g. incident types). The system then generates an incident report from the form data and distributes the incident report for example to a site supervisor, regional manager, safety manager and others. They system allows the safety manager to review the incident and take remedial action as required, and performs logging and timestamping to enable generation of additional reports, for example to meet work safety reporting requirements. Figure I OB illustrates the architecture of a Health Safety Environment and Quality (HSEQ) audit report according to an embodiment. Similarly to the incident report the app is configured to provide a site customised form to allow a nominated user, such as a site manager, to generate a HSEQ audit report. The system is then configured to distribute the report and ensure all relevant parties review and resolve any issues, and provide logging to support generation of reports to official bodies.

[0078] The system can be used for retail sites as well as building sites and allows induction record details to be embedded into each visitor profile and can be validated against the site's own or a 3' party database via 'API'. The system provides multiple features in this context. These include that: * Multiple cards can be uploaded: * All Visitor profiles are centrally loaded 8]; editable; * All visits date and time stamped from arrival to departure * All activity (alerts and acknowledgements) in the platform is date and time recorded; * Auto Check Out feature * Visitors details and visit records private and secured * Unique Visitation -signed in to one site at a time * Visitor arrival & on-site visibility with reporting * Restrict site access as required via Grey and Black-Lists * Secure site logs, preventing privacy infommtion being released [0079] In one embodiment the system is configured to allow a company to invite a contractor to join the system, and delegate management of contractor employees to the contractor. The contractor completes all relevant pre-screening (users, safety, etc.) after which the company approves the contractor. The contractor is then provided with login details and the system gives the authorisation to manage all of their teams. This thus allows the company (site owner) to push the accountability back to the contractor for compliance with safety and site requirements. The system then provides induction questions on a reoccurring timeframe and manages the paperwork compliance to ensure the company, contractor and the contractor's employees are operating safely and legally. When an employee of the contractor visits a site, the application checks the company and the individual profile prior to allowing entry to the site.

[0080] The system provides real-time delivery of safety notifications and tasks upon arrival and can be initiated at either State, Region or Site level. Visitors and contractors using their mobile device are required to acknowledge receipt upon site entry. Site administrators can upload business specific electronic forms to be completed by the visitors based on the visitor's profile whilst on site, and can set location specific access (e.g. gco-locked or not). These can be geo-locked to specific sub-sites. Dynamic (customisable) forms can be used to complete anything from a checklist for Site Supervisors, client update reports through to HSEQ checks. All forms may be available as a PDF (email) or live in a client web page. The server 10 tracks visits, forms, and may implement a business intelligence reporting platform (for example using Microsoft Poweriff) to provide both live and regular (e.g. weekly and monthly) reports.

100811 The system described herein provides numerous advantages over existing systems. It steam lines the visitor process, improves safety, communication and security, provides real-time analytics and provides improved productivity to both suppliers and retailers. Further it can be used at a range of worksitcs (building sitcs, childcare centres, industrial sites, hospitals, pharmacies, prisons, etc.) and visitor types (suppliers, inspectors, maintenance, parents, general public, etc.). Figure 3C is a schematic diagram showing the benefits for the RETAILER and how the interface will support managing, communicating and tracking of visitors and Figure 3D is a schematic diagram showing the benefits for the SUPPLIERS and how the interface will support managing, communicating and tracking of visitors. Advantages include no wait time to sign in and out for visitors, automatic entry and exit notifications to visitor supervisors and staff contacts, reduced chasing of store contacts, and allows visitors or staff contacts to pre-book appointments. The system can be implemented using mobile application (App) and web based interfaces and deployed on defence grade secure servers. The visitor registration devices include a worksite identifier (e.g. PDF417) and can be a small non-obtrusive plaque (e.g. PDF417 code or similar), or more sophisticated electronic devices, including NFC, pin code and biometric scanners, and allows visitor entry/exit to be recorded when arriving/leaving (either in conjunction with the visitor application, or a stand-alone recordal). The worksite identifier can comprise data identifying the store and location. A GNS (or GPS) receiver or a photo of the user can also be sent to the server to verify the user is at the store. In some embodiments locations and multiple geo-fences may be used instead of visitor registration devices. This allows the use of a first check-in zone (first geofence) and a second allowable movement zone (second geofence) typically larger than the first geofence. Visitor registration devices can then be used to check the visitor visits specific sub-sites within the overall site (e.g. a specific room or floor). The system can automatically notify store contacts of the arrival and departure of visitors. The message store and forward function also allows store contacts to automatic notify visitors of issues on arrival. Further the safety of visitors is increased as all visitors are pre-inducted and accredited, and they always have access to relevant safety information via the visitor App. The app can be used to alert them in emergency situations and make them aware of safe zones and out of bound areas. The visitor can be made aware of security requirements (e.g, out of bound areas) via the app (e.g. they may be provided with a marked up site map) and/or geofencing and geotracking can be used to enforce compliance with notifications issued if the visitor enters out of bound areas. The system allows visits information to be recorded centrally, and enables live/realtime reporting of visits. Users can customise their reporting dashboard, generate daily/weekly exception reporting, an optimise route scheduling for a sales representative.

[0082] In some cases, a single embodiment may, for succinctness and/or to assist in understanding the scope of the disclosure, combine multiple features. It is to be understood that in such a case, these multiple features may be provided separately (in separate embodiments), or in any other suitable combination. Alternatively, where separate features are described in separate embodiments, these separate features may be combined into a single embodiment unless otherwise stated or implied. This also applies to the claims which can be recombined in any combination. That is a claim may be amended to include a feature defined in any other claim. Further, a phrase referring to "at least one of' a list of items refers to any combination of those items, including single members As an example, -at least one of a, b, or c" is intended to cover: a b, c, a-b. a-c, b-c, and a-b-c.

[0083] Those of skill in the art would understand that infonnation and signals may be represented using any of a variety of technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof [0084] Those of skill in the art would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software or instructions, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

[0085] The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. For a hardware implementation, processing may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), proccssors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof. Software modules, also known as computer programs, computer codes, or instructions, may contain a number a number of source code or object code segments or instructions, and may reside in any computer readable medium such as a RAM memory, flash memory, ROM memory, EPROM memory, registers, hard disk, a removable disk, a CD-ROM, a DVD-ROM, a Blu-ray disc, or any other form of computer readable medium. In some aspects the computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media). In addition, for other aspects computer-readable media may comprise transitory computer-readable media (e.g., a signal). Combinations of the above should also be included within the scope of computer-readable media. In another aspect, the computer readable medium may be integral to the processor. The processor and the computer readable medium may reside in an ASIC or related device. The software codes may be stored in a memory unit and the processor may be configured to execute them. The memory unit may be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.

[0086] Further, it should be appreciated that modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by computing device. For example, such a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.), such that a computing device can obtain the various methods upon coupling or providing the storage means to the device. Moreover, any other suitable technique for providing the methods and techniques described herein to a device can be utilized.

[0087] In one form the invention may comprise a computer program product for performing the method or operations presented herein. For example, such a computer program product may comprise a computer (or processor) readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein For certain aspects, the computer program product may include packaging material.

[0088] The methods disclosed herein comprise one or more steps or actions for achieving the described method. The method steps and/or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.

[0089] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory) and the like. Also, "determining" may include resolving, selecting, choosing, establishing and the like.

[0090] Throughout the specification and the claims that follow, unless the context requires otherwise, the words "comprise" and "include" and variations such as "comprising" and "including" will be understood to imply the inclusion of a stated integer or group of integers, but not the exclusion of any other integer or group of integers.

[0091] The reference to any prior art in this specification is not, and should not be taken as, an acknowledgement of any form of suggestion that such prior art forms part of the common general knowledge.

[0092] It will be appreciated by those skilled in the art that the disclosure is not restricted in its use to the particular application or applications described. Neither is the present disclosure restricted in its preferred embodiment with regard to the particular elements and/or features described or depicted herein. It will be appreciated that the disclosure is not limited to the embodiment or embodiments disclosed, but is capable of numerous rearrangements, modifications and substitutions without departing from the scope as set forth and defined by the following claims.

Claims

CLAIMS1. A system for managing, communicating and tracking visits by plurality of visitors to a plurality of worksites from comprising: a server system configured to store information on a plurality of registered visitors, a plurality of worksite identifiers, and visitor information relevant to each worksite associated with a worksite identifier, wherein for each worksite a first check-in geofence, and a second allowable movement geofence are stored, wherein the second allowable movement geofence is the same or encompasses the first check-in geofence zone; a plurality of visitor applications, each configured to execute on a mobile device and registered to a visitor; wherein the visitor applications and server system are configured such that: the visitor is only permitted to check-in to a worksite if a position estimate of the mobile device the visitor application is executing on is within the first check-in geofence zone; and once checked-in, their position is monitored and if they are detected outside die second allowable movement geofence zone the visitor is checked out; on check-in, the system checks that the visitor is accredited to visit the site, and if not the visitor performs a visitor accreditation using the visitor application, a worksite contact is notified of the arrival of the visitor, and the visitor can access any information relevant to the worksite for the visitor via the visitor application; at the end of the visit the visitor either signs out using the app or the system detects the visitor is outside the second allowable movement geofence zone and signs the visitor out; and on sign-out, the worksite contact is notified the visitor has left the worksite.
2. The system as claimed in claim I herein the second allowable movement geofence is larger than the first check-in geofence zone.
3. The system as claimed in claim 1 or 2, where die visitor application further comprises a check out timer which is configured to start when the visitor is first detected as outside the second allowable movement geofence, and once a pre-defined time out period expires, the visitor's location is checked again, and the visitor is only checked out if they are still outside the outside the second allowable movement geofence.
4. The systcm as claimed in claim 3. wherein the pre-defined time out period is 15 minutes or less.
The systcm as claimed in any one of claims 1 to 4, wherein each visitor application is configured to send a periodic heartbeat signal to the server, and the site manager is notified if a heartbeat signal is not received a predetermined number of times in a row, or a heartbeat signal is not received for a predetermined time period.
The system as claimed in claim 5, wherein the pre-defined time period is 15 minutes or less.
7. The system as claimed in any one of claims 1 to 6, wherein the system is configured to allow a site operator to further define one or more subsite geofences within the second allowable movement geofence, wherein the system is configured to record a visitor application entering and leaving the respective subzone.
8. The system as claimed in claim 7, wherein one or more forms for collecting or displaying visitor information are geolocked to one or more of the one or more subsites, and a visitor of a visitor application is prevented from viewing or filling in the form until they are detected as at or within the subsite.
9. The system as claimed in claim 8, further comprising one or more visitor registration devices, each located at one of the subsites and configured to store or encode a worksite identifier, and when the visitor is proximal to a visitor registration device the system is configured to record visitor attendance at the subsite by the visitor application detecting the worksite identifier, the visitor application interacting with visitor registration device to obtain the worksite identifier, or the visitor providing a visitor identifier to the visitor registration device.
10. A computer implemented method for managing, communicating and tracking visits by plurality of visitors to a plurality of worksites from comprising: registering a plurality of visitors and associating a visitor identifier and a visitor application with each registered visitor; registering a plurality of worksites, and associating a worksite identifier with each worksite; storing a first check-in potence, and a second allowable movement potence for each worksite, wherein the second allowable movement geofence is the same or encompasses the first check-in potence zone storing visitor information relevant to each worksite associated with a worksite identifier; checking-in a visitor to a website via the respective visitor's visitor application, where checking-in comprises: obtaining a position estimate of a mobile device the visitor application is executing on, and the visitor is only allowed to check-in if they are within the first check-in geofence zone; checking if the visitor is accredited to visit the site, and if not, the visitor performs a visitor accreditation process using the visitor application, notifying a worksite contact of the arrival of the visitor; providing information relevant to the worksite for the visitor via the visitor application whilst the visitor is at the worksite; monitoring, by the visitor application, the visitor's position, and if the visitor is detected outside the second allowable movement geofence zone the visitor is checked out of the worksite; and notifying the worksite contact that visitor has left the worksite.
11. A computer implemented method as claimed in claim 10, wherein the second allowable movement geofence is larger than the first check-in geofence zone.
12. A computer implemented method as claimed in claim 10 or 11, where the visitor application further comprises a check out timer which is configured to start when the visitor is first detected as outside the second allowable movement geofence, and once a pre-defined time out period expires, the visitor's location is checked again, and the visitor is only checked out if they are still outside the outside the second allowable movement geofence.
13. A computer implemented method as claimed in claim 12, wherein the pre-defined time out period is 15 minutes or less.
14. A computer implemented method as claimed in any one of claims 10 to 13, wherein each visitor application is configured to send a periodic heartbeat signal to the server, and the site manager is notified if a heartbeat signal is not received a predetermined number of times in a row, or a heartbeat signal is not received for a predetermined time period.
15. A computer implemented method as claimed in claim 14, wherein the pre-defined time period is 15 minutes or less.
16. A computer implemented method as claimed in any one of claims 10 to 15, wherein the system is configured to allow a site operator to further define one or more subsitc geofences within the second allowable movement potence, wherein the system is configured to record a visitor application entering and leaving the respective subzone.
17. A computer implemented method as claimed in claim 16, wherein one or more forms for collecting or displaying visitor information are geolocked to one or more of the one or more subsites, and a visitor of a visitor application is prevented from viewing or filling in the form until they are detected as at or within the subsite.
18. A computer implemented method as claimed in claim 17, further comprising one or more visitor registration devices, each located at one of the subsites and configured to store or encode a worksite identifier, and when the visitor is proximal to a visitor registration device the system is configured to record visitor attendance at the subsite by the visitor application detecting the worksite identifier, the visitor application interacting with visitor registration device to obtain the worksite identifier, or the visitor providing a visitor identifier to the visitor registration device.
19. A computer apparatus comprising: At least one memory; At least one processor, wherein the processor is configured to perform the method of any one of claims 10 to 18.
20. The computing apparatus as claimed in claim 19, wherein the computing apparatus is a mobile computing apparatus configured to execute the visitor application.