ITxPT, tenders and “no lock-in”
– where do Adibus and ChargePlan fit in?

Adibus and ChargePlan are built around exactly this logic: an open architecture where both bus IT and charging management can be replaced, expanded and combined without having to start from scratch.
 

ITxPT as a safety net in tenders

Seen from a PTA or PTO perspective, ITxPT is about three things:

• A common language – standardised interfaces for data, services and equipment.
• Interoperability – several suppliers can deliver equipment to the same bus or depot as long as they follow the standard.
• Future-proofing – new systems can be added later without rebuilding the entire architecture.

By including ITxPT requirements in a tender you essentially specify that buses must be able to operate in a multi-vendor environment, that data must be exchanged according to a defined standard, and that future components – such as new screens or new charging suppliers – can be added as long as they speak the same language.
 

Adibus – ITxPT in practice

Adibus is active in the ITxPT community and has for years delivered projects where both hardware and software follow the standard. In practice this means that the Vehicle Communication Gateway (VCG) and bus IT are built on ITxPT principles and that data from the bus – position, doors, HVAC, energy and more – is exposed via well-defined services. Passenger information, real-time data, fleet management and reporting can be combined with systems from other suppliers without bespoke integrations every time.
 

ChargePlan – open charging management, not an isolated island

On the charging side, ChargePlan is the natural companion to the ITxPT mindset. ChargePlan is an intelligent charging management system that optimises charging based on available power at the depot, timetables and electricity prices. It can run as a standalone solution or in a professional configuration integrated with planning and operational systems for even more precise energy planning.
 

For tender work it is important that ChargePlan is technology-neutral and can work with different charger brands and different vehicle types. This makes it easier to require smart charging without at the same time locking yourself into a specific hardware supplier.
 

Five concrete requirements you can include

Below are five plain-language formulations that can be adapted to your legal templates:

• 1. ITxPT-based bus IT
  “Bus IT, including AVMS and passenger information, must be based on the ITxPT standard and support interoperable cooperation with third-party systems.”
• 2. Open interfaces for real-time data
  “Real-time data (position, predictions, events) must be provided via documented, open APIs so it can be reused in other systems (e.g. national data hubs).”
• 3. Standardised charging management
  “The charging management system must be able to integrate with AVMS/ITxPT or planning systems in order to optimise charging according to timetable and electricity price.”
• 4. Vendor-independent architecture
  “The system architecture must be documented with clear interfaces so that the PTA can replace individual components (bus IT, chargers, charging management) without replacing the entire solution.”
• 5. Data ownership and access
  “The PTA/PTO must have long-term access to operational and energy data in machine-readable formats for reporting and further analysis.”

Adibus’ ITxPT-based bus IT and ChargePlan already meet these principles in ongoing projects. This gives tangible assurance when you as a buyer want to use ITxPT as a safety net to avoid vendor lock-in and at the same time ensure future flexibility.

Glossary

ITxPT – Information Technology for Public Transport – European standard for open, modular IT architecture in public transport.)

PTA – Public Transport Authority – public transport authority that orders and finances public transport services.)

PTO – Public Transport Operator – operator responsible for day-to-day bus or rail operations.)

VCG – Vehicle Communication Gateway – communication unit in the bus that collects and distributes data.)

HVAC – Heating, Ventilation and Air Conditioning – heating, ventilation and air conditioning system in the bus.)

API – Application Programming Interface – technical interface used for automated data exchange between systems.)