Download atfm modelling capability amoc

Transcript
EUROCONTROL EXPERIMENTAL CENTRE
EEC NOTE No 28 /97
The format of a flow is as follows:
<dep_family>{exception_list}.<arr_family>{exception_list}[^volume]
nb_of_flows
<flow_name1> 1
<start_of_period> <end_of_period>
...
<flow_nameN> 1
<start_of_period> <end_of_period>
(1) The <dep_family>/<arr_family> is the name of a set of airports. The family name
must be defined in the aerodromes file unless it is a single airport, a centre (all airports
belonging to the centre) or a country as whole.
(2) The <exception_list> specifies the set of airports to be excluded from the family of
the airports.
(3) <volume> specifies the part of the airspace to be protected. The volume is not mandatory and if it is not present then the protected area is the dep_family.
(4) nb_of_flows specifies the number of the sub-flows. Suppose that you want to protect a volume from 07:00 to 10:00 and from 12:00 to 18:00. As CASA does not accept
non contiguous intervals, you must define 2 sub-flows, one sub-flow for each interval.
(5) flow_name identifies the name of the flow. This name will be used later as the
name of the CASA regulation.
(6) start_of_period and end_of_period specify the start and end of the activation
period. SelFlow will be used to extract flights whose ETOs fall within this period and
CASA will use this period with a corresponding capacity to allocate slots.
Example1: Suppose we want to regulate all the traffic coming from LFPO, going to
LFMN and crossing the sector UGW between the period 08:00 and 18:00. First, you
must define the flow and give it a name. The name of this flow will be rUGW. The definition for this flow is as follows:
LFPO.LFMN^UGW
1
rUGW 1
480.0 1080.0
The departure and arrival family are single airports so you don’t need to define them in
the aerodrome files. You can if you want but it will be a redundant definition because
SelFlow understands the concept of single airports.
Example2: Suppose that we are interested in departures from FRANCE, going to the
North Atlantic between 18:00 and 20:00. We can see that the only volume of interest
in this abstraction is the departures from the French airports to the North Atlantic
regardless of which sectors are crossed. This flow will be called FRANC>NATS for
departures from France to NATS. Below we show some steps to define this flow:
AMOC: ATFM Modelling Capability
36