Big Picture User Experience
With Analog Cutoff, the value read from the field is clamped to user-configured Hi or Low values. With the value clamped, all SCADA Controller sees is the clamped value. With this feature enhancement, a clamped DQ/Indication is added to notify that the value the SCADA Controller sees is clamped either to Hi or Low values. The indication will indicate that the real value that is read from the field is not what the controller sees.
Detailed Description
The Analog Cutoff feature is designed to reduce false readings from field devices for analog and rate points. Analog Cutoff, validates the field read value against configured Hi and low configured values, and in case the field value is above or below the Hi/Low thresholds, it will replace the field value with the Hi/Low setting. However, When the value is clamped, there is no indication that the value is actually clamped.
As such, this request is to add a clamping indication for analog and rate points when the field value is cut off and replaced with the upper or lower threshold. The clamp indication will indicate to the SCADA Controller that the value displayed for a telemetry point is the clamped value and the field value is different from the displayed value. With this feature, it is requested that the clamped indication (or DQ) shall be displayed to the SCADA controller on the HMI display as points data attributed and adhere to points attribute (DQ) precedence as configured within the FDA.
Additionally, in the case, the clamped indication is applied and the point's value is collected to the historical DB by the collection process, the clamped DQ must be collected as well and interleaved with the configured precedence of other baseline DQ.
Business Value
Improve SCADA Controllers situational awareness by presenting the most important points’ attributes on ezXOS Trend and HMi displays.
Customer, Project, and Deadline Details
-
Number of customers (names/projects) that will consume this
-
Deadlines and Commitments
-
Commercial and/or Contractual Impacts
Out of Scope
Assumptions
Dependencies
Productization of configurable DQ collection.
The HMI team needs to provide guidance on the “contracted” data format expected by FCO object after the design phase of FCO. (see ADO - 1006723) - First step was done. During implementation the two team will need to collaborate.
PSR - Performance, Scalability, Resilience
NFR – Non-Functional Requirements
Properly documented
Risks/Mitigations
Most of the DQ are baseline attributes that are defined either in flags, Hilo or tankHilow structures. Clamped DQ is currently not part of these.
Link to full doc (appendix incl):https://aveva.sharepoint.com/sites/MidStreamPM/Shared%20Documents/Customers/Shell%20Pipeline/Rationalization/PMFR/Historical%20Collection/PMFR%20-%20Historical%20Collection.docx?web=1
Aha Epic:https://aveva.aha.io/epics/OASYS-E-35
AHA Feature:TBD
Corresponding HMI Feature:https://dev.azure.com/AVEVA-VSTS/OASyS/_workitems/edit/1006723
User Story
As a SCADA controller, I want the point's data attribute indicated when the point is clamped (cutoff). So that I can know the value that is presented in the HMI display is replaced (clamped) by the Enterprise SCADA system.
As SCADA Administrator, I want to configure Clamped attribute with precedence, icon, and "silo" for the Flex Device and Flex text objects. So that the clamped attribute will be part of the overall DQ confirmation for the system.
As SCADA Controller, I want Clamped attribute to be reflected with configured color and pen-style in my Trends if that was the highest attribute active on the point at the collected time. So that, when inspecting trends of historical data I can know that the value was clamped.
