View Issue Details

IDProjectCategoryView StatusLast Update
000459110000-011: Historical AccessSpecpublic2023-03-23 18:26
ReporterDoug Stewart Assigned ToPaul Hunkar  
PrioritynormalSeverityfeatureReproducibilityN/A
Status closedResolutionfixed 
PlatformPCOSWindowsOS Version8.1
Fixed in Version1.05.03 RC1 
Summary0004591: Need a new relationship type to relate a node in a realtime OPC UA Server to another node in Historical OPC UA Server.
Description

Part 11 recognizes that it is a common configuration that there will be a specialized OPC UA Server that provides historical access to data.

The reality of that is that you have 1 server that has the capability of Realtime data updates, and probably a full address space. And another server that has a scoped down set of nodes that may or may not be organized into any particular meaningful address space.

What I think is missing is a relationship type that can be used by these 2 servers that allow them to point to each others nodes with the semantic meaning the target of this relationship is a node that can be used in the historical read services and its has the same semantic meaning as the source node of the relationship, and if its an extended nodeID on another server, you need to call those historical read services on that external OPC UA Server. The inverse of this relationship would also be used by the historical server to indicate an extended nodeID with the semantic meaning, this other node provides the realtime values of this historizing node, and will likely provide more fidelity for the realtime values, and that target node has the same semantic meaning as the source node.

I think a potential browse names for this relationship is HasHistoricalData, and the inverse name would be HasRealtimeData.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2019-06-25 16:12

administrator   ~0010407

Also consider adding a remote reference to the HistoricalConfiguration node also.

Jim Luth

2019-06-25 16:18

administrator   ~0010408

Consider deriving this reference from some yet undefined base class indication "equivalence" or "aspect of" (to be worked out by UA Working Group or Harmonization).

Paul Hunkar

2023-03-23 05:18

developer   ~0018995

Added reference as defined

Jim Luth

2023-03-23 18:26

administrator   ~0019007

Agreed to changes edited in Dallas meeting.

Issue History

Date Modified Username Field Change
2019-01-23 23:11 Doug Stewart New Issue
2019-06-25 16:12 Jim Luth Note Added: 0010407
2019-06-25 16:12 Jim Luth Target Version => 1.05
2019-06-25 16:13 Jim Luth Assigned To => Rod Stein
2019-06-25 16:13 Jim Luth Status new => assigned
2019-06-25 16:18 Jim Luth Note Added: 0010408
2023-03-14 15:53 Paul Hunkar Assigned To Rod Stein => Paul Hunkar
2023-03-23 05:18 Paul Hunkar Status assigned => resolved
2023-03-23 05:18 Paul Hunkar Resolution open => fixed
2023-03-23 05:18 Paul Hunkar Fixed in Version => 1.05.03 RC1
2023-03-23 05:18 Paul Hunkar Note Added: 0018995
2023-03-23 18:26 Jim Luth Status resolved => closed
2023-03-23 18:26 Jim Luth Note Added: 0019007