Industries
Sectors where systems have to keep running
The problems change between a water utility and a telecom operator, but the hard part is usually the same one — making new technology work with what is already installed, and keeping it working afterwards.
Overview
Industries overview
How we think about sector differences, and what does not change between them.
We work across eight sectors. What differs between them is the deadline the physical world imposes, the accountability attached to the data, and how expensive it is to reach the equipment. A traffic signal and a water meter are both connected devices, but one has a decision deadline measured in seconds and the other in days.
What does not differ is where the difficulty sits. In every sector, the equipment that already exists outlasts the project that adds to it, someone has to operate the result, and the integration is harder than the installation. Those constraints shape how we scope work far more than the sector label does.
Each card below states what makes that sector hard and which of our solution areas apply to it. It is a description of fit, not a record of delivery.
Sectors
Industries we build for
Eight sectors, with the constraints that shape work in each.
Government
Public bodies modernising services while working with installed systems, procurement rules and data they are accountable for.
Key challenges
- Systems bought at different times, by different departments, that now have to exchange data.
- Accountability for where operational data lives, who may see it, and how long it is kept.
- Procurement and budget cycles that make phased delivery easier to fund than a single large programme.
- Services that must remain available while they are being replaced.
Relevant platforms
- MingoThings Mobility
- thethings.io
Telecommunications
Operators running networks that other sectors depend on, where visibility and response time are the product.
Key challenges
- Monitoring distributed infrastructure without sending an engineer to find out what happened.
- Power and environmental conditions at sites that are expensive to reach.
- Operational data spread across tools that were never designed to be read together.
- Security expectations that apply to the network and to the systems managing it.
Relevant solutions
Relevant platforms
- thethings.io
Transportation
Authorities and operators managing movement, where a decision taken late is a decision that no longer applies.
Key challenges
- Field equipment from several suppliers that has to behave as one system.
- Data that is only useful inside a deadline set by the physical world.
- Maintenance access that may require closing part of a road.
- Fleets whose condition and position matter as much as their location.
Relevant solutions
Relevant platforms
- MingoThings Mobility
- thethings.io
Utilities
Water and network operators where loss, leakage and unplanned downtime are measured in resources as well as money.
Key challenges
- Faults that are only visible after the service has already failed.
- Meter reading and inspection that still require site visits.
- Assets spread thinly over distance, often without mains power.
- Billing and monitoring data that need to agree with each other.
Relevant solutions
Relevant platforms
- MingoThings Mobility
- thethings.io
Energy
Generation, storage and distribution where the mix of sources makes consumption harder to see than to pay for.
Key challenges
- Sites running on a mix of grid supply, generators, batteries and solar.
- Equipment condition that is only checked on a schedule, not continuously.
- Fuel and generator running costs that are hard to attribute.
- Production and consumption data that arrive in different formats.
Relevant solutions
Relevant platforms
- thethings.io
Healthcare
Providers whose facilities must stay within tolerance, and whose data carries obligations beyond the technical.
Key challenges
- Cold-chain and environmental conditions that must hold continuously, not on average.
- Building systems — power, cooling, water — that support services which cannot pause.
- Patient-related data with confidentiality obligations that shape system design.
- Equipment and consumables that need to be traceable.
Relevant platforms
- thethings.io
Education
Universities and schools running estates and networks for a population that arrives and leaves in waves.
Key challenges
- Campus utilities and buildings whose consumption changes sharply with the timetable.
- Networks that must serve many devices nobody centrally manages.
- Access control and safety systems usually managed separately from everything else.
- Limited operational staff relative to the number of sites.
Relevant solutions
Relevant platforms
- thethings.io
Manufacturing
Plants where unplanned downtime is the expensive event, and most of the useful signal is already in the equipment.
Key challenges
- Machines that fail between scheduled maintenance intervals.
- Production data held in equipment that does not readily share it.
- Energy use per line or machine that is not separately measured.
- Older equipment that has to be instrumented without being replaced.
Relevant solutions
Relevant platforms
- thethings.io
These cards describe the sectors we build for and the capabilities that apply to them. They are not a customer list, and listing a sector is not a statement that we have delivered a project in it — where a project or case study exists, it will be named and linked. Nothing on this page should be read as a reference.
Common ground
Cross-industry capabilities
The parts of the work that look the same whichever sector it is in.
Connecting equipment that already exists
Most sites are not empty. The work usually starts with installed controllers, meters and management software that have to keep operating while something new is added alongside them.
Getting operational data into one place
Readings are rarely missing so much as scattered across tools that were never meant to be read together. Bringing them into one view is often the whole gain.
Deciding what counts as an alert
A system that cries wolf gets muted, and a muted system is worse than none because it carries an assurance nobody can rely on. Alert thresholds and routing are a design decision, not a configuration step.
Building for the handover
Someone operates what we deliver. Documentation, alert ownership and maintenance access are part of the work rather than paperwork after it.
Working in Arabic and English
Interfaces, documentation and support in both languages, because operations teams and the people who procure for them do not always read the same one.
Starting narrow enough to fail safely
A single corridor, pump or production line, instrumented properly and run long enough to see bad weather and an outage, teaches more than a broad deployment that has never been stressed.
Approach
Security and integration approach
How we treat the two things that decide whether a connected system survives contact with operations.
Security designed in, not added
Device identity, network segmentation, access control and update paths are decided while the architecture is being drawn. Retrofitting them means touching every device already installed.
Integration is the deliverable
New equipment is straightforward; making it coexist with installed systems and established procedures is where the schedule goes. We scope that explicitly instead of treating it as a final step.
Data ownership settled early
Who may see operational data, who may act on it, how long it is kept and what happens to it at the end of a contract. Left unsettled, this surfaces at the worst possible moment.
Designed for the link dropping
Connectivity fails. Systems should buffer locally, resynchronise on recovery, and make late data distinguishable from live data rather than presenting a backlog as a sudden event.
This describes how we approach security and integration. It is not a claim to hold any specific certification or formal accreditation — where a certification exists, it will be named.
Next step
Discuss a sector-specific requirement
The useful conversation is usually about a particular asset, corridor or site rather than a sector in general.