In telecom and operational technology, engineers describe a device's connections by compass direction. The north-bound interface is the side that faces upward, toward higher-level enterprise, management, or cloud systems, while the south-bound interface faces downward toward the field equipment. The convention borrows from network diagrams, which conventionally place higher-level systems at the top of the page. A gateway, plant historian, or SCADA server uses its north-bound interface to publish aggregated data upstream to whoever needs it.
North-Bound Interface in one line: A north-bound interface is the upward-facing connection of a device or system that exposes data and control to higher-level enterprise or cloud platforms. In SCADA it is how a gateway or historian pushes field data toward management systems, typically over REST, MQTT, or OPC UA. It is the counterpart to the south-bound interface, which faces the field devices.
The north and south naming comes from layered architecture diagrams, where higher-level systems are drawn at the top and lower-level infrastructure at the bottom. A component in the middle, such as a gateway, has a north-bound interface pointing up to the systems that manage or consume its data, and a south-bound interface pointing down to the devices it controls or polls. The terms are relative to the component, not absolute, so a system that is north-bound to one layer can be south-bound to the layer above it.
This directionality also tends to describe data flow and authority. Data usually aggregates as it moves northbound, becoming coarser, more summarized, and more business-oriented at each level. Commands and configuration often flow southbound, becoming more specific and device-level as they descend. Understanding which way a given interface faces tells you whether you are looking at the reporting side or the field-control side of a component.
The convention is common in telecom network management, where a network element exposes a north-bound interface to the operations support system. Industrial automation borrowed it because SCADA and IIoT architectures have the same layered shape, from field devices up through gateways and SCADA to enterprise and cloud.
A north-bound interface publishes data in forms the upper layers can consume without needing to know anything about the field protocols underneath. Common choices are a REST API returning JSON, an MQTT feed publishing tag values to a broker, or an OPC UA server that enterprise clients can browse and subscribe to. The interface hides the Modbus, DNP3, or vendor-specific complexity below it and presents a clean, standardized surface upward.
Beyond raw values, a well-designed north-bound interface exposes structure: named tags, engineering units, quality flags, timestamps, and often a model of the assets the data describes. This is what lets an enterprise dashboard or analytics tool make sense of a reading without a lookup table of register addresses. The north-bound side is where field data becomes information that business systems can act on.
It is worth distinguishing a north-bound interface from a generic API. Any API is a programmatic surface, but calling something north-bound specifically says it faces the higher layers of a layered architecture and carries data upward. The term communicates position and direction, not just that an integration point exists.
In a cloud SCADA architecture, the north-bound interface is how field infrastructure feeds the cloud. A plant gateway or edge historian collects readings from devices on its south-bound side, then publishes them northbound to a cloud platform or a unified namespace. The cloud becomes the shared upper layer that every site reports into, and the north-bound interface is the pipe that carries each site's data there.
For dispersed operations this framing keeps integration clean. Each site's gateway has one job on its north-bound side, publishing to the platform over a standard protocol such as MQTT or REST. The platform does not care how many devices sit below any gateway, only what the gateway publishes upward. Adding a site means standing up another gateway with the same north-bound behavior, not redesigning the enterprise integration.
Merobix, as cloud SCADA for oil and gas and other industries, sits at the top of this north-bound flow. Field gateways publish upstream into the platform, which then re-exposes the data through its own north-bound APIs to dashboards, ERP systems, and analytics. The compass metaphor makes the whole chain legible: field devices at the bottom, cloud at the top, each layer publishing northbound to the next.
Every north-bound interface is a kind of interface or API, but the term adds direction. Calling it north-bound says it faces the higher layers of a layered architecture and carries data and reporting upward, toward enterprise or cloud systems. A generic API could point in any direction; north-bound specifically means upstream.
North-bound faces up toward higher-level management, enterprise, or cloud systems and usually carries aggregated data upward. South-bound faces down toward the field devices and usually carries commands and configuration downward. The two are opposite sides of the same middle component, such as a gateway or SCADA server.
It depends on what the upper layer expects, but common choices are REST over HTTP with JSON, MQTT publishing to a broker, and OPC UA for browsable, subscribable data. The point is that the north-bound side speaks something the enterprise or cloud can consume, hiding the field protocols beneath it.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.