Open Message Format Specification

The Open Message Format (OMF) specification defines a set of message headers and bodies that can be used to generate messages for ingestion into a compliant back-end system.

OMF can be used to develop data acquisition applications on platforms and in languages for which there are no supported AVEVA libraries.

OMF does not specify or rely on any specific binary message protocol such as HTTP, AMQP, or Kafka. Rather, it is built on an abstract message format where a message includes a collection of key/value pairs known as headers, along with a binary payload referred to as the body. As a result, OMF messages can be created using any messaging protocol that supports headers and bodies.

For up to date information on the specific binary protocols currently supported by AVEVA systems, consult the CONNECT data services, PI Web API, and Edge Data Store (EDS) documentation.

Note: All definitions within this document, including keywords and enumerated values, are considered case insensitive. The case sensitivity of any user-provided values is governed by the regulations of the back-end system.