DS StationInfo holds the operational information your airline runs on, in a structure you build yourself. Any department can own an area of it, and any system can read from it, so it grows on both sides as the operation does.
Categories, fields and data groups follow the way your airline is organised, and they move when the organisation moves.
Every department maintains its own area of one structure, and the application and your own systems both read from it. The departments and the systems shown are only examples: you build the structure on one side, and the open API takes whatever you connect on the other.
Flight operations, technical operations, ground operations, cabin crew and catering run from the same structure, and any other part of the airline can hold its own area. Each one is maintained by the people who hold that knowledge.
Station content is edited as a revision against the version currently published, so work in progress stays out of the application until it is released.
Everything held in StationInfo is available over a documented API, an open architecture your own systems plug into. There is no fixed list of what can consume it: operators feed their own systems from it and build their own applications on top of it, including the channels their passengers use.
The dashboard opens on a map of every station you operate, with a side panel alongside it carrying the summary, the pending updates, your filters and current alerts.
REST APIs, Active Directory support, and cloud hosting we run and maintain for you. Other arrangements are available on request.
Nothing changes quietly. Every action is logged and stored, and the revision timeline shows exactly what changed and when. Date fields raise their own alerts, so a renewal or an expiry reaches the people who own it before it lapses.
We will show you StationInfo carrying a real airline structure.
