Someone drives out
A machine stops or behaves oddly. The only way to find out why is to send someone to look.
Industrial telematics & remote diagnostics
See problems on your machinesvehiclesequipment
before they cost you a wasted trip.
Melqart connects machines, vehicles and plant equipment to the systems your teams already use. Your service team knows what failed, and whether a visit is needed, before anyone leaves the yard. Built on open Linux hardware, with no vendor lock-in.
Sound familiar?
You dispatch first. You diagnose later.
That order costs money. A technician drives out, looks, and often comes back for parts while the machine sits idle. We flip it: machine health first, then the right visit.
The fault is found on site
The technician diagnoses at the machine, often without the right part on the van.
A second trip follows
Back to the yard for parts, then out again. The machine earns nothing in between.
What changes
What changes when your machines report their health.
Machine data is only worth collecting if it changes decisions on the ground. These are the decisions it should change.
Fewer wasted trips
You send someone when the data says the drive is worth it, not to find out on site what broke.
Better first-time fix
Parts and skills leave the yard already matched to the fault. Fewer return visits.
Fewer Friday-afternoon scrambles
Unknown faults stop turning into last-minute overtime across the fleet.
Less surprise downtime
You plan the stop with operations instead of discovering it mid-shift. Machines keep earning.
What we connect
Open industrial IoT paths from machine data to business systems.
Start with rugged gateways, then connect the signals to the software your teams already use.
Industrial 5G routers & IoT gateways
Open Linux hardware for PLCs, meters, sensors and remote assets, with Modbus, OPC-UA and MQTT integration.
Explore
Maintenance & asset software integration
Feed CMMS, EAM and ERP systems with runtime, alarms, condition data and work-order-ready events.
Explore
Condition & process monitoring
Turn vibration, level, flow, temperature and runtime signals into alarms, dashboards and maintenance context.
Explore
Remote access & OT security
Give operations controlled remote diagnostics, updates and gateway access without closed-platform lock-in.
Explore
Concrete truck tracking
Drum rotation, hydraulic pressure, GPS and delivery events from every mixer truck, on a gateway you own.
Explore
Building management
Connect BMS, HVAC, metering and controls data to open monitoring and reporting workflows.
Explore
M2M connectivity
Industrial routers and gateways for remote device fleets, with open connectivity options you choose and control.
Explore
Energy management
Bring metering, load and site energy data into open operational systems.
ExploreServices
How we build: no lock-in, no hidden costs.
Whether you run a mixed fleet, retrofit heavy machinery, or design telemetry for production-line OEMs, our engagements are structured to give you complete operational independence.
Strategic consulting & discovery.
Should you build this, and if so, what's the clear path to ROI?
We analyze your existing telemetry stack, run feasibility studies, and deliver a comprehensive architecture design document. The artifact is yours to keep, whether you build it with us or not.
End-to-end implementation.
Powered by the OWA open Linux gateway family.
A fully integrated system: ruggedized hardware, custom embedded software, secure cloud brokers, and unified operational views. Every deployment uses preconfigured, git-versioned Linux images with secure OTA management. You own the gateway and every line of code that runs on it.
Managed operations.
Managed operations, or a full handover to your team.
Optional managed operations, with quarterly checkpoints so you can transition operations fully in-house at any time, with no clawback and no licensing surprises.
Why engage with us
Added value baked into every engagement.
Four commitments we build into every engagement, designed to remove the friction, the surprises, and the lock-in.
Open stack, end to end.
Open Linux gateways, open-core software, open data formats.
Owasys-class hardware, Linux, Yocto, Mosquitto, Kafka, TimescaleDB, Grafana. No proprietary lock-in at any layer between machine and database.
Customer-owned IP.
Source code, schematics, and machine data belong to you.
Every engagement ends with git-versioned source code, hardware schematics, production access credentials, runbooks, and the accumulated machine data. The system runs without us.
Customer support with fast response.
Engineering support from the team that built your system.
Support from the engineers who built your system, not a tier-1 call center. Fast response on incidents and direct access to the team that knows your stack.
Cost transparency.
Fixed-scope work, written budgets, no licensing surprises.
Every engagement starts with a written budget, and discovery is bounded by a clear go/no-go decision. There is no per-asset licensing, no clawback, and no per-feature upsell: the price you agree to is the price you pay.
Case studies
Proven in the field
Real engagements with mixed fleets and OEMs, with data brokered and stored on customer-owned infrastructure.
Concrete fleetCase 01 · Mobile fleet
Concrete fleet: drum rotation, slump proxy, work events
Monitor drum rotation, slump proxy, pressure, GPS, and work events for complete visibility, with data brokered and stored on the customer's infrastructure.
Read the case study
Hardware & ecosystemOWA open Linux gateways.
OWA open Linux gateways.
Open-core software stack.
Owasys is our authorized hardware partner, supplying production-grade OWA gateways engineered for harsh industrial environments.
The software path is industry-standard open core: Linux, Yocto, Mosquitto, Kafka, TimescaleDB, Grafana.
No proprietary lock-in at any layer.
How it works
Three steps from idea to running system.
Bounded engagements, written deliverables, and an explicit go/no-go at every gate.
Discovery
We work with your team to audit the existing stack and identify integration risks. The outcome is a feasibility report and a written architecture design, yours to keep, whether or not we build the system.
Planning
We translate the design into a delivery plan: bill of materials, work packages, milestones, budget, and an explicit go/no-go gate. Quarterly checkpoints, transparent budget, no surprises.
Execution
We build, integrate, and roll out ruggedized gateways, custom embedded software, secure brokers, and operational views. At handover, you keep the source, the schematics, the credentials, and the data.
Questions we hear often.
01What does Melqart Systems do?
We connect machines, vehicles and plant equipment to the systems your teams already use, so maintenance and operations see faults and status before anyone travels. We deliver the gateways, the embedded software and the integration as engineering projects.
02Where is Melqart Systems based?
Melqart Systems is an engineering company based in Luxembourg. We work in English, French and German.
03Which machines do you work with?
Mobile machines and vehicles such as concrete mixer trucks, cranes and bulk tanker trailers, as well as fixed plant equipment and sites.
04How is this different from buying a gateway?
A gateway is one part of the job. We start from the operating problem, for example diagnosing before travel, proving a delivery or documenting a cleaning cycle. Then we choose the hardware (usually Owasys open Linux gateways), write the software that runs on it and connect it to your systems.
05Who owns the software and the data?
You do. Machine data goes to infrastructure you control, and the source code we write for your project is handed over to you. There is no per-asset licensing.
06How does a project start?
With a short discovery: a few assets, the signals that matter and where the data has to end up. You get a written scope and budget, then decide go or no-go before any rollout.
Tell us what is failing quietly.
Share a few machines and the operating problem. Our engineering team in Luxembourg comes back with a proposed next step.