. Request for ride report
. Response to CAT information
. Request for altitude change
. Report of speed change
. Declaration of emergency
. Sector exit
plus a minimum level of controller response. These standard procedures were then integrated into sequences (along with associated related actions) to handle the various situations that could arise in the CAT scenario, including:
. Handling various PIREPs
. Response to CAT sensor warnings
. Response actions to experience of light/moderate/severe turbulence
. Declaration of emergency
The full scripts are given in Appendix C.
Controller Specifications
This section presents an overview of the functional specification of the tasks to be performed by the en route sector controller. This specification describes the processes and decision rules that controllers use to perform these tasks. The representation of the cognitive behavior involved in executing these tasks must take account of several aspects, including monitoring and perception, decision-making and planning, and associated communications and other actions. Within this framework, controller situation awareness is modeled as a set of data that needs to be constantly updated. As was established by prior efforts to develop a formal representation of controller tasks (CTA, Inc., 1987; CTA, Inc., 1988; Rodgers and Drechsler, 1993), it is apparent that controller behavior cannot be represented as a rigid sequence of tasks. Rather, the controller must switch between tasks, suspend and resume tasks, and repeat tasks depending on the events that take place.
In defining the controller tasks, particular attention was given to those tasks involved in responding to the occurrence of clear air turbulence (CAT) within a sector. Therefore the scope of this specification is limited to controller tasks that are directly applicable to the modeling effort being undertaken and is not intended to provide a complete representation of all controller responsibilities. While this task specification was tailored to a specific application, it was structured so that it could be expanded in scope to include additional controller tasks, or to represent controller operating procedures in greater detail.
Assumptions
In defining the tasks to be performed by a controller, it is recognized that many of these tasks will need to be iterative. While the behavioral logic describes a progression through a sequence of successive tasks, in some cases it will be necessary to repeat specific subtasks. For example, the process of selecting the preferred maneuver to avoid a conflict might include identifying, checking, and comparing several unique maneuvers.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址:DEVELOPMENT OF FAST-TIME SIMULATION TECHNIQUES IN THE NATION(33)