DOCSEARCHbyAlgolia
Submit Docs

RCOM Gateway Documentation

website·Indexed 30 days ago

https://docs.rcom-gateway.com

An event-driven automation platform for building dynamic workflows and exchanging data with external systems via REST APIs and MQTT messaging. The documentation covers workflow management, EPCIS 2.0 standards, role-based access control, and system administration for versions 3.8 and 3.9.

Tokens
145.2K
Snippets
370
Records
1.1K
Agent score
47%

What's inside RCOM Gateway

  1. Overview of RCOM Gateway Event-Driven Architecture

    The RCOM Gateway uses a fully event-driven architecture where every action—such as tag reads, barcode scans, sensor updates, API calls, or UI interactions—is treated as an incoming event. This model ensures low latency, predictable behavior, and high scalability by normalizing all incoming data into a unified internal event format and processing it asynchronously.

  2. Overview of RCOM Gateway Custom Map spatial intelligence

    Custom Map is a feature in RCOM Gateway (v3.8) that integrates spatial awareness directly into the platform. It allows users to upload layout images (such as floorplans or warehouse maps), define visual zones, and link operational logic to specific physical areas. This eliminates the need for external GIS tools or manual coordinate mapping by allowing teams to overlay zones (e.g., 'Cold Storage' or 'Packing Area') on a custom floorplan and trigger automated workflows based on zone transitions (entry, exit, or updates).

  3. Overview of RCOM Gateway Import Process

    Imports allow a developer to apply configuration from a ZIP package (created via Exports) to a target RCOM Gateway. The process is designed to separate validation from execution: uploading a package creates an import job, which generates a preview for review and resolution of errors before any changes are actually applied to the Gateway.

  4. Overview of RCOM Agents

    RCOM Agents are lightweight edge-side software components used to connect Auto-ID and IoT devices (such as RFID readers, barcode scanners, BLE signals, and sensors) to the RCOM Gateway or custom middleware. They are responsible for collecting, filtering, normalizing, and securely forwarding real-time device data for event-driven automation. Agents are centrally managed via the RCOM Gateway, allowing administrators to register, configure, update, and monitor edge operations across multiple sites from a single interface.

  5. Overview of RCOM Gateway Workflows

    In RCOM Gateway, a workflow is a dynamic sequence of actions executed in response to events such as device readings, API calls, or scheduled triggers. Workflows are used to transform raw event data into automation, enabling integrations with external systems, databases, and notifications. Common operations include extracting/transforming input data, triggering REST or MQTT calls, modifying platform database records, and sending alerts or emails.

  7. Overview of External Storage Providers in RCOM Gateway

    RCOM Gateway allows attachments and file-based data for Object Groups to be stored outside the main Gateway database using external storage backends. This is used to prevent database growth, support large file volumes, and integrate with customer-managed cloud or on-premise storage.

    Supported provider types include:

    • Database: Internal Gateway storage mechanism.
    • Amazon S3: Amazon S3 buckets.
    • Azure Blob Storage: Azure Blob Storage containers.
    • S3-compatible storage: Systems such as MinIO, Ceph, or Wasabi.

  8. Overview of the RCOM Agent Process Template Designer

    Process Templates are visual, no-code blueprints used to standardize edge operations (RFID readers, sensors) across multiple RCOM Agents. A template defines the data capture flow, local processing, and final destination. To access the designer, navigate to Agents > Process Templates and select Create template.

  9. Overview of RCOM Gateway Access Control Model

    RCOM Gateway manages system security using a three-dimensional access control model that defines who can access the system, what actions they can perform, and where those actions are applicable:

    1. Users: Individual accounts (email/password) representing the person accessing the system.
    2. Roles & Permissions: Collections of permissions that define the actions a user can perform (e.g., 'Viewer' for read-only access vs. 'Admin' for modifying settings).
    3. Access Groups: Logical or physical boundaries (zones) that restrict where a user's permissions apply (e.g., restricting a manager's access to a specific warehouse).

  10. Overview of the RCOM Gateway Event Scheduler

    The Event Scheduler allows RCOM Gateway to trigger workflows based on time instead of device events or external API calls. It generates internal, time-based events that enter the standard ingestion pipeline. This is used for periodic tasks (daily reports, system cleanups, audits), one-off actions, or maintenance routines that lack a corresponding device event.

  11. Overview of the RCOM Gateway Event Scheduler

    The Event Scheduler allows RCOM Gateway to trigger workflows based on time (daily, hourly, or one-time) instead of device events or external API calls. It generates internal time-based events that enter the standard ingestion pipeline. Use the Scheduler for periodic tasks like daily reports, system cleanups, audits, or maintenance routines that lack a corresponding hardware device event.

  12. Overview of RCOM Gateway Custom Map

    Custom Map is a spatial intelligence feature in RCOM Gateway (v3.9) that allows users to upload layout images (such as floorplans or warehouse maps) and define visual zones. This enables teams to overlay operational areas (e.g., Cold Storage, Packing Area), view objects associated with specific zones, and trigger automated workflows based on zone transitions (entry, exit, or updates) without requiring external GIS tools.