PI ICU rejects options IGNORE5TH and IGNOREFLDMSEC at the same time. When modeling teams change MEAS fields often, IGNORE5TH is extremely useful to keep data history contiguous. When using field time that is stamped by the EMS, milliseconds are not useful.

Please remove the constraint on having both options.

Add OMF health function to Citect interface.

Currently the PI Buffer Subsystem only has the capability to speak directly with the Data Archive. This setup can have a negative impact on your Cyber Security setup as you are not able to leverage the DMZ between the IT/OT networks as it is designed.

This request is to allow the PI Buffer Subsystem to communicate with another buffer subsystem to act as a relay to the data archive and would allow all cyber security requirements to be met.

The counter path of NVidia's GPU temperature is \computername\NVIDIA GPU(#0 Quadro M4000 (id=1, NVAPI ID=1280))\Temperature C.

Enhance the PI Perfmon interface to accept the counter path if the first character after the first bracket is a "#".

When a phase end event is received at the same time as a phase start event, the WWInBatch interface currently creates batches/event frames of zero duration despite there being phase state events under the phase event.
It would be helpful if the interface logic is updated so that either:
the phase end time is updated to the timestamp of the most current phase end event
or ignore phase end events that happen at the same time as phase start events.

PI Buffer Subsystem must have a option to set up the user account is logged instead of using Windows Domain or Local account that is running the windows service. This is a huge security issue when using Buffer on client computer to send manual data because you will need to create a Mapping or Trust and give permission in so many pi points when the user logged on computer should have access to write in few pi points.

Please prioritize this one!

Batch Framework Interfaces currently do not support two byte languages. Please add support of two byte languages to batch interfaces.

Emerson has a new PK Controller based DCS available (in lieu of full blown DeltaV). This new device is contained with OPC-UA and Batch Exec/Historian. We want support for the existing EMDVB interface to supply S88 based batches into PI Event Frames and/or PI Batch. Additionally, we will want to run the PI OPC-UA interface to get the live module data into PI tags. Do you have support for this today?

whenever the OPC server undergoes any restarts or configuration changes, the OPC interface will delete all old connections, groups, etc. and it will establish a new connection to the OPC server, loading all ItemID's etc (as if it is an automatic restart of the interface).

The reason for this enhancement request:
if OPC server is restarted or undergone configuration changes, all the handles and subscriptions for advise tags are not valid anymore. The interface would get the advise values in an inconsistent manor (values betwen the OPC server and the interface would show a mismatch)

Add an option to encrypt trafic between interfaces/connectors and the PI Data Archive

We are using this interface to capture meter attributes and measurements. However, the voltage comes in the XML files as an "instrumentation value", which is not currently supported. We would like to bring the voltage into a tag for the meter to use in PI analytics.

When our EEAMAS Interface was originally implemented, the HeadEnd parameter was set to "Elster", the vendor name for our meters. So all of our meters from that interface are named Elsterxxx. Elster was purchased by Honeywell, so the name no longer makes sense. We would like to change our prefix for the elements to something more generic like "MTR", since the element name is something that is exposed regularly to end users.

EMBVBCS currently does not bring in UOM from source files to the interface.

Allow for monthly scan intervals for scan classes. i.e. "scan monthly on the first hour of the first day of every month".

When using a single PI tag, the fields are delimited by the pipe (|) symbol by default.
It would be useful to change it to another delimiter or a combination of others. There could be messages containing this pipe (|) symbol, which would make it difficult to split the fields afterwards.