曝光臺 注意防騙 網(wǎng)曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費(fèi)者

Note: These terms and attributed ‘meanings’ are not formal definitions, nor does their use suggest that they are the only terms in use. These explanations are provided for reasons of clarity, and additional information is provided at para. 1.3.1.
.  
Base Case and Test Case: Respectively, these terms are the ‘validation equivalent’ of the Reference Scenario and a Proposed Scenario referred to in the conceptual design phase. The Base Case and Test Case have two components viz. Airspace Organisation and the Traffic Sample.

Note: The Base and Test Case are created for Validation purposes. They are based upon the Design Concept developed as per the Design Methodology (for example) contained in Part C of this document.

.  
Airspace Organisation: The airspace organisation is made up of five parameters (list below). The first four of these are components of the Base and Test Case - which are based upon the Design Concept following, for example, the guidelines contained specifically in Chapters 5 & 6 of Part C.

.  
Terminal Airspace structure;

.  
ATC Sectorisation;

.  
Routes;

.  
Holds;

.  
Rules.

.  
Traffic Sample: The Traffic Sample is made up of three parameters, viz.:

.  
(Air) traffic which operates in a particular airspace organisation;

.  
Date e.g. DDMMYY (A Time ‘stamp’ may also be included;

.  
Rules of traffic assignment.

Note 1: See also Part C, Chapter 4 and para. 1.5.4.
Note 2: A Reference Traffic Sample is usually associated with a Base Case.
T
e
r
m
i
n
a
l
A
i
r
s
p
a
c
e
D
e
s
i
g
n
G
u
i
d
e
l
i
n
e
s
-
P
a
r
t
D

.  
Parameters: An element of either the Airspace Organisation or Traffic Sample.

.  
Trajectory/Aircraft Trajectory/Flight Trajectory: refers to the 4D path of an aircraft through (simulated) airspace.

.  
Rules: Refer to any operational procedure and/or co-ordination agreement that-

.  
as regards Airspace Organisation, affects the dimensions of the Terminal Airspace structure and/or ATC Sectorisation and/or the definition of or operation along Routes and Holds. Examples of Rules which might affect the operation along Routes and Holds include level/speed restrictions published in SIDs/STARs or inter-sector co-ordination agreements to be replicated on a fast-time simulator.

.  
as regards the Traffic Sample, affects the way in which the air traffic is assigned to operate, either along pre-defined Routes/Holds or in anticipation of tactical vectoring by ATC.

1.3.1 NAMING BASE AND TEST CASES
In order to trace cause and effect when analysing simulation runs, and as a means of properly recording simulation results, it is crucial that Base and Test Cases be clearlyidentified. More importantly, clear identification is important in order to avoid confusing the vast quantities of numerical data generated by quantitative assessment tools. For this reason, the Terminal Airspace design team (and its Validation counterpart) should agree upon a clear Scenario/Test Case naming convention. As importantly, this naming convention should be systematically used and commonly understood by all participants – see Figure 1 -2, below, for examples.
It is recommended that such a naming convention should at least provide the following information:
.  
Coded designator of the Airspace Organisation to be used (e.g. Org PR, Org A etc.)

.  
Coded designator of the Runway in use and associated Traffic Sample (e.g. 01-RT means RWY01, Reference Traffic Sample or 01-R24022004, where the numbers after the R are a date-time ‘stamp’ of the traffic sample.)
　
中國航空網(wǎng) m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：EUROCONTROL MANUAL FOR AIRSPACE PLANNING 2(83)