Welcome to the Open Message Format Specification 2​.0

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 supports the transmission of time-series data as well as enriched information such as contextual data, asset representations, and events, enabling more expressive and structured data exchange.

OMF enables the creation of data acquisition and data publishing applications on platforms and in programming languages that do not support AVEVA libraries. This adaptability permits producers to build messages that consistently communicate measurements, context, and associated metadata across different platforms.

OMF does not specify or rely on any particular binary message protocol such as gRPC, AMQP, or Kafka. Instead, it is based on an abstract message format in which a message consists of a collection of key/value pairs, referred to as headers, together with a payload, referred to as the body. This abstraction allows OMF messages to be created and transported using any messaging protocol that supports headers and bodies.

The currently supported transport options are JSON (format), Gzip (compression), and HTTP (transport protocol). For more information on the ingestion endpoints currently supported by AVEVA systems, consult the CONNECT data services or Edge Data Store 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.