DERAS connects RFID reads to business workflows.

The software layer between supported RFID readers and the applications that use their data.

DERAS is a joint effort by TUDI (PT Hano Identik Teknologi) and PRIEDS (PT Solusi Kebutuhan Teknologi).

From a tag read to a useful record.

A tag read is not automatically a validated stock movement, location or transaction. The workflow defines what the captured data means.

RFID reader
A configured reader captures the tag identity and available read data at a defined point.
DERAS layer
Agree the device connection, output fields and how repeated or unexpected reads are handled. The event can then be sent through an agreed interface.
Business system
A TUDI application or your existing system applies workflow rules before the result becomes a stock record, movement or alert.

This sample shows device identity, EPC and RSSI. It illustrates data, not a live reader connection or evidence of a customer deployment.

Illustration with sample data: each tag read by a UHF RFID scanner arrives through DERAS as a scan-rfid-result WebSocket event.

DERAS WebSocket

Sample stream

Illustrative sample events: UHF RFID scan results streamed by DERAS over WebSocket.

These examples help define a project. Confirm the reader, interface and application behavior for your own conditions.

Inventory and assets: Review counted, missing and unexpected items before reconciling stock.
Item movement: Define checkpoints and the rules for recording a movement.
Loss prevention: Define an exit event and the appropriate staff response.

This information helps define a suitable integration path. Device and system support is not automatic for every configuration.

Devices: Confirm reader model, firmware, connectivity and on-site configuration.
Data: Agree item identity, valid events, duplicates, destination fields and business actions.
Interface: Define the receiving application, data format and interfaces actually available for the project.
Operations: Discuss software placement, network needs, failure behavior, logs, data access and support responsibilities.
Support boundaries: Connectors and camera or door-access integrations are separate discussions and must be confirmed per project.

Tell us which reader you use, the process you need to record and the destination system. We can review the appropriate scope with you.