# US 11,443,467 B2 · Server systems and methods for utilizing a namespace property to correlate process tag values to corresponding events > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,443,467 B2 - Document ID: US11443467B2 - Status: Granted - Kind: B2 - Application number: 17/153,619 - Filed: 2021-01-20 - Published: 2021-08-12 - Granted: 2022-09-13 - Earliest claimed: 2017-12-28 - Assignees: Aveva Software, LLC - Applicants: Aveva Software, LLC - Inventors: Brian Kenneth Erickson; Sripraneeth Kumar Nara; Ravi Kumar Herunde Prakash; Vinay T. Kamath; Abhijit Manushree - Web page: https://patentgrep.com/patent/US11443467B2 ## CPC - G06T 11/26: Drawing of charts or graphs - G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)} - G06F 16/24568: {Data stream processing; Continuous queries} - G06F 16/285: {Clustering or classification} - G06F 16/904: Browsing; Visualisation therefor (for navigating the web G06F16/954; browsing optimisation for the web G06F16/957) - G06T 11/60: Creating or editing images; Combining images with text - G06T 2200/24: involving graphical user interfaces [GUIs] - G08B 5/22: using electric transmission; using electromagnetic transmission - G06T: IMAGE DATA PROCESSING OR GENERATION, IN GENERAL - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G08B: SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS ## Abstract Automated correlation of process attribute value changes with events related to the changes. A managed historian utilizes a namespace property to correlate process tag values with corresponding events. The managed historian generates and provides to remote user devices a graphical user interface that includes a plot of data values of the process tag and a visual icon representing the event overlaid atop the plot of data values. ## Claims ### Claim 1 A system for correlating a process tag value with a corresponding event comprising: a managed historian server comprising one or more computers comprising one or more processors and one or more non-transitory computer readable media, the non-transitory computer readable media having program instructions stored thereon that when executed configure the managed historian server to: receive, by the one or more processors, a process tag from an application server; determine, by the one or more processors, a namespace property of the process tag; receive, by the one or more processors, an event associated with the process tag; set, by the one or more processors, a namespace property of the event to match the namespace property of the process tag; and link, by the one or more processors, the event to the process tag using the matched namespace properties. ### Claim 2 (depends on 1) The system of claim 1, wherein determining a namespace property of the process tag includes parsing the process tag. ### Claim 3 (depends on 1) The system of claim 1, wherein the application server includes a name property that identifies the application server; and wherein the namespace property includes the name property. ### Claim 4 (depends on 3) The system of claim 3, wherein the system further comprises a tier historian server comprising a hierarchic name; wherein the tier historian server is configured to receive the process tag from the application server; and wherein the managed historian server is configured to receive the process tag from the tier historian server. ### Claim 5 (depends on 4) The system of claim 4, the non-transitory computer readable media including further program instructions stored thereon that when executed configure the managed historian server to: create, by the one or more processors, a fully qualified tag name for the process tag; wherein the fully qualified tag name includes the name property and the hierarchic name. ### Claim 6 (depends on 5) The system of claim 5, wherein determining a namespace property of the process tag includes parsing the process tag. ### Claim 7 (depends on 5) The system of claim 5, the non-transitory computer readable media including further program instructions stored thereon that when executed configure the managed historian server to determine, by the one or more processors, whether the process tag already exists. ### Claim 8 (depends on 7) The system of claim 7, the non-transitory computer readable media includes further program instructions stored thereon that when executed configure the managed historian server to store, by the one or more processors, the existing process tag as a saved version if the process tag already exists. ### Claim 9 (depends on 7) The system of claim 7, the non-transitory computer readable media including further program instructions stored thereon that when executed configure the managed historian server to set, by the one or more processors, the fully qualified tag name as an active version of the process tag. ### Claim 10 A system for correlating a process tag value with a corresponding event comprising: a managed historian server comprising one or more computers comprising one or more processors and one or more non-transitory computer readable media, the non-transitory computer readable media having program instructions stored thereon that when executed configure the managed historian server to: receive, by the one or more processors, a process tag from an application server; determine, by the one or more processors, a namespace property of the process tag by parsing the process tag; receive, by the one or more processors, an event associated with the process tag; set, by the one or more processors, a namespace of the event to match a namespace of the process tag; link, by the one or more processors, the event to the process tag using the matched namespace; and display, by the one or more processors, an event icon representing the event along with data values of the process tag. ### Claim 11 (depends on 10) The system of claim 10, wherein the application server includes a name property that identifies the application server; and wherein the namespace property includes the name property. ### Claim 12 (depends on 11) The system of claim 11, wherein the system further comprises a tier historian server comprising a hierarchic name; wherein the tier historian server is configured to receive the process tag from the application server; and wherein the managed historian server is configured to receive the process tag from the tier historian server. ### Claim 13 (depends on 12) The system of claim 12, the non-transitory computer readable media includes further program instructions stored thereon that when executed configure the managed historian server to: create, by the one or more processors, a fully qualified tag name for the process tag; and wherein the fully qualified tag name includes the name property and the hierarchic name. ### Claim 14 (depends on 10) The system of claim 10, the non-transitory computer readable media including further program instructions stored thereon that when executed configure the managed historian server to determine, by the one or more processors, whether the process tag already exists. ### Claim 15 (depends on 14) The system of claim 14, the non-transitory computer readable media including further program instructions stored thereon that when executed configure the managed historian server to store, by the one or more processors, the existing process tag as a saved version if the process tag already exists. ### Claim 16 (depends on 15) The system of claim 15, the non-transitory computer readable media includes further program instructions stored thereon that when executed configure the managed historian server to set, by the one or more processors, a fully qualified tag name as an active version of the process tag. ### Claim 17 (depends on 16) The system of claim 16, wherein the fully qualified tag name includes the name property and a hierarchic name. ### Claim 18 (depends on 17) The system of claim 17, wherein the system further comprises a tier historian server comprising the hierarchic name; wherein the tier historian server is configured to receive the process tag from the application server; and wherein the managed historian server is configured to receive the process tag from the tier historian server.