CASE STUDY / FEASIBILITY

One Mobility Network: from car park to service hub.

Existing infrastructure can become a platform only when the operating model, stakeholders and technology are designed together.

Editorial visual for One Mobility Network
Mobility HUBItalyConcept and architecture
FeasibilityProject stage
Smart mobilityPrimary context
360°Cross-functional view
Mobility HUBOrganisation / project
Project statusFeasibility study

THE PROJECT, EXPLAINED

Parking becomes a service node.

MOBILITY ECOSYSTEM

An architecture connecting mobility, energy and services.

Parking is treated as an access infrastructure for different services, with common governance for identity, availability, bookings and operating data.

A modular growth path allows charging, sharing and local services to be introduced without losing coherence between the physical node and the digital experience.

The model connects the physical hub, shared vehicles, the service corner and a common digital access layer.

From car park to mobility node

One Mobility Network starts with distributed infrastructure — staffed garages and car parks — and explores its evolution into service hubs. Parking becomes a base for car, scooter and bicycle sharing or rental, charging and local services, supported by a digital experience that connects different locations and operators. The concept also includes physical corners within the hubs, bringing direct-to-consumer and partner services closer to everyday mobility.

Rethinking the operating model

The challenge is organisational before it is technological. Infrastructure owners, managers, users and service partners need shared processes, standards and responsibilities. The work structures operating units, key activities, channels and customer relationships, showing how a parking-centred business can evolve towards a multi-service model.

A platform serving the network

The concept connects node access, vehicle availability, booking, payments, assistance and information. Common identity, data and workflows allow different services to coexist without fragmenting the user experience. Sensors and site automation support physical operations, while apps and platform services coordinate the customer relationship.

Validate before scaling

The proposed path is progressive: convert nodes, activate core services, integrate partners and gradually extend the network. This modularity allows demand, operations and sustainability to be tested for each block before replication across further sites.

Project360’s contribution

Project360 provided cross-functional technology consulting, analysis and project documentation. Its contribution connects the business model, journeys, digital requirements and operating dependencies, translating a broad vision into assessable modules and a common language for operators and partners.

Transferable value

The case shows how a physical network can become a platform without starting from software. Defining stakeholders, value exchanges and processes first reduces the risk of isolated features and creates a stronger basis for experiments and partnerships. It also makes the investment sequence visible, from adapting each physical node to activating shared digital capabilities across the network.

FROM PROJECT TO INDUSTRY

IndustriesSmart Mobility & Connected Infrastructure
Explore the complete portfolio

Does your project have many moving parts to connect?

We start from context, dependencies and the decisions needed to build a credible path.

Let’s talk
PRIVACY / CONSENT MODE V2

We use technical storage required by the site. Google Analytics remains blocked until you choose to allow anonymous usage measurement.