ISO/TR 7878:2023

TECHNICAL ISO/TR
REPORT 7878
First edition
2023-02
Intelligent transport systems —
Mobility integration — Enterprise
view
Systèmes de transport intelligents - Intégration des services de la
mobilité - Vue globale des rôles des organisations et des relations avec
les utilisateurs
Reference number
© ISO 2023
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on
the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below
or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 2
5 Mobility service and transport service . 2
5.1 Mobility service . 2
5.2 Transport service . 3
6 The core enterprise objects in the provision and use of mobility services .4
6.1 Overview . 4
6.2 Mobility service user responsibilities. 5
6.3 Mobility service provider responsibilities . 7
6.4 Transport service provider responsibilities . 8
7 Regulating, governing and supporting enterprise objects . 9
7.1 Regulator . 9
7.1.1 Overview . 9
7.1.2 Regulator responsibilities . 11
7.2 ICT service providers . 12
7.2.1 Overview . 12
7.2.2 ICT service provider responsibilities .13
7.3 Transport infrastructure operator . 15
7.3.1 Overview . 15
7.3.2 Transport infrastructure operator responsibilities . 16
7.4 Payment service provider . . 16
7.4.1 Overview . 16
7.4.2 Payment service provider responsibilities . 17
Bibliography .19
iii
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing International Standards is normally carried out
through ISO technical committees. Each member body interested in a subject for which a technical
committee has been established has the right to be represented on that committee. International
organizations, governmental and non-governmental, in liaison with ISO, also take part in the work.
ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of
electrotechnical standardization.
The procedures used to develop this document and those intended for its further maintenance are
described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the
different types of ISO documents should be noted. This document was drafted in accordance with the
editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of
any patent rights identified during the development of the document will be in the Introduction and/or
on the ISO list of patent declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not
constitute an endorsement.
For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and
expressions related to conformity assessment, as well as information about ISO's adherence to
the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see
www.iso.org/iso/foreword.html.
This document was prepared by Technical Committee ISO/TC 204, Intelligent transport systems.
Any feedback or questions on this document should be directed to the user’s national standards body. A
complete listing of these bodies can be found at www.iso.org/members.html.
iv
Introduction
Urbanization, changes in climate and demographic and societal changes are some of the major trends
that have had an impact on transport systems and services over the last decades. Combined with
the implementation of ITS services and Internet of Things (IoT), new transport concepts have been
developed. User requirements on efficiency, availability and interoperability have also been driving
forces for new transport concepts for the integration of multimodal, existing and new transport services
as described and implemented in mobility concepts like Mobility as a service (MaaS) and Mobility on
Demand (MOD). Cooperative, connected and automated mobility (CCAM) will also have a significant
effect on how travellers plan and implement their journeys between multiple modes of transport in the
integrated mobility environment.
Integrated mobility concepts are evolving around the world, mostly based on the MaaS and MOD
concepts. Hence, there is a need for a generic, common and world-wide concept description mapping
all existing and foreseen concepts for interoperable, integrated and seamless multimodal transport
services.
The role and responsibility models for MaaS and MOD have already been described in ISO/TR 4447, but
there is also a need for a common role and responsibility model for integrated and multimodal mobility
services, recognizing and including the work already done by the two mainstream organizations for
integrated mobility services, MaaS and MOD. A common role and responsibility model can be described
[3]
from an enterprise view where the stakeholders, actors and roles in the MaaS/MOD ecosystem
are merged into one enterprise view. The enterprise view addresses the relationships between the
entities (e.g. organizations) involved in the provision of the mobility services. However, there is also
a need for enhancing the MaaS and MOD models to include more services, e.g. security services,
certification services and interoperability management. The following documents have been used for
the enhancement of the common MaaS/MOD model (ecosystem):
— ISO 24014-1 on interoperable fare management;
— ISO 17573-1 on electronic fee collection;
— ISO/TR 21724-1 on common transport service account systems;
— EN 12896-5 on public transport fare management.
The objective of this document is to describe integrated mobility from an enterprise view to which
existing implementations of integrated mobility systems can potentially be mapped. This is intended
to enable a common understanding, an exchange of information and knowledge, and a convergence
towards one world-wide integrated mobility concept description.
v
TECHNICAL REPORT ISO/TR 7878:2023(E)
Intelligent transport systems — Mobility integration —
Enterprise view
1 Scope
This document describes the enterprise view (see ISO/TS 14812:2022, 3.1.4.3) of integrated mobility
based on the role and responsibility models in the mobility as a service (MaaS) and mobility on demand
(MOD) ecosystems as described in ISO/TR 4447. Other ISO documents (e.g. ISO 24014-1, ISO 17573-1
and ISO/TR 21724-1) have been reviewed in order to enhance and merge the MaaS and MOD role models.
The enterprise view addresses the relationships between organizations and users, and the roles those
entities play in the delivery and consumption of mobility services. Relationships between entities are
[3]
dependent on the roles those entities take in the delivery of user services.
Enterprise objects interact to exchange information, manage and operate systems beyond the scope of
one organization. The enterprise view focuses on the relationships between those enterprise objects,
but also defines how enterprise objects interact with physical objects, which appear in the enterprise
view as "resources".
This document focuses on mobility service concepts where the included transport services are publicly
available. Examples of such transport services are listed in Clause 3.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO/TS 14812, Intelligent transport systems — Vocabulary
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/TS 14812 and the following
apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— ISO Online browsing platform: available at https:// www .iso .org/ obp
— IEC Electropedia: available at https:// www .electropedia .org/
3.1
mobility service
service that provides an integrated interface for multiple transport services
Note 1 to entry: The integrated interface can include an online interface, a payment interface, and/or rules for
physically accessing the various transport services.
Note 2 to entry: The typical goal of a mobility service is to fulfil the needs of a transport user in an optimal
fashion, even if that requires using multiple transport services.
3.2
mobility service provider
entity that delivers one or more mobility services
4 Abbreviated terms
AI artificial intelligence
ARC-IT Architecture Reference for Cooperative and Intelligent Transportation
GNSS Global Navigation Satellite System
ICT information and communication technologies
IFM interoperable fare management
IFMS interoperable fare management systems
ITS intelligent transport systems
MaaS mobility as a service
MOD mobility on demand
PT public transport
PTA public transport authority
PTO public transport operator
UITP Union Internationale des Transport Publics
USDOT United States Department of Transportation
VRU vulnerable road user
5 Mobility service and transport service
5.1 Mobility service
Integrated mobility is based on two crucial services: the mobility service and the transport service.
The European MaaS concept describes a mobility service as the integration of various forms of
[4]
transport services into a single mobility service accessible on demand. According to Reference [4],
the core purposes of the service are:
— to facilitate a diverse menu of transport alternatives, for example public transport, ride-sharing,
car-sharing, bike-sharing, taxi or car rental/lease, or a combination thereof;
— to offer added value to the user through the use of a single application to provide access to mobility,
with a single payment channel instead of multiple ticketing and payment operations;
— to be the best-value proposition for users by helping them to meet their mobility needs and solve the
inconvenient parts of individual journeys as well as the entire system of mobility services.
The main goal of the mobility service is to provide an alternative to the use of the private car that can
be as convenient, more sustainable, help in reducing congestion and constraints in transport capacity,
[4]
and reduce costs.
The United States Department of Transportation (USDOT) uses the term mobility on demand (MOD) to
represent its vision for future mobility, which is a safe, reliable and carefree mobility ecosystem that
[11]
supports complete trips for all, both personalized mobility and goods delivery.
According to Reference [11], the core purpose of the service is:
— to leverage innovative technologies and facilitate public private partnerships to allow for a user-
centric approach that improves mobility alternatives for all travellers and the delivery of goods and
services.
USDOT’s MOD vision does recognize private car for private use as a possible mobility service option for
some, just like walking and cycling.
The International Association of Public Transport (Union Internationale des Transport Publics - UITP)
defines the mobility service as the integration of, and access to, different transport services (such as
public transport, ride-sharing, car-sharing, bike-sharing, scooter-sharing, taxi, car rental, ride-hailing,
etc.) in one single digital mobility offer, with active mobility and an efficient public transport system as
[1]
its basis.
According to Reference [1], the core purposes of the service are:
— to provide a tailor-made service suggesting the most suitable solutions based on the user’s travel
needs;
— to be available anytime and to offer integrated planning, booking and payment, as well as en-route
information in order to provide easy mobility and enable a way of living that does not require car
ownership.
These three definitions for the term "mobility" service can be synthesized as:
A mobility service is the integration of, and access to, different transport services that are
integrated into a single mobility service representing the best value proposition for the user and
being accessible anytime on demand.
In this document, the term "mobility service" is defined as a service that provides an integrated
interface for multiple transport services; see 3.1.
5.2 Transport service
The term transport service is defined in ISO/TS 14812 as a service that delivers one or more material
entities from one location to another to satisfy a need. A note to the definition says that the entities
delivered can be people and/or goods.
Figure 1 shows the relationship between a mobility service and multiple transport services. In the
example shown in the figure, the user used a mobility service provider to generate alternatives for
transport from A to B. In this example, the user receives three different proposals representing the
"lowest cost", most "environment-friendly" and "fastest" way to get from A to B. Two of the proposals
include walking between transport services while the third one is a single door-to-door transport
service, e.g. by taxi.
Key
a subway line 1 (jurisdiction A)
b subway line 2 (jurisdiction A)
c bus line 3 (jurisdiction B)
d bus line 4 (jurisdiction A)
e bus line 5 (jurisdiction B)
f e-scooter sharing (privately operated)
g car (e.g. taxi)
NOTE Each link (i.e. key references "a" through "g") represents a transport service.
Figure 1 — The relationship between mobility services and transport services
Transport services are categorized in different ways by different concepts, e.g. the MaaS, MoD and
UITP concepts. A synthesis of different categories can be summarized in the four main attributes that
describe a transport service.
1) Accessibility: whether the transport service is accessible by the public or only for private access.
2) Financing: whether the transport service is fully or partly financed by the authorities, or if it is
commercial, it is a public-private financial model, it is mutual benefit, fractional or completely paid
by the user.
3) Item transported: whether it is a person or goods.
4) Operational: whether the service is sequential or concurrent, where concurrent can be further
divided into fixed-route, dynamic route and paired on-demand.
6 The core enterprise objects in the provision and use of mobility services
6.1 Overview
Figure 2 shows an enterprise view of the three core objects, "mobility service user", "mobility service
provider" and "transport service provider", based on the responsibilities described in 6.2 to 6.4.
The enterprise view presented in Figure 2 is based on a service provider model where the mobility
service provider buys the transport services from the different transport operators and resells them
under their own conditions, i.e. by repackaging and repricing the services. In this model, the mobility
service provider would take over the user relations including responsibilities. From a legal point of
view, issues could arise around the pricing, e.g. for public transport services where fares and discounts
[2]
are often fixed by laws or regulations that have to be respected.
NOTE See Reference [2] for a description of other models, e.g. agency model, merchant model and
transactional model.
Sharing of data and responsibilities as well as commercial rules are crucial issues in integrated mobility
service ecosystems.
Key
enterprise centre
enterprise personal
Figure 2 — Enterprise view for the three core enterprise objects
6.2 Mobility service user responsibilities
The enterprise object using the mobility service is called the mobility service user. The user is very often
the entity that requests the mobility service, selects the mobility service fulfilling the user needs and
preferences, uses the service and pays for it. However, the user responsibilities/activities can be divided
between different persons, organizations, legal entities etc. This is also the case in interoperable fare
management systems (see ISO 24024-1) where the public transport user is divided into the enterprise
objects, "passenger" and "customer". The passenger is the person travelling with the public transport
means and the customer is an entity that has an explicit or implicit agreement with the product owner
via a retailer and pays for the service. e.g. a parent books and pays a public transport service for a child
and an employer book and pays for an employee. This could also be the case for mobility services.
The MOD also includes the transport of goods, in which case the user is not travelling, but the user is
still the entity that requests the mobility service, selects the mobility service fulfilling the user needs
and preferences, uses the service and pays for it.
Mobility services also include transport services where the user is not a passenger, but rather the
driver of the transport means used for the transport service. Finally, the user of a mobility service will
sometimes be a non-motorized user as part of a mobility service, e.g. when walking from one transport
service to another transport service being part of the mobility service.
1)
The term vulnerable road user (VRU) is described in ISO/TR 24317:— . The term is differently defined
in regulations and standards published by SAE, European Union and ETSI. In relation to mobility
services, a VRU could be both a driver and a non-motorized user.
Table 1 shows how other transport service concepts have named the user of the service, thereby enabling
a comparison of the roles in this document with similar roles in MaaS, MOD and UITP documents and in
other ISO documents involving a user of a transport-related service.
Table 1 — Terms related to "mobility service user" in other transport-related documents
Term used in MaaS MOD UITP ISO 24014-1 ISO ISO/TR EN 12896-5
this docu- 17573-1 21724-1
ment
Mobility ser- Customer Consumer Traveller Customer User of the Transport Transport
vice user service service user user role
NOTE Customer Passenger
Customer
is some-
times called
“Mobility
Manager”
in the US.
(MOD)
Based on the descriptions of the enterprise object responsibilities in the 7 reference sources listed in
Table 1 and a further detailing of those, the responsibilities of the enterprise object mobility service
user can be as follows.
— Agree to an explicit or implicit agreement with the mobility service provider on the exchange of
information needed for the delivery and use of mobility services.
— Identify the user's transport needs and send a request to a mobility service provider. The request
will also usually contain information about the user, for example, user category (e.g. children,
adults, seniors and people with reduced mobility and the number of travellers in each category).
The request can also contain the desired time of departure or arrival and preferences regarding
means of transport, number of stops and maximum waiting time when changing from one transport
service to another. The request can also contain preferences such as most environmentally-friendly,
shortest travel time and lowest price.
— Receive different alternatives from the mobility service provider and evaluate the different
alternatives, select the preferred option, and book this.
— Receive and store the access rights to the mobility service and present these when using the
mobility service. The access rights can be stored, for example, in an app in a mobile phone, a wireless
smart card, an electronic tag with a unique code, a smartwatch or any electronic medium that can
communicate with the provider of the transport service's local or central system, e.g. validators
installed in buses or QR codes readers on a shared el-scooter. Ideally, the user ought to be able to use
the same medium to access all the different transport services in a mobility service, but in practice
this is difficult before there is a common system that has technical, functional and contractual
interoperability between all actors involved in the mobility service provider ecosystem.
— Use the mobility service according to the terms that apply to the service, e.g. usage and pricing
rules.
— Pay for the mobility service. The easiest way for the user could be to link the use of mobility services
to a bank account, a credit card account or a common transport service account (see ISO/TR 21724-1),
but there are also other solutions such as electronic values stored in the same medium (e.g. a mobile
phone or smart card) that stores and presents the access rights. As the user uses the mobility
1) Under preparation. Stage at the time of publication: ISO/DTR 24317:2023.
service, the various providers of transport services will retrieve electronic values from the medium
corresponding to the price of the service (pay-as-you-go).
6.3 Mobility service provider responsibilities
Table 2 shows how other transport service concepts have named the provider of the service, thereby
enabling a comparison of the roles in this document with similar roles in MaaS, MOD and UITP
documents and in other ISO documents involving a provider of a transport-related service.
Table 2 — Terms related to "mobility service provider" in other transport-related documents
Term used MaaS MOD UITP ISO 24014-1 ISO 17573-1 ISO/TR EN 12896-
in this doc- 21724-1 5
ument
Mobility MaaS MOD op- MaaS Pro- Product owner Toll service Transport ser- Fare prod-
service pro- provider erator vider and Product provider vice manager uct owner
a
vider retailers role and
Integrator Mobility ser-
its Fare
vice manager
product
retailers
a
A mobility service provider has many similarities with the "product owner" role in ISO 24014-1 as the mobility service
providers describe the recommended use of the mobility service (usage rules), the recommended payment means for the
service (pricing rules) and the recommended means for sharing the income for a service between the involved stakeholders
(commercial rules). The mobility service providers can also have retailers in the same way as the product owner in an
interoperable fare management systems (IFMS).
Based on the descriptions of the enterprise object responsibilities in the 7 reference sources listed in
Table 2 and a further detailing of those, the responsibilities of the enterprise object mobility service
provider can be as follows.
— Establish an explicit or implicit agreement with the Mobility service user on the exchange of
information needed for the delivery and use of mobility services.
— Acquire/procure and integrate real time multi-modal system performance data.
— Establish an agreement with the transport service providers on transport service provision.
— Prepare a policy for the delivery of mobility services in accordance with the laws and regulations
relevant to this type of services. Such a policy would also ensure transparency for all actors invo
...