Annex A (informative) Aggregate Specific examples – Historical Access ToC Previous

A.1 Historical Aggregate specific characteristics ToC Previous Next

A.1.2 Example Aggregate data – Historian 2 ToC Previous Next

This example is included to illustrate non-periodic data. For the purposes of Historian 2 examples consider a source historian with the following data:

Timestamp Value StatusCode Notes
12:00:00 - Bad_NoData First archive entry, Point created
12:00:02 10 Raw, Good  
12:00:25 20 Raw, Good  
12:00:28 25 Raw, Good  
12:00:39 30 Raw, Good  
12:00:42 - Raw, Bad Bad quality data received, Bad data entered
12:00:48 40 Raw, Good Received Good StatusCode value
12:00:52 50 Raw, Good  
12:01:12 60 Raw, Good  
12:01:17 70 Raw, Uncertain Value is flagged as questionable
12:01:23 70 Raw, Good  
12:01:26 80 Raw, Good  
12:01:30 90 Raw, Good  
  - No Data No more entries, awaiting next Value

readme_files/image009.jpg Figure 7 – Example Data for Historian 2

For the purposes of all Historian 2 examples:

  1. TreatUncertainAsBad = True. Therefore Uncertain values are treated as Bad, and not included in the Aggregate call.
  2. Stepped Attribute = False. Therefore SlopedInterpolation is used between data points.
  3. UseSlopedExtrapolation = False. Therefore SteppedExtrapolation is used at end boundary conditions.
  4. PercentBad = 100, PercentGood = 100. Therefore unless if all values are Good then the quality will be Good, or if all values are Bad then the quality will be Bad, but if there is some Good and some Bad then the quality will be Uncertain.

Previous Next