
Introduction
This section supports the development of plans and specifications by providing the following information:
- Actors: who need to be considered in the development of the system.
- Architecture and Data flows: showing how administrators and users interact and use the system, to help identify and develop the needs and specifications of the system.
- Standards: that are important and how these are used in the context of this use case.
- Possible future developments: in practices and technology that may provide opportunities in the future.
Actors
The service design is functionally described by the interaction between the service and the actors (any user or system that interacts with the service).
The following actors need to be considered in the development of the service design:
- Road users: who interact with traffic signals either directly through the use of on-road facilities, or indirectly through the use of services using the data provided by traffic signal infrastructure.
- Authority: who is legally responsible for providing and operating the traffic signal control system.
- Third-Party providers: third parties may support Authorities in implementing and operating traffic signals through the supply of products and/or services. They may also deliver digital services to road users supported by data derived from the signal facilities.
Architecture and Data Flows
For the purpose of the information and diagram presented in this section, a road user journey is defined as a single journey undertaken by one vehicle. However, similar activities apply to navigation service providers and logistics managers.
The data flows are illustrated in Figure 2 – Idealised road user journey for traffic signal control and Figure 4 – Idealised Traffic Signal Control Manager’s processes.
The data requirements and data flows are tabulated in Figure 3 – Data Requirements for idealised user journey for signal controls and Figure 5 – Data Requirements for Idealised Traffic Signal Manager / Administrator Activities.

Interfaces
Interfaces between systems and services depend on the specific design and the boundaries with other systems and services. The general principle is that interfaces should be specified to use standardised data flows wherever standards are available such as UTMC, and specifications such as TOPAS.
Standards and Specifications
It is important to align with and/or support the development of National Standards:
- To ensure the digitalised services consumed by customers is Authority agnostic and users do not have to have different apps/services for different towns and cities.
- To ensure the services can interface with recognised customer-facing accounts e.g. Google, Apple, OEM -based services.
DATEX II (CEN/TS 16157) is a multi-part set of international data content and framework standards for road transport and traffic telematics.
UTMC provides traffic managers with open technical specifications that support an innovative, competitive, marketplace that assists effective system interworking. The Urban Traffic Management Control Specification and Standards Group produces and maintains UK intelligent transport systems technical specifications which is the core of the UTMC initiative. This includes:
- The TS003 framework specification: defining the general architecture for UTMC systems which is based on current mainstream ICT practice where practicable and aims to avoid bespoke solutions which are difficult to support.
- TS004 objects register: defies the formats and structures of data objects used in UTMC systems including traffic control system functions, the road network descriptors and information structures such as “predictions” or “faults”.
- UTMC provides guidance and good practice on UTMC linked specifications. This includes traffic data as DATEX II profiles, which can be considered for implementation by traffic managers in their UTMC systems’.
Since April 2016 TOPAS (Traffic Open Products And Specifications) replaced the previously statutory Type Approval and TOPAS Product Registration became live for new product registrations for traffic control equipment, with the aim of promoting convergence of specifications to reduce the risk of operational problems. TOPAS’ product registration enables customers to verify compliance of solutions they purchase and Authorities may specify TOPAS compliance within their procurement documents.
Under the European ‘Co-operative Intelligent Transport Systems’ (C-ITS) programme a range of standards have been produced and continue to be developed. ITS specifications are developed to address specific service domains such as public transport, road safety, freight and logistics, emergency services and systems such as electronic fee collection.
C-ITS services are based on the concept of data exchange between vehicles of any category, the roadside infrastructure, control and service centres and other road users such as pedestrians and cyclists with guidelines on their use published by ISO and CEN.
Possible Future Development
Areas currently near to market and in development include:
- Real-time model signal strategies, potentially using AI approaches. Several vendors offer strategy selection systems and AI UTC systems that will compete with traditional systems, and many more are in the pilot stage.
- New sensors at the roadside to replace loops, especially using image processing to identify and classify pedestrian and cyclists as well as monitoring traffic movements.
- Use of floating vehicle data to replace or augment data collected from sensors.
- Linking UTC plans to wider services such as in-vehicle information.
- Potential new Public Transport priority systems based on BODS.