System event filtering and notification for OPC clients

• US 20040006652A1
• Filed: 06/05/2003
• Published: 01/08/2004
• Est. Priority Date: 06/28/2002
• Status: Abandoned Application

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Lin, Haur J., Prall, John M., Urso, Jason T.
• Application Number:
  US10/455,482
• Publication Number:
  US 20040006652A1
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 2209/546 Xcast
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A system operating in a Windows environment that provides notification of events to OPC clients is disclosed. NT events generated in the system are filtered and converted to an OPC format for presentation to the OPC clients. The converted NT event notification includes a designation of the source that generated the NT event. The system includes a filter configuration tool that permits entry of user-defined filter criteria and transformation information. The transformation information includes the source designation, event severity, event type (simple, tracking and conditional), event category, event condition, event sub-condition and event attributes.

Claims

1. A method of notification of OPC alarms and events (OPC-AEs) and NT alarms and events (NT-AEs) to an OPC client comprising:

converting an NT-AE notification of an NT-AE to an OPC-AE notification; and

presenting said OPC-AE notification to said OPC client.

2. The method of claim 1, further comprising:

filtering said NT-AEs according to filter criteria.

3. The method of claim 2, wherein said filter criteria are provided by a filter configuration tool.

4. The method of claim 2, wherein said filter criteria are provided by a system event filter snap-in.

5. The method of claim 1, wherein said converting step adds additional information to said NT-AE notification to produce said OPC-AE notification.

6. The method of claim 5, wherein said additional information includes a designation of the source that created said NT-AE notification.

7. The method of claim 5, wherein said source designation comprises a name of a computer that created said NT-AE notification and an insertion string of said NT-AE.

8. The method of claim 7, wherein said insertion string identifies a component that generated said NT-AE.

9. The method of claim 5, wherein said additional information includes an event severity.

10. The method of claim 9, wherein said event severity is an NT compliant severity, wherein said converting step provides a transformation of said NT compliant severity to an OPC compliant severity.

11. The method of claim 10, wherein said transformation is based on pre-defined severity values.

12. The method of claim 11, wherein said transformation is based on logged severity values of said NT-AE notification.

13. The method of claim 5, wherein said additional information is one or more items selected from the group consisting of:

event cookie, source designation, event severity, event category, event type, event acknowledgeability and event acknowledge state.

14. The method of claim 1, wherein said OPC client is either local or remote with respect to a source that created said NT-AE notification.

15. The method of claim 1, wherein said presenting step presents said OPC-AE notification to said OPC client via a multicast link.

16. The method of claim 1, wherein said NT-AEs comprise condition events, simple events or tracking events.

17. The method of claim 16, wherein at least one of said condition events reflects a state of a specific source.

18. The method of claim 1, further comprising synchronizing said OPC-AE notifications among a plurality of nodes via a multicast link.

19. The method of claim 1, wherein said OPC-AE notifications are accessible via OPC-AE interfaces or via WMI interfaces.

43. The method of claim 1, wherein one or more of said NT-AEs are condition events that are generated by a source and that reflect a state of said source, and further comprising changing a status between active and inactive of an earlier-occurring one of said condition events in response to a later-occurring one of said condition events generated due to a change in state of said source.

44. The method of claim 43, wherein said converting and presenting steps convert NT-AE notifications of said earlier- and later-occurring condition events to OPC-AE notifications for presentation to OPC clients.

20. A device for notification of OPC alarms and events (OPC-AEs) and NT alarms and events (NT-AEs) to an OPC client, said device comprising:

a system event provider that links an NT-AE notification of an NT-AE to additional information; and

a system event server that packages said NT-AE notification and said additional information as an OPC-AE notification for presentation to said OPC client.

21. The device of claim 20, further comprising a filter that filters said NT-AE notifications according to filter criteria.

22. The device of claim 21, wherein said filter criteria are provided by a filter configuration tool.

23. The device of claim 21, wherein said filter criteria are provided by a system event filter snap-in.

24. The device of claim 20, wherein said additional information includes a designation of the source that created said NT-AE notification.

25. The device of claim 24, wherein said source designation comprises a name of a computer that created said NT-AE and an insertion string of said NT-AE, wherein said NT-AE is a condition event.

26. The device of claim 25, wherein said insertion string identifies a component that generated said NT-AE.

27. The device of claim 20, wherein said additional information includes an event severity.

28. The device of claim 27, wherein said event severity is an NT compliant severity, wherein said system event provider provides a transformation of said NT compliant severity to an OPC compliant severity.

29. The device of claim 28, wherein said transformation is based on pre-defined severity values.

30. The device of claim 28, wherein said transformation is based on logged severity values of said NT-AE notification.

31. The device of claim 20, wherein said additional information includes one or more items selected from the group consisting of:

event cookie, source designation, event severity, event category, event type, event acknowledgeability and event acknowledge state.

32. The device of claim 20, wherein said OPC client is either local or remote with respect to a source that created said NT-AE notification.

33. The device of claim 20, further comprising a synchronized repository provider that presents said OPC-AE notification to said OPC client via a multicast link.

34. The device of claim 20, wherein said events are condition events, simple events or tracking events.

35. The device of claim 34, wherein at least one of said condition events reflects a state of a specific source.

36. The device of claim 20, further comprising a synchronized repository for synchronizing said OPC-AE notifications among a plurality of nodes via a multicast link.

37. The device of claim 20, wherein said OPC-AE notifications are accessible via OPC-AE interfaces or via WMI interfaces.

38. The device of claim 20, wherein said system event server serves said OPC-AE notifications to said OPC client.

39. The device of claim 20, wherein said system event provider communicates with said system event server via a WMI interface.

40. The device of claim 20, further comprising:

an NT event provider that provides said NT-AE notifications; and

a filter that filters said NT-AE notifications according to filter criteria so that only NT-AE notifications that satisfy said filter criteria are linked to OPC-AE notifications by said system event provider.

41. The device of claim 20, wherein one or more of said NT-AE notifications are condition events that are generated by a source and that reflect a state of said source, and further comprising changing a status between active and inactive of an earlier-occurring one of said condition events in response to a later-occurring one of said condition events generated due to a change in state of said source.

42. The device of claim 41, wherein said system event provider links the NT-AE notifications of said earlier- and later-occurring condition events to OPC-AE notifications for presentation to OPC clients.

45. A method for populating a filter that filters NT alarms and events (NT-AEs) for conversion to OPC alarms and events comprising:

entering NT-AEs for which notifications thereof are to be passed by said filter; and

configuring said entered NT-AEs with one or more event characteristics selected from the group consisting of;

event type, event source, event severity, event category, event condition, event sub-condition and event attributes.

46. The method of claim 45, wherein said event type comprises condition, simple and tracking.

47. The method of claim 45, wherein said event source comprises a name of a computer that created a particular NT-AE notification and an insertion string of the NT-AE thereof.

48. The method of claim 45, wherein said event severity comprises predefined severity values or logged severity values.

49. The method of claim 45, wherein said event category comprises a status of a device.

50. The method of claim 45, wherein said event attributes comprise for a particular event category, an acknowledgeability of a particular NT-AE and a status of active or inactive.

53. The configurator of claim 49, wherein said event source comprises a name of a computer that created a particular NT-AE notification and an insertion string of an NT-AE thereof.

54. The configurator of claim 49, wherein said event severity comprises predefined severity values or logged severity values.

55. The configurator of claim 49, wherein said event category comprises a status of a device.

56. The configurator of claim 49, wherein said event attributes comprise for a particular event category an acknowledgeability of a particular NT-AE and a status of active or inactive.

51. A configurator that populates a filter that filters NT alarms and events (NT-AEs) for conversion to OPC alarms and events comprising:

a configuration device that provides for entry into said filter of NT-AEs for which notifications thereof are to be passed by said filter and configuration of said entered NT-AEs with one or more event characteristics selected from the group consisting of;

event type, event source, event severity, event category, event condition, event sub-condition and event attributes.

52. The configurator of claim 51, wherein said event type comprises condition, simple and tracking.