Read-only first
Every new install starts in monitor-only mode: it reads and shows everything and writes nothing to a PLC. Outputs are switched on in settings, deliberately, after your team has checked the rules. Only one program may write a given PLC bit.
Interlocks that fail safe
Interlocks run on the PLC harness, so they keep working if a machine's EUROMAP or OPC UA data link drops. A heartbeat bit lets PLC ladder logic detect that the server stopped and fall back to local interlocks.
Outbound only
Plants connect out to CycleWright Cloud over HTTPS. There are no inbound firewall ports and no VPN. The cloud receives data and can never control machines.
Keeps running offline
The plant server runs on a PC on your network and needs no internet to monitor machines and run interlocks. An expired license never stops production.
Safe updates
Updates are signed and go to pilot plants before stable. The database is backed up before every update, and a version that fails to start rolls back automatically. A release that changes output behavior needs explicit confirmation while outputs are on.
Access control
- An admin password protects plant settings; the board and reports stay readable on the plant network.
- In the ERP, viewers read, supervisors create and change, and only admins delete.
- API keys belong to one company and can be revoked at any time.
- Every change is kept in a change history, at the plant and in the ERP: who made it, when, and the value before and after. Passwords and keys are never stored in it. Every record is scoped to its company.
- Stored EDI and accounting credentials are encrypted.
Your data
Machine history lives on your plant PC. Reports export to CSV, the configuration exports from settings, and the ERP has a REST API for everything.