Allow specification of PI Point Attributes set by the PI Asset Connector for Emerson DeltaV 3.X

Argument in Support of Enhancement Request:

Allow Specification of PI Point Attributes Set by the PI Asset Connector for Emerson DeltaV 3.X

Summary of Issue:

After upgrading from DeltaV v13.3.2 to v15.LTS, and transitioning from DeltaV Advanced Continuous Historian (DVACH) to Enterprise PI Historian (EEH), a discrepancy in how UINT32 DeltaV points are mapped to PI tags has emerged. Previously, under DVACH, UINT32 tags were stored as Int32, but now under EEH, the same data types are being stored as Float64 on both the Enterprise PI Server and Site PI Server. This inconsistency causes practical issues for long-term data management, client usability, and standardization.

Why This Enhancement is Necessary:

1) Lack of Control Over PI Point Attribute Definitions Leads to Inconsistencies

The current functionality of the PI Asset Connector for Emerson DeltaV 3.X does not allow users to specify PI Point Attributes before creation—it simply maps attributes based on values in EntHist.xml or applies default values. However, because DeltaV’s representation of UINT32 data has changed over time, users have no way to enforce consistency in how similar data types are mapped.

This has resulted in an inconsistent data model where pre-existing tags of the same type are Int32, but new ones are Float64, breaking the uniformity of stored values.

2) Client Tools Display Issues & User Experience Impact

Storing these values as Float64 creates unintended display issues in client tools such as PI Vision, or Datalink, 3rd Party tools. Instead of clean 0 or 1 values for discrete signals (e.g., level switches, pressure switches, status indicators), users now see floating-point representations (e.g., 0.000000xx, 1.000000xx). While technically correct, this:

• Requires manual adjustments to number formatting in client tools, making it more difficult for operators to read and interpret data efficiently.

• Causes visual inconsistencies when historical Int32 values are displayed alongside newly created Float64 values.

Allowing users to set PI Point Attributes before point creation would help prevent these formatting problems by enabling adjustments to DisplayDigits, ExcDev, and other key attributes before storage.

3) Storage & Performance Concerns

Float64 data types require more disk space than Int32, which can lead to:

• Increased storage costs over time, as more high-frequency tags are created.

• Potential performance impacts, especially in analytics that need to process large datasets.

This is particularly important for customers like us, who retain PI data for 15+ years, meaning small inefficiencies can have long-term scalability consequences.

4) Vendor Coordination Issues Leave Customers Stuck in the Middle

Both Emerson and Aveva have taken different approaches to handling UINT32:

• Emerson previously mapped UINT32 as Int32.

• Aveva now maps UINT32 as Float64.

This means the same system is now storing similar DeltaV data differently before and after an upgrade. With no ability to modify the Asset Connector’s behavior before point creation, we are left with no standardized solution, and neither vendor is taking responsibility for aligning data handling methods.

This enhancement would give end users the flexibility to implement a standardized approach that best fits their historical data and operational needs, rather than being forced into a one-size-fits-all mapping dictated by current limitations.

5) No Workable Alternative Without Breaking Synchronization

While manually modifying point attributes after creation (e.g., using PI Builder, SMT > Point Builder) is possible, this is not an acceptable workaround for the following reasons:

• Breaks synchronization between the Enterprise PI Server and Site PI Server.

• Requires constant manual intervention, which is impractical for large systems.

• Does not prevent the problem at the source, meaning all future points will still be created incorrectly.

Recommended Enhancement Scope:

To properly address this issue, Aveva should modify the PI Asset Connector for Emerson DeltaV 3.X to allow pre-configuration of PI Point Attributes before point creation. Specifically, users should be able to control:

• Point Type (e.g., Int32 vs. Float64 where applicable)

This aligns with the existing enhancement request:

“The PI Asset Connector for Emerson DeltaV 3.X sets PI Point Attributes either based on the values in the enterprise historian configuration file (EntHist.xml) or based on default values. It would be useful to have the option to adapt the PI Point Attributes set by the DeltaV Asset Connector before a PI Point is created.”

However, this request should be expanded to explicitly include the ability to define Point Type (e.g., Int32 vs. Float64) and related attributes to maintain consistency across historical and new PI tags.