1. ETFMS - SYSTEM OVERVIEW
Meteo Interface
FP-1
(Haren)
ETFMS
Central Server
(ETFMS-CS)
AN-1
ENV
Local
Terminals
Remote
FP-2
(Brétigny)
AFTN
CIDIN
Wide Area Network (s) T
AN-3
NM (CFMU)
ACC R
Entry
Nodes
ATM
systems
SDPS
FDPS

2. ETFMS - ARCHITECTURE

3. ETFMS - ARCHITECTURE Haren WAN Brétigny ATS ATS ATS AN3 CS EN-A EN-B
Router
ECMC
Others CS
ATS
EN-A
EN-B
Router
Correlated Position Data
Flight data (FSA)
ATS
EN-A
EN-B
Router
Correlated Position Data
Flight data (FSA)
WAN
Brétigny
ECMC
Router
AN3
Others CS
ATS
EN-A
EN-B
Router
Correlated Position Data
Flight data (FSA)

4. ETFMS - INSTALLED SITES
Planned 2012
Pending

5. ETFMS - EN Physical view

6. EN - Data Functions (1) Data Collection Data Forwarding
Interface to various ATS configurations at different sites
Receive Position Data (tracks) and Flight Plan Data
Data Forwarding
Connection Management, Frame Assembly
Data Replication to several recipients

7. EN - Data Functions (2) Data Processing
Convert data to common representation (ASTERIX CAT062)
Transform Coordinates into WGS84
Maintain Track and Flight Plan Database
User Controlled Data Reduction
Update Tracks and Flight Plan data Id fields

8. ETFMS - Data Items (1) Mandatory Data Items
Aircraft Identification (callsign)
Flight Level
Aircraft Position
ADEP / ADES
EOBT (*)
Mode 3/A SSR Code
(*) Highly desirable

9. ETFMS - Data Items (2) Optional Data Items IFPS_Flight_ID
24bit ICAO Aircraft address
Track Status
Aircraft Velocity
Rate of Climb and Descent
Rate of Turn

10. ETFMS - Interfaces (1) Supported Input Data Formats
ASTERIX CAT062 (v0.17 or v1.3)
FSA (*)
(*) Needed in case flight data items (e.g. ADEP, ADES, EOBT, IFPLID) are not present in the position data stream and/or to filter out VFR and OAT traffic.

11. ETFMS - Interfaces (2) Supported Connection Types TCP (¹) UDP (¹) X25
HDLC Datagram
‘RMCDE’
‘ARTAS’
AFTN - Async (²)
(¹) Preferred
(²) In case FSA messages are needed

12. ETFMS - PROCESS (1)
Agreement on the technical interfaces between EN and ATC system - ICD
Signature of Letter of Agreements (LoA), related to
Data provision
Equipment (ownership, installation, etc)
Financial conditions

13. ETFMS - PROCESS (2) Adaptations, if any, in ATC systems
Purchase and installation by NM (CFMU) of EN
Validation of received data (CPRs) in NMOC (CFMU) test system
Move of received data (CPRs) to NMOC (CFMU) operational system
FAM activation (after agreement with ANSP)

14. CPR Operational Evaluation
ETFMS - PROCESS (3)
CPR Operational Evaluation
Provide live data to ETFMS Shadow/test system.
NMOC (CFMU) Evaluates and provides evaluation report to ANSP.
Improvements may be required.
Go-No-Go decision.
Agree date to send CPRs to ETFMS Operational system.

15. ETFMS - PROCESS (4) Costs NM (CFMU) provides Entry Node.
NM (CFMU) provides network connection.
NMOC (CFMU) Operates Entry Node.
ANSP is requested to:
Supply space for EN rack in the computer room
Supply power for the EN
Adapt software of its ATC systems if required

16. Your questions are very welcome

17. Thank you for your attention
Michel Wuestenberghs