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.

Provide support for Modbus function code 20

As a PI System Admin, I would like to see a confirmation window (acceptation pop-up message), when deleting Interface instances in PI Event Frames Interface Manager. This would minimize the deletion of the instances by error.

Some of the fields incoming from the DCS are user entered and prone to errors. Please allow for the option to include slightly different logics to be able to filter out those user errors (such as empty spaces at the end of the string, etc).

POINDexter application be modified such that addresses beyond 64000 are able to be ‘tested’ / polled, rather than having to configure a tag to read those registers

The newest version of UCOS now supports string tags.  Currently the CSIUCOS interface (1.0.0.22 as of writing) does not support these types of tags.

Customer would like the ability to have PItoPI create a list of tags that includes the FULL name of the source tags, as well as the destination tags they are mapped to.  This will greatly assist in managing tags that are being sent to a remote customer.

Currently, Batch Interface Framework interfaces implement tag template triggers that can trigger whenever a placeholder has any value. These interfaces should also support triggering when a placeholder does not have a value. For example, our SISBatch data source has separate columns for Operation and Phase information. We would like to record the value of the [DESCRIPT] column in a tag only for non-phase batch events (i.e. trigger the tag template only when the [PHASE] placeholder is blank).

For whatever reason, times such as -1w or -1y are not accepted, but times such as -1mo and -1d are OK.

Please make the PI Interface for RDBMS accept the same relative times that other PI programs accept.

For instance, cyrillic characters are not rendered correctly in spite of appropriate regional settings.

When the PI RDBMS Interface gets a bad timestamp from the source RDB that it cannot coerce into a PI Timestamp, the interface attempts to use the current timestamp instead and logs the following error:

"pitm_settime() error - 15002. Using current time."

The interface should instead include an option that controls what to do in this situation. The potential options would be to either discard the event entirely after logging an appropriate error or to use the current timestamp of when the event was retrieved (Also logging an appropriate warning).

I had a case (794719) with a customer who would like to have SNMPTrap interface available on our live library so that he can browse online instead of downloading the user manual.
Thank you!

allow instruction level data to use batch level start time. Add an option to allow this. use case: the instruction level start time is the time when the DOT should be ramped up or down.  The batch start time is a few minutes before that timestamp.  To get the turbines adjusted in time, they need to use the batch start time.  This gives the operator enough time to adjust the set point and have the new target met by the instruction start time.

Most of the problems appear in the FIELD, MSG, and message sections of the INI file. Note the difference in clarity, readability, and length between the current and proposed syntaxes below.

Current syntax:

[FIELD]
FIELD(1).NAME="Tag"
FIELD(1).TYPE="String"
FIELD(2).NAME="Date"
FIELD(2).TYPE="DateTime"
FIELD(2).FORMAT="yyyy-MM-dd"

[MSG]
MSG(1).NAME="MessageSection1"
MSG(2).NAME="MessageSection2"

[MessageSection1]
MessageSection1.FILTER = (MessageSection1 message filter)
(MessageSection1 code)

[MessageSection2]
MessageSection2.FILTER = (MessageSection2 message filter)
(MessageSection2 code)

Proposed syntax:

[Variables]
Tag String
Date DateTime("yyyy-MM-dd")

[Messages]

<(MessageSection1 message filter)>
(MessageSection1 code)

<(MessageSection2 message filter)>
(MessageSection2 code)

The BES/MES sometimes contains recipes with no Procedure, or even Unit Procedure. The Batch Framework Interfaces should allow the creation of only the Event Frame levels that exist on the data source. This would need to be enabled with an interface configuration parameter so the default behavior is not changed on upgrades to existing systems. This enhancement would not be possible when writing to the PI Batch Database.