11
NASPAC 2.0 ArchitectureJanuary 27, 2010
22
Agenda• Introduction to NASPAC• Current Architecture• NASPAC 2.0 Requirements• NASPAC 2.0 Architecture
33
Introduction to NASPAC
• 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
44
NASPAC Architecture - Current
SCHEDULE FILTER
ITINERARY GENERATOR
Fleet Evolution flag enabled?
ETMA-BADAAircraft
Modeler flag enabled?
ETMS-BADA AIRCRAFT MAPPER
TRAJECTORY MODELER
No
Yes
No
FLEET EVOLUTION
Yes
Itinerary
Itinerary
FlightPlan Itinerary
Itinerary
Itinerary
VFRAircraft
ATO-P Input ScheduleATO-P ScheduleCity Pair filesEquipage file
Flight PlanTurn Around Times
ETMS to BADA Mapping DictionaryCombined Fleet ForecastATO-P Input ScheduleBetween Aircraft Category Evolution Configuraton File
Equipment CategoriesClimb & Descent Profile MapAM Departure FixAM Arrival FixAM AirportsAM VFR Airports
Q ROUTES 2 FORMATTER
IFR TrajectoriesIFR Trajectories
IFRCrossings
Sector Geometry DefinitionRestrictions Definition
IFR CrossingsAirport AttributesVFR AircraftExpanded Quota Overflow Delays to AirportEstimated Departure Clearance TimeSwap CNX
CHANGE FILE GENERATOR
GDP GENERATOR
SIMULATION ENGINE
POSTPROCESSOR
GDP Module enabled?Yes
No
Aircraft(file will be modified)
Aircraft
ChangeParameter
Change ParameterAirport Initialization
Aircraft File
Trace files
FilenamesArrival Fix CapacityDeparture Fix CapacityIn-Trail RestrictionSector CapacitySimulation Airport Pareto CurvesAirport InitializationTurnaround TimeEn Route TimeAircraftChange ParameterPeriodic
Airport WeatherAirport Special Conditions
Airport Pareto CurvesAirport InitializationAirport ConditionsSector Capacity
Sector Time Capacity
GDP Airport ConfigurationAirport Initialization
Airport Pareto CurvesAirport
Aircraft
Legend:
Pre-Processor
Simulation Core
Post-Processor
Trimming and Smoothing
Q-ROUTE 1
FIND CROSSINGS
IFR TrajectoiresAnd
Find Corssings
Sector Initial capacity FileCity Pairs file
GATE FINDERInput Schedules
Sector DefinitionsSector Names
55
NASPAC Architecture – Current (simplified)
Post-Processor(Java)
Simulation Engine(SimScript language)
Aircraft File Generator
Change File Generator
GDP Generator
Aircraft File
Change File
Pre-Processor(Mostly Java)
Preprocessed Input Data to
Sim Core
Output data files from Sim Core
Data FilesData Files
66
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• Input files – inputs bounds and consistency check• Provide output data analysis• Output files – Graphical display of outputs
• Testing and Validation • Automate testing and validation
• Speed of execution
77
NASPAC 2.0 Architecture (proposed)
Data Files
Sim CoreTwo way
JAVA Controller
Data FilesRelational
DB
Optional
Web Application Server
For light weight standalone reporting
NASPAC Analyst
Web
bro
wse
r bas
ed
Presentation of Input Data
Control the processing
Java components
Scheduler Flt Evolution
Traj Modeler Find Cross.
Change FileGDP Module
88
NASPAC 2.0 – Architecture …• 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
99
Questions?
Top Related