Data services feedback portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about CONNECT products and services. All of the feedback you share here is monitored and reviewed by the CONNECT product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for CONNECT data services. For links to our other feedback portals, please see RESOURCES below.

ADD A NEW IDEA

Clear

Ideas

Showing 33 of 696

OMF: Swagger Specification

I think it would be beneficial to have a Swagger Specification for OMF similar to what currently exists for the PI Web API. As a programmer, I would like to be able to reduce startup time by having a pre-existing libraries that allow me to reduce ...
Guest about 3 years ago in Developer Resources / Open Message Format (OMF) 1 Declined

OMF: Binary data format support

Provide a binary data format option in addition to JSON in the OSIsoft Message Format (OMF) spec.
Guest about 3 years ago in Developer Resources / Open Message Format (OMF) 0 Declined

OMF: Ability to patch data messages

Add the ability to provide partial information for an existing data point. This is meant as a partial update which replaces values for some properties of a type without affecting others.
Guest about 3 years ago in Developer Resources / Open Message Format (OMF) 0 Planned

OMF: the possibility to set/create security settings (groups …) by using OMF

After creating Elements and Tags in AF by using OMF standard, I don´t want to manually configure security settings in AF. The possibility to set/create security settings (groups …) by only using OMF standard would be very helpfull.
Guest about 3 years ago in Developer Resources / Open Message Format (OMF) 0 Declined

More control on MQTT parameters on the AVEVA Adapter for MQTT

It would be nice to have more control on additional MQTT parameters for the AVEVA Adapter for MQTT. We are especially interested in having control on the QoS of the subscription. Setting this would give us more control in buffering, especially whe...
Guest 11 months ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

Allow MQTT adapter to parse timestamps in local time without specifying a timezone suffix to each timestamp

We would like the MQTT Adapter to be able to interpret timestamps in local time without needing to explicitly state the timezone or UTC offset in each timestamp, but for the adapter to always interpret the timestamps as being in a specific timezon...
Guest about 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

OMF should accept the use of special characters like / : @ ! + % < > ( ) when writing to PI WebAPI OMF endpoint

The OMF 1.1 spec does not allow certain special characters that are indeed accepted in the PI Core system like these here: / : @ ! + % < > ( ) When OMF is used to write to PI Core via the PI WebAPI OMF endpoint, this hinders the migration p...
Guest about 3 years ago in Developer Resources / Open Message Format (OMF) 0 No status

Improve throughput

I am not sure if this is a limitation connected to the OMF, WebAPI, or https itself, but in the manual it is given that the maximum message size is 192KB. I am aware that compression is recommended and applied by default by the adapters. For the r...
Guest over 2 years ago in Developer Resources / Open Message Format (OMF) 0 No status

Access Adapter configuration via cloud (read files from edge)

Browse device(s) view/update configuration for a device verify configuration naming updates - typo, change to naming customize for site specific scenario Push updated configuration
Glenn Moffett about 1 year ago in Software Management / Edge Management Integration 0 No status

Include information from Json body in the stream name created by the MQTT Adapter

As a system admin I would like to send mqtt messages from multiple devices to a single topic on an mqtt broker. Each message would contain data for the device along with a field to say which device the data has come from. Then I would like to use ...
Guest about 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status