Airport staff help during system outages
Gate and check-in agents follow outage procedures on a handheld when the network or departure systems go down.
Conductors and onboard staff check rules, fares and procedures between stations with no signal.
A passenger has a ticket for yesterday’s train. What do I do?
Check the fare rules for missed trains. If the delay was caused by the operator, accept the ticket and note it; otherwise sell the difference, per section 6.
Which platform does the connection to the coast leave from?
Platform 3, departing 14:22. You have eight minutes after we arrive, per today’s timetable.
A wheelchair user needs help getting off at the next stop.
Radio the next station to have the ramp ready and note the coach number. Staff meet the train at the accessible door.
Trains run through tunnels, cuttings and rural stretches where the signal disappears. Conductors handle fare disputes, accessibility requests and incidents from memory. Rulebooks are long, updated often, and hard to search on the move.
Conductors, train managers and onboard catering staff on long-distance and regional routes.
Fare rules, ticket validity, onboard procedures and accessibility guidance become the assistant’s knowledge.
The model runs on the handheld, so tunnels and cuttings make no difference.
New fare rules and timetables arrive when devices are back on the depot network.
Every conductor applies the same rule to the same situation.
Answers come from the handheld, not the network.
Connections and accessibility answers come in seconds.
It answers fare questions. Selling tickets stays with your ticketing device.
Yes. Train it on the rules and timetables for every route your crews work.
The same engine can power a passenger app or station kiosk if you want one.
Pick one team and one use case. We’ll have it running on your own devices in weeks.
Ask ChatGPT, Claude or Perplexity and see what they think. One click, instant insight.