1 / 9

Standardization of the Cabin Human Machine Interface

Presented by Rolf Goedecke, Airbus. Standardization of the Cabin Human Machine Interface. Goals. Standardization of the Cabin Human Machine Interface in order to increase the user acceptance increase the acceptance of the authorities reduce the training effort for airlines

joyce
Télécharger la présentation

Standardization of the Cabin Human Machine Interface

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Presented by Rolf Goedecke, Airbus Standardization of the Cabin Human Machine Interface 23/01/08 WAEA TC Meeting Burbank

  2. Goals • Standardization of the Cabin Human Machine Interface in order to • increase the user acceptance • increase the acceptance of the authorities • reduce the training effort for airlines • reduce the testing effort for the aircraft manufacturer • reduce the development effort • by • design of consistent screen layouts • definition of consistent work flows • definition of a consistent wording • design of a consistent Look & Feel across different systems ! Focus in a first step on touch screen devices

  3. HMI Examples Airbus Cabin Management System Airbus Digital Cabin Logbook Thales IFE System Panasonic IFE System

  4. Layout • Amongst other • Graphical elements shall be aligned to a grid whichshall be maintained throughout the HMI of the application/device • The screen shall be divided into areas provided for specific purposesE. g.: content area, navigation area, title area Example: title area optional navigation Navigation area

  5. Complexity • Amongst other • Navigation hierarchy (menu structure) shall be of minimal complexity • Number of different graphical elements shall be minimized • Same function shall have the same appearance E. g.: a Button shall always have the same size and appearance clearly discriminable from other graphical elements Example for graphical element diversity: Graphical Element Button Label List Scrollbar Toggle Button Push Button Image Tree view

  6. Design rules • Text and characters • Alignment of text (left/right/center) shall be used consistently all over the HMI • The number of different character sizes and styles shall be kept to a minimum • Upper/lower case shall be used consistently • Only one sans-serif font shall be used • Spacing • Spacing between and within graphical elements (E. g. the text or icon on a Button) shall be appropriately • Colors • The number of colors shall be kept to a minimum • Contrast and saturation shall be used appropriately • Specific colors (E. g. red/green) shall be used according to the policies of the aircraft manufacturer

  7. Wording • Wording shall be used consistently all over the HMI • Aircraft specific terms and abbreviations shall be used according to a standard catalog

  8. Definition of reusable assembled structures • The HMI is mostly composed of reusable assembled structures which shall have a constant layout and Look & Feel throughout the HMI of the application/device • Amongst others these structures are • Scrollable lists of text composed of Buttons, a List, and a Scrollbar (e. g.) • Virtual keyboards and other complex virtual input devices • Dialogs (e. g. the login dialog, message boxes with confirmation Buttons)

  9. AEEC HMI standardization proposal • Feedback is appreciated from users/operators • Send comments, opinions, questions, proposals ect. • to Rolf Goedecke, Airbus (rolf.goedecke@airbus.com) or • to Earl Nicks, AEEC (wen@arinc.com) or participate next CSS meeting

More Related