AU2017200943A1 - A System for Measuring and Managing Driver Performance - Google Patents

Abstract

A system for measuring and managing vehicle driver performance of the present invention directed towards fatigued commercial drivers and aims at minimizing road accidents and fatalities through a comprehensive fatigue management program.

Description

ι 2017200943 10 Feb 2017

A SYSTEM FOR MEASURING AND MANAGING DRIVER PERFORMANCE TECHNICAL FIELD

[0001] The present invention relates to a system for measuring and managing driver performance.

BACKGROUND ART

[0002] Vehicle fleet information systems are available. One such system is centralised online, removing the need to install any software or applications. All fleet management features and modules are easily accessible, 24-7 anywhere in the world, by all users. The range of tools and modules includes: • GPS tracking and history replay • Waypoint (geo-fencing) management • Performance dashboards • Job dispatch and planning • Non-conformance recording and corrective action management • Live fatigue management • Maintenance scheduler • Mass management • Speed alerts • Route management • Exception and alerts reporting • Driver management • Refrigerated temperature monitoring [0003] A portion of this conventionally available vehicle fleet management system includes a driver fatigue solution which allow an employer to: • Implement a fatigue management system • Electronically manage work diary checks • Reduce time and resources spent managing fatigue compliance • Easily keep track of non-conformance [0004] The driver fatigue solution is available in two different models, a standalone system assisting managers when planning and reviewing work diaries, as well as an integrated system 2 with fleet management that are based about an in-vehicle touch screen. 2017200943 10 Feb 2017 [0005] Both systems are compliant with current fatigue laws and support all schemes operating across Australia. The driver fatigue solution is equipped with in-vehicle warning systems to alert drivers when breaks are due. Visible pop-up prompts and audible messages proactively warn drivers of upcoming rest periods and continue until breaks are taken.

[0006] It will be clearly understood that, if a prior art publication is referred to herein, this reference does not constitute an admission that the publication forms part of the common general knowledge in the art in Australia or in any other country.

SUMMARY OF INVENTION

[0007] The present invention is directed to a system for measuring and managing driver performance, which may at least partially overcome at least one of the abovementioned disadvantages or provide the consumer with a useful or commercial choice.

[0008] With the foregoing in view, the present invention in one form, resides broadly in a system for measuring and managing vehicle driver performance, the system including a wearable electronic device operating a client software application to capture information relating to at least one biometric parameter of a vehicle driver, a central software application operating on a central computing device or network with which the client software application of the wearable electronic device is associated such that the wearable device communicates with the central software application operating on the central computing device or network to capture information relating the at least one biometric parameter of the vehicle driver and transmit captured information to the central software application in order to measure and preferably monitor vehicle driver performance.

[0009] In a more particular form, the present invention resides in a system for measuring and managing vehicle driver performance, the system including a wearable electronic device to capture information relating to at least one biometric parameter of a vehicle driver, a personal computing device operating a client software application with which the wearable electronic device is associated, a central software application operating on a central computing device or network such that a vehicle driver is required to sync the wearable device with the client software application and the client software application communicates with the central software application operating on the central computing device or network to capture information relating the at least one biometric parameter of the vehicle driver and transmit captured information to the central software application in order to measure vehicle driver performance. 3 2017200943 10 Feb 2017 [0010] In an alternative aspect, the present invention resides in a system for measuring and managing vehicle driver performance, the system including a portable electronic device operating a client software application to at least capture information relating to at least one biometric parameter of a vehicle driver, a central software application operating on a central computing device or network with which the portable electronic device is associated, such that the portable device communicates with the central software application operating on the central computing device or network to capture information relating the at least one biometric parameter of the vehicle driver and transmit captured information to the central software application in order to measure vehicle driver performance.

[0011] The system for measuring and managing vehicle driver performance of the present invention is directed towards capture of information in relation to particularly professional drivers to assess their level of fatigue or at least work hours. The aim of the system is to provide a simple to use but pervasive system to capture information relating to particularly driver fatigue levels to minimize road accidents and fatalities through a comprehensive fatigue monitoring and management system. The system is aimed at answering the risk that “moonlighting” truck drivers pose to road users and chain of responsibility issues with transport companies through driver management and reporting.

[0012] Where commercial drivers lack sleep and are fatigued they cause accidents on roads. The system of the present invention aims at minimising these risks by providing a system allowing drivers to monitor vehicle driver performance and demanding compliance with Heavy Vehicle Driver Fatigue (HVDF) laws in Australia. The system preferably requires each driver to clock on and off before a journey and tracks their travel and rest times. This allows the system to advise the driver when they need to rest for a safe journey and if they do not rest when required to. This will normally be achieved through the preferred client software application notifying directly a system administrator (normally the employer commercial trucking company) to let them know their driver is not complying and/or escalating action in relation to a driver such as disabling access to the vehicle and/or preventing operation of the vehicle as well as notifications. This also allows the companies to show the community and authorities they are implementing best practices for fatigue management and accountability of their drivers for road safety.

[0013] Moreover if the drivers have been working for another company that day, this activity will show the system administrator if that driver has already exceeded their daily limit of behind the wheel driving time before taking on a new journey. The system can therefore be used to create a comprehensive network whereby all trucking companies can regulate the driver 4 behaviour of commercial contractors. 2017200943 10 Feb 2017 [0014] Currently, there is no communication between competitor transport companies which ensures that subcontracting drivers haven’t been driving for another company that week, allowing drivers to work continuously between different transport companies.

[0015] The system of the present invention will typically include hardware and associated software designed to utilise the hardware capabilities in order to collect information and to police compliance with recommendations as to work/rest balance and other health or cognition or performance criteria in order to reduce the incidence of vehicle accidents and fatalities, particularly in relation to professional drivers both within an organisation and between different organisations.

[0016] The system of the present invention will normally require a driver to login or receive authorisation at the start of every trip, work day or whatever other period is being measured. Information is typically collected while the driver is logged into the system and then the driver will typically logout or end the connection when the trip or a portion of the trip or whatever other period is being measured, ends in order to capture information about the driver whilst working.

[0017] The information that may be collected using the system includes time periods, distances, biometric data relating to the driver and the like. The data may be in relation to the driver, the vehicle being driven and/or trip parameters which are preferably or maintained in order to ascertain the periods of work and/or rest of drivers in order to ensure that the drivers are not exceeding safety requirements or recommendations in relation to time periods work and rest periods and the like.

[0018] The system of the present invention may additionally be utilised in order to keep records in relation to driver performance, vehicle history or any other information that may be collected using the system. A biometrioc reader may be used for example to ensure that a particular driver booked for a job is the driver completing the job, initially and/or at one or more other times during the job. A transport company may for example have a biometric reader kiosk or similar to allow drivers to be identified using biometric data specific to them.

[0019] Information can be entered into the system from other external sources in addition to the information captured within the system and the possible external sources may include medical records, police or other law enforcement records and the like, in order to give or maintain a history of driver performance. 5 2017200943 10 Feb 2017 [0020] The system of the present invention includes a portable or wearable electronic device to capture information relating to at least one biometric parameter of a vehicle driver. The information captured relating to the at least one biometric parameter of the vehicle driver may be used for any purpose but preferably, is at least used to identify the driver. The information captured can also be recorded in order to monitor or measure performance of the driver and/or a vehicle.

[0021] Preferably, the at least one biometric parameter of the vehicle driver is used to identify the driver to the central software application in order to keep track of the driver and statistics relating to driver performance.

[0022] According to preferred embodiments of the present invention, the electronic device can be a wearable electronic device which is associated with the central software application, the electronic device can be a wearable electronic device which is associated with a portable electronic device which is in turn associated with the central software application or alternatively, the electronic device can be a portable electronic device (not wearable) which is associated with the central software application.

[0023] Normally, a system including at least a wearable electronic device is preferred because in this way, a wearable electronic device can be carried with the driver easily and is less likely to be forgotten, misplaced or lost. Therefore, in addition to the central software application operating on a central computing device or network, one or more electronic devices operating a client software application can be provided within the system of the present invention. In its simplest form, the present system may include a wearable device with all functionality, operating a client software application in order to communicate directly (through an appropriate communications network) with the central software application operating on a central computing device or network. Where more than one electronic device is provided, typically appropriate communications pathways can be provided between the more than one electronic device.

[0024] Importantly, the function of the one or more electronic devices which are in communication with the central software application operating on the central computing device or network is to capture information about at least one biometric parameter of the driver firstly to identify the driver within the system and then secondly to capture information in relation to driver performance either physiological performance or operational performance. The one or more electronic devices are therefore expressly configured to achieve these aims. The configuration of the electronic devices will typically differ depending upon the type of biometric parameter to be captured. One electronic device may also be capable of capturing information in 6 relation to more than one biometric parameter. 2017200943 10 Feb 2017 [0025] For example, in relation to the capture of information relating to a biometric parameter which can be used to identify a driver, the simplest biometric parameters which could be used include a fingerprint, voice print or retinal scan as examples. Although any biometric parameter which could be used to uniquely identify the driver could be captured, these three biometric markers represent the most commonly conventionally used identification biometric parameters.

[0026] Other biometric parameters about which information could be captured include heart rate, movement, breathing, energy usage in terms of calories or kilojoules, hours slept, quality of sleep, anxiety levels or the like. These biometric parameters would not generally be used to identify the driver but more to monitor the driver’s physiological performance.

[0027] Therefore, an appropriate electronic device or device with an appropriate information capture mechanism will typically be provided depending upon the information to be captured by the device. For example, in order to capture fingerprint information, this may be most easily captured with an electronic touch screen display of a computing device such as a smart phone, tablet or alternatively, a wearable electronic device having some form of touch screen to allow capture of finger print information. In order to capture voice information, a microphone may be provided. Further, in order to capture retinal scan information, a camera may be provided.

[0028] Therefore, as can be seen, the information capture mechanism will largely be dependent upon the biometric parameter in relation to which information is to be captured. In one particularly preferred embodiment, a single device such as a smart phone or tablet or the like can provide a touchscreen display, a microphone and a camera so that any one or more of fingerprint information, voice print information or retinal scan information can be captured using a single device.

[0029] In relation to the information captured relating to biometric parameters used to monitor physiological performance, these may be best monitored or information may be best captured using a wearable device as close contact with the driver’s body is typically required in order to monitor these parameters effectively and/or accurately.

[0030] Wearable devices that are capable of information capture in relation to biometric parameters used to identify driver and/or to capture information in relation to biometric parameters used to monitor physiological performance may also be used. Such a device will typically include GPS functionality, heart rate monitor, step counter, energy usage counter, 7 2017200943 10 Feb 2017 active time tracker as well as a recording function for any or all of the above could be used. A device such as this will typically allow the recording of information, the transmission of information captured, allow notifications to be made to the device either from the client software application operating on the device and/or from the central software application, and may link to other electronic devices such as a smartphone or tablet in order to receive telephone calls or SMS messages. Device such as this will normally have a touchscreen display to allow both import and display of information, a sleep monitor and will typically sync wirelessly with a smart phone, tablet or computer. Further, a wearable device such as this will preferably include at least one accelerometer. The wearable device may also monitor physiological performance during different periods, for example during sleep.

[0031] In order to control or allow the information capture of the at least one, and typically multiple biometric parameters used to identify the driver and monitor physiological performance, the wearable or portable electronic device will typically operate a client software application which allows capture of biometric information as well as control communication and information transfer with the central software application either directly or through at least one other electronic device. The client software application will normally utilise the hardware components provided on the electronic device in order to ensure that any required information is either captured or entered so that it may be used as required and/or transmitted as required in order to monitor the performance of the driver.

[0032] As mentioned above, the portable electronic device can be a smart phone or tablet or the like with which a wearable electronic device is associated and may in some instances be a wearable device having integrated functionality as outlined above and which does not require association with a smart phone or tablet or the like in order to operate within the system.

[0033] Normally, the client software application is a software application which is downloadable to one or more wearable or portable electronic devices and which allows interfacing and access to functionality of the central software application provided at a central computer server.

[0034] The client software application will preferably be available through an application distribution platform, which is typically operated by the owner of a mobile operating system, such as the Apple App Store, Google Play, Windows Phone Store and BlackBerry App World. The client software application of the present invention will normally be downloaded from the application distribution platform to a target wearable or portable electronic device. 8 2017200943 10 Feb 2017 [0035] Once downloaded, the client software application will normally be stored in memory and have access to at least one processor in order to operate. The driver will normally interact with the client software application through a number of interfaces generated and displayed on a display of the particular piece of hardware upon which the client software application is operating. Therefore, the interaction with the client software application will normally be interface driven.

[0036] Each user of the system, typically each driver or each potential driver will create or have created an individual profile including information which is stored electronically in relation to a particularly unique identifier identifying that profile as belonging to a particular driver or potential drop. Normally, each driver or potential driver will create a profile through either the client software application but may do so through the central software application, or the system administrator may set up drive all potential driver profiles.

[0037] During setup, appropriate identifying information will normally be captured and recorded in each individual profile and against which a later login request can be compared. Normally, each individual profile is saved in at least one database associated with or accessible by the central software application operating on the central computer server. The information captured by the electronic devices within the system normally transmitted to the central software application and saved against or in the individual profiles so that the system administrator can search records and produce reports or monitor the performance of drivers through the information.

[0038] According to a preferred embodiment of the system of the present invention, the login or authorisation process is particularly important as it is this process which will identify a particular driver within the system. The login or authorisation process preferably also begins the information capture of biometric parameters for monitoring purposes, both physiological monitoring and operational monitoring within the system.

[0039] Normally, a driver will log into the system when their employment or trip begins and will log out when complete or at one or more particular milestones. This will allow the system to track particularly the time that a driver works in order to monitor for fatigue. Information in relation to one or more biometric parameters is typically captured while the driver’s log into the system.

[0040] Alternatively, a separate “begin” or “start” and “end” or “stop” procedure may be used but this is less preferred as it may allow manipulation of the information capture process in 9 order to give false or misleading information. 2017200943 10 Feb 2017 [0041] According to a particularly preferred embodiment, the login process will typically capture one or more uniquely identifying biometric characteristics of a particular driver as outlined above. Other interfaces are preferably provided within the client software application to allow entry of data or information into the client software application of various types such as food or liquid intake or other parameters that cannot be captured using direct measurement of biometric parameter.

[0042] A dashboard interface is typically provided by the client software application allowing a user to view a visual display of information or statistics in relation to information captured.

[0043] The client software application of the present invention preferably captures information and then transmits that captured information to the central software application for recording, monitoring and/or manipulation. The client software application may also receive or collect information from a wearable device and provide information entry, display and transmission functionality. Again however whether the client software application captures in transmits the information directly to the central software application or receives captured information from a wearable device in transmits that information to the central software application depends largely upon the configuration of the system used, in particular whether one or more electronic devices are provided. It is clearly preferred that fewer electronic devices be provided in that a driver only has one electronic device, preferably a wearable electronic device that allows all functionality as this will minimise the number of devices which the driver has to keep track of.

[0044] Therefore, it should be relatively clear that the system of the present invention is preferably used to capture two types of information, a first type of information used to identify a particular driver to the system and a second type of information collected in an ongoing manner in relation to physiological or operational performance.

[0045] The system of the present invention will also normally allow analysis of any information collected. It may be important operationally such as for example information captured may be used to log work hours for payroll purposes and/or create a driver history record. The system of the present invention may also provide information to the driver such as provide traffic information or routing information or warnings as to hazardous situations that may occur from time to time. 10 2017200943 10 Feb 2017 [0046] The system of the present invention may also be used to ensure that drivers operate within the correct geographic area and do not stray into the geographic areas of other drivers where this is appropriate.

[0047] The electronic device used by the driver may include other ancillary functionality which may be useful such as breathalyser capability, a visual acuity test, a mental acuity test, cognition testing, drug analysis or the like as these can be used to ensure driver compliance with safety requirements or regulations.

[0048] Still further, the client software application of the present invention can be used to send and/or receive instructions or notifications to and from the central software application in order that an employer can maintain contact and instruct, notify or interact with individual drivers.

[0049] The system of the present invention can include a booking system according to which, customers or employers may be able to drivers based on the availability or a performance rating in any one or more particular areas.

[0050] The software application of the present invention may include one or more checklists provided in relation to vehicle safety or vehicle standards or vehicle repair or functionality in order to allow a driver to assess vehicle standard at any time and if necessary, produce notifications in relation to the vehicle standards. In this way, a fleet owner may be able to track the standard of one or more vehicles in the fleet over time.

[0051] The electronic devices which are part of the present invention may include location functionality or at least one location device in order to determine and/or track the location of the device, driver and thereby, track the location of a vehicle.

[0052] The client software application of the present invention may be provided with the ability to capture vehicle information such as a license plate, a vehicle identification number, the condition of the vehicle, the sensor information from an on-board weighing system and the like in order to maintain information in relation to the vehicle or identify the vehicle within the system.

[0053] The system of the present invention includes a central software application operating on a central computer device or network with which the client software application is associated. The central software application will preferably be what is known as a “fat client” with the bulk of the processing or analysis of any information captured occurring in the central software 11 application. The client software application will therefore preferably be a “thin client”. 2017200943 10 Feb 2017 [0054] Normally, processing, record-keeping and analysis are performed at the central software application. The central software application will also typically be responsible for receiving identification requests from a client software application and comparing these requests to the profile of individual drivers in order to identify driver within the system. Normally, the identification process will be a part of an authorisation process through which authority is granted based on the particular identification and authorisations set or allowed by a system administrator in relation to individual drivers. This will typically allow the system administrator to control which drivers are driving which vehicles and either allow or deny authorisation to start and/or drive the vehicle as required.

[0055] Information captured or produced in the system will typically be recorded to an individual driver profile or associated with an individual driver profile. The central software application will therefore preferably be management software responsible for recording and analysis in order to keep records, analyse information, flag issues and issue notifications or instructions. The central software application will also be responsible for storage and mining of information for management uses. The central software application may communicate with payroll or accounting packages or other information stored in such a way that these packages can access information stored for use in those packages. Therefore, information may be stored in one or many databases or parts thereof. Normally, the driver information will be stored in a database which is accessed through individual driver profiles.

[0056] The central software application and/or the client software application will preferably be used to monitor a driver against pre-established standards of performance in order to avoid basing themselves in situations where the driver may be fatigued or other hazardous situations in which accident or incident may occur which put the driver and/or other members of the public or property in danger. For example, one simple parameter that can be measured and monitored using the system of the present invention is that a certain period of time elapsed between the finish of one workday and the start of next workday in order to ensure that the driver has sufficient rest to be performing at an optimum level. The central software may also restricted driver to operation in a particular area and issue notifications if the driver goes outside that area, may monitor cumulative drive time over an extended period or may measure appropriate or sufficient rest periods as examples only.

[0057] Preferably, the driver logon and use of the system in relation to their performance or compliance will be incentivised and will preferably not require any vehicle authorisation devices, 12 but these could be used. 2017200943 10 Feb 2017 [0058] The invention may further include an authorisation device attached to each vehicle registered in the system of the present invention which is capable of preventing the vehicle being started or driven without authorisation. An authorisation code or similar will typically be provided to the authorisation device and a corresponding authorisation code is preferably provided to the personal computing device of the driver authorised to operate that vehicle for any particular trip.

[0059] Most modern vehicles include management software operating on a small onboard processor. It is relatively straightforward to upload an application to that onboard processor that has the ability to receive an authorisation code or similar from a central software application and to compare that to an authorisation code or similar received from a proposed driver and to allow startup if the codes match and to not allow software if the codes do not match.

[0060] Prior to vehicle startup, the authorised driver will normally be required to provide their corresponding code to the authorisation device on the vehicle, generally using their personal computing device, and vehicle startup will generally only be possible if the authorisation code provided to the authorisation device and the authorisation code provided by the personal computing device of the driver authorised to operate that vehicle for any particular trip, correspond. If not, vehicle startup will not be authorised and the vehicle preferably cannot be driven. Normally the authorisation codes will be provided to the authorisation device and the personal computing device of the driver authorised to operate that vehicle for any particular trip from the central software application operating on the central computing device or network.

[0061] Any of the features described herein can be combined in any combination with any one or more of the other features described herein within the scope of the invention.

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

BRIEF DESCRIPTION OF DRAWINGS

[0063] Preferred features, embodiments and variations of the invention may be discerned from the following Detailed Description which provides sufficient information for those skilled in the art to perform the invention. The Detailed Description is not to be regarded as limiting the scope of the preceding Summary of the Invention in any way. The Detailed Description will 13 make reference to a number of drawings as follows: 2017200943 10 Feb 2017 [0064] Figure 1 is a schematic illustration of a system according to a first preferred embodiment of the present invention.

[0065] Figure 2 is a schematic illustration of a system according to a second preferred embodiment of the present invention.

[0066] Figure 3 is a schematic illustration of a system according to a third preferred embodiment of the present invention.

[0067] Figure 4 is a schematic illustration of a wearable device according to a preferred embodiment of the present invention.

[0068] Figure 5 is a schematic rear view of the device illustrated in Figure 4 with heartrate monitoring assembly.

[0069] Figure 5A is a schematic view of a wearable device and a smartphone operating a client software application to sync with the operating a client software application operating on the wearable.

[0070] Figure 6 is a schematic view of a sign in process according to a preferred embodiment of the present invention.

[0071] Figure 7 is a schematic view of a fleet management process according to a preferred embodiment of the present invention.

[0072] Figure 8 is a schematic view of a booking or scheduling process according to a preferred embodiment of the present invention.

[0073] Figure 9 is an overview schematic view of functionality offered by a preferred embodiment of the present invention.

[0074] Figure 10 is a schematic view of an interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0075] Figure 11 is an example login interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. 14 2017200943 10 Feb 2017 [0076] Figure 12 is an example registration interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0077] Figure 13 is an example biometric entry interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0078] Figure 14 is an example confirmation interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0079] Figure 15 is an example vehicle registration interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0080] Figure 16 is an example checklist interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0081] Figure 17 is an example roadworthiness alert interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0082] Figure 18 is an example damage management interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0083] Figure 19 is an example rest management interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0084] Figure 20 is an example fatigue management interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0085] Figure 21 is an example fatigue alert interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. 15 2017200943 10 Feb 2017 [0086] Figure 22 is an example administrator fatigue alert interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0087] Figure 23 is an example home interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0088] Figure 24 is an example Day 1 advisory interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

[0089] Figure 25 is an example Day 7 advisory interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention.

DESCRIPTION OF EMBODIMENTS

[0090] According to a particularly preferred embodiment of the present invention, a system for measuring and managing vehicle driver performance is provided.

[0091] A first preferred configuration of system for measuring and managing vehicle driver performance is illustrated in Figure 1. The system includes a wearable electronic device 10 operating a client software application to capture information relating to at least one biometric parameter of a vehicle driver, a central software application operating on a central computer server 11 with which the client software application of the wearable electronic device is associated through a wireless communication network 12 such that the wearable electronic device 10 communicates with the central software application operating on the central computer server 11 to capture information relating the at least one biometric parameter of the vehicle driver and transmit captured information to the central software application in order to measure vehicle driver performance.

[0092] A second preferred configuration of system for measuring and managing vehicle driver performance is illustrated in Figure 2. The system including a wearable electronic device 10 to capture information relating to at least one biometric parameter of a vehicle driver, a personal computing device 13 operating a client software application with which the wearable electronic device 10 is associated, a central software application operating on a central computer server 11 such that a vehicle driver is required to sync the wearable device 10 with the client software application and the client software application communicates with the central software 16 2017200943 10 Feb 2017 application operating on the central computer server 11 to capture information relating the at least one biometric parameter of the vehicle driver and transmit captured information to the central software application in order to measure vehicle driver performance.

[0093] A third preferred configuration of system for measuring and managing vehicle driver performance is illustrated in Figure 3. The system including a portable electronic device 13 operating a client software application to at least capture information relating to at least one biometric parameter of a vehicle driver, a central software application operating on a central computer server 11 with which the portable electronic device 13 is associated, such that the portable device 13 communicates with the central software application operating on the central computer server 11 to capture information relating the at least one biometric parameter of the vehicle driver and transmit captured information to the central software application in order to measure vehicle driver performance.

[0094] The system for measuring and managing vehicle driver performance is directed towards fatigued commercial drivers and aims at minimizing road accidents and fatalities through a comprehensive fatigue management program. The system is aimed at answering the risk that “moonlighting” truck drivers pose to road users and chain of responsibility issues with transport companies through driver management and reporting.

[0095] In all three embodiments, the system of the present invention will include hardware and associated software designed to utilise the hardware capabilities in order to collect information and to police compliance with recommendations as to work/rest balance and other health or cognition or performance criteria in order to reduce the incidence of vehicle accidents and fatalities, particularly in relation to professional drivers. The system will also centralise other functions that are related to driving performance such as booking or scheduling drivers, one example of which is illustrated in Figure 8 and fleet management as illustrated in Figure 7.

[0096] The system of the present invention will normally require a driver to login and may go further and require that each driver receive authorisation at the start of every trip, work day or whatever other period is being measured. Information is typically collected while the driver is logged into the system and then the driver will typically logout or end the connection when the trip or a portion of the trip or whatever other period is being measured, ends. An example login process is illustrated in Figure 6.

[0097] The information that may be collected using the system includes time periods, distances, biometric data relating to the driver and the like. The data may be in relation to the 17 2017200943 10 Feb 2017 driver, the vehicle being driven and/or trip parameters which are preferably or maintained in order to ascertain the periods of work and/or rest of drivers in order to ensure that the drivers are not exceeding safety requirements or recommendations in relation to time periods work and rest periods and the like.

[0098] The system of the present invention may additionally be utilised in order to keep records in relation to driver performance, vehicle history or any other information that may be collected using the system.

[0099] Information can be entered into the system from other external sources in addition to the information captured within the system and the external sources may include medical records, police or other law enforcement records and the like in order to give or maintain a history of driver performance.

[0100] The system of the present invention includes a portable electronic device and/or wearable electronic device to capture information relating to at least one biometric parameter of a vehicle driver. The information captured relating to the at least one biometric parameter of the vehicle driver may be used for any purpose but preferably, is at least used to identify the driver. The information captured can also be recorded in order to monitor or measure performance of the driver and/or a vehicle.

[0101] At least one biometric parameter of the vehicle driver is preferably used to identify the driver to the central software application in order to keep track of the driver and statistics relating to driver performance.

[0102] According to preferred embodiments of the present invention, the electronic device can be a wearable electronic device operating a client software application which is associated with the central software application (Figure 1), the electronic device can be a wearable electronic device which is associated with a portable electronic device which is in turn associated with the central software application (Figure 2) or alternatively, the electronic device can be a portable electronic device (not wearable) which is associated with the central software application (Figure 3).

[0103] Normally, a system including at least a wearable electronic device 10 is preferred because in this way, a wearable electronic device 10 can be carried with the driver easily and is less likely to be forgotten, misplaced or lost. Therefore, in addition to the central software application operating on a central computing device or network, one or more electronic devices operating a client software application can be provided within the system of the present 18 2017200943 10 Feb 2017 invention. Where more than one electronic device is provided, typically appropriate communications pathways can be provided between the electronic devices. , such as is illustrated in Figure 2.

[0104] Importantly, the function of the one or more electronic devices which are in communication with the central software application operating on the central computing device or network is to capture information about at least one biometric parameter of the driver firstly to identify the driver within the system and then secondly to capture information in relation to driver performance, either physiological performance or operational performance. The electronic devices are therefore expressly configured to achieve these aims. The configuration of the electronic devices will typically differ depending upon the type of biometric parameter to be captured. One electronic device may also be capable of capturing information in relation to more than one biometric parameter.

[0105] For example, in relation to the capture of information relating to a biometric parameter which can be used to identify a driver, the simplest biometric parameters which could be used include a fingerprint, voice print or retinal scan as examples. Although any biometric parameter which could be used to uniquely identify the driver, could be captured, these three represent the biometric parameters most commonly conventionally used for identification.

[0106] Other biometric parameters about which information could be captured using the system include heart rate, movement, breathing, energy usage in terms of calories or kilojoules, hours slept, quality of sleep, anxiety levels or the like. These biometric parameters would not generally be used to identify the driver, but more to monitor the driver’s physiological condition and/or performance.

[0107] Therefore, an appropriate electronic device or device with an appropriate information capture mechanism will typically be provided depending upon the information to be captured by the device. For example, in order to capture fingerprint information, this may be most easily captured with an electronic touch screen display of a computing device such as a smart phone, tablet or alternatively, a wearable electronic device having some form of touch screen to allow capture of finger print information. In order to capture voice information, a microphone may be provided. Further, in order to capture retinal scan information, a camera may be provided.

[0108] Therefore, as can be seen, the information capture mechanism will largely be dependent upon the biometric parameter in relation to which information is to be captured. In one particularly preferred embodiment, a single device such as a smart phone or tablet or the like 19 2017200943 10 Feb 2017 can provide a touchscreen display, a microphone and a camera so that any one or more of fingerprint information, voice print information or retinal scan information can be captured using a single device.

[0109] In relation to the information captured relating to biometric parameters used to monitor physiological performance, these are normally best monitored or information may be best captured using a wearable device as close contact with the driver’s body is typically required in order to monitor these parameters effectively and/or accurately.

[0110] Wearable devices that are capable of information capture in relation to biometric parameters used to identify driver and to capture information in relation to biometric parameters used to monitor physiological performance may also be used. Such a device will typically include GPS functionality, heart rate monitor, step counter, energy usage counter, active time tracker as well as a recording function for any or all of the above could be used. A device such as this will typically allow the recording of information, the transmission of information captured, allow notifications to be made to the device either from the client software application operating on the device and/or from the central software application, and may link to other electronic devices such as a smartphone or tablet in order to receive telephone calls or SMS messages. Device such as this will normally have a touchscreen display to allow both import and display of information, asleep monitor and will typically sync wirelessly with a smart phone, tablet or computer. Further, a wearable device such as this will preferably include at least one accelerometer. Provided with the client software application as described herein, the wearable device could be used to capture biometric information for both identification and monitoring.

[0111] In order to control or allow the information capture of the at least one, and typically multiple biometric parameters used to identify the driver and monitor physiological performance, the wearable or portable electronic device will typically operate a client software application which allows capture of biometric information as well as to control communication and information transfer with the central software application either directly or through at least one other electronic device. The client software application will normally utilise the hardware components provided on the electronic device such as a display, camera and/or microphone or the like in order to ensure that any required information is either captured or entered so that it may be used as required and/or transmitted as required in order to monitor the performance of the driver.

[0112] As mentioned above, the portable electronic device can be a smart phone or tablet with which a wearable electronic device is associated, such as illustrated in Figure 2 but may in 20 2017200943 10 Feb 2017 some instances be a wearable device having integrated functionality as outlined above and which does not require association with a smart phone or tablet or the like in order to operate within the system such as that illustrated in Figure 1.

[0113] Normally, the client software application is a software application which is downloadable to one or more wearable or portable electronic devices and which allows interfacing and access to functionality of the central software application provided at a central computer server 11.

[0114] The client software application will preferably be available through an application distribution platform, which is typically operated by the owner of a mobile operating system, such as the Apple App Store, Google Play, Windows Phone Store and BlackBerry App World. The client software application of the present invention will normally be downloaded from the application distribution platform to a target wearable or portable electronic device.

[0115] Once downloaded, the client software application will normally be stored in memory and have access to at least one processor in order to operate. The vehicle driver will normally interact with the client software application through a number of interfaces generated and displayed on a display of the particular piece of hardware upon which the client software application is operating. Therefore, the interaction with the client software application will normally be interface driven.

[0116] Each user of the system, typically each driver or each potential driver will create or have created an individual profile including information which is stored electronically in relation to a particularly unique identifier identifying that profile as belonging to a particular driver or potential drop. Normally, each driver or potential driver will create a profile through either the client software application but may do so through the central software application, or the system administrator may set up drive all potential driver profiles.

[0117] During setup, appropriate identifying information will normally be captured and recorded in each individual profile and against which a later login request can be compared. Normally, each individual profile is saved in at least one database associated with or accessible by the central software application operating on the central computer server 11. The information captured by the electronic devices within the system is normally transmitted to the central software application and saved against or in the individual profiles so that the system administrator can search records and produce reports or monitor the performance of drivers through the information. 21 2017200943 10 Feb 2017 [0118] According to a preferred embodiment of the system of the present invention, the login or authorisation process is particularly important as it is this process which will identify a particular driver within the system. The login or authorisation process preferably also begins the information capture of biometric parameters for monitoring purposes, both physiological monitoring and operational monitoring within the system.

[0119] Normally, a driver will log into the system when their employment or trip begins and will log out when complete or at one or more particular milestones. This will allow the system to track particularly the time that a driver works in order to monitor for fatigue. Information in relation to one or more biometric parameters is typically captured while the driver’s log into the system.

[0120] Alternatively, a separate “begin” or “start” and “end” or “stop” procedure may be used but this is less preferred as it may allow manipulation of the information capture process in order to give false or misleading information.

[0121] According to a particularly preferred embodiment, the login process will typically capture one or more uniquely identifying biometric characteristics of a particular driver as outlined above. Other interfaces are preferably provided within the client software application to allow entry of data or information into the client software application of various types such as food or liquid intake or other parameters that cannot be captured using direct measurement of biometric parameter.

[0122] A dashboard interface is typically provided by the client software application allowing a user to view a visual display of information or statistics in relation to information captured.

[0123] The client software application of the present invention preferably captures information and then transmits that captured information to the central software application for recording, monitoring and/or manipulation. The client software application may also receive or collect information from a wearable device and provide information entry, display and transmission functionality. Again however whether the client software application captures in transmits the information directly to the central software application or receives captured information from a wearable device in transmits that information to the central software application depends largely upon the configuration of the system used, in particular whether one or more electronic devices are provided. It is clearly preferred that fewer electronic devices be provided in that a driver only has one electronic device, preferably a wearable electronic device 22 2017200943 10 Feb 2017 that allows all functionality as this will minimise the number of devices which the driver has to keep track of.

[0124] Therefore, it should be relatively clear that the system of the present invention is preferably used to capture two types of information, a first type of information used to identify a particular driver to the system and a second type of information collected in an ongoing manner in relation to physiological or operational performance.

[0125] The system of the present invention will also normally allow analysis of any information collected. It may be important operationally such as for example information captured may be used to log work hours for payroll purposes and/or create a driver history record. The system of the present invention may also provide information to the driver such as provide traffic information or routing information or warnings as to hazardous situations that may occur from time to time.

[0126] The system of the present invention may also be used to ensure that drivers operate within the correct geographic area and do not stray into the geographic areas of other drivers where this is appropriate.

[0127] The electronic device used by the driver may be provided with hardware which allows the client software application to include other ancillary functionality which may be useful such as breathalyser capability, a visual acuity test, a mental acuity test, cognition testing, drug analysis or the like as these can be used to ensure driver compliance with safety requirements or regulations.

[0128] The electronic devices which are part of the present invention may include a location functionality in order to track the location of the driver and thereby, track the location of a vehicle.

[0129] The client software application of the present invention may be provided with the ability to capture vehicle information such as a license plate, a vehicle identification number, the condition of the vehicle, the sensor information from an on-board weighing system and the like in order to maintain information in relation to the vehicle or identify the vehicle within the system.

[0130] A particularly preferred wearable device is illustrated in Figures 4 and 5. This device is worn on a driver’s wrist and includes a location device which allows the tracking of the location of the device and thereby, the driver wearing the device. The device also has a heart rate 23 2017200943 10 Feb 2017 monitor incorporated therein which allows monitoring of the driver’s heart rate. The device also includes a touchscreen display 14 which allows both input information through the touchscreen display and display of the interfaces generated by the client software application. The touchscreen display allows identification of a particular driver through fingerprint capture directly using the touchscreen display. The touchscreen display can also be used to make notifications to the driver as well as to allow the driver interaction with the client software application operating thereon. The device will typically be provided with a wireless communication pathway allowing the device to transmit information to and receive information from either a portable electronic device 13 or directly with the central software application operating on the computer server 11. This device therefore is capable of being used to identify a particular driver and then once the identity of the driver has been determined, allows the capture of a variety of information in relation to the driver’s physiological condition and operational performance. Figure 5 shows one configuration of heartrate monitor that could be used. The driver will typically use the device to log into the system of the present invention and to remain logged in whenever the driver is working which allows the system to capture information in relation to the driver’s performance, whenever logged into the system as well is to calculate other information based on the periods in which the driver is logged in to the system and/or logged out of the system. In addition to the touchscreen display, the device has a pair of buttons 15 on the side to assist with input or selection of information.

[0131] The system of the present invention includes a central software application operating on a central computer device or network with which the client software application is associated. The central software application will preferably be what is known as a “fat client” with the bulk of the processing or analysis of any information captured occurring in the central software application. The client software application will therefore preferably be a “thin client”.

[0132] Normally, processing, record-keeping and analysis are all performed at the central software application. The central software application will also typically be responsible for receiving identification requests from a client software application and comparing these requests to the profile of individual drivers in order to identify driver within the system. Normally, the identification process will be a part of an authorisation process through which authority is granted based on the particular identification and authorisations set or allowed by a system administrator in relation to individual drivers. This will typically allow the system administrator to control which drivers are driving which vehicles and either allow or deny authorisation to start and/or drive the vehicle as required. 24 2017200943 10 Feb 2017 [0133] Information captured or produced in the system will typically be recorded to an individual driver profile or associated with an individual driver profile. The central software application will therefore preferably be management software responsible for recording and analysis in order to keep records, analyse information, flag issues and issue notifications or instructions. The central software application will also be responsible for storage and mining of information for management uses. The central software application may communicate with payroll or accounting packages or other information stored in such a way that these packages can access information stored for use in those packages. Therefore, information may be stored in one or many databases or parts thereof. Normally, the driver information will be stored in a database which is accessed through individual driver profiles.

[0134] The central software application and/or the client software application will preferably be used to monitor a driver against pre-established standards of performance in order to avoid basing themselves in situations where the driver may be fatigued or other hazardous situations in which accident or incident may occur which put the driver and/or other members of the public or property in danger. For example, one simple parameter that can be measured and monitored using the system of the present invention is that a certain period of time elapsed between the finish of one workday and the start of next workday in order to ensure that the driver has sufficient rest to be performing at an optimum level. The central software may also restricted driver to operation in a particular area and issue notifications if the driver goes outside that area, may monitor cumulative drive time over an extended period or may measure appropriate or sufficient rest periods as examples only.

[0135] Preferably, the driver logon and use of the system in relation to their performance or compliance will be incentivised and will preferably not require any vehicle authorisation devices, but these could be used.

[0136] In an alternative and preferred embodiment, the invention may further include an authorisation device attached to each vehicle registered in the system of the present invention which is capable of preventing the vehicle being started or driven without authorisation. An authorisation code or similar will typically be provided to the authorisation device and a corresponding authorisation code is preferably provided to the personal computing device of the driver authorised to operate that vehicle for any particular trip.

[0137] Prior to vehicle startup, the authorised driver will normally be required to provide their corresponding code to the authorisation device on the vehicle, generally using their personal computing device, and vehicle startup will generally only be possible if the 25 2017200943 10 Feb 2017 authorisation code provided to the authorisation device and the authorisation code provided by the personal computing device of the driver authorised to operate that vehicle for any particular trip, correspond. If not, vehicle startup will not be authorised and the vehicle preferably cannot be driven. Normally the authorisation codes will be provided to the authorisation device and the personal computing device of the driver authorised to operate that vehicle for any particular trip from the central software application operating on the central computing device or network.

[0138] In a preferred form, the information captured in relation to a particular driver may be used to create or in a national driver database. A database such as this allows a manager or even a customer wishing to engage a driver using the system of the present invention to match selected criteria in the selection of a driver. This will assist with the chain or responsibility and there may be restrictions placed on driver records within the driver database which prevents a driver having an adverse record being selected within the system until such time as the adverse record or conditions have passed. For example, if a driver has accumulated too much of driving time on the road in a particular period, they may be temporarily blocked from any further selection which will typically flow into the authorisation process which will preferably prevent a particular driver operating until an appropriate period has passed.

[0139] The information collected may allow the tracking of a driver’s fuel consumption practices and allowing remedial action to be taken with employee drivers to improve techniques that minimise costs and improve efficiencies.

[0140] Within the system of the preferred embodiment, drivers are able to take photos of defects and damage to provide extra information about a check, which then records whether the vehicle or trailer passes or fails the driver’s check. Depending on the result of all the checks performed, the driver will preferably sign off against a specific declaration as defined in a checklist so that consistent and complete records are maintained.

[0141] The system preferably includes a pre-start checklist as well as damage reporting prior to a vehicle commencing work. The client software application will preferably be used for capture of this type of information and checklist completion and then normally uploads all the information and images to the central software application accessible via web portal. Preferably the central software application will have a subsystem to automatically produce and dispatch notifications to parties of any defects or damage a vehicle may have. These notifications can be custom set to notify a nominated mechanic or repairer.

[0142] The central software application will also preferably have a “master roster” with 26 2017200943 10 Feb 2017 timeslots that need to be filled. These slots will normally be broken down into the type of carrier required and start times and the type of vehicle required, for example agency labour, subcontractor, tow operator or sub-contractor full rig.

[0143] If the vehicle is company-owned it will preferably be up to the agency to fill in the name of the driver and confirm the booking. Should the driver be changed for any reason or not show up for his/her shift the agency may be charged a nominal fee as an incentive to keep on reliable drivers, with data to be stored so a reliability rating may be used for future reference. This feature will preferably result in less roster changing and will also highlight the drivers who are unreliable or reliable, without bias.

[0144] The same principle may be used for sub-contractors. If a sub-contractor does not meet their obligation, an automatic reliability rating can be applied and the history stored in a database so as to avoid any confusion or disputes in the future.

[0145] According to a preferred embodiment, there are three basic steps for the employer to complete the rostering using the system of the present invention: • The central software application will normally send a notification via the client software application and/or email that there are vacancies to be filled at a specific site with times, dates, and the licence/vehicle type required. • An employer or company may then contact eligible applicants with their availability and log into the central software application with their unique login details. • The employer or company can then enter in the applicant driver’s licence details into the specified field to see if they are eligible to work at the required site. If the driver does not meet the required criteria; fatigue, inductions, licence class or they are double-booked, the application will be rejected and the driver cannot be used or authorised.

[0146] Effective and efficient capture of information in relation to a driver’s work can be used to post accurate driver time information to produce timesheets, in real time. This then preferably connects directly into an accounting packages and/or database. This allows capture of information in relation to the driver and ties that information specifically to that driver through the requirement for biometric identification allowing a variety of aspects of management to be managed centrally as illustrated in Figure 9.

[0147] Preferably, access to the system and information is available in real time, from anywhere in the world by logging into a web portal. 27 2017200943 10 Feb 2017 [0148] An important part of the present invention is the client software application operating on a portable electronic device to at least capture information relating to at least one biometric parameter of a vehicle driver. According to a preferred embodiment, the portable electronic device will be associated with a wearable device to collect information relating to the driver, collect information about the vehicle to be driven and to provide feedback on and/or alerts from the central software application operating on the central computing device or network in relation to the driver statistics or performance and/or the vehicle statistics.

[0149] Figure 10 shows an interface which is generated and displayed on a portable electronic device in the position of a driver which is preferably sent to a wearable device.

[0150] Figure 11 shows an example login interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. As illustrated, the login interface requests the driver’s name and password and once entered, entry of the correct name and password which matches the name and password on a driver profile accessible by a central software application operating on the central computing device network will allow access to the system.

[0151] Figure 12 is an example registration interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. This interface shows the types of information which are required in order to create a driver profile for use within the present invention.

[0152] Figure 13 is an example biometric entry interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. This interface will typically be generated and displayed on the portable computing device in order to allow a driver to begin recording information using the system of the present invention. As illustrated, the interface includes a picture of the driver, information about their identity, and importantly, an identified portion for biometric identification of the user. Once the user has entered the information requested in the interface illustrated in Figure 12, the interface in Figure 13 can be generated and displayed requesting capture of the user’s fingerprint for storage in relation to the user’s profile. The portion identified in the example interface illustrated in Figure 13 is a fingerprint scanning portion which can utilise the touchscreen capabilities of a preferred portable computing device to capture biometric information in relation to the user’s fingerprint for storage within the database. Once the user profile has been set up, and the biometric reference fingerprint captured and stored in the profile, the reference fingerprint can then be used at a later stages for authentication of the user’s identity through a comparison of a 28 fingerprint captured at any time with the reference fingerprint in the particular user’s profile. 2017200943 10 Feb 2017 [0153] Figure 14 is an example confirmation interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. The user can at any stage access the system by correct entry of the password matching the password used for the user identified on the interface.

[0154] Figure 15 is an example vehicle registration interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. This interface will typically be generated and displayed prior to vehicle start each time a driver prepares to use a vehicle. In use, the interface will include a number of “buttons” allowing capture of information in relation to a particular vehicle. Typically, the user will tap the “truck registration” in order to enter the particular registration details of the vehicle which they propose to drive and then select the “start session” button in order to access the interface illustrated in Figure 16.

[0155] Figure 16 is an example checklist interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. This interface allows the driver to capture information using the client software application in relation to particular aspects of the vehicle which require checking in order to ensure compliance with roadworthiness criteria. In practice, the driver will typically go through each item identified in the checklist and ensure compliance. This may require entry of checkmarks as illustrated on the right-hand side of Figure 16 and/or require entry of actual parameters. This will allow information entered using the interface illustrated in Figure 16 to be assessed against roadworthiness criteria which are stored in the central software application.

[0156] Figure 17 is an example roadworthiness alert interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. As a part of the roadworthy check, if any items or missed all the information entered in relation to a particular checklist item does not match the roadworthiness criteria stored in the central software application, an alert will typically be issued by the central software application and transmitted to the driver via the client software application operating on the portable computing device. The alert interface illustrated in Figure 17 can be accompanied by one or more tones or vibration alerts as well and preferably, prevents the driver proceeding further until the issue is overcome or resolved.

[0157] Figure 18 is an example damage management interface generated on a portable 29 2017200943 10 Feb 2017 computing device by the client software application according to a preferred embodiment of the present invention. Using this interface, the driver can log damage to the vehicle either before or after driving the vehicle. This will act to notify damage to the vehicle to the central computer system or network. In particular, the drive will have the ability to use the portable computing device to enter information as to the location of any damage to the vehicle and preferably indication of the extent of damage to the vehicle by tapping the image generated and displayed on the display of the portable computing device. This interface also allows logging of a case number and the registration details in relation to the particular vehicle as well as capture images of the damage using the image capture capabilities of the preferred portable computing device which is normally a smart phone for uploading with the particular damage log.

[1000] Figure 19 is an example rest management interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. This interface shows a summary of the driver’s work and rest hours. The upper portion of the interface shows the time elapsed at work in relation to the hours which remain until a compulsory rest stop will be required. This is shown in graphical terms as well as in a quantitative time manner. Directly below this, is a quantitative representation of the time remaining until a compulsory rest stop will be required. As indicated, the driver may stop at any time prior to this. The drive will typically interact with this interface and thereby with the client software application operating on the portable computing device using the large “drive” and “stop” buttons at the bottom of the interface. Using these buttons, the driver will be able to indicate to the client software application operating on the portable computing device whether the driver is driving or whether the driver has stopped for a rest.

[0158] Figure 20 is an example fatigue management interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. This interface can illustrate the location of a rest location appropriate for the driver. The preferred manner of indication is through the generation in display of a map interface showing the rest location on the map. This will allow a driver to be forewarned of upcoming rest locations in order to take appropriate rest when the rest locations are available.

[0159] Once the driver has stopped, the client software application operating on the portable computing device which as indicated above is normally a smart phone, will typically utilise the positioning functionality operating on the portable computing device to ascertain that the driver has stopped, and the location which the driver stopped. The system of the present invention can utilise the GPS functionality in the portable computing device to ensure that the driver has 30 actually stopped when the driver has indicated that they have stopped. 2017200943 10 Feb 2017 [0160] Figure 21 is an example fatigue alert interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. If a driver reaches predetermined work levels, one or more alerts can be generated by the central software application and transmitted to the client software application operating on the portable computing device for alerting the driver that they are about to breach the fatigue management guidelines. Again, an alert will typically be issued by the central software application and transmitted to the driver via the client software application operating on the portable computing device. The alert interface illustrated in Figure 21 can be accompanied by one or more tones or vibration alerts as well. Depending upon how close the driver is to breaching the condition, the alerts issued can escalate.

[0161] Figure 22 is an example administrator fatigue alert interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. This interface shows that an alert has been issued to the administrator of the system noting that the driver has breached the fatigue guidelines or laws. As mentioned in the alert, the notification will also be lodged on the driver’s individual driving profile.

[0162] Figure 23 is an example home interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. From this interface, the driver can access the various portions of the system for information recorded, scheduled jobs or loads or overall management.

[0163] Figure 24 is an example Day 1 advisory interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. This interface shows that after a single day at work, the driver is required have 7 continuous hours of stationery rest time. This can be taken in a number of ways, but preferably, the client software application will interface with the positioning functionality operating on the portable computing device to ensure that the driver is stationary during the entire 7 hours indicative of an appropriate rest period.

[0164] Figure 25 is an example Day 7 advisory interface generated on a portable computing device by the client software application according to a preferred embodiment of the present invention. This interface shows that after 7 days of work, the driver is required to have 24 continuous hours stationery rest time again, This can be taken in a number of ways, but preferably, the client software application will interface with the positioning functionality 2017200943 10 Feb 2017 31 operating on the portable computing device to ensure that the driver is stationary during the entire 7 hours indicative of an appropriate rest period.

[0165] As can be seen from the preferred embodiment, the present invention provides a unified system for driver management particularly in relation to fatigue management but also for ancillary items such as vehicle management, vehicle safety and job management.

[0166] In the present specification and claims (if any), the word ‘comprising’ and its derivatives including ‘comprises’ and ‘comprise’ include each of the stated integers but does not exclude the inclusion of one or more further integers.

[0167] Reference throughout this specification to ‘one embodiment’ or ‘an embodiment’ means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearance of the phrases ‘in one embodiment’ or ‘in an embodiment’ in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more combinations.

[0168] In compliance with the statute, the invention has been described in language more or less specific to structural or methodical features. It is to be understood that the invention is not limited to specific features shown or described since the means herein described comprises preferred forms of putting the invention into effect. The invention is, therefore, claimed in any of its forms or modifications within the proper scope of the appended claims (if any) appropriately interpreted by those skilled in the art.

Claims (20)

1. A system for measuring and managing vehicle driver performance, the system including a wearable electronic device operating a client software application to capture information relating to at least one biometric parameter of a vehicle driver, a central software application operating on a central computing device or network with which the client software application of the wearable electronic device is associated such that the wearable device communicates with the central software application operating on the central computing device or network to capture information relating the at least one biometric parameter of the vehicle driver and transmit captured information to the central software application in order to monitor vehicle driver performance.

2. A system for measuring and managing vehicle driver performance, the system including a wearable electronic device to capture information relating to at least one biometric parameter of a vehicle driver, a personal computing device operating a client software application with which the wearable electronic device is associated, a central software application operating on a central computing device or network such that a vehicle driver is required to sync the wearable device with the client software application and the client software application communicates with the central software application operating on the central computing device or network to capture information relating the at least one biometric parameter of the vehicle driver and transmit captured information to the central software application in order to measure vehicle driver performance.

3. A system for measuring and managing vehicle driver performance, the system including a portable electronic device operating a client software application to at least capture information relating to at least one biometric parameter of a vehicle driver, a central software application operating on a central computing device or network with which the portable electronic device is associated, such that the portable device communicates with the central software application operating on the central computing device or network to capture information relating the at least one biometric parameter of the vehicle driver and transmit captured information to the central software application in order to measure vehicle driver performance.

4. A system as claimed in any one of the preceding claims further including at least one biometric reader to allow a driver to be identified using biometric data specific to the driver.

5. A system as claimed in claim 4 wherein the at least one biometric reader is provided in relation to at least one vehicle.

6. A system as claimed in Claim 5 wherein the at least one vehicle is fitted with an authorisation device to prevent operation of the at least one vehicle without authorisation.

7. A system as claimed in Claim 6 wherein an authorisation code or similar is provided to the authorisation device by a particular driver using the client software application to authorise the particular driver to operate that vehicle for any particular trip and failure to provide the authorisation code will cause the authorisation device to prevent operation of the at least one vehicle.

8. A system as claimed in Claim 7 wherein an authorisation code or similar is provided to the authorisation device from the central software application and the authorisation code supplied from the client software application is compared that to the authorisation code or similar from the central software application allowing vehicle operation if the respective authorisation codes match and to not allow operation if the respective authorisation codes do not match.

9. A system as claimed in any one of the preceding claims wherein the portable or wearable electronic device to capture information relating to at least one biometric parameter of a vehicle driver is at least used to identify the driver and to capture information in order to monitor or measure performance of the driver and/or vehicle.

10. A system as claimed in any one of the preceding claims wherein the electronic device is a wearable electronic device which is associated with the central software application with access to at least one communication channel.

11. A system as claimed in any one of claims 1 to 10 wherein the electronic device is an wearable electronic device which is associated with a portable electronic device which is in turn associated with the central software application.

12. A system as claimed in any one of claims 1 to 10 wherein the electronic device is a portable electronic device not wearable, which is associated with the central software application.

13. A system as claimed in any one of the preceding claims wherein the electronic device captures information in relation to driver performance either physiological performance or operational performance.

14. A system as claimed in any one of the preceding claims wherein the electronic device is configured to capture information relating to a biometric parameter which can be used to identify a driver, including any one or more of a fingerprint, voice print or retinal scan.

15. A system as claimed in any one of the preceding claims wherein the electronic device is configured to capture information relating to a biometric parameter which can be used to monitor the performance of the driver, including at least one of heart rate, movement, breathing, energy usage, hours slept, quality of sleep, or anxiety levels.

16. A system as claimed in any one of the preceding claims wherein during setup, appropriate identifying information will normally be captured by the client software application and recorded in an individual driver profile and against which a later login request can be compared.

17. A system as claimed in any one of the preceding claims further including a dashboard interface provided by the client software application allowing a user to view a visual display of information or statistics in relation to information captured.

18. A system as claimed in any one of the preceding claims wherein the electronic device further includes at least one positioning receiver to provide real time location information of the electronic device.

19. A system as claimed in any one of the preceding claims wherein the electronic device further includes other ancillary functionality including at least one of an alcohol level meter, a visual acuity test, a mental acuity test, cognition testing, or drug analysis.

20. A system as claimed in any one of the preceding claims wherein the electronic device via the client software application of has access to at least one commination’s pathway to send and/or receive instructions or notifications to and from the central software application in order that an employer can maintain contact and instruct, notify or interact with individual drivers.