Skip to main content

RCOM Gateway Introduction

The RCOM Gateway is the central automation and integration engine of the RCOM Gateway Suite. It is designed to collect high-volume data from Auto-ID devices and enterprise systems, process that data in real time through configurable workflows, and deliver clean, structured information to the applications that need it.

If the RCOM Gateway Suite is a nervous system, the Gateway is the brain. Coordinating events, managing logic, storing operational data, and orchestrating interactions across your entire environment.

This article gives you a clear understanding of what the Gateway does, the problems it solves, and the concepts you need to know before you explore the rest of the documentation.

Why Organizations Use RCOM Gateway​

Modern warehouses, hospitals, factories, and logistics networks rely on continuous device data - RFID readers, barcode scanners, sensors, AGVs, cameras, mobile devices, and more. These devices produce large volumes of fragmented data that often:

  • arrives in different formats,
  • requires validation and filtering,
  • needs immediate reaction,
  • must integrate with multiple downstream systems.

Traditionally, this leads to complex custom middleware, high maintenance cost, and inconsistent reliability.

RCOM Gateway eliminates that complexity by providing a unified, event‑driven platform with built-in automation tools, storage models, integrations, and monitoring capabilities. Instead of developing custom scripts or services, integrators use the Gateway to visually model logic and centrally manage all device and system interactions.

Core Capabilities of RCOM Gateway​

1. Event-Driven Automation​

Every incoming piece of data, whether from a device, an API call, a map interaction, or a timed job is treated as an event.
Events trigger workflows that:

  • validate content,
  • transform data,
  • check conditions,
  • update objects,
  • push messages to external systems,
  • notify operators,
  • or make decisions.

This event-driven approach allows systems to react instantly to real‑world actions.

2. Low-Code Workflow Engine​

The workflow engine is the heart of the Gateway. Instead of coding backend logic, users design workflows visually by assembling actions into a flow.

Workflows can:

  • extract values from JSON/XML payloads,
  • evaluate conditions,
  • update object groups,
  • call SQL queries,
  • make REST API calls,
  • publish MQTT messages,
  • send notifications,
  • run timers and delays,
  • create files (XML, Excel),
  • and much more.

The Gateway compiles these workflows into optimized execution plans and runs them on a high-performance runtime capable of handling thousands of concurrent events.

3. Digital Twin Storage Through Object Groups​

The Gateway includes a built-in data model called Object Groups, a flexible structure for representing any real-world entity: pallets, orders, assets, equipment, devices, patients, vehicles, containers, rooms, and more.

Object Groups provide:

  • typed attributes (string, number, boolean, date…),
  • custom attributes with predefined values,
  • relationships,
  • access control,
  • soft/hard delete options,
  • audit trails,
  • history tracking,
  • linkability to maps and UIs.

This enables the Gateway to maintain accurate, real-time digital twins of operational entities.

4. Multiple Data Ingestion Channels​

RCOM Gateway can receive data from a wide range of sources:

  • REST API: Custom endpoints allow external systems or mobile devices to send data into workflows. Supports sync/async modes and authentication.
  • MQTT: Ideal for high-frequency IoT or Auto-ID devices. Supports wildcards, QoS levels, and dynamic routing.
  • Scheduler: Allows workflows to run at defined intervals or specific times.

This versatility allows the Gateway to sit naturally inside almost any IT/OT landscape.

5. Custom UI System​

The Gateway includes a built-in UI rendering engine that allows you to create HTML/JavaScript interfaces directly inside the platform.

You can build:

  • dashboards,
  • live monitors,
  • operational panels,
  • vendor portals,
  • mobile-friendly pages.

These UIs can fetch workflow data, subscribe to MQTT updates, and dynamically render objects without needing a separate web server.

6. Custom Maps for Spatial Intelligence​

Custom Maps let you upload layout images and draw zones that represent areas like gates, aisles, storage bins, or hospital wings.

Objects tied to coordinates or storage locations appear live on the map.

This enables spatial logic such as:

  • “Alert when a pallet enters Zone C”
  • “Show equipment currently in Room 14”
  • “Track movement across different zones”

Mapping is especially powerful in logistics, healthcare, and manufacturing.

7. Integration Layer​

The Gateway connects effortlessly with external systems using:

  • REST APIs,
  • MQTT,
  • SQL databases,
  • EPCIS,
  • Webhooks,
  • Custom endpoints,
  • File-based formats (XML, Excel),
  • Mobile devices.

This turns it into a universal middleware layer capable of bridging OT data with enterprise applications.

8. Security, Roles, and Access Control​

The Gateway offers fine-grained permission management:

  • user accounts and roles,
  • read/write/update/delete permissions per module,
  • access groups for scoping data and UIs,
  • external user access for APIs,
  • OpenID support for enterprise authentication.

This enables safe multi-tenant or multi-department deployments.

9. Multi‑Tenant Operation​

The RCOM Gateway supports true multi‑tenant operation, allowing multiple customers, sites, or departments to run on a single platform while keeping their data fully isolated. Each tenant can have its own object groups, maps, UIs, integrations, and user permissions. Access control ensures that users only see the data and tools belonging to their assigned tenant. This makes the Gateway suitable for large enterprises, managed service providers, and multi-site environments that require strict separation without running separate installations.

How RCOM Gateway Fits Into Your Architecture​

The typical flow looks like this:

  • Devices publish scans, reads, sensor values, images, or messages.
  • Agents (optional but recommended) filter, validate, and normalize the data at the edge.
  • The Gateway receives the clean data through REST, MQTT, EPCIS, or scheduled triggers.
  • Workflows process the event using your business logic.
  • Object Groups store and update relevant operational data.
  • External systems receive structured outputs.
  • Custom Maps and custom UIs present the information visually.

This modular structure makes the Gateway adaptable to small single-site deployments as well as large, distributed enterprise environments.

When to Use RCOM Gateway​

Use the Gateway when you need to:

  • automate real-time operational processes,
  • unify data from multiple device types,
  • reduce custom middleware development,
  • digitize assets or equipment,
  • track movements across areas or facilities,
  • build dashboards or operator tools,
  • integrate with ERP/WMS/MES systems,
  • improve consistency and reliability across workflows.

Because the Gateway handles ingestion, automation, storage, visualization, and integration in one platform, it significantly reduces engineering effort and ongoing maintenance.

Where to Go Next