Skip to content
Book a Demo
software
Data Management
use cases
Industrial Automation, Network & Device Management
Licensing
3rd party

Autosol

We unify industrial data communications to reveal new opportunities for operational gains.

Anytime data. Everywhere insights.
Our solutions go beyond real-time to bring you both historical and real-time data, from every industrial device, so you have all you need to optimize operations from edge to edge.
Data-focused. Customer-driven.
Contact us to add to Neeve
Benefits of Autosol on Neeve
Deploying Autosol eACM on the Neeve Secure Edge creates a high-performance industrial gateway that reduces bandwidth consumption by up to 90%. By moving polling to the edge, Autosol ensures that critical data is never lost, even during prolonged network outages.
Protocol Translation at Scale: Unify data from diverse manufacturers (Allen Bradley, Emerson, ABB, Schneider) into a single MQTT Sparkplug B stream.
Bandwidth Optimization: Replace traditional “request-response” polling with “Report-by-Exception” (RBE), publishing only when data changes to drastically reduce telemetry costs.
Historical Resiliency (EFM): Collect and backfill historical records and EFM data automatically, ensuring regulatory compliance and accurate accounting without manual intervention.
Local Store-and-Forward: Utilize Neeve’s persistent SSD storage to buffer data locally during cloud disconnects, with automatic backfilling once the link is restored.
High-Resolution Insights: Perform local polling as fast as 50ms at the edge while only streaming required intervals to the cloud, providing a granular view of equipment health.
Architecture
Deployment Architecture on Neeve
Deployment model: Singleton (One eACM instance per site/network segment).
Workload: Light-to-medium; CPU usage is proportional to the number of active poll-cycles and tags.
Components: eACM Polling Engine, Protocol Drivers, MQTT Sparkplug B Publisher.
Data flows: * Ingress: Native industrial protocols (Modbus, ROC, BSAP, CIP) via Serial or Ethernet.
Egress (TCP 1883/8883): MQTT Sparkplug B traffic to the central broker.
Management: Communication with the “Autosol App Manager” for remote configuration.
Failure domains: If the pod fails, local polling stops. History is preserved in the field device (RTU) and can be retrieved by eACM upon restart.