PI Interfaces
Welcome to the PI Interfaces feature suggestion box. We created this forum to hear your ideas, suggestions and feedback.
Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.
- NOTE: for bugs, please report to OSIsoft Tech Support at https://techsupport.osisoft.com/My-Support/My-Cases/New/ rather than entering them on this site.
- NOTE: for documentation feedback and bugs, please report to Documentation@osisoft.com rather than entering them on this site.
-
Provide localized versions of PI ICU
For instance, cyrillic characters are not rendered correctly in spite of appropriate regional settings.
1 vote -
Modifying the functionality of Trend Advise feature for PI OPC interface
As a PI OPC Interface user I would like to get step-like trends whenever that the Trend Advise parameter is enabled (even with having large exception and compression deviations that filter some of the events) so that I don't need to enable the step attribute for each PI tag.
1 vote -
Option for PI Interface for UFL to purge read-only files
Create an option to allow the PI Interface for UFL to delete files with the read-only attribute.
1 vote -
Offset timestamps send by PI Interface for Environmental Systems Corp StackVision
Please allow the option to offset data sent by the interface. This will enhance the ability to compare time stamps between data sources and the PI Server in different timezones.
1 vote -
DNP3: add functionality to allow outputs
DNP3 - add functionality to allow outputs for binary and possibly other object groups/variations.
1 vote -
Please add a DAYOFWEEK function to the UFL interface
Can you please add a DAYOFWEEK function to the available functions in the UFL interface.
This will greatly assist with the handling of daylight savings transitions (e.g. first sunday in April) as there is currently no easy way of determining the current day of week.
Function should take a DateTime and return an integer (i.e. Monday=1, Tues=2 etc)
1 vote -
Create a clearer, shorter INI file syntax
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)1 vote -
Batch Framework Interfaces - Allow creation of only the Event Frame levels that exist on data source
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.
1 vote -
Always use arc_append when archiving data using SIPowerTG interface
This is the interface from the Siemens Power TG EMS system. The problem is with the saving of Alarm and Event text messages. There are instances when the data files are produced out of order. When data is sent out of order the interface seems to go into arc_noreplace mode and our data is lost.
To store Alarm and Event messages, the duplicate record check is turned off so there is no way to overwrite data, therefore the arc_noreplace is a meaningless protection. Data will never be over written.1 vote -
UFLDesigner should aid with visualizing the flow of control through the INI file
Currently, the UFLDesigner is focused on helping the user add content (variables, filters, actions, etc.) to the INI file. However, the UFLDesigner does nothing to help the user understand the interaction between these components.
Rather than having the 5 tabs on the left pane, the UFLDesigner should be rearranged to show the flow of control through the INI file, perhaps as a programming loop. Then the user can add content to the skeleton loop.
The loop arrangement would also help the user debug the INI file, since now the loop can be stepped through, line by line, showing the value…
1 vote -
PI UFL Interface - create selected tags using EnablePointCreation parameter.
Customer noticed that tags can be created automatically, but he does not want to create all of the tags autmatically, but select which tags will be created. He wants to be able to select which tags will be created and which won't.
1 vote -
Enhance OPC server failover capability
Need to trigger failover when a watchdog tag is stale for a configurable duration.
1 vote -
When Citect Interface loses connection to a device, throttle errors relating to failed tag reads
OSI PI Citect Interface
The interface will log an entry to the message log for every tag that it can't source data for. This is fine for a small number of tags that have not been able to read data from Citect. However, when a Citect Unit (eg PLC) goes offline and there are thousands of tags assigned to that unit, every single tag that is scanned is logged with the same message generating thousands and at times hundreds of thousands of log entries in a short time frame, eg every second. This results in a very, very large log…
1 vote -
Clarification on InstrumentTag attribute
If you use IntrumentTag for the query, it has to be a file containing the query, not the query itself.
You can specify the actual query in Exdesc.1 vote -
Provide the option of specifying an output file path for the processed files that is different than the input file path
Allow the user to specify an output file path for the processed files that is different than the input file path, moving the files to this "output" path after they are processed.
Note: This was previously Enhancement 100038.
1 vote -
Create a new function indicating if the string can be turned into a number
Create a new function indicating if the string can be turned into a number. For example, IsNumber() function could return 1 if the string can be turned into a number 0 if not.
1 vote -
OPC HDA Interface: Add a health digital tag for each scan class to indicate when HR is occurring versus realtime for that scan class
Add health digital tags for each scan class to indicate when HR is occurring versus realtime for that scan class. This would indicate when the interface is performing HR for the scan class and when it switches to realtime collection.
1 vote -
Batch Framework Interfaces - Support filtering by whitelisting
As a Batch Framework Interface user, I would like to filter my batch data by whitelisting. Currently the only option is blacklisting. This is inconvenient, for example, if data is only desired from a few units. Each time a new unit is added to the data source, the interface configuration must be updated.
0 votes -
PI EFGEN Interface -- Allow the "time true" fuction for EFGen
in order to eliminate unwanted or noise event which be triggered and recovered in a short period.
0 votes -
PI PerfMon tags to support Timestamp DataType
There are some performance counters that are Date and Time based.
PI PerfMon tags have to be configured as Float32 or Int32 and at PI AF it has to be converted by using PI Analysis or Formulas. Would be easier to configure, maintenance and to build reports if there is a direct way.
0 votes
- Don't see your idea?