RTCA SC 206EUROCAE 44

1
RTCA SC 206/EUROCAE 44533rd meeting (30 Jan-3
Feb 2006) AIS Group summary Brussels

• Presented by
• Ana Paula Frangolho

European Organisation for the Safety of Air
Navigation
2
Agenda 3rd meetingAIS Group

• 1 Approval of the minutes
• 2 Review of action items
• 3 Short summary of previous meeting
• 4 Objectives for the meeting
• 5 Presentations
• 6 Working/discussion sessions
• 7 Discussion on progress and achievements
• 8 Planning work ahead
• 9 Assignment of work and activities

3
Services

• 1 - Transmission NOTAM / temporary information
• a) Transmission of NOTAM / temporary information
  (current text format)
• b) Transmission of NOTAM / temporary information
  data in computer interpretable structured format
  that may be converted into suitable graphic form
• Considered to be mature. First priority in
  development
• Definitions
• 1-a) Provision to flight crew of relevant,
  up-to-date, and consistent temporary information
  in textual format
• 1-b) Provision to flight crew of relevant,
  up-to-date, and consistent temporary information
  in a structured format suitable for graphic
  display

4
Services

• 2 - Update of AIRAC cycle (static) information
• a) Transmission of static aeronautical data for
  update of onboard databases (EFB, FMS)
• b) Terrain, obstacle and airport mapping data
• How to deal with certification issues when
  dynamically updating
• Need to take into account operational
  considerations!
• Requires hi-bandwidth capability
• 3 - Real-time aeronautical information (static
  and dynamic e.g. navigation, terrain, obstacle
  and airport mapping)
• Probably not feasible in near/mid-term
• Need to confirm user requirements and the
  availability of enabling technology to support 2
  3

5
Scope
AIS Data Chain
End Users
AIR
Scope begins after the AIS publication
6
Scope/purpose

• Transmit all relevant aeronautical information to
  the data user in the cockpit in a useable way
• Focus on aeronautical information and data rather
  than applications
• Standardising with a view on the future, taking
  into account legacy systems and procedures
• Look at the structure, format, timeliness,
  accuracy, and safety relevance of aeronautical
  data.
• Specify what service needs to be provided and
  related requirements, not who provides it

7

• Outside scope
• defining the symbology /graphical representation
  of the aeronautical information
• Liability issues
• The pipe- data link technology - used to
  transmit the information

8
Issues

• Need to filter the information presented to the
  users
• Update/change of FMS data and associated
  certification requirements
• Broadcast versus service request and push versus
  pull
• Aeronautical Information What definition and
  scope
• Identification of different types of NOTAM like
  (temporality characteristics and immediate
  operational relevance) aeronautical messages
  (GPS, CRAM, etc)
• Operational concept and definition of users
  requirements
• Time criticality and associated constraints
• Define the time frame of applicability

9
Objectives for the meeting

• Achievements
• Draft document was developed in accordance with
  RTCA/EUROCAE methodology ED 78 A/DO 264 -
  Thanks to all contributors
• Objectives
• Comment and discuss the draft document
• Services
• Are feasible realistic in a 10 year time frame?
• Are in accordance with and resulting from users
  needs/expectations?
• Are aligned with and following the
  evolution/trend of onboard avionics
  developments/manufacturers?
• Other services (PIB FIB)
• Integration of existing developments/deliverables
  and trials (D-OTIS, EGOA, FIS B Product
  definition Mitre).. How and when?
• Define/agree structure/chapters of the document
  and information requirements
• (Initial) Identification of Abnormal Events not
  yet addressed
• (Initial Data Link) Quality Of Service
  requirements- not yet addressed
• Address identified issues