Interfaces
What do we talk to?
From the machine controller to the tax advisor: open, common standards — no proprietary islands. Data comes in, flows through, goes out structured.
OT · machine level
How machine & sensor data comes in — vendor-neutral, down to the controller.
OP OPC-UA The shared language of machines: values, typed devices (Companion Specs) and standard alarms (Alarms & Conditions) — vendor-neutrally into the historian. ↔ bidirectional standard SP SPS / Steuerungen Cycle, states, faults straight from the plant controller. ↘ inbound standard BE Beckhoff / TwinCAT PC-based control: variables & axis data tapped directly. ↘ inbound standard PR PROFINET Fieldbus: drives, I/O and sensors on the machine network. ↘ inbound standard OP OPC-UA FX (UAFX) Field-level OPC-UA: controller-to-controller and devices, deterministic (TSN) — the open path to field I/O instead of a vendor island. ↘ inbound standard
Data · integration
Connect other systems, legacy data and the AI — cleanly and permission-checked.
RE REST API Open interface: external systems read & write orders, status, data. ↔ bidirectional standard MC MCP (Model-Context-Protocol) The AI bridge: the AI accesses search & company data permission-checked — answers with real numbers. ↔ bidirectional standard ET ETL from Excel & files The catch-all: legacy data, spreadsheets and files get pulled in, cleaned and linked. ↘ inbound standard
Business · finance
Invoices, accounting and filings — structured, in and out.
PE PEPPOL (e-invoice) Structured e-invoicing in & out (UBL / BIS Billing 3.0) — demonstrated in the customer portal. ↔ bidirectional ● live demo
DATEV Accounting export to the tax advisor — at the push of a button. ↗ outbound standard BM BMD Export into the BMD finance suite (AT/DACH). ↗ outbound standard VA VAT / tax Advance VAT returns & statutory filings. ↗ outbound standard
Standards instead of islands: anything with an open interface can be connected — and whatever comes in is yours.