Retrofit
Connecting legacy machines
Older controllers deliver over Modbus, classic control protocols or digital inputs. The SWIFT-BOX turns that into clean OPC UA data points — without replacing the controller.
Follow-up · Edge · SWIFT-BOX
The edge gateway that does more than forward
An edge gateway that only passes data through just moves the problem upstairs. The SWIFT-BOX captures, historises, controls and computes right at the machine — in three tiers you pick as needed.
Clarify the tierThree tiers
Time-series capture and historisation are included in every tier. You pay for compute and control functions, not for the basics.
- Connect
- Pure collector: protocol connectivity, time series, historisation, hand-off to iniationOS, MES or cloud
- Control
- Adds control tasks at the machine: energy and load management, peak shaving, switching logic
- Compute
- Adds AI inference and a micro-MES at the line — models run where the data is created
01
What customers use the SWIFT-BOX for
Energy
Retrofitting energy monitoring
Meters and machines are captured and joined with order data. You see consumption per machine, order and unit — the data basis for ISO 50001 and energy legislation.
Load management
Shaving load peaks
In the Control tier the box regulates itself: consumers are staged by priority and process state, instead of one peak fixing your capacity charge for a year.
AI at the edge
Inference at the machine
Anomaly detection and quality prediction run locally in the Compute tier — without cloud latency and without process data leaving the plant.
02
Why not just a standard gateway?
Because a gateway without a data model only moves bytes. What arrives upstairs is “DB12.DBW4” again — and the modelling work is still ahead of you.
The SWIFT-BOX ships with your asset model: data points carry meaning, unit and asset context from day one. That is precisely what lets ERP, MES and AI systems use the values without rework.
And because edge computing does not end at capture: rules and models run where the data is created. That saves bandwidth, keeps latency low and keeps working when the link to head office drops.
Frequently asked about the SWIFT-BOX
Which protocols does the SWIFT-BOX support?
OPC UA including information models and companion specifications, Modbus TCP and RTU, MQTT and Sparkplug, BACnet and classic control protocols. Send us the list of your controllers and we will tell you how each one connects.
Do we need iniationOS to use the SWIFT-BOX?
No. The box delivers just as well into your existing MES, time-series database or cloud. iniationOS is the route when you want several lines and several systems on one shared data foundation.
Can we start with one machine?
That is the usual entry point. One box, one line, one measurable result — then you decide about the rollout. Tell us which machine you have in mind.
Does our process data leave the plant?
Only if you want it to. In the default setup everything stays on-premise; the box historises locally and serves your in-house systems. Cloud connectivity is an option, not a requirement.
How does Control differ from Compute?
Control regulates against fixed rules — load management, priorities, switching logic. Compute additionally executes models: anomaly detection, quality prediction or a micro-MES at the line. Which one you need depends on the task; a ten-minute call settles it.
Interested, but not ready to enquire?
An e-mail address is enough. We come back once with a short read on it — no newsletter.
Which machine should deliver data first?
Send us the controller type, year of manufacture and the figure you want to see. You get an assessment of which tier is enough.
Describe the machine