Capture the desired precision for analogs in the backend for use by the HMI

Big Picture User Experience

Customers desire to configure the number of decimal places used when displaying floating point numbers on the alarm summary only.

Detailed Description

The current workaround is to use the internationalisation feature to configure how the number is formatted. This is seen as only a partial solution, plus, number formatting in ResX was not part of the i18n effort for ES2021, and requires testing before we can officially support it. Meanwhile, we know that projects are already relying on this method.
Aha Feature: OASYS-390 (Make number formatting a tested and supported aspect of ResX file - estimate requested for 2022 SP1) is to remedy that.
Further, the limitations of the workaround are that one cannot have different precision for different points. EG. the HIHI alarm for pressure may only need 2 DP, whereas the HIHI alarm for a specific gravity needs 4.

Events will always match the same precision as the alarm

The customer wants to retain the full precision in the timeline database, which is made available via realtime interfaces, and then historised in timeseries with the full precision also.

• The precision be set at the point level

  • And it is only used when formatting alarms in the realtime almsum table based on this point's value

Acceptance Criteria

The customer is able to configure how a point's analog value should appear when rendered into an alarm text message.

Business Value

This is seen as table stakes by our customers. The effort required to edit the ResX files is high, and error prone (you might miss a string).
Customers want to configure the decimal placed according to measurement type. Pressures and temperatures might only need 1 or 2 decimals places, whereas a density may need 4.