Assets and Data Point History
- Last UpdatedApr 05, 2020
- 1 minute read
The introduction of Dynamic Assets in AVEVA Mobile Operator created the need to retrieve data point history differently. The following table provides an overview of how data points are retrieved.
|
Scenario |
Criterion or Criteria |
|
Static Asset, Without Shared Data Points |
Task Identifier |
|
Any Asset, With Shared Data Points |
|
|
Dynamic or Inherited Asset, Without Shared Data Points |
|
The scenario in which a Dynamic Asset does not use Shared Data Points differs because a single Task can be performed on different Assets.
For example, let's say Task A, configured for Dynamic Asset selection, directs the Operator to collect inlet pressure on a pump.
The task is then performed on Pump 101 several times, then on Pump 102. Since the Assets are different, the reading taken can represent different acceptable ranges.
If the data point history were retrieved on the basis of a Task identifier only, the results may represent readings of 10, 11, 10, and then 110, 111, and so forth. The data point history would display completely unrelated readings, and for this reason, the Asset identifier is also used.