Monitoring system with particular application to monitoring a cash-basis operation

Abstract

The invention enables an operation to be monitored directly by a single person at a monitoring site. Certain predefined activities at one or more operating sites are automatically monitored. Information regarding these activities is conveyed to the monitoring site as directed by the person doing the monitoring. The information collected at the monitoring site is used to describe the status of the operation at a given time or the change in status of the operation over a period of time, and to verify information about the conduct of the operation supplied by third parties to the person monitoring the operation. The operation can be conducted at any number of operating sites and the operating sites can be separated by any distance. The monitoring site can be, and frequently is, geographically remote from the operating sites. Further, the monitoring site can be mobile, without affecting the monitoring capabilities of the invention. The invention is useful in monitoring a variety of commercial operations such as, for example, a chain of restaurants or multiplicity of car washes. Further, the invention is particularly useful in monitoring commercial operations that operate on a cash-basis or that are conducted primarily on a self-serve basis such as, for example, laundromats or arcades. However, the invention can be used to monitor any type of operation.

Claims

We claim:

1. A system for automatically monitoring the conduct a cash-basis operation that takes place at an operating site, comprising:

means for automatically determining the amount of cash that should have been deposited in at least one machine located at the operating site during a specified period of time;

means for maintaining information regarding the amount of cash collected from each of the at least one machines during the specified period of time; and

means for comparing the amount of cash collected to the amount of cash that should have been deposited.

2. A system as in claim 1, wherein the determining means further comprises means for sensing each activation of each of the at least one machines during the specified period of time.

3. A system as in claim 1, further comprising means for uniquely identifying each of the at least one machines, so that the means for determining, maintaining and comparing enable comparison of the amount of cash collected to the amount of cash that should have been deposited for each of the at least one machines.

4. A system as in claim 3, further comprising means for identifying the type of each of the at least one machines, so that the means for determining, maintaining and comparing enable comparison of the amount of cash collected to the amount of cash that should have been deposited for each type of machine.

5. A system as in claim 1 further comprising means for monitoring the operation of one or more machines at the operating site.

6. A system as in claim 5, wherein the machine operation monitoring means further comprises means for sensing an opening or closing of a service door on each of the one or more machines.

7. A system as in claim 5, wherein the machine operation monitoring means further comprises means for monitoring each repair made to one or more of the machines.

8. A system as in claim 7, wherein the repair monitoring means further comprises:

means for recording the date of the repair;

means for recording the name of the person who performed the repair; and

means for recording a description of the repair.

9. A system as in claim 5, wherein the machine operation monitoring means further comprises means for determining when one of the machines is out of order.

10. A system as in claim 9, wherein the out-of-order machine determining means further comprises means for sensing each activation of each of the one or more machines.

11. A system as in claim 9, wherein the out-of-order machine determining means further comprises means for monitoring an out-of-order switch located on each of the one or more machines.

12. A system as in claim 9, wherein the machine operation monitoring means further comprises:

means for determining the date that a machine becomes out of order;

means for determining the time of day that a machine becomes out of order;

means for determining the operating site at which each out-of-order machine is located; and

means for determining identifying information regarding each out-of-order machine.

13. A system for managing the operation of a plurality of laundromats, comprising:

means for remotely monitoring from a monitoring site a first set of predefined aspects of the operation of the plurality of laundromats; and

means for remotely controlling from the monitoring site a second set of predefined aspects of the operation of the plurality of laundromats.

14. A system as in claim 13, wherein the remote monitoring means further comprises:

means for monitoring cash receipts at each laundromat; and

means for monitoring the operation of one or more machines at each laundromat.

15. A system as in claim 13, wherein:

one or more machines includes a display; and

the remote controlling means further comprises means for controlling the contents of the display.

16. A system as in claim 13, wherein

the remote controlling means further comprises means for establishing an activation price of one or more machines at each laundromat.

17. A system as in claim 16, wherein the price establishing means further comprises means for establishing different prices for different time periods during the day.

18. A system as in claim 13, wherein:

a plurality of machines are located at each laundromat; and

the remote controlling means further comprises means for testing the operation of one or more machines at each laundromat.

19. A system as in claim 18, wherein the remote controlling means further comprises means for placing a machine out of service when the machine does not perform acceptably well during the testing.

20. A system for acquiring data regarding the operation of a cash-basis operation that takes place at an operating site, comprising:

means for automatically acquiring data regarding cash receipts at the cash-basis operation;

means for automatically acquiring data regarding the operation of one or more machines at the cash-basis operation; and

means for automatically transferring the acquired data from the operating site to a remote monitoring site for use in monitoring the cash-basis operation.

21. A system as in claim 20, wherein the data is acquired automatically at each of a plurality of predetermined times according to a single instruction by a user.

22. A system as in claim 21, wherein the data can also be acquired automatically a single time at the instruction of a user, the data acquisition beginning immediately after the user instruction.

23. A system for monitoring from a monitoring site the conduct of a cash-basis operation that takes place at an operating site, comprising:

means for automatically determining, for a machine at the operating site, the amount of cash that should have been deposited in the machine during a specified period of time; and

means for monitoring the operation of a machine at the operating site.

24. A system as in claim 23, wherein the operation takes place at a plurality of operating sites.

25. A system as in claim 23, wherein the monitoring site is geographically remote from the operating site.

26. A system as in claim 23, wherein the determining means further comprises means for sensing each activation of the machine during the specified period of time.

27. A system as in claim 23, wherein the monitoring means further comprises means for sensing openings or closings of a service door on the machine.

28. A system as in claim 23, wherein the operation is a self-service operation.

29. A system for monitoring the conduct of an operation that takes place at an operating site, a plurality of devices to be monitored being located at the operating site, comprising:

a plurality of sensors, at least one sensor being mounted on each device, each sensor adapted to acquire data regarding the operation of the device on which the sensor is mounted;

a plurality of internal control units, at least one internal control unit being mounted on each device, each internal control unit adapted to receive data from at least one sensor;

a site controller unit located at the operating site;

a plurality of communications devices for transferring data between each of the internal control units and the site controller unit;

a main controller unit located at a monitoring site; and

a communications device for transferring data between the site controller unit and the main controller unit.

30. A system as in claim 29, further comprising means for monitoring communications between the main controller unit and the site controller unit and communications between the site controller unit and the internal control units.

31. A system as in claim 29, wherein the monitoring site is geographically remote from the operating site, the system further comprising means for synchronizing the time of day at the location of the monitoring site to the time of day at the location of the operating site.

32. A system as in claim 29, wherein the communications device for transferring data between the site controller unit and the main controller unit comprises:

a modem; and

a telephone line.

33. A system as in claim 29, wherein the plurality of communications devices for transferring data between each of the internal control units and the site controller unit comprises a second plurality of communications devices, one of the second plurality of communications devices transferring data between the site controller unit and one of the internal control units, each of the remainder of the second plurality of communications devices transferring data between a pair of internal control units, such that less than all of the internal control units are directly connected to the site controller unit by a communications device.

34. A system as in claim 29, wherein the communication monitoring means further comprises:

means for detecting communication conditions, the types of communication conditions including a successful communication, a communication problem and a communication error; and

means for recording communication conditions.

35. A system as in claim 34, wherein the communication condition detecting means further comprises:

means for determining the type of a detected communication condition;

means for determining the date of occurrence of a detected communication condition;

means for determining the time of day of a detected communication condition;

means for identifying the operating site with which a detected communication condition is associated;

means for identifying the device with which a detected communication condition is associated;

means for obtaining a description of a detected communication condition; and

means for determining, if a communication condition is a communication error or communication problem, when the communication condition has been corrected.

36. A method for automatically monitoring the conduct a cash-basis operation that takes place at an operating site, comprising:

automatically determining the amount of cash that should have been deposited in at least one machine located at the operating site during a specified period of time;

maintaining information regarding the amount of cash collected from each of the at least one machines during the specified period of time; and

comparing the amount of cash collected to the amount of cash that should have been deposited.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to monitoring the conduct of an operation. The monitoring is typically done remotely and frequently encompasses an operation that is conducted at a multiplicity of geographically separate sites. In particular, the invention relates to monitoring the conduct of a commercial operation and, most particularly, to monitoring the conduct of a cash-basis commercial operation.

2. Related Art

The proprietor of a commercial operation must continually monitor that operation to, for example, verify that all receipts and payments are accounted for properly, ensure that all equipment associated with the operation is working properly, and confirm that each employee is present during assigned working hours. Such monitoring can be very time consuming, particularly where the commercial operation encompasses activity at a large number of sites or at two or more sites that are relatively distant from each other. Thus, a proprietor may not have the time or the inclination, or it may be prohibitively costly, to monitor the commercial operation firsthand. Often, an employee manager or managers are hired to oversee operations at one or more sites. However, the efficacy of the proprietor's monitoring of the operation is then subject to the honesty or competence of the managers, so such a solution is not optimal. Thus, a proprietor is frequently faced with a choice among limiting the expansion of the operation, spending large amounts of time monitoring the operation, or accepting the risks associated with hiring other people to monitor the operation.

Monitoring is even more difficult for a cash-basis commercial operation or for a commercial operation that is conducted primarily on a self-serve basis. Businesses having both of these characteristics, such as laundromats or arcades, are particularly difficult commercial operations to monitor. Frequently, such commercial operations have, at most, a single employee manager to oversee activity at each site. Further, maintenance and other periodic activities may be performed by a traveling employee who is not assigned to work regularly at any particular location. The potential for employee abuse (e.g., stealing cash from the machines, absenteeism) in such situations is great.

Some self-serve cash-basis commercial operations have incorporated the use of a debit card system. In a debit card system, the machines to be operated ("operating machines") are equipped with card readers and are activated using debit cards rather than money. A debit card machine accepts money and issues a debit card which is coded to indicate a cash allowance equal to the amount of money input into the debit card machine. To use a machine, a debit card is inserted into the card reader which checks to determine whether an adequate cash allowance is coded onto the debit card and, if so, deducts an appropriate amount from that cash allowance as payment for activating the machine. While this affords some monitoring over cash collections, the system can still be subverted and the system does not provide information about aspects of the operation other than cash collections.

Some machines for coin-operated laundromats have included a sensing device within the machine that senses and stores information regarding a machine's operation. The information is then read from the sensing device by a hand-held device using an infrared beam. The information is stored in the hand-held device which is then taken back to a monitoring site. The information is transferred from the hand-held device to a computer where the information is stored. The information can then be processed by the computer to provide information regarding operation of the machines at the laundromat. While this system does enable, to some degree, automatic acquisition of information regarding laundromat operation, it does not overcome the problems that necessitate having an employee perform the direct monitoring of the operation. Since employee monitoring is still required, this system does not overcome the problems associated with direct monitoring by an employee rather than the proprietor.

Currently, for coin-operated laundromats, there is no effective system for monitoring cash collections. One method that has been used is to compare the energy usage for the laundromat over a given period of time with an estimated expected energy usage based upon the cash collections for that period of time. Another method for monitoring cash collections is simply to compare the cash collections for an operating site to the cash collections for other comparable operating sites and/or to the historic cash collection data for the operating site. However, neither of these methods are sufficiently accurate, they do not provide information regarding individual machines, and they do not enable monitoring of aspects of the operation other than cash collection.

As mentioned above, another problem with monitoring a commercial operation is ensuring that all equipment associated with the operation is working. Performance of required repairs should also be monitored. Previously, there was no way to know that a machine at an operating site was not operating properly unless the proprietor or an employee visited the site (or was present on a daily basis at the site) and observed that the machine was not operating properly. Moreover, the person observing the inoperative machine often does not have the tools or parts to effect a repair. Consequently, a machine may remain inoperative for an extended period of time until a repair is made. Further, previously, repairs to machines have been tracked using a log book that is filled out manually each time that a repair is made. Such recording is tedious, requiring the manual entry of detailed information regarding the repair. Additionally, the manual recording may not be done consistently, causing the repair record to be incomplete. As a result, machines having chronic problems may not be identified. Moreover, the number of entries can easily become large and may not be organized in a way that allows easy analysis of the repair history of the machines.

It is desirable for a proprietor to be able to monitor a commercial operation (such as a coin-operated laundromat) directly, regardless of the number of sites at which the commercial operation is conducted or the geographical separation of multiple sites. It is also desirable for the site from which the commercial operation is monitored to be mobile, capable of being located at any distance from the sites at which the commercial operation is conducted, thereby enhancing the flexibility of the monitoring. Finally, it is desirable that such a system be capable of monitoring cash collections for the operation, providing information from which the operating condition of the machines associated with the operation can be deduced, and providing at least some information regarding the performance of employees hired to assist in conducting the operation.

SUMMARY OF THE INVENTION

According to the invention, an operation conducted at one or more operating sites can be monitored directly by a single person at a monitoring site. Certain predefined activities at one or more operating sites are automatically monitored. Information regarding these activities is communicated to the monitoring site. The information collected at the monitoring site is used to describe the status of the operation at a given time or the change in status of the operation over a period of time, and to verify information about the conduct of the operation supplied by third parties to the person monitoring the operation.

The operation can be conducted at any number of operating sites and the operating sites can be separated by any distance. The monitoring site can be, and frequently is, geographically remote from the operating sites. Further, the monitoring site can be mobile without affecting the monitoring capabilities of the invention.

The invention is useful in monitoring a variety of commercial operations such as, for example, a chain of restaurants or a multiplicity of car washes. Further, the invention is particularly useful in monitoring commercial operations that operate on a cash-basis or that are conducted primarily on a self-serve basis such as, for example, laundromats or arcades. However, the invention can be used to monitor any type of operation.

When used to monitor a cash-basis operation, a monitoring system according to the invention can be used to monitor the income that should have been received by the operation for particular periods of time. This information can be compared to the actual collections for those periods of time. Significant discrepancies may indicate a problem in the conduct of the operation (e.g., employee or customer stealing) that needs to be addressed. The monitoring system can also be used to monitor the performance of machines associated with the operation so that, for example, high maintenance machines can be identified. The monitoring system also provides information from which at least some aspects of employee performance can be monitored. For instance, the monitoring system provides information from which the proprietor can determine whether a repair person has attempted scheduled repairs and, as noted above, the cash collection information can be used to determine if an employee is stealing from the proprietor. An important aspect of the invention is that all of this information is made easily accessible so that the proprietor can quickly ascertain information regarding whatever particular aspect of the operation is of interest. Another important aspect of the invention is that the invention provides up-to-date information regarding the system operation, enabling the proprietor to immediately identify problems with the operation.

In one embodiment, the invention automatically monitors the operation of one or more laundromats, each of which include a multiplicity of machines. The invention monitors cash receipts at the laundromats and monitors the operation of one or more of the machines at each of the laundromats. The invention is particularly useful for monitoring a multiplicity of laundromats or for monitoring laundromats that are geographically remote from a monitoring site.

The cash receipts monitoring can include determining the amount of cash that should have been deposited in particular machines during a specified period of time. This can be accomplished by, for example, sensing each activation of the machines during the specified period of time. The cash receipts monitoring can also include maintaining information regarding the amount of cash collected from the machines during the specified period of time. The amount of cash collected can be compared to the amount of cash that should have been deposited so that any discrepancies can be identified.

The machine operation monitoring can include sensing openings or closings of a service door on particular machines. The machine operation monitoring can also include monitoring whether particular machines are out of order or not. The out-of-order machine monitoring can be accomplished by sensing and monitoring activations of the machines or by monitoring an out-of-order switch located on the machines. The machine operation monitoring can also include monitoring repairs made to machines. Such monitoring can include, for example, recording the date of each repair, recording the name of the person who performed the repair, and recording a description of the repair.

In another embodiment of the invention for automatically monitoring the operation of one or more laundromats that each include a multiplicity of machines, the invention senses activations of particular machines, openings and closings of a cash vault of particular machines, and openings and closings of a service door or doors of particular machines. As above, in this embodiment, the invention may also be capable of determining whether a machine is out of order or not. Additionally, in a further particular embodiment, the invention monitors a monitoring mechanism included with particular machines that has the capability of monitoring the operation of those machines to obtain information regarding predefined characteristics of those machines. Such predefined characteristics may include, for example, machine malfunctions, identity of repair personnel working on the machine, information regarding the manner in which the machine has been operated, and the price or prices being charged for operation of the machine.

In another embodiment, the invention automatically manages the operation of one or more laundromats by remotely monitoring a first set of predefined aspects of the operation of the laundromats and remotely controlling a second set of predefined aspects of the operation of the laundromats. The remote monitoring can include monitoring cash receipts from machines at the laundromats and monitoring the operation of the machines. The remote controlling can include establishing a price of operation of the machines (or different prices for different time periods during the day), testing the operation of the machines, placing machines out of service when the machines do not perform acceptably well during the testing, and controlling the contents of displays associated with the machines.

In yet another embodiment, the invention automatically acquires data regarding the expected cash receipts at each of one or more laundromats and data regarding the operation of one or more machines at each of the one or more laundromats. The invention includes an option that enables the data to be obtained automatically at each of a multiplicity of predetermined times.

In still another embodiment, the invention monitors, from a monitoring site, the conduct of a cash-basis operation that takes place at one or more operating sites, each of which include a multiplicity of machines. The invention determines, for each of one or more machines at the operating site, the amount of cash that should have been deposited in the machine during a specified period of time and monitors the operation of one or more machines at each operating site. The invention is particularly useful for monitoring a multiplicity of operating sites (especially where each operating site is geographically separated from any other operating site) or for monitoring operating sites that are geographically remote from the monitoring site.

In still another embodiment, the invention monitors the conduct of an operation that takes place at one or more operating sites, each of which include a multiplicity of devices to be monitored. The invention includes: i) a multiplicity of sensors; ii), a multiplicity of internal control units; iii) a multiplicity of site controller units; iv) a first multiplicity of communications devices for transferring data between each of the internal control units and a corresponding one of the site controller units; v) a main controller unit; and vi) a second multiplicity of communications devices for transferring data between each of the site controller units and the main controller unit. At least one sensor is mounted on each machine or device and is adapted to acquire data regarding the operation of the machine or device. At least one internal control unit is mounted on each machine or device and is adapted to receive data from the at least one sensor. At least one site controller unit is located at each laundromat or operating site. Like the immediately previous embodiment of the invention, this embodiment is particularly useful for monitoring a multiplicity of operating sites (especially where each operating site is geographically separated from any other operating site) or for monitoring operating sites that are geographically remote from the monitoring site. The invention is also particular useful in monitoring a commercial operation, especially where the operation is a cash-basis or self-service operation.

In this embodiment, the invention may further include a mechanism for monitoring communications between the main controller unit and the site controller unit and communications between the site controller unit and the internal control unit. This communication monitoring mechanism can include a mechanism for detecting communication conditions (communication conditions including successful communications, communication problems and communication errors) and a mechanism for recording communication conditions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B are a simplified representation of a system according to an embodiment of the invention.

FIG. 1C is a block diagram of a monitoring system according to the invention.

FIG. 2 is a block diagram of a main controller unit for use with a monitoring system according to the invention such as the monitoring system of FIG. 1C.

FIG. 3 is a block diagram of a site controller unit for use with a monitoring system according to the invention such as the monitoring system of FIG. 1C.

FIGS. 4A and 4B are block diagrams of internal control units for use with a monitoring system according to the invention such as the monitoring system of FIG. 1C.

FIG. 5 illustrates a Main window of an application program of a monitoring system according to the invention.

FIG. 6 illustrates a Site Status window of an application program of a monitoring system according to the invention.

FIG. 7 illustrates a Site Status Event Information window of an application program of a monitoring system according to the invention.

FIG. 8 illustrates a Site Status Event Options window of an application program of a monitoring system according to the invention.

FIG. 9 illustrates a Site Information window of an application program of a monitoring system according to the invention.

FIG. 10 illustrates a Attendants window of an application program of a monitoring system according to the invention.

FIG. 11 illustrates a Machine Information window of an application program of a monitoring system according to the invention.

FIG. 12 illustrates a Machine Types window of an application program of a monitoring system according to the invention.

FIG. 13A illustrates a Machine Activation Fee Discounts window of an application program of a monitoring System according to the invention.

FIG. 13B illustrates a Correct Machine Activation Fee Discounts window of an application program of a monitoring system according to the invention.

FIG. 14A illustrates a Site Special Operations window of an application program of a monitoring system according to the invention.

FIG. 14B illustrates a Download Site Configuration window of an application program of a monitoring system according to the invention.

FIG. 14C illustrates a Change Password window of an application program of a monitoring system according to the invention.

FIG. 14D illustrates a Get Version Number Of Site's Software window of an application program of a monitoring system according to the invention.

FIG. 14E illustrates a Get Version Report Of Site's ICUs window of an application program of a monitoring system according to the invention.

FIG. 14F illustrates a Download Updated Site Software window of an application program of a monitoring system according to the invention.

FIG. 15 illustrates a Data Collection Parameters window of an application program of a monitoring system according to the invention.

FIG. 16 illustrates a User List window of an application program of a monitoring system according to the invention.

FIG. 17 illustrates a Business Information window of an application program of a monitoring system according to the invention.

FIG. 18 illustrates a Manual Data Acquisition window of an application program of a monitoring system according to the invention.

FIG. 19 illustrates a Collection Entry window of an application program of a monitoring system according to the invention.

FIG. 20 illustrates a Reports window of an application program of a monitoring system according to the invention.

FIG. 21 illustrates a Save Report File As window of an application program of a monitoring system according to the invention.

FIG. 22 illustrates a Report Export Options window of an application program of a monitoring system according to the invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

According to the invention, the activities associated with an operation can be monitored directly by a single person at a monitoring site. The operation can be spread over a number of geographically separate operating sites. The monitoring site can be geographically remote from the operating sites and can even be mobile.

At each operating site, certain predefined activities are automatically monitored. Information regarding these activities is communicated to the monitoring site. This information can be used to describe the status of the operation at a given time or the change in status of the operation over a period of time. This information can also be used to verify that the operation is being properly conducted by third parties working at each operating site.

The invention can be used to monitor any type of operation. However, as will be apparent from the description below, the invention is particularly useful in monitoring a variety of commercial operations such as, for example, a chain of restaurants or a multiplicity of car washes. Further, the invention is especially useful in monitoring commercial operations that operate on a cash-basis or that are conducted primarily on a self-serve basis such as, for example, laundromats or arcades.

For example, a system according to one embodiment of the invention, shown in FIGS. 1A and 1B, is used to monitor operations at a multiplicity of laundromats, e.g., laundromats 151 and 152 (FIG. 1A). The laundromats can be located anywhere and, typically, are located at sites (operating sites) that are geographically remote from each other and from the site (monitoring site) at which an owner or manager (proprietor) monitors the operations. The system monitors machines, e.g., machines 156, 157 and 158 (FIG. 1B), that are located at each laundromat, such as washing machines, dryers, snack vending machines, soda vending machines, bag vending machines, detergent machines, extractors, money changers and bar code readers. The system can also control aspects of the operation such as automatic door locks, a heating, ventilation and cooling (HVAC) system and lights. Generally, any number of laundromats and any number of machines at each laundromat can be monitored. For example, in one embodiment, up to 200 laundromats can be monitored and, in another embodiment, up to 512 machines at each laundromat can be monitored. The system can be used to monitor many aspects of laundromat operation; however, of particular importance, the system enables the proprietor to monitor cash collections from the laundromats (i.e., identify the amount of cash that should have been collected and compare that amount to the amount that was reported as collected) and monitor performance of each machine in the laundromat (i.e., identify defects or malfunctions in the operation of a machine, as well as monitor the amount of time spent on repairing a machine).

In one embodiment of the invention, shown in FIG. 1A, a system includes a main computer 153 at the monitoring site that communicates with a site computer at each laundromat, e.g., site computers 154 and 155 at laundromats 151 and 152, respectively, via a telephone line. The proprietor uses the main computer 153 to acquire data from the site computers, e.g., site computers 154 and 155, and to issue commands to the site computers to control operations at each laundromat, e.g., laundromats 151 and 152. Each of the site computers, e.g. site computer 155 (FIG. 1B), in turn, communicates with a microcontroller (ICU) installed on each machine, e.g., ICUs 159, 160 and 161 on machines 156, 157 and 158, respectively, at the corresponding laundromat. The microcontrollers are configured to acquire information about the operation of the corresponding machine and to issue commands regarding operation of that machine. In the embodiment shown in FIG. 1B, the microcontrollers are configured to communicate with computers installed on each of the machines, e.g., computers 162, 163 and 164 on machines 156, 157 and 158, respectively. However, as will be clear from the discussion below, not all machines monitored by the invention include such computers.

FIG. 1C is a simplified block diagram of a monitoring system 100 according to the invention. The monitoring system 100 is used to monitor operations at a multiplicity of operating sites, e.g., operating sites 111, 112 and 113, from a monitoring site 101. In FIG. 1C, for simplicity, only three operating sites are shown; however the system 100 can be used to monitor any number of operating sites. Each of the operating sites can be, for instance, a coin-operated laundromat. A multiplicity of machines are located at each of the operating sites, e.g., machines 131a, 131b and 131c, machines 132a, 132b and 132c, and machines 133a, 133b and 133c at operating site 111.

In FIG. 1C, for simplicity, the machines at operating sites 112 and 113 are not shown, nor are all of the machines at operating site 111 shown. If each operating site is a laundromat, the machines can be, for instance, various types of washers and dryers, as well as snack machines, detergent machines and soda machines.

The monitoring system 100 includes a main controller unit (MCU) 102, a multiplicity of site controller units (SCUs), e.g., SCUs 121, 122 and 123, designated generally as SCU.sub.1 through SCU.sub.m, and a multiplicity of internal control units (ICUs), e.g., ICUs 141a, 141b, 141c, 142a, 143b, 142c, 143a, 142b and 143c, designated generally as ICU.sub.1 through ICU.sub.pn. The MCU 102 is located at the monitoring site 101. Each SCU is located at a corresponding one of the operating sites, e.g., SCU 121 is located at operating site 111. Each ICU is located at one of the operating sites and is associated with a corresponding one of the machines located at that operating site, e.g., ICU 141a is associated with machine 131a at site 111.

In the monitoring system 100, the MCU 102 is connected to each SCU, SCU.sub.1 through SCU.sub.m, by a communication line, e.g., MCU 102 is connected to SCUs 121, 122 and 123 by communication lines 103, 104 and 105, respectively. The communication lines 103, 104 and 105 can be, for example, conventional telephone lines (see, e.g., phone lines 165 in FIG. 1A). In another embodiment, communication between the MCU 102 and SCU.sub.1 through SCU.sub.m is implemented using a wireless cellular telephone. Use of telephone lines to connect the MCU 102 to SCU.sub.1 through SCU.sub.m enables the MCU 102 to be located at any desired monitoring site. Further, the MCU 102 can be moved easily from one monitoring site to another monitoring site. Additionally, the MCU 102 can be located at a mobile monitoring site such as an airplane or boat.

Each SCU, SCU.sub.1 through SCU.sub.m, is connected by one or more communication lines to the ICUs at that operating site. In one embodiment of the invention, one or more sets ("strings") of ICUs are connected serially to each SCU (see, e.g., communication lines 166, 167 and 168 connecting ICUs 159, 160 and 161, respectively, in FIG. 1B). In monitoring system 100, SCU.sub.1 (SCU 121), located at operating site 111, is connected serially to each of p strings of ICUs. Each string includes n ICUs. Generally, according to the invention, each string can include any number of ICUs and any number of strings of ICUs can be connected to an SCU. In one embodiment of the invention, up to 16 strings can be connected to each SCU 121 and each string can include up to 32 ICUs. In another embodiment, each string can include up to 128 ICUs.

In the monitoring system 100, the SCU 121 is connected to the ICUs 141a, 142a and 143a, i.e., the first ICU in particular strings of ICUs, by communication lines 124, 125 and 126, respectively. Each ICU that is first in a string of ICUs is then connected to the next ICU in the string by a communication line, e.g., ICUs 141a, 142a and 143a are connected to ICUs 141b, 142b and 143b, respectively, by communication lines 134a, 135a, 135a, respectively. These ICUs are, in turn, connected to the next ICU in the string by another communication line, e.g., ICUs 141b, 142b and 143b by communication lines 134b, 135b, 135b, respectively, to subsequent ICUs (not shown). All ICUs in the string are connected in a series in this manner until the last ICU in each string, e.g., ICUs 141c, 142c, 143c, is connected to the previous ICU by a communication line, e.g., communication lines 134c, 135c, 136c, respectively. Each of the communication lines 124, 125, 126, 134a, 134b, 134c, 135a, 135b, 135c, 136a, 136b, 136c can be, for example, conventional six conductor electrical cables.

Connecting the ICUs serially to the SCU, as described above, is particularly advantageous when a monitoring system according to the invention is used to monitor the operation of one or more laundromats. This is because the machines in a laundromat are typically arranged in rows, either along a wall or in aisles on a floor. It is easier to assemble a monitoring system according to the invention by connecting one communication line between the SCU and the ICU on the first machine in a row and an additional communication line between each pair of ICUs of adjacent machines, then it is to connect a communication line directly from the SCU to the ICU on each machine. However, if one of the communication lines in a string of ICUs malfunctions or is disconnected, communication is lost between the SCU and each ICU in the chain after the defective communication line.

Each ICU monitors information regarding operation of the machine associated with the ICU. The operational information can be monitored automatically by the system or only upon the request of a user of the system (as explained in more detail below). Some machines ("smart machines") include a microprocessor which monitors information regarding the operation of the machine. For those machines, the ICU communicates with the machine's microprocessor to obtain information regarding operation of the machine. Other machines (electromechanical or "dumb machines"), do not include a microprocessor: for those machines, the ICU monitors sensors installed on the machine to obtain information regarding operation of the machine. All information obtained regarding machine operation is identified with the time and date at which the described event occurred.

For dumb machines, information can only be deduced by activation of one or more of the sensors. In one embodiment, when a monitoring system according to the invention is used to monitor operation of one or more laundromats, the sensors on dumb machines sense: 1) opening and closing of the cash vault of a machine, 2) opening and closing of the service door or doors of a machine, and 3) activation of a machine. From this sensed information, the monitoring system can determine the amount of cash that should be in the machine based upon the number of activations of the machine after the cash vault was last closed (i.e., after the cash was last removed). The monitoring system also provides information that is useful in monitoring cash collections from the machine (e.g., when and for how long the cash vault is accessed) and service activity (e.g., when and for how long the service door is open) on the machine. Additionally, the monitoring system also monitors a switch that indicates whether the machine is out of order. This switch is activated manually at the operating site. The existence of an out-of-order machine can also be deduced by observing that monitored activations decrease to zero for a period of time.

For smart machines, the information that can be obtained regarding the operation of the machine is limited only by the capabilities of the machine's microprocessor. For example, in addition to all of the above information that can be obtained from the dumb machines, the smart machines may also be able to report: i) whether the machine has malfunctioned and, if so, which part; ii) identifying information regarding the mechanic or mechanics who have worked on a malfunctioning machine (this information is initially input to the smart machine by the mechanic or mechanic) iii) information regarding the manner in which the machine has been operated (e.g., for washing machines, the type of wash cycle and the temperature of the water); and iv) the prices being charged for operation of the machine (which may be dependent on the time of day and on the manner in which the machine is operated).

Monitoring information as described above is useful for a number of reasons. The monitoring of cash collections and the capacity to organize the cash collections in a variety of ways (e.g., by particular machine, by machine type or other groups of machines, by operating site, by calendar period), described in more detail below, eases accounting for income received from conduct of the operation. Monitoring of cash collections can also be useful in identifying characteristics of the operation (e.g., the location of heavily used machines within a laundromat can be identified). The monitoring of service information results in a repair record being automatically kept for each machine, thereby enabling chronically poor performing machines to be identified easily. Additionally, monitoring of service information provides the proprietor with information that can indicate whether or not a repair person has attempted scheduled repairs. Further, information regarding out-of-order machines can be used to more productively schedule repair activities (e.g., if the monitoring system indicates that no machines are out of order at an operating site, the repair person need not visit that operating site).

The monitoring capabilities of the monitoring system according to the invention provide a number of important advantages over previous monitoring methods. All of the information regarding conduct of the operation is made easily accessible so that the proprietor can quickly ascertain information regarding whatever particular aspect of the operation is of interest. The invention also provides completely up-to-date information regarding the system operation, enabling the proprietor to immediately identify problems with the operation. Additionally, any type of machine, made by any manufacturer of any model, can be monitored by the monitoring system of the invention. Moreover, all of the monitoring information can be obtained remotely at the monitoring site, without need for someone actually visit the operating sites.

For smart machines, the ICU can also communicate instructions to the machine regarding operation of the machine. The instructions that can be communicated are limited only by the capabilities of the machine's microprocessor. For example, the price of operating the machine may be specified or modified. Moreover, according to the invention, different prices may be specified for different times of day, enabling promotions such as "happy hours" to be implemented remotely. The ICU may also be used to perform diagnostic tests on the machine or components of the machine. The ICU may be used to place a machine out of service or put the machine back into service. If the machine has an associated display, the contents of the display can be controlled. If equipped with a printing mechanism, the machine can be controlled to print and dispense coupons or custom messages. Like monitoring of operational information, the instructions to the smart machines can be sent automatically by the system or only upon the request of a user of the system (as explained in more detail below).

The capacity to send instructions to smart machines also provides a number of advantages. Instructions regarding machine operation can be implemented easily and instantaneously. The instructions can be implemented from the monitoring site so that it is not necessary for someone to physically go to the operating site. Moreover, instructions can be implemented simultaneously for many or all of the machines at an operating site; instructions need not be entered in each machine separately. Additionally, instructions can be sent to any type of machine, made by any manufacturer of any model.

In order for a system according to the invention to be able to communicate with a smart machine's microprocessor, the smart machine must include a communications device that implements the same communications protocol that is implemented by the ICU mounted on the smart machine. This protocol is explained in more detail below. Without implementation of this communication protocol, a smart machine can only be treated as a dumb machine by the monitoring system.

FIG. 2 is a simplified block diagram of an MCU 200 for use with a monitoring system according to the invention, e.g., monitoring system 100 (FIG. 1C). The MCU 200 includes a memory 201, a modem 202, a display 203, a microprocessor 204 and a user interface device 205. The components of the MCU 200 can be embodied in, for example, a computer such as a desktop or notebook computer. Embodiment of the MCU in a notebook computer is particularly advantageous for enabling the MCU to be moved to various locations thereby making the monitoring site mobile.

The microprocessor 204 controls operation of the MCU 200. The microprocessor 204 can be, for example, a 386DX microprocessor running at 33 megahertz. Other later processors in the x86 series can also be used. Generally, any suitable microprocessor can be used that is compatible with an operating system and application program used to implement the invention.

The memory 201 can include, for example, a random access memory (RAM), a read only memory (ROM), and a floppy or hard disk storage device. The memory 201 is used for storing software used to control the operation of the MCU 200, such as software for controlling operation of the microprocessor 204, modem 202, display 203 and user interface device 205, and application software (described in more detail below) used to implement various characteristics of the monitoring system. The memory 204 also stores the data (described in more detail below) collected from the ICUs after that data is downloaded from the SCUs. Generally, the memory 204 must include sufficient RAM and permanent storage capacity to accommodate the above-described software. Illustratively, a RAM having 4-8 megabytes of storage capacity and a hard disk having 340-540 megabytes of storage capacity are adequate for executing and storing programs for use in controlling operation of the system according to the invention.

The display 203 can be, for example, a computer monitor and/or a printer. The display 203 is used to display data obtained by the monitoring system according to the invention or to display choices for effecting control of the monitoring system, as described in more detail below.

The user interface device 205 can be, for example, a conventional computer keyboard, conventional mouse, conventional trackball, or some combination of those. The user interface device 205 enables a user to input and display data describing the status of the operation being monitored and to effect control of the monitoring system.

The MCU 200 communicates with each SCU through a communication line (e.g., communication line 103, 104 or 105 in FIG. 1C) that is connected to the modem 202 of the MCU 200. Communication from the MCU to the SCU includes, for example, instructions regarding data collection from, and operation of, particular machines (as explained in more detail below) at the operating site. Communication from the SCU to the MCU includes, for example, data from each machine regarding operation of the machine (as explained in more detail below). As described above, the communication line between the SCU and MCU is, in one embodiment, a conventional telephone line. In such an embodiment, the modem 202 is a conventional modem for use in sending and receiving data over telephone lines. The modem 202 is, in one embodiment, a 2400 baud external modem. However, modems having other data transmission rates greater than 2400 baud can also be used. Communication between the MCU and SCU is governed by a standard ZMODEM protocol.

FIG. 3 is a simplified block diagram of an SCU 300 for use with a monitoring system according to the invention, e.g., monitoring system 100 (FIG. 1C). As described above, an SCU such as SCU 300 is located at each operating site of the operation being monitored. The SCU 300 includes a real time clock 301, a microprocessor 302, a communications device 303, a modem 304, an input/output (I/O) device 305, a video interface device 306 and a memory 307, all of which are encased in a housing.

The communication line between the SCU 300 and the MCU is connected to the modem 304 of the SCU 300. Before allowing communication with the MCU, the SCU 300 must receive an appropriate password (i.e., a password that matches one of the passwords stored in the memory 307) from the MCU. In the embodiment in which the communication line is a conventional telephone line, the modem 304 is a conventional modem for use in sending and receiving data over telephone lines. The modem 304 is, in one embodiment, a 2400 baud modem. However, modems having other data transmission rates greater than 2400 baud can also be used.

Information (e.g., data and instructions as described above) is transferred between the modem 304 and the microprocessor 302. The microprocessor 302 controls the flow of information through the SCU 300 and performs any calculations and processing operations necessary for operation of the SCU 300. The microprocessor 302 can be, for example, a 286 processor or any later processor in the x86 series. However, any suitable microprocessor can be used.

The real time clock 301 is conventional and communicates with the microprocessor 302. The real time clock 301 keeps track of the time of day and date at the operational site at which the SCU 300 is located. Each time that the MCU begins a communication with the SCU 300 (i.e., after each occasion when a proper password is received by the MCU), the MCU checks the real time clock 301 to ascertain the time and date at the operating site and synchronizes the time and date at the monitoring site (i.e., the location of the MCU) to that at the operating site. This is particularly desirable when the monitoring site and the operating site are in different time zones, since much of the information transferred back and forth between the MCU and SCU is associated with a particular date and time.

The microprocessor 302 also communicates with the memory 307. The memory 307 includes a hard disk storage device, a read-only memory (ROM) and a random access memory (RAM). The memory 307 is used for storing software used to control the operation of the SCU 300, such as operating system software for controlling operation of the microprocessor 302, communications software (described in more detail below) for controlling operation of the communications device 303, communications software for controlling operation of the I/O device 305, and communications software for controlling operation of the video interface device 306. The memory 307 also stores software which controls the acquisition of data from the ICUs regarding operation of the machine and sending of commands to the ICUs to control operation of the machine. Additionally, the memory 307 stores information regarding the configuration of machines at the site and the operating status (e.g., out of order) of machines, as well as data collected from the ICUs regarding operation of the machines at the operating site.

The microprocessor 302 also communicates with the communications device 303. The communications device 303 enables communication between the SCU 300 and each of the ICUs at the operational site at which the SCU 300 is located. Communications from the SCU to each ICU includes, for example, instructions regarding data collection from the machine associated with the ICU, operation of the machine and sensor or machine microprocessor testing (as appropriate). Communication from each ICU to the SCU includes, for example, data regarding operation of the machine or the status of the sensors or machine microprocessor. As shown in FIGS. 1C and 3 (and explained in more detail above with respect to FIG. 1C), the SCU 300 is connected to p strings of ICUs, each of which are interconnected in a daisy-chain fashion. Generally, the communications device 303 is conventional; however, the communications device 303 must be capable of multi-drawing (i.e., communicating with multiple devices in a chain).

In one embodiment, the communications device 303 is a standard RS-485 communications board commercially available from, for instance, Quatech in Akron, Ohio. The following parameters may be set for communication over the RS-485: Baud Rate is set to 4800 bps, Parity is set to "None", Data Bits is set to 8, and Stop Bits is set to 1.

As mentioned above, the memory 307 is used for, among other things, storing a communications protocol (SCU-ICU protocol) for governing communication between the SCU 300 and the ICUs. (A similar protocol is stored in a memory in a microcontroller of each ICU; see microcontroller 402 in ICUs 400 and 450 of FIGS. 4A, and 4B, respectively, below.) In one embodiment of the invention, the SCU-ICU protocol is a packet protocol, i.e., information is passed between the SCU 300 and the ICUs in packets that can vary in size. Thus, only as much information as is necessary is passed during each communication between the SCU and an ICU, increasing the efficiency and speed of the communication. Each packet of information includes information that indicates the size of the packet. Further, since the ICUs are connected serially in a daisy-chain fashion, each packet of information includes an address indicating the destination of the information (i.e., SCU or particular ICU) to ensure that the information is received by the proper device. Details of a particular embodiment of the SCU-ICU protocol for enabling communication between the SCU and ICU are given immediately below.

All communications between an SCU and the corresponding ICU's are initiated by the SCU. All commands sent from the SCU ("SCU commands") are two bytes in length. The first byte specifies the address of the ICU to which the command is directed. (Note that the SCU may send a command to all ICUs on a string by using the Command Broadcast option described below.) The second byte contains the actual information to be transmitted to the ICU.

The bits of the first byte of an SCU command have the format given below in TABLE 1:

                  TABLE 1
    ______________________________________
    SCU-ICU Protocol, Byte #1 of SCU Command
    7      6            5     4-0
    ______________________________________
    0      0            CB    Device Address
    ______________________________________

                  TABLE 2
    ______________________________________
    SCU-ICU Protocol, Byte #2 of SCU Command
    7            6     5-0
    ______________________________________
    0            1     Command Code
    ______________________________________

                  TABLE 3
    ______________________________________
    SCU-ICU Protocol, SCU Command Codes
    Code (H)         Description
    ______________________________________
    00               Send Data
    01               Clear Counters
    02               Go Active
    03               Go Inactive
    04               Perform Self Test
    05               Reset
    06               Repeat Last Data
    07               Send Firmware Version
    08               Not Defined
    09               Not Defined
    OA-3F            Not Defined
    ______________________________________

                  TABLE 4
    ______________________________________
    SCU-ICU Protocol, Byte #1 of ICU Command
    7            6-5     4-0
    ______________________________________
    1            STAT    Device Address
    ______________________________________

                  TABLE 5
    ______________________________________
    SCU-ICU Protocol, ICU Status Bits
    STAT               Description
    ______________________________________
    00                 No New Data
    01                 Data Available
    10                 ICU Fault
    11                 Power Up
    ______________________________________

                  TABLE 6
    ______________________________________
    SCU-ICU Protocol, Bytes # 2, 3, 4 of ICU Command
    7    6       5         4-3     2       1-0
    ______________________________________
    1    DAT     Sen0/2/4  Sen0/2/4
                                   Sen1/3/5
                                           Sen1/3/5
                 Level     Count   Level   Count
    ______________________________________

                  TABLE 7
    ______________________________________
    SCU-ICU Protocol, Sensor Assignments
    Sensor #         Descriptions
    ______________________________________
    0                Front Service Door
    1                Cash Vault Door
    2                Machine Activator
                     (e.g., Coin Mechanism)
    3                Top Service Door
    4                Unassigned
    5                Unassigned
    ______________________________________

                  TABLE 8
    ______________________________________
    SCU-ICU Protocol, Byte #5 of ICU Command
    7      6              4-1      0
    ______________________________________
    1      DAT            Not Used OOO
    ______________________________________

                  TABLE 9
    ______________________________________
    SCU-ICU Protocol, Error Byte of ICU Command
    7            6      5-0
    ______________________________________
    1            DAT    Faulty Sensor Bits
    ______________________________________

                  TABLE 10
    ______________________________________
    SCU-ICU Protocol, ICU Firmware Version Command
    7            6     5-0
    ______________________________________
    1            0     Firmware Version
    ______________________________________

                  TABLE 11
    ______________________________________
    ICU-Machine Protocol, Interface Pinout
    Pin #   Pin Name       Description
    ______________________________________
    1       TXD            ICU Transmit Data Line
    2       RXD            ICU Receive Data Line
    3       GPI            ICU General Purpose
                           Input Line
    4       GPO            ICU General Purpose
                           Output Line
    5       GND            Common Ground
    6       NC             Not Connected
    ______________________________________

                  TABLE 12
    ______________________________________
    ICU-Machine Protocol, Information Byte Format
    7              6         5-0
    ______________________________________
    SM/ICU*        DAT/CMD*  DATA
    ______________________________________

                  TABLE 13
    ______________________________________
    ICU-Machine Protocol Commands
    Command  Description     Code     Origin
    ______________________________________
    SMFGID   Send Manufacturer ID
                             00H      ICU
             Code
    SMMODEL  Send Machine Model #
                             01H      ICU
    SSMVER   Send SM Firmware
                             02H      ICU
             Version
    SICUVER  Send ICU Firmware
                             03H      SM
             Version
    ACTPREQ  Activate Permission
                             04H      SM
             Request
    GOFF     Go inactive (pause
                             05H      ICU
             cycle)
    GON      Go active (continue
                             06H      ICU
             cycle)
    SRES     Perform a Soft Reset
                             07H      ICU
    HRES     Perform a Hard Reset
                             08H      ICU
    HELLO    Alive check     09H      ICU
    RCVPR    Receive Price Update
                             0AH      ICU
    SNDPR    Send Prices     0BH      ICU
    NEVENT   New Event       0CH      SM
    SNDLEV   Send SM Sensors level
                             0DH      ICU
             Info
    SNDSEN   Send ICU Sensors Info
                             0EH      SM
    SSMFLT   Send SM Fault   0FH      ICU
             Registers
    SICUFLT  Send ICU Fault  10H      SM
             Register
    PSELFT   Perform Self Test
                             11H
    DSCNT    Activate Price  12H      ICU
             Discount
    DSCLEV   Report discount level
                             13H      ICU
    SNDSTAT  Send Machine Status
                             14H      ICU
    MFGCMD   Following is a  15H      ICU
             manufacturer specific
             command structure
             Not Defined     16H-3DH
    KILL     Abort Current Command
                             3EH      ICU
    NSP      Command not supported
                             3FH      SM
    ______________________________________

                  TABLE 14
    ______________________________________
    ICU-Machine Protocol, Manufacturer Data Byte
    7            6     5-0
    ______________________________________
    1            1     Manufacturer Code
    ______________________________________

                  TABLE 15
    ______________________________________
    ICU-Machine Protocol, Manufacturer Data Bits
    Code (H)            Manufacturer
    ______________________________________
    00                  Wascomat
    01                  GE
    02                  Maytag
    03                  Whirlpool
    04                  Dexter
    05                  Unimac
    06                  Speed Queen
    07                  Huebtch
    08                  Ipso
    09                  Milnor
    0A                  Primus
    0B                  American
    0C-3E               Undefined
    3F                  Wrong Mfg.
    ______________________________________

                  TABLE 16
    ______________________________________
    ICU-Machine Protocol, Model Data Byte
    7            6     5-0
    ______________________________________
    1            0     Manufacturer Model
    ______________________________________

                  TABLE 17
    ______________________________________
    ICU-Machine Protocol, Byte #1 of Machine Firmware Data
    7            6     5-0
    ______________________________________
    1            1     Version # Prefix
    ______________________________________


              TABLE 18
    ______________________________________
    ICU-Machine Protocol, Byte #2 of Machine Firmware Data
    7            6     5-0
    ______________________________________
    1            1     Version # Suffix
    ______________________________________

                  TABLE 19
    ______________________________________
    ICU-Machine Protocol, Byte #1 of ICU Firmware Data
    7            6     5-0
    ______________________________________
    0            1     Version # Prefix
    ______________________________________


              TABLE 20
    ______________________________________
    ICU-Machine Protocol, Byte #2 of ICU Firmware Data
    7            6     5-0
    ______________________________________
    0            1     Version # Suffix
    ______________________________________

                  TABLE 21
    ______________________________________
    ICU-Machine Protocol, Activation Permission Data Byte
    7      6             5-1      0
    ______________________________________
    0      1             Not Used PER*
    ______________________________________

                  TABLE 22
    ______________________________________
    ICU-Machine Protocol, Transmit Prices Data Bytes
    Command Byte #
                 7     6        5-0    Price
    ______________________________________
    1            0     0        001010 Command
    2            0     1        0000BB 1
    3            0     1        AAAAAA 1
    4            0     1        0000BB 2
    5            0     1        AAAAAA 2
    *            *     *        *      *
    2*n          0     1        0000BB n
    2*n + 1      0     1        AAAAAA n
    ______________________________________

                  TABLE 23
    ______________________________________
    ICU-Machine Protocol, Byte #1 of New Event Report Data
    7    6      5-4      3       2      1     0
    ______________________________________
    1    1      Not Used Service #2
                                 Not Used
                                        Vault Service #1
    ______________________________________


              TABLE 24
    ______________________________________
    ICU-Machine Protocol, Byte #2 of New Event Report Data
    7       6           5        4-0
    ______________________________________
    1       1           Activation
                                 Cycle Type
    ______________________________________

                  TABLE 25
    ______________________________________
    ICU-Machine Protocol, Byte #1 of Sensor Data
    7   6       5        4-3      2      1-0
    ______________________________________
    0   1       Sensor #1
                         Sensor #1
                                  Sensor #2
                                         Sensor #2
                Level    Count    Level  Count
    ______________________________________


              TABLE 26
    ______________________________________
    ICU-Machine Protocol, Byte #2 of Sensor Data
    7   6       5        4-3      2      1-0
    ______________________________________
    0   1       Sensor #3
                         Sensor #3
                                  Sensor #4
                                         Sensor #4
                Level    Count    Level  Count
    ______________________________________


              TABLE 27
    ______________________________________
    ICU-Machine Protocol, Byte #3 of Sensor Data
    7   6       5        4-3      2      1-0
    ______________________________________
    0   1       Sensor #5
                         Sensor #5
                                  Sensor #6
                                         Sensor #6
                Level    Count    Level  Count
    ______________________________________

                  TABLE 28
    ______________________________________
    ICU-Machine Protocol, Byte #1 of Fault Registers Data
    7   6       5      4      3    2      1    0
    ______________________________________
    1   1       SEN6   SEN5   SEN4 SEN3   SEN2 SEN1
    ______________________________________


              TABLE 29
    ______________________________________
    ICU-Machine Protocol, Byte #2 of Fault Registers Data
    7    6      5       4      3     2     1     0
    ______________________________________
    1    1      SEN12   SEN11  SEN10 SEN9  SEN8  SEN7
    ______________________________________

                  TABLE 30
    ______________________________________
    ICU-Machine Protocol, Machine Sensor Definition
    Sensor #           Description
    ______________________________________
    SEN1               Water Pump
    SEN2               Water Valve
    SEN3               Heating Element
    SEN4               TBD
    SEN5               TBD
    SEN6               TBD
    SEN7               TBD
    SEN8               TBD
    SEN9               TBD
    SEN10              TBD
    SEN11              TBD
    SEN12              TBD
    ______________________________________

                  TABLE 31
    ______________________________________
    ICU-Machine Protocol, Faulty Sensor Data
    7   6       5      4      3    2      1    0
    ______________________________________
    0   1       SEN6   SEN5   SEN4 SEN3   SEN2 SEN1
    ______________________________________

                  TABLE 32
    ______________________________________
    ICU-Machine Protocol, Byte #2 of Machine Self Test Data
    7       6           5-3      2-0
    ______________________________________
    1       1           Not Used Result Code
    ______________________________________


              TABLE 33
    ______________________________________
    ICU-Machine Protocol, Machine Test Result Codes
    Result Code   Description
    ______________________________________
    000           Pass
    001           TBD
    010           TBD
    011           TBD
    100           TBD
    101           TBD
    110           TBD
    111           Fail
    ______________________________________

                  TABLE 34
    ______________________________________
    ICU-Machine Protocol, Price Discount Data Byte
    7      6           5-2      1-0
    ______________________________________
    0      1           Not Used Discount Code
    ______________________________________

                  TABLE 35
    ______________________________________
    ICU-Machine Protocol, Discount Codes
    Discount Code     Description
    ______________________________________
    00                Regular Price Discount
    01                Price Discount 1
    10                Price Discount 2
    11                Price Discount 3
    ______________________________________

                  TABLE 36
    ______________________________________
    ICU-Machine Protocol, Machine Status Byte
    7       6           5        4-0
    ______________________________________
    1       1           Operating
                                 Cycle Type
    ______________________________________

                  TABLE 37
    ______________________________________
    ICU-Machine Protocol, Manufacturer Identification Byte
    7            6     5-0
    ______________________________________
    0            1     Manufacturer Code
    ______________________________________