Spain is rewriting the contractual basis of its intercity bus network, and the rewrite carries a technology mandate. The new state concession map, or mapa concesional, replaces titles whose original terms date in some cases from the 1990s. Every new corridor contract requires the concessionaire to operate an intelligent transport system, including a fleet management and operations support system based on satellite positioning, plus passenger information covering disruptions.
In Spanish terminology that operations system is the SAE, sistema de ayuda a la explotación, and the passenger-facing layer the SIV, sistema de información al viajero. For any operator bidding on a Spanish corridor, they are now entry conditions rather than differentiators.
Where the concession map stands
The Ministry of Transport put the remaining 31 corridors out for public information in June 2026. Together the new map covers roughly 600 routes and about 2,300 stops across more than 1,600 municipalities, serving over 30 million passengers, with an average fare reduction of around 22 percent per user. The Ministry is co-financing ten corridors, in the order of 8.6 million euros, to keep marginal services viable. The target is approval of the full map before the end of 2026, a deadline set by the Ley de Movilidad Sostenible.
Individual corridors are already moving ahead of the full map. The Bilbao to Castro Urdiales tender was the first of the 2026 programme, and further corridors linking Madrid with Zaragoza, Catalonia, Castilla-La Mancha, Aragón and the Valencian Community have followed.
The consultation was not uncontested. Municipalities, provincial authorities and regions including Castilla-La Mancha and Castilla y León filed submissions, and the debate over service levels in low-density provinces is ongoing. The relevant point for an operator is that the digital requirement was never the contested part. It survived consultation intact.
Three separate modernisation tracks, running at once
Operators looking only at the state concession map are seeing a third of the picture. Three tracks are moving in parallel, on different timelines, and they interact.
The state concession map. Interurban corridors under central government competence. SAE and passenger information are contractual obligations. Timeline: approval targeted before the end of 2026, with corridor tenders rolling.
Regional and autonomous community concessions. Each community runs its own regime, and several are moving faster than the state. Catalonia's Decreto ley 5/2026 of 28 April is the clearest example: it allows current interurban concessions to be extended by up to six years, explicitly as compensation for mandatory investment in fleet decarbonisation and improved passenger information systems, with the underlying climate and digitalisation objectives to be met before 1 January 2029. In other words, an extension is granted in exchange for investment, and the investment includes the information layer.
Urban networks. Municipal and metropolitan services procure independently, frequently as combined supply and software contracts covering stops, shelters, displays and the management system behind them. These are smaller contracts, they move quickly, and they are often where a supplier relationship starts.
An operator active across more than one of these tracks has to assume the requirements will not arrive in a coordinated way, and that the same fleet will need to satisfy several reporting interfaces.
The funding route operators most often miss
Spain's Recovery, Transformation and Resilience Plan channels 220 million euros to the autonomous communities, Ceuta and Melilla for the modernisation and digitalisation of regional and local transport, within component 6 on sustainable, safe and connected mobility. Of that, 110 million is directed at modernising and digitalising private companies in the passenger and freight road transport sector, including small and medium-sized enterprises and self-employed operators, distributed through open grant calls managed by the communities themselves.
Two practical consequences follow. Grant calls are managed regionally, so the calendar and the eligibility criteria differ by community and an operator working across several regions is tracking several calendars. And because the calls are competitive and time-bound, the operators that benefit are the ones that already know which system they intend to deploy when a call opens. Choosing the system after the call is published is usually too late.
What the SAE requirement means in practice
The contractual language is short. The operational reality behind it is not. A specification asking for satellite positioning and real-time fleet information implies several things that are worth being explicit about before signing.
Position capture that survives Spanish geography. Interurban corridors cross terrain with real connectivity gaps. A system that treats a coverage gap as missing service will generate compliance problems that did not happen. Buffering on the vehicle and reconciliation on reconnection is a baseline requirement, not an option.
Trip-matched data, not raw tracking. A GPS trace is not schedule adherence. The obligation is to know whether the declared service ran as declared, which requires positions matched to the assigned trip. This is the single most common gap between what an operator buys and what the concession expects.
Passenger information triggered from the same event. The SIV obligation covers communicating incidents. If disruption messaging is a separate system fed manually, it will lag the operational reality during exactly the events it exists for.
Reporting the granting authority accepts. Different corridors and different communities will ask in different formats. The question to put to a supplier is whether an arbitrary past period can be reproduced unattended, not whether reports exist.
Standards, because there are several counterparties. GTFS and GTFS-RT for journey planners and public data, plus the interfaces the specific authority requires. Native support matters more than a promise to build an exporter.
A reasonable sequence for an operator
Operators facing all three tracks at once tend to succeed by decoupling the technology decision from the contract calendar.
Start with the fleet data layer, because it is common to every requirement you will face. Continuous position reporting matched to planned trips satisfies the SAE obligation, feeds passenger information, and produces the evidence base for reporting, regardless of which corridor or community asks.
Then clean the static schedule data and publish it properly. Nothing downstream, prediction, passenger information or reporting, is better than the timetable and stop data it references.
Then add the passenger information layer on top of the same event stream rather than beside it.
And keep the funding calendar and the deployment calendar separate. An operator with a chosen platform and a costed deployment can respond to a regional grant call in the window it is open. An operator starting the evaluation when the call publishes will miss it.
Frequently asked questions
Is a SAE mandatory for all Spanish bus operators?
It is a requirement of the new state concession contracts, and it appears in regional and urban specifications too. It is not a blanket national obligation on every operator today, but for anyone bidding on a new concession it is a condition of entry.
What is the difference between SAE and SAEIV?
SAE covers the operations side, vehicle location and schedule adherence. SAEIV adds the passenger information dimension. Spanish specifications frequently split the two, with SAE for operations and SIV for passenger information.
How long does a SAE deployment take?
Software configuration and onboard installation are usually measured in weeks per depot. The longer items are schedule data cleaning and, where displays are involved, on-street works. Sequence them in parallel rather than in series.
Do the recovery plan funds cover software?
The digitalisation line is aimed at modernising and digitalising transport companies, and calls are defined regionally. Eligible cost definitions vary by community, so the operative step is reading the specific call rather than the national framing.
If you are preparing a bid on a Spanish corridor or responding to a regional digitalisation call, Pysae's team can walk through what a SAE deployment looks like on an interurban fleet, including data publication and the reporting evidence the concession expects.