Skip to main content
IronKernel
Products Solutions For Customers About FAQ Contact
IronKernel Platform

YMS: Device Gateway

Hardware devices (OCR cameras, RFID readers, truck scales, reefer units, sensors, kiosks, gate arms) register through a unified API with auto-generated API keys.

Problem

Hardware devices (OCR cameras, RFID readers, truck scales, reefer units, sensors, kiosks, gate arms) register through a unified API with auto-generated API keys.

Capability

Hardware devices (OCR cameras, RFID readers, truck scales, reefer units, sensors, kiosks, gate arms) register through a unified API with auto-generated API keys.

How it works

  1. 1 Device gateway now enforces registration lifecycle, heartbeat checks, command dispatch, and fault-to-work-order automation.
  2. 2 Fault telemetry from devices is routed into CMMS and audit-ready operational event streams.

Operational outcomes

  • Device gateway now enforces registration lifecycle, heartbeat checks, command dispatch, and fault-to-work-order automation.
  • Fault telemetry from devices is routed into CMMS and audit-ready operational event streams.

Integration boundaries

  • Ownership Realignment Program (Crew + CMMS)
  • Crew Integration Summary (Mirrored)
  • Sites & Zones

Proof model

Feature-level proof

  • Device Gateway scope is defined in product module catalog.

    verified

    docs/products/yms/product.md · Module Catalog > Device Gateway

  • YMS gate operation execution is implemented with dedicated gate rule modules and geofence-ready integrations.

    verified

    docs/products/yms/product.md · Module Catalog > Gate Operations

    Code: backend/services/yms/internal/modules/gates

    Contract: proto/yms/gates/v1

  • YMS gate execution is implemented in dedicated gate modules.

    verified

    docs/products/yms/product.md · Module Catalog > Gate Operations

    Code: backend/services/yms/internal/modules/gates

    Contract: proto/yms/gates/v1

Solution routes that reuse this feature

Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (1).