Bill Cunningham, Boeing Bruno Chatel, Chadocs 2012 ATA eBusiness Forum, October 22-24, 2012, Applicable Standard: ATA Spec 2300 Topic: Flight Operations Digital Data Abstract: This will be a joint presentation given by Bruno Chatel of Chadocs and Bill Cunningham of the Boeing Company. The presentation provides an update on the current status of ATA Specification 2300, as of Release 2011.2 and the schema consolidation effort that the FOIG is undertaking for CY 2012. It includes background on why the FOIG is creating a unique specification for flight operations data. It also provides information on some features of data management using XML concepts in the current release. Historically, every airplane maker developed proprietary tools and software to create and deliver flight operations data to their airline customers. They created unique data structures and system architecture to support their data and documents. Airlines need to purchase and maintain multiple customization and publishing systems and environments for their fleets. Airlines have asked for a common data standard for flight operations documents. This standard would allow them to set up a single interchange system for flight operations, regardless of airplane model or manufacturer. The ATA Flight Operations Interest Group (FOIG) works to develop data structures and standards that support data interchange for flight operations documents. The results of their efforts are published as ATA Specification 2300. The purpose of Spec 2300 is to provide a concise set of information standards and guidelines for the management, configuration and interchange of flight operations technical data. Based on XML standards, Spec 2300 uses advanced modular organization of data, giving opportunity for a progressive data exchange protocol. It uses a data-centric approach, focusing on defining individual data objects, known as data modules that represent a unique piece of technical content. Each data module has it own life cycle, revision and configuration management. In addition to the technical mark-up of individual data modules, Spec 2300 contains detailed sections on data management, applicability management, meta-data, revision management and publication management. When implemented Spec 2300 will provide interchange mechanisms that are non-proprietary, software / hardware independent, integrity checked, secure and self-verified.