Lockheed MITRE Collaborative Effort Go Button Implementation Using AviationSimNet 29 th June 2006 Bernard Asare Lockheed Martin Transportation & Security Solutions Strategic Programs & Initiatives T: +1 301 640 3681 E: bernard.asare@lmco.com The contents reflect the views of the author and The MITRE Corporation and do not necessarily reflect the views of the Federal Aviation Administration (FAA), the Department of Transportation (DOT), the National Aeronautics and Space Administration (NASA) or any other AviationSimNet partner. Neither the FAA, the DOT, NASA, nor other AviationSimNet partners make any warranty or guarantee, expressed or implied, concerning the content or accuracy of these views. This is the copyright work of The MITRE Corporation. No other use is authorized without the express written permission of The MITRE Corporation. For further information, please contact The MITRE Corporation, Contracts Office, 7515 Colshire Drive, McLean, VA 22102-7508, 703-983- 6000 Patti Liguori The MITRE Corporation Center for Advanced Aviation System Development (CAASD) AviationSimNet Standards Working Group Chair T: +1 609 272 4044 E: pshearn@mitre.org Approved for public release; distribution unlimited Case # 06-0947 2006 The MITRE Corporation. All rights reserved. F053-B06-015 1
Background & Context Future operational concepts for managing NAS will involve a more integrated exchange of information between distributed stakeholders: National Traffic Flow Managers Air Traffic Control Centers Cockpit Crews Airline Dispatchers Defense / Homeland Security Participants All Stakeholders will need to have: Common Information on Flights, Weather, Track Data, and System Constraints (Shared Situational Awareness) Current & Future New Systems that are able to exchange information on seamlessly We believe information sharing Via SWIM-Infrastructure Infrastructure can start now with existing systems that are already in the field today 2
Go Button : Reroutes Today Advisory Messages CDM Net AOC/Dispatch Refiled flight 1 Refiled flight 2. Refiled flight N Strategic Planning Telcons Reroute Messages Sector Controller Amended flight 1 Amended flight 2. Amended flight N 3
Reroutes Integrated with User, ATM Automation Advisory Messages CDM Net AOC/Dispatch Refiled flight 1 Refiled flight 2. Refiled flight N Strategic Planning Telcons TFM-I Flight- Specific Reroutes Messages Sector Controller Conflict Probe Amended flight 1 Amended flight 2. Amended flight N CPDLC 4
Why AviationSimNet? Supports rapid integration of existing disparate simulation environments into a single simulation environment that is defined and built by the users of the environment. (The AviationSimNet Standards Working Group) Provides a simulation environment to experiment with new operational concepts and the required flight objects, architectures, res, etc. for implementing and validating such concepts that otherwise would not be available Provides a great opportunity for collaboration across the aviation industry 5
Lockheed / MITRE Collaborative Work: : Project Overview The first step to exploring the integration issues at the conceptual level of TFM & En-Route integration would be to connect the Lockheed Martin TSS aviation laboratory with MITRE CAASD s aviation laboratory through the AviationSimNet to enable MITRE TFM systems, such as CRCT,, to exchange information with Lockheed Martin s s systems, such as URET, which is part of the SWIM infrastructure McLean, VA Rockville, MD Execution of an airborne reroute CAASD ATM LAB CRCT LM R & D Lab SWIM IRAD URET ARTCC TMC TFMS ARTCC ATC ERAM 6
Lockheed / MITRE Collaborative Work: : Concept Cross-Domain Linkage CRCT: Reroute Planning Aircraft ID Arrival airport Departure airport End-to-end reroute TMI information URET: Reroute Delivery 7
Lockheed / MITRE Collaborative Work: Goals Develop a better understanding of the cross domain issues associated with integrating emerging decision support capabilities whose implementation will require the integration of o TFM, terminal and en route decision support systems and data bases with systems used by airline operations centers. Develop a better understanding of issues associated with exchanging Flight Object data in an operational SWIM-like environment and to subsequently establish the industry standard for exchange of flight information in a simulation environment by b extending the AviationSimNet FOM Collaborate with the AviationSimNet Standards Working Group to refine and enhance the Federation Object Model and to ensure that the AviationSimNet FOM complements the Flight Object used in operational Air Traffic Management automation systems 8
Lockheed / MITRE Collaborative Work: Approach Phase 1: Establish connectivity between Labs (July 2006) Determine network requirements Work through corporate security requirements Using Go Button ops concept as starting point, determine data exchange requirements Phase 2: Exchange information between MITRE s s CRCT Tool and Lockheed s s SWIM Infrastructure (Preliminary experiment) (Sept 2006) Show receipt and application at LMTSS of flight specific flight plan amendment data generated at MITRE Phase 3: Design and Execution of Flight Object Experiment (Date not yet determined) Extend definition of FOM to include information used by operational Flight Data Object Determine requirements for exchanging TMI messages between TFM systems and en route decision support automation (ERAM) 9
Lockheed / MITRE Collaborative Work: Work: Preliminary Experiment Scenario Using the CRCT system, the reroute information will be sent to URET via the AviationSimNet. URET, using SWIM services, receives the reroute information, processes the reroute, performs conflict probe, and presents the proposed change to the controller. Once the proposed reroute is accepted then the corresponding SWIM/URET flight data is updated. If conditions allow, additional airborne flights may be rerouted following the same process. 10