ed-147 how standardisation supports v&v activities · connecting eec validation infrastructure....
TRANSCRIPT
Thomas Damm, DFSEUROCAE WG-81 Chairman
ED-147 How Standardisation Supports V&V Activities
✈ Who are we?✈ Where do we come from?✈ What have we done?✈ How are we using our results?✈ What is next?
Structure
Who are we?
EUROCAE facts and figures
Non-profit organisation
270+ Members (+10% p.a.)
39 active working groups
2000+ experts
Staffing 12
Non-EuropeanMembers
30%
70%
EuropeanMembers
Global coordination
Standard RoundTable
50 % joint WGs
10 % joint WGs
EUROCAE WG-81
WG-81 is working on the interoperability between ATM:• real-time platforms and • real-time and fast-time platforms Founded: April 2008Members: ANSPs, airborne and ground
industry, aerospace institutesPublications: ED-147A / ED-148
Where do we comefrom?
✈ EVI counted in 2010 in Europe ✈ 26 analytical modelling tools✈ 30 automatic simulators✈ 38 HITL simulators✈ 13 field try platformsoperated by stakeholders of different ATM domains
✈ a few of them were partly interoperable
European V&V Infrastructure
Existing V&VI needed to change due to ✈ New global ATM concepts ✈ Collaboration of ATM stakeholders✈ SWIM throughout the ATM network
Indentified needs
✈No standard input formats ✈No ATM Interoperability standards✈No cross domain support✈No interchangeability standards ✈No real-time/fast-time couplings
Indentified gaps
What have we done?
ED-147 The Standard
Common Communication
Language
Common IOP Architecture
Common Operational Environment
CCL: • Reference Information Model • Common Information Model
CIA: • Logical interoperability architecture• Key architectural concepts• State and time management• Interoperability services
COE: • Operational environmental data formats • Output data formats
ED-147 RIM and CIM
• RIM the baseline for a common language
• CIM the „contract“ between participants
• Extracting and extentingas key to interoperability
ED-147 IOP Architecture
• Agent gateways connect cross domain ATM VPs
• Runtime IOP services• Network centric
infrastructure• State management
ED-147 Input and Output
Common formats for offline data preparation• Environmental data based on AIXM• Weather data based on AIXM extension• Flightplan data based on FIXM
Rules for common output format definition based on• CSV• JASON• XML
ED-148 The Guidance
Common Collaboration
Model
IOP IntegrationGuidelines
OperationsAt
Runtime
CCM: • V Model • Best practices for collaboration
IIG: • Data preparation• Model issues• Participant IOP needs• Engineering
OAR: • Runtime issues• Failure handling
✈ ED-147 stops at level of service definition✈ Various technologies are possible✈ Known implementations are based on HLA
✈ SVS – Shared Virtual Sky (Sopra Steria)✈ HLA Evolved (Pitch)
✈ Supplement to ED-147
ED-147 Implementations
Partners capabilities
Organisation SVS HLA (1516:2010)
Airbus
DFS
DSNA
ENAV
EUROCONTROL
NATS
THALES
SESARProgramme
EUROCAE & SESAR
• V&VI IOP requirements from SESAR program
• Feedback from validation exercises
• Helped to deliver improved EDs
R&D-standardisation-deployment
R&D Standardization Deployment and Regulation
✈No standard input formats ✈No ATM Interoperability standards ✈No cross domain support ✈No interchangeability standards ✈No real-time/fast-time couplings ()
Gaps vs Achievements
✈Interoperable Air Traffic Management validation platforms
✈Interoperability between components or systems✈Saves time and costs due to reusability✈Enables sharing of simulation platforms across
vendors and domains
ED-147 usage benefits
How are we using theresults?
AIRBUS Examples
AIRBUS
SESAR1 :• initial 4D (EXE-708, EXE-805) with Eurocontrol, EEC, ENAV• ASAS with ENAV• D-TAXI with EEC, ENAV
SESAR 2020:• Solution PJ18-02a with Skyguide & Dassault
Airbus Project :• i4d China - preparation for the flight test (March 2019)
Airbus internally to link simulators together or with other platforms(traffic generator, ATC platforms…)
CPNY: AIRBUSPILOT: Flight Test pilots and Airline
Simulator: A320 Simulator: A350 PURPLES
Shared Virtual Sky
CPNY: AIRBUSPILOT: Flight Test pilots and Airline
Simulator: ATG
CPNY: AIRBUSPILOT:Simulator testers
ED-147
Agent Gateway Agent Gateway Agent Gateway
Simulator: R&T Sim
CPNY: AIRBUSPILOT: Flight Test pilots and Airline
Agent Gateway
Simulator: TESLA
CPNY: AIRBUS Defense & SpaceATC center
Agent Gateway
Simulator: Voice
CPNY: AIRBUSPILOT: Flight Test pilots and Airline
Agent Gateway
Internal usage
SESAR 1: D-Taxi
CPNY: AIRBUSPILOT: Flight Test pilots
Simulator: A320 Simulator: ENAV PURPLES
Shared Virtual Sky
ATC center
ED-147
Agent Gateway Agent Gateway• Aircraft positions• Flight plan • Datalink messages• Voice
Data Link
Voice
ARINC ATN network(AGR/GGR)
i4D China
Shared Virtual Sky
System: Airtel DL-FEP
Agent GatewayAgent Gateway
Aircraft VHF antenna
VLD2 air/ground link
ARINC VHF ground station
ATM System (CWP/FDP)
• Air traffic• Surveillance data
SESAR Flight Object IOP
DFS Example
FO IOP Validation
Validation subject: Flight Object Interoperability (En-route/En-route)Validation framework: SESAR 2020 – Solution PJ18-02bPartners: DFS, DSNA, ENAV, EUROCONTROL, COOPANS, NATS, INDRA, LEONARDO, THALES Air Systems
ED-147 enabled simulators of four ANSPs are supporting the validation of Flight Object Interoperability by:• Synchronizing the start of the exercise run • Locally stimulating the system prototypes with surveillance data• Exchanging the position of each aircraft among each other• Handing over the aircraft control between the upstream and the downstream
simulator at the boundary
FO IOP Airspace
DFS: Karlsruhe UACDSNA: Reims UAC +
Geneva & Zurich UACENAV: Paduva & Milan UACMUAC: Maastricht UAC
FO IOP Validation Setup
ANSP: DFSSystem: iTECAirspace: KUACLocation: Langen
FO Manager
Simulator: NEWSIM Simulator: PURPLES Simulator: SimK
Shared Virtual Sky / HLA Evolved
SWIM Blue Profile
ANSP: DSNASystem: COFLIGHTAirspace: REIMSLocation: Toulouse
FO Manager
Simulator: eATG
ANSP: ENAVSystem: COFLIGHTAirspace: PaduvaLocation: Rome
FO Manager
ANSP: ECTRL MUACSystem: NewFDPSAirspace: MUACLocation: Maastricht
FO Manager
ED-147
ED-133 FO
AOTPOAFO
Agent Gateway Agent Gateway Agent Gateway Agent Gateway
Connecting EEC Validation Infrastructure
EUROCONTROL Examples
ED-147 by means of HLA Evolved
EUROCONTROL validation tools interop based onED-147 HLA-Evolved
ECS cockpit
ESCAPEEn-route/TMA
eDEPTower
Tower external view
eATGAir Traffic Generator
HLAevolved
ED-147 by means of SVS
EUROCONTROL validation tools interop based on ED-147 SVS
ESCAPEEn-route/TMA
eDEPTower
eATGAir Traffic Generator
SVS
THALES Examples
THALES
THALES used ED-147 (in SESAR 1) during: • i4D (EXE-203, EXE-204) together with Airbus, MUAC and
NORACON/Thales • FO IOP (EXE-022, EXE-711) with DFS/INDRA, DSNA/Thales
and MUAC/INDRA
We are also currently implementing internally a simulation bus using an implementation of ED147-A on HLA Evolved with the objective to prepare and be compliant with the future ED147-B HLA Technology Mapping.
What is next?
✈ Publications✈ ED-147B✈ ED-148A✈ Supplement to ED-147B
(HLA Technical Mapping)✈ Model Driven Approach✈ ED-147 / RPR FOM bridging✈ OEVIS - Technical feasibility study
WG-81 way forward
✈ How is the FAA and the American ATM community solving the interoperability topic?
✈ Do you see a chance for a collaboration with us together with RTCA?
Questions