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

A.1 Historical Aggregate specific characteristics ToC Previous Next

A.1.1 Example Aggregate data – Historian 1 ToC Previous Next

For the purposes of Historian 1 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:10 10 Raw, Good  
12:00:20 20 Raw, Good  
12:00:30 30 Raw, Good  
12:00:40 40 Raw, Bad ANNOTATION: Operator 1
Jan-02-2012 8:00:00 Scan failed, Bad data entered
ANNOTATION:
Jan-04-2012 7:10:00 Value cannot be verified
12:00:50 50 Raw, Good ANNOTATION: Engineer1
Jan-04-2012 7:00:00 Scanner fixed
12:01:00 60 Raw, Good  
12:01:10 70 Raw, Uncertain ANNOTATION: Technician_1
Jan-02-2012 8:00:00 Value flagged as questionable
12:01:20 80 Raw, Good  
12:01:30 90 Raw, Good  
  null No Data No more entries, awaiting next scan

The example historian also has Annotations associated with three data points.

readme_files/image008.jpg Figure 6 – Example Data for Historian 1

For the purposes of all Historian 1 examples:

  1. TreatUncertainAsBad = False. Therefore Uncertain values are included in Aggregate calls.
  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 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