IP Library Granted Patent US 10,579,601
Granted Patent B2
US 10,579,601 · App. 14/569,220 · Granted Mar 3, 2020

Data dictionary system in an event historian

Inventors: Brian Kenneth Erickson (Long Beach, CA); Bala Kamesh Sista (Lake Forest, CA); Abhijit Manushree (Laguna Niguel, CA); Vinay T. Kamath (Rancho Santa Margarita, CA)
Assignee: AVEVA SOFTWARE, LLC
G06F16/213G06F16/211G06F16/2246G06F2212/205
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,579,601
App. No.
14/569,220
Granted
Mar 3, 2020
Kind
B2
Abstract

An event historian system stores an event data dictionary. The system receives an initial query from a client device on a network connection and responds by providing the event data dictionary information to the client device. The client device sends another query requesting data values which are defined in the event data dictionary. The system responds to the second query by sending results comprising the requested data values to the client system over the network connection.

Claims (48)

1. A system comprising:

a client system; and

an event historian system comprising:

a processor;

a network connection coupling the client system to the event historian system; and

a memory storage device coupled to the processor, said memory storage device storing event data and instructions, said instructions comprising instructions for:

storing an event data dictionary on the memory storage device, the event data dictionary comprising a data schema defining how the event data is stored and organized on the memory storage device and including at least one default data property representing data values currently available for querying;

in response to a change to the organization of the event data on the memory storage device, altering the event data dictionary to match the change;

receiving a first query via the network connection from the client system, the first query requesting one or more data values;

determining if the one or more data values requested by the first query are represented by the default data property and currently available for querying or represented by a custom data property and not currently available for querying;

in response to the first query requesting the data values represented by the custom data property, further altering the event data dictionary to add the custom data property such that the data values represented by the custom data property are available for querying;

sending the further altered event data dictionary to the client system via the network connection in response to said receiving the first query;

receiving a second query via the network connection from the client system, said second query requesting one or more data values defined in the further altered event data dictionary as represented by the custom data property and available for querying; and

sending results to the client system via the network connection in response to said receiving the second query, the results comprising the one or more data values requested by the second query;

wherein the client system is configured to:

obtain the further altered event data dictionary sent by the event historian system; and

interpret the results in accordance with the further altered event data dictionary.

2. The system of claim 1 , said instructions further comprising instructions for receiving a request via the network connection from the client system to add the custom data property to the event data dictionary.

3. The system of claim 2 , said instructions further comprising instructions for amending the event data dictionary to include the custom data property.

4. The system of claim 3 , said custom data property comprising a list data structure comprising a plurality of data values.

5. The system of claim 1 , wherein the event data dictionary comprises event data structures and at least one of provider data structures, user data structures, source data structures, and alarm data structures.

6. The system of claim 1 , said instructions further comprising instructions for confirming the events in the second query exist in the event data dictionary after receiving the second query.

7. The system of claim 5 , said instructions further comprising instructions for determining the second query comprises event data which is not represented in the event data dictionary and updating the event data dictionary with a new event representing the event data which is not represented.

8. The system of claim 1 , said instructions further comprising instructions for:

receiving, by the event historian system, event data from a process control system, said received event data comprising an event data property which is not represented in the event data dictionary; and

storing, by the event historian system, the received event data on the memory storage.

9. The system of claim 8 , said instructions further comprising instructions for updating the event data dictionary to include the event data property from the event data received from the process control system.

10. A method for providing a data dictionary for an event historian system to a client system comprising:

storing, by the event historian system, an event data dictionary on a memory storage device, the event data dictionary comprising a data schema defining how event data is stored and organized on the memory storage device and including at least one default data property representing data values currently available for querying;

in response to a change to the organization of the event data on the memory storage device, altering, by the event historian system, the event data dictionary to match the change;

receiving, by the event historian system, a first query via a network connection from the client system, the first query requesting one or more data values;

determining if the one or more data values requested by the first query are represented by the default data property and currently available for querying or represented by a custom data property and not currently available for querying;

in response to the first query requesting the data values represented by the custom data property, further altering the event data dictionary to add the custom data property such that the data values represented by the custom data property are available for querying;

sending, by the event historian system in response to said receiving the first query, the further altered event data dictionary to the client system via the network connection;

obtaining, by the client system, the further altered event data dictionary sent by the event historian system;

receiving, by the event historian system, a second query via the network connection from the client system, said second query requesting one or more data values defined in the further altered event data dictionary as represented by the custom data property and available for querying;

sending, by the event historian system in response to said receiving the second query, results to the client system via the network connection, the results comprising the one or more data values requested by the second query; and

interpreting, by the client system, the results in accordance with the further altered event data dictionary.

11. The method of claim 10 , further comprising receiving a request via the network connection from the client system to add the custom data property to the event data dictionary.

12. The method of claim 11 , further comprising amending the event data dictionary to include the custom data property.

13. The method of claim 12 , said custom data property comprising a list data structure comprising a plurality of data values.

14. The method of claim 10 , wherein the event data dictionary comprises event data structures and at least one of provider data structures, user data structures, source data structures, and alarm data structures.

15. The method of claim 10 , further comprising confirming the events in the second query exist in the event data dictionary after receiving the second query.

16. The method of claim 15 , further comprising determining the second query comprises event data which is not represented in the event data dictionary and updating the event data dictionary with a new event representing the event data which is not represented.

17. The method of claim 10 , further comprising:

receiving, by the event historian system, event data from a process control system, said received event data comprising an event data property which is not represented in the event data dictionary; and

storing, by the event historian system, the received event data on the memory storage.

18. The method of claim 17 , said instructions further comprising instructions for updating the event data dictionary to include the event data property from the event data received from the process control system.

Assignments (3)
CHANGE OF NAME Recorded Oct 7, 2019
From: SCHNEIDER ELECTRIC SOFTWARE, LLC
To: AVEVA SOFTWARE, LLC
Reel/Frame 050647/0283 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 9, 2017
From: INVENSYS SYSTEMS, INC.
To: SCHNEIDER ELECTRIC SOFTWARE, LLC
Reel/Frame 041935/0683 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 3, 2015
From: ERICKSON, BRIAN KENNETH; SISTA, BALA KAMESH; MANUSHREE, ABHIJIT; KAMATH, VINAY T.
To: INVENSYS SYSTEMS, INC.
Reel/Frame 036235/0810 →