FleetCaptain is easy to use. All that’s needed is a computer with a web browser and a reliable internet connection. Type in the web address of an interface, log in and you’re ready to go. The system can run on any reasonably modern computer and web browser, needs a printer for the flight authority form, and smartphone or tablet devices for various other interfaces. Apple and Android mobile operating systems are supported. FleetCaptain also supports a variety of television status boards for the dispatch and maintenance areas.
Behind the scenes, FleetCaptain uses the latest technology to provide seamless service to the operations team. For example “push” technology is used to automatically send updated information from one browser to another – avoiding the need for anyone to refresh their screen. When a plane is returned, its new status becomes available to everyone else. Its maintenance times are automatically re-calculated and sent to every other interface to ensure everyone is using up-to the second data at all times. If one dispatcher is dispatching a plane, that plane becomes temporarily unavailable to other dispatchers so there is no chance of conflict. It is natural to use, but there’s a lot of communication going on behind the scenes to make it all work. In addition there is a specialized framework for generating graphs and for mobile device functions. The hard work is done by the system so the people can concentrate on their work.
OK – This looks a little complicated. For people who want to take a look behind the scenes, this is what the topology overview looks like. For people who don’t – here’s the point:
All aircraft, flight and other operational data is backed up as it is generated, in an off-site location. If there should be some kind of disaster at the main location, the data remains safe, and operations can be restored by accessing the backup location over the internet. Flight records are a regulatory requirement so this architecture ensures they remain safely backed up.