Flight Operations Data - Spec 2000spec2000.com/presentations/lucb.pdf · Flight Operations Data Air Transport Association Flight Operations Working Group ... Flight Crew Training

Flight Operations Flight Operations DataData

Air Transport AssociationAir Transport AssociationFlight Operations Working GroupFlight Operations Working Group

Luc Bourgon, Bombardier

October 28, 2004 ATA E-Business 2

•• Flight Operations information has very few standard Flight Operations information has very few standard taxonomies.taxonomies.

•• There are no industry wide standards for Flight There are no industry wide standards for Flight Operations documentation:Operations documentation:•• Common Data for Flight Manuals was desired 40 years ago Common Data for Flight Manuals was desired 40 years ago

at the same time ATA Spec 100 was being developedat the same time ATA Spec 100 was being developed•• Airlines and Manufacturers could not agree on common data Airlines and Manufacturers could not agree on common data

structure structure

•• Common Flight Manuals structure is still seen as Common Flight Manuals structure is still seen as impossible to agree onimpossible to agree on

The Problem with Operating The Problem with Operating DocumentsDocuments


•• ICAO ICAO ( 187 Member states)( 187 Member states) requires standard informationrequires standard information•• RegulatorsRegulators ((JAA, FAA, T/C)JAA, FAA, T/C) require require (and audit for)(and audit for) standard standard

information across fleet typesinformation across fleet types•• Manufacturers Manufacturers (4 major)(4 major) deliver information in diverse deliver information in diverse

structures and formatsstructures and formats•• OperatorsOperators rere--format and deliver internal documentation format and deliver internal documentation

in some internal, standard formatin some internal, standard format

Flight Operations InformationFlight Operations InformationOperating Manuals Operating Manuals ReviewReview


Manuals Manuals Delivered Delivered to to Operators by ManufacturersOperators by Manufacturers

••Airplane Flight Manual (AFM)Airplane Flight Manual (AFM)••Approved information in manufacturer’s jurisdictionApproved information in manufacturer’s jurisdiction

••Flight Crew Operating Manual (FCOM)Flight Crew Operating Manual (FCOM)

••Quick Reference Handbook (QRH)Quick Reference Handbook (QRH)

••Flight Crew Training Manual (FTCM)Flight Crew Training Manual (FTCM)

••Master Minimum Equipment List (MMEL)Master Minimum Equipment List (MMEL)••(Only common link between Flight Ops and Maintenance)(Only common link between Flight Ops and Maintenance)

••Configuration Deviation list (CDL)Configuration Deviation list (CDL)


No StandardsNo Standards for Manuals for Manuals between Manufacturersbetween Manufacturers

AIRBUS BOEING BOMBARDIER EMBRAER

VOLUME 1

Systems Arranged by: ATA Spec

Limitations Normal Procedures Supp Procedures

Systems Arranged by: Alphabetic

General Limitations Emerg/Abnormal Normal Proc Performance Flight Planning Weight and Balance Loading Config Dev List Min Equipt List Emerg Info Emergency Evac Grnd Servicing

VOLUME 2

Loading T.O Perf Land Perform Special Ops Flight Planning

Systems Arranged by: Alphabetic

Limitations Checklists Normal Ops Supp Procedures Emergency Abnormals Performance Spec Ops In Flight Checks

Systems Arranged by Chronological Use

VOLUME 3 & 4

Limitations Abnormals Std Oper Proc Supp Technics In Flight Performance Engine Out Ops FMGS Volume

QRH Emergency Abnormals

ALL Non-normals ALL Performance

Emergency Abnormals

Normals Section Abnormals: Emergency Cautions

FORMAT

SGML w/FrameMaker CD-ROM (html) Paper

Some SGML FrameMaker PDF Paper

Quicksilver / (Interleaf) Paper

Word, PDF Paper

PAGE 5.83 x 8.27 (A5) 5.5 x 8.5 5.5 x 8.5 5.5 x 8.5


ICAO ICAO RegulationsRegulations

Dictate to all member states (187) basic requirements for Dictate to all member states (187) basic requirements for flight operations information in ANNEX 6flight operations information in ANNEX 6

Member states must comply to fly internationally or file Member states must comply to fly internationally or file a difference of nona difference of non--compliancecompliance

a)a) policy and administration manual;policy and administration manual;b)b) aircraft operating manual;aircraft operating manual;c)c) minimum equipment list (MEL) and configuration deviation list minimum equipment list (MEL) and configuration deviation list

(CDL);(CDL);e)e) training manual;training manual;f)f) aircraft performance manual;aircraft performance manual;g)g) route guide;route guide;h)h) Etc.Etc.


Manuals Required by State Manuals Required by State Regulators Regulators for Operatorsfor Operators

Aircraft Operating Manual Aircraft Operating Manual (AOM)(AOM) (FAA...CFM)(FAA...CFM)

Flight Crew Training Manual Flight Crew Training Manual (FCTM)(FCTM)Flight Operations Manual Flight Operations Manual (FOM)(FOM) (FAA…COM, FOPM)(FAA…COM, FOPM)

Master Minimum Equipment List Master Minimum Equipment List (MMEL)(MMEL)

These manuals must be be These manuals must be be Approved/Accepted by regulatorsApproved/Accepted by regulators


•• Standard structure of manuals increases user Standard structure of manuals increases user acceptance of informationacceptance of information

•• Standard location of information between Standard location of information between fleets for users transitioning between fleets for users transitioning between aircraft typesaircraft types

•• Mental Model of information is enhanced in Mental Model of information is enhanced in company procedures and policies company procedures and policies

Most Large Commercial Operators Most Large Commercial Operators Use Use Internal StandardsInternal Standards


Support for Standard:Support for Standard:NASA / FAA Document ProjectNASA / FAA Document Project

“Across fleet standardization should be “Across fleet standardization should be established at several levels, from operational established at several levels, from operational philosophy through procedures, to the use of philosophy through procedures, to the use of common formats and terms in the different common formats and terms in the different fleets. Operators should establish formal fleets. Operators should establish formal working groups and processes to ensure working groups and processes to ensure standard procedures across fleets. ”standard procedures across fleets. ”


Support for Standard:Support for Standard:NASA Report NASA Report

“We recommend a three“We recommend a three--way approach for a way approach for a crosscross--fleet standardization. (1) development fleet standardization. (1) development of a crossof a cross--fleet philosophy, (2) creating a fleet philosophy, (2) creating a crosscross--fleet standardization forum, and (3) fleet standardization forum, and (3) obtaining input for procedural design from obtaining input for procedural design from personnel that design, certify, teach, use and personnel that design, certify, teach, use and check procedures. ”check procedures. ”


An operator’s documents system should An operator’s documents system should ensure standardization across flight ensure standardization across flight document types, including formatting, document types, including formatting, writing standards, standard writing style, writing standards, standard writing style, terminology, use of graphics and symbols and terminology, use of graphics and symbols and formatting across documentsformatting across documents. This includes a . This includes a consistent location of specific types of consistent location of specific types of informationinformation, consistent use of units of , consistent use of units of measurement and consistent use of codes.measurement and consistent use of codes.

Support for Standard:Support for Standard:ICAOICAO


“Principle Operations Inspectors (Principle Operations Inspectors (POI’sPOI’s) ) should ensure that operators standardize should ensure that operators standardize their operating procedures both within and their operating procedures both within and across aircraft types to the greatest extent across aircraft types to the greatest extent possible”possible”

“...Standardized procedures promote understanding and effective “...Standardized procedures promote understanding and effective communications communications between crewmembers…Crewmembers of most large operators operate between crewmembers…Crewmembers of most large operators operate numerous numerous different aircraft during their career. Standardized procedures different aircraft during their career. Standardized procedures enhance a enhance a crewmember’s transfer of learning...complete standardization of crewmember’s transfer of learning...complete standardization of procedures is not procedures is not possible when there are significant differences between manufactpossible when there are significant differences between manufacturers and installed urers and installed equipment. A high degree of standardization, however, is possiblequipment. A high degree of standardization, however, is possible…”e…”

Support for Standard:Support for Standard:FAAFAA


“Since it is believed that a high degree of “Since it is believed that a high degree of standardization of Operations Manuals standardization of Operations Manuals within the JAA will lead to improved overall within the JAA will lead to improved overall flight safety, it is strongly recommended that flight safety, it is strongly recommended that the structure described in this IEM the structure described in this IEM (interpretive (interpretive

explanation material) explanation material) should be used by operators as should be used by operators as far as possible.”far as possible.”

Support for Standard:Support for Standard:JAAJAA


Regulators...Regulators...•• Regional Regional -- JAA tries to do this but is not popular JAA tries to do this but is not popular

amongst member (and nonamongst member (and non--member) statesmember) states•• Added expense to comply when manufacturers do Added expense to comply when manufacturers do

not complynot comply•• Individual states force additional expense to Individual states force additional expense to

airlines under jurisdictionairlines under jurisdiction

WhoWho do you turn to for do you turn to for standards in the industry?standards in the industry?


Operators or Manufacturers...Operators or Manufacturers...•• Provide information based upon legacy formatsProvide information based upon legacy formats•• Interested in selling proprietary system and updatesInterested in selling proprietary system and updates•• In competition with each otherIn competition with each other•• Each has individual formats and structures of informationEach has individual formats and structures of information•• Each operator has specific needs, i.e., areas of operations, Each operator has specific needs, i.e., areas of operations,

large and small operations, etc.large and small operations, etc.



Support Groups…Support Groups…•• Each have differing ideas of applications for Each have differing ideas of applications for

flight operations documentationflight operations documentation


Third Party Vendors…Third Party Vendors…•• Corporate proprietary standardsCorporate proprietary standards•• Industry would be at the mercy of corporate Industry would be at the mercy of corporate

entityentity



Industry OrganizationsIndustry Organizations

•• ICAO…regulator at the highest levelICAO…regulator at the highest level•• IATA…standards development with ICAO IATA…standards development with ICAO •• ATA…industry organization known for ATA…industry organization known for

specifications development specifications development


The SolutionThe Solution

• Flight Operations Working Group was formed within the ATA to develop a common data interchange model for Flight Operations Data


Flight Operation Working Flight Operation Working GroupGroup

FOWG created in 1997FOWG created in 1997•• Prior attempts failed because they focused on Prior attempts failed because they focused on

setting paper/word processing standardsetting paper/word processing standard

Meet 3Meet 3--4 times/year4 times/year•• Up to 15 Air Carrier / OperatorsUp to 15 Air Carrier / Operators•• All 4 major ManufacturersAll 4 major Manufacturers•• Up to 12 vendors/consultants/suppliersUp to 12 vendors/consultants/suppliers

International RepresentationInternational Representation


““To develop a specification for the cost To develop a specification for the cost effective and efficient interchange of effective and efficient interchange of digital data between Information digital data between Information

Providers and Information Users for Providers and Information Users for Flight OperationsFlight Operations””

Flight Operations Working GroupFlight Operations Working GroupMission StatementMission Statement


Flight Operations Working GroupFlight Operations Working GroupDigitalDigital DATADATA Transfer Transfer

•• Not concerned with text in manualsNot concerned with text in manuals but with but with DATADATA identification and structureidentification and structure

•• Makes Makes manipulationmanipulation of digital of digital DATA DATA possible in the futurepossible in the future

•• Does Does not enforcenot enforce information layout in information layout in documentsdocuments


FOWG Achievements to FOWG Achievements to DateDate•• Adoption of the ATA Systems Specification at Adoption of the ATA Systems Specification at

Two Digit Level OnlyTwo Digit Level Only•• Part of Part of iSpeciSpec 2200 for Flight Operations2200 for Flight Operations

•• Adoption of XML as basis for Interchange Adoption of XML as basis for Interchange SpecificationSpecification

•• Creation of the Phase of Flight SpecificationCreation of the Phase of Flight Specification•• Part of Part of iSpeciSpec 2200 for Flight Operations2200 for Flight Operations


FOWG Achievements to FOWG Achievements to DateDate•• Data ModelData Model

•• Data decomposition and validation of the data model Data decomposition and validation of the data model has been done with current manufacturer manuals has been done with current manufacturer manuals

•• First Drafts of Interchange Specification well First Drafts of Interchange Specification well under wayunder way

•• MMEL Portion of Interchange Spec being separated MMEL Portion of Interchange Spec being separated and completed at the request of Operators and FAAand completed at the request of Operators and FAA


ATA Systems SpecificationATA Systems Specification@@Two DigitTwo Digit Level Only*Level Only*

2020 GeneralGeneral2121 Air Conditioning & PressurizationAir Conditioning & Pressurization2222 AutoflightAutoflight2323 CommunicationsCommunications2424 ElectricalElectrical2525 EquipmentEquipment26 26 Fire ProtectionFire Protection27 27 Flight ControlsFlight Controls2828 FuelFuel29 29 HydraulicsHydraulics3030 Ice and Rain ProtectionIce and Rain Protection3131 Indicating & RecordingIndicating & Recording

3232 Landing GearLanding Gear3333 LightsLights3434 NavigationNavigation3535 OxygenOxygen36 36 PneumaticsPneumatics3838 Water & WasteWater & Waste45 45 On Board MaintenanceOn Board Maintenance4949 Auxiliary PowerAuxiliary Power52 52 DoorsDoors56 56 WindowsWindows7171 Power PlantPower Plant

* * iiSpecSpec 2200 for flight 2200 for flight operations useoperations use


ATA Phase of Flight ATA Phase of Flight SpecificationSpecification

FlightClose

Pre-flightPost Flight

Eng Start /Depart

Arrival /

Eng Shut

Taxi-out Taxi-in

Take-off RejectedTake-off

Go-around Landing

InitialClimb

Approach

En RouteClimb

Descent

Cruise

FlightPlanning

Ground Service

3 letter ID; not sequentially 3 letter ID; not sequentially numbered numbered : can be used and : can be used and interspersed with future interspersed with future orbital craft POF orbital craft POF requirementsrequirements

••Introduced 1999Introduced 1999••Recommended for Use 2001*Recommended for Use 2001*••Approved for Use 2002*Approved for Use 2002*

* * iiSpecSpec 22002200


Action

Procedure

Aircraft System

Limitation

Phase of Flight

Performance

Annunciation Malfunction

Environment Planning Information

MMELDispatch

MaintenanceTask

AerodynamicState

ATA FOWG Data ModelATA FOWG Data Model(Simplified) (Simplified)


Future of Data…Future of Data…LinksLinks Basic EntitiesBasic Entities

ATA Systems ATA Systems 2020 GeneralGeneral2121 Air Conditioning & PressurizationAir Conditioning & Pressurization2222 AutoflightAutoflight2323 CommunicationsCommunications2424 ElectricalElectrical2525 EquipmentEquipment26 26 Fire ProtectionFire Protection27 27 Flight ControlsFlight Controls2828 FuelFuel29 29 HydraulicsHydraulics3030 Ice and Rain ProtectionIce and Rain Protection3131 Indicating & RecordingIndicating & Recording3232 Landing GearLanding Gear3333 LightsLights3434 NavigationNavigation…Etc.…Etc.

ATA Phases of Flight ATA Phases of Flight FLPFLP Flight PlanningFlight PlanningPFLPFL PrePre--flightflightESD ESD Engine Start / DepartEngine Start / DepartTXOTXO TaxiTaxi--outoutTOFTOF TakeTake--offoffRTORTO Rejected TakeRejected Take--offoffICLICL Initial ClimbInitial ClimbECLECL En Route ClimbEn Route ClimbCRZCRZ CruiseCruiseDES DES DescentDescentAPRAPR ApproachApproachGOA GOA GoGo--aroundaroundLND LND LandingLandingTXITXI TaxiTaxi--ininAESAES Arrival / Engine ShutdownArrival / Engine Shutdown…Etc.…Etc.

LinkLink


Sharing Sharing Electronic DataElectronic DataThroughout Flight OpsThroughout Flight Ops

AQPAQP LOSALOSA FOQAFOQA

TOF TOF TOF

CRMCRM

TOFTOFAOMAOM

FCTMFCTM

L/G 32 L/G 32 L/G 32 L/G 32 L/G 32

AOMAOM

MELMELFCTMFCTM

Access Access DataDatathis this way way

electronicallyelectronically

ATA Phase of FlightATA Phase of Flight

ATA SystemsATA Systems

ProceduresSystem

s

Concept of shared information is changingConcept of shared information is changing


Data Tagging Data Tagging Across Across Document SystemsDocument Systems

Abn

orm

als

Lim

its

Abn

orm

als

Supp

Tec

hs

Des

crip

tion

FOQALOSACRMAQP

ME

L

Policy

SOPs

Performance

Norm

als

FCTM

MEL

AOMFOM

AOM FCTM

ATA Systems ATA Phase of FlightSupportSupportA

cces

s Sy

stem

Dat

a Access PO

F Data

02/02/12 rwt

4


Data Tagging Data Tagging Across Support Across Support DisciplinesDisciplines

AQ

P

Hua

mn

Fact

ors

LOSA

FOQ

A

AOMFCTMMELQRH

FOM PolicyCB

T

CR

M

LO

SA

FOQ

A

AQ

P

Training Safety Safety Training

ATA Systems ATA Phase of FlightOPSA

cces

s Sy

stem

Dat

a Access PO

F Data

02/02/12 rwt


FOWG MIT SubgroupFOWG MIT Subgroup

•• Manufacturers Information Team (MIT) subgroup Manufacturers Information Team (MIT) subgroup was created at Charlotte meeting, March, 2002 was created at Charlotte meeting, March, 2002 •• Manufacturer’s initiative to create a small working Manufacturer’s initiative to create a small working

group to kickgroup to kick--start the development of the Specstart the development of the Spec•• Group consisted of Airbus, Boeing, Bombardier, and Fairchild Group consisted of Airbus, Boeing, Bombardier, and Fairchild

DornierDornier

•• MIT meetings in conjunction with FOWG MIT meetings in conjunction with FOWG meetings plus additional meetingsmeetings plus additional meetings


FOWG MIT workFOWG MIT work•• Proposed and developed a solution based on :Proposed and developed a solution based on :

•• Master DocumentMaster Document•• FOWG Data ModelFOWG Data Model•• XML SchemasXML Schemas•• Content/DataContent/Data--centric approachcentric approach

•• MIT work submitted to FOWG for MIT work submitted to FOWG for Review, Testing Review, Testing and Approvaland Approval

•• MIT suggested approach consisted of:MIT suggested approach consisted of:•• Information Unit (IU) / Product Structure (PS) conceptInformation Unit (IU) / Product Structure (PS) concept

Concept was approved and adopted by the FOWG as Concept was approved and adopted by the FOWG as way forwardway forward


Information Unit / Product Information Unit / Product Structure ConceptStructure Concept

Information Unit (IU):Information Unit (IU):•• IU’sIU’s are entities with content (minimum are entities with content (minimum reviseablereviseable

unit):unit):•• LimitationsLimitations•• Performance dataPerformance data•• ProceduresProcedures•• Descriptions (Air transport system)Descriptions (Air transport system)•• Airworthiness Airworthiness DispatchabilityDispatchability



•• Metadata Unit (MU):Metadata Unit (MU):•• All metadata is contained within an IU as a separate MUAll metadata is contained within an IU as a separate MU

•• Found at the beginning of the IU with links between MU and IU Found at the beginning of the IU with links between MU and IU contentcontent

•• Examples:Examples:•• ATA systemsATA systems•• POFPOF•• EffectivityEffectivity•• RevisionsRevisions•• Cat II, Cat III, RVSM (not defined as part of 2.0)Cat II, Cat III, RVSM (not defined as part of 2.0)•• Etc.Etc.



•• Product Structure:Product Structure:•• PS defines the structure, sequence and references PS defines the structure, sequence and references

that make up a delivery product. that make up a delivery product. •• PS permits airlines to reorganize the structure of PS permits airlines to reorganize the structure of

the product without impacting the content (e.g. the product without impacting the content (e.g. JAR Ops)JAR Ops)



•• The Vision:The Vision:•• Content / Content / ProductProduct Structure are Structure are separatedseparated

•• Content Content isis managedmanaged throughthrough thethe Information Unit (IU) e.g. Information Unit (IU) e.g. procedureprocedure, , description, limitation. description, limitation. ReferRefer to Data Modelto Data Model

•• MetadataMetadata ((e.g.effectivitye.g.effectivity, , revisionrevision information, information, highlighthighlight, POF, ATA , POF, ATA etc.) etc.) isis part of part of thethe IU but IU but separateseparate fromfrom thethe content.content.

•• IUsIUs are are managedmanaged throughthrough thethe ProductProduct Structure (PS) Structure (PS) thatthat mapsmaps theirtheirorganizationorganization andand relationshipsrelationships

•• e.g. FCOM, MMEL, AFM, e.g. FCOM, MMEL, AFM, etcetc….….

•• TheThe PS PS isis alwaysalways delivereddelivered completecomplete, , whilewhile thethe IUsIUs andand associatedassociated Mus are Mus are delivereddelivered as an as an incrementalincremental update update

OnlyOnly New or New or RevisedRevised IUsIUs or MUs are or MUs are delivereddelivered


Delivery MechanismDelivery Mechanismps.xml contains the product structure

Volume

Chapter

00: Section

IU-level

IU

IU-id1: DS2-001-00001

MU-id1

IU

IU-id2 MU-id2

<?xml version="1.0" encoding="UTF-8"?><!ENTITY DS1-001-00001 SYSTEM “../IU/xxxIU-001-000001.xml" ><!ENTITY DS2-001-00001 SYSTEM "../IU/xxxIU-002-000001.xml" ><!ENTITY DS3-001-00001 SYSTEM "../IU/xxxIU-003-000001.xml"'><!ENTITY ABN1-03-028-0001 SYSTEM “../IU/xxxIU- 004-000001.xml"'>…

IU are found using the .ENT file containing entities that points to the physical files

The .ENT file is included in the PS instance.

IU.ent

ps.xml

IU

GFX

XXXIU-001-000001.xml

XXXIU-002-000001.xml

Graphic1.tif

Graphic2.tif

GFX.ent

DTDs/Schemas


Target for completionTarget for completion

MMEL Data Transfer Spec by Second Quarter 2005MMEL Data Transfer Spec by Second Quarter 2005Flight Operations Data Transfer Spec by Fourth Flight Operations Data Transfer Spec by Fourth

Quarter 2005Quarter 2005


MMEL Spec DevelopmentMMEL Spec Development

FOWG was tasked by ATA to develop a MEL Spec FOWG was tasked by ATA to develop a MEL Spec to replace the existing SGML DTDto replace the existing SGML DTD•• MEL schemas required by Operators and requested by MEL schemas required by Operators and requested by

FAA ShortFAA Short--termterm•• Development started during FOWG meeting in Development started during FOWG meeting in

Washington DC in Sept, 03Washington DC in Sept, 03•• Extraction of necessary MEL elements from Interchange Extraction of necessary MEL elements from Interchange

Schema to create separate MEL schema as temporary solutionSchema to create separate MEL schema as temporary solution•• This will permit the MEL schema to be reThis will permit the MEL schema to be re--integrated into the integrated into the

main schema at a later datemain schema at a later date


Work to be DoneWork to be Done

EstablishEstablish•• Transfer ProtocolTransfer Protocol•• A Means for Verification & Data History A Means for Verification & Data History •• Quality Assurance ProtocolQuality Assurance Protocol•• Means of Signature (Identify Certificates of Means of Signature (Identify Certificates of

Authority)Authority)


Industry BenefitsIndustry Benefits

•• ReRe--use datause data•• Share dataShare data•• Single source dataSingle source data•• To improve…To improve…

•• Revision Workflow timelinesRevision Workflow timelines•• Reliability of data Reliability of data •• Efficiency (no more cut and paste)Efficiency (no more cut and paste)•• Audit and approval TrailAudit and approval Trail