To Skip Navigation Press Enter.Link to the Color Usage Site Home Page
Use the category links below to navigate this web site. All site pages can also be accessed with the site map.
Design Process Color Graphics Topics Color Tool Color Guidelines Aerospace
Color Science Utilities Site Map
Link back to the CURL Home Page
 

DESIGN OF AIR TRAFFIC MANAGEMENT GRAPHICS (EXAMPLE)

On This Page:  • Prototype Color Design  • Phase 1: Data Planning  • Phase 2: Design of Graphics Implementation


This page presents a brief example of how the design process described on the color graphics design page might be applied to an Air Traffic Management (ATM) display.

Even at current data rates the display of information at ATM workstations must be very carefully designed. The consequences for public safety are high and cognitive workload at its peak is heavy. The controller has to maintain an elaborate mental model of the aircrafts' current and future positions and develop primary and backup plans for maintaining adequate separation of aircraft in the presence of a wide assortment of operational constraints. The displays must support those tasks.

Current upgrade programs are providing more detailed weather information at more locations. New display and communication hardware provide greatly increased display possibilities. New software is being developed to provide computational support for tactical and strategic planning and to reduce communication and display-manipulation demands.

Addition of area variables (terrain, weather) and new software tools require substantial changes from traditional ATM graphics to meet legibility, attention management, and color-coding demands. Redesigns of ATM displays are under way at research centers worldwide.


Prototype Color Design for an Integrated Display of Hazard Information Back to the top of the page.

At the outset we have to emphasize that this example represents just an initial draft of the display and associated user operations. In good design practice every decision regarding the data set to be displayed, the associated user procedures, and the data hierarchy should be initially reviewed by the design team (human factors experts, subject matter experts, and engineering experts) and then re-examined several times during the course of an iterative development process of design/test/redesign/retest.

Phase 1: Data Planning Back to the top of the page.

Starting Point. This enroute air traffic controller's display is based on a NASA research prototype display Link Opens a New Window. (external site). That prototype represents a substantial development effort over several years. It was developed to give the controller improved situation awareness and access to an array of new software tools, including NASA's CTAS planning tools, and advanced communication tools. This starting point for our design is already an enhancement of existing display of traffic data and includes the graphics of software tools that help the pilots plan conflict-free routes.

Part of a prototype NASA display with colored features on a black background.
Larger Image New Window. 
The color scheme of the NASA prototype display includes manipulation of luminance contrast for attention management, labeling of aircrafts' phase of flight, warning of conflict hazard, and grouping of elements pertaining to the currently selected aircraft. Symbols for aircraft arriving, departing, or overflying DFW airport are labeled by hue. Context graphics (e.g., static labels, navigation aids, borders, and framework graphics) are coded in lower luminance contrasts than more urgent data.

Our example design here extends the NASA prototype display to include other hazards. Except for color the existing air traffic and display controls, data, and graphic coding are kept without modification. The color design for the pre-existing elements is changed in the new overall color design.

Data Inventory / Data Analysis . The data to be displayed are the traffic and context data of the NASA prototype display, plus NEXRAD weather radar, and maximum altitudes and motion vectors of the weather. They are shown here first in isolation, then in colors appropriate for integrated display, then in an integrated display.

Some further data details are derived from consideration of operational constraints. For the weather data, we assume in this example that the intensity categories identified in current airborne radar displays are sufficient for pilots' trajectory decisions, so the 15 levels of NEXRAD are collapsed to four levels that correspond to those in current airborne radar systems. We also assumed for this example that the controller only needs to know the altitudes of the weather to determine whether it is possible to fly above the storm.

NEXRAD shows the current position of storm cells, but this is not usually the position of interest to the ATM users. Decisions about trajectories of aircraft are made well in advance, so the weather may have moved or developed appreciably in the time required to fly to it. It's obviously desirable to have accurate predictions of where the storm cells will be and how severe when encountered, with a well-designed graphical depiction of the current and future situations. This is much harder for ATM stations than for the cockpit, where there is only one flightpath to consider. For ATM the controller needs the predicted storm position for whichever of the aircraft are involved in the current planning activity. Since the aircraft and prediction times can vary from moment to moment, this will require some sophisticated graphics. The NASA prototype display includes a "scroll-forward" capability that allows the controller to preview the predicted positions of all the aircraft, based on the software's model predictions. When suitable short-term predictions of storm motion and development are available these predicted motions can be graphically represented in the preview tool. For the current example, the controllers are required to mentally estimate the future location from the current location and motion vector of the cell.

A display of several aircraft data points on a white background. Component data in isolation: Aircraft for which the controller has responsibility require focal attention.
Component data in isolation: NEXRAD weather data, coded in fifteen levels, in spatial grid of 1 km pixels. Convective weather cells create hazards for some flights. Lower intensity weather with potential to impact flights in the future should be displayed as context information. Part of a color weather hazard map. A variety of colors are used to indicate various levels of potential weather hazard on a black background.
A variety of small black arrow-like symbols in isolation on a white background. Component data in isolation: Context aircraft are aircraft that are the responsibility of another controller or (in some sectors) flying under Visual Flight Rules. They should pose no immediate hazard to the controller's aircraft but may be displayed to maintain situation awareness.
Component data in isolation: Fixed context information includes such elements as sector boundaries, navigation fixes and routes, range rings, distance scales, etc. A black and white aerospace display showing circular and linear boundaries and routes.
Attention Management. The data were sorted into categories and the categories ordered in a hierarchy of urgency. This urgency hierarchy provides the rationale for the graphic design of the display.
Sample ATC Data Hierarchy
1. Urgent aircraft (approaching hazard, declared emergency)
2. Hazard area variables (weather, terrain)
3. Selected aircraft
4. Focal aircraft ("own" aircraft)
5. Context aircraft (not hazard for "own" aircraft)
6. Potential area hazards (low severity weather)
7. Context lines, symbols (boundaries, airways, navaids)
8. Context area variables (own vs. other sectors)
  The most urgent categories include aircraft that require immediate attention for safety and hazard area variables that are in a "warning" state. The aircraft are considered more urgent because they always require immediate action. The area hazards continuously affect planning, but they require only intermittent action, when they immediately endanger aircraft. All deserve high salience.

The next several categories are data about aircraft. They are all dynamic and include the symbols for the aircrafts' current positions, trajectory graphics, and the current and assigned state variables (call sign, altitude, speed, and destination) in the data tag.

The most urgent non-emergency aircraft is the one currently selected. The user has selected it as the focus of immediate intentions, e.g., to examine its state variables in more detail or to make or plan some change in its clearance.

The next category is non-selected aircraft that are under the user's control. The sector controller must plan a safe trajectory across the sector for these aircraft. Their data directly affect the controller's primary and backup plans for the use of the sector airspace
.

The next two categories down are context aircraft and potentially hazardous area variables. The aircraft are passing over, under, or adjacent to the controller's sector and are being worked by the controller of another sector. The weather is currently below "caution" severity. Both categories are dynamic and need occasional monitoring to estimate the likelihood of their becoming a hazard to the controller's aircraft.

At the bottom in urgency are static context variables. The lines and symbols delineate boundaries of air traffic control sectors, fixed airways, and navigation fixes, along with the associated text labels. Fixed areas include such things as ATC sectors and restricted-access military airspace.

Phase 2: Design of the Graphics ImplementationBack to the top of the page.

The hierarchy of data urgency provides the guidance for the design of the graphics, including color assignments.

Design perceptual layers using achromatic color. The first issue was choice of contrast polarity. Traditional ATC displays were "radar-like", with bright symbols on dark backgrounds. In modern ATC settings the display equipment and working environment permit a "map-like" design, with dark symbols on light backgrounds. The second was chosen for this design.

The next step was to design achromatic graphics that gave the graphic elements salience that corresponds to the urgency hierarchy, using only non-color graphic variables. In this prototype design only luminance contrast was manipulated for attention control, but font size and stroke width could provide further distinctions.

An integrated aerospace display. The display includes
		low luminance contrast boundary data, higher contrast data points, and color-coded
		weather information on a white background.
Larger Image New Window.


In this color design, symbols and alphanumeric data for focal aircraft (the ones under the user's immediate control) were assigned high luminance contrast, to give them the highest salience during normal monitoring and planning. Aircraft owned by another controller were given noticeably lower luminance contrast. Context data--lines, symbols, labels, and non-hazard area variables--were coded at low luminance contrasts to give them the least salience without actually removing them. The sector regions were labeled with grayscale shading.

That leaves only the urgent data. Since the focal aircraft already had been given high luminance-contrast other graphic variables were needed to give the maximum salience to the urgent data. These aircraft and hazards were made to stand out by use of chromatic color. While not included in this prototype, various degrees of temporal modulation (blinking and flashing) and possibly auditory signals might also be used to further increase the salience of the most extreme, unusual hazards, should they prove necessary.

Decide where chromatic color will be used and why. Chromatic color is used sparingly in this prototype, for specific purposes. The most important use is caution-and-warning color codings for the symbols of aircraft in traffic conflicts and for weather. The saturated colors give these high-urgency data still higher salience through "popout" and provide specific, culturally conventional labels. More subtle chromatic color is also used to group classes of aircraft. Static grouping includes groups of aircraft in different phases of flight (arrivals, departures, and overflights). This helps the controllers plan by providing expectations about the aircrews' intentions. Temporary color coding to achieve visual grouping and popout includes color coding of all interface elements that relate to the currently selected flight. The datablock element currently under the cursor is also highlighted. This helps the controller quickly find and integrate all of the information pertaining to the flight under scrutiny. It also aids interaction by identifying targets for possible cursor movements.

Demo of an integrated display- In colors for integrated display: Aircraft for which the controller has responsibility require focal attention, so they are given high luminance-contrast. Arriving aircraft are color-coded green. Overflights are black.




In colors for integrated display: Aircraft for which the controller has responsibility require focal attention, so they are given high luminance-contrast. Arriving aircraft are color-coded green. Overflights are black.

 

In colors for integrated display: Weather hazards (magenta, red and yellow) are high in the urgency hierarchy. The low-severity weather (green) is lower in the hierarchy. Example of colors used to display levels of weather hazard. Displayed are yellow, red and green areas on a white background.
Several grey arrow-shaped data points on a white background. In colors for integrated display: Aircraft for which other controllers have responsibility and which pose no immediate hazards for owned aircraft are less urgent but should still be visible.
In colors for integrated display: Fixed features of the airspace provide background context, a frame of reference for the controller's decisions and actions. This is low urgency information and should not distract attention from higher priority layers. A grey and white, low luminance contrast display of circular sector boundaries and linear route paths.

 

Choose colors. The color choices were based on a number of considerations. Cultural constraints and standards were considered first in selecting hues and saturations for labeling the hazard data. Warning status and caution status required saturated red and saturated yellow or yellow-orange, respectively. ((Use of magenta for the fourth, most severe weather level is not a broad cultural convention but is incorporated because it corresponds to usage in many cockpit weather displays).

The luminance and purity values were chosen on the basis of perceptual layering demands. Very pale green was used for low intensity weather for several reasons. The areas covered by low intensity weather can be quite large, and aircraft often fly through it. Use of a low-saturation green for this level of weather allows high luminance-contrasts with aircraft and other symbols. It also avoids simultaneous- and successive-contrast problems that can occur with large areas of saturated color. Warning-level weather is usually confined to small areas so the relatively low luminance of high-saturation red is a minor problem. Caution-level weather also tends to be small, and maximum purity and high luminance can be gotten simultaneously in yellow. Adjacent sectors were shaded slightly darker than the controller's own sector. The controller's own sector was left white so that it had maximum background brightness and the maximum range of possible luminance-contrasts for data elements.

Discriminability and identifiability then became constraints on choices as the hazard labeling reduced the options for other coding colors. Arrivals and departures were labeled in green and blue, respectively, dark enough to preserve the high luminance-contrast required by their position in the urgency hierarchy, but not so dark as to make identification problems. Overflights remain black. Magenta was chosen as the grouping color for the selected aircraft's data elements (not shown in this sample). Highlighting for mouseover status is accomplished by bolding, which produces subjective darkening in this contrast polarity (not shown in this sample).

Solve problems. There are several aspects of this design that need testing and possible modification:

Current cultural usage and standards require that aircraft in warning status (due to traffic conflict or declared emergency) and hazardous weather both be coded in saturated red. In the presumably infrequent case of a red aircraft being in the middle of red weather the luminance-contrast between aircraft symbol and background will be low. The proposed solution is outlining the aircraft symbol in black.

The use of green to label the arrivals also deserves further scrutiny. Cultural usage is that green implies a "safe" condition, i.e., that it has been evaluated and determined to be safe. Arrival traffic often does get extra scrutiny (due to the natural convergence of arrivals as they near the airport), but there may be circumstances in which an aircraft is not currently in caution or warning status but doesn't yet have a conflict-free route in the controller's overall plan. If so, another color might need to be substituted for the dark green, and that choice might require some adjustment of the other colors used for aircraft symbols.

The distinction between the two most severe weather categories may not prove justified in practice--aircraft should avoid both whenever possible. In that case only three levels would be used, with red for both of the previous top levels.

As the interface undergoes successive stages of testing these and other problems may require redesign of part or all of the color scheme. These redesigns must be done with as much or more care than the initial design, and the required time and money should be identified at the beginning of the project.


Related Topics:
go to this page Designing a Color Graphics Page (Checklist)
go to this page Design of Cockpit Graphics (Example)



About This Site

Home
| Design Process | Color Graphics Topics | Color Tool | Guidelines | Aerospace | Color Science | Utilities

  Site Curator: Jeffrey McCandless | Responsible NASA Official: Jeffrey McCandless | Privacy Statement


NASA Logo     Ames Research Center Logo     Human Systems Integration Division Logo