What the line did, not just what it is doing
Tags can be sampled and queried so a supervisor can go back through a shift, a jam or a divert problem with real values, not recollection.
Data, historian and reporting
Know what the line actually did — this shift and last month
Secure Sorter keeps tag history, carton and order context, and the confirms and exceptions that explain a divert. Reports can go out as PDF, CSV or a spreadsheet. A SQL bridge can meet a plant database. Retention is set per site, by Electrol.
- Tag historian you can query
- Shift and sorter reports
- SQL bridge to plant databases
- Carton-level confirms and exceptions
History that is useful the next morning
A line improves when people can see what was released, what diverted, and what took the exception path — on this shift and last month.
PDF, CSV or a spreadsheet
Reports the operations team can actually hand on — including scheduled ticks Electrol configures — in the forms people already use.
Meet the plant database where it is
A SQL path can connect history and records to plant databases. Optional historian sinks in the platform include a MySQL and MariaDB path. What is turned on is a site decision.
License plates, orders, confirms
Alongside tag samples, the WCS keeps license-plate and order context, divert confirms and exception events — the story of a carton, not only a trend of a motor.
The local historian file is not page-encrypted. The on-disk SQLite historian is not encrypted at the page level. Electrol uses encrypted backups and disk encryption for that file. Remote historian connections — Postgres, MySQL and SQL Server — require TLS.
Ask what a shift report can look like on your line
Retention and reports are set per site by Electrol. [email protected]