Four monitor and checkpoint designating system5166499Abstract A tour monitor system includes a portable tour monitor and a central programming/report generating computer. The tour monitor includes a bar code reader, an alphanumeric display, and an alphanumeric keyboard. The tour is organized into zones, each including a set of checkpoints, wherein each checkpoint is labeled by a bar code. The tour monitor is programmed to prompt the guard through the tour by displaying the names of successive zones. In addition, individual checkpoints can be designated as higher or lower priority checkpoints, and the tour monitor is programmed to alert the guard if higher priority checkpoints are missed, and to require the guard either to scan the missed higher priority checkpoint or to provide an override signal. The tour monitor also allows the guard to enter alphanumeric messages which are stored in combination with the scanned checkpoint codes in a log. This log is then transmitted to the programming/report generating computer for analysis. Preferably, reports are organized in terms of zones, and reports specifically highlight higher priority checkpoints which were missed. By organizing the tour into zones and checkpoints, the tour monitor can be programmed more efficiently. Claims What is claimed is: Description BACKGROUND OF THE INVENTION
TABLE 1
______________________________________
Record Type Log Data Time Stamp
______________________________________
Start Route Number Date, Time
Guard Guard ID Number
Date, Time
Enter Zone Zone Number Date, Time
Leave Zone Zone Number Date, Time
Read Bar Code Date, Time
Finish Route Number Date, Time
______________________________________
At the beginning of each tour, a Start record and a Guard record are entered into the log. Once this has been accomplished, control is transferred to the Advance to Next Zone routine of FIG. 9. This routine first checks to determine whether this is the first zone of the tour. If not, a Leave Zone record is entered into the log. In any case, the routine then reads the next zone in the route and checks to determine whether the tour has been completed. If so, a tour complete message is displayed on the display 34 and a Finish record is entered into the log. The routine then shuts down the monitor 30 and awaits for a next key to be pressed. Assuming that this is not the end of the tour, the routine then checks to see if HAND-OFF is set. If so, a Guard record is entered int he log and in any case an Enter Zone record is entered into the log and flags are cleared for all of the higher priority checkpoints in the new zone. These higher priority checkpoints are referred to as "must scan" checkpoints in the figures. Control is then transferred to the Display Zones routine of FIG. 10. The Display Zones routine of FIG. 10 first checks TEMP-DATA. TEMP-DATA is a temporary storage location that is used to store a scanned bar code when the scanned bar code is outside of the current zone. Thus, TEMP-DATA will be equal to zero in the event the scanned bar code is inside the current zone. If TEMP-DATA is not equal to zero, TEMP-DATA is set equal to the scanned checkpoint variable and control is transferred to the Process Scanned Checkpoint routine of FIG. 13. Otherwise, HAND-OFF and TEMP-DATA are cleared and both the current zone and the next zone of the tour are displayed on the display 34. For example, when the guard enters Zone FLlA of FIG. 3, the display 34 is caused to display the messages "1ST FLOOR-W/1ST FLOOR-E". The routine then waits for the input of a bar code from the bar code reader 36 or a key input from the keyboard 32. If either the F1 or F4 key is pressed, control branches to the routines of FIGS. 11 and 12, respectively. If the mode key is pressed, the monitor 30 is shut down to wait for additional key inputs. Assuming that a bar code has been scanned, the routine then checks for specific scanned codes. If the scanned code is equal to "ZZ", the routine stores an alphanumeric keyboard entry from the keyboard 32 and returns to the start of the Display Zones routine of FIG. 10. If the scanned code is equal to "YY", the routine confirms that the user is requesting a hand-off, and then sets HAND-OFF and branches to node 11 of FIG. 8. If the scanned bar code is equal to "XX" the routine branches to the Request Advance routine of FIG. 11 if the guard is in the last zone, otherwise an error, message is displayed and control is returned to the start of the Display Zones routine of FIG. 10. Finally, if the scanned code is an incident code, the scanned code is simply written into the log as a Read entry before control is returned to the start of the Display Zones routine. Assuming that the scanned code is equal to none of the tested values, control branches to the Process Scanned Checkpoint routine of FIG. 13. FIG. 11 shows the Request Advance routine that can be reached from the Display Zones routine of FIG. 10. This routine first checks to determine whether all of the higher priority or must scan checkpoints in the current zone have been scanned. If some of the must scan checkpoints have not be scanned, then an error message "MISSED MUST-SCAN/CANNOT ADVANCE/HIT F4 TO REVIEW/MISSED MUST-SCAN" is presented on the display 34 and control is returned to the Display Zones routine of FIG. 10. Otherwise HAND-OFF is checked. If it is set, control is transferred to node 11 of FIG. 8 to get the new guard ID. Otherwise, TEMP-DATA is checked. If it is not equal to zero (indicating that the scanned code is outside of the current zone), control is transferred to the Advance to Next Zone routine of FIG. 9. Similarly, if TEMP-DATA is equal to zero and the o.k. to advance test is met, control is transferred to the Advance to Next Zone of FIG. 9. Otherwise, control is returned to the Display Zones routine of FIG. 10. FIG. 12 shows the Review Missed Must-Scans routine that is entered by use of the F4 key in the Display Zones routine of FIG. 10. The first step is to search for any higher priority or must scan checkpoints which were missed in the current zone. If there are no such checkpoints, a message is displayed ("END OF MUST-SCAN/POINTS THIS ZONE") and control is returned to the Display Zones routine of FIG. 10. Otherwise, the name of the missed must-scan checkpoint is displayed and the user is asked whether he wishes to skip this must scan checkpoint. If the received keyboard entry indicates the user wishes to skip the must scan checkpoint, then an appropriate message is displayed and the fact that the user or guard has provided an override signal to skip the checkpoint is recorded. The routine then finds the next missed must scan checkpoint and repeats the process. FIG. 13 shows the Process Scanned Checkpoint routine that is called by the Display Zones routine of FIG. 10. The Process Scanned Checkpoint routine first determines whether the scanned bar code corresponds to one of the higher priority checkpoints in the current zone. If so, this higher priority checkpoint is indicated as having been scanned. Then TEMP-DATA is checked. If TEMP-DATA is not equal to zero the scanned bar code is date stamped and recorded in the log as a Read record, and TEMP-DATA is cleared before control is returned to the Display Zones routine of FIG. 10. If TEMP-DATA is equal to zero, the checkpoint corresponding to the most recently scanned bar code is checked to determine whether that checkpoint is in the current zone. If so, a Read record is recorded in the log. If the most recently scanned checkpoint is outside of the current zone, the routine then determines whether the scanned checkpoint is in the next zone. If not, an error message is displayed on the display 34 and a Read record is entered into the log before control is returned to the Display Zones routine of FIG. 10. If the scanned checkpoint is in the next zone, the scanned checkpoint is stored in TEMP-DATA and control branches to the Request Advance routine of FIG. 11. Table 2 provides a sample log as created by the tour monitor 30 during a tour of the routine illustrated in FIG. 3.
TABLE 2
______________________________________
SAMPLE LOG
LOG
ENTRIES
______________________________________
1 S R002 890113150622
2 G CEB 890113150622
3 E FL1A 890113150622
4 R F50A 890113151019
5 R F50B 890113151042
6 R F50C 890113151105
7 L FL1A 890113151210
8 E FL1B 890113151210
9 R F51A 890113151220
10 R ZZ 890113151235
11 R F51D 890113151350
12 L FL1B 890113151410
13 F R002 890113151410
MESSAGES
14 WINDOW OPEN
______________________________________
In Table 2, the route is designated R002. The checkpoint codes for checkpoints 50a-50c and 51a-51d are F50A-F50C and F51A-F51D, respectively. The date stamp is a twelve digit number in the form year-month-day-hour-minute-second. Note in the log of Table 2 that the guard has failed to scan the 51b and 51c cheokpoints. Of these the 51c checkpoint is a higher priority, must scan checkpoint. Also at line 10 of the log the guard has scanned the bar code ZZ from a pocket reference card and then has entered the alphanumeric message "WINDOW OPEN", which is shown schematically at line 14. A number of important operational features of the tour monitor 30 have been illustrated by the flowcharts of FIGS. 4-13. In particular, it should be noted that the monitor 30 displays on the display 34 both the name of the current zone and the name of the next zone in the tour. These zone identifying messages assist a new guard in conducting the tour in the order intended, and they also assist an experienced guard in learning a new tour. Second, the monitor 30 is pre-programmed by the tour defining record for a tour made up of an ordered sequence of zones, wherein each zone includes a set of checkpoints that are not ordered within the set. This allows the guard to check the checkpoints within each zone in any order he desires while enforcing an overall sequence of zones in the tour. Third, the checkpoints within each zone are designated as either higher priority (must scan) checkpoints or lower priority checkpoints. The monitor 30 does not take any action if lower priority checkpoints are not scanned during the tour. However, in the event any higher priority checkpoints are not scanned, the monitor 30 does not advance to the next zone until the guard has been reminded that the higher priority checkpoints were not scanned and the guard has indicated an intention to override this warning by skipping rather than scanning the missed checkpoints. This allows flexibility during the tour, because the guard can scan only a varying number of the lower priority checkpoints in each tour. Nevertheless, the guard is reminded that each of the higher priority checkpoints is to be scanned each tour. For example, potential fire sources such as coffee pots can be designated as higher priority checkpoints so that in each tour each coffee pot in a building is checked to ensure that it is unpowered and therefore not a fire hazard. Another important advantage is that the monitor 30 allows the guard to record any desired alphanumeric message (within the allowed length) at any point within the tour. This is done by scanning a bar code that designates an alphanumeric message is to follow, and then entering the alphanumeric message via the keyboard 32. The keyboard 32 generates key signals which are then stored by the monitor in association with the bar codes of the log for later transmission to the computer 12. This feature provides an important degree of flexibility in the log which allows the guard to record unexpected events. Turning now to FIGS. 14-16, the tour programming software 20 and the report generating software 22 of the computer 12 will now be described. FIG. 14 shows an overall flowchart of the software of the computer 12. The software requires a password of the user and then after monthly maintenance displays a main menu and waits for a selection. As shown in FIG. 14 there are four basic sets of routines available to the user. The first is a down-load routine that downloads a tour defining record to the tour monitor 30. The tour defining record is of the type described above prior to the discussion of the program of FIG. 4, and it includes a route record which is created with the program of FIG. 16 described below. The user can also select from the main menu an up-load routine that up-loads a completed tour log (as for example that shown in Table 2) from the tour monitor 30. The letter "C" can be used to select processing routines that process a completed tour log and print a tour report. Table 3 is an example of a report that may, for example, be printed in response to the tour log of Table 2. This report provides a summary of the information included in the log, in a format that is readily understood by supervisory personnel.
TABLE 3
______________________________________
DETAIL ROUTE REPORT
______________________________________
Guard Name: John Doe
Check In: 1-13-89 15:06
Route Name: Route No. 2
Check Out: 1-13-89 15:14
Total Time: 0 Hr. 8 Min.
Zones Checked: 2 of 2
Total In Zone Points: 7
In Zones: 0 Hr. 8 Min.
In Zone Points Checked: 5
Between Zones: 0 Hr. 0 Min.
Percent Checked: 71%
Must Scans Missed: 1
______________________________________
* = Out of Zone
! = Missed Must Scan
Zone Check Bar Check Between
No. Point Code Time Time Incident
______________________________________
Check In 15:06
Enter Zone FL1A - 1st Floor-W
15:06 00:00
FL1A Suite 100- F50A 15:10 00:04
Kitchen
FL1A Coffee Pot F50B 15:11 00:01
FL1A Window F50C 15:11 00:00
Leave Zone
Enter Zone FL1B - 1st Floor-E
15:12 00:01
FL1B Hall Window F51A 15:12 00:00 WINDOW
OPEN
! Suite 102 F51C
FL1B Hall Door F51D 15:14 00:02
Leave Zone 15:14 00:00
Check Out 15:14 00:00
______________________________________
Note in particular that for each checkpoint that was scanned during the tour the report includes a description of the checkpoint along with the checkpoint's zone number, bar code and the time the checkpoint was scanned. As shown in Table 3, the report is divided into sections corresponding to the separate zones of the tour. This allows supervisory personnel to focus on particular zones easily. Another important feature of the report of Table 3 is that it includes the alphanumeric messages that were keyed by the guard after the bar code "ZZ" was scanned. Note, for example, the "WINDOW OPEN" message in the incident column. A third important feature of the report of Table 3 is that higher priority checkpoints that were not scanned by the guard are highlighted, while missed lower priority checkpoints are not indicated. Note the exclamation point at the line associated with Suite 102, bar code F51C. The exclamation point indicates that the guard missed this higher priority checkpoint. Also, the header of the report summarizes the total number of higher priority or must-scan checkpoints which were missed. By pressing the letter "D" in the main menu, the user can select the print history reports routine shown in FIG. 15. This routine first displays a history report menu and then waits for the user to select one of five possible history reports. For example, the system can be commanded to prepare and print reports summarizing the history of a particular guard, a particular zone or zones, a particular checkpoint or checkpoints, and incidents reported by guards. Finally, detailed history reports are also available. By typing the letter "E" in the main menu of FIG. 14, the user can select the file maintenance routines shown in FIG. 16. The file maintenance routines allow the user to create, delete and edit entries in a guard ID file, a set of zone files, and a set of route files. The guard ID file maintains a list of authorized guard codes. Once the guard ID file has been created and updated as necessary in the routine of FIG. 16, this file is included in the tour defining record (Item 7). In the zone maintenance portion of the routine of FIG. 16 a user can create or delete a zone and add, delete or edit checkpoints within the zone. Within each zone, a bar code, description and must-scan flag are entered by the user to define each checkpoint of the zone. The bar code identifies the bar code associated with the checkpoint; the description is used by the tour monitor 30 in the event of a missed higher priority checkpoint and by the report generating software; the must scan flag designates the checkpoint as either a higher priority or a lower priority checkpoint. None, some, or all of the checkpoints within any zone can be designated as higher priority checkpoints. Each zone can be thought of as a set of checkpoints, and if desired a zone can have no checkpoints (the empty set). Such a zone is in effect merely a message displayed to the guard at a selected point in the tour. The route maintenance portion of the routine of FIG. 16 allows the user to create and delete a route and to add and delete zones within a route. Finally, the print data listing portion of the routine of FIG. 16 allows the user to print out a list of guards, zones and routes. The file maintenance routine of FIG. 16 is used by a user first to create a number of zones. In the example of Route No. 2 shown in FIG. 3, the user creates two zones, FL1A and FL1B. For each checkpoint in each zone, the user enters the checkpoint bar code, description, and must-scan flag for that checkpoint. The user then uses the route maintenance portion of the routine of FIG. 16 to actually create the route. In this case, the user merely indicates that Route 2 is to include zones FL1A and FL1B. Individual zones may appear in more than one route or more than once in a route, and individual checkpoints may appear in more than one zone. This allows a high degree of flexibility in programming the tour monitor 30. For example, a user can change the order in which zones are inspected, or move individual zones from one route to another, simply and easily, without re-entering individual checkpoints. This flexibility is directly attributable to the fact that each route is a set of zones, and that each zone is a set of checkpoints. This arrangement has been found to simplify the programming of the tour monitor 30 when routes are being modified. Simply by way of example in order better to define the presently preferred embodiment of this invention, Appendices 1-1 and 2-1 list the programs executed by the computer 12 and the tour monitor 30, respectively. Appendix 3-1 provides instructions for usihg these listings, and Appendices 1-2, 1-3 and 1-4 are also referenced in Appendix 3-1. In each case the listing is to be regarded as the primary disclosure of the presently preferred embodiment. In the event of any inconsistency between the listing and the flowcharts the listing is to govern. In the event of any inconsistency between the flowcharts and the written description, the flowcharts are to govern. Of course, it should be understood that a wide range of changes and modifications can be made to the preferred embodiments described above. For example, this invention is not limited to use in security tours, but can readily be adapted for other types of tours such as the tours to inspect or perform janitorial activities such as housekeeping activities. Furthermore, this invention is not limited to the specific hardware used in the foregoing examples. For example, magnetic code readers, character recognition devices and the like can be substituted for the bar code reader described above. Furthermore, it is not essential in all embodiments that a cable 42 be used to interconnect the monitor 30 with the computer 12. A wide variety of communication approaches can be used, including modems, radios, and optical communication systems. In the event remote transmission capabilities are provided to the monitor 30, it is not essential that the log be stored in memory until the tour is completed prior to transmission of portions of the log back to the computer 12. Of course, a wide variety of reports can be generated utilizing the information transmitted from the monitor 30 to the computer 12. It is therefore intended that the foregoing detailed description be regarded as illustrative rather than limiting, and that it be understood that it is the following claims, including all equivalents, which were intended to define the scope of this invention. ##SPC1## ##SPC2## ##SPC3## ##SPC4## ##SPC5## ##SPC6## ##SPC7## ##SPC8## ##SPC9## ##SPC10## ##SPC11## ##SPC12## ##SPC13## ##SPC14## ##SPC15## ##SPC16## ##SPC17## ##SPC18## ##SPC19## ##SPC20##
|
Same subclass Same class Consider this |
||||||||||