8/8/2019 01 Asmgcs History
1/25
1
A-SMGCS
History &
EUROCONTROL Project
8/8/2019 01 Asmgcs History
2/25
2
Contents
Brief History
EUROCONTROL A-SMGCS Project
8/8/2019 01 Asmgcs History
3/25
3
History 1
1974
First overall view of SMGCS by
ICAO, who laid down first
Operational requirements.
International Group set up to
determine how these requirements
should be met.
1979 ICAO Circular 148 SMGCS.
8/8/2019 01 Asmgcs History
4/25
4
History 2 1981
Agreement to improve
SMGCS related
specifications in Doc.4444,
Annexes and Circular 148
Recommendation to publish
SMGCS related material in
separate Manual
1986
Doc. 9476 SMGCS
published
8/8/2019 01 Asmgcs History
5/25
5
A-SMGCS
Conceived 1990
Current players
ICAO
EUROCAE
European Comission
EUROCONTROL
FAA/NASA
Airports
Draft ICAO Manual published EUROCAE MASPS available
Implementation underway
8/8/2019 01 Asmgcs History
6/25
6
Eurocontrol Airport Operations
Programme
w Consists of four main projects: A-SMGCS
Airport CDM Applications
Airport Airside Capacity Enhancement
Runway Safety
w Also involved in Wake Vortex separation criteria
w Timeframe 2002-2006
8/8/2019 01 Asmgcs History
7/25
7
A-SMGCS Project Objectives
To fully develop A-SMGCS Levels 1 & 2, ensuring that all issues
relevant to operational implementation are identified and addressed
Identify, develop & validate appropriate procedures
Verify performance requirements
Build Safety & Human Factors Cases Address training & licensing
Support harmonised implementation within ECAC
Support global implementation (through ICAO)
Ensure coordination with ICAO, EC, FAA, NAV CANADA etc.
Provide baseline for further developments (A-SMGCS Levels 3 & 4)
8/8/2019 01 Asmgcs History
8/25
8
Project Organisation
A-SMGCSProject
Airport Operations ProgrammeAdvisory Group
Airport Operations Team
A-SMGCSProject Coordination Group
A-SMGCSProcedures Group
ICAOEUROCAE
EC
8/8/2019 01 Asmgcs History
9/25
9
Outline Roadmap2002 2003 2004 2005 2006
Requirements Definition 12/03
Evaluation/Validation 07/05
Update Requirements 12/05
Development of Implementation Plan 12/06
Development of Standards, Recommendations
& Procedures
12/06
8/8/2019 01 Asmgcs History
10/25
10
A-SMGCS Context & Project Scope
A-SMGCS
MOBILES
Collaborative
Decision Making
Arrival
Management
Airport
Management
Departure
ManagementPlanning
/ Routing
Guidance
Surveillance
Control
Times ofarrival
Times ofDeparture
Stand allocation
Runway /Taxiway status,
Navigation(GNSS,)
Mobile Position
Voice And Data Link
communicationAutomatic Dependant
Surveillance
Other sensors Mobile Parameters
Alerts, guidance,
Traffic situation
Assigned routes
Alert eventsConflict
resolutions
Project
Scope
8/8/2019 01 Asmgcs History
11/25
11
What are A-SMGCS Levels?
Level 1
Based upon improved surveillance (cooperative independent, dependent or
multilateration) and procedures (identification, issuance of ATC
instructions & clearances)
Level 2 Safety nets (runway, restricted areas) and associated procedures.
Level 3
Detection of all conflicts on movement area, improved guidance &
planning (for controllers)
Level 4
Resolution of all conflicts, automatic planning & automatic guidance for(pilots & controllers)
Levels 3 & 4 are outside scope of current project
8/8/2019 01 Asmgcs History
12/25
12
A-SMGCS Level 1
A-SMGCS Surveillance
Manoeuvring Area for Vehicles
Movement Area for Aircraft
Cooperative Surveillance
Display
Traffic Context
Position
Identity
Performance based upon
ICAO/EUROCAE Air Traffic Controller
Traffic
Situation
Picture
Traffic Context
Position, Identity
of Mobiles
Airport Traffic Context
Airport Traffic
Actions on
Traffic
Surveillance
Information
8/8/2019 01 Asmgcs History
13/25
13
A-SMGCS Level 2
A-SMGCS Surveillance +(elementary) Control
Conflicts/infringements
between all mobiles on
runways
Incursion into restricted
areas by aircraft
Appropriate alert to
controllers Intended as a commonly
agreed minimum safety
net
Air Traffic Controller
Traffic Situation
Picture +Conflicts /
Infringements
Detection
Traffic Context
Position, Identity,
Speed, of
Mobiles
Airport Traffic Context
Airport Traffic
Actions on
Traffic
Surveillance
Information
Alerts
8/8/2019 01 Asmgcs History
14/25
14
Level 2 Runway Safety Net
Aimed at detecting potentially dangerous scenarios
Addresses aircraft & vehicles (not persons)
Does not vehicle/vehicle conflicts
Generic scenarios identified for:
Single runway
parallel runways
Intersecting runways
Multiple conflicts to be considered as multiple pairs
Two warning types
Prediction
Alert
Parameters for:
Normal Visibility
Low Visibility
32 1432 1432 1432 14
8/8/2019 01 Asmgcs History
15/25
15
What does it look like?
SMR
Basic
A-SMGCS
(SMR + Mutilateration)
8/8/2019 01 Asmgcs History
16/25
16
Need for A-SMGCS Procedures
No provisions addressing use of A-SMGCS Surveillance
Ambiguities with respect to the use of SMR:
Interpretations of augment & assist
Diverse uses/procedures Need for harmonised use of A-SMGCS surveillance data
Concerns Controllers/Pilots/drivers
Global application, increased traffic in all weather conditions
Basis for further A-SMGCS developments
Need to deliver benefits of A-SMGCS!
Aim to deliver validated proposal (including safety case) to ICAO
8/8/2019 01 Asmgcs History
17/25
17
A-SMGCS Procedures
Transponder Operation
Methods of identification
Issuance of ATC instructions and clearances to aircraft & vehicles on the Manoeuvring
area
Taxi Clearances
Resolution of conflicts
Issuance of ATC instructions and clearances to aircraft and vehicles on the the runway Conditional Clearances
Multiple line-up/intersection departures
Crossing
Phraseology
Contingency & Failure mode
Low Visibility Procedures (transition from Visibility 2 to 3)
8/8/2019 01 Asmgcs History
18/25
18
Transponder Operating Procedures
Pilots requested to switch on their
transponders from:
From the request for push-back or taxi
(whichever is earlier)
After landing, until the aircraft is parked
on stand
Use XPNDR or equivalent mode
Not use STDBY or OFF
AIP, AIC & Brochure
Widespread Distribution Planned
8/8/2019 01 Asmgcs History
19/25
19
RPX 123,stand 1,
request taxi for departure
RPX 123Taxi to holding position
runway 27 viataxiway Alpha
RPX at holdingPosition Runway 27
RPX 123,Roger
27
RPX 123,stand 1,
request taxi for departure
RPX 123Taxi to holding position
runway 27 viataxiway Alpha
27
Example: Procedure 2Issuance of Taxi Clearances andInstructions
Applied to aircraft & vehicles
Applied in Visibility conditions (1), 2, 3 & 4
8/8/2019 01 Asmgcs History
20/25
20
DLH 456report passing Alpha
Taxi to Bravo,RPX 123
Report passingAlpha,
DLH 456
DLH 456passing Alpha
RPX 123,taxi to Bravo
RPX 123,holding position Bravo
RPX 123,roger
DLH 345,roger
RPX 123give way to DLH 737,
crossing fromthe right
Give way toDLH 737,RPX 123
Example: Procedure 3Resolution of Conflicts on Taxiways
Applied to aircraft & vehiclesApplied in Visibility (1), 2, 3 & 4
8/8/2019 01 Asmgcs History
21/25
21
Licensing/Training
Current provisions based upon the use of
SMGCS, where SMR is used to augment
and assist
However, the European ATC License will
support A-SMGCS
Specific training requirements to be
developed
8/8/2019 01 Asmgcs History
22/25
22
Implementation Mechanisms
Best Practice
Standards
Guidance Material
ECIP Objectives
Aim to ensure consistent application of A-SMGCS tools &
procedures, which will build confidence amongst users and
provide common specifications to assist manufacturers.
8/8/2019 01 Asmgcs History
23/25
23
Current Status & Next Steps
Agreed Requirements
documentation
Agreed Procedures concepts
Agreed Verification & ValidationProcess
First element of Verification &
Validation underway
Efforts to secures Trial Airports
8/8/2019 01 Asmgcs History
24/25
24
Summary Eurocontrol aims in support of harmonised implementation
Maximise benefits to individual airports & the overall ATMnetwork
Main tasks include:
Agreed concepts Agreed procedures
Safety (Case)
Human factors (case)
Licensing/training
Deliver validated concepts & procedures to ICAO
Global cooperation required
8/8/2019 01 Asmgcs History
25/25
25
Thanks &Any Questions?