Trajectory Tool Questions and Answers.pdf

SIR

Section

Question FAA Response

C.4 Would like to know if the base year is paid upfront or after the successful delivery of the custom application?

Payment is made upon delivery and acceptance of this custom software tool for each 12 month performance period.

Training hours will be paid as required.

L The Government is requesting a software product / license as the predominate scope of work requested within the SIR. Would the Government consider updating the NAICS to 513210

– Software Publishers?

NAICS code 513210 applies to establishments primarily engaged in computer software publishing or publishing and reproduction. This requirement is more appropriate to establishments primarily engaged in planning and designing computer systems and has been used in the prior acquisition of this tool.

C.3.2 The listed requirements and specifications for the tool, are purely for domestic flights, as well as flights entering and leaving U.S airspace correct?

This requirement is for a tool that can be used for both domestic and oceanic operations that either terminate or originate or cross US airspace. All oceanic operations need to include origin to termination trajectory points. This is critical to some of the oceanic analysis especially boundary crossings.

International flights that have nothing to do with the US are to be disregarded?

Yes provided that they do not cross through US Airspace whether domestic or oceanic. For instance, a flight that flies from Canada to Asia that crosses over Alaska would need to be included. This is a hypothetical example. Similarly, over the ocean, it is possible to cross across over US controlled oceanic air space yet never touch US soil.

The Confirmation that the data provided by the FAA’s SWIM subscription is sufficient enough when it comes to fast-time/real-time data , as well as historical data?

The tool needs to be able to interface and process SWIM historical data.

L We respectfully request the inclusion of NAICS code 541330, Engineering Services, Military and Aerospace Equipment and Military Weapons, with a size standard of $47.0M.

NAICS code 541330 applies to establishments primarily engaged in applying physical laws and principles of engineering in the design, development, and utilization of machines, materials, instruments, processes, and systems specifically relating to military aerospace equipment and/or military weapons. This requirement is more appropriate to establishments primarily engaged in planning and designing computer systems and has been used in the prior acquisition of this tool.

C.3.2 Is the tool assumed to be an aircraft simulation or an analytical tool with algorithms for trajectory planning?

This should be an analytical tool that can allow trajectory analyses including modification of historical trajectories. It is not an aircraft simulator in the sense of a cockpit simulator where the user flies the aircraft. The prime capabilities listed under Task 1 of the SOW state it should show flight progress against a map of the airspace being analyzed. Using historical data, it should allow for “what-if” scenarios, adjusting flight trajectories and evaluating aircraft-to-aircraft conflicts. It essentially simulates traffic in a specified airspace, allowing analysis of movement in the airspace by adjusting flight trajectories and evaluating possible conflict.

Is the tool required to have all required functionality out of the box, or is it assumed some adjustments and development will need to be done to tailor the tool to the exact needs of the customer?

It is expected that the tool will be functional for analyses of trajectories out of the box. It is expected that modifications made to update and create interfaces to data sources will be required as data sources change and new sources become available.

Are modifications of input data for what-if scenarios done outside the tool before it is run (e.g. modification of file with fixes or flight definition) or is it assumed to be done within the tool? If within the tool, is it expected to be done in text editors or a graphical interface?

It is expected that the tool will allow the development of what if scenarios using a combination of input data modification, user interface, and text configuration files if part of the tool.

How are trajectories envisioned to be adjusted?

Trajectories are expected to be adjusted via text manipulation of the trajectory file indicating coordinate waypoints, compass heading, velocity, and altitude.

If a tool allows graphical manipulation, it may be considered beneficial however the practicality of manipulating an entire NAS of trajectories using graphical means seems impractial.

What are examples of assumptions, formulas, and algorithms that should be visible, and how changes to scenarios to be implemented? (e.g. by changing values in configuration, creating API and interface to allow third-party to implement some code into the tool?)

This is not to be considered an all encompassing list but rather represents a few examples of how the tool will be used. 1) Cloning a series of trajectories to represent increased operations and then running the model to determine if increased traffic results in increased separation violations. This might include the ability to allow the modeled flights to pass very close to determine how much separation is lost with the increased operations. 2) Counting traffic flying through a specific flight region to determine the number of aircraft being handled. 3)Allow traffic in a particular region to look ahead to traffic entering from multiple other regions. Given this set of examples, it is expected that the user would have an understanding of separation measurement algorithms including the variables used in the calculations. If multiple methods are used, the user should be able to select the method of measurement and the associated variables. It would probably be useful for the tool to offer a notebook type mode where key metrics and assumptions could be laid out for review.

Any probabilistic functions should use repeatable numbers.