Soyez le premier à aimer ceci
ATA e-Business FORUM 2014, Presentation Proposal, San Antonio, Texas, Bruno Chatel, Chadocs
From the version 2013.1, the ATA Spec 2300 can be considered as ready for implementation. This presentation details the implementation perspectives of the specification in the whole process of Flight Operations data management, from the OEM data producer to the operators’ needs and uses (customization and final pilot uses). It highlights the different possible scenarios to implement the specification, with the triggers, functional areas and the possible approaches, taking into account existing systems and constraints.
After a very short review of the status of ATA Spec 2300 (functional perimeter: Flight Operations data exchange, version 2013.1 all flight crew manuals, ready to implement), the presentation describes the global functional process of Flight Operations data management and identifies where ATA Spec 2300 is designed to be used. It also highlights the expected value-added in the process. OEMs are data producers, providing data to operators who need to customize and publish the flight ops manuals to final users (including on-board/on-ground e-viewer applications)..
Based on this global view, several opportunities to implement systems based on ATA Spec 2300 are studied:
o OEM: producing and delivering ATA Spec 2300 compliant data.
Based on different OEM approaches and taking into account the existing constraints (systems, programs, etc.), several questions are discussed: the triggers for OEM to implement such systems, the possible levels of support of the specification features, and, at a high level, the impacts on the current data production process.
o Operators/airlines: customizing OEM data, producing its own data, publishing in different environments (paper, electronic viewers, on board, on ground).
As an airline would take advantage of receiving ATA 2300 compliant data from OEMs when it will be produced, in the meantime an anticipated approach may be considered. The perspective for an airline to develop a new system to manage its flight operations data needs to consider the advantage of using ATA Spec 2300, a standard business-focused data format, as the core data model of the system and as the internal exchange data format between modules (content management, publishing engines, electronic consultation tools). The advantages and difficulties are discussed with the general principles of using ATA 2300 compliant features at different levels of the airline process.
Finally, for any scenario, the real remaining question is: when?