OSIsoft Message Format (OMF)

← User Feedback for OSIsoft Products and Services

Welcome to the OSIsoft Message Format feature suggestion box. We created this forum to hear your ideas, suggestions and feedback. For more information on OMF, please refer to: http://omf-docs.readthedocs.io

Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.

Please note that your ideas and comments posted here are visible to all other users.

  • For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal  (https://my.osisoft.com) instead of sharing them on this site.
  • For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.

How can we improve OSIsoft Message Format?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Send only data that has changed.

    When transferring data via satellite it is necessary to keep bandwidth usage to a bare minimum. Currently OMF must send all values regardless of whether they have changed or not. If it could send only the data parameters that have changed that would be very helpful.

    17 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
    NEEDS MORE DISCUSSION  ·  AdminKevin Geneva (Admin, OSIsoft) responded

    Since OMF is just a specification that can be used to create data acquisition applications, it does not seem appropriate to add this feature here. However, I am curious, what are the roadblocks from introducing this rule into your application? OMF does not control what gets posted and what doesn’t, but an application could introduce a register for the last value sent and compare that to the current value before posting or ignoring the data.

  2. OMF: Time Range / Events / Spans Support

    Support the concept of time ranges / events EFs / spans as a pre-defined type in the OSIsoft Message Format (OMF) spec.

    9 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
    NEEDS MORE DISCUSSION  ·  AdminChris Felts (Product Manager, OSIsoft) responded

    For the spans implementation, let’s consider implications on PI, OCS and EDS. E.g. how does the data source represent spans and/or how does the OMF application recognize these spans? Who / what uses the span data? How does the thing using the span data represent a span and associated data? Do we have scenarios with non-time based spans for OCS and EDS?

  • Don't see your idea?

OSIsoft Message Format (OMF)

Categories

Feedback and Knowledge Base

(thinking…)
Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED