ISO/TS 5206-1:2023
(Main)Intelligent transport systems — Parking — Part 1: Core data model
Intelligent transport systems — Parking — Part 1: Core data model
This document defines terms, characterization and the relationship of concepts, defined using model-driven architecture methods, for parking and parking-related activities (both on-street and off-street) covering common data supporting business to business exchanges and end user services.
Systèmes intelligents de transport - Stationnement — Partie 1: Modèle de données de base
General Information
Buy Standard
Standards Content (Sample)
TECHNICAL ISO/TS
SPECIFICATION 5206-1
First edition
2023-04
Intelligent transport systems —
Parking —
Part 1:
Core data model
Systèmes intelligents de transport - Stationnement —
Partie 1: Modèle de données de base
Reference number
ISO/TS 5206-1:2023(E)
© ISO 2023
---------------------- Page: 1 ----------------------
ISO/TS 5206-1:2023(E)
COPYRIGHT PROTECTED DOCUMENT
© 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
© ISO 2023 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/TS 5206-1:2023(E)
Contents Page
Foreword .v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms, definitions and abbreviated terms . 1
3.1 Terms and definitions . 1
3.2 Abbreviated terms . 2
4 Conformance . 2
5 UML notation . 2
6 Data model . 3
6.1 Data model overview . 3
6.2 Place data concepts . 4
6.2.1 Place hierarchy . 4
6.2.2 IdentifiedArea sub-types .12
6.2.3 Common components . 16
6.2.4 Payment method. 17
6.2.5 Basic elements (in place) . 18
6.3 Occupancy . . 19
6.3.1 Introduction to occupancy . 19
6.3.2 Supply . 20
6.3.3 Demand . 21
6.3.4 Enumerations (for occupancy). 21
6.3.5 External codelists (for occupancy) . 22
6.4 Rates . 22
6.4.1 Introduction to rates. 22
6.4.2 Rate tables .22
6.4.3 Eligibility . 24
6.4.4 Enumerations (for rates) . 25
6.4.5 External codelists (for rates) . 26
6.5 Right . 26
6.5.1 Enumerations (for right) . 37
6.5.2 External codelists (for right) .38
6.6 Session .38
6.6.1 General .38
6.6.2 Enumerations (for session) .40
6.6.3 External codelists (for session) .40
6.7 Observation .40
6.7.1 Enumerations (for observation) . 42
6.7.2 External codelists (for observation) . 42
6.8 Quote . 42
6.8.1 Introduction to quote . 42
6.8.2 QuoteRightRequest — Request for a new transaction. 43
6.8.3 QuoteRightResponse — Response to a QuoteRightRequest for a new
transaction.44
6.8.4 QuoteSessionExtensionRequest — Request for an extension of an existing
session . 45
6.8.5 QuoteSessionExtensionResponse — Response to a
QuoteSessionExtensionRequest for an extension of an existing session .46
6.8.6 Enumerations (for quote) .48
6.8.7 External codelists (for quote) .48
6.9 Common elements .48
6.9.1 Introduction to common elements .48
iii
© ISO 2023 – All rights reserved
---------------------- Page: 3 ----------------------
ISO/TS 5206-1:2023(E)
6.9.2 Data types (general) .50
6.9.3 Enumerations (general) .50
6.9.4 Common classes . 51
6.9.5 External codelists . 52
6.9.6 Organisation, contacts and address . 53
6.9.7 Describing Locations .56
6.9.8 Data types (for location) .64
6.9.9 Enumerations (for location) .64
6.9.10 External codelists (for location) .66
6.9.11 Times.66
6.10 Facilities . 69
6.10.1 Overview . 69
6.10.2 Data types (for facilities). 70
6.10.3 Enumerations (for facilities) . 70
6.10.4 External codelists (for facilities) . 70
6.11 Energy infrastructure . 71
6.11.1 Overview . 71
6.11.2 Data types (for energy infrastructure) .72
6.11.3 Enumerations (for energy infrastructure).73
6.11.4 External codelists (for energy infrastructure) .74
Annex A (normative) Data dictionary .75
Annex B (informative) Relationship to CEN 16157 "DATEX II" Data Modelling Concept and
Framework . 196
Annex C (informative) Use case examples . 197
Annex D (informative) Example user-defined codelists .246
Bibliography . 247
iv
© ISO 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/TS 5206-1:2023(E)
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.
A list of all parts in the ISO 5206 series can be found on the ISO website.
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.
v
© ISO 2023 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/TS 5206-1:2023(E)
Introduction
Around the globe, new services and technologies are intersecting to create value-added convenience
to customers and business owners while better utilizing available parking, mobility and transport
infrastructure. Whether supporting car sharing, ride sharing, micro mobility services, prepaid parking,
dynamic pricing in parking structures, remote management of operations, and/or improved reporting,
the sharing of data is key to accelerating the adoption of these services.
To enable the sharing of data, the global community has collaborated to create consensus-built,
international parking and mobility data specifications to establish a common language for data concepts
and definitions in the parking, transport and mobility sectors. These “data specifications” define a
common language composed of a set of data concepts and definitions that public and private property
owners, operators and service providers can follow to facilitate communication between themselves
and with the other industries. These specifications facilitate seamless integration, compatibility and
communication between parking entities, mobility operators, the automotive industry, IT developers,
ITS operators, services, and map and app providers, as well as other stakeholders.
These specifications, as defined in this document, seek to reduce the effort required to connect
technology solutions to one another and to allow companies to refocus their resources on innovating
new services and operations.
This document defines the structure, definition and relationships of data constructs relevant to parking
and mobility data. This document provides a description of the data constructs in the context of the
data model in Clause 6.
Annex A provides a data dictionary of definitions for attributes, classes and relationships.
Annex B provides a description of the data modelling approach defined in this document and how this
relates to the CEN 16157 series "DATEX II" modelling approach, defined in EN 16157-1.
NOTE By choice, the Alliance for Parking Data Standards has substantively adopted the DATEX II modelling
approach, as this can potentially facilitate simpler integration, at a later date, to data concepts and standards
defining road traffic management and information concepts.
Annex C provides use cases and examples for the use of the data defined.
vi
© ISO 2023 – All rights reserved
---------------------- Page: 6 ----------------------
TECHNICAL SPECIFICATION ISO/TS 5206-1:2023(E)
Intelligent transport systems — Parking —
Part 1:
Core data model
1 Scope
This document defines terms, characterization and the relationship of concepts, defined using model-
driven architecture methods, for parking and parking-related activities (both on-street and off-street)
covering common data supporting business to business exchanges and end user services.
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 639-1, Codes for the representation of names of languages — Part 1: Alpha-2 code
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country
code
ISO 4217, Codes for the representation of currencies
ISO 8601-1, Date and time — Representations for information interchange — Part 1: Basic rules
ISO/IEC 10646, Information technology — Universal coded character set (UCS)
ISO/IEC 19505-1, Information technology — Object Management Group Unified Modeling Language (OMG
UML) — Part 1: Infrastructure
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions 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.1
data receiving party
entity that is requesting or receiving data using the specification from a reliable data source
3.1.2
data distributing party
entity holding data with permission to distribute, that is issuing data using the specification to other
entities
1
© ISO 2023 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/TS 5206-1:2023(E)
3.2 Abbreviated terms
ANPR automatic number plate recognition
RFID radio frequency identification
UML unified modeling language
4 Conformance
A specification, system or exchange of data (hereafter called "specification") claiming conformance to
this document shall include a comparison of the specification of data against the data model defined in
this document. This comparison shall be defined at two conformance levels:
— level 1 (data domain) which identifies which data domains within the specification correspond to
the data domains specified in this document, and which are not;
— level 2 (detailed level) which compares the data model within the specification against the packages,
classes, attributes and relationships specified in this document.
The level 1 conformance statement should be presented as a table based on the data domains defined
in the normative part of this document. This includes place, occupancy, session, right, rates, quote,
observation, energy infrastructure and parking common (PkCommon); or
The level 2 conformance statement should be presented as a table in which the data concepts used in
the specification are described as follows.
— “Unmodified”: concepts in the specification which have the same definition, properties and
relationships as in the corresponding data domain specified in this document.
— “Modified”: concepts in the specification which are similar to the data concept defined in this
document, but which differ in the details of certain attributes and/or relationships (e.g. attributes
added).
— “Alternative”: concepts or groups of concepts in the specification intended to model the same
concepts as defined in this document but in a significantly different way.
— “Additional”: concepts in the specification which are additional to the concepts defined in this
document and therefore are not covered by and drawn from the data concepts specified in this
document.
— “Omitted”: data concepts specified in this document which are not used in the specification.
Data concepts shall include packages, classes, attributes, relationships, definitions and properties, and
comparison shall present conformance with the following requirements as expressed in this document:
— conformance to all stipulated minimum and maximum multiplicity requirements for UML elements
and relationships;
— conformance to all definitions, types and ordering;
— employment of optional elements as specified;
— conformance to all expressed constraints.
5 UML notation
The UML notation used in this document shall be as described in ISO/IEC 19505-1.
NOTE The use of UML notation follows the DATEX II methodology which is specified in EN 16157-1.
2
© ISO 2023 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/TS 5206-1:2023(E)
6 Data model
6.1 Data model overview
This specification facilitates the sharing of basic information between entities and systems. This
includes map services, online marketing and aggregator services, event ticketing platforms, transit and
transportation agencies, and other firms, organizations or individuals that have a need to know the
location of parking and other mobility-related services and general information about the operation.
Figure 1 shows the data domains in this document. Each data domain defines a specific set of data
concepts that logically can be grouped.
Figure 1 — Data domains
To assist navigation and understanding of the specification in this document, the overall model
is separated into data domains, which can be seen in UML packages in Figure 2. The domains focus
on functional groups of data concepts and relationships. Each of the domains is specified in its own
namespace. In addition, the structure of the data model supports the definition of common concepts
that are referenced and reused across several domains. These common concepts are specified in the
“PkCommon” domain.
3
© ISO 2023 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/TS 5206-1:2023(E)
Figure 2 — Namespace dependencies
Figure 2 illustrates the dependency between namespaces.
These data domains, as characterized by the namespaces, are combined in various manners to support
specific use cases that exist in parking and mobility operations. For example:
— the operations and systems to support automated valet parking rely on this document's data
domains of place, rate, quote, session, right and occupancy;
— the operation and systems to support curbside management rely on all data domains in this
document to support data sharing.
6.2 Place data concepts
6.2.1 Place hierarchy
6.2.1.1 Overview
This subclause describes concepts used in the place hierarchy, which are defined in the
namespace of the data model.
NOTE Location, time and contact/organization concepts are defined in the namespace of this
data model.
6.2.1.2 Place hierarchy
The specification defines a method for building a hierarchy of place records in on-street, off-street and
zone environments. Each instance of a place record corresponds to an instance of a class within the
place hierarchy. This enables a parking or other type of operation to identify a location or zone in a
4
© ISO 2023 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/TS 5206-1:2023(E)
simple manner with a single hierarchy element or to break down a place into a multi-layered hierarchy
that identifies discrete parking enclosures or defined areas to communicate operating hours, space
counts, operating restrictions, location, rights and associated pricing and occupancy.
The hierarchy supports the ability of lower-level place hierarchy class instances (child records) to inherit
specific instance data from a higher-level place hierarchy class instance (a parent record) in order to
simplify the amount of data shared. The place hierarchy also enables lower-level place hierarchy class
instances to document variations in specific attributes from their parent, higher-level place hierarchy
class instance.
Additionally, the specification enables other operation types, not directly related to parking, to define a
place in discrete operating enclosures. This may include a defined on-street area for managing delivery
services or a sidewalk area enabled for bike or e-scooter placement.
The hierarchy allows a data distributing party to decide the appropriate level of detail to send to a data
receiving party via messaging protocols. In addition, it is not necessary to build multi-layer hierarchies
of Place data. Simple data needs can be represented without using the multiple layers available in the
data specification.
Each of the component Place data concepts is mentioned in this subclause, but further details and
descriptions follow in subsequent subclauses. These component data concepts are:
— Place (6.2.1.4),
— SubplaceElement (6.2.1.5),
— IdentifiedArea (6.2.1.6),
— Space (6.2.1.7),
— Campus,
— PedestrianAccess (6.2.2.1),
— VehicularAccess (6.2.2.2),
— SpecificArea (6.2.2.3), and
— SupplementalFacility (6.2.2.4).
Place is a term introduced in the specification to define where a vehicle may park, stand, rest or briefly
transit to allow a person to change modes of transport (i.e. taxi drop-off/pickup, ride share drop-off/
pickup, valet stand, etc.). Place is instantiated via the Place class. Place can also be used to define entry
and exit roadways, driveways, and acceleration/deceleration zones for vehicles as well as pedestrian
access points. Place supports both on-street and off-street operating environments. Place also defines
specific areas to be defined for mobility or other related uses such as bike storage, e-scooter enclosures,
etc. where it i
...
TECHNICAL ISO/TS
SPECIFICATION 5206-1
First edition
Intelligent transport systems —
Parking —
Part 1:
Core data model
Systèmes intelligents de transport - Stationnement —
Partie 1: Modèle de données de base
PROOF/ÉPREUVE
Reference number
ISO/TS 5206-1:2023(E)
© ISO 2023
---------------------- Page: 1 ----------------------
ISO/TS 5206-1:2023(E)
COPYRIGHT PROTECTED DOCUMENT
© 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
PROOF/ÉPREUVE © ISO 2023 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/TS 5206-1:2023(E)
Contents Page
Foreword .v
Introduction . vi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Conformance . 2
5 UML notation . 2
6 Data model . 2
6.1 Data model overview . 2
6.2 Place data concepts . 4
6.2.1 Place hierarchy . 4
6.2.2 IdentifiedArea sub-types .12
6.2.3 Common components . 16
6.2.4 Payment method. 17
6.2.5 Basic elements (in place) . 18
6.3 Occupancy . . 19
6.3.1 Introduction to occupancy . 19
6.3.2 Supply . 20
6.3.3 Demand . 21
6.3.4 Enumerations (for occupancy). 21
6.3.5 External codelists (for occupancy) . 22
6.4 Rates . 22
6.4.1 Introduction to rates. 22
6.4.2 Rate tables .22
6.4.3 Eligibility . 24
6.4.4 Enumerations (for rates) . 25
6.4.5 External codelists (for rates) . 26
6.5 Right . 26
6.5.1 Enumerations (for right) .36
6.5.2 External codelists (for right) . 37
6.6 Session . 37
6.6.1 General . 37
6.6.2 Enumerations (for session) . 39
6.6.3 External codelists (for session) .39
6.7 Observation .39
6.7.1 Enumerations (for observation) . 41
6.7.2 External codelists (for observation) . 41
6.8 Quote . 41
6.8.1 Introduction to quote . 41
6.8.2 QuoteRightRequest — Request for a new transaction. 42
6.8.3 QuoteRightResponse — Response to a QuoteRightRequest for a new
transaction. 43
6.8.4 QuoteSessionExtensionRequest — Request for an extension of an existing
session .44
6.8.5 QuoteSessionExtensionResponse — Response to a
QuoteSessionExtensionRequest for an extension of an existing session . 45
6.8.6 Enumerations (for quote) . 47
6.8.7 External codelists (for quote) . 47
6.9 Common elements . 47
6.9.1 Introduction to common elements . 47
6.9.2 Data types (general) .49
6.9.3 Enumerations (general) .49
iii
© ISO 2023 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 3 ----------------------
ISO/TS 5206-1:2023(E)
6.9.4 Common classes .50
6.9.5 External codelists . 51
6.9.6 Organisation, contacts and address . 52
6.9.7 Describing Locations .55
6.9.8 Data types (for location) .63
6.9.9 Enumerations (for location) .63
6.9.10 External codelists (for location) .65
6.9.11 Times.65
6.10 Facilities . 67
6.10.1 Overview . 67
6.10.2 Data types (for facilities).68
6.10.3 Enumerations (for facilities) .68
6.10.4 External codelists (for facilities) .68
6.11 Energy infrastructure . 69
6.11.1 Overview . 69
6.11.2 Data types (for energy infrastructure) . 70
6.11.3 Enumerations (for energy infrastructure). 71
6.11.4 External codelists (for energy infrastructure) .72
Annex A (normative) Data dictionary .73
Annex B (informative) Relationship to CEN 16157 "DATEX II" Data Modelling Concept and
Framework . 194
Annex C (informative) Use case examples .195
Annex D (informative) Example user-defined codelists.244
Bibliography . 245
iv
PROOF/ÉPREUVE © ISO 2023 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/TS 5206-1:2023(E)
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.
A list of all parts in the ISO 5206 series can be found on the ISO website.
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.
v
© ISO 2023 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 5 ----------------------
ISO/TS 5206-1:2023(E)
Introduction
Around the globe, new services and technologies are intersecting to create value-added convenience
to customers and business owners while better utilizing available parking, mobility and transport
infrastructure. Whether supporting car sharing, ride sharing, micro mobility services, prepaid parking,
dynamic pricing in parking structures, remote management of operations, and/or improved reporting,
the sharing of data is key to accelerating the adoption of these services.
To enable the sharing of data, the global community has collaborated to create consensus-built,
international parking and mobility data specifications to establish a common language for data concepts
and definitions in the parking, transport and mobility sectors. These “data specifications” define a
common language composed of a set of data concepts and definitions that public and private property
owners, operators and service providers can follow to facilitate communication between themselves
and with the other industries. These specifications facilitate seamless integration, compatibility and
communication between parking entities, mobility operators, the automotive industry, IT developers,
ITS operators, services, and map and app providers, as well as other stakeholders.
These specifications, as defined in this document, seek to reduce the effort required to connect
technology solutions to one another and to allow companies to refocus their resources on innovating
new services and operations.
This document defines the structure, definition and relationships of data constructs relevant to parking
and mobility data. This document provides a description of the data constructs in the context of the
data model in Clause 6.
Annex A provides a data dictionary of definitions for attributes, classes and relationships.
Annex B provides a description of the data modelling approach defined in this document and how this
relates to the CEN 16157 series "DATEX II" modelling approach, defined in EN 16157-1.
NOTE By choice, the Alliance for Parking Data Standards has substantively adopted the DATEX II modelling
approach, as this can potentially facilitate simpler integration, at a later date, to data concepts and standards
defining road traffic management and information concepts.
Annex C provide use cases and examples for the use of the data defined.
vi
PROOF/ÉPREUVE © ISO 2023 – All rights reserved
---------------------- Page: 6 ----------------------
TECHNICAL SPECIFICATION ISO/TS 5206-1:2023(E)
Intelligent transport systems — Parking —
Part 1:
Core data model
1 Scope
This document defines terms, characterization and the relationship of concepts, defined using model-
driven architecture methods, for parking and parking-related activities (both on-street and off-street)
covering common data supporting business to business exchanges and end user services.
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 639-1, Codes for the representation of names of languages — Part 1: Alpha-2 code
ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country
code
ISO 4217, Codes for the representation of currencies
ISO 8601-1, Date and time — Representations for information interchange — Part 1: Basic rules
ISO/IEC 10646, Information technology — Universal coded character set (UCS)
ISO/IEC 19505-1, Information technology — Object Management Group Unified Modeling Language (OMG
UML) — Part 1: Infrastructure
3 Terms and definitions
For the purposes of this document, the following terms and definitions 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
data receiving party
entity that is requesting or receiving data using the specification from a reliable data source
3.2
data distributing party
entity holding data with permission to distribute, that is issuing data using the specification to other
entities
1
© ISO 2023 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 7 ----------------------
ISO/TS 5206-1:2023(E)
4 Conformance
A specification, system or exchange of data (hereafter called "specification") claiming conformance to
this document shall include a comparison of the specification of data against the data model defined in
this document. This comparison shall be defined at two conformance levels:
— level 1 (data domain) which identifies which data domains within the specification correspond to
the data domains specified in this document, and which are not;
— level 2 (detailed level) which compares the data model within the specification against the packages,
classes, attributes and relationships specified in this document.
The level 1 conformance statement should be presented as a table based on the data domains defined
in the normative part of this document. This includes place, occupancy, session, right, rates, quote,
observation, energy infrastructure and parking common (PkCommon); or
The level 2 conformance statement should be presented as a table in which the data concepts used in
the specification are described as follows.
— “Unmodified”: concepts in the specification which have the same definition, properties and
relationships as in the corresponding data domain specified in this document.
— “Modified”: concepts in the specification which are similar to the data concept defined in this
document, but which differ in the details of certain attributes and/or relationships (e.g. attributes
added).
— “Alternative”: concepts or groups of concepts in the specification intended to model the same
concepts as defined in this document but in a significantly different way.
— “Additional”: concepts in the specification which are additional to the concepts defined in this
document and therefore are not covered by and drawn from the data concepts specified in this
document.
— “Omitted”: data concepts specified in this document which are not used in the specification.
Data concepts shall include packages, classes, attributes, relationships, definitions and properties, and
comparison shall present conformance with the following requirements as expressed in this document:
— conformance to all stipulated minimum and maximum multiplicity requirements for UML elements
and relationships;
— conformance to all definitions, types and ordering;
— employment of optional elements as specified;
— conformance to all expressed constraints.
5 UML notation
The UML notation used in this document shall be as described in ISO/IEC 19505-1.
NOTE The use of UML notation follows the DATEX II methodology which is specified in EN 16157-1.
6 Data model
6.1 Data model overview
This specification facilitates the sharing of basic information between entities and systems. This
includes map services, online marketing and aggregator services, event ticketing platforms, transit and
2
PROOF/ÉPREUVE © ISO 2023 – All rights reserved
---------------------- Page: 8 ----------------------
ISO/TS 5206-1:2023(E)
transportation agencies, and other firms, organizations or individuals that have a need to know the
location of parking and other mobility-related services and general information about the operation.
Figure 1 shows the data domains in this document. Each data domain defines a specific set of data
concepts that logically can be grouped.
Figure 1 — Data domains
To assist navigation and understanding of the specification in this document, the overall model
is separated into data domains, which can be seen in UML packages in Figure 2. The domains focus
on functional groups of data concepts and relationships. Each of the domains is specified in its own
namespace. In addition, the structure of the data model supports the definition of common concepts
that are referenced and reused across several domains. These common concepts are specified in the
“PkCommon” domain.
3
© ISO 2023 – All rights reserved PROOF/ÉPREUVE
---------------------- Page: 9 ----------------------
ISO/TS 5206-1:2023(E)
Figure 2 — Namespace dependencies
Figure 2 illustrates the dependency between namespaces.
These data domains, as characterized by the namespaces, are combined in various manners to support
specific use cases that exist in parking and mobility operations. For example:
— the operations and systems to support automated valet parking rely on this document's data
domains of place, rate, quote, session, right and occupancy;
— the operation and systems to support curbside management rely on all data domains in this
document to support data sharing.
6.2 Place data concepts
6.2.1 Place hierarchy
6.2.1.1 Overview
This subclause describes concepts used in the place hierarchy, which are defined in the
namespace of the data model.
NOTE Location, time and contact/organization concepts are defined in the namespace of this
data model.
6.2.1.2 Place hierarchy
The specification defines a method for building a hierarchy of place records in on-street, off-street and
zone environments. Each instance of a place record corresponds to an instance of a class within the
place hierarchy. This enables a parking or other type of operation to identify a location or zone in a
4
PROOF/ÉPREUVE © ISO 2023 – All rights reserved
---------------------- Page: 10 ----------------------
ISO/TS 5206-1:2023(E)
simple manner with a single hierarchy element or to break down a place into a multi-layered hierarchy
that identifies discrete parking enclosures or defined areas to communicate operating hours, space
counts, operating restrictions, location, rights and associated pricing and occupancy.
The hierarchy supports the ability of lower-level place hierarchy class instances (child records) to inherit
specific instance data from a higher-level place hierarchy class instance (a parent record) in order to
simplify the amount of data shared. The place hierarchy also enables lower-level place hierarchy class
instances to document variations in specific attributes from their parent, higher-level place hierarchy
class instance.
Additionally, the specification enables other operation types, not directly related to parking, to define a
place in discrete operating enclosures. This may include a defined on-street area for managing delivery
services or a sidewalk area enabled for bike or e-scooter placement.
The hierarchy allows a data distributing party to decide the appropriate level of detail to send to a data
receiving party via messaging protocols. In addition, it is not necessary to build multi-layer hierarchies
of Place data. Simple data needs can be represented without using the multiple layers available in the
data specification.
Each of the component Place data concepts is mentioned in this subclause, but further details and
descriptions follow in subsequent subclauses. These component data concepts are:
— Place (6.2.1.4),
— SubplaceElement (6.2.1.5),
— IdentifiedArea (6.2.1.6),
— Space (6.2.1.7),
— Campus,
— PedestrianAccess (6.2.2.1),
— VehicularAccess (6.2.2.2),
— SpecificArea (6.2.2.3), and
— SupplementalFacility (6.2.2.4).
Place is a term introduced in the specification to define where a vehicle may park, stand, rest or briefly
transit to allow a person to change modes of transport (i.e. taxi drop-off/pickup, ride share drop-off/
pickup, valet stand, etc.). Place is instantiated via the Place class. Place can also be used to define entry
and exit roadways, driveways, and acceleration/deceleration zones for vehicles as well as pedestrian
access points. Place supports both on-street and off-street operating environments. Place also defines
specific areas to be defined for mobility or other related uses such as bike storage, e-scooter enclosures,
etc. where it is useful to share operating parameters or assign RightSpecifications, Rates or other data
domains.
A Place is an aggregation of instances of SubplaceElement, IdentifiedArea and Space. In this
specification, the lowest mandatory class instance to define a Place is the IdentifiedArea.
NOTE Space is a lower data concept instance that can exist below IdentifiedArea data concept instance,
but it is not required
...
© ISO 5206-1 – All rights reserved
TECHNICAL SPECIFICATION Style Definition
...
Formatted: Font: 13 pt
ISO /TS 5206-1:2020(X2023(E)
Formatted
...
ISO TC 204/WG 19
Formatted: zzCover, Left
Date: 2023-02
Formatted: zzCover, Left, Space After: 0 pt
Secretariat: ANSI
Formatted: Font: 13 pt
Intelligent transport systems –— Parking –— Part 1: Core data model
Formatted
...
Formatted: zzCover, Line spacing: single
WD stage
Warning for WDs and CDs
This document is not an ISO International Standard. It is distributed for review and comment. It is subject to
change without notice and may not be referred to as an International Standard.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of
which they are aware and to provide supporting documentation.
---------------------- Page: 1 ----------------------
ISO 5206-1:2020(X)
© ISO 2020
© ISO 5206-1 – All rights reserved 3
---------------------- Page: 2 ----------------------
ISO /TS 5206-1:2020(X2023(E)
© ISO 2023 Formatted: Left: 1.27 cm, Right: 1.27 cm, Top: 1.27
cm, Bottom: 1.27 cm, Width: 21.59 cm, Height: 27.94
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of cm
this publication may be reproduced or utilized otherwise in any form or by any means, electronic or
Formatted: Font: 11 pt, Font color: Blue
mechanical, including photocopying, or posting on the internet or an intranet, without prior written
Formatted: Border: Box: (Single solid line, Blue, 0.5 pt
permission. Permission can be requested from either ISO at the address below or ISO’s member body in the
Line width)
country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Formatted: Font: 11 pt, Font color: Blue, English
(United Kingdom)
Email: copyright@iso.org
Website: www.iso.orgwww.iso.org
Formatted: Font: 11 pt, Font color: Blue
Formatted: Font: 11 pt, Font color: Blue
Published in Switzerland
Formatted: Font: 11 pt
Formatted: Space After: 6 pt, Line spacing: Exactly 11
pt
ii © ISO 5206-1 – All rights reserved
ii © ISO 2023 – All rights reserved
---------------------- Page: 3 ----------------------
ISO /TS 5206-1:2020(X2023(E)
Contents Formatted: Space Before: 48 pt, Don't adjust space
between Latin and Asian text, Don't adjust space
between Asian text and numbers
Foreword . xv
Introduction . xvi
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Conformance . 2
5 UML notation . 2
6 Data Model . 3
6.1 Data Model Overview . 3
6.2 Place Data Concepts . 5
6.2.1 Place Hierarchy . 5
6.2.2 IdentifiedArea Sub-Types . 15
6.2.3 Common Components. 20
6.2.4 PaymentMethod . 22
6.2.5 Basic Elements (in Place) . 23
6.3 Occupancy . 25
6.3.1 Introduction to Occupancy . 25
6.3.2 Supply . 25
6.3.3 Demand . 27
6.3.4 Enumerations (for Occupancy) . 29
6.3.5 External Codelists (for Occupancy) . 29
6.4 Rates . 29
6.4.1 Introduction to Rates . 29
6.4.2 Rate Tables . 29
6.4.3 Eligibility . 32
6.4.4 Enumerations (for Rates) . 34
6.4.5 External Codelists (for Rates) . 35
6.5 Right . 36
6.5.1 Enumerations (for Right) . 47
6.5.2 External Codelists (for Right) . 47
6.6 Session . 48
6.6.1 Enumerations (for Session) . 49
6.6.2 External Codelists (for Session) . 49
6.7 Observation . 50
6.7.1 Enumerations (for Observation) . 51
6.7.2 External Codelists (for Observation) . 51
6.8 Quote . 52
6.8.1 Introduction to Quote . 52
6.8.2 QuoteRightRequest - Request for a new transaction . 52
Formatted: Font: 11 pt
6.8.3 QuoteRightResponse – Response to a QuoteRightRequest for a new Transaction . 54
6.8.4 QuoteSessionExtensionRequest – Request for an extension of an existing Session . 55 Formatted: Space After: 6 pt, Line spacing: Exactly 11
pt
© ISO 5206-1 – All rights reserved iii
© ISO 2023 – All rights reserved iii
---------------------- Page: 4 ----------------------
ISO /TS 5206-1:2020(X2023(E)
6.8.5 QuoteSessionExtensionResponse – Response to a QuoteSessionExtensionRequest for an
extension of an existing Session . 57
6.8.6 Enumerations (for Quote) . 59
6.8.7 External Codelists (for Quote) . 59
6.9 Common Elements . 59
6.9.1 Introduction to Common Elements . 59
6.9.2 DataTypes (General) . 61
6.9.3 Enumerations (General) . 62
6.9.4 Common Classes . 64
6.9.5 External Code Lists . 65
6.9.6 Organisation, Contacts and Address . 66
6.9.7 Describing Locations . 69
6.9.8 Data Types (for Location) . 79
6.9.9 Enumerations (for Location) . 79
6.9.10 External Codelists (for Location) . 81
6.9.11 Times . 81
6.10 Facilities . 85
6.10.1 Overview . 85
6.10.2 Data Types (for Facilities) . 85
6.10.3 Enumerations (for Facilities) . 86
6.10.4 External Codelists (for Facilities) . 87
6.11 Energy Infrastructure . 87
6.11.1 Overview . 87
6.11.2 Data Types (for Energy Infrastructure) . 89
6.11.3 Enumerations (for Energy Infrastructure) . 90
6.11.4 External Codelists (for Energy Infrastructure) . 91
Annex A (normative) Data Dictionary . 92
A.1 Data Dictionary for "Parking" . 94
A.1.1 "AreaLocation" package . 94
A.1.1.1 Location of "AreaLocation" package . 94
A.1.1.2 Classes of the "AreaLocation" package . 94
A.1.1.3 Specializations of the "AreaLocation" package . 94
A.1.1.4 Associations of the "AreaLocation" package . 94
A.1.1.5 Attributes of the "AreaLocation" package . 95
A.1.2 "Classes" package . 95
A.1.2.1 Location of "Classes" package . 95
A.1.2.2 Classes of the "Classes" package . 95
A.1.2.3 Specializations of the "Classes" package . 96
A.1.2.4 Associations of the "Classes" package . 96
Formatted: Font: 11 pt
A.1.2.5 Attributes of the "Classes" package . 96
Formatted: Space After: 6 pt, Line spacing: Exactly 11
pt
iv © ISO 5206-1 – All rights reserved
iv © ISO 2023 – All rights reserved
---------------------- Page: 5 ----------------------
ISO /TS 5206-1:2020(X2023(E)
A.1.3 "CodeLists" package . 99
A.1.3.1 Location of "CodeLists" package . 99
A.1.3.2 Classes of the "CodeLists" package . 99
A.1.3.3 Specializations of the "CodeLists" package . 99
A.1.3.4 Associations of the "CodeLists" package . 99
A.1.3.5 Attributes of the "CodeLists" package . 100
A.1.4 "CommonClasses" package . 101
A.1.4.1 Location of "CommonClasses" package . 101
A.1.4.2 Classes of the "CommonClasses" package . 101
A.1.4.3 Specializations of the "CommonClasses" package . 101
A.1.4.4 Associations of the "CommonClasses" package . 101
A.1.4.5 Attributes of the "CommonClasses" package . 102
A.1.5 "CommonComponents" package . 103
A.1.5.1 Location of "CommonComponents" package . 103
A.1.5.2 Classes of the "CommonComponents" package . 103
A.1.5.3 Specializations of the "CommonComponents" package . 104
A.1.5.4 Associations of the "CommonComponents" package . 104
A.1.5.5 Attributes of the "CommonComponents" package . 105
A.1.6 "Contacts" package . 107
A.1.6.1 Location of "Contacts" package . 107
A.1.6.2 Classes of the "Contacts" package . 108
A.1.6.3 Specializations of the "Contacts" package . 109
A.1.6.4 Associations of the "Contacts" package . 109
A.1.6.5 Attributes of the "Contacts" package . 110
A.1.7 "Demand" package . 113
A.1.7.1 Location of "Demand" package . 113
A.1.7.2 Classes of the "Demand" package . 113
A.1.7.3 Specializations of the "Demand" package . 114
A.1.7.4 Associations of the "Demand" package. 114
A.1.7.5 Attributes of the "Demand" package . 115
A.1.8 "Eligibility" package . 116
Formatted: Font: 11 pt
A.1.8.1 Location of "Eligibility" package . 116
Formatted: Space After: 6 pt, Line spacing: Exactly 11
pt
© ISO 5206-1 – All rights reserved v
© ISO 2023 – All rights reserved v
---------------------- Page: 6 ----------------------
ISO /TS 5206-1:2020(X2023(E)
A.1.8.2 Classes of the "Eligibility" package . 116
A.1.8.3 Specializations of the "Eligibility" package . 117
A.1.8.4 Associations of the "Eligibility" package . 118
A.1.8.5 Attributes of the "Eligibility" package . 119
A.1.9 "GeoJSON" package. 122
A.1.9.1 Location of "GeoJSON" package . 122
A.1.9.2 Classes of the "GeoJSON" package . 122
A.1.9.3 Specializations of the "GeoJSON" package . 123
A.1.9.4 Associations of the "GeoJSON" package . 123
A.1.9.5 Attributes of the "GeoJSON" package . 124
A.1.10 "Gml" package . 124
A.1.10.1 Location of "Gml" package . 124
A.1.10.2 Classes of the "Gml" package . 124
A.1.10.3 Specializations of the "Gml" package . 125
A.1.10.4 Associations of the "Gml" package . 125
A.1.10.5 Attributes of the "Gml" package . 126
A.1.11 "IdentifiedArea" package . 126
A.1.11.1 Location of "IdentifiedArea" package . 126
A.1.11.2 Classes of the "IdentifiedArea" package . 126
A.1.11.3 Specializations of the "IdentifiedArea" package. 127
A.1.11.4 Associations of the "IdentifiedArea" package . 127
A.1.11.5 Attributes of the "IdentifiedArea" package . 128
A.1.12 "LinearReference" package . 128
A.1.12.1 Location of "LinearReference" package . 128
A.1.12.2 Classes of the "LinearReference" package . 128
A.1.12.3 Specializations of the "LinearReference" package . 128
A.1.12.4 Associations of the "LinearReference" package . 128
A.1.12.5 Attributes of the "LinearReference" package . 129
A.1.13 "Location" package . 129
A.1.13.1 Location of "Location" package . 129
A.1.13.2 Classes of the "Location" package . 129
Formatted: Font: 11 pt
A.1.13.3 Specializations of the "Location" package . 129
Formatted: Space After: 6 pt, Line spacing: Exactly 11
pt
vi © ISO 5206-1 – All rights reserved
vi © ISO 2023 – All rights reserved
---------------------- Page: 7 ----------------------
ISO /TS 5206-1:2020(X2023(E)
A.1.13.4 Associations of the "Location" package . 130
A.1.13.5 Attributes of the "Location" package . 130
A.1.14 "NamedArea" package . 130
A.1.14.1 Location of "NamedArea" package . 130
A.1.14.2 Classes of the "NamedArea" package . 130
A.1.14.3 Specializations of the "NamedArea" package . 130
A.1.14.4 Associations of the "NamedArea" package . 131
A.1.14.5 Attributes of the "NamedArea" package . 131
A.1.15 "Observation" package . 132
A.1.15.1 Location of "Observation" package. 132
A.1.15.2 Classes of the "Observation" package . 132
A.1.15.3 Specializations of the "Observation" package . 132
A.1.15.4 Associations of the "Observation" package . 132
A.1.15.5 Attributes of the "Observation" package . 133
(pkcmn:Organisation) . Error! Bookmark not defined.
startTime. Error! Bookmark not defined.
Start time. Error! Bookmark not defined.
The date and time of the observation. event started. (e.g. a car was observed to enter a
delivery zone at 8:01am) . Error! Bookmark not defined.
1.1 . Error! Bookmark not defined.
PkCommon.DateTime . Error! Bookmark not defined.
type . Error! Bookmark not defined.
Type . Error! Bookmark not defined.
Type of the credential referenced within the observation. . Error! Bookmark not defined.
0.1 . Error! Bookmark not defined.
Right.CredentialTypeEnum . Error! Bookmark not defined.
A.1.16 "OpenLR" package . 136
A.1.16.1 Location of "OpenLR" package . 136
A.1.16.2 Classes of the "OpenLR" package . 136
A.1.16.3 Specializations of the "OpenLR" package . 136
A.1.16.4 Associations of the "OpenLR" package . 137
Formatted: Font: 11 pt
A.1.16.5 Attributes of the "OpenLR" package . 137
Formatted: Space After: 6 pt, Line spacing: Exactly 11
A.1.17 "OpenlrArea" package . 138
pt
© ISO 5206-1 – All rights reserved vii
© ISO 2023 – All rights reserved vii
---------------------- Page: 8 ----------------------
ISO /TS 5206-1:2020(X2023(E)
A.1.17.1 Location of "OpenlrArea" package . 138
A.1.17.2 Classes of the "OpenlrArea" package . 138
A.1.17.3 Specializations of the "OpenlrArea" package . 139
A.1.17.4 Associations of the "OpenlrArea" package .
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.