BoundingValues – OPC Unified Architecture – Part 11: Historical Access

OPC Unified Architecture – Part 11: Historical Access

v1.05.04

1Scope
2Normative references
3Terms, definitions, and abbreviations
- 3.1Terms and definitions
- 3.2Abbreviated terms
4Concepts
5Historical Information Model
6Historical Access specific usage of Services
Annex AClient conventions (Informative)
- A.1How clients can request timestamps
- A.2Determining the first or last historical data point

3.1.2 BoundingValues

values associated with the starting and ending time

Note 1

Note 1 to entry: BoundingValues are the values that are associated with the starting and ending time of a ProcessingInterval specified when reading from the historian. BoundingValues may be required by Clients to determine the starting and ending values when requesting RawData over a time range. If a RawData value exists at the start or end point, it is considered the bounding value even though it is part of the data request. If no RawData value exists at the start or end point, then the Server will determine the boundary value, which may require data from a data point outside of the requested range. See 4.6 for details on using BoundingValues.