Technical
What IT and automation will ask
Straight answers on architecture, network, security and data. The rest we discuss with your team.
Nothing is written to the PLC
The drivers have no write function and the controller program does not change. Automation stays in charge of the process.
Data stays at the plant
Server at the plant, local database, access over the company network or VPN. Cloud only if the customer wants it, for outgoing e-mail.
Open database
SQLite or PostgreSQL, CSV and JSON API. The history belongs to the customer and can be read by any tool.
Protocols
Eight ways to read, all read-only
A new driver joins the same scan, with the same watchdog and the same test. Several PLCs and protocols coexist in one installation.
| Protocol | Port | Equipment | How |
|---|---|---|---|
| OPC UA | 4840 · 4870 | Siemens S7-1500/1200 with OPC UA server, WinCC RT Advanced, B&R, ABB, Beckhoff, Rockwell FactoryTalk Linx | subscription, 180 s watchdog |
| Siemens S7 (PUT/GET) | 102 | S7-300/400/1200/1500, standard-access DBs, I/Q/M | read only (Read Var) |
| Modbus TCP | 502 | Schneider M221/M241/M251/M340, WEG, ABB AC500, Delta, meters and relays | functions 01 to 04 |
| Modbus RTU (RS-485) | COM | multimeters, WEG CFW and ABB ACS drives, soft starters, relays without Ethernet | same scan, per slave |
| EtherNet/IP (CIP) | 44818 | Rockwell ControlLogix, CompactLogix, Micro800; Omron NJ/NX | tags by name |
| Beckhoff ADS | 48898 | TwinCAT 2 and 3, variables by name | ADS route on the PLC |
| MQTT | 1883 · 8883 | IoT gateways, wireless sensors, scales, other systems | JSON or Sparkplug B |
| Database | — | WinCC RT Advanced data logs, tables from another system | imports by interval |
Architecture
One service, one database, one web interface
- Windows service in Python with embedded web interface (port 8480). Starts with the machine, no window open.
- Local SQLite database on Edge; PostgreSQL with TimescaleDB on Server. Automatic full and incremental backup, restore from the screen.
- Store-on-change (deadband per variable) with one guaranteed sample per minute, so a trend never runs out of points.
- No client installation: any browser on the network, including phones over VPN.
- Single instance per server, no-data watchdog per source, running batch recovered after a restart.
Requirements
What the plant needs
- Server: Windows 10/11 or Server, 4 cores, 8 GB RAM, SSD. An industrial mini-PC is enough for Edge.
- Disk: on the order of 1 GB per month for 1,500 variables stored on change; depends on the process.
- Network: outbound from the server to the PLCs on the protocol ports (102, 502, 4840, 44818…); inbound 8480 for users. NTP for the clock.
- On the PLC: Siemens needs PUT/GET enabled or the OPC UA server on; Rockwell needs nothing; Beckhoff needs an ADS route.
- E-mail: outbound SMTP (587 or 465) for automatic reports, via the company server or a sending service.
Security
Read-only by design
- No writes to the PLC: the drivers implement read functions only.
- Users and roles (viewer, operator, engineer, admin), PBKDF2 passwords, forced change on first login, lockout after failed attempts, 12-hour sessions.
- Activity log: who logged in, what changed, which factor was applied, which report was generated. Exportable as CSV.
- Offline licence by signed machine code. No telemetry, no cloud dependency.
- Protected code: critical modules are compiled to native code in the installed package.
Integration
API for ERP and BI
- JSON: closed batches, production per day and per shift, instant state, KPIs. Designed for ERPs through a REST integrator.
- CSV: series of any variable, batches and production, ready for Excel and Power BI.
- Tag catalogue generated from the PLC project, an OPC UA server or a spreadsheet.
- Ready device models for common drives and meters, with the right current scaling and the manufacturer’s fault table.