AU2002244516A1 - A method and apparatus for monitoring attendance - Google Patents

Description

TITLE "A METHOD AND APPARATUS FOR MONITORING ATTENDANCE"

FIELD OF THE INVENTION

This system relates to a method and apparatus for monitoring attendance. In particular, the invention resides in monitoring of attendance of cleaning staff at a shopping centre and therefore will be described in this context. However, the invention is not limited to monitoring attendance at a shopping centre and it is envisaged that the invention may be used to monitor other staffing roles, such as security in various locations such as schools or warehouses.

BACKGROUND OF THE INVENTION

Shopping centre owners and/or contractors are increasingly concerned with persons injuring themselves within the shopping centre. Any injury that occurs within the shopping centre has the potential for the shopping centre owners and/or contractors to be found to be negligent and being required to pay large sums of money to the injured person.

One possible scenario in which shopping centre owners and/or contractors can be considered to be negligent is if litter and/or spillages are located on the floor of a shopping centre and a person injures themselves as a consequence. If the shopping centre owner and/or contractor was not considered to be diligent in removing the litter and/or spillage, then the likelihood of the shopping centre owner and/or contractor being found to be negligent is significantly increased.

In an attempt to decrease the liability of the shopping centre owners and/or contractors, attendance verification systems for shopping centre staff have been developed. The simplest form of attendance verification is time sheets which are stored at various locations around the shopping centre. A staff member must then fill in the time at which an area was inspected by the staff member. The disadvantage with this system is that there needs to be a place for location of the time sheet, staff must be trusted to fill in the time sheet correctly and consumables such as ink and paper must be replaced. Further, the manual system of reading and storing information does not readily lend itself to computation and manipulation of statistics. Paper storage space is also space intensive.

Alternately, time clocks with punch cards have been used. This addresses the difficulty of staff providing accurate time keeping. However, the disadvantages of consumables being used such as time cards and ink have not been rectified. Further, time cards must also be collected and transcribed for record keeping purposes.

In an attempt to address the above drawbacks, an electronic attendance verification system has been developed. This system involves providing a number of embedded silicon chips positioned around a shopping centre. Each silicon chip has an individual serial number associated with the chip. Each cleaner carries a reader that is able to read and record the serial number on the silicon chip and the time at which the silicon chip was read. The reader is then downloaded after the end of the shift at a central location within the shopping centre.

The electronic attendance verification system is very accurate and does not consume materials. However, it is time-consuming and expensive to collate and analyse the results located within readers at the end of a shift.

All of the previous systems need constant diagnosis to identify problem areas and/or problem staff members. Moreover, none of the prior art systems rectify a problem instantaneously. Therefore, if an area is not inspected for litter and/or spillage, this is only identified later when the data is analysed. Hence, if litter and/or spillage remains in a location for a long period of time, the chances of a shopping centre owner and/or contractor being found to be liable if a person injures themselves also increases.

OBJECT OF THE INVENTION It is therefore an object of this invention to overcome at least one or more of the above disadvantages or provide the consumer with a useful or commercial choice. SUMMARY OF THE INVENTION Accordingly, in one form the invention resides in a system for monitoring attendance comprising: recording means to record that a user has attended a predetermined location; transmitting means to transmit a signal that the user has attended said location; receiving means to receive said signal a timer to set a predetermined time limit to record attendance at said location; an alert means to provide an alert; wherein said alert means is activated if said user has not attended said location within said time limit.

In another form, the invention resides in a method for monitoring attendance including the steps of: recording the attendance of a user at a predetermined location; transmitting a signal via transmitting means that indicates that said user has attended said location; receiving said signal via a receiving means activating an alert means if said user has not attended said location within a predetermined time limit.

BRIEF DESCRIPTION OF THE DRAWINGS Embodiments of the invention will now be described with reference to the accompanying drawings, in which: FIG. 1 is a schematic drawing of a monitoring attendance system for cleaning staff in a shopping centre according to a first embodiment of the invention; and

FIG. 2 is a schematic drawing of a monitoring attendance system for cleaning staff in a shopping centre according to a second embodiment of the invention. DETAILED DESCRIPTION OF THE PREFFERRED EMBODIMENT

FIG 1 shows a first embodiment of a monitoring system 10 comprising a series of remote stations 30, 31 , 32 and 33 that are located at various predetermined positions within a shopping centre. Each remote station 30, 31 , 32 and 33 includes a reader, a transmitter and an associated timer.

The reader is a magnetic card reader that reads magnetic cards. The reader may read other devices such as silicon chips, radio waves or the like and may be chosen dependant on various conditions such as climatic conditions. For example, the reader would need to be weather proof if located outside.

The transmitter is a radio transmitter in this embodiment. However, the transmitter may transmit other frequencies of electromagnetic waves such as light or microwaves. The timer is programmable between a range of times, such as between 5 and 30 minutes, depending on specific requirements. The time is also used to switch the remote station on and off depending on individual requirements.

A receiver 40, such as a pager, is worn by a cleaning supervisor. The receiver 40 provides an alert to the cleaning supervisor when a transmitter of any of the remote stations is activated.

The attendance monitoring system operates by providing each of the cleaners 20 and 21 with a magnetic card. If the magnetic card is swiped adjacent to readers 30, 31 and 32 within a pre-programmed timed limit, the timer is reset. It should be appreciated that there may be more than two cleaners.

If a magnetic card is not swiped adjacent to a reader 33 within the time limit, the transmitter is activated and sends a signal. The receiver

40 receives the signal and provides an alert to the cleaning supervisor of the problem. For example, when using a pager, an appropriate text message such as "AREA 5 HAS NOT BEEN ATTENDED IN THE LAST 15 MINUTES" is received. All messages received by the pager are time and date stamped. The cleaning supervisor 50 then either attends to the matter or communicates with a cleaning staff member to attend the area. Any litter and/or spillage found in the area is then cleaned. Once the area is attended, a magnetic card is swiped adjacent the card reader 33. This resets the timer within the remote station 33 and a reset message is sent by the transmitter to the receiver 40. The receiver 40 retains all messages including when and at what time the messages were sent for later use. Preferably the information retained by the receiver 40 is downloaded and/or printed for analysis.

A central monitoring station 60 can also be linked to the remote stations 30, 31 , 32 and 33. The central monitoring station includes a receiver that receives the same messages as receiver 40. The central monitoring station 60 may include a computer. An output device 70, such as a printer, is linked to the central monitoring device to produce a hard copy of all signals transmitted. Further, the central monitoring system is linked to a supervisory monitoring station that monitors more than one system.

A test switch may be provided on the remote station. The test switch may cause the remote station to be tested and if the remote station is fully operational then a message is transmitted such as "REMOTE STATION IS OPERATIONAL". Normally a test would be conducted on each remote station daily.

FIG 2 shows a second embodiment of a monitoring system 100 comprising 100 a series of client units 200, identification devices 300 , a server 400, a wireless network and associated software.

The client units 200 are handheld computers that users are used to interact with the server 400 via a receiver and a transmitter. Typically the client units 200 include palm units that are commonly available in the trade. The client units 200 are hand held devices that are stored on users' belts whilst not in use. The client units 200 are operated via an interface such as a touch screen. The user is able to select large buttons with one of their fingers. The user, at times, needs to enter written information that is produced using a stylus.

The client units 200 have an advanced network compatible operating system (OS) to enable each client unit 200 to operate independently in case of network unavailability and to reduce network traffic.

The OS has networking functions built in so that the software does not need to generate this functionality. Windows CE is an example of a suitable OS. Each client unit 200 has either or both a bar scanner or radio frequency ID (RFID) built in. The client unit 200 needs to record when a user has cleaned a point in the site. This is achieved by the client unit 200 interacting with an identification device located at predetermined locations around the shopping centre. Typically the identification devices 300 are barcodes 301 or radio frequency IDs (RFID) 302. Hence, the client unit 200 can record when a location has been attended by scanning a barcode 301 on the wall or by receiving a radio signal from an RFID 302. The RFID 302 is preferable because the user does not need to interrupt their cleaning to inform the system they have cleaned that point.

The client unit 200 has a sufficient battery life to last at least as long as a normal shift. Hence a battery life of between 6 and 14 hours is suitable. The client unit 200 is resistant to damage from being dropped on to hard floors or coming in contact with liquids such as cleaning fluids.

The server 400 communicates with all the client units 200, via a receiver and a transmitter, to coordinate communication between the client units 200. The server 400 communicates with a database 401 that stores all information about the shopping centre on the database 401. The server 400 handles multiple communications between the client units 200 and stores and retrieves information in the database 401 in real-time.

The server 400 is a desktop personal computer (PC) with sufficient RAM and hard drive capacity for the operation. It would be appreciated by a person skilled in the art that the more client units 200 and identification devices 300, the greater the need for RAM and hard drive space. Hence, the server 400 needs to be a modern desktop PC with relatively strong performance.

The server 400 requires a stable operating system (OS) such as Windows 2000 to minimise the risk of the operating system crashing during operations.

The information in the database 401 is backed up at regular intervals, usually daily. The server 400 therefore uses suitable backup hardware that allows it to perform this operation automatically. For example, a tape or CD backup system would be suitable. The server 400 also has an uninterrupted power supply (UPS).

The UPS prevents the loss of data due to power surges or outages. The UPS can normally provide power for approximately 20 minutes in the event of a black out.

The server 400 also allows for a dial up connection. A dialup connection for the server 400 allows remote access is to the server 400 for administration or reporting functions. Accordingly, a modem 402 that utilises a dictated phone is connected to the server 400. Normally, communications over the internet in conjunction with a personal computer 500 are utilised for remote access. Hard copies of reports can be produced via the printer 403. The wireless network allows the client units 200 to communicate with the server 400. There are two types of network that are used with the monitoring system 100: a wireless wide area network (WWAN) and a wireless local area network (WLAN). Software that is utilised by the system is designed to operate across either type of network without any need for extensive modification.

The WWAN communicates across large distances by communicating across third party networks such as the mobile phone network. The WLAN communicates within a site via wireless networking equipment installed into the shopping centre at the time of implementation. The wireless network uses TCP/IP protocol to utilise the existing networking capabilities of the client units 200 and server 400. This also enables the system to be implemented across a WWAN or a WLAN without excessive reengineering.

The wireless network provides coverage to all points within a site. If coverage fails on one point then the user can come into range within a few minutes so the network message is sent in close to real time.

The wireless network provides reasonable security from being accessed by unauthorised users orfrom information being intercepted. This is important across a WWAN which is a public network, but also across a

WLAN which is operating on a public frequency and has the potential to be accessed by anyone entering the site with a WLAN capable computer.

The associate software includes several components working together. These components are the database 401 , the server 400, client unit 200 software and remote access web server 400.

The database 401 performs the function of logging the cleaning activity within the site and holding the information describing the shopping centre and the parameters that need to be met in cleaning it. The database 401 holds information pertaining to the following fields:

• Site information. A description of the site for reporting purposes. A single server 400 needs to be able to handle multiple sites in the case of a WWAN.

• Point information. A list of all the points within a site and a description that allows them to be identified by a user

• Conformance parameters. The parameters that the system checks against the users' activities. For example a list of points to be checked every 15 minutes, a list to be checked every 30 minutes, etc. These parameters are specific to days and time of the day to cater for varying traffic within the site.

• Event definitions. A list of major and minor events that are relevant to this site. • User information. Information required allowing an user to login and access the system. The user is also logged against any event to allow later identification.

• Event log. The log of all the events that occur within the site. This log is NOT capable of being changed or edited by anyone.

• Incident reports. A report of circumstances pertaining to an incident entered by a user via the client unit.

• Daily circuit definition. A list of points that must be checked in a certain order as part of the daily checklist. • Daily checklist. A daily report of the state of the site including maintenance issues and door count.

The server 400 software performs the function of handling communication between the server 400 and the client units 200, storing events from the client units 200 in the database 401 and monitoring users conformance to the conformance parameters.

The server 400 handles communication between the client units 200 that communicate with each other via the server 400. Communication between individual client units 200 is achieved by assigning each an IP address of the client units 200. The server 400 allocates the IP addresses of the client units 200 dynamically, and through which all communications pass. The server 400 knows which user is on which client unit 200 at what IP address and hence forwards any appropriate message to that address. All communications are routed through the server 400 because it is securely locked in its own room connected to a UPS and therefore is less likely to be lost or damaged.

The server 400 handles storing events in the database 401 to reduce the data being passed between client units 200 and server 400. Instead of a client unit 200 having to establish its own connection to the database 401 it can instead send a small message to the server 400. This server 400 then interprets that message (for instance user X has checked point Y) and connects to the database 401 to store the information. This is particularly important in a WWAN situation where access to the network is being paid for according to amount of data transmitted.

The server 400 monitors user conformance and responds appropriately. If the users fail to check all the necessary points within a timeframe, then the server 400 alerts a supervisor so action can be taken to correct the error. The server 400 handles this function so that if a client unit 200 stops functioning then the server 400 knows that it is not receiving event information and can respond.

The client unit 200 software performs the following functions: authenticate user, capture data from the barcode 301 or RFID 302, capture data through touch screen entry, log events locally, send and receive communications to server 400, upload event log to server 400.

When a user begins their shift the first thing they do is to log on to the system. The server 400 then authenticates them against the database 401. If they are a supervisor then they are allowed extra privileges to access functionality specific to the supervisor. Once authentication has occurred, the server 400 then knows who is on the floor and their IP address.

The client unit 200 captures data from the barcode 301 or RFID 302 to determine whether points have been checked. The barcode 301 or RFID 302 have a unique ID that represents details of the specific location it is attached to within the shopping centre.

The client unit 200 also captures data through touch screen entry. Daily checklist and incident reports are examples of data that is captured this way. The user can tick off entries and enter further comments as is necessary.

The client unit 200 logs events locally for redundancy. These events are stored as a text based XML document that can then be uploaded to the server 400 at the end of the day. The server 400 uses this log to check against the database 401 to ensure that no events have been missed. Every time an event occurs, the client unit 200 sends this data to the server 400 as an XML document. Data is also sent to the server 400 for reports, events, etc. The client unit 200 also receives messages. If the users fail to meet the conformance parameters then the server 400 sends an alert message notifying the supervisor.

The remote access web server 400 handles the tasks of administration and reporting. Handling these tasks via a web interface allows these functions to be handled remotely if required. The web server 400 authenticates users, allows administration and generates reports.

When a user first logs on the web server 400 authenticates them against the database 401 to determine how much access they are granted. Some users may be able to administer the system, whilst others may only be able to generate reports.

Users who can administer the system need to be able to change all the system settings. This is achieved by having the configuration stored in the database 401 itself. A user may need to create a new site, add points to the site, change conformance parameters, add users, and other such operations.

The web interface provides a scalable design so that new reports are added as needed. Users are able to choose reports, specify parameters for those reports, print them and save them locally without being able to change the information contained with those reports. For example, the server 400 can convert the reports to PDF files for downloading.

The monitoring system 100 allows three types of users to operate the client units 200. The monitoring systems 100 behaviour varies depending on the type of user that is operating the client unit. The types of users are supervisors, cleaning staff and miscellaneous users.

The supervisor is responsible for coordinating cleaning staff and ensuring conformance is maintained in the event of problems. The supervisor is the first point of contact for the majority of alerts that the system generates. The supervisor also has access to the daily checklist and other relevant functionality. The cleaning staffs are responsible for the checking of points within their circuit and to respond to any instructions from the supervisor. The system actively monitors the activity of these users and measures this against the conformance parameters. Miscellaneous users are staff such as security guards or maintenance staff who have a client unit. These staff have no responsibility for cleaning activity, but may record minor events, major events they personally attend to, or be utilised by the supervisor to check points that have been missed. The system does not actively monitor their activity, but allows them to manually enter into the client unit 200 that they have checked a point.

The monitoring system 100 describes the shopping centre in terms of a collection of points that need to be checked at regular intervals. The conformance parameters describe how often each point needs to be checked and the maximum time that is allowed between checking any two consecutive points. The system measures whether users are conforming to these parameters. The system measures this conformance in the following way: -

1. The cleaning circuit starts and the server 400 starts a timer that is used to determine when to check the conformance.

2. Every time a client unit 200 passes a point the client unit 200 recognises the point through a barcode 301 being scanned or via the RFID 302.

3. The client unit 200 sends data to the server 400 describing the event that just occurred. That is, the date, the time, the ID of the point and the ID of the user.

4. The client unit 200 logs this event locally in its daily event log.

5. The server 400 receives this data and stores it in the database 401.

6. The server 400 determines the time between this event and the previous event for this user and also between the previous event and the event before that. If both of these times exceed the maximum time allowed between any two points then the server 400 sends an alert to the user and the supervisor.

7. When the timer reaches the time the points are required to be checked in (usually fifteen minutes) the server 400 examines the event log to determine if all the points have been checked. The timer is restarted and the next conformance period begins.

8. If any points have not been checked (because they have been missed or because a user is too slow or detained) then an alert is sent to the supervisor notifying him or her of the outstanding points.

9. Another timer is started to measure a secondary conformance period (usually three minutes). During this time the supervisor will take action to ensure the outstanding points are checked by him/herself, a user or a miscellaneous staff member (e.g. a security guard who also has a client unit). This occurs during the first few minutes of the next primary conformance period.

10. When the second timer reaches then end of this secondary conformance period the server 400 checks again to see if all the necessary points have been checked. 11. If any points are still unchecked then the server sends an alert to the supervisor notifying them of the outstanding points. At this stage it is too late to correct this error and a breech in duty of care may have occurred.

As a user does his or her circuit, they may come across something that needs to be noted , but that does not stop the user from what they are doing. This is termed a minor event. For example, a user may identify a maintenance issue that centre management needs to be told of at the end of the shift. This is handled in the following manner: -

1. The user selects a minor event entry on the client unit. 2. The user is presented with a list of possible events including "other" and selects the appropriate event.

3. The user enters any relevant comments.

4. The client unit 200 sends this data to the server 400. That is, date/time, issue, comments, location, user. The location of the event is entered from a pull down list of shop numbers to show the nearest shop to the event.

5. The server 400 enters the data in the event log.

6. The client unit 200 stores the data in its local event log. This event can then be automatically included on the daily report and also retrieved when required as part of other reports. No other action is required of the user as the daily reports automatically included in the event for centre management or for the supervisor to pass on to centre management. There are times when a user comes across something that requires extra attention and prevents the user from continuing with the circuit. These events are termed a major event. These events are handled by temporarily pausing the circuit for up to a pre-determined amount of time (defined in the database 401). The system does the following things: - 1. The user goes to a major event screen and selects the type of event

(these are listed in the database 401 ).

2. The client unit 200 sends data to the server 400 outlining the major event, which is stored in the event log.

3. The client unit 200 stores this data in its local event log. 4. A new timer starts on the server 400.

5. The server 400 sends an alert to the supervisor notifying them that a particular user is dealing with a specified major event.

6. If the new timer on the server 400 reaches the maximum pause time then it sends an alert to the user and the supervisor informing them that this time is up. This timer is then stopped. 7. The supervisor can then contact the user and if the user needs more time to deal with the event, then the supervisor can ask another user to do an expanded circuit to cover the uncovered points.

8. When the initial user finishes dealing with the major event, then they enter any further data about the event that may need recording (e.g. free text comments). They then indicate that they have finished dealing with the event.

9. The client unit 200 sends data to the server 400 outlining the end of the pause event. This data is stored in the event log on the server 400 and the client unit.

10. An alert is sent to the supervisor who can then ask the alternate user to go back to his normal circuit.

There are instances where an event may occur that prevents some or all points within a site from being checked. This is term as a catastrophic event. For example, an armed hold up may prevent access to some points for staff safety, or a fire may require the evacuation of the whole centre and therefore prevent access to all points.

Catastrophic events are divided into two types of events: partial catastrophe, which prevents access to some points and complete catastrophe, which prevents access to all points. The list of events could be classified as partial or complete catastrophic events or just as general catastrophic events. A user may also indicate if the catastrophe is partial or complete when it occurs. The system handles a catastrophic event in the following way: - 1. The user selects the type of event on the client unit.

2. If the events are just classified as catastrophic then the user selects whether the event is a partial or complete catastrophe.

3. The client unit 200 sends this data to the server 400 and logs it locally. 4. The server 400 stores the data in the database 401 and sends an alert to all client units 200 (including miscellaneous users) informing them of the event.

5. If the event is a partial catastrophe then the system continues to record user activity and monitor conformance. Every conformance period in which the catastrophic event is active, the supervisor is alerted that points have been missed. However, a suitable reason for missing these points is logged in the database 401 so the supervisor can safely ignore these alerts. If the event is a complete catastrophe then the system continues to record activity, but does not monitor conformance. This is to allow staff to focus on emergency duties without being distracted by irrelevant alerts.

6. At such time that the event is over, the supervisor can enter into the client unit 201 that the event has concluded. This is logged locally and on the server 400.

Everyday two daily checks are performed. The night supervisor performs an external check of the site prior to handing over to the day supervisor and the day supervisor performs an internal check. The system records the details of this check and monitor the supervisor during the check to ensure that the all points that need to be checked are checked and checked in order. The daily check will be performed as follows: -

1. The supervisor selects the daily check on their client unit 200 and is presented with a list in order of items and points they need to check.

2. The client unit will check that the point before the current point and check it against the database to ensure the operator is performing the check in the correct order. If not it will alert the user.

3. Once the check is completed the operator will press a button, which will submit the data to the server.

4. The server will store the report in the database. The slipperiness of the floor surfaces in public spaces needs to be carefully monitored and maintained to ensure public safety. Current practice involves a specialist testing the slipperiness of the floors once a month and a rotating regime of recoating floor surfaces. The system is used to log these events simply by configuring them as minor events in the database 401. The supervisor can then enter these into his client unit 201 as they occur. A permanent record exists of when these events occurred.

Conformance to a maintenance plan could be monitored on a monthly report, which searches the event log to see if the appropriate events have occurred. If they haven't then the report can indicate what has been missed.

The server 400 has the ability to generate as many reports as are required. A daily report is the primary report that is required. The supervisor, centre management and other allocated persons may view this point daily.

Everyday the monitoring system 100 performs tasks when it is started and stopped. At start-up the system checks system integrity and starts the circuit timer. At stop the system reconciles logs, backs-ups data and restarts the hardware.

The monitoring system 100 performs a system integrity test at start up. In particular the monitoring system 100 checks that it has access to the database 401. In the event of a monitoring system 100 crash, the monitoring system 100 ensures that data is not further corrupted. The monitoring system 100 is designed so that it starts the timer for conformance monitoring at a certain time each day. Hence, each user must be on-site and beginning their duties at the correct time to conform to their circuit parameters.

At stop the system reconciles the client unit 200 logs with the database 401. This redundancy ensures that no data is lost in the event of either a server 400 or client unit 200 crash. To perform this reconciliation the data in the client units 200 must be uploaded to the server 400. This is done via a battery charger/Ethernet cradle. The client units 200 are plugged into this cradle that charges the battery overnight and uploads the data via a wired connection. This allows users to simply plug the units into the cradle and have the log reconciliation performed after they leave.

After the logs have been reconciled the system then backs up the database 401. A two layer backup strategy is typically used. The first layer is a daily backup whereby the database 401 is saved onto one of two media (for example a zip disk). These two disks are rotated. This way if a server 400 crash was to occur in the middle of backup, which corrupts the backup disk and the server 400's data, and then another backup would exist that was only 24 hours old. Only a single day's of data is lost and the opportunity to recover this data from the local logs of the client units 200 still exists. A second layer of backup, which occurred weekly, could create another backup onto a media that was stored at another location. Should a disaster occur on-site that destroyed the server 400 and backup media then only a single weeks worth of data is lost.

To complete the stop, process the server 400 is restarted daily to maintain system stability. Both the backup and restart is performed automatically at the system level using an application such as Task Scheduler. This is scheduled every morning at a time that is well after the system has finished reconciling the logs.

The interface, normally the touch screen, provides intuitive labels that match the language currently used by the users. The interface is simple and does not include unnecessary features. The majority of tasks are able to be completed in a minimum of touches. The user is able to use their finger and not require the stylus except when they need to enter comments. All onscreen buttons are large to facilitate this. The user does not need to navigate through several layers to complete their task. The interface provides positive feedback through sound when an event is logged. In a noisy environment this is a loud sound at a pitch that is easily audible, especially if the client unit 200 is on their belt.

All the tasks that users need to complete are available for selection on the interface. The tasks are organised into preliminary categories and interaction flowcharts.

Because the monitoring system 100 is a mission critical application it is important that redundancies are built into it at all possible points of failure. In the event of a component failing, a strategy is in place to capture data, resolve the problem and account for any missed entries in the event log.

Any critical failure is logged in the database 401 as a major event so that a reason is demonstrated as to why log entries are missing. Once the failure has been rectified the event is logged off.

Possible points of failure are the server 400, client units 200, network and RFID 302 points.

The failure of the server 400 prevents conformance being monitored. The local event logs on the client units 200 are used to restore data not logged by the server 400, but the system does not alert the supervisor in real time that there has been a failure in conformance. The client unit 200 are programmed to alert all users that communication has been lost with the server 400 and log this in the local event log. A reason can then be identified for not responding to a failure in conformance if that were to occur. This is recorded on all client units 200 so that loss of communication is identified as network wide or only on one or more client units 200. Once communication has been restored the users are alerted and a log entry generated marking the end of the event.

In the event of a server 400 crash, a local user is able to restart the monitoring system 100 so that it can continue operating. On restart the monitoring system 100 performs an integrity test to ensure it has access to the database 401. It identifies that it is past the normal circuit start time and start a new conformance period immediately. In the case of a failure that disables the system beyond the repair of a local user, external technical support is notified. If necessary, a back up server 400 may be available that could be installed locally prior to the start of the next day. This monitoring system 100 is configured from the backup media from the prior to the crash and then synchronised with the data from the client units 200. It is then ready to operate the next day until the original server 400 is repaired.

A client unit 200 failure may go unnoticed by the user, but becomes apparent to the supervisor at the end of a conformance period. . At the end of a conformance period the server 400 notifies the supervisor that a series of points have been missed. The supervisor recognises who is responsible for these points and asks them to check that their client unit 200 is operating. If the system is handling voice communication then the user has to be physically located by the supervisor. Once the user or supervisor determines that there is a problem with a client unit, the supervisor logs the failure as a major event. He or she then instructs other users to expand their cleaning circuits to cover the points being missed by the user of the failed client unit 200 whilst the problem is being resolved. At least one spare client unit 200 is available on each site to replace failed units. The user can get this unit and log in on the new unit. Once the user has determined that the new client unit 200 is working, he or she informs the supervisor. The supervisor logs off the client unit 200 failure event and instructs other users to return to their normal circuits. The failed client unit 200 is examined by technical support to determine if the problem is a software or hardware issue. If it is a hardware issue then the unit is returned to the supplier for repair. Software issues are able to be resolved by technical support to bring the client unit 200 back on line the next day. Network failure also prevent conformance being monitored because the server 400 cannot receive events and log them in the database 401. This data is restored from the client units 200 at the end of the day.

The server 400 knows a network failure has occurred at the end of a conformance period. If all points have been missed then the server

400 logs the error as a critical failure rather than as a conformance failure.

Later reporting then identifies that the failure was most likely a network failure.

As in a server 400 failure, the client units 200 are able to identify a loss of communication, alert the users and log the failure. The supervisor then takes action to determine the cause of the failure.

The supervisor firstly checks the server 400, which display clearly that the network has lost its connection. The supervisor knows that the problem is the network and does not restart the server 400 (restarting the server 400 is unnecessary and would create event logs which might confuse later reporting).

The second step is to check the network. The supervisor then advises technical support that the network is completely down or that a particular network access point is not working. Technical support responds by the start of the following day to attempt to resolve the problem. Simple software or connectivity problems are able to be resolved quickly, however, hardware failures require intervention from the supplier.

The failure of an RFID 302 unit prevents the system from logging that an individual point has been checked. This comes to the attention of the supervisor at the end of one conformance period. If the supervisor has been alerted prior to the end of the period that a point has been missed, he or she instructs a user to recheck the point. When rechecking any point a user should pay careful attention to an LED on RFID 302 unit to ensure the RFID 302 is functioning. If the unit is not functioning then the LED does not flash and the client unit 200 does not recognise the point. The user then informs the supervisor of the problem.

Once the supervisor has been alerted to the RFID 302 failure, the supervisor logs the failure as a major alert. He or she can then take action to replace the failed unit. A spare RFID 302 unit is available onsite at all times. The supervisor or maintenance staff can replace the faulty unit with the new unit.

The new RFID 302 unit is then coded as belonging to that specific point. The supervisor can do this via his client unit. Using a maintenance interface, the supervisor can enter the point number and write this to the RFID 302. A test function is available on the client unit 200 that reads the point number from the RFID 302 and displays it on the screen. This function is used at anytime to determine whether any RFID 302 unit is functioning correctly. Once the new RFID 302 unit is working, the supervisor can log off the RFID 302 failure event.

The above monitoring systems provides a warning that a particular area has not been attended in a predetermined time. The area can thus be attended to quickly. If any litter and/or spillage is observed in the area then this litter and/or spillage is removed. Persons using the shopping centre are less likely to injure themselves as the litter and/or spillage is less likely to remain within the shopping centre for extended periods of time. Further, the shopping centre owner and/or contractor, in attempting to be diligent, decreases the likelihood of being found to be negligent if a person does injure themselves. Reports and/or records show cleaning frequency in an order way.

A person skilled in the art would realise that the monitoring systems could be used for other forms of monitoring, including security monitoring. Further, a person skilled in the art would also realise that the monitoring systems could be used in a single premises, such as a warehouse, or on various related premises, such as a number of banks. It should be appreciated that various changes and modifications may be made to the embodiment described without departing from the spirit or scope of the invention.

Claims (15)

CLAIMS:

1. A system for monitoring attendance comprising: recording means to record that a user has attended a predetermined location; transmitting means to transmit a signal that the user has attended said location; receiving means to receive said signal; a timer to set a predetermined time limit for the user to record attendance at said location; an alert means to provide an alert; wherein said alert means is activated if said user has not attended said location within said time limit.

2. The system for monitoring attendance according to claim 1 wherein the recording means and transmitting means are located within a discrete unit.

3. The system for monitoring attendance according to claim 2 wherein the discrete unit is fixed adjacent said predetermined location.

4. The system of claim 3 wherein the timer forms part of the discrete unit.

5. The system for monitoring attendance according to claim 2 wherein the discrete unit is portable.

6. The system for monitoring attendance according to claim 3 wherein the discrete unit is hand held.

7. The system for monitoring attendance according to claim 2 wherein the receiving means is connected to a server.

8. The system of claim 7 wherein the server logs and stores data provided by said signals received by said receiver.

9. The system of claim 7 wherein said server is remotely accessible.

10. The system of claim 8 wherein said server produces reports from said data.

11. The system of claim 1 wherein the alert means provides an alert in real time.

12. The system of claim 1 wherein the said signal is send by said transmitting means to said receiving means via a wireless network.

13. A method for monitoring attendance including the steps of: recording the attendance of a user at a predetermined location; transmitting a signal via transmitting means that indicates that said user has attended said location; receiving said signal via a receiving means activating an alert means if said has not attended said location within a predetermined time limit.

14. The method of claim 12 wherein data received from said signal is logged and stored.

15. The method of claim 12 wherein the activation of the alert means is conducted in real time.