GI4 ·MIO ·INDUSTRY 4.0/5.0 ·DATA KEPT IN-HOUSE
Machine data, OEE, recipes, batches and energy use in one system,
on the machines you already have, without overhauling them.
Not a feature list: the questions heard every day on the shop floor, and where GI4 answers them. Each question takes you to the point that explains how.
Start from that batch: GI4 gives every machine on the line the recipe and version it ran with then, and lets you keep those values or move to the latest version. Before starting you see, row by row, what will change on each machine.
OEE by batch, machine and shift, states over time and downtime causes: not just how much you lose, but where to act.
Every change carries parameter, values, batch, recipe and operator. Two batches are compared with what happened inside each.
Every change becomes a version, every gap between machine and recipe is counted. Writes to the machine only when it is stopped.
MIO, included in GI4: settings and measurements on the same axis, rejects per test, per-piece data, energy use machine by machine.
RFID access, users managed in one place, and the shop floor deciding which parameters matter.
Connecting machines and systems
OPC UA, S7, Modbus or added sensors; MES and ERP via MQTT, OPC UA, HTTPS, databases or files. No cloud.
A real case
A dryer, a batch that ran for three days. The number on its own would have sent someone to check the machine. The batch view says something else.
Where the time went
It ran 20% faster than target, with no rejects. It lost a third of its efficiency waiting for material from upstream. The problem was the line.
How GI4 reads OEE
A core that collects data inside the company, and two web interfaces on top: one to manage production, one to analyse it. The rest is added when needed.
Your machines
always reads · writes only when the machine is stopped
The GI4 core, in-house
At the edge on Docker: company server or preconfigured NAS. No cloud.
MES and ERP
MQTT · OPC UA · HTTPS · databases · files
Manages
GI4 app
Batches, recipes, parameters, users, downtime causes.
Analyses
MIO
Dashboards, OEE, per-piece quality, energy use. Included.
Recogniseswhen needed
KID
The operator, with a personal RFID key.
Answerswhen needed
Queries the data with knowledge of the plant.
The operator panel stays in charge: working from the machine always remains possible.
A value changed on the panel is information to keep, not an error to normalise.
Not only which recipe, but what was changed, by whom and in which batch.
Parameter importance is set by the shop floor, not the technical office.
Sending is an explicit act, never a side effect of saving.
From a configuration file, line and machine generate themselves, and acquisition starts.
No cloud. Bought once, with no per-user or per-device licences.
GI4 records from day one, but it is at its best once it has built up history. Better to say so upfront.
Six pages, one per topic, with real screenshots of GI4 and MIO.
OEE and downtime Where production is really lost: times, states, causes.
Recipes and parameters Automatic versions, comparisons, readable parameters.
Batches and traceability Who changed what, when, in which batch.
MIO: dashboards and analysis Cross-referenced charts, per-piece quality, energy use.
Connecting machines and systems Machines of any age, MES and ERP, data kept in-house.
Operators and access Personal keys, permissions, the shop floor at the centre.It is the question that decides the time and cost of every GI4 installation. We look for the answer together, on your plant, before any quote.
