Frequently asked questions about ARIA Track.

ARIA Track is the entry edition: the platform's traceability surface — genealogy of batches and parts, batch search, live monitoring, and history — packaged as a product of its own. ARIA MES/SCADA (Lite and Pro) adds line governance: recipes, orders, andon, flow orchestration, and commands to the PLCs. Track is the entry point and uses the same data and master data, so the upgrade doesn't start from scratch.

No. Track observes and records: it reads field events and reconstructs traceability, but it does not write to the PLCs and does not govern recipes or orders. The PLC remains the single source of truth for the process. When you need to control the line — not just trace it — you move to ARIA MES/SCADA.

You enable the MES/SCADA edition on the same installation: the data, genealogy, and line master data already in ARIA Track stay, and the control modules are added. The public plans are Lite at €1,600 and Pro at €2,300 per station per year; the upgrade is sized during the assessment based on the monitored stations.

Track reads field data through ARIA Connector, which speaks OPC UA (any compatible PLC) and S7 (Siemens). For PLCs from other vendors we use the PLC's own OPC UA server or a dedicated gateway. The connection is read-only: no writes toward the field.

Wherever the customer needs it: on-premise on the plant server to reduce latency and network dependency, or in the cloud for consolidated multi-site reporting. History retention is designed together based on compliance and analytics requirements.

Yes. Genealogy and event history export to CSV, ready to attach to a quality report or a customer reply. Every part carries its batch, the stations traversed, parameters, and timestamps: the full history, searchable by batch.