FAQ

1. What is ITxPT?

ITxPT is a non-profit organization open to companies and organizations with an interest in developing public transport into the most efficient, sustainable and attractive means of travel. Its members are a mix of industry, operators and authorities from all over the world. The mission of the ITxPT Association is to enable interoperability between IT systems in Public Transport by offering public specification of an IT architecture based on standards with open interfaces for on-board, over-the-air and back-office IT systems.

2. Why was ITxPT founded?

The mission of the ITxPT Association is to enable interoperability between IT systems in Public Transport by offering public specification of IT architecture based on standards with open interfaces for on-board, over-the-air and back-office IT systems.

3. Who can join the ITxPT Association?

ITxPT is open to all Public Transport stakeholders: Public Transport Authorities (PTAs), Public Transport Operators (PTOs), Vehicle Manufacturers, IT Suppliers and Consultants.

4. How does one become a member? What is the application process?

The first step is to fill in a contact form here. We’ll contact you shortly afterwards to discuss your business needs and expectations from ITxPT membership and help you choose a relevant membership level. We will then send you a membership agreement for you to read and sign, after which you send us back a signed copy. Finally, we’ll ask the ITxPT Executive Board for approval of your candidature, which is usually just a formality. The whole application process usually takes a couple of weeks.

5. What is ITxPT architecture?

The EBSF project defined a set of needs of major stakeholders, travellers, operators and authorities for innovative bus systems in urban and suburban areas using new technologies for vehicles and infrastructure.

ITxPT architecture describes a set of services and the way these services interact or exchange information using an IP network in order to satisfy these needs.

The services are described by focusing on key PT applications like Advanced Vehicle Monitoring System, Dynamic Passenger Information and Remote Diagnosis, defining services such as:

  • Vehicle Gateway
  • Automatic Vehicle Monitoring (AVMS)
  • Multi application driver terminal (MADT)
  • Dynamic passenger information (DPI)
  • Vehicle Fleet Management System (FMS) interface to IP bridge
  • Pre-diagnostic
  • Automatic Vehicle Monitoring (AVMS) integration
  • Dynamic passenger information (DPI) integration

The ITxPT services were grouped into three sides:

  • Vehicle side
  • Back office side and Vehicle – Back-office communication
  • Back-office interoperability

6. Which systems are involved in the ITxPT architecture?

The ITxPT architecture is a logical, service-oriented architecture. Consequently, it allows for multiple possibilities of physical architectures where each device can provide one or more services.

It is perfectly feasible to build a physical on-board architecture where each service is implemented by a different device. For instance, a bus could be delivered equipped with a Gateway, an FMS to IP bridge and a MADT driver terminal. Later an AVMS could be installed and integrated with the existing devices and with a DPI system. Finally, at a different time, a pre-diagnostic system could be installed and integrated with the other devices.

Alternatively, different services, for instance the AVMS and the Gateway, could also be implemented on the same “on-board computer”.

7. Where can I download the ITxPT specifications?

The ITxPT specifications are published in the Documentation Centre. You can download them in the section entitled ITxPT Technical Specifications.

8. How can I register to the Documentation Centre?

All you have to do is to request a new account by clicking here. Once the account is approved, you will be emailed a notification message, including your credentials to log in.

9. How often are the ITxPT specifications updated?

Three levels of updates can be applied to ITxPT specifications, incremented in their release number vA.B.C:

  • Corrective update vA.B.C (e.g. v2.0.1):
    • Applied as soon as an error or bug is reported
    • Frequency: several times a year (if requested)
  • Details update vA.B.C (e.g. v2.1.0):
    • Based on input of experiences and feedback from members
    • Frequency: maximum twice a year (if requested)
  • Main update vA.B.C (e.g. v2.0.0):
    • Includes key extensions and/or changes of current scope based on workgroups and/or project outcomes
    • Frequency: maximum once a year (if requested)

10. How can I be notified of the new updates?

Specification updates are announced in the ITxPT website, in the news section.
The ITxPT newsletter does also share the news, and you can subscribe below. Social networks, such as Twitter and LinkedIn also broadcast such updates.

11. What is the ITxPT label?

The ITxPT label is offered as proof of compliance for any vehicle, software or equipment that has passed the compliance tests. The ITxPT label can be acquired by any supplier, not necessarily an ITxPT Member, and can easily be requested through ITxPT.

The first module was labeled in 2017 and since then several vehicles and modules have been tested for compliance with ITxPT and have officially received the label. All ITxPT-compliant equipment is listed in the Catalogue available from the ITxPT Documentation Centre.

12. How to receive the ITxPT label?

The process for receiving the ITxPT label requires completion of a few steps. For more information, please go here.

13. Vehicle location, voice call or vehicle delay/advance estimates are typical AVMS functions, why are they not described as AVMS services in the ITxPT architecture?

AVMS services are defined within the ITxPT architecture; not the AVMS system itself (this means the functional description).

In order to achieve integration of an AVMS system with other systems such as DPI, some specific services are required. For instance, ITxPT architecture describes how to subscribe to a DPI application in the on-board IP network to receive stop and journey information from the AVMS.

The way the AVMS locates the stops or the end of each journey (the location function itself) is an internal function of the AVMS as a system and not relevant to the ITxPT architecture.

14. What is a Service-Oriented Architecture?

A Service-Oriented Architecture – SOA – is a modular software design architecture where modules exchange information through services. It is based on publication and subscription mechanisms via a defined protocol. An SOA is independent of any technical solutions and products from suppliers.

15. What are the main technologies?

ITxPT architecture is based on well-known Internet technologies which are commonly used in IT systems.

16. Is there an existing European Standards for IT architecture?

Yes, a set IT standards has already been published for PT applications as part of the scope of the CEN group (TC 278 WG3): – at the back-office level like TRANSMODELSIRI and NeTEx – at the onboard level with the recent TS13149 part 7/8/9 based on EBSF project results.

17. Has ITxPT architecture already been implemented in the field?

Yes, there are already some PT references where ITxPT architecture has been implemented and deployed in European PT networks. In addition, some PT tenders already include references to ITxPT or related concepts.

18. How to visit the ITxPT test bench?

Visits of the test bench are available and can be organized here for all interested PT stakeholders who want to find out more about ITxPT architecture.

19. How do I test my modules and services on the test bench?

The ITxPT test bench offers services for ITxPT Principal and Strategic Members to test and validate modules and services compliance with related specifications. Test sessions can be booked on request.

20. Can I download tools to help me implement ITxPT architecture?

ITxPT offers to its Principal and Strategic members a benchmark of available tools which can be used with ITxPT On-board Architecture. It includes available links to download these open tools.