Cross-domain engineering that owns the whole system
Some problems cannot be sliced. When hardware, firmware, software and wireless have to work together, no single specialist can own the result. You either find one team that takes the whole thing, or you split it across vendors and carry the integration risk yourself.
We’re that team, on two fronts: integrating the systems you already run, and developing the hardware that does not exist yet.
From the sensor to the ERP
We climb the automation pyramid (ISA-95) for you: from the sensors and the PLCs on the line, through supervision and the MES, up to the plant’s ERP. These are the buses we already work with.
Software that measures, decides and records on production test machines, built and maintained by us.
PLCs, motion control, HMI, SCADA and edge devices brought together into one working line.
The plant’s data reaching the MES and the ERP, so the people who plan see what the line does.
Devices, down to the silicon
When the device does not exist yet, we design it: electronics, RF and antennas, ultra-low-power design and firmware, the equipment that tests it, and at the silicon level, the chip itself.
RF and ultra-low-power are the layers even strong electronics teams don’t have.
We have spent more than 20 years at exactly that intersection. Our battery-free sensor tags are the proof: they run on the energy of the radio that reads them.
The seam between the device and the plant
Usually the device and the system that reads it come from different suppliers, and the seam between them belongs to nobody. With us, they are one project with one owner.
When teams come to us
The firmware works on the bench but not in the field. The RF range dropped when the enclosure went on.
- Software
- Firmware
- Wireless / RF?
- Electronics
Strong in electronics, missing wireless or RF, and no time to hire a whole department.
Three suppliers, one system, and nobody owning the integration.
Start with a paid scoping study
A short, fixed-fee engagement where we assess your cross-domain engineering problem and hand you an architecture and a plan.
What you get
- A clear understanding of the cross-domain challenge
- An architecture proposal
- A realistic plan with timeline and investment range
- An honest assessment: can we solve this, and should you proceed?
The report is yours to keep, whether or not you build with us.
For a battery-free sensor, the first step is a Feasibility Study, typically four to five weeks, with the link and power budget, concepts and cost bands.
How it goes from there
Scoping Study for a system, typically one to two weeks.
Feasibility Study for a battery-free sensor, typically four to five weeks.
Fixed fee, typically €5,000 to €10,000, agreed before we start.
Tell us about your system
A few lines are enough: what you are building, and where it is stuck.
Want to see what we have done first? Work we can talk about.