Smart Transit Payments Architecture — 2014 Case Study (Kyiv)

Technological Breakthrough That Did Not Fit the Old System

In late 2013 and early 2014, the development of a unified passenger flow accounting and electronic ticketing system for Kyiv’s public transport began. The goal was to replace the outdated, fragmented fare collection methods for the metro, trams, trolleybuses, buses, suburban trains, and funicular, creating a seamless, citywide transport payment network.

The Arrival of a Team with Ready-Made Solutions

At 53 years old, I started the project, bringing with me extensive experience in developing information concentrators, communication nodes, and network solutions for complex distributed systems.

• 🚌 🚛 I brought with me a team of trusted developers and a truck full of ready-made solutions accumulated over years of prior work.
• 🛠 We did not reinvent the wheel; instead, we integrated tried-and-tested technological solutions to ensure the system’s reliability and flexibility.

However, once our solutions were integrated, everything we contributed suddenly became "company-confidential information."

System Architecture: The Concentrator as the Nervous System

To make the system scalable and fail-safe, we built it on a two-layer "sandwich" principle:

• Physical infrastructure (network-dependent layer) – handling data transmission and device communication.
• Logical platform (network-independent layer) – responsible for routing, prioritization, and transaction processing.

The Role of the Information Concentrator

💡 The information concentrator became the central node of the system, performing three main functions:

1. Real-time data collection – processing millions of messages from terminals, turnstiles, and ticketing servers.
2. Message analysis and prioritization – categorizing them as "lightning," "urgent," "standard," or "background."
3. Load optimization – accumulating data during peak hours and flexibly offloading it during less busy periods.

🔗 The Oracle database was connected to the concentrator under a single account, which was supposed to significantly reduce licensing costs. However, due to misguided managerial decisions by the company’s owners — who overestimated their management skills while lacking sufficient IT experience — this opportunity was unfortunately missed.

Innovations: Accounting and Security System

1. "Internet of Things" or "Intranet of Things"

The system was built on TCP/IP and essentially became an "Internet of Things" network before IoT became mainstream. Or rather, an "Intranet of Things," where a closed network of smart devices operated within the city’s transport system.

2. Multi-Level Message Prioritization

• 📡 "Lightning" – emergency and critical control commands.
• 🎟 "Urgent" – ticketing transactions and payment processing.
• 📊 "Standard" – analytical and reporting data.
• 📥 "Background" – file transfers and non-time-sensitive operations.

This mechanism ensured instantaneous reactions to critical events while preventing network congestion.

3. Fraud Detection and Prevention

🚔 The system was designed to detect fake tickets by analyzing anomalous transactions and identifying fraudulent activity.

Security: Political Barriers and Bureaucratic Sabotage

The original design included:

• 🔐 Hardware-based encryption for data transmission.
• 💾 Ukrainian-certified cryptographic solutions.
• 🚫 Guaranteed protection from third-party interference.

However, in 2014, during the political turbulence, the situation changed:

• 🚧 The encryption implementation was blocked at the bureaucratic level.
• 🗣 The project owner failed to argue for its necessity.
• ⚖ Under the then-existing administration, security took a backseat to political maneuvering.

📉 This effectively killed the flexible tariff system and complicated system integration.

Testing and Demonstration

🚆 A test system was deployed in Kyiv City Hall, while the central server was in Kharkiv.

📊 Real-time data was displayed on large screens, tracking ticket purchases, card validations, and passenger flow through turnstiles.

👀 Even Kyiv Mayor Vitaliy Klitschko personally inspected the system and was pleasantly surprised.

Financial Collapse: Why Did It Fail?

Two months before the demonstration, the company ran out of money for salaries.

Reasons:

• 👥 Instead of hiring technical specialists, management hired "watchdogs" to oversee developers.
• 📉 Bloated bureaucracy rather than proper IT project management.
• 💸 Complete mismanagement of resources. The company's management lived large, drove a luxury car, rented a corporate apartment right in the center of Kyiv, set up an office in Kharkiv, and established a lavish, spacious office in downtown Kyiv with a brand-new, beautiful renovation.

📢 I made the decision to complete the project for free, fulfilling my commitment.

🚪 But after the successful demonstration, I resigned – because working for free under capitalism is immoral.

💻 The developers who joined with me also left, making further system implementation impossible.

Conclusions: What Remains of the Project?

• ✔ Development of a unified system for access management and fare payment in urban transport, including transfer tracking under the 'unified ticket' scheme.
• ✔ Innovative technologies – prioritization, data protection, and fraud prevention.
• ✔ Early "Intranet of Things" implementation.

Most importantly, the project proved the feasibility of the idea.

💡 If not for bureaucratic barriers and managerial incompetence, Kyiv could have implemented a full-fledged world-class passenger accounting system in summer 2014. Its core would have been the time-tested Information Concentrator model, featuring priority queues – technology with unmatched reliability since 1999.

Epilogue

🛠 The system worked.

🔌 It was ready for launch.

🚇 But it was never allowed to go live.

Technology endures. The solutions developed for this project may yet form the foundation for future smart transport systems in Ukraine and beyond.

🚦 Although the project was eventually transferred to another team in a stripped-down form and adapted for implementation in other cities, it lost its original momentum and innovative edge. Valuable time was wasted, and key technological advantages were diluted. Nevertheless, the core architectural principles — though protected by NDAs — proved their viability. In future publications, we will outline these foundational concepts without breaching confidentiality.

💎 The true tragedy is that Kyiv residents paid the price for these decisions through decades of outdated technology.