BENEFITS
What changes once the data flows by itself
The benefit of a middleware rarely shows on day one. It shows in the work nobody is doing any more six months later.
Nine points that come up in project after project
- Automated data exchange
- Readings move between machine and IT system with no one lifting a finger. No retyping, no detour through a spreadsheet.
- Better processes through transparent communication
- Whoever can see where something is stuck can fix it. Only a continuous data picture makes bottlenecks visible.
- More flexibility in production
- Plant and machines can be used better when their condition is known continuously rather than at the shift handover.
- Productivity, cost and quality
- The three hang together: fewer manual steps mean fewer mistakes, and fewer mistakes mean less rework.
- Scalability
- One more machine is one more connection, not a new project.
- Platform independence
- Runs on Windows, in Docker or in Kubernetes — whichever way your IT is set up already.
- Stability and security at high throughput
- Encrypted transfer and operation inside secured network zones, without the throughput suffering for it.
- Status and diagnosis for every transfer
- You see which connection is running, which is stuck and since when. That cuts fault finding from hours to minutes.
- Modular build from plug-ins
- You switch on what you need. The rest stands ready in case the system landscape changes.
FOR IT MANAGEMENT
One layer instead of many single connections
Point-to-point connections grow quadratically with every new machine. Each one has to be documented, monitored and touched again at the next system change. A mediating layer replaces that tangle with one place where connections are created, stay visible and disappear again.
For whoever runs it, that means one place for permissions, one place for logs, one place for updates.
FOR PRODUCTION
The machine stays as it is
connubes picks the data up where it already arises — at the controller, at the sensor, at the scale. Nothing changes on the machine itself, no operating step is added, and the line does not have to stop for it.
What does change: messages arrive earlier, orders are at the line without a printout, and the record for a batch can be looked up instead of collected together.
FROM RUNNING INSTALLATIONS
Figures customers report
| Measure | Wert | Context |
|---|---|---|
| Update time | under 15 ms | Label production with connected SAP communication |
| Data telegrams per day | around 15,000 | The same installation, in continuous operation |
| Sites in one architecture | several, international | Distributed instances including in the USA and in China |
| In use since | 2012 | Port logistics: machine data from the handling equipment to SAP and databases |
The figures come from specific installations and are not a promise for your environment — throughput and response time depend on the network, the controller and the target system.
Voices from the shop floor
„Die Prozesse laufen seit der Einführung durchgehend stabil und belastbar. Die schrittweise Automatisierung unserer Fertigung hat sich bestens bewährt.“
Hardy Schwenke, HERMA GmbH
„Wir konnten unsere Systeme ohne größeren Aufwand in nahezu jede Produktionslinie integrieren — viele Anlagen setzen ohnehin bereits auf offene Standards.“
Andreas Waneck, X-Rite Inc.
„Die Anbindung ließ sich von Anfang an zuverlässiger und einfacher konfigurieren als bei anderen Lösungen, die wir geprüft hatten.“
Thomas Ruppmann, Andreas Stihl AG & Co KG
