AQonvis

Why are the numbers correct?

A fair question. Here's the answer.

Many sources. One number.

Machines
ERP
Workstations
Accounting
Linking and context
One solid process chain

Every source speaks its own language. The ERP knows orders, the machine knows signals, accounting knows costs. None of them knows the margin. AQonvis puts events from every source into a chronological, factual order (a process chain) and derives from it what actually happened.

How operational data is created today

The operator books it at the end of the shift, from memory. Several operations get started at once because it's faster. Whatever doesn't add up gets corrected later in the office. Every one of those corrections is a guess that enters the report as a fact.

How it's created with AQonvis

Start, interruption, and end are derived from machine behavior and location. What's in the system isn't better maintained — it came to exist differently.

In a study of 16 mid-sized contract manufacturers at IFW Hannover, 36% of operations were recorded as simultaneous bookings, and between 36% and 50% of the data was corrected manually after the fact.

We're often mistaken for two other things. Rightly so both times, and wrongly so both times.

A dashboard

A dashboard shows you what's in your data. If the data is wrong, it just shows you the wrong thing more nicely. AQonvis starts one level deeper, at the point where the number is created.

An MES

A manufacturing execution system controls production. It speaks the language of machines and operations, not costs. AQonvis doesn't replace it — it translates between what happens on the shop floor and what it costs.

AQonvis

We're the layer in between. We turn existing sources into solid data and convert it into euros. Your ERP stays your ERP, your MES stays your MES.

Questions from IT

Runs on your own premises

AQonvis runs on your network, on your infrastructure. Your production data never leaves the building.

Interfaces

Connects to common machine controllers and systems via established protocols: OPC UA, UMATI, MTConnect, DNC, S7.

No changes to your ERP

Your system stays unchanged, with every customization built up over the years.

Security

Integration happens in close coordination with your IT department.

Data protection and machine data

Do you track how fast individual employees work? No. We measure orders and machines. Our reference point is the order: which operation ran when, on which machine, for how long, with what result.

Do we need the works council for this? Yes, as soon as per-workstation times are captured — regardless of what the data is used for. Who in the company sees which data is defined through roles during setup.

Request a sample works agreement
Grounded in research

Grounded in research

Research and publications

Get started

Read the whitepaper

Request whitepaper

Interested

Five orders, one report

Request free analysis

Ready to commit

Request a proof of concept

Request test project