Method and system for scheduling the maintenance of remotely monitored devices

• US 20030101262A1
• Filed: 11/26/2002
• Published: 05/29/2003
• Est. Priority Date: 11/27/2001
• Status: Abandoned Application

• Current Assignee: Crane Merchandising Systems Incorporated (Crane Company)
• Original Assignee: Isochron Data Corporation (Isochron Data Corp /Harris/)
• Inventors: Godwin, Bryan W.
• Application Number:
  US10/304,603
• Publication Number:
  US 20030101262A1
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G07F 9/002 Vending machines being part of a centrally controlled network of vending machines
• CPC Class Codes: G07F 9/026 for alarm, monitoring and auditing in vending machines or means for indication, e.g. when empty

Abstract

A system and method for transitioning remotely monitored devices, including point of sale devices such as vending machines, between maintenance states is disclosed. The system and method provide that operational data for a remotely monitored device may be reviewed such that a determination may be made as to the device'"'"'s ability to continue operating on an as-needed maintenance schedule. Any errors or discrepancies detected in the operational data may result in the remote device being placed on a defined maintenance schedule. Should the operational data indicate that the remote device is performing within desirable parameters, the remote device may remain on or be transitioned back to as-needed maintenance scheduling. The system and method generally ensure that remote devices in a distributed asset system are properly maintained in an efficient, cost effective manner.

Claims

1. A method for transitioning a maintenance schedule for a remotely monitored device between as-needed maintenance scheduling and defined maintenance scheduling comprising:

maintaining historical operational data for the remotely monitored device;

verifying receipt of valid operational data for the remotely monitored device;

verifying current operational data is consistent with a predefined period of historical operational data;

examining the current operational data and the historical operational data to detect an occurrence of at least one triggering event;

determining whether the triggering event indicates a failure in verification;

transitioning from as-needed maintenance scheduling to defined maintenance scheduling in response to the triggering event indicating failure in verification; and

transitioning from defined maintenance scheduling to as-needed maintenance scheduling in response to failing to detect at least one triggering event after as-needed maintenance has been performed.

2. The method of claim 1 further comprising:

requesting operational data from the remotely monitored device; and

transitioning from as-needed maintenance scheduling to defined maintenance scheduling in response to a failure in fulfillment of the operational data request.

3. The method of claim 1 further comprising the triggering event including a vending machine refill event.

4. The method of claim 1 wherein the operational data further comprises DEX data.

5. The method of claim 1 further comprising scheduling the remotely monitored device for maintenance according to a defined maintenance schedule in response to failed communications between the remotely monitored device and a network operations center.

6. The method of claim 1 further comprising the remotely monitored device comprising point of sale hardware.

7. The method of claim 1 further comprising transitioning the remotely monitored device to defined maintenance scheduling in response to receipt of invalid operational data.

8. The method of claim 1 further comprising transitioning the remotely monitored device from defined maintenance scheduling to as-needed maintenance scheduling in response to receipt of valid operational data, consistent operational data and at least two refill events from the remotely monitored device.

9. A system for scheduling maintenance of remote devices comprising:

a wide area network;

at least one remote device operably coupled to the wide area network;

a network operations center operably coupled to the wide area network and operable to monitor the at least one remote device via the wide area network;

the at least one remote device operable to communicate operational data to the network operations center;

the network operations center operable to place the remote device on a defined maintenance schedule in response to a determination that current and historical operational data for the remote device are not consistent and that the current operational data for the remote device may be invalid; and

the network operations center operable to place the remote device on an as-needed maintenance schedule in response to a determination that the current and historical operational data for the remote device is consistent and that the current operational data for the remote device is valid.

10. The system of claim 9 further comprising:

the network operations center operable to evaluate the current operational data and the historical operational data to determine whether at least one triggering event has occurred; and

the network operations center operable to schedule the remote device for a maintenance visit in response to an absence of at least one triggering event.

11. The system of claim 10 further comprising:

the network operations center operable to place the remote device on a defined maintenance schedule in response to inconsistent current and historical operational data, invalid current operational data and the absence of at least one triggering event; and

the network operations center operable to place the remote device on an as-needed maintenance schedule in response to consistent current and historical operational data, valid current operational data and the occurrence of at least one triggering event.

12. The system of claim 9 further comprising the network operations center operable to place the remote device on a defined maintenance schedule in response to a failure by the network operations center to establish communications with the remote device.

13. The system of claim 12 further comprising the network operations center operable to schedule the remote device for a maintenance visit in response to a determination that at least one triggering event has not occurred.

14. The system of claim 9 further comprising the remote device including vending hardware.

15. A method for ensuring the maintenance scheduling of remotely located point of sale devices comprising:

identifying a current maintenance schedule for a remotely located point of sale device;

examining a data file including information indicative of a current operating status of the remotely located point of sale device to verify validity of the data file, consistency of the current operating status with a history of the remotely located point of sale device'"'"'s operating characteristics and to identify at least one triggering event;

transitioning, if the current maintenance schedule for the remotely located point of sale device is an as-needed maintenance schedule, the remotely located point of sale device from the as-needed maintenance schedule to a defined maintenance schedule in response to a failure in verification of the data file;

transitioning, if the current maintenance schedule for the remotely located point of sale device is an as-needed maintenance schedule, the remotely located point of sale device from the as-needed maintenance schedule to a defined maintenance schedule in response to a failure in identification of at least one triggering event in the data file; and

transitioning, if the current maintenance schedule for the remotely located point of sale device is a defined maintenance schedule, to an as-needed maintenance schedule in response to verification of data file validity and consistency and identification of at least one triggering event.

16. The method of claim 15 further comprising maintaining the remotely located point of sale device on the as-needed maintenance schedule in response to verification of data file validity, data file consistency and identification of at least one triggering event.

17. The method of claim 15 further comprising examining the data file to determine whether the remotely located point of sale device requires maintenance.

18. The method of claim 15 further comprising transitioning, if the current maintenance schedule for the remotely located point of sale device is an as-needed maintenance schedule, the remotely located point of sale device to a defined maintenance schedule in response to an inability to communicate between a network operations center and the remotely located point of sale device.

19. The method of claim 15 further comprising examining the data file including information indicative of a current operating status of the remotely located point of sale device to verify that a valid data file has been received for a predefined period of time, that consistency between the current operating status and the remotely located point of sale device'"'"'s history exists for a predefined period of time and to identify an occurrence of at least one refill event.

20. The method of claim 15 further comprising the remotely located point of sale device including a vending machine.