CONNECT to PI release history

Save PDF

Last UpdatedApr 08, 2025
6 minute read

CONNECT
CONNECT to PI Agent
Agents
PI Server

1.1.260 release: 01/30/2025

Adapter Framework: 1.8.3.49

Overview

CONNECT to PI Agent is a hybrid data connectivity software that enables the transfer of data from CONNECT data services to AVEVA PI Server. Together with PI to CONNECT Agent, you can manage bi-directional data flow between PI Server and the CONNECT industrial intelligence platform.  

CONNECT to PI Agent empowers customers by:  

Marrying the power of the cloud with the industry-leading AVEVA PI Server capabilities 
Enhancing collaboration between operations domain experts and other stakeholders 
Sending model and analytic results in the cloud back on-premises to turn insights into action using their familiar tools and existing workflows

Version 1.1.260, released January 30, 2025, is a minor release that adds support for transferring community streams to an AVEVA PI Server.

Enhancements

The following enhancements are included in this release:

The agent now supports the transfer of community streams in CONNECT data services. Previously, each transfer was limited to SDS streams in a single namespace. While namespace-scoped transfers are still supported, community-scoped transfers can now be used to select any SDS stream shared to a particular community in a single transfer.
SDS streams based on derived SDS types are now supported. Previously, the agent would report an error when a stream that is based on a derived type was included in the transfer.
The agent now supports SDS types with properties of type Int64 and NullableInt64, enhancing compatibility with a broader range of data types.

Fixes

The following issues were resolved in this release:

Work Item	Description
3473774	The transfer would fail if the data selections included SDS streams with SDS type IDs that had a common suffix, where the common suffix happened to be delimited by a period (.). For example, the agent would treat the unique IDs “MyType1.CommonSuffix” and “Mytype2.CommonSuffix” as the same ID, causing a failure on startup. This problem has been fixed.
3474289	The transfer would fail if the data selections included SDS streams with SDS types that had UOMs that were not defined in AF server. For example, the quantity "Conductivity" (typically, microsiemens per centimeter) is defined in CONNECT data services but is not defined in AF server. This problem has been fixed. The agent will now ignore such mismatches and will transfer the stream’s data. Moreover, the string representation of the UOM will be transferred to the PI point’s EngUnits attribute, even if the UOM does not have a representation in AF server.
3486818	The CONNECT to PI Configuration Utility could not be used to configure agents in any region other than West US. For example, for namespaces in Northern Europe or Australia, the utility would fail. This problem has been fixed.
3686021	The transfer would fail if Forbidden (HTTP status code 403) was encountered while accessing any SDS stream in the data selections. This problem has been fixed. The agent will now log errors for inaccessible streams and will continue to send data for accessible streams.
3294618	Type IDs for enumeration sets were generated based on the SDS name of the enumeration type. Since names of SDS types are not unique in CONNECT data services, this could lead to type ID collisions, and data would not be transferred for those streams with collisions. The old IDs for enumeration sets were of the form "CONNECT.CONNECT.{sdsType.Name}Enum". Not only were the IDs potentially not unique, the IDs started strangely with “CONNECT.CONNECT”. The ID generation was also not consistent with the IDs generated for complex types, which were simply “{sdsType.Id}”. With this release, the IDs for enumeration types and complex streams now both correspond to “CONNECT.{sdsType.Id}”. Although the new conventions generate more sensible IDs, there are some consequences for upgrades because type IDs cannot be changed for existing streams. As a result, you may see warnings in the PI Web API Windows Event Viewer logs (one error per SDS stream in the transfer, each time that the agent is started), but only if debug logging is enabled for PI Web API. These warnings can be safely ignored.
3617201	The agent previously ignored the interpolation mode set at the SDS stream or SDS type levels, using only the mode specified in the property or property override, which could cause the Step attribute to be set incorrectly for some PI points in the transfer. This problem has been fixed. The agent now properly respects interpolation modes set at four different levels, in the following order of priority, according to the rules defined in SDS. In a stream property override on the stream.  Directly on a property in the SDS type. This provides the default for the property if not overridden by #1 Directly on the stream. This provides the default for the properties if not overridden by #1 or #2. Directly on the type. This provides the default for the properties if not overridden by #1, #2, or #3.

Known issues

This section lists problems and/or enhancements that have been deferred until a future release:

Work Item	Description
000031681	When creating dynamic data of any point type using PI Web API's OMF Endpoint, users may see an error in the PI Server message log similar to this one: >> Postevent failed: [-15031] Point type is not digital Point ID: 7, Connection ID: 25, User: piadmin, User ID: 1, mode: noreplace Event time: 18-Jan-38 00:00:00, value: DS_16382_16382 There is no impact associated with this message, and it can be ignored. Note: This issue needs to be addressed by PI Web API in order to be resolved.

Work Item

Description

000031681

When creating dynamic data of any point type using PI Web API's OMF Endpoint, users may see an error in the PI Server message log similar to this one:

>> Postevent failed: [-15031] Point type is not digital

Point ID: 7, Connection ID: 25, User: piadmin, User ID: 1, mode: noreplace

Event time: 18-Jan-38 00:00:00, value: DS_16382_16382

There is no impact associated with this message, and it can be ignored.

Note: This issue needs to be addressed by PI Web API in order to be resolved.

Security information and guidance

We are committed to releasing secure products.

We proactively disclose aggregate information about the number and severity of security vulnerabilities addressed in each release.

Distribution Kits

Product	Software Version
CONNECT to PI Agent Installation	1.1.260

1.0.1523 release: 08/21/2024

Adapter Framework: 1.8.3.49

Overview

CONNECT to PI Agent is a hybrid data connectivity software that delivers an intuitive user experience for natively managing the transfer of data from CONNECT data services to AVEVA PI Server. Together with PI to CONNECT Agent, you can now manage bi-directional data flow between PI Server and the CONNECT industrial intelligence platform.  

CONNECT to PI Agent empowers customers by:  

Marrying the power of the cloud with the industry-leading AVEVA PI Server capabilities 
Enhancing collaboration between operations domain experts and other stakeholders 
Sending model and analytic results in the cloud back on-premises to turn insights into action using their familiar tools and existing workflows

Features

CONNECT to PI Agent enables users to: 

Transfer CONNECT data services streams from a tenant to PI Tags in AVEVA PI Server 
- Natively supports real-time, historical, and future data transfer  
- Works with simple and complex stream types  
- Allows backfilling PI Tags from the cloud 
Centrally create, configure, and manage transfers within the CONNECT portal 
Authenticate to the PI Web API OMF endpoint with OIDC, Kerberos, or Basic

CONNECT to PI Agent components 

This hybrid release includes the following elements:  

CONNECT to PI Agent Portal: A web page in CONNECT where users can download the CONNECT to PI install kit and centrally create, configure, and manage data transfers.
CONNECT to PI Agent: An installable agent that moves data from CONNECT data services to PI and creates tags as required via OMF and the PI Web API OMF endpoint. For architecture, basic data flow, and technical requirements and prerequisites, please see the documentation.

For more information, see CONNECT to PI Agent.

Security information and guidance

We are committed to releasing secure products.

We proactively disclose aggregate information about the number and severity of security vulnerabilities addressed in each release.

Overview of new vulnerabilities fixed or mitigated

This section is intended to provide relevant security-related information to guide your installation or upgrade decision. AVEVA is proactively disclosing aggregate information about the number and severity of CONNECT to PI Agent security vulnerabilities that are fixed in this release.

For this initial release of CONNECT to PI Agent, the following vulnerabilities have been identified.

Vulnerability Mitigations in CONNECT to PI Agent 1.0.1523 Release

Component	Version	CVE or Reference	CVSS	Mitigation
Microsoft.AspNetCore.Components.WebView.Maui	8.0.70	CVE-2024-35264	8.1	Vulnerable code is not in execution path.
Mudblazor	6.21.0	CVE-2024-35264	8.1	Vulnerable code is not in execution path.
System.Text.Json	8.0.3	CVE-2024-30105	7.5	Vulnerable code is not in execution path.

Distribution Kits

Product	Software Version
CONNECT to PI Agent Installation	1.0.1523

CONNECT to PI Agent