>> From the field

Proof on the production floor.

From component suppliers to global machine builders and operators. They build on voraus because it runs in production, on hardware and in places they choose. The reasons are commercial as much as technical: every change costs less, every rollout risks less, and the lead they build cannot be bought with hardware.

Talk to an engineer →Get started →
>> Cases

Find the one that sounds like you.

Five transformations, anonymized by customer type. Different industries, different entry points, same platform underneath.

01Plant operator · brownfield migration

Modernize the plant without replacing it.

The challenge

Industrialized series production on grown control structures. Every product change rippled through controls, robotics, HMI and IT, and the production had to keep running, with as little new investment as possible.

› Show the full case
What we built together
  • Analysis of the running plant, quantifying the potential
  • Step-by-step introduction of a software-defined layer
  • Application logic decoupled from robot and controller specifics
  • Standardized APIs instead of point-to-point connections
  • Existing controls, MES and peripherals integrated
  • Simulation and virtual commissioning to de-risk changes
What it delivers
  • Cells extended by software update instead of rebuild
  • New components integrated faster, robots and peripherals alike
  • Central state and diagnostics data across lines
  • Less downtime when production changes
Where it leads

From plant-specific automation to one platform that every new line starts from.

Where it pays

Less capital tied up in new hardware, lower maintenance per line, and less risk in every change.

a change simulation voraus.pioneer, validated first voraus.core software-defined layer, added on top controls existing MES existing periphery existing
The layer goes on top. Controls, MES and periphery stay. Changes are tested in simulation first.
02Global machine builder · standardization

One software base for a global product portfolio.

The challenge

Machines and production systems across several business units, each with its own robot brands, controller types and standards. Recurring functions were built and maintained many times over.

› Show the full case
What we built together
  • Vendor-independent robotics abstraction layer
  • One shared release for every business unit, instead of one per product line
  • Standardized APIs for robots, peripherals and higher-level systems
  • Reusable software building blocks and one shared test environment
What it delivers
  • One software base across different robot systems
  • Less engineering effort per customer project
  • Additional robot brands integrated faster
  • Higher reuse of software and test artifacts
  • Less dependence on single suppliers: components and vendors stay interchangeable
Where it leads

From individual projects to a group-wide platform strategy: faster innovation, and an engineering organization that scales.

Where it pays

Higher margin per project, less maintenance across the portfolio, and less exposure to single suppliers.

One shared release voraus.core, one test environment same build, different business units unit A own brands unit B own brands unit C own brands
One release, different business units. The builds that were maintained many times over collapse into one.
03Technology provider · integration as a product

Scale your technology without becoming an integrator.

The challenge

Specialized technology, vision or AI, met a different customer environment every time. Industrial scaling failed on integration effort, not on the product.

› Show the full case
What we built together
  • One integration package the integrator installs, instead of a project per customer environment
  • Standardized APIs for robotics, fieldbus and plant integration
  • Clear split between product IP and customer-specific integration
What it delivers
  • Shorter integration times at end customers
  • Reusable interfaces and integration patterns
  • Several customer environments supported without separate builds
  • Faster pilots and customer evaluations
Where it leads

From technology provider to a scalable platform component that ships through integrators and machine builders.

Where it pays

Higher margin, room to price competitively, and a larger addressable market.

Product IP your vision, your AI, your components One integration package voraus.core, installed with voraus.pioneer your side customer side customer A customer B customer C
One package crosses the boundary, instead of a project for every customer environment.
04Plant operator · smart production

From production data to production decisions.

The challenge

Machine, process and quality data sat in separate machines, controls and databases. Root causes stayed invisible and process changes rested on experience rather than evidence.

› Show the full case
What we built together
  • Data comes straight from the runtime on the machine, not from a separate copy of it
  • Machine, process and quality data brought together
  • Standardized data interfaces and models
  • Dashboards, KPIs and alarms on a shared foundation
What it delivers
  • One view of the relevant production data
  • Deviations spotted faster
  • Traceability across manufacturing steps
  • Less manual analysis effort
Where it leads

Continuous optimization instead of firefighting: less scrap and less energy per part, and the basis for predictive analytics and AI on the shopfloor.

Where it pays

Higher OEE and output, and decisions made on evidence instead of experience.

dashboards, KPIs, alarms separate copy of the data one model standardized voraus.core the runtime on the machine machine, process, quality
The data comes from the runtime itself. The separate copy is what went away.
05Robot manufacturer · robot as a product

A software-defined robot.

The challenge

Powerful robot hardware, and programming that set the limits. Ease of use fell short of what the market expects, functionality was missing, and new technologies could be used only in part, which narrowed the applications.

› Show the full case
What we built together
  • Software-centric control architecture on voraus.core, including force and torque control
  • One or several arms from one program, coordinated and collision-free
  • Graphical programming for simple tasks, full Python for complex ones
  • Simulation and digital commissioning included
What it delivers
  • Programming without deep robot expertise
  • Force-guided processes implemented directly
  • Several arms in one application, without a second control system
  • Faster development of new applications
  • One operating concept for different user groups
  • New technologies and AI integrated without touching the control architecture
Where it leads

Differentiation through software instead of mechanics alone: new functions ship as updates, and a wide developer ecosystem grows around the robot.

Where it pays

Shorter development cycles for new applications, a wider market for the same hardware, and a higher margin per unit.

graphical simple tasks Python complex tasks voraus.core coordinated motion, force and torque control digital twin voraus.pioneer robot hardware robot hardware
Two ways in, one runtime. One program moves one arm or several, coordinated, against the hardware or against the simulation.
>> Benchmarks

Proven under load, not in a demo.

Qualified in production at a global machine builder. When it has to work 24/7, it does.

Real-time control, delivered in software, on standard hardware. 1 ms cycle time with 119 µs worst-case task jitter, on par with a classic controller.
worst-case task jitter119 µsvs. 178 µs, 33% lower
cycle time1 mson par with dedicated controllers
EtherCAT round tripapprox. 32 µsdeviations in the low µs range

Task jitter and cycle time measured with standard Linux benchmarking tools (cyclictest under load) on standard industrial hardware. Fieldbus figures measured on the bus under the same load.

› Show an example architecture

High-volume palletizing: one edge PC carries HMI, cell, gripper and robot control. Hardware is abstracted without extra effort. The same application runs against the real component or its true-to-reality simulation. Access, data and the cabinet architecture get simpler, and the real-time demands of robots and peripherals are met as a matter of course.

Edge PCHMI, cell / gripper control, robot controlPLCcell / gripper controlPLCrobot controlrealsimrobotrealsimgripperrealsimsignals, …
voraus automation
deployment timeapprox. 2 minvs. approx. 60 min
recovery timeapprox. 1 minvs. more than 120 min
cost of change€vs. €€€€
system complexitylowvs. high
automated test coverageapprox. 80%vs. near to none
>> Your turn

Recognized your situation?

One of the cases above addresses your challenge, or you bring us a new one. Tell us where you stand and who you are, and you get a concrete plan instead of a brochure.

Get your plan →Talk to an engineer →