As one of Europe’s busiest commuter rail networks, NMBS/SNCB primarily operates with non-reserved ticketing, allowing passengers to travel flexibly without reserving a specific seat or train. This open-ticketing model supports high-frequency services and gives passengers the freedom to travel when it suits them.

The Challenge: Replacing a long-running bespoke system

For nearly two decades, NMBS/SNCB relied on a bespoke ticketing system that supported its open ticketing model. While the system had served the organisation well, maintaining and adapting it became increasingly challenging as passenger expectations and market conditions evolved.

As the demand for flexibility and digital capabilities continued to grow, NMBS/SNCB needed a more scalable and adaptable solution that could support future fare structures and evolving commercial strategies.

The goal was to move away from a custom-built platform toward a modern Software-as-a-Service solution that could provide long-term stability while remaining flexible enough to support the operator’s non-reserved travel model.

Supporting non-reserved ticketing with S3 Passenger

With the implementation of S3 Passenger, NMBS/SNCB became the first operator to exclusively process non-reserved ticketing on the platform.

This milestone demonstrates the flexibility of S3 Passenger’s architecture, which supports both reserved and non-reserved travel models within the same system. For NMBS/SNCB, this meant adopting a platform capable of handling open ticketing as a standard capability while providing a robust and scalable commercial foundation.

The transition from a bespoke system to S3 Passenger allows NMBS/SNCB to operate on a modern platform designed to evolve alongside the passenger transport industry.

A phased implementation approach

To ensure a smooth transition, the project followed a phased rollout strategy. Multiple workstreams ran in parallel as NMBS/SNCB gradually replaced several existing bespoke systems.

By implementing individual components step by step rather than switching everything at once, the teams were able to minimise risk and maintain stability throughout the process. This structured approach helped ensure a successful go-live while maintaining continuity for both operations and passengers.

Collaboration as a key success factor

The implementation was driven by close collaboration between the Sqills and NMBS/SNCB teams. From the start of the project, both organisations worked closely across departments to ensure a successful transition.

Sqills provided extensive training to the NMBS/SNCB project team, enabling them to effectively work with S3 Passenger. At the same time, NMBS/SNCB shared detailed insights into their business processes and IT landscape.

This exchange of expertise allowed both teams to identify and address potential gaps between operational requirements and the standard capabilities of the platform, ensuring that the system could fully support NMBS/SNCB’s unique operational model.

Building a future-ready platform

The transition to S3 Passenger provides NMBS/SNCB with a modern and scalable foundation for the future.

By adopting a flexible SaaS platform, the operator is better positioned to introduce new fare structures, respond to evolving passenger expectations and continue modernising its ticketing environment.

This milestone also demonstrates the versatility of S3 Passenger, confirming its ability to support both reserved and non-reserved ticketing models within the same platform.