The hardware E-stop always wins
If someone cuts the machine with the wall switch or the emergency stop, that wins over any remote command. Local industrial safety is never overridden.
The app reads what every machine is doing (when it starts, how much it processed) and sends it commands: start the bottling line, stop a pump, change the chiller setpoint. Critical ones need approval from another authorized person or your QR-verified presence.
Compatibility
Five integration tiers, from the manufacturer's cloud down to manual logging. No machine is left out of the book.
| Tier | How it connects | What you get |
|---|---|---|
| A | Manufacturer platform (cloud) | Data reading with the winery's credentials; no commands |
| B | Modbus TCP / OPC-UA via local gateway | Reading + commands to the PLC through the bridge device |
| C | Relay + flow-meter retrofit | Start/stop and volume cut-off on machines without a PLC |
| D | Read-only (telemetry) | Live status and counters, no commands |
| E | Manual operator logging | The operation enters the book just as complete |
Safety
If someone cuts the machine with the wall switch or the emergency stop, that wins over any remote command. Local industrial safety is never overridden.
Starting a pump or a line needs approval from another authorized person, or the sender confirms with the machine's QR code that they are on the floor. You cannot approve your own command, even as the owner.
Scanning the machine's QR code on the floor confirms a person is watching the hose. It replaces the second approval and is valid for 10 minutes, only for whoever scanned it.
You ask for X litres and the bridge device cuts off at the target volume; if it loses the flow-meter reading, it stops the pump. Commands not executed within 10 minutes expire and are never retried automatically.
The differentiator
Dedicated automation systems record "the pump started at 14:30" and nobody knows which batch it was. In Cepaos, every commanded operation is automatically written to your cellar book and compliance records:
Yes. You can start, stop and request pumping X litres from your phone. Critical commands need approval from another authorized person or QR-verified presence on the floor; you cannot approve your own command.
Pumps, presses, chillers, bottling lines, CIP systems, boilers, bench scales, in-line sensors, irrigation and more. There are five integration tiers: the manufacturer's native API, Modbus/OPC-UA via gateway, relay + flow-meter retrofit, read-only, and manual logging. No machine stays out of the book.
The plant's physical emergency stop always wins over any remote command. On top of that: approval from another authorized person or QR-verified presence on critical commands, volume cut-off via flow meter, and automatic expiry: if a command is not executed within 10 minutes, it expires and nothing is retried automatically.
Connected Winery is a monthly add-on on top of your Cepaos plan, at list price for your market and currency. Available from the Domaine plan; included in Estate and in custom plans. Check the pricing page or talk to us about your case.
No. The integration uses what your machine already offers: the manufacturer's API or the existing PLC via Modbus/OPC-UA. For machines without a PLC, a relay + flow-meter retrofit is enough, and you can always start read-only or with manual logging without touching anything.
The machine stays under its local control: plant safety does not depend on the cloud. The bridge device stops accepting new commands, and those not executed within 10 minutes expire without being retried. When the connection returns, it sends the readings it stored.
Start with read-only (tier D) and enable commands when your team is ready.