PI Connectors
Welcome to the
PI Connectors feedback page!
We created this forum to hear your ideas, feature suggestions and feedback on PI Connectors. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.
Please note that your ideas and comments posted here are visible to all other users.
- For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal (https://my.osisoft.com) instead of sharing them on this site.
- For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
-
PI Connector for IEC 60870-5-104 writes 'No Data' or another SYSTEM digital state when connection to the Data Source is lost.
This connector is specially used to monitor the connection of the machines, but if there is a general network crash, and the connector losses the connection to the Datasource, it will stop sending data instead of sending something to alert of the situation.
Not being aware of that situation can cause big impact in the companies.
Receiving a Sytem digital state when the connection to the data source is lost would help to create an alarm and let the people in charge know.30 votes -
Allow specification of PI Point Attributes set by the PI Asset Connector for Emerson DeltaV 3.X
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. These are: PtClassName, PointSource, PtOwner, PtGroup, DataOwner, DataGroup, PtAccess, DataAccess, DisplayDigits, ExcDev, Location1, Location2, Location3, Location5, Shutdown.
So far, it is only possible to adapt them after the PI Point creation (for example by using PI Builder or SMT > Point Builder).
15 votes -
DeltaV Smart Connector Update to OPC UA
The newest release of DeltaV has the capabilities of enabling an OPC UA server that could be used to transmit realtime date from DeltaV to the PI database. Right now, the interface between the two systems uses OPC DA. With DeltaV's plan to migrate to only using OPC UA, Is there a roadmap to update the smart connector such that it uses OPC UA for realtime data transmission? This could allow the OPC UA connector to be placed on the PI data server directly since it is much easier to setup OPC UA connections across physically separate machines (as opposed…
15 votes -
Reduce Number of Point Sources for PI Connector for PI System Health
PI Connector for PI System Health creates a LOT of different point sources for the Pi points it creates on the Data Archive. Some customer may prefer to not have so many point sources show up for one interface/connector. Adding a method to reduce/condense point sources pre-point creation would eliminate to need to edit the point sources manually afterwards.
15 votes -
PI Connector for IEC 60870-5-104: to filter IOAs
Considering the following scenario encountered by the customer:
In IEC-104 data source, there might be 500 signals of single point (type=1, MSPNA1) and 1000 measurements of normalized value (type=9, MMENA1); however the customer would not like to transfer all those signals and measurements into PI system with PI Connector for IEC 60870-5-104.
How to configure the connector to filter them (such as filter them by IOA of signals and measurements)? Just like what can be done with filter file in PI OPC UA Connector?
13 votes -
Further development of OMF
In OMF unfortunately more complex use cases are not possible
Integration of Script functionally for generated elements from OMF are needed. Please insert an possibility or allow an other development method to use all AF functionality in case of generated OMF Elements.10 votes -
Adjust GE e-terraHabitat Connector to support e-terraPipeline systems
The Pi Connector for GE e-terraHabitat systems was apparently only written to support GE's Electrical SCADA systems (EMS/DMS) that are based on e-terraHabitat. They also have Oil & Gas Pipeline SCADA systems, also based on e-terraHabitat, known as "ETPL" (e-terraPipeline), which have a slightly different record structure for POINT and ANALOG records. Both expose their data via GE's SAMPLER technology, which at a basic level works the same for both types of SCADA systems, the difference is in the record structure related to POINTS and ANALOGS that is slightly different for each system.
The existing Pi Connector would need a…
9 votes -
Allow rename of tags for IEC-60870-104 connector
The connector should allow sending the data to a custom tag name. The combination of ASDU and IOA are not useful to end users without the signal list.
There should also be an option to automatically combine the quality flags with the value e.g. if the quality is not valid, then write the quality code to the value
8 votes -
Update PI Interface for Citect Supported Operating System to Windows Server 2019
The latest supported operating system for PI Interface for Citect is Windows Server 2016, with a requirement to upgrade our machines to Windows Server 2019, this interface is the only thing holding us back, the ICU is supported although the interface is unsupported.
7 votes -
Setting of parameters k and w for IEC 60870-5-104
Parameters k (Maximum number of outstanding I format APDUs) and w, cannot be adjusted, while vendors recommend customers to set it to k=12 and w=8
7 votes -
Enable child Event Frames for Alarms and Conditions from PI Connector for Siemens Simatic PCS 7
Would like to see states of alarms captured as child Event Frames of the parent alarm Event Frame that is currently created. Today this data is only captured in tags.
7 votes -
Enable setting tag attributes in MQTT Connector
The MQTT Connector should have ways to set tag attributes. There should be way to set the default compression and exception settings and also other tag attributes like point and data security.
6 votes -
The PI Connector for WITSML should be able to perform history recovery and real-time data collection at the same time
As a PI System Administrator, I would like to configure the data collection mode for the PI Connector for WITSML for each data source so that I can perform history recovery and real-time data collection without having to host multiple installations of the connector on different machines.
Additionally, I would like to be able to update the data collection mode from the Data Collection Manager website instead of having to edit the ConnectorGlobal.config.json file.
5 votes -
Configure PI Smart Connector for Emerson DeltaV 3.x Health Tags
PI Smart Connector for Emerson DeltaV 3.x creates the following two health tags on the PI Data Archive:
DeltaVACtrAssetSyncHealthTag
DeltaVACtrPointSyncHealthTagThe names of these tags are hardcoded, so if I install another instance of the Smart Connector and configure it to create tags on the same PI Data Archive, it will write to these same health tags when reporting the status of a sync. I would like to configure the names of these health tags so my two Smart Connector instances write to two different sets of health tags.
5 votes -
PI Connector for HART-IP / Support SECURE data transfer
I work with an global oil and gas company who is interested in collecting data using the PI Connector for HART-IP but their IT requires them to utilize SECURE data transfer.
The current connector only utilizes STANDARD data transfer.
The lack of this feature is prohibitive to collecting data from a large set of assets and potentially using an optimized PI System architecture.
5 votes -
Option to set Client_ID parameters in MQTT SparkPlug Connector.
We need to have an option to set the Client ID parameter.
We need an option to set the starting set of the characters of the parameter to have the possibility to use the fixed text "cva::" before a random number.
Thanks5 votes -
PI Connector for HART-IP: Remove UoM from being added to PI point "descriptor" attribute
Currently, the connector applies the UoM to the PI point "descriptor" attribute. If I want to write in a custom descriptor, every time I restart the connector, I then need to re-edit all of the points.
4 votes -
Discrimnate meta data changes of source items picked by PI Connector for IEC 60870-5-104
We would like to discrimnate when the meta data around the data item changes on the source. The digital states related to it, the description, etc. If these change, the connector will change them on our PI server.
Currently PI Data Archive.does not discriminate it just blows away the current configuration and reloads everything from the source overwritting our custom changes.
4 votes -
PI Connector for Siemens SIMATIC PCS7 Alarm and Conditions backfilling support
In case of an interruption, the PI Connector has the current capability of backfilling any tag data from the source OpenPCS 7 system.
Condition data leading to PI Event Frame creation from the connector should also support similar backfilling capability to avoid data loss.
4 votes -
IEC61850 encryption
Implement TLS encryption between the IEC61850 Connector and the target IED(s) as per TS 62351.
4 votes
- Don't see your idea?