TAP connects every subsystem, supplier and level of the transit network into one coordinated, verifiable ITS.
TAP integrates the fare system, fleet management, passenger information, security and surveillance, depot, energy and communications into a single, coordinated ITS, and connects it to the authority’s central systems, clearing house, vehicle electronics and third-party platforms.
Integration is engineered, not improvised. Every interface is identified, specified in an interface control document, built against simulators and test beds, and verified end-to-end through system integration testing before it reaches passenger service.
System Levels
Integrated Across Every Level of the Architecture
Transit ITS is organized in levels, from the authority’s central systems down to the card in a passenger’s hand. TAP delivers and operates the middle levels and integrates them upward and downward.
-
L4
Authority Central Systems
Integrated by TAPCentral fare management and clearing, network-wide fleet management, passenger information and master data.
-
L3
Management Centers
Delivered by TAPServers and software that manage and oversee the line's fare, fleet, passenger information, security and energy systems.
-
L2
Station & Depot Systems
Delivered by TAPStation and depot computers that concentrate data, store transactions and keep local operations running.
-
L1
Field & On-Board Devices
Delivered by TAPValidators, gates, vending machines, displays, cameras and on-board units at stations and in vehicles.
-
L0
Fare Media
Integrated by TAPContactless cards, bank cards and QR tickets issued within the interoperable fare scheme.
Interfaces
Every Connection Specified and Proven
TAP integrates its systems with each other and with external platforms using open, documented protocols, so the network can grow with new lines, operators and suppliers.
| System | Connected to | Integration basis |
|---|---|---|
| Fare System | ⇄Central Clearing House | Secure messagingSettlement data |
| Fare Devices | ⇄Fare Media | ISO/IEC 14443EMVQRSAM |
| Fleet Management | ⇄Authority Scheduling | GTFSGTFS-Realtime |
| Passenger Information | ⇄Journey Planners & Apps | SIRIOpen APIs |
| On-Board Units | ⇄Vehicle Electronics | CAN J1939Bus-FMSITxPT |
| Security & Surveillance | ⇄Control Center Video Wall | ONVIFVideo streaming |
| Asset Management | ⇄Authority ERP | REST API |
| Sales Channels | ⇄Payment Gateways | PCI DSSTokenization |
| Line Network | ⇄Authority Core Network | Fiber uplinksSegmented VLANs |
Interface Management
A Disciplined Path for Every Interface
TAP manages interfaces as controlled engineering items, from first identification to verified operation, with a clear owner on each side of every connection.
- Phase A
Identify
Every internal and external interface listed with its owners and dependencies.
- Phase B
Specify
Data, electrical and security elements defined in an interface control document.
- Phase C
Agree
Specifications reviewed and approved with the authority and third parties.
- Phase D
Build & Simulate
Interfaces developed against emulators, SDKs and test APIs.
- Phase E
Verify
End-to-end tests prove data flows correctly across every connection.
- Phase F
Control
Changes managed through formal change control throughout operation.
On-Board Integration Sheet
Typical configuration| Architecture | ITxPT-aligned on-board IT architecture |
|---|---|
| Vehicle Network | CAN J1939 with Bus-FMS interface |
| Gateway | Vehicle-to-IP gateway for vehicle data |
| On-Board LAN | Ethernet switch with ruggedized M12 connectors |
| Communications | Vehicle communication gateway with Wi-Fi and 4G/5G |
| Positioning | GNSS geo-location module |
| Connected Devices | Validators, driver console, displays, cameras, passenger counters |
The Bus as a Connected Network Node
On-board systems must work with the vehicle as well as with each other. TAP integrates fare, location, video, passenger counting and information equipment into a common on-board network connected to the vehicle’s own electronics.
Vehicle data such as door status, odometer and diagnostics are read through standard vehicle interfaces, and the on-board network connects to the control center through the vehicle communication gateway.
System Integration Testing
Proven Together Before Passenger Service
Before site-wide rollout, TAP assembles a representative integration test bed that includes every type of equipment and interface, and proves the system works as a whole.
- VehiclesFully equipped buses
- StationsComplete station installations
- DepotDepot systems and wireless
- Control CenterCentral systems and consoles
System Configuration
All devices and subsystems configured to their production settings.
Integrated Operation
Devices and subsystems operating together as one system.
End-to-End Data
Connectivity, data processing, messages and software updates verified across every level.
Scenario Testing
Operational use cases proving every system-level requirement.
Environmental & Electrical
Electrical and electromagnetic compliance in the integrated configuration.
Related
Works Together With
Hardware & Software
Management
Comments are closed