Air Transport Association
Flight Operations Working Group
Flight Operations
Data
Luc Bourgon, Bombardier
The Problem with Operating
Documents
• Flight Operations information has very few standard
taxonomies.
• There are no industry wide standards for Flight
Operations documentation:
• Common Data for Flight Manuals was desired 40 years ago
at the same time ATA Spec 100 was being developed
• Airlines and Manufacturers could not agree on common data
structure
• Common Flight Manuals structure is still seen as
impossible to agree on
October 28, 2004
ATA E-Business
2
Flight Operations Information
Operating Manuals Review
• ICAO ( 187 Member states) requires standard information
• Regulators (JAA, FAA, T/C) require (and audit for) standard
information across fleet types
• Manufacturers (4 major) deliver information in diverse
structures and formats
• Operators re-format and deliver internal documentation
in some internal, standard format
October 28, 2004
ATA E-Business
3
Manuals Delivered to
Operators by Manufacturers
•Airplane Flight Manual (AFM)
•Approved information in manufacturer’s jurisdiction
•Flight Crew Operating Manual (FCOM)
•Quick Reference Handbook (QRH)
•Flight Crew Training Manual (FTCM)
•Master Minimum Equipment List (MMEL)
•(Only common link between Flight Ops and Maintenance)
•Configuration Deviation list (CDL)
October 28, 2004
ATA E-Business
4
No Standards for Manuals
between Manufacturers
AIRBUS
Systems
Arranged by:
ATA Spec
BOEING
Limitations
Normal Procedures
Supp Procedures
BOMBARDIER
Systems
Arranged by:
Alphabetic
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
Emergency
Abnormals
ALL Non-normals
ALL Performance
Emergency
Abnormals
Normals Section
Abnormals: Emergency
Cautions
SGML w/FrameMaker
CD-ROM (html)
Paper
Some SGML
FrameMaker
PDF
Paper
Quicksilver /
(Interleaf)
Paper
Word, PDF
Paper
VOLUME
1
VOLUME
2
VOLUME
3&4
QRH
FORMAT
EMBRAER
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
Limitations
Abnormals
Std Oper Proc
Supp Technics
In Flight Performance
Engine Out Ops
FMGS Volume
October
PAGE
28, 2004 5.83 x 8.27 (A5)
5.5ATA
x 8.5E-Business
5.5 x 8.5
5.5 x 8.5
5
ICAO Regulations
Dictate to all member states (187) basic requirements for
flight operations information in ANNEX 6
Member states must comply to fly internationally or file
a difference of non-compliance
a)
b)
c)
e)
f)
g)
h)
policy and administration manual;
aircraft operating manual;
minimum equipment list (MEL) and configuration deviation list
(CDL);
training manual;
aircraft performance manual;
route guide;
Etc.
October 28, 2004
ATA E-Business
6
Manuals Required by State
Regulators for Operators
Aircraft Operating Manual (AOM) (FAA...CFM)
Flight Crew Training Manual (FCTM)
Flight Operations Manual (FOM) (FAA…COM, FOPM)
Master Minimum Equipment List (MMEL)
These manuals must be be
Approved/Accepted by regulators
October 28, 2004
ATA E-Business
7
Most Large Commercial Operators
Use Internal Standards
• Standard structure of manuals increases user
acceptance of information
• Standard location of information between
fleets for users transitioning between
aircraft types
• Mental Model of information is enhanced in
company procedures and policies
October 28, 2004
ATA E-Business
8
Support for Standard:
NASA / FAA Document Project
“Across fleet standardization should be
established at several levels, from operational
philosophy through procedures, to the use of
common formats and terms in the different
fleets. Operators should establish formal
working groups and processes to ensure
standard procedures across fleets. ”
October 28, 2004
ATA E-Business
9
Support for Standard:
NASA Report
“We recommend a three-way approach for a
cross-fleet standardization. (1) development
of a cross-fleet philosophy, (2) creating a
cross-fleet standardization forum, and (3)
obtaining input for procedural design from
personnel that design, certify, teach, use and
check procedures. ”
October 28, 2004
ATA E-Business
10
Support for Standard:
ICAO
An operator’s documents system should
ensure standardization across flight
document types, including formatting,
writing standards, standard writing style,
terminology, use of graphics and symbols and
formatting across documents. This includes a
consistent location of specific types of
information, consistent use of units of
measurement and consistent use of codes.
October 28, 2004
ATA E-Business
11
Support for Standard:
FAA
“Principle Operations Inspectors (POI’s)
should ensure that operators standardize
their operating procedures both within and
across aircraft types to the greatest extent
possible”
“...Standardized procedures promote understanding and effective communications
between crewmembers…Crewmembers of most large operators operate numerous
different aircraft during their career. Standardized procedures enhance a
crewmember’s transfer of learning...complete standardization of procedures is not
possible when there are significant differences between manufacturers
manufacturers and installed
equipment. A high degree of standardization, however, is possible…”
possible…”
October 28, 2004
ATA E-Business
12
Support for Standard:
JAA
“Since it is believed that a high degree of
standardization of Operations Manuals
within the JAA will lead to improved overall
flight safety, it is strongly recommended that
the structure described in this IEM (interpretive
explanation material) should be used by operators as
far as possible.”
October 28, 2004
ATA E-Business
13
Who do you turn to for
standards in the industry?
Regulators...
• Regional - JAA tries to do this but is not popular
amongst member (and non-member) states
• Added expense to comply when manufacturers do
not comply
• Individual states force additional expense to
airlines under jurisdiction
October 28, 2004
ATA E-Business
14
Who do you turn to for
standards in the industry?
Operators or Manufacturers...
•
•
•
•
•
Provide information based upon legacy formats
Interested in selling proprietary system and updates
In competition with each other
Each has individual formats and structures of information
Each operator has specific needs, i.e., areas of operations,
large and small operations, etc.
October 28, 2004
ATA E-Business
15
Who do you turn to for
standards in the industry?
Support Groups…
• Each have differing ideas of applications for
flight operations documentation
Third Party Vendors…
• Corporate proprietary standards
• Industry would be at the mercy of corporate
entity
October 28, 2004
ATA E-Business
16
Who do you turn to for
standards in the industry?
Industry Organizations
•
•
•
ICAO…regulator at the highest level
IATA…standards development with ICAO
ATA…industry organization known for
specifications development
October 28, 2004
ATA E-Business
17
The Solution
• Flight Operations Working Group was
formed within the ATA to develop a
common data interchange model for Flight
Operations Data
October 28, 2004
ATA E-Business
18
Flight Operation Working
Group
FOWG created in 1997
• Prior attempts failed because they focused on
setting paper/word processing standard
Meet 3-4 times/year
•
•
•
Up to 15 Air Carrier / Operators
All 4 major Manufacturers
Up to 12 vendors/consultants/suppliers
International Representation
October 28, 2004
ATA E-Business
19
Flight Operations Working Group
Mission Statement
“To develop a specification for the cost
effective and efficient interchange of
digital data between Information
Providers and Information Users for
Flight Operations”
October 28, 2004
ATA E-Business
20
Flight Operations Working Group
Digital DATA Transfer
• Not concerned with text in manuals but with
DATA identification and structure
• Makes manipulation of digital DATA
possible in the future
• Does not enforce information layout in
documents
October 28, 2004
ATA E-Business
21
FOWG Achievements to
Date
• Adoption of the ATA Systems Specification at
Two Digit Level Only
• Part of iSpec 2200 for Flight Operations
• Adoption of XML as basis for Interchange
Specification
• Creation of the Phase of Flight Specification
• Part of iSpec 2200 for Flight Operations
October 28, 2004
ATA E-Business
22
FOWG Achievements to
Date
• Data Model
• Data decomposition and validation of the data model
has been done with current manufacturer manuals
• First Drafts of Interchange Specification well
under way
• MMEL Portion of Interchange Spec being separated
and completed at the request of Operators and FAA
October 28, 2004
ATA E-Business
23
ATA Systems Specification
@Two Digit Level Only*
20 General
21 Air Conditioning & Pressurization
22 Autoflight
23 Communications
24 Electrical
25 Equipment
26 Fire Protection
27 Flight Controls
28 Fuel
29 Hydraulics
30 Ice and Rain Protection
31 Indicating & Recording
October 28, 2004
* iSpec 2200 for flight
operations use
32 Landing Gear
33 Lights
34 Navigation
35 Oxygen
36 Pneumatics
38 Water & Waste
45 On Board Maintenance
49 Auxiliary Power
52 Doors
56 Windows
71 Power Plant
ATA E-Business
24
ATA Phase of Flight
Specification
Cruise
Descent
En Route
Climb
Initial
Climb
Take-off
•Introduced 1999
•Recommended for Use 2001*
•Approved for Use 2002*
* iSpec 2200
Approach
Rejected
Take-off
Go-around
Taxi-out
Taxi-in
Arrival /
Eng Start /
Depart
Eng Shut
Post Flight
Pre-flight
3 letter ID; not sequentially
numbered : can be used and
interspersed with future
orbital craft POF
requirements
October 28, 2004
Landing
Flight
Close
Flight
Planning
Ground
Service
ATA E-Business
25
ATA FOWG Data Model
(Simplified)
Aircraft
System
Action
Annunciation
Malfunction
Phase of
Flight
Aerodynamic
State
MMEL
Dispatch
Procedure
Environment
Limitation
October 28, 2004
Performance
ATA E-Business
Maintenance
Task
Planning
Information
26
Future of Data…
Links Basic Entities
ATA Systems
20 General
21 Air Conditioning & Pressurization
22 Autoflight
23 Communications
24 Electrical
25 Equipment
Link
26 Fire Protection
27 Flight Controls
28 Fuel
29 Hydraulics
30 Ice and Rain Protection
31 Indicating & Recording
32 Landing Gear
33 Lights
34 Navigation
…Etc.
October 28, 2004
ATA Phases of Flight
FLP Flight Planning
PFL PrePre-flight
ESD Engine Start / Depart
TXO TaxiTaxi-out
TOF TakeTake-off
RTO Rejected TakeTake-off
ICL Initial Climb
ECL En Route Climb
CRZ Cruise
DES Descent
APR Approach
GOA GoGo-around
LND Landing
TXI TaxiTaxi-in
AES Arrival / Engine Shutdown
…Etc.
ATA E-Business
27
Sharing Electronic Data
Throughout Flight Ops
AQP
TOF
TOF
ATA Phase
L/G 32
L/G 32
L/G 32
Access
TOF
TOF
Data
of Flight this
way
electronically
L/G 32
L/G 32
Systems
AOM
FCTM
MEL
TOF
CRM
Procedures
AOM
FCTM
LOSA FOQA
ATA Systems
Concept of shared information is changing
October 28, 2004
ATA E-Business
28
4
Data Tagging Across
Document Systems
ATA Systems
Limits
Abnormals
Description
Normals
MEL
FCTM
FOM
Policy
Access POF Data
Access System Data
AOM
SOPs
FOQA
LOSA
CRM
AQP
ATA Phase of Flight
Performance
MEL
Supp Techs
AOM
FCTM
Abnormals
Support
02/02/12 rwt
October 28, 2004
ATA E-Business
29
Data Tagging Across Support
Disciplines
ATA Systems
Huamn Factors
LOSA
FOQA
Training
AQP
Access POF Data
Access System Data
Safety
CRM
AOM
FCTM
MEL
QRH
FOM Policy
LOSA
CBT
Safety
ATA Phase of Flight
FOQA
AQP
Training
OPS
02/02/12 rwt
October 28, 2004
ATA E-Business
30
FOWG MIT Subgroup
• Manufacturers Information Team (MIT) subgroup
was created at Charlotte meeting, March, 2002
• Manufacturer’s initiative to create a small working
group to kick-start the development of the Spec
• Group consisted of Airbus, Boeing, Bombardier, and Fairchild
Dornier
• MIT meetings in conjunction with FOWG
meetings plus additional meetings
October 28, 2004
ATA E-Business
31
FOWG MIT work
• Proposed and developed a solution based on :
•
•
•
•
Master Document
FOWG Data Model
XML Schemas
Content/DataContent/Data-centric approach
• MIT work submitted to FOWG for Review, Testing
and Approval
• MIT suggested approach consisted of:
• Information Unit (IU) / Product Structure (PS) concept
Concept was approved and adopted by the FOWG as
way forward
October 28, 2004
ATA E-Business
32
Information Unit / Product
Structure Concept
Information Unit (IU):
• IU’s are entities with content (minimum reviseable
unit):
• Limitations
• Performance data
• Procedures
• Descriptions (Air transport system)
• Airworthiness Dispatchability
October 28, 2004
ATA E-Business
33
Information Unit / Product
Structure Concept
• Metadata Unit (MU):
• All metadata is contained within an IU as a separate MU
• Found at the beginning of the IU with links between MU and IU
content
• Examples:
• ATA systems
• POF
• Effectivity
• Revisions
• Cat II, Cat III, RVSM (not defined as part of 2.0)
• Etc.
October 28, 2004
ATA E-Business
34
Information Unit / Product
Structure Concept
• Product Structure:
• PS defines the structure, sequence and references
that make up a delivery product.
• PS permits airlines to reorganize the structure of
the product without impacting the content (e.g.
JAR Ops)
October 28, 2004
ATA E-Business
35
Information Unit / Product
Structure Concept
• The Vision:
• Content / Product Structure are separated
• Content is managed through the Information Unit (IU) e.g. procedure,
procedure,
description, limitation. Refer to Data Model
• Metadata (e.g.effectivity,
e.g.effectivity, revision information, highlight,
highlight, POF, ATA
etc.) is part of the IU but separate from the content.
• IUs are managed through the Product Structure (PS) that maps their
organization and relationships
• e.g. FCOM, MMEL, AFM, etc….
etc….
• The PS is always delivered complete,
complete, while the IUs and associated Mus are
delivered as an incremental update
Only New or Revised IUs or MUs are delivered
October 28, 2004
ATA E-Business
36
Delivery Mechanism
ps.xml contains the product structure
Volume
ps.xml
Chapter
DTDs/Schemas
00: Section
IU-level
IU
IU
IU.ent
IU-id1: DS2-001-00001
XXXIU-001-000001.xml
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- 004000001.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.
October 28, 2004
ATA E-Business
XXXIU-002-000001.xml
GFX
GFX.ent
Graphic1.tif
Graphic2.tif
37
Target for completion
MMEL Data Transfer Spec by Second Quarter 2005
Flight Operations Data Transfer Spec by Fourth
Quarter 2005
October 28, 2004
ATA E-Business
38
MMEL Spec Development
FOWG was tasked by ATA to develop a MEL Spec
to replace the existing SGML DTD
• MEL schemas required by Operators and requested by
FAA Short -term
• Development started during FOWG meeting in
Washington DC in Sept, 03
• Extraction of necessary MEL elements from Interchange
Schema to create separate MEL schema as temporary solution
• This will permit the MEL schema to be rere-integrated into the
main schema at a later date
October 28, 2004
ATA E-Business
39
Work to be Done
Establish
•
•
•
•
Transfer Protocol
A Means for Verification & Data History
Quality Assurance Protocol
Means of Signature (Identify Certificates of
Authority)
October 28, 2004
ATA E-Business
40
Industry Benefits
•
•
•
•
Re-use data
Share data
Single source data
To improve…
•
•
•
•
Revision Workflow timelines
Reliability of data
Efficiency (no more cut and paste)
Audit and approval Trail
October 28, 2004
ATA E-Business
41