Transportation
Decisions that have to arrive before the traffic does
In transport, a decision taken late is a decision that no longer applies. The deadline comes from the physical world, and everything upstream of it — devices, links, platform — has to be designed to meet it.
Context
Industry context
What shapes technology decisions in this sector.
Transport is the sector where latency stops being an engineering preference and becomes a hard requirement. Anything that changes what a driver sees or what a signal does inherits a deadline nobody negotiated.
Field equipment usually comes from several suppliers, installed at different times, and has to behave as one system regardless. That is an integration problem before it is a mobility problem.
Maintenance access is a real constraint. Equipment that needs a lane closure to service carries a cost that does not appear in its purchase price, and it changes which designs are sensible.
Constraints
Key operational challenges
The conditions any solution here has to work within.
- 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.
Capabilities
Relevant ZouhThings capabilities
What we can bring to this sector, stated as capability rather than track record.
Connected mobility platforms
Relevant to fleet and mobility operations, drawing on the platform work from our partnership in Spain.
Field device integration
Designed for making equipment from several suppliers behave as one system rather than several dashboards.
Latency-aware architecture
Can support functions with hard deadlines by writing the latency requirement per function rather than per system.
Operational analytics
May enable understanding demand patterns over time, which tolerates delay well and informs planning rather than control.
Solutions
Relevant solutions
Solution areas that apply here. Each links to how it is delivered.
Platforms
Relevant platforms
Platforms that would apply to this sector.
- MingoThings Mobility
- thethings.io
Applications
Example use cases
Possible applications, to show the shape of the work.
Corridor instrumentation
Possible use cases include instrumenting a single corridor to understand flow before extending to a network.
Fleet condition and utilisation
Can support tracking vehicle condition, driving behaviour and maintenance need alongside position.
Cold-chain transport monitoring
May enable monitoring temperature-sensitive loads throughout a journey, with an alert before a consignment is lost.
Signal and detector visibility
Designed for surfacing when a detector or controller has stopped reporting, which is otherwise indistinguishable from quiet traffic.
These are possible use cases, described to illustrate what the technology can support in this sector. They are not descriptions of completed work, and none should be read as a reference. Where a confirmed project exists, it will be named and linked under Related projects.
Security
Security considerations
What has to be decided early rather than added later.
Field equipment identity
Roadside equipment is physically accessible, so device identity and revocation matter more than in a controlled environment.
Separation from control functions
Relevant where a monitoring system must not be able to influence a signal or a safety function.
Update paths without site visits
Designed so firmware can be updated remotely, because a lane closure per update is not sustainable.
Data on movement handled carefully
Movement data can be sensitive even when it is not personal; retention and access decided at design time.
This describes how we approach security in this sector. It is not a claim to hold any specific certification, accreditation or compliance attestation — where one exists, it will be named.
Integration
Integration considerations
Where the difficulty usually sits in this sector.
Installed controllers first
Designed for working with controllers and management software already in service rather than assuming replacement.
One system from several suppliers
Can support normalising differing protocols and message formats so operations reads one picture.
Behaviour during outage
Local buffering with clear separation of observed and received times, so a backlog is not mistaken for an incident.
Procedures as part of the design
Relevant because a system that requires attention nobody has spare will be worked around, and the workaround becomes the real system.
Evidence
Related projects
Confirmed work in this sector, where any is published.
No project is published for this sector yet. When one is confirmed and approved for publication, it will appear here — so an empty section means exactly that, rather than work we cannot discuss.
Next step
Discuss a requirement in this sector
The useful conversation is usually about a specific asset, site or corridor rather than the sector in general.