Industry 4.0 · software, consulting and implementation
Connect your factory. Make its data work.
Bring existing machines, controllers and business systems into one shared information model. We help you assess the opportunity, connect the data and put it to work across production, energy and operations.
Conceptual connected factory. An illustration of the idea, not a photograph of a site and not a picture of a product.
The problem
The holy grail, and why the climb never pays for itself
For forty years a factory has been built in levels: the machine at the bottom, the control room above it, then whatever tracks production, then the office, then whatever is off site. Each level talks to the one directly above it, and to nothing else.
It works. It is also why a number takes days to travel five floors, and why the answer at the top rarely matches the reading at the bottom.
- Every level keeps its own
- The control room knows things the office never sees, and the office keeps records the floor cannot check. Nothing is hidden on purpose — there is simply nowhere shared for it to be.
- Nothing is named the same twice
- The same filler is a tag number in one system, a line item in another and a description typed by hand in a third. Joining them is somebody deciding, again, which three names mean one machine.
- Every join is paid for
- Four boundaries, four projects — a specification, a consultant, an invoice, and a thing that breaks the next time either end is upgraded. Ten systems wired to each other is forty-five of those.
The trade names for those three: data silos, no common data model, and integration overhead. The levels themselves are ISA-95 levels one to four, which is the part worth keeping — see below.
Industry 3.0 · the holy grail4 joins
The solution
A UNS: one ring, and everything one hop from the middle
A unified namespace — a UNS — is one shared place that everything publishes into and everything reads from. No system is wired to another. The machine, the control room, production, the office and the warehouse each connect once, to the middle, and immediately have everything already in it.
It only works if everything in it is named the same way, so the naming follows the shape you already use: which site, which area, which line, which machine, which reading. That shape is ISA-95 — the same levels the holy grail stacks, kept as an address instead of a chain of custody.
- One place to look
- The reading, the order it belongs to and what it cost are in the same place, under the same name, at the same moment.
- One name per thing
- A machine has one address, and it is the address in the message, the chart, the alert and the export. Rename a line and it is renamed everywhere.
- One join, not forty-five
- A system connects to the UNS rather than to every other system. The eleventh one costs one connection, not ten more.
Production, energy and buildings are applications we build on the UNS. Your business system, warehouse system and customer system are destinations we connect to — we do not supply those, and we do not replace them.
Industry 4.0 · the UNS1 join each
What an address looks like
site / area / line / cell / reading
What runs on it
Both halves of the plant, on one UNS
OT is the equipment side: the machines, their controllers and what they measure. IT is the business side: the orders, the stock and the customers. The UNS is what lets a question cross between them.
OT · what we build on the UNS
Production
MESMachine states, runs, downtime and quality — with the performance picture, and the reason a line lost its shift, inside the same application.
Energy
EMSWhat each area, line and machine used, on which source, in the context of the site and what it was making at the time.
Buildings
BMSEnvironmental readings and scheduled equipment control, in the same operational view rather than on a separate panel nobody opens.
IT · what we connect it to
Orders and costing
ERPThe order the plant is working against, and what it actually cost to fulfil. Odoo and ERPNext are current integration paths; anything else is scoped through its own interface.
Stock and movements
WMSWhat the store holds, what moved, and what a job consumed against what it was supposed to — read from the warehouse system you already run.
Customers and demand
CRMWhich customer an order belongs to, so a delay on a line can be answered before somebody rings to ask about it.
The OT three are applications we build on your UNS. The IT three are systems you already run, and we exchange agreed data with them — we do not supply or replace an ERP, a warehouse system or a CRM.
Working with your equipment
Keep the systems you already know.
Different makers and different communication interfaces can feed the same information model. We choose the right adapter, map what the equipment reports and connect it to the way your plant actually works.
Automation and control
Siemens
Schneider Electric
ABB
Rockwell Automation
Mitsubishi Electric
Omron
Beckhoff
WAGO
Phoenix Contact
Delta
Examples of equipment we can assess and integrate through a suitable interface. A compatibility discussion — not a partner list, and not a customer list.
How we work
From the first question to everyday use.
- 01
Assess
Map the equipment and systems you have, the people using them, and the outcome worth testing first.
- 02
Connect
Configure the interfaces, the asset model and the software around the site as it already is.
- 03
Prove
Run one agreed workflow with a baseline, an owner and a result somebody can check.
- 04
Expand
Reuse the same foundation across more machines and more applications, then document it and train the team.
Software subscriptions, custom integration and local deployment are scoped around the project rather than sold as a package.
Training and exposure
Industry 4.0. For factories, and for people.
We are building practical demonstrations and learning sessions for students, engineers and industrial teams: follow a signal from the equipment into the UNS, build a view worth looking at, and explain the decision it supports.
Start with the question your factory needs answered.
Tell us what you run today and what you want to understand or improve. We will help define a first demonstration worth doing, and what comes after it.