Big Picture User Experience

This enhancement will improve the point-to-point verification process by aligning the state-enumeration numbering with the states defined in the messageSet table. This will ensure that the field technician and the SCADA operator are configuring the correct abnormal states for digital points to alarm against by either using the state name, or the raw number

Detailed Description

During Point to Point Verification, the field technician communicates essential information to the SCADA Database administrator. For multistate points, the technician may report abnormal states configured in the device using decimal equivalents programmed in the field device. The SCADA Database admin must configure these points to match the decimal numbers in the PLC and ensure the correct state name corresponds with the raw decimal number. Below is a PoC that outlines the abnormal states. The enhancement is to display the raw number to the left of the enumeration state, because without this, , it will be extremely difficult for the field technician and the DB Admin to confirm the states are one and the same, especially when configuring multistate points which have a large messageSet with non-unique message state names. For example, look at states 10 and 12 below:

Figure 1 - A Proof of Concept showing the new raw number to the left of the enumeration name. Without this number, states 10 and 12 appear identical.

Currently, in order to verify alignment, the SCADA Database Admin must check the MessageSet Table of the selected record. Due to the lack of standardization across the organization, configuration becomes challenging with varying numeric values for the same state. It would be beneficial if the ADE form that is used to configure abnormal states included the decimal numbers as well as their corresponding text states from the MessageSet.

Business Value

Improve Point to Point Verification by eliminating a source of ambiguity in the SCADA interface, which simplifies the effort of configuration and reduces risk of human error.

Acceptance Criteria

• The raw value of the messageSet state should be printed on the ADE form alongside the corresponding state.

• Both Status and MultiState points should be enhanced to support this behavior.

• User Documentation updated.

• 

Out of Scope

No other place will exhibit this behavior. Alarms, events and all other Visual representation of states will remain as is today. Customers are able to modify the baseline screens to add this and any other information as they desire.

Assumptions

This is a cosmetic change to the abnormal state config screen only. No additional logic, sanity checks or functions are required. Config change events are not changed.

Dependencies

None Identified

Upgradability

No issue or concerns have been identified. This is just an ADE form that reads the data directly from the DB.

PSR - Performance, Scalability, Resilience

No PSR impact as this only enhancement is only on the ADE form edit. There are no processing, alarming or any other places that his behavior will be observed.

NFR - Non-Functional Requirements

none identified.

Mock-up / Supporting Information