Device Based History to support additional Data Types

Big Picture User Experience

Enhance Device Based History to support common device based data types such as 32 bit integers and double types. Device Based History is what we call the ability to upload data from a device in bulk, such as historical VTQ data, and events. This is not related to EFM data.

Detailed Description

Newer devices today are capable of storing in their memory data that is 32 bit integer or doubles. This storage locations are used to store TimeSeries data and later uploaded to the Enterprise SCADA. To support these new types Device based History feature (also known as RTUDD) must be enhanced to support these new data types.

Business Value

For device based History feature to support wider range of PLCs and RTUs that are now capable of larger types.

Target Version

Target version for this feature: TBD .

Version the customer is on or consuming: .

Version being targeted by project or future opportunity: TBD.

Customer, Project, and Deadline Details

Customers (names/projects) that will consume this: .

Deadlines and Commitments: No commitments currently made.

Commercial and/or Contractual Impacts: .

Is this a customer funding candidate?: .

Customers System / Architecture

Size: Large

Topology: Enterprise

Any Unique configuration to note?: None

Has this functionality been delivered before?: (project / custom code):

If yes, please include requirements, test cases, test data, use-cases, SWANA captures, ADE screens, database .l files

Out of Scope

None identified

Assumptions

Need to consider if this work result in current API change or we add new API to support new datatypes.
It must support live upgradability

Dependencies

Other Features? Other Teams? Project timelines?

Future considerations?

Upgradability

Backward compatibility.

PSR - Performance, Scalability, Resilience

There is no new requirement for the PSR. The PSR requirement remain the same as in the past product versions.

NFR - Non-Functional Requirements