RAMS Plus Features

The RAMS Plus ATM modelling features consist of two functional domains: RAMS Plus Airside and Groundside.

Both functional domains work together in the same environment to provide a global macro/micro gate-to-gate view of the air traffic system being modelled.

RAMS Plus Airside is a runway-to-runway simulator, where the primary functionality includes:

  • 4D Flight Trajectory Calculation, including Great Circle and speed/altitude restrictions
  • 3D Sectorisation
  • 4D Spatial Conflict Detection
  • Multiple Separation Strategies (e.g. controllers, equipment, dynamic situations, etc.)
  • AI Rulebase Conflict Resolution
  • 4D Resolution Maneuvering (for enroute delay)
  • TMA (arr/dep sequencing, SIDS/STARS, Holdstacks, vectoring on approach, etc.
  • Dynamic Task Assignment
  • 1..N Stream Time-Based Metering with user-defined subscription
  • Runway scheduling and runway usage conflicts
  • Weather (wind effects on airborne aircraft performance)
  • Editor and display environment in standard MS Windows look-and-feel
  • Animated simulation graphics and replay mode

Primary objectives of the RAMS Plus Airside include:

  • Benefits of NexGen and SESAR implementations
  • Propose alternative sectorisation
  • Measure controller workload
  • Measure airspace and conflict complexity/density
  • Measure airspace safety in relation to separation violations
  • Impacts of free-routing or RVSM concepts
  • Impact of the ATM system on fuelburn
  • Unlimited views of ATM concepts
RAMS Plus Groundside simulates airport operations from the gate to SIDS & STARS, where features include:

  • 1..N Airport Layouts within the same scenario
  • Gate allocation by airline/aircraft model
  • Shortest path taxi routes
  • Taxi link speed and separations
  • Taxi links by arrival/departure, airline, and aircraft model
  • AI Rulebase Conflict Resolution
  • TMA (arr/dep sequencing, SIDS/STARS, Holdstacks, vectoring on approach, etc.
  • 4D Resolution Maneuvering (for TMA approach)
  • Runway scheduling and runway usage conflicts
  • Runway accel/decel rates by aircraft model
  • Runway hi-speed exits (by aircraft model/type/airline)/
  • Runway back-tracking
  • Runway blocking other runways when in use
  • Running crossing for taxiing aircraft
  • Editor and display environment in standard MS Windows look-and-feel
  • Animated simulation graphics
  • Delay reports by unlimited criteria (e.g. airline, gate(s), runway, departure queue…

Primary objectives of the RAMS Plus Groundside include:

  • Propose alternate runway configurations, including new or closed runways
  • Measuring runway demands and operations
  • Measuring ground delay, for example by taxi times, airlines, arr/dep, average flight delay, etc.
  • Proposing taxiway configurations
  • Using Both Domains Together: Gate-to-Gate
  • The Airside and Groundside share much of the same data, and co-exist in the same environment.

Examples of data and feature overlap include:

  • Traffic schedule and profile definition
  • Aircraft model performance data
  • Airports
  • Runway configurations.
  • SIDS/STARS

The primary objective of using both the Airside and Groundside features together is to measure the impacts of ground operations/delay on the entire ATM System, providing a gate-to-gate view of the scenario being studied. This gate-to-gate view reflects interaction and knock-on effects of aircraft from departure gate passenger loading to arrival gate unloading.

Type of Data RAMS Plus requires:

RAMS Plus is fully data-driven, and includes default data for aircraft models, aircraft performance, airport locations, default rulebases, country frontiers, etc.

RAMS Plus data formats are easy to create, where RAMS Plus data is ASCII text format, and all location references are lat/long in any recognised format (decimal degrees, HHMMSSD, etc.)

If you have time or resource constraints, ISA Software are specialists in ATM analytic studies and data preparation.

To study a basic airspace scenario, you need data to represent

  • Navaid names & geographic locations
  • Traffic schedule
  • Traffic routes (navaids and/or airway routes (comprised of navaids)
  • Sectorisation (basically comprised of geographic lat/long corner locations)

To study a basic TMA scenario, you need additional data to represent

  • SIDS and STARS
  • Airport runway locations
  • Holdstacks (optional)

To study a basic airport movements, you need additional data to represent

  • runway configurations
  • gate locations and gate usage (by airline, aircraft type, etc.
  • taxipath routes and usage (by departure/arrival, aircraft type, etc.)