Hi all,
 
i got to know this standard:
Standards – SiLA Rapid Integration
This standard is a really good approach to connect various types of lab equipment. Over it it is possible to fetch for example the RPM of a mixing device, temperature of a heater etc.
For my understanding, this screams loudly for a time series recorder with analytic options.
 
Thanks for your support
Thorsten

Right now PerfMon only supports ArcNoReplace. PerfMon has a history of failing over if a server is unreachable. And since PerfMon only supports Hot failover, every time it fails over the new interface tries to write values that the old one already wrote. I would like to be able to specify ArcNoReplace so I don't get an error flood every time the interface fails over.

Currently DNP3 outputs are done one event at a time. We could improve performance by either supporting multiple DNP messages per TCP packet or multiple analog output commands per DNP message.

Currently the ODBC connection is configured with a SQL date time parameter when retrieving the TS parameter (snapshot time stamp).
Due to the fact lots of sources system having more precision in their time stamps, it makes it hard to compair source time stamp to the pi time stamp (precision and rounding issue in SQL).
I request to add support for sql datetime2 into the ODBC connection, or an option to read the time from the snapshot in seconds since 1.1.1970

Having the support of the PI Annotations in the PI-to-PI Interface.

1. Having the capability of acknowledging the message in the PI Buffer GUI and removing the "red flag" when messages acknoledged.
2. Having the Buffer updated automatically when a tag is renamed, without having to restart the buffer.

We see a data gap in one PI Data Archive after the machine hosting the PI-to-PI interface was one hour in the future. In this case, the buffer disconnected from the machine when the issue happened, The buffer did not work correctly and there was a data gap in the target server.

/fd parameter is only used while performing real-time scan. If scan rate is set to a higher value such as a day, the user would need to wait for the first scan (after a day) to get future data. This should be done at interface startup. For use case see notes for Case # 895278.

I would like the ability for the PI Interface for OPC DA to retry writing data when it receives a CONNECT_E_ADVISELIMIT error. Certain OPC servers return a CONNECT_E_ADVISELIMIT error when write requests are received in quick succession, and having a setting to retry writing the data would be better than the current method of performing a restart of the service. The issue is exacerbated when the network is unstable.

Add the YouTube help videos that exist on the OSIsoft Learning channel to the "Help" section of ICU. For example, the UFL designer YouTube videos would appear alongside the corresponding documentation that should be accessible from ICU > Help > Interface Manual...

The PI Interface for Quindar SCADA should have an option to log all values and timestamps from the data source (Prior to any processing by UniInt) for a specified PI point.

I have a scan-based output point writing multiple PI values to the relational database as described here:
https://livelibrary.osisoft.com/LiveLibrary/content/en/int-rdbms-v4/GUID-1A194D2B-388B-4FD7-8B82-D85EDDBBC572

I would like to perform history recovery for such an output point, but this is currently not possible because the output point is scan-based:
https://techsupport.osisoft.com/Troubleshooting/KB/KB01139/

Since event-driven tags can have only one source tags, I cannot recover historical data from multiple PI tags with only one output tag.

For the SNMP Interface, the suggestion would be to have the interface output a .txt file that includes the SNMP devices that have lost connection with the interface. This could be useful when there is a high volume of SNMP devices that connect to the interface.

The health point names for the Read_Only 1.6.8.1 SNMP Interface have a different naming convention than the health points for Read-Write SNMP Interface 1.5.1.306. In order to keep monitoring consistent across version upgrades, the suggestion is to keep naming convention of the health points the same across versions.

PI EMDVB interface stops because of time difference between SQL and PI servers:

"Error, SQL Server is ahead of PI Server more than 30 seconds, please adjust clocks. "

That means we should adjust the (SQL server) DCS clock. However 30 seconds seems a short time to me.

I would like the PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

Several PI Interfaces that previously only had read-write versions (e.g. OPC DA, SNMP) now have read-only versions to help protect the data source from unintended or malicious edits.

We need the same for the PI Interface for RDBMS. Since the PI Interface for RDBMS already comes in 2 versions (32-bit and 64-bit), we will now have 4 versions. The documentation must be clarified so that the user knows exactly which install kit to download.

Currently if you attempt to create a service for a UniInt interface without a service ID you get an error message "Unknown Error" (see attached screenshot)

Generally review and improve error messages to be meaningful but also allow the creation of services without service IDs if the user wishes.