ISO/TR 14813-3:2000

TECHNICAL ISO/TR
REPORT 14813-3
First edition
2000-12-15
Transport information and control
systems — Reference model architecture(s)
for the TICS sector —
Part 3:
Example elaboration
Systèmes de commande et d'information des transports — Architecture(s)
du modèle de référence du secteur TICS —
Partie 3: Élaboration d'exemple
Reference number
©
ISO 2000
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but shall not
be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In downloading this
file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat accepts no liability in this
area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation parameters
were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In the unlikely event
that a problem relating to it is found, please inform the Central Secretariat at the address given below.
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic
or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body
in the country of the requester.
ISO copyright office
Case postale 56 � CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.ch
Web www.iso.ch
Printed in Switzerland
ii © ISO 2000 – All rights reserved

Contents
Foreword.ix
Introduction.xi
1 Scope .1
2 Normative References.2
3 Terms and Definitions.2
4 Symbols and Abbreviated Terms.4
4.1 Use Case diagram.4
4.2 Package Diagram.5
4.3 Class diagram .5
4.4 Association .6
4.5 Sequence (interaction) diagram.6
5 Elaboration Method .7
6 Elaboration of the Classes.7
6.1 Control Classes .9
6.1.1 Roadway Classes .9
6.1.2 Transport Classes .10
6.1.3 Vehicles Classes.12
6.1.4 Event Classes .12
6.1.5 Payment Classes .13
6.2 Interface Classes .14
6.2.1 Operating Interface.14
6.2.2 Travel Terminal .14
6.2.3 Vehicle Interface .15
6.2.4 Roadside Peripheral.15
6.3 Information Classes .16
6.3.1 Information Classes for Traffic Management and Traveller Information.16
7 Elaboration of the Sequence Diagrams.27
7.1 Traveller Information.27
7.1.1 Pre-journey Information.27
7.1.2 Route Guidance and Navigation .28
7.1.3 Journey Schedule.30
7.1.4 Journey Payment.30
7.1.5 On-trip Traveller Information.31
7.2 Traffic Management.37
7.2.1 Traffic and Pollution Measurement and Control .37
7.2.2 Performance Evaluation.39
7.2.3 Performance Prediction .40
7.2.4 Traffic Control .40
7.2.5 Incident Management.41
7.2.6 Demand Management.42
7.2.7 Transport Planning Support.43
7.2.8 Infrastructure Maintenance and Management.45
7.2.9 Package Classes for Traffic Management.45
7.3 Vehicle .63
7.3.1 Vehicle Status .63
7.3.2 Vehicle Operation .63
7.4 Commercial Vehicle.64
7.4.1 Order and Shipment .64
7.4.2 Commercial Vehicle Tour Planning .65
7.4.3 Commercial Vehicle Administrative Processes .66
7.4.4 Commercial Vehicle Road Operation.67
7.5 Public Transport .73
7.5.1 Route and Schedule Planning .73
7.5.2 Fixed Route Public Transport.73
7.5.3 Demand Responsive Public Transport.74
7.6 Emergency.79
7.6.1 Emergency Notification and Personal Security.79
7.6.2 Emergency Resources Allocation.79
7.6.3 Emergency Vehicle Management.80
7.7 Electronic Payment.84
7.7.1 Payment Means.84
7.7.2 Fare Collection.84
7.7.3 Vehicle Charges.84
7.7.4 Payment Transaction.85
7.8 Safety .91
7.8.1 Safety Enhancement for Vulnerable Road Users.91
8 Elaboration of the Packages.93
8.1 Roadway .93
8.2 Transport .96
8.3 Vehicles .99
8.4 Events .101
8.5 Payment .103
8.6 Interfaces .105
8.7 Class-Sequence Diagram Matrix.107
8.7.1 Matrix for Key Control and Information Classes .107
8.7.2 Matrix for Interface Classes.112
9 Package Interfaces .115
9.1 Roadway Interfaces .117
9.2 Transport Interfaces .119
9.3 Vehicle Interfaces .120
9.4 Events Interfaces .121
9.5 Payment Interfaces.122
10 Dependencies between Packages .123
10.1 Roadway - Transport Collaboration.123
10.2 Roadway - Vehicles Collaboration.123
10.3 Roadway - Events Collaboration.123
10.4 Roadway - Payment Collaboration.126
10.5 Transport - Events Collaboration.126
10.6 Transport - Payment Collaboration.127
10.7 Vehicles - Events Collaboration.127
Annex A (informative) Management and Information Centres Information Classes.128
A.1 Infrastructure Map .128
A.2 Moving Components .134
A.3 Effects on Operations.138
A.4 Traffic Usage .144
A.5 Traffic Management.152
A.6 User Information .155
A.7 Transport Systems .157
A.8 Financial Data.159
A.9 TMIC Management .160
Bibliography .164
List of figures
Figure 1 — A use case diagram consisting of two use cases and one actor.4
Figure 2 — Package diagram showing nested packages and a dependency relationship .5
iv © ISO 2000 – All rights reserved

Figure 3 — Class diagrams showing the use of a single name compartment and three compartments.5
Figure 4 — Common types of class association .6
Figure 5 — A sequence diagram consisting of three interactions.6
Figure 6 — Steps in the elaboration of the Core Reference Architecture .8
Figure 7 — Control class diagram of the Roadway package .10
Figure 8 — Control class diagram of the Transport package.12
Figure 9 — Control class diagram of the Events package .13
Figure 10 — Top level aggregation of Information classes derived from the 14827 naming tree.17
Figure 11 — Information classes in the aggregation of infrastructureMap.18
Figure 12 — Information classes in the aggregation of movingComponents.19
Figure 13 — Information classes in the aggregation of effectsOnOperations.20
Figure 14 — Information classes in the aggregation of trafficUsage.21
Figure 15 — Information classes in the aggregation of trafficManagement.22
Figure 16 — Information classes in the aggregation of userInformation.23
Figure 17 — Information classes in the aggregation of transportSystems.24
Figure 18 — Information classes in the aggregation of financialData.25
Figure 19 — Information classes in the aggregation of tmicManagement .26
Figure 20 — Sequence diagram for Pre-journey Information.32
Figure 21 — Sequence diagram for Route Guidance and Navigation .33
Figure 22 — Sequence diagram for Journey Schedule .34
Figure 23 — Sequence diagram for Journey Payment .35
Figure 24 — Sequence diagram for On-trip Traveller Information .36
Figure 25 — Sequence diagram for Traffic and Pollution Measurement and Control.46
Figure 26 — Packages, control and information classes for Traffic and Pollution and Measurement and Control .47
Figure 27 — Sequence diagram for Performance Evaluation.48
Figure 28 — Packages, control and information classes for Performance Evaluation .49
Figure 29 — Sequence diagram for Performance Prediction.50
Figure 30 — Packages, control and information classes for Performance Prediction .50
Figure 31 —Sequence diagram for Traffic Control.51
Figure 32 — Packages, control and information classes for Traffic Control .52
Figure 33 — Sequence diagram for Incident management.53
Figure 34 — Packages, control and information classes for Incident Management .54
Figure 35 — Sequence diagram for Demand Management.55
Figure 36 — Packages, control and information classes for Demand Management .56
Figure 37 — Sequence diagram for Transportation Planning Support .57
Figure 38 — Packages, control and information classes for Transportation Planning Support.58
Figure 39 — Sequence diagram for Infrastructure Maintenance Management .59
Figure 40 — Packages, control and information classes for Infrastructure Maintenance and Management.59
Figure 41 — Roadway package class operations and information class associations for Traffic Management.60
Figure 42 — Events package class operations and information class associations for Traffic Management.61
Figure 43 — Transport package class operations and information class associations for Traffic Management .62
Figure 44 — Sequence diagram for Vehicle Status .64
Figure 45 — Sequence diagram for Vehicle Operation.64
Figure 46 — Sequence diagram for Order and Shipment.69
Figure 47 — Sequence diagram for Commercial Vehicle Tour Planning.70
Figure 48 — Sequence diagram for Commercial Vehicle Administrative Processes.71
Figure 49 — Sequence diagram for Commercial Vehicle Road Operation.72
Figure 50 — Sequence diagram for Route and Schedule Planning.76
Figure 51 — Sequence diagram for Fixed Route Public Transport.77
Figure 52 — Sequence Diagram for Demand Responsive Public Transport.78
Figure 53 — Sequence diagram for Emergency Notification and Personal Security.81
Figure 54 — Sequence diagram for Emergency Resources Allocation .82
Figure 55 — Sequence diagram for Emergency Vehicle Management .83
Figure 56 — Sequence diagram for Payment Means .87
Figure 57 — Sequence diagram for Fare Collection .88
Figure 58 — Sequence diagram for Vehicle Charges .89
Figure 59 — Sequence diagram for Payment Transaction .90
Figure 60 — Sequence diagram for Safety Enhancement for Vulnerable Road Users .92
Figure 61 — Key classes of the Roadway package .93
Figure 62 — Key classes of the Transport package.96
vi © ISO 2000 – All rights reserved

Figure 63 — Key classes of the Vehicle package .100
Figure 64 — Key classes of the Events package.101
Figure 65 — Key classes of the Payment package.103
Figure 66 — Key classes of the interface packages .105
Figure 67 — Roadway Package Interfaces.116
Figure 68 — Transport Package Interfaces.118
Figure 69 — Vehicle Package Interfaces .120
Figure 70 — Events Package Interfaces.121
Figure 71 — Payment Package Interfaces.122
Figure 72 — Roadway - Transport Collaborations .124
Figure 73 — Roadway - Vehicles Collaborations.124
Figure 74 — Roadway - Events Collaborations.125
Figure 75 — Roadway - Payment Collaborations .126
Figure 76 — Transport - Events Collaborations .127
Figure 77 — Transport - Payment Collaborations.127
Figure 78 — Vehicles - Events Collaborations.127
Figure A.1 — The top level of the naming tree for the information classes defined in the data dictionary .128
List of tables
Table 1 —Control classes and operations of the Roadway package.9
Table 2 — Control classes and operations of the Transport package .11
Table 3 — Control classes and operations of the Vehicle package.12
Table 4 — Control classes and operations of the Events package.13
Table 5 — Control classes and operations of the Payment package.14
Table 6 — Operating Interface class and operations .14
Table 7 — Travel Terminal class and operations.15
Table 8 — Vehicle Interface class and operations .15
Table 9 — Roadside Peripheral class and operations .15
Table 10 — Matrix count of Roadway class Interface class collaborations .117
Table 11 — Matrix count of Transport class Interface class collaborations .119
Table 12 — Matrix count of Vehicles class Interface class collaborations.120
Table 13 — Matrix count of Events class Interface class collaborations.121
Table 14 — Matrix count of Payment class Interface class collaborations .122
Table 15 — Matrix count of Roadway class Transport class collaborations .123
Table 16 — Matrix count of Roadway class Events class collaborations.125
Table 17 — Matrix count of Roadway class Payment class collaborations .126
viii © ISO 2000 – All rights reserved

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 main task of technical committees is to prepare International Standards, but in exceptional circumstances a
technical committee may propose the publication of a Technical Report of one of the following types:
— type 1, when the required support cannot be obtained for the publication of an International Standard, despite
repeated efforts;
— type 2, when the subject is still under technical development or where for any other reason there is the future
but not immediate possibility of an agreement on an International Standard;
— type 3, when a technical committee has collected data of different kind from that which is normally published
as an International Standard ("state of the art", for example).
Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether they
can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to be
reviewed until the data they provide are considered to be no longer valid or useful.
Technical Reports are drafted in accordance with the rules given in the ISO/IEC Directives, Part 3.
Attention is drawn to the possibility that some of the elements of this part of ISO TR 14813 may be the subject of
patent rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/TR 14813-3, which is a Technical Report of type 2, was prepared by Technical Committee ISO/TC 204,
Transport information and control systems.
This document is being issued in the Technical Report (type 2) series of publications (according to
subclause G.3.2.2 of Part 1 of the ISO/IEC Directives, 1995) as a “prospective standard for provisional application”
in the field of transport information and control systems because there is an urgent need for guidance on how
standards in this field should be used to meet an identified need.
This document is not to be regarded as an “International Standard”. It is proposed for provisional application so that
information and experience of its use in practice may be gathered. Comments on the content of this document
should be sent to the ISO Central Secretariat.
A review of this Technical Report (type 2) will be carried out not later than three years after its publication with the
options of: extension for another three years; conversion into an International Standard; or withdrawal.
ISO TR 14813 consists of the following parts, under the general title Transport information and control systems —
Reference model architecture(s) for the TICS sector:
 Part 1: TICS Fundamental Services: This document presents the definition of 32 TICS fundamental services
that are the informational products or services or applications areas provided to a TICS user.
 Part 2: Core TICS Reference Architecture: This document describes an abstract object-oriented system
architecture based on the TICS Fundamental Services.
 Part 3: Example Elaboration: This document refines the Core TICS Reference Architecture (Part 2) with some
emphasis on traffic management.
 Part 4: Reference Model Tutorial: This document describes the basic terms, graphical representations and
modelling views exploited in the object-oriented definition of the architecture development of Parts 2 and 3.
 Part 5: Requirements for Architecture Description in TICS Standards: Requirements for Architecture
Description in TICS Standards: This document describes the terminology and form to be used when
documenting or referencing aspects of architecture description in TICS standards.
 Part 6: Data Presentation in ASN.1: This document establishes the use of ASN.1 as the normal syntax notation
to be used in standards for the TICS sector and a common message form for such ASN.1 based data
elements.
Annex A of this part of ISO/TR 14813 is for information only.
x © ISO 2000 – All rights reserved

Introduction
TC204/WG1 is a working group whose prime objectives are to provide services to ISO TC204 and its working
groups. A specific mission of WG1 is to:
“Provide ISO TC204, its working Groups, related bodies and those involved in the TICS sector, with a reference
model of Conceptual Reference Architecture(s) that show the structure and inter-relationships of the sector .”
It is expected that there may well be more than one single TICS Architecture approach to be considered and
documented and that existing architecture approaches will have previously-produced documentation developed
according to disparate standards and conventions.
It is also implicit in the work being undertaken by WG1, that working group members will require a clear, well-
structured understanding of the work of the following participant groups:
 Other TC 204 Working Groups
 CEN TC 278 Working Groups
 Japanese initiatives
 European Road Transport and Traffic Telematics programs
 US Intelligent Transportation Systems program
 Australian initiatives
 Canadian Initiatives
Full documentation of all possible architectural approaches is obviously not feasible given the high level of
resources required to carry this out. Indeed full documentation and description of all possible approaches is
undesirable as an item for Standardisation.
A defined and consistent approach is however required to facilitate the specification of architecture requirements to
enable a clear view to be developed and presented of the work of each participant group This document is one of a
set of WG1 documents intended to respond to stated WG1 objectives regarding the production of a TICS
Reference Architecture.
In order to document an architecture, graphical and textual components of a model are required. WG1 has adopted
a methodology based on the Unified Modelling Language (UML) for documenting the TICS Reference Architecture.
A tutorial on the UML is provided in ISO/TR 14813 Part 4. UML is a visual modelling language for building object-
oriented and component-based systems. A commercially available Computer Aided Software Engineering (CASE)
tool has been used by WG1 to document the Architecture. While the tool is a commercial product, UML is open and
non-proprietary.
TECHNICAL REPORT ISO/TR 14813-3:2000(E)
Transport information and control systems — Reference model
architecture(s) for the TICS sector — Part 3: Example elaboration
1 Scope
The architecture of an information and control system merges hardware and software considerations into a
coordinated and integrated system view. The system architecture is a high level abstraction, or model, of the
system. A system architecture should embrace both today’s applications and the applications that are expected in
the future. Architecture begins with the definition of the conceptual services (e.g. Part 1 - TICS Fundamental
Services). There are several identifiable stages of system architecture development.
a) Reference architecture
b) Logical architecture
c) Physical architecture
A reference architecture is the first of all architectures. It is a concise generic framework which guides the
development of more concrete system architectures. It is large enough that distinct concepts are not merged out of
necessity and small enough that it does not become unwieldy.
A most significant example of a reference architecture in information systems is the Reference Model of Open
Systems Interconnection (often called the seven layer model) developed by ISO in the 1970’s. This model has
underpinned the development of all modern computer networks, allowing services such as global networking, of
which the prime example is the Internet, to become a reality.
A reference architecture is generic and non-prescriptive and captures the concepts of the system. A logical
architecture elaborates the conceptual behaviour, and in so doing it provides more detail about the modularity. A
physical architecture is reached when the actual distribution of the system modules is defined, thus leading to
important implications for communications.
There is no firm demarcation between a reference architecture and a logical architecture. Thus the essence of
behaviour and modularity is present in a reference architecture. The TICS Reference Architecture developed by
WG1 shows important inter-relationships that arise in the provision of the services of the sector. However the TICS
Reference Architecture is more abstract than, for example, the logical architecture of the US National Architecture.
It is envisioned that the TICS Reference Architecture will be used by the TC204 Working Groups to develop their
own logical and physical architectures in a cohesive manner.
Some TICS Fundamental Services are already well developed by the industry, while others are less mature.
Therefore the TICS Reference Architecture does not have a uniform granularity across all services. This
characteristic is a direct result of the fore mentioned requirement that architecture embrace the applications that are
intended in the future. This suggests one of the ways in which the architecture will undergo change in the future.
Architectures may present only static characteristics or both static and dynamic characteristics. Dynamic
characteristics may be seen as belonging solely to the design/implementation stages of system development.
However by including dynamic characteristics at the reference architecture stage one can gain important insights
into the static architecture. Thus two orthogonal views of architecture are presented:
a) static relationship view (class diagram)
b) dynamic interactive view (sequence diagram)
Part 2 develops a Core TICS Reference Architecture. The static scope is determined by deriving the system
boundary and the use cases from an analysis of the TICS Fundamental Services (Part 1).
The Core Reference Architecture is a reference for the development of national architectures.
This Part elaborates the core by refinement of the two orthogonal views. The elaboration calls upon domain
expertise which would be provided by other TC204 Working Groups in the development of ISO standards, or by
national groups developing national architectures and standards.
The Core Reference Architecture is elaborated in Clauses 6 to 8. Clause 5 introduces the elaboration method
employed. Clause 6 elaborates the classes. Clause 7 elaborates the sequence diagrams. Clause 8 describes the
elaborated packages. Clauses 9 and 10 identify some of the main dependencies between the packages.
Readers should refer to Part 4 (Tutorial) for an introduction to the modelling views used in this Part and the overall
methodology.
2 Normative references
The following normative documents contain provisions that, through reference in this text, constitute provisions of
this part of ISO/TR 14813. For dated references, subsequent amendments to, or revisions of, any of these
publications do not apply. However, parties to agreements based on this part of ISO/TR 14813 are encouraged to
investigate the possibility of applying the most recent editions of the normative documents indicated below. For
undated references, the latest edition of the normative document referred to applies. Members of ISO and IEC
maintain registers of currently valid International Standards.
ISO/TR 14813-1:1999, Transport information and control systems – Reference model architecture(s) for the TICS
sector – Part 1:TICS fundamental services.
ISO/TR 14813-2:2000, Transport information and control systems – Reference model architecture(s) for the TICS
sector – Part 2: Core TICS reference architecture.
ISO/TR 14813-4:2000, Transport information and control systems – Reference model architecture(s) for the TICS
sector – Part 4: Reference model tutorial.
3 Terms and Definitions
For the purposes of this part of ISO/TR 14813, the following semantic definitions apply.
3.1
The Unified Modeling Language (UML) is the industry-standard language for specifying, visualising, constructing,
and documenting the artefacts of software systems. It simplifies the complex process of software design, making a
“bl
...