Overview #
Raw Message Streaming (RMS) is a high-performance data delivery solution designed for large enterprise customers. It enables real-time streaming of raw device data seamlessly to customer systems without intermediate interfaces or modules, ensuring minimal latency. This mechanism provides partners and large fleet customer organizations with raw data feeds from ZF devices to build their own applications.
Key benefits #
- Real-time data delivery: Direct streaming of real-time data feeds from ZF devices to customer-facing Kafka topics
- Incoming messages are filtered based on the organization and required events and mapped to standardized or structured formats.
- Kafka is a message streaming platform.
- High scalability: Supports large-scale integrations for enterprise customers
- Publisher-consumer architecture: Data is published by SCALAR and consumed by the customer through Kafka topic
- Decision making: Empowers fleet organizations to make data-driven decisions and provide real-time insights
- Security: Offers a centralized, secure, and customizable data streaming infrastructure
Subscription process #
Customers can request access to RMS by reaching out to the SCALAR Sales or Customer Success teams who will create a subscription subject to approval. The approval workflow involves review of the subscription by the internal committee, followed by external Kafka topic creation by the support team.
Only one subscription is allowed per organization.
Supported events #
Several event details are published through the Raw Message Streaming (RMS) service, originating from SCALAR devices. When a device triggers an event, it is immediately captured by the SCALAR app and delivered to a customer-facing Kafka topic, making it available for consumption in real time. The supported event types are listed below.
Event |
Description |
position.registered |
Registers device position |
status.tpms |
TPMS (Tire Pressure Monitoring System) status details, such as location, pressure, pressure status, and temperature |
status.tbs |
TBS (Trailer braking system) status details, such as for brake lining, power, and the color code (for amber and red) |
config.tbs |
TBS configuration details, such as brand, model, serial number, type, and VIN |
event.drive.state |
Event details, such as fuel, mileage, coordinates, and state |
config.tpms.v2 |
TPMS configuration details |
event.harshbrake |
Harsh brake event details, such as axle load, mileage, coordinates, and speed |
event.rssactivation |
RSS activation event details, such as axle load, mileage, coordinates, and speed |
event.absactivation |
Anti-lock braking system event details, such as axle load, mileage, coordinates, and speed |
event.tbs.dtc.raised |
Sensor or system related to the TBS component has detected an issue that falls outside of normal operating limits and generated a Diagnostic Trouble Code |
status.trailer |
Status of the trailer, such as axle load, mileage, and speed |
status.comunit.power |
Status of the communication unit power source in terms of the following: battery pack, external power, and from TBS |
Sample RMS message #
This section explains with the help of an example how raw data feeds transmitted by a ZF device (as incoming message) are structured or formatted and published (as outgoing messages) to dedicated Kafka topics.
Event: position.registered
This event relates to providing GPS position information in a structured format, based on the standards for defining parameters.
Outgoing (formatted) message
{
"eventSubscriptionId": "unique_identifier_of_rmssubscription_guid_value",
"eventType": "position.registered",
"eventId": "unique_identifier_of_event_guid_value",
"eventVersion": 0,
"assetId": "unique_identifier_of_asset_guid_value",
"unitId": "unique_identifier_of_unit",
"eventData": {
"registeredOn": "2025-11-30T18:25:21Z",
"heading": 50,
"latitude": 50.8687,
"longitude": 2.8929,
"satCount": 0,
"speed": 0,
"validity": true
}
}