Dipole LAMA Middleware

What Dipole LAMA Middleware is

Dipole LAMA Middleware collects and manages data from RFID, NFC, barcodes, and other technologies for real-time tracking. It connects readers, printers, vision cameras, sensors, and other Auto-ID devices with systems such as ERP, WMS, and MES, as well as business management software and applications including Kanban and Lean. Read events can identify what happened, where, and when, with optional status and direction details. Supported technologies include UHF, HF, NFC, and LF. The product page describes a Cross ID System, computing-platform plugins, Plug & Play setup, and configurable predefined scenarios. Its datasheet lists communication options such as REST, POST, WCF, SOAP, Socket, WebSocket, XML, and JSON. It can produce custom reports and manage alerts for errors and communication disconnections, alongside read-event analytics and movement history. LAMA is deployed on premises. Requirements include Microsoft SQL Server and Windows 7 or later, or Windows Server 2012 or later; minimum hardware is 8 GiB RAM and 2 GiB disk space. Sizing is customized, and pricing is on request.

Who it suits

LAMA Middleware suits organizations that need to connect Auto-ID devices with enterprise systems and track read events on premises. It may fit deployments needing movement history, analytics, reports, and exception alerts.

Limits

No free plan or trial is listed. The smallest available size is customized, and pricing is on request.

Getting started

1. Visit the Dipole LAMA Middleware product page.
2. Contact Dipole for assistance and customized sizing.
3. Prepare a Windows 7 or later system, or Windows Server 2012 or later, with Microsoft SQL Server.
4. Meet the minimum requirements of 8 GiB RAM and 2 GiB disk space; the recommended amounts are 16 GiB RAM and 4 GiB disk space.
5. Plan the on-premises deployment and connect the required Auto-ID devices and business systems.

Verdict

LAMA Middleware combines device integration, read-event tracking, reporting, and alerts for on-premises deployments. Buyers should account for its Windows and SQL Server requirements and request customized sizing and pricing.