How do we connect your machines and business systems?
We check which machine data is available and how to exchange it with your systems. This defines the connections, work required and costs.
Let's talk about your plant
The questions on this page
- “What is needed to connect my machines?”First, we check which data is accessible
- “Can I keep my existing MES?”Connect GI4 to the systems you already use
- “Where does my data end up?”Run GI4 in-house and access it through a browser
- “How much work is it to add a machine?”We configure the data for each machine
- “What exactly do I need to get?”Start with the core system, add what you need
The problem
“What is needed to connect my machines?”
First, we check which data is accessible
Time and cost depend on how we can read and write machine data. In some cases the manufacturer needs to be involved.
We assess the plant before quoting, starting with the available connections.
- PLC and panel software managed by GEM
- We can add the data areas and signals needed for the connection.
- Standard connection available
- We use OPC UA, S7 or Modbus to access data exposed by the manufacturer.
- No connection available
- We study the machine and assess sensors, modules or gateways to collect data.
The problem
“Can I keep my existing MES?”
Connect GI4 to the systems you already use
GI4 can receive batches, products and recipes from the MES or ERP and send them to machines. It can also observe production or manage batches where there is no MES.
We use MQTT, OPC UA, HTTPS, databases or files. Data exchange is tailored to the meaning and rules of your systems.
The problem
“Where does my data end up?”
Run GI4 in-house and access it through a browser
GI4 runs on company servers or a preconfigured NAS, without sending production data to the cloud. Access it from computers and mobile devices.
For each parameter, we choose what to keep: its current value, change history or measurements over time.
The problem
“How much work is it to add a machine?”
We configure the data for each machine
For each machine, we define which parameters to read, where to find them and how to store them: frequency, thresholds and data type.
GI4 uses this configuration to create lines and machines in the system and start collection. Changes are linked to the active user, batch and recipe.
The problem
“What exactly do I need to get?”
Start with the core system, add what you need
The core collects and stores data. The GI4 app manages batches, recipes and users; MIO, included, provides dashboards and analysis.
You can add KID for RFID access and an AI agent to query data using knowledge of the plant. Both are options to assess against your needs.
Start with one machine. Purchase the system once, with no mandatory subscriptions or per-user or per-device licences.
At a glance
- PLCs and machines via OPC UA, S7, Modbus, or with added hardware
- MES and ERP via MQTT, OPC UA, HTTPS, databases or files
- At the edge on Docker: company server or preconfigured NAS
- Relational and time-series databases, chosen parameter by parameter
- No subscription, no per-user licence
Other topics
OEE and downtime Find production losses: times, stops and causes.
Recipes and parameters Retrieve recipe versions and compare them with the machine.
Batches and traceability Compare production runs and start from a previous batch.
MIO: dashboards and analysis Read settings, measurements, rejects and consumption together.
Operators and access Identify operators and trace their changes.
Let’s start with your machines.
Tell us what you want to improve. Together, we check which data we can collect and how to connect your plant before preparing a quote.
- 8plants in operation
- 4industries
- 28machines connected in the largest installation, across 11 lines