OSIsoft Message Format (OMF)
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.
-
OMF: Data Quality Support
Add a data quality keyword to the OSIsoft Message Format (OMF) spec and allow specification of a data quality format.
13 votesPlanned for OMF 1.2
-
OMF: Digital State Tags
Would it be possible to adapt the PI WebAPI and OMF to accept digital state tags? For example, 0,1,2,3,4 which can be mapped to named values “open”, “closed”, “half”, “fault”, etc?
4 votesThis feature is planned for OMF v1.2. See “enum” Types
-
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.
4 votesPlanned for OMF 1.2
-
OMF: Per-object CRUD operation override
Add the ability to override the message-level CRUD mode for each object (Type, Container, or Data) within the body.
1 votePlanned for OMF 1.2
-
OMF: Container-level overrides
Ability to override Type-level property keywords on a Container level.
1 votePlanned for OMF 1.2
- Don't see your idea?