Partner technology platform

MingoThings Mobility

Partner platformProvided by MingoThings

A smart mobility and fleet management platform provided by MingoThings, our technology partner in Spain. ZouhThings deploys it, integrates it with the systems an operator already runs, and supports it locally.

Ownership and attribution

MingoThings Mobility is developed and owned by MingoThings. ZouhThings deploys, integrates and supports the platform for organisations in the region. ZouhThings does not own or develop the platform, and this page does not describe any resale, exclusivity or territory arrangement.

Platform overview

What the platform is, and what ZouhThings does with it

MingoThings Mobility is a commercial smart mobility and fleet management platform. It is the platform layer ZouhThings works on for transport and fleet projects, rather than something built from scratch for each operator.

What distinguishes the platform in the work ZouhThings does with it is that fleet operations are treated as more than vehicle position. Vehicle condition sits alongside location, which is the difference between knowing where a vehicle is and knowing whether it should be in service.

This page states what has been confirmed in writing. Platform detail that needs partner-approved product information is marked as awaiting confirmation rather than filled in with something plausible.

What ZouhThings does

  • Deployment and configuration for the operator's own fleet and routes.
  • Integration with existing maintenance, scheduling and enterprise systems.
  • Local support, in Arabic and English, in the same time zone as the operator.
  • Training and operational handover to dispatch and maintenance teams.

The problem

Mobility challenges

These are characteristic difficulties in transport and fleet operations. They explain what a mobility platform is for, and are not a list of features of any particular platform.

  • Position without context

    Knowing where a vehicle is does not say whether it is roadworthy, on schedule, or carrying passengers. Location alone leaves the operational question unanswered.

  • Reactive maintenance

    When a fault is discovered by breakdown rather than by observation, the cost is a vehicle out of service at the least convenient moment, plus the disruption to the service it was running.

  • Fragmented systems

    Dispatch, maintenance, fuel and scheduling are frequently separate systems that do not share a view of the same vehicle. Staff reconcile them by hand.

  • Schedule adherence is hard to see

    Without route and timing data collected consistently, whether a service actually ran as planned is reconstructed after the fact rather than observed as it happens.

  • Mixed and ageing fleets

    A fleet is rarely one make, one model or one generation of equipment. Any approach that assumes uniform vehicles fails on the older half of the fleet.

  • Data that does not reach decisions

    Operational data is often collected but not brought to the people planning services, so the same problems recur across seasons.

Capabilities

Core capabilities

The capabilities below are the ones with an approved written basis. The remaining candidates are listed separately by name only: they are ordinary for a mobility platform, but they have not been confirmed against partner-approved product information, so this page neither describes them nor presents them as capabilities. Each will be moved up once MingoThings supplies that information.

  • Fleet and mobility operations

    The platform is used for running fleet and mobility operations rather than for reporting on them after the event.

  • Vehicle condition

    Vehicle condition is available alongside position, which is what allows a decision about service readiness rather than only about location.

  • Vehicle position

    Vehicle location across the fleet, which the approved platform description treats as the baseline the condition data is added to.

Candidate capabilities awaiting partner-approved information

Awaiting approved documentation from the platform provider.

  • Passenger information
  • Operational analytics
  • Route and schedule monitoring
  • Mobility data integration
  • Control-centre dashboards
  • Alerting and thresholds

Applications

Typical use cases

  • Public transport operations

    Can support an operator running scheduled passenger services, where vehicle availability and service adherence both matter daily.

  • Fleet visibility

    Designed for organisations that need one view of a fleet rather than a separate answer from each depot or each system.

  • Vehicle tracking

    Relevant to operations where knowing the current location of every vehicle is the starting point for dispatch decisions.

  • Passenger information

    May enable operational data to feed the information given to passengers, subject to confirming what the platform provides for this.

  • Operational analytics

    Relevant to reviewing how a service actually performed over time, rather than relying on recollection.

  • Route and schedule monitoring

    Can support comparing what was planned against what ran, as a routine operational review rather than an investigation.

  • Mobility data integration

    Designed for cases where mobility data has to reach existing maintenance, scheduling or enterprise systems to be acted on.

  • Control-centre dashboards

    Relevant to a dispatch or control function that needs the current operational picture on screen continuously.

Possible use cases include the applications above. They describe operational needs that smart mobility deployments address and that ZouhThings works on. They are not a list of product modules, and no delivered customer deployment is described on this page. Confirming which of these MingoThings Mobility covers in its current release requires partner-approved product information.

Architecture

Platform architecture

The platform's architecture will be described here from partner-approved information. ZouhThings' own approach to integration architecture is described on the Systems Integration page.

Information to be supplied

Platform architecture

Awaiting approved documentation from the platform provider.

Operations

Operational dashboards

Which operational views the platform provides, and how far they can be configured for a specific operator, is being confirmed with MingoThings.

Information to be supplied

Operational dashboards

Awaiting approved documentation from the platform provider.

Integration

Integration options

The platform's supported integration routes will be listed here once confirmed. Integration into existing maintenance and scheduling systems is work ZouhThings does, and is described on the Systems Integration page.

Information to be supplied

Integration options

Awaiting approved documentation from the platform provider.

Who it is for

Target organisations

  • Public transport authorities

    Bodies responsible for scheduled passenger services across a city or region.

  • Municipal fleet operators

    Municipalities running service vehicles, from waste collection to maintenance fleets.

  • Passenger transport companies

    Private operators running bus, coach or shared passenger services.

  • Logistics and distribution fleets

    Organisations whose vehicles are the delivery mechanism for their business.

  • Utility and infrastructure field fleets

    Operators whose crews travel to dispersed assets, where vehicle and job data belong together.

  • Government vehicle fleets

    Public bodies accountable for the use, condition and cost of a vehicle fleet.

These are the kinds of organisation the platform and ZouhThings' deployment work are relevant to. Listing an organisation type is not a statement that ZouhThings has delivered a project for one.

Partnership

Partnership attribution

MingoThings

Strategic technology partner

MingoThings is the provider of the MingoThings Mobility platform and a strategic technology partner of ZouhThings. ZouhThings deploys, integrates and supports the platform for organisations in the region.

Awaiting approved wording from the partner.

What this partnership does not imply

  • ZouhThings does not own, develop or control the MingoThings Mobility platform.
  • The partnership does not grant ZouhThings exclusivity in any market or territory.
  • Nothing on this page describes a resale, distribution or licensing arrangement.
  • No statement here should be read as a legal relationship between the two companies beyond a technology partnership.
MingoThings logoImage to be supplied

Next step

Request a demonstration

ZouhThings can show the platform running with live data, and explain how it would be deployed for a specific fleet.

TEXPO Damascus

See the platform at TEXPO

ZouhThings and MingoThings are exhibiting jointly at TEXPO in Damascus, on a stand registered under the MingoThings name.

MingoThings Mobility is demonstrated running with live data rather than presented as slides. Stand, dates and the full demonstration list are on the TEXPO page.