<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Operationalization of Norms in Aircraft Approach/Departure Decision Support</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Laura SAVIČIENĖ</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Faculty of Mathematics and Informatics, Vilnius University</institution>
          ,
          <country country="LT">Lithuania</country>
        </aff>
      </contrib-group>
      <fpage>208</fpage>
      <lpage>214</lpage>
      <abstract>
        <p>This work is focused on norm operationalization in aviation domain. The investigated paradigm can be described as: from legal norms to technical rules in the artifact. Normative requirements (norms) for the aircraft trajectories are extracted from the flight rules and airport procedures, and operationalized in a decision support system (DSS). The decision support is based on evaluation of risk to violate the normative requirement. The following risks are modeled: trajectories' conformance with the flight rules, safe distance between aircraft, wake turbulence separation and avoidance of volcanic ash. The DSS is for the air traffic controller (not pilot) and must respond in real time. It provides surveillance, evaluates and recommends, whereas the human controller takes a decision.</p>
      </abstract>
      <kwd-group>
        <kwd />
        <kwd>Air traffic control</kwd>
        <kwd>instrument approach procedure</kwd>
        <kwd>SKY-Scanner</kwd>
        <kwd>realtime decision support</kwd>
        <kwd>norm operationalization</kwd>
        <kwd>risk model</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>This research is focused on the operationalization of normative rules in aviation
domain (air traffic control, ATC). A proposed paradigm can be called “from legal
norms to technical rules in the artifact”. Normative requirements are extracted from the
flight rules, maps and approach/departure procedure charts. An example of a normative
rule is “Keep 3 degrees descent angle while landing and hold restrictions of the altitude
and geography depicted in the aerodrome chart”.</p>
      <p>
        Normative rules are modeled in order to provide decision support in terms of norm
violation risk. A decision support system (DSS) provides surveillance, evaluates and
recommends, whereas the human controller takes a decision. The final decision is done
by human controller. This approach accords with SESAR (Single European Sky Air
Traffic Management Research) target concept, which states that humans should
constitute the core of the future air traffic management (ATM) operations [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>The decision support is based on lidar (laser radar – LIght Detection And Ranging)
and radar data fusion. It relies on the assumption that the precise aircraft position data
(with error margin of meters, not hundreds of meters) from the lidar will facilitate
detection of risks that are not possible to detect using only radar data.</p>
      <p>The research goal is to develop a conception for operationalization of the aircraft
approach/departure norms in a decision support system, taking into consideration the
use of lidar for aircraft tracking. The goal is broken down into these tasks: (1) modeling
norm violation risk in the airport traffic zone (ATZ), (2) modeling radar and lidar data
fusion, and (3) development of a prototype decision support system.</p>
    </sec>
    <sec id="sec-2">
      <title>1. Domain Analysis and Related Works</title>
      <p>The norm operationalization is investigated in the context of the ATM paradigm
developed in the EU FP6 SKY-Scanner project1: expanding surveillance and the ATC
control to the approach/departure phases by using radar and lidar data fusion and
decision support in terms of norm violation risk. Only norms that can be checked using
the lidar-radar fused data (position and speed) are examined and included in the
operationalization conception.</p>
      <p>
        The project was aimed at developing a laser system to detect and track aircraft up
to at least 6 nautical miles (NM) from the aerodrome traffic zone (ATZ) barycenter [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
The project objectives include aircraft collision probability model (ACPM) based on
radar data and laser tracking data fusion and a prototype decision support system
(Figure 1) for aircraft approach and departure [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The current research builds on the
constraint models developed by the SKY-Scanner project, and aims to abstract them
into a unified norm operationalization conception, also further refining the DSS
prototype and visualization models.
      </p>
      <p>Several important assumptions stem from the SKY-Scanner project and thus form
the boundaries of the current research:</p>
      <p>
        1) ATC activities require a real-time response from the DSS. A study of
timecritical decision support models provided in [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] concludes that the naturalistic decision
support approach should be used and highlights the need to filter out the most
important information for the user.
      </p>
      <p>
        2) The emphasis is on informing the controller, who then makes a final decision on
the actions. This accords with the results of studies of human-automation interaction:
high levels of automation are not advisable in systems dealing with dynamic
environments with many external and changing constraints [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        Normative rules for aircraft approach/departure from International Civil Aviation
Organization (ICAO) flight rule documents [
        <xref ref-type="bibr" rid="ref6 ref7 ref8 ref9">6, 7, 8, 9</xref>
        ] are grouped into four categories:
ATC separation rules, airport procedures, wake turbulence separation rules, and
volcanic ash rules. Each airport has a different set of approach/departure procedures.
Approach/departure procedure constitutes a complex object and contains a number of
interrelated norms that define the ought-to-be trajectory with additional constraints.
      </p>
      <p>
        Current aviation-related decision support systems do not model norms
comprehensively, but there is some research in that direction. One type of decision
support – Conflict Detection and Resolution (CD&amp;R) systems. The structure of the
1 “Development of an Innovative LIDAR Technology for New Generation ATM
Paradigms” (SKY-Scanner), 2007-2010, http://www.sky-scanner.it/
CD&amp;R process [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] is designed for the aircraft separation conflicts, but can be
expanded to cover other normative rules. Conformance alerting philosophy is suitable
for the approach/departure norm supervising scenario: alert is issued when the aircraft
is close to violating the norm.
      </p>
      <p>
        2D visualizations in the ATM domain are no longer sufficient, and the modern 3D
visualizations have drawbacks [
        <xref ref-type="bibr" rid="ref11 ref3">3, 11</xref>
        ]. By augmenting the 3D screens with auxiliary
2D elements it is possible to visualize the ought-to-be trajectory requirements: a
relationship between horizontal position, distance and altitude.
      </p>
    </sec>
    <sec id="sec-3">
      <title>2. Norm Conceptualization and Risk Modeling</title>
      <p>The approach/departure decision support focuses on detecting violations of the flight
rules for the aircraft. We conceptualize each norm as a triplet of a norm factor, norm
pattern, and the expected value. Norm factor represents a quantitative trajectory
attribute of one or several aircraft. Only factors that can be computed from the DSS
input data are considered in this conception. Expected value, vN, is the value defined in
the text of the normative requirement. Norm pattern (‘≤vN’, ‘≥vN’, or ‘=vN’) explicates
how to interpret the expected value. For example, norm pattern ‘≥vN’ means the actual
value of the factor should be greater than the expected value.</p>
      <p>
        Patterns ‘≤vN’ and ‘≥vN’ constitute limit-based norms, and pattern ‘=vN’ –
deviation-based norms. Example of the limit-based norm (Figure 2): “height minimum
is 3900 ft. at 6 nautical miles from distance measurement equipment (DME)”. An
example of the deviation-based norm could be the track (the direction that the aircraft
should follow), which is expressed in degrees from North, e.g. 236° [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>The defined operationalization structure translates each norm into a risk definition
in the DSS. The use of discrete risk levels abstracts from unnecessary details. In the
DSS risk levels are defined based on the likelihood of violating the norm. A separate
risk definition is formulated for each normative requirement. An individual risk
evaluation maps the observed factor value to a discrete scale of risk levels.</p>
      <p>The L-level risk concept is characterized by five elements (Figure 3): (1) risk
factor (e.g. ‘altitude’ or ‘indicated airspeed’); (2) risk type (‘limit’ or ‘deviation’); (3)
the norm pattern (‘≥vN’, ‘≤vN’, ‘=vN’); (4) expected value of the factor; (5) a set of
thresholds for risk levels. If the risk type is ‘limit’, a set of thresholds consists of L-1
constants, defined in the terms of factor measurement units. If risk type is ‘deviation’, a
set of thresholds consists of L-1 pairs of constants, defining allowable deviation levels.</p>
      <p>
        For convenience of visual representation of the risk definition, a piece-wise linear
risk-magnitude function is used, which maps the observed factor value to a number
from the interval [
        <xref ref-type="bibr" rid="ref1">0, 1</xref>
        ]. Zero means the lowest risk, 1 means the highest risk level, and
values in the interval (0, 1) mean intermediate risk levels.
      </p>
      <p>As an example we consider the norm “altitude 3900 ft at 6 DME” (Figure 2). In
deviation-based risk evaluation we consider not the expected value itself, but the
expected deviation (dN = 0). There are 4 risk levels and 3 pairs of thresholds. The
corresponding risk definition is: (1) factor: 'altitude'; (2) type: 'deviation'; (3) pattern:
‘=vN’; (4) expected value: 3900 ft at 6 DME (deviation 0); (5) thresholds: dn0 = -0.5, dp0
= 2, dn1 = -1, dp1 = 3.5, dn2 = -1.5, dp2 = 5; (see Figure 4) The threshold values in this
example are chosen only for demonstration purposes.</p>
      <p>Each risk is represented in a separate indicator on the DSS control panel (Figure 5).
The risk level is shown with color and the number of colored slots on the indicator.</p>
    </sec>
    <sec id="sec-4">
      <title>3. DSS Prototype</title>
      <p>The DSS prototype embodies the norm operationalization conception proposed in the
previous chapter. It illustrates the modeling of several norms for the approaching
aircraft, and provides a real-time simulation of the suggested decision support scenario.</p>
      <p>
        Advanced ATC visualization ideas are adapted to context of approach/departure
decision support. The DSS prototype provides a laboratory implementation, which
advances technology readiness level (TRL [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]) 1-2 ideas to level 3. The aim was to
visualize airport procedure requirements (the ought-to-be trajectory), so that the
controller could visually estimate possible violation without looking at the control
panel. Two visualizations are developed: 2D-in-3D prototype and pure-3D prototype.
Both visualizations embed auxiliary 2D elements into the main 3D view of the
observed airspace.
      </p>
      <p>2D-in-3D prototype uses generalized terrain model and embeds 2D
semitransparent projection walls (Figure 6). Aircraft are represented with spheres. The
ought-to-be trajectory is projected on the wall (white line), as well as the aircraft
position (black dot). If the dot is not on the line, there is a path violation.</p>
      <p>The pure-3D prototype uses photographic terrain (high resolution satellite images)
and represent the aircraft as full 3D models (Figure 7). 2D rings enclose the
ought-tobe trajectory (plus some allowable deviation). The violation is detected when the
aircraft indicator is outside the rings. This approach is less strict that the 2D-in-3D.</p>
      <p>Human operator needs are satisfied in the following way: 3D display improves
situation awareness as the airport environment is depicted with essential terrain
obstacles; 2D elements (walls, ring) that relate the aircraft position to the airport
procedures reduce cognitive workload.</p>
    </sec>
    <sec id="sec-5">
      <title>4. Conclusions</title>
      <p>The following conclusions are drawn:
1. The proposed norm operationalization conception enables to represent a subset of
aircraft approach/departure normative rules in a decision support system for the
air traffic controller. The referred subset is defined as the norms concerning
aircraft trajectories, or simply, geometrical norms.
2. The prototype decision support system provides an integrated solution to
facilitating the controller: risk indicators automate detection of the possible norm
violations, 2D-in-3D visualizations help comprehend conformance to the
approach/departure procedure. The controller’s work improvement is not
quantifiable because the research addresses the needs that will only become
relevant in the future.
3. Analysis of the prototype development process demonstrates that the following
steps are needed to operationalize a norm: (a) setting up risk levels and colors, (b)
creating risk definitions (consisting of norm factor, expected value, type, pattern
and a set of thresholds), and (c) setting up risk indicators. The process cannot be
fully automated, as each norm factor is unique, and analysis has to be performed
for each new kind of norm to be operationalized.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <article-title>[1] The ATM Target Concept</article-title>
          , SESAR Consortium, Toulouse, France, Sept.
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Salerno</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Rondinella</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. V.</given-names>
            <surname>Crispino</surname>
          </string-name>
          , G. Costantini,
          <string-name>
            <given-names>M.</given-names>
            <surname>Carota</surname>
          </string-name>
          , and
          <string-name>
            <given-names>D.</given-names>
            <surname>Casali</surname>
          </string-name>
          , SKY-Scanner:
          <article-title>a new paradigm for air traffic management</article-title>
          ,
          <source>International Journal Of Circuits, Systems And Signal Processing</source>
          <volume>2</volume>
          (
          <issue>2</issue>
          ) (
          <year>2008</year>
          ),
          <fpage>131</fpage>
          -
          <lpage>139</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>S.</given-names>
            <surname>Rozzi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Boccalatte</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Amaldi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Fields</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Loomes</surname>
          </string-name>
          , and
          <string-name>
            <given-names>W.</given-names>
            <surname>Wong</surname>
          </string-name>
          , Innovation and
          <string-name>
            <given-names>Consolidation</given-names>
            <surname>Report</surname>
          </string-name>
          , Middlesex University, London, UK,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>K.</given-names>
            <surname>Lapin</surname>
          </string-name>
          ,
          <article-title>SKY-Scanner: time-critical decision support system surveilling aircraft landing and take-off</article-title>
          .
          <source>In: Proceedings of 9th Innovative Research Workshop &amp; Exhibition</source>
          ,
          <string-name>
            <surname>Brétigny-</surname>
          </string-name>
          sur-Orge, France,
          <year>2010</year>
          ,
          <fpage>19</fpage>
          -
          <lpage>26</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>R.</given-names>
            <surname>Parasuraman</surname>
          </string-name>
          and
          <string-name>
            <given-names>C. D.</given-names>
            <surname>Wickens</surname>
          </string-name>
          ,
          <article-title>Humans: still vital after all these years of automation</article-title>
          .
          <source>Human Factors</source>
          <volume>50</volume>
          (
          <issue>3</issue>
          ) (
          <year>2008</year>
          ),
          <fpage>511</fpage>
          -
          <lpage>520</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Procedures for Air Navigation Services - Air Traffic Management</surname>
          </string-name>
          . Fifteenth ed.
          <source>International Civil Aviation Organization, ICAO</source>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Aeronautical</given-names>
            <surname>Charts</surname>
          </string-name>
          .
          <article-title>Annex 4 to the Convention on International Civil Aviation</article-title>
          . 11th ed. International Civil Aviation Organization,
          <string-name>
            <surname>ICAO</surname>
          </string-name>
          ,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Procedures for Air Navigation Services - Aircraft Operations</surname>
          </string-name>
          , vol.
          <volume>1</volume>
          and 2. International Civil Aviation Organization,
          <string-name>
            <surname>ICAO</surname>
          </string-name>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <article-title>[9] Manual on Volcanic Ash, Radioactive Material and Toxic Chemical Clouds</article-title>
          . Second ed.
          <source>International Civil Aviation Organization, ICAO</source>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>J. K.</given-names>
            <surname>Kuchar</surname>
          </string-name>
          and
          <string-name>
            <given-names>L. C.</given-names>
            <surname>Yang</surname>
          </string-name>
          ,
          <article-title>A review of conflict detection and resolution modeling methods</article-title>
          ,
          <source>IEEE Transactions on Intelligent Transportation Systems</source>
          <volume>1</volume>
          (
          <issue>4</issue>
          ) (
          <year>2000</year>
          ),
          <fpage>179</fpage>
          -
          <lpage>189</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>W. B.</given-names>
            <surname>Wong</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Rozzi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Boccalatte</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Gaukrodger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Amaldi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Fields</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Loomes</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Martin</surname>
          </string-name>
          ,
          <article-title>3D-in-2D displays for ATC</article-title>
          .
          <source>In: 6th EUROCONTROL Innovative Research Workshop</source>
          , Bretigny, France,
          <year>2007</year>
          ,
          <fpage>47</fpage>
          -
          <lpage>62</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>VatIta</given-names>
            <surname>Dispatching</surname>
          </string-name>
          , IAC No.
          <volume>350</volume>
          ,
          <string-name>
            <surname>Instrument</surname>
            <given-names>Approach Chart</given-names>
          </string-name>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>J. C.</given-names>
            <surname>Mankins</surname>
          </string-name>
          , Technology Readiness Levels,
          <string-name>
            <surname>NASA</surname>
          </string-name>
          ,
          <source>Office of Space Access and Technology, Advanced Concepts Office</source>
          ,
          <year>April 1995</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>