End-to-end IoT engineering
oscarcabreragonzalez IoT Studio What isn't measured slips away
Our IoT engineering

End-to-end IoT engineering, from the board to the decision

An IoT ecosystem doesn't fail because of the missing part, but because of the layer nobody coordinated. These are the five we solve in-house, each with its grades and options according to what the project requires, and a real case at the end so you can judge the result.

5engineering layers under a single contract
EN 54design reference in detection and suppression
Class 3IPC-6012 standard for industrial boards
NL · BE · LUservice area
How we work

Each layer is sized separately according to what the project requires, and delivered integrated with the others. These are the options we cover in each one.

01

Hardware

Hardware revolves around demand

Not every project needs the same grade. In the technical phase we determine the required level and design the board for that level from the first schematic, because a prototype that cannot be certified never reaches production.

  • Prototype and backup boardProof of concept and domestic project. Rapid functional validation.
  • CE gradeCommercial product compliant with CE marking and the applicable radio directive.
  • Industrial gradeMultilayer PCB to IPC-6012 Class 3, IP65 / IP67 / IP68 encapsulation.
  • Sector-specific gradeEN 54 in detection and suppression · EN 12830 and HACCP in the cold chain · MID class 1 in electricity metering · EN IEC 61730 and 62446 in photovoltaics.
Hardware revolves around demand
02

Software

From storage to the dashboard

The software layer is sized according to the equipment manufacturer and the customer's specification. We cover everything from data persistence and redundancy to the screen where the decision is made.

  • Storage and redundancyRAID architectures and persistence strategies according to how critical the data is.
  • Backend and integrationsOur own API and integration with the systems and manufacturers already present at the customer.
  • Control dashboardsVisualisation and control panels operated by the customer's team.
  • Tailored to the manufacturerAdaptation to the protocol and specification of each integrated device.
From storage to the dashboard
03

Machine learning and AI

The parameter isn't assumed: it is trained

We design end to end the models that define the parameters of each IoT solution, instead of setting thresholds by intuition. It is the difference between a system that warns and a system that gets it right.

  • Training neural networksDefining the decision parameters of the IoT solution from real data.
  • Custom i-BooksComplete end-to-end design of the customer's interactive material.
  • Inference on field dataModels applied to the data produced by the deployed ecosystem itself.
The parameter isn't assumed: it is trained
04

Mobile applications

The app is never on its own

We always design the mobile client connected to the IoT solution, not as a separate piece. Whoever operates the system carries it with them.

  • Connected mobile clientThe app talks directly to the deployed IoT ecosystem.
  • iOS and AndroidDevelopment for both platforms according to the customer's device fleet.
  • Alerts and field operationNotification and action from the operator's own device.
The app is never on its own
05

Materials science

The enclosure is engineering too

We study and combine materials to solve the physical housing of each solution: enclosure, bracket and mount are part of the design, not an accessory bought at the end.

  • Enclosures, brackets and mountsSpecific design for the real installation environment of each device.
  • 3D printingPrototyping and short runs of our own parts.
  • Composition and chemical studyMaterial selection according to the aggressiveness of the environment, temperature and sealing.
  • Feasibility studyPrior analysis of manufacturability and cost before committing to the design.
The enclosure is engineering too
Tell us about your project
European case · specific product

Remote management of street lighting in a Dutch municipality

A municipality in the Netherlands needed to cut its lighting costs and deal with faults faster. We designed a complete ecosystem: each luminaire has an IoT controller that dims the light according to the time and presence, and reports its status over LoRaWAN to a central platform. The operator sees on a map which light point has failed, without waiting for a resident to report it.

The result: less energy consumed, data-driven maintenance and a better-lit city where and when it is needed.

−42%
Lighting consumption
3.800
Connected light points
−65%
Fault time
7 years
Extended LED service life

The stack we use in this case

Proven technology in every layer, chosen for reliability and for fitting the customer's ecosystem.

Sensing
Luminaire controllers with photocell and presence sensor, with built-in consumption metering.
Connectivity
Private LoRaWAN network with municipal gateways, low power and long urban range.
Platform
Dashboard with a real-time map, scheduled dimming and automatic fault alerts.
Security
End-to-end encryption, identity management and GDPR compliance by design.

* Illustrative case representative of smart city projects in Europe. The actual design is adapted to each customer's infrastructure and objectives.

Tell us about your project