System and method for monitoring management

• US 20050225441A1
• Filed: 04/06/2004
• Published: 10/13/2005
• Est. Priority Date: 04/06/2004
• Status: Active Grant

• Current Assignee: Sitewatch Technologies, LLC
• Original Assignee: Sitewatch Technologies, LLC
• Inventors: Kernan, Timothy S.
• Granted Patent: US 7,457,869 B2
• Time in Patent Office: Days
• US Class Current: 340/506
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Abstract

A system and a method for automating the management, reporting and tracking of compliance of monitored systems provides for collecting data specific to the compliance requirements of a monitored system, monitoring the periodic status of compliance, managing manually provided compliance requirements and reporting on compliance status whereby a multi-facility, multi-system compliance manager can manage compliance and a single facility, single system user can manage site or system-specific compliance. A monitoring management system comprises a plurality of devices, a gateway server and a host. Each device provides monitoring data associated with monitoring of a corresponding resource, the monitoring data for each particular device represented in a data format specific to that device. The gateway server includes a plurality of device ports, each device port connected to a corresponding device for receiving the monitoring data, a processor that processes the received data into a common format from the device-specific formats, and a communication port for communicating the processed data. The host is connected to the gateway server communication port over a communications network and has a receiver for receiving the communicated data, a parser for parsing the received data, and an auditor for auditing the parsed data.

Claims

1. A monitoring management system comprising:

a plurality of devices, each device providing monitoring data associated with monitoring of a corresponding resource, the monitoring data for each particular device represented in a data format specific to that device;

a gateway server having a plurality of device ports, each device port connected to a corresponding device for receiving the monitoring data, a processor for processing the received data into a common format from the device-specific formats, and a communication port for communicating the processed data;

a host connected to the gateway server communication port having a receiver for receiving the communicated data, a parser for parsing the received data, and an auditor for auditing the parsed data.

2. The monitoring management system of claim 1 wherein the common format defines a data record structure that includes a device identifier field for identifying the specific device and a native data field for carrying the monitoring data.

3. The monitoring management system of claim 2 wherein the monitoring data carried in the native data field is in the device-specific format.

4. The monitoring management system of claim 2 wherein the monitoring data carried in the native data field is modified from the device-specific format.

5. The monitoring management system of claim 2 wherein the processed monitoring data in the common format comprises plural data records that is communicated to the host as data file.

6. The monitoring management system of claim 2 wherein the parser parses the received data based on the device identifier field and native data identifiers contained within the native data field and stores the parsed data in device-specific databases.

7. The monitoring management system of claim 1 wherein the host further includes one or more exception tables that define rules for testing for out of limit conditions associated with monitored resources and wherein the auditor provides auditing by evaluating the parsed data based on one or more rules defined by one or more entries of the exception tables to provide one or more exception reports based on an outcome of the audit.

8. The monitoring management system of claim 7 wherein the one or more exception reports are any of a type that includes daily, periodic and manual compliance reports.

9. The monitoring management system of claim 7 wherein the exception tables are based on regulations of a type that includes local, county, state, federal and other regulatory entities.

10. The monitoring management system of claim 7 wherein the exception tables are based on non-regulatory rules of a type that includes corporate policy and industry standards.

11. The monitoring management system of claim 2 wherein the monitoring data includes alarm data that the auditor audits to provide one or more exception reports.

12. The monitoring management system of claim 1 wherein the plurality of devices includes more than one type of device.

13. The monitoring management system of claim 12 wherein the more one than one device type includes RS232, RS485, FireWire, Current Loop, and Ethernet.

14. The monitoring management system of claim 1 wherein the gateway server further includes plural device-specific software modules, each module associated with a corresponding device port for handling processing of data through the device port.

15. The monitoring management system of claim 14 wherein the gateway server processor is adapted to identify the type of device port and load the corresponding device-specific software module into a processor memory.

16. The monitoring management system of claim 1 wherein the host is connected to the gateway server over a communications network.

17. The monitoring management system of claim 16 wherein the communications network includes a data network.

18. The monitoring management system of claim 16 wherein the communications network includes a public switched telephone network.

19. The monitoring management system of claim 1 further comprising a data source that communicates other monitoring data in the common format to the host, wherein the parser parses the received other monitoring data and the auditor audits the parsed other monitoring data.

20. The monitoring management system of claim 19 wherein the host further includes one or more exception tables that define rules for testing for out of limit conditions associated with monitored resources and wherein the auditor provides auditing by evaluating the parsed other monitoring data based on one or more rules defined by one or more entries of the exception tables to provide one or more exception reports based on an outcome of the audit.

21. The monitoring management system of claim 20 wherein the one or more exception reports include daily, periodic and manual compliance reports.

22. The monitoring management system of claim 19 wherein the other monitoring data includes alarm data that the auditor audits to provide one or more exception reports.

23. The monitoring management system of claim 1 wherein the host further includes a user interface application that provides access to audited data.

24. The monitoring management system of claim 23 wherein the devices are associated with monitoring multiple systems at multiple locations, and wherein the user interface application provides access to data from multiple systems and multiple locations.

25. A gateway server comprising:

a plurality of device ports, each device port for connecting to a corresponding monitoring device for receiving monitoring data associated with monitoring of a corresponding resource, the monitoring data for each particular device represented in a data format specific to that device; and

a processor for processing the received data into a common format from the device-specific formats, and a communication port for communicating the processed data.

26. The gateway server of claim 25 wherein the common format defines a data record structure that includes a device identifier field for identifying the specific device and a native data field for carrying the monitoring data.

27. The gateway server of claim 26 wherein the monitoring data carried in the native data field is in the device-specific format.

28. The gateway server of claim 26 wherein the monitoring data carried in the native data field is modified from the device-specific format.

29. The gateway server of claim 26 wherein the processed monitoring data in the common format comprises plural data records that is communicated as a data file.

30. The gateway server of claim 26 further comprising plural device-specific software modules, each module associated with a corresponding device port for handling processing of data through the device port.

31. The gateway server of claim 30 wherein the processor is adapted to identify the type of device port and load the corresponding device-specific software module into a processor memory.

32. A host comprising:

a receiver for receiving monitoring data in a common format, the monitoring data associated with monitoring of resources by corresponding monitoring devices, the monitoring data for each particular device represented in a data format specific to that device, the common format defining a data record structure that includes a device identifier field for identifying the specific device and a native data field for carrying the monitoring data;

a parser for parsing the received data based on the device identifier field and native data identifiers contained within the native data field;

one or more exception tables that define rules for testing for out of limit conditions associated with monitored resources; and

an auditor for auditing the parsed data by evaluating the parsed data based on one or more rules defined by one or more entries of the exception tables to provide one or more exception reports based on an outcome of the audit.

33. The host of claim 32 wherein the monitoring data carried in the native data field is in the device-specific format.

34. The host of claim 32 wherein the monitoring data carried in the native data field is modified from the device-specific format.

35. The host of claim 32 wherein the monitoring data in the common format comprises plural data records that is communicated to the host as a data file.

36. The host of claim 32 wherein the one or more exception reports are any of a type that includes daily, periodic and manual compliance reports.

37. The host of claim 32 wherein the exception tables are based on regulations of a type that includes local, county, state, federal and other regulatory entities.

38. The host of claim 32 wherein the exception tables are based on non-regulatory rules of a type that includes corporate policy and industry standards.

39. The host of claim 32 wherein the monitoring data includes alarm data that the auditor audits to provide one or more exception reports.

40. The host of claim 32 wherein the received monitoring data includes other monitoring data in the common format from a data source, wherein the parser parses the received other monitoring data and the auditor audits the parsed other monitoring data.

41. A method of communication at a gateway server, the method comprising:

receiving monitoring data associated with monitoring of resources at a plurality of device ports connected to corresponding monitoring devices, the monitoring data for each particular device represented in a data format specific to that device; and

processing the received data into a common format from the device-specific formats, and

communicating the processed data from a communication port.

42. A method of communicating at a host, the method comprising:

receiving monitoring data in a common format, the monitoring data associated with monitoring of resources by corresponding monitoring devices, the monitoring data for each particular device represented in a data format specific to that device, the common format defining a data record structure that includes a device identifier field for identifying the specific device and a native data field for carrying the monitoring data;

parsing the received data based on the device identifier field and native data identifiers contained within the native data field;

defining rules in one or more exception tables for testing for out of limit conditions associated with monitored resources; and

auditing the parsed data by evaluating the parsed data based on one or more rules defined by one or more entries of the exception tables to provide one or more exception reports based on an outcome of the audit.

43. A gateway server comprising:

means for receiving monitoring data associated with monitoring of resources at a plurality of device ports connected to corresponding monitoring devices, the monitoring data for each particular device represented in a data format specific to that device; and

means for processing the received data into a common format from the device-specific formats, and

means for communicating the processed data from a communication port.

44. A host comprising:

means for receiving monitoring data in a common format, the monitoring data associated with monitoring of resources by corresponding monitoring devices, the monitoring data for each particular device represented in a data format specific to that device, the common format defining a data record structure that includes a device identifier field for identifying the specific device and a native data field for carrying the monitoring data;

means for parsing the received data based on the device identifier field and native data identifiers contained within the native data field;

means for defining rules in one or more exception tables for testing for out of limit conditions associated with monitored resources; and

means for auditing the parsed data by evaluating the parsed data based on one or more rules defined by one or more entries of the exception tables to provide one or more exception reports based on an outcome of the audit.