Ministry of Transport, Malta — Queue Management Across All Hubs
Vehicle licensing + driver services + transport permits, queued through one consistent citizen flow.
Ministry of Transport, Malta
Malta's Ministry of Transport runs the country's vehicle licensing, driver services, and transport-permit programmes. Service hubs see high citizen volume tied to renewal cycles (licence expiry, vehicle inspection windows) with predictable spikes. Citizens previously queued in a single FIFO across multiple unrelated transaction types — a license renewal sat behind a driver-test booking sat behind a complex vehicle-transfer case. Per-visit-reason segmentation was the clear opportunity.
The Zeour stack at Ministry of Transport, Malta
GLARUS queue management deployed across the Ministry's service-hub network: service-type definitions per transaction (renewal vs. new application vs. test booking vs. transfer), skill-routing so the right counter handles the right transaction, central rule configuration via MSA / GLITT, and per-hub execution via EMS. Live queue boards at each hub. Reporting via the central CIO console: per-hub throughput, per-reason CSAT, peak-hour staffing recommendations.
Phased engagement — Discovery → Build → Pilot → Roll-out → Operate
Discovery covered every Ministry of Transport service hub with per-hub catalogue documentation: vehicle licensing flows, driver-service flows, transport-permit flows. The fixed-fee Statement of Work covered MSA/GLITT central rule configuration plus per-hub EMS execution + lobby queue boards. Build phase delivered service-type definitions per transaction type (renewal vs. new application vs. test booking vs. transfer) with explicit skill-routing per counter. Pilot at the largest hub validated the segmentation assumptions — peak-hour throughput improved enough during pilot to commit to network rollout without further changes. Subsequent hubs rolled out phased over weeks, with the Ministry's ops team running the cutover under Zeour observation. Operate runs in-house with the Care Plan as a fall-back for incident escalation.
Operational outcomes the deployment enabled
Single-FIFO queueing across mixed transaction types replaced with per-visit-reason routing. The four-minute license-renewal customer no longer waits behind a twenty-five-minute vehicle-transfer case. Service-type definitions live centrally in MSA/GLITT — when policy changes, the new rule propagates across all hubs same-day rather than requiring per-site redeployment. Reporting shifted from per-hub manual aggregation (the historical pain point) to a central CIO console with per-hub + per-reason rollups. Counter-staff capacity now visible per hub in real time, which informs staffing decisions during predictable seasonal spikes (licence-expiry windows, post-inspection waves).
Zeour solutions in production at Ministry of Transport, Malta.
What this deployment delivered.
License vs. new application vs. test vs. transfer — separate routing.
Single central console; per-hub execution autonomy.
Per-hub + per-reason rollup replaces manual aggregation.
Other production references close to this one.
Ranked by overlap on industry, country, region, and shared solutions deployed.
Talk to the engineers who shipped this.
A 30-minute scoping call to walk your operational profile against this reference, then a fixed-fee Discovery price by the end of the call.
Glossary — concepts in this deployment
Definitions for the operational terms behind this case. Open any chip for the full entry plus its cross-links across the site.