Connect road experience with analysis and technology to design clearer operating models and assess opportunities before scaling. From demand studies to devices, applications, business models and future fleets.
01 / STUDIES & RESEARCH
Practical questions. Useful decision inputs.
Define the question, required data and expected output before starting. These assessment tracks are scoped to each project.
MAJOR-PROJECT PROGRAMMES
The vehicle is part of a programme. The plan connects the details.
For multi-site and multi-shift projects, start with passengers, arrival windows and access, then review vehicle categories, routes and duration. Connect vehicle selection with a clear schedule and coordinating contact so your team can review delivery and confirmation points before agreement.
Our guides show how to allocate demand, review site or headcount changes and turn trip information into an action. Monitoring and connected applications are assessed against equipment, systems and scope: a reviewable decision and a programme the team can coordinate.
Project demandPassengers by site/shift and arrival window.
Movement planCategories, routes, frequency and returns.
Clear responsibilitiesWritten scope, coordinator and change approval.
Actionable monitoringUseful data, accountable action and review.
Designing a staff transport network: routes, fleet size and arrival plans
Staff transport must balance cost, journey length and reliable shift arrival. One vehicle may reduce direct expenditure while adding a long loop through several neighbourhoods. Two parallel routes may cost more but reduce passenger time and limit the impact of a disruption. Define priorities and acceptable service limits before selecting capacity.
This is an original Deal Master planning study, not a claim about a completed customer project. Its worked figures are explicitly hypothetical. The objective is a comparison whose assumptions can be checked, rather than a promise of a fixed saving.
Route design starts with real locations and journey times. Context photograph of Riyadh.
Cycle time changes fleet requirementsHypothetical example · departures every 12 minutes
36 min
3buses
48 min
4buses
60 min
5buses
Active buses = cycle time ÷ departure interval, rounded up. Reserve vehicles and driver breaks are excluded.
Demand and route design
Where is a bus needed, at what time and capacity?
What we examine
Meeting points, shifts, passenger counts and travel times.
Decision inputs
Comparable routes, capacity options and arrival windows.
Operating efficiency and fleet cost
How do we balance service quality and cost?
What we examine
Operating hours, distances, waiting time and maintenance.
Decision inputs
Clear measures of trip cost, vehicle utilization and service quality.
Evaluate innovation before scaling
Will this technology help this operation?
What we examine
A defined objective, available data and a bounded pilot.
Decision inputs
A review of benefits, compatibility and cost to inform the next step.
02 / DATA & AI
From scattered data to one operating picture.
A connected application model for requests, vehicles, drivers, maintenance and reports. Integration starts with existing systems, data quality and access roles.
Research review | data & devices
Fleet AI and bus occupancy: turn connected devices into reliable decisions
More devices do not automatically create better knowledge. Define the decision: explain delays, improve capacity allocation or close maintenance actions. Vehicle location answers a different question from passenger count. Connect each signal to an action and an accountable person.
A delay report should lead to a timetable or boarding review; a maintenance alert should lead to an inspection record. This is an operating model whose equipment and integrations depend on the project, not a claim that every vehicle has identical technology.
From a signal to an actionOperating model · not measured fleet performance
1Field devicesLocation, counts, alerts
2Unified recordJourney, vehicle, time
3ValidationMeasured or estimated?
4Action & reviewOwner, action, outcome
On-time performance
In-window runs ÷ included runs
Seat occupancy
Passengers ÷ seats at a defined point
User cost
Defined cost ÷ actual users
Vehicle availability
Available time ÷ required time
Use consistent definitions and reporting periods, and show missing data before comparing results.
Capacity and demand planning
Review occupancy and peaks to refine routes and vehicle allocation.
Safety and maintenance support
Interpret vehicle signals and alerts with human review and response plans.
Connected team and customer applications
Clear tasks, reporting and roles, with compatible system integrations.
Data quality first
Check accuracy and compatibility, and agree retention and access.
Operations overviewIllustrative demo
Schematic only. No live vehicle data.
Demo trips3
Sample occupancy82%
Safety statusReview
Maintenance alert1
01
Journey data
Vehicle, driver, route and request.
02
Connected platform
Access roles, integrations and reports.
03
Analysis & review
Occupancy, time, cost and alerts.
04
Operating decision
An accountable action and outcome review.
03 / TECHNOLOGY & DEVICES
Every device starts with a purpose.
Match equipment to the vehicle, purpose and compatibility, then define the alert or report the team needs.
Applied reading: connected bus equipment
Useful equipment answers an operating question.
Tracking supports location and journey-time review; passenger counting addresses capacity. Driver-monitoring cameras generate alerts requiring an agreed human response, while vehicle signals can support maintenance review. Combining these functions on one screen does not validate them. Operators need the source, refresh time and response to missing information.
Before installing equipment, review vehicle compatibility, connectivity, positioning and calibration. Choose an actionable alert or report and test weak connections, incomplete counts and false alerts. Record which values are measured and which are estimated. The linked study considers published occupancy research and a practical pilot before wider deployment.
Data should support safety and service with clear access roles. Assign an alert reviewer, appropriate retention and action approval. A connected application starts with consistent journey and vehicle records and may use APIs, files or validated manual entries. Actual equipment and integrations are confirmed within the project scope.
A dedicated path for businesses, investors and fleet operators: assess, decide and manage with visibility.
Feasibility | ownership & finance
Buy or hire a bus? A full-cost study of financing and operating risk
Buying creates an asset and operating responsibilities. Hiring may transfer some responsibilities to an operator, but the contract must identify which ones. A finance instalment and a monthly hire invoice are not comparable unless route, capacity, hours, days and continuity requirements match.
This is a planning framework, not a personal investment recommendation or finance offer. Actual supplier prices, finance terms and accounting treatment must come from the relevant parties. Unknown costs remain visible instead of disappearing from the comparison.
A future research and planning track at Deal Master. Assess electrification against the operation before committing to vehicles or infrastructure. Electric buses are not offered as part of the current bookable fleet.
FUTURE FLEET
2026 report | future fleets
Electric buses in 2026: market evidence and a Saudi route-readiness plan
IEA’s Global EV Outlook 2026 reports nearly 70,000 electric buses sold worldwide in 2025, up 12% year on year. Battery-electric vehicles represented 98% of electric-bus sales. Its definition covers buses with at least ten seats. These are global annual sales, not Saudi fleet totals or Deal Master inventory.
The article first reports published evidence, then offers an original local-readiness framework. Electric buses remain a future planning topic here rather than a currently bookable fleet category.
Dated selections from official transport news and data. Reporting periods and sources are shown separately from Deal Master’s own plans.
A news item starts the analysis; it does not decide your project.
We examine reporting periods, geography, service type and whether a number is observed or projected. Public-network growth does not establish demand on a staff route, and a seasonal service does not prove a model will work elsewhere. Each article follows the reported development with original analysis and practical planning questions.
Articles contain the full editorial text, then dated source links and related studies. The library connects news with capacity, scheduling and passenger-experience decisions. This is a reviewed editorial selection rather than a live feed or a claim that Deal Master operated the referenced projects.
Umm Al-Qura University’s Hajj research forum explored simulation, transport performance measures and field studies to improve bus movements and the pilgrim experience.
The Transport General Authority reported 23.2% year-on-year growth in urban public bus passengers in Q2 2026. These figures describe the Saudi transport sector.
Madinah’s dates season announced shuttles between Aliyah Mall and the central market for 20 July–2 August 2026, illustrating scheduled connections between visitor hubs and events.
