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.18 votes
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.
Support the concept of time ranges / events EFs / spans as a pre-defined type in the OSIsoft Message Format (OMF) spec.10 votes
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?