For a PI tag with a specific scan class, if no new value is collected by the PI Interface after a period of time (for example 2x the scan class) , the interface will add automaticaly the value "No Data". It will avoid the usage of a dedicated analyze for this, in the PI Server. And like that, the PI user will be aware of the issue, by using any PI Visualization tool.

My OPC server's items have the OPC server node name included in the itemID, for example: serverA.AB_1234.PV. I have redundant OPC servers and redundant interfaces (in failover) and would like the tags to refer to the correct OPC address including when the OPC servers fail over. Currently the workaround is to create two sets of tags, each pointing to one OPC server's itemIDs in their instrument tags and then merge the data with AF or a PE.

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

Smart Connector foo DeltaV should let user configure some default attributes for tags created:
- User should be able to define what the default point security should be
- User should be able to decide if tags should be created as Poll or Advise

Currently, the interface does not have any means to convert timestamp values (i.e. not the actual timestamps corresponding to values), such as InstructionStart, to account for timezone differences.  Therefore, the timestamps have to be manually adjusted to account for timezone differences once it reaches the archives. 

Having to manually adjust the timestamp causes issues further down the line, such as with PItoPI, and creates unnecessary overhead in AF to do said conversion.

The IEEE specification of the IEEE C37.118 protocol does not specify if analog data should be singed or unsigned for 16-bit integers. The currently the PI Interface for IEEE C37.118 represents these values as exclusively unsigned. Both types should be configurable in the interface

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.

As a PI Admin, I may have already created a AF Element Hierarchy corresponding to my BES or MES source data. Therefore I have no need for the interface to create a new AF Elements and I would like to suppress this completely.

We noticed that changes to the configuration of newer interfaces / connectors like
- PI EMDVBCS interface 4.0
- PI inbatch interface
- PI Connector Wonderware Historian
are no longer recorded in the PI Audit trail. (see also TechSupport Case # 937205)
This is a compliance issue for the regulated industries.

Add support for BACnet Setpoint objects in the PI BACnet interface.

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

My device only supports SubscribeCOV, but the PI Interface for BACnet only supports SubscribeCOVProperty. I would like the PI Interface for BACnet to support SubscribeCOV like the PI Connector for BACnet already does.

Currently only POINT/ANALOG fields support COUNT. This request would be to enhance the interface to additionally support the COUNT field.

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.