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 58 of 727

    versioning/version control to enable

    Customer was making changes and wanted to save the previous version in case the updates were not what they wanted/error.
    Glenn Moffett about 1 year ago in Assets & Metadata Rules / Asset Rules 0 No status

    Asset Hierarchy that changes over time

    Be able to specify hierarchical parent/child relationships between assets that also support these relationships changing over time for mobile Assets that get deployed to different locations.
    Guest over 3 years ago in Assets & Metadata Rules / Assets 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 over 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

    Create stream metadata and asset rules across namespaces

    Challenge: We have split our AVEVA Data Hub tenant across different namespaces as of data residency requirements. However, the naming conventions of our tags across the company has been standardized. We would like now to use stream metadata and as...
    Guest almost 2 years ago in Assets & Metadata Rules / Metadata Rules 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 over 1 year ago in Software Management / Edge Management Integration 0 No status

    OMF: Property Bags

    Allow reuse of a set of properties for multiple type definitions in the OSIsoft Message Format (OMF) spec.
    Guest over 3 years ago in Developer Resources / Open Message Format (OMF) 0 No status

    GitHub samples need updates for OMF 1.2 spec with PI Web API

    OMF 1.2 specification have been out now.However, the current samples for OMF w/ PI Web API (BasicAPI, ComplexDynamic and Bart Ingress ) only feature OMF 1.1 versions.PI Developers will need OMF 1.2 samples in GitHub so that they have a reference t...
    Guest over 2 years ago in Developer Resources / Open Message Format (OMF) 1 No status

    Community Driven Asset Views

    Enable a way for people across different companies to collaborate together with the goal of defining standard Asset Views/Shapes for different types of assets (pumps, steam turbines, tanks, etc.) that can be published and used by all customers SO ...
    Guest over 3 years ago in Assets & Metadata Rules / Assets 0 No status

    Improve Asset Rule Flexibility - Accommodate Stream with Segments with two purposes / overlapping token strings

    The ability to derive multiple tokens from the same overlapping strings. Requirement: From the example stream name “PIDAHou_Flow.PV”, we need to be able to derive the following asset ID and metadata information. Asset ID: ”PIDAHou” Asset prope...
    Guest over 3 years ago in Assets & Metadata Rules / Asset Rules 0 No status