CASE STUDY

Playmoove in Saudi Giga Projects

A Digital Infrastructure for Integrated Mobility at Scale

← back to all Case Studies

Project Highlights

1,000+ vehicles

Large fleets and multiple vehicle categories involved across the implementations developed through Playmoove.

Saudi Arabia

Platforms configured to operate within the KSA’s technology and regulatory ecosystem.

Sharing + Ride Hailing + Shuttle Bus

Different mobility modes that can be managed or integrated within the same digital ecosystem.

Tamm + Tajeer + Yakeen

Integration with Saudi digital services supporting vehicle management, rental processes and data verification.

Cybersecurity & Data Protection

An architecture designed around applicable National Cybersecurity Authority requirements and Saudi Arabia’s personal data protection framework.

Software + Hardware Compliance

Security and data management addressed across the entire technology chain, from applications to the telematics devices installed in vehicles.

Play Connect

Playmoove middleware for integrating telematics, hardware and the platform.

Mobility as a Service

An architecture designed to progressively integrate new mobility operators and transport modes.

Playmoove in Saudi Giga Projects

Technology, integration and operational management to support the evolution of mobility across Saudi Arabia’s major development projects

Saudi Arabia’s major development projects are creating new districts, infrastructure and communities where mobility needs to be designed alongside other digital services.

In this context, Playmoove has been used to develop digital solutions for managing complex and continuously evolving mobility ecosystems.

The implementations covered in this case study involve thousands of vehicles and combine different mobility models, from vehicle sharing to collective transport services, with an architecture designed to integrate sharing, automated rental, ride hailing and shuttle bus services within the same ecosystem.

The objective is not simply to digitalise vehicle booking, but to build an infrastructure capable of coordinating users, vehicles, operations, telematics, data and integrations, while maintaining the flexibility to progressively introduce new services.

The projects behind this experience include both the management of large-scale corporate fleets and collective transport services, as well as shared electric mobility systems designed within territorial ecosystems that are still evolving.

The implementations were developed for our client and partner in Saudi Arabia as part of some of the country’s major territorial transformation and development projects.

These are environments where mobility represents a core infrastructure component: thousands of users, large fleets, different vehicle categories and transport services need to be coordinated within an operational environment that is continuously evolving.

The requirements extend well beyond vehicle usage and involve the entire process: user identification, authorisations, bookings, vehicle access, operational management, maintenance, telematics, security, data and integration with external systems.

The platform therefore needs to operate as part of the organisation’s existing digital environment and the wider Saudi digital ecosystem, rather than creating a separate technology infrastructure.

Managing mobility within major development projects involves very different requirements from those of an established urban or corporate environment.

On the one hand, daily journeys for employees, managers, authorised personnel and other user groups need to be organised while optimising large fleets made up of different vehicle types.

On the other hand, some infrastructure and services are being developed while the territory itself is still evolving. The system therefore needs to support current operational requirements without limiting the configurations and services that may be introduced later.

Having a large number of vehicles is not enough in itself. Fleet availability and vehicle status need to be visible centrally, access needs to be controlled, operational activities coordinated, and maintenance and fleet management organised in a structured way.

At the same time, not every journey needs to be made using a shared car. Shuttle bus, ride hailing and other collective or on-demand transport services can address different mobility requirements more efficiently.

The platform therefore needs to evolve from managing a single mode of transport to supporting an ecosystem in which different services coexist within the same digital infrastructure.

The main challenge was to build a platform capable of operating in environments characterised by large scale, high technological complexity and specific requirements for security, integration and data management.

The system needed to support both the people using the mobility services and the operators responsible for managing them on a daily basis.

The main requirements included:

managing users, profiles and different levels of authorisation;
enabling vehicle booking and usage;
supporting different vehicle categories and types;
automating access to the fleet;
monitoring vehicle availability and status;
managing maintenance and operational activities;
managing sharing, automated rental and collective transport services;
enabling integration with ride hailing and additional on-demand mobility services;
integrating hardware and telematics systems;
centralising documentation and information;
generating data and reports on fleet utilisation;
integrating with Saudi digital services and platforms;
meeting local cybersecurity, data protection and data residency requirements;
maintaining the ability to progressively introduce additional mobility services.

The platform therefore needed to go beyond the initial service configuration and retain the flexibility required to support the evolution of the entire ecosystem.

One of the main objectives was to use technology to centralise and simplify mobility management without creating separate systems for each individual service.

The platform needed to:

simplify access to mobility services for authorised users;
improve fleet utilisation efficiency;
reduce manual vehicle allocation processes;
centralise vehicle availability and status;
improve control over vehicle usage;
automate authorisation and operational processes;
structure maintenance activities;
provide dedicated tools for operators;
manage different vehicle categories;
integrate sharing, automated rental, ride hailing and shuttle bus services;
connect with local digital systems and institutional services;
ensure high standards of security and data protection;
adapt applications and processes to the linguistic and operational characteristics of the Saudi market;
prepare the infrastructure for integration with new services;
enable the system to scale without a proportional increase in operational complexity.

The objective was therefore not to introduce a simple booking system, but to create a technology foundation on which an integrated mobility ecosystem could progressively be developed.

The Playmoove Solution

Playmoove provided a modular and customisable platform through which the different components of the mobility ecosystem could be managed digitally.

Depending on the requirements of each project, the architecture can combine sharing, corporate mobility, automated rental, ride hailing and shuttle bus services, keeping users, fleets, operations and data within the same ecosystem.

The platform includes:

customised mobile applications;
web app;
administrative and operational back office;
user and profile management;
authorisation systems;
vehicle booking and access;
fleet management;
document management;
dedicated maintenance tools;
telematics and vehicle control;
payment systems;
shuttle service management;
integration with ride hailing services;
reporting and analytics;
APIs and integrations with external systems.

Customisation extends beyond the visual identity of the applications to include workflows, authorisation rules and operational processes.

For the Saudi market, applications and back-office tools have also been adapted to the Arabic language and its specific interface navigation and display requirements.

In major development projects, mobility is not simply a service to be digitalised: it is an infrastructure that needs to evolve together with the ecosystem it supports.

Sharing and Shared Fleet Utilisation

One of the core components is the ability to share vehicles among different users according to actual operational requirements.

Playmoove provides centralised visibility of vehicle availability and status and makes it possible to determine which users are authorised to access specific vehicle categories or services.

This model moves beyond a rigid system based solely on individual vehicle allocation: the same vehicle can be used by multiple people and respond more dynamically to actual mobility demand.

In ecosystems involving more than 1,000 vehicles, centralising this information becomes particularly important for maintaining fleet control, supporting operational activities and improving vehicle utilisation.

Fleet growth should not automatically result in an equivalent increase in operational complexity.

Sharing, Ride Hailing and Shuttle Bus Services in the Same Ecosystem

A large-scale mobility ecosystem cannot be built around a single mode of transport.

Individual journeys can be managed through shared vehicles or automated rental, while different mobility requirements can be served through ride hailing, shuttle buses and collective transport services.

Playmoove provides a common digital layer through which these different modes can be progressively coordinated.

For users, this means being able to access different services through an integrated environment. For operators, it means managing multiple mobility components through common tools, data and operational logic.

This approach moves the project towards a Mobility as a Service model, in which new mobility modes and operators can be introduced without creating a separate technology ecosystem each time.

Sharing, ride hailing and shuttle bus services can become components of the same digital ecosystem rather than independent services.

Integration with the Saudi Digital and Government Ecosystem

Operating in the Saudi market also requires the ability to connect with the country’s highly structured national digital ecosystem.

The platform has been designed to integrate with services and portals used in the Kingdom for vehicle management, contracts and user identification.

These include:

Tamm, used by companies operating in transport, vehicle sales and rental, as well as by organisations managing fleets. The service provides electronic access to General Traffic Department information and supports a range of vehicle-related transactions.

Tajeer, the platform dedicated to regulating vehicle leasing and rental operations, through which standardised rental contracts are issued and the rules defined by the Transport General Authority are applied consistently. Tajeer also integrates with Tamm for specific vehicle authorisation procedures.

Yakeen, an electronic verification service that enables authorised organisations to verify in real time the data of individuals with whom they maintain an official relationship, through connections with information held by the National Information Center and other official registries.

Integration with these systems enables the mobility platform to become part of the digital processes already in place in the Kingdom, avoiding the duplication of information or procedures that can instead be managed through national infrastructure.

An international platform needs to adapt to the local digital ecosystem: not only in terms of language and processes, but also through integration with the country’s institutional systems.

Play Connect and Telematics Integration

Communication between vehicles and the platform is a fundamental component of the architecture.

To manage this connection, Playmoove uses Play Connect, its middleware designed to create an intermediate layer between hardware and software.

Play Connect can acquire and normalise data generated by telematics devices installed in the vehicles and make this information available to the different functions of the platform.

Separating the software platform from the hardware also reduces dependency on a single telematics technology, making the infrastructure easier to adapt to different vehicles, suppliers and operational configurations.

This abstraction layer becomes even more important when the entire data chain needs to meet specific security and data localisation requirements.

Cybersecurity, Data Protection and Data Residency in the KSA

One of the most complex aspects of these implementations is the need to address security and data protection across the entire architecture, rather than only at application level.

The solution has therefore been designed taking into account the requirements applicable in the Kingdom to the management of digital systems and personal data.

From a cybersecurity perspective, the National Cybersecurity Authority (NCA) defines the Essential Cybersecurity Controls, together with specific controls relating to data security and cloud environments.

From a privacy perspective, the regulatory framework includes the Saudi Personal Data Protection Law (PDPL) and its implementing regulations, including those governing the transfer of personal data outside the Kingdom.

For this reason, requirements are considered across the entire technology chain:

mobile and web applications;
back office;
server and cloud infrastructure;
databases;
APIs and integrations;
authentication systems;
middleware;
telematics devices installed in vehicles;
communications between hardware and the platform;
external services used by the ecosystem.

Particular attention has been given to the hardware component. A telematics solution installed in a vehicle may rely on external middleware or cloud infrastructure and transfer information to data centres located in other jurisdictions.

Hardware and telematics choices therefore need to be assessed together with the software architecture, ensuring that the entire data flow is aligned with the requirements defined for the project.

This is why the most appropriate approach is compliance by architecture: software, infrastructure and hardware are treated as components of the same system.

Data protection does not end with the software: it covers the entire information flow, from the vehicle and hardware to middleware and cloud infrastructure.

An Ecosystem Open to Integrations

Within large-scale technology projects, a mobility platform cannot be designed as an isolated system.

Playmoove can connect with:

government and institutional systems;
identification and authorisation systems;
payment providers;
corporate IT infrastructure;
hardware and devices installed in vehicles;
localisation systems;
parking infrastructure;
ride hailing platforms;
shuttle and collective transport operators;
additional mobility services and operators.

The open architecture makes it possible to progressively introduce new integrations without creating separate technology ecosystems.

This approach is particularly important in major development projects, where infrastructure, operators and services may be introduced at different stages and need to evolve while retaining the ability to communicate with each other.

Managing Operational Activities

The platform is not designed solely for users booking or accessing a vehicle.

A significant part of its functionality is dedicated to the operators responsible for the day-to-day management of the services.

Through the Playmoove back office, it is possible to centralise:

vehicle availability and status;
bookings;
users and authorisations;
maintenance;
fleet operations;
documentation;
vehicle utilisation;
activities relating to different mobility services;
system data and indicators.

Centralised access to information provides greater fleet visibility and allows operational activities to be organised in a more structured way.

Playmoove therefore becomes a tool used daily both by people accessing mobility services and by the operators responsible for keeping those services running.

A Platform Designed to Scale

One of the most important aspects of the platform is its ability to evolve together with the projects it supports.

New users, vehicles, operational areas, features and transport modes can be progressively introduced within the same infrastructure.

Playmoove’s modular architecture makes it possible to add new services without having to redesign the entire system each time.

A configuration initially focused on vehicle sharing can therefore be progressively expanded to include automated rental, ride hailing, shuttle bus services and other transport modes, including autonomous vehicles.

This capability is particularly important in large-scale development projects, where volumes, infrastructure and operational requirements can change significantly over time.

Data and Reporting

Playmoove centralises the information generated by users, vehicles, bookings and operational activities.

Management teams and operators can use this data to monitor fleet utilisation, understand changes in demand and identify potential inefficiencies or opportunities for optimisation.

Information generated across different transport modes also makes it possible to build an increasingly comprehensive view of mobility demand.

Reporting therefore becomes not only a monitoring tool, but also an information base for supporting decisions regarding the organisation and future development of mobility services.

Results

The different implementations have made it possible to bring together within centralised digital infrastructures:

thousands of vehicles across the different implementations;
users and different levels of authorisation;
multi-category fleets;
vehicle sharing and corporate mobility;
automated rental;
shuttle bus and collective transport services;
integration readiness for ride hailing and on-demand services;
vehicle booking and access;
fleet management;
maintenance;
telematics;
document management;
payment systems;
integrations with Saudi digital services;
security and data management;
back office and reporting;
integrations with external platforms.

One of the most significant outcomes is the ability to use the same technology architecture as the foundation for different mobility models, progressively introducing new services as individual projects evolve.

Technology therefore becomes more than the layer used to digitalise an existing service: it becomes the infrastructure on which a broader mobility ecosystem can progressively be built.

Why Playmoove

Large-scale development projects require much more than an application for booking a vehicle.

They require the management of users and authorisations, large fleets, multiple transport modes, telematics, maintenance, operations, cybersecurity, data protection and integrations with external infrastructure.

They also require the ability to adapt to the specific digital and regulatory ecosystem of the market in which the service operates.

Playmoove combines a platform developed for different mobility models with a high degree of configurability and customisation.

Its modular architecture makes it possible to integrate sharing, automated rental, ride hailing and shuttle bus services; Play Connect separates the software layer from the telematics hardware; while APIs and middleware connect the platform with corporate systems, external operators and national services such as Tamm, Tajeer and Yakeen.

The ability to manage the entire architecture — from applications and telematics to data localisation and processing — also enables the system to be configured around the specific cybersecurity, privacy and data residency requirements applicable in the Kingdom.

The experience gained across Saudi Arabia’s major development projects demonstrates how Playmoove can evolve from a solution for managing shared fleets into a digital infrastructure for integrated, scalable, interoperable and progressively multimodal mobility ecosystems.