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.
Yes, there are already sevral PT references where ITxPT architecture has been implemented and deployed in PT networks. In addition, many PT tenders now include references to ITxPT or related concepts.
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.
ITxPT architecture is based on well-known Internet technologies which are commonly used in IT systems.
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.
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
- 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
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.
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)
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. The ITxPT Statutes comprehensively describe bodies and rules of the Association.
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.
The process for receiving the ITxPT label requires completion of a few steps.
The ITxPT label is offered as proof of compliance for any vehicle, software or equipment.
The ITxPT label can be obtained by any supplier who has passed the compliance tests within the label procedure. It is not necessary to be an ITxPT member to apply for the label, the application form is available in the procedure or directly here. The related fees are detailed on this page.
All ITxPT-compliant equipment is listed in the ITxPT catalogue, also available in the ITxPT Documentation Centre.
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.
The ITxPT laboratories offer 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.
Visits of the showroom and test bench of ITxPT laboratories can be organized for all interested PT stakeholders who want to find out more about ITxPT architecture.
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. The whole application process usually takes a couple of weeks.
ITxPT is open to all Public Transport stakeholders: Public Transport Authorities (PTA), Public Transport Operators (PTO), Vehicle Manufacturers, IT Suppliers and Consultants.
Software & Tools
The ITxPT github resource which can be reached via https://github.com/ITxPT provides examples and validation schemas. Specifically, for the GNSSLocation service these can be found under: