NASPAC 2.0 Architecture
January 27, 2010
Agenda
•
•
•
•
Introduction to NASPAC
Current Architecture
NASPAC 2.0 Requirements
NASPAC 2.0 Architecture
2
Introduction to NASPAC
3
• National Airspace System Performance Analysis Capability (NASPAC)
• System wide discrete event Simulation tool
• Purpose
• Tool to aid in designing, developing, and managing the National Airspace
System
• Cost benefit analysis
• Why NASPAC?
• SPEED!
• Takes less than 10 minutes to model one day
4
NASPAC Architecture - Current
ATO-P Input Schedule
ATO-P Schedule
City Pair files
Equipage file
Trimming and
Smoothing
SCHEDULE
FILTER
Q-ROUTE 1
ETMS to BADA Mapping
Dictionary
Combined Fleet Forecast
ATO-P Input Schedule
Between Aircraft Category
Evolution Configuraton File
Flight Plan
Turn Around Times
Flight
Plan
ITINERARY
GENERATOR
Itinerary
Fleet Evolution
flag enabled?
FLEET
EVOLUTION
Yes
Itinerary
No
Itinerary
Itinerary
Input Schedules
Sector Definitions
Sector Names
ETMA-BADA
Aircraft
Modeler flag
enabled?
GATE FINDER
Yes
Itinerary
ETMS-BADA
AIRCRAFT
MAPPER
No
TRAJECTORY
MODELER
VFR
Aircraft
Sector Geometry Definition
Restrictions Definition
FIND
CROSSINGS
Equipment Categories
Climb & Descent
Profile Map
AM Departure Fix
AM Arrival Fix
AM Airports
AM VFR Airports
IFR Trajectories
IFR Trajectories
Sector Initial capacity File
City Pairs file
IFR Trajectoires
And
Find Corssings
IFR
Crossings
Q ROUTES 2
FORMATTER
IFR Crossings
Airport Attributes
VFR Aircraft
Expanded Quota Overflow
Delays to Airport
Estimated Departure
Clearance Time
Swap CNX
Aircraft
Airport Weather
Airport Special Conditions
Airport Pareto Curves
Airport Initialization
Airport Conditions
Sector Capacity
Sector Time Capacity
GDP Airport Configuration
Airport Initialization
Airport Pareto Curves
Airport
CHANGE FILE
GENERATOR
Change
Parameter
GDP
GENERATOR
Yes
Aircraft
(file will be
modified)
No
Aircraft
Legend:
Pre-Processor
Simulation Core
GDP Module
enabled?
Change Parameter
Airport Initialization
Aircraft File
SIMULATION
ENGINE
Trace files
Post-Processor
POST
PROCESSOR
Filenames
Arrival Fix Capacity
Departure Fix Capacity
In-Trail Restriction
Sector Capacity
Simulation Airport Pareto Curves
Airport Initialization
Turnaround Time
En Route Time
Aircraft
Change Parameter
Periodic
NASPAC Architecture – Current (simplified)
Data Files
Data Files
Pre-Processor
(Mostly Java)
Aircraft File
Generator
Aircraft File
Simulation Engine
(SimScript language)
GDP Generator
Change File
Generator
Post-Processor
(Java)
Change File
Preprocessed
Input Data to
Sim Core
Output data files
from Sim Core
5
NASPAC 2.0 – Requirements
•
•
•
Reduce complexity
•
•
•
•
Preprocessing
Deployment
Post-processing
Maintenance
Support dynamic events - generic software agents that can change model
conditions during runtime based on pre-defined rules
•
•
•
•
•
Trajectory modeling, rerouting and cancellations
Model dynamic weather
Introduce geometry into SIM (spatial calculations)
Support multi-pass GDPs
Dynamic sectorization
Support Monte Carlo Simulation or Batch runs
•
Bring schedule generation and trimming into NASPAC
•
Data management
•
Testing and Validation
•
•
•
•
•
Input files – inputs bounds and consistency check
Provide output data analysis
Output files – Graphical display of outputs
Automate testing and validation
Speed of execution
6
NASPAC 2.0 Architecture (proposed)
Data
nput g
I
f
o
n
ntatio
cessin
Prese ol the pro
Contr
Data Files
Scheduler
Flt Evolution
Traj Modeler
Find Cross.
GDP Module
Change File
JAVA Controller
NASPAC Analyst
Two way
Sim Core
Web browser based
Java components
Web Application
Server
Optional
Data Files
Relational
DB
For light weight standalone reporting
7
NASPAC 2.0 – Architecture …
8
• Description
• Port all pre and post processors to Java
• Component based architecture (jars as plug-ins)
• Use JNI to transfer data between Sim Core and Java or use a java based
simulation package
• Provide reporting tools for output data analysis
• Provide GUI to run and manage batch processing
• Advantages
• Ease of development in java for data preparation, and pre and post processing
• Allows seamless communication between all the components providing a
feedback mechanism
• Challenges
• SimScript language does not support JNI interface
• Java based simulation packages are not scaling too well (threading and memory
issues)
• Bring schedule generation within NASPAC
Questions?