Rail & public transit | Modelled case study
Rotate fare-system keys across gates, validators, and mobile wallets
Can new keys become active across every channel without rejecting riders or extending old trust indefinitely?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Fare Systems · Payments Security · Station Operations functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
A transit operator runs signalling support, fare collection, station systems, fleet maintenance, mobile channels, depots, and supplier diagnostics.
What is at stake
Trust changes must not interfere with safe movement, rider access, revenue collection, maintenance release, or recovery from field connectivity gaps.
Situation
Offline validators, concession devices, account-based systems, bank interfaces, and mobile credentials update at different rates.
Event that forces action
Payment-scheme change, key expiry, new fare medium, or suspected compromise.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
station gates and validators
mobile wallet backend
fare clearing service
key activation and retirement schedule
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Offline validators, concession devices, account-based systems, bank interfaces, and mobile credentials update at different rates.
Frame the decision the owners must make
Can new keys become active across every channel without rejecting riders or extending old trust indefinitely?
Apply QNSI to the controlled boundary
Track key generations, device cohorts, activation windows, algorithms, issuers, and last-seen validation in QNSI.
Leave the team with a concrete result
A fare-key cutover plan with overlap limits, station readiness, offline acceptance, fraud monitoring, and retirement proof.
Prove the result in the organisation's environment
The authority tests payment compliance, passenger impact, revenue protection, offline behavior, settlement, and rollback.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A fare-key cutover plan with overlap limits, station readiness, offline acceptance, fraud monitoring, and retirement proof.
Independent validation boundary
The authority tests payment compliance, passenger impact, revenue protection, offline behavior, settlement, and rollback.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.