FSM-TSD ROM Draft 11.20.2020.docx

Rough Order of Magnitude (ROM) estimate for study in Statement of Work (SOW)

As part of their market research, the FAA is requesting a Rough Order of Magnitude (ROM) estimate for completion of the simulation platform in the enclosed SOW.

I. Scope of Work

The delivery vehicle is expected to be a high fidelity Flight Schedule Monitor (FSM)/Traffic Situation Display (TSD) cloud-based interactive simulation platform that allows for scenario development. The SVRWX trainee will use simulated TSD weather and the Traffic Flow Management Convective Forecast TCF to determine the most efficient use of airspace then build/send playbook and ad-hoc reroutes. The simulation platform must allow the Air Traffic Control System Command Center (ATCSCC) to create training scenarios that can be fully manipulated by the instructors and trainees.

Please consider the following requirements when building your ROM response (From section 1.3 of the SOW):

a. To effectively create and execute the scenarios, the ATCSCC needs the ability to model and send a GDP/GS including the ability to manually build FSM data to meet the training needs.

b. Modeling, sending, and modifying TSD reroutes is a critical job task for the SVRWX specialist. To effectively create and execute the scenarios, the ATCSCC needs the ability to manipulate TSD weather, TCF, demand, and playbook routes. Being able to model, send data, and make revisions creates a realistic simulated training environment.

c. The Terminal trainee will have the ability to model and send GDPs/GSs using manually constructed airport demand via simulation equipment. Each platform will be capable of holding at least 50 scenarios each. Scenarios and simulation fidelity must closely replicate the display and functionality of the TSD and FSM. Scenarios will be scripted.

d. The simulation equipment may include a Graphical User Interface (GUI) that displays textual injects that simulate input from the airlines and FAA facilities. Automated evaluation of skill performance (demonstration) should be considered. Incorrect selections may receive context appropriate feedback messages, to include graphically illustrated demonstrations of correct control activities. Seat hours for each scenario is not expected to exceed 1 hour.

e. The vendor will incorporate the existing ATCSCC scripted scenarios into the simulation platforms. In addition, the vendor will assist the ATCSCC in developing a bank of Terminal/SVRWX scenarios.

f. Scenario Storage – Vendor must incorporate the ability to store scenarios and student scenario run-throughs.

g. Simulation options – The vendor must consider options for either interfacing with the real FSM/TSD or creating a representation of the real world FSM and TSD. The vendor must take into consideration the fact that the FSM and TSD reside in the Traffic Flow Management Workstation (TFMS) when considering simulation options.

h. Schedule - Contractor input will be taken into consideration when determining a reasonable schedule for completion of the work outlined in this SOW. A detailed task schedule will be provided in the final version of the SOW to be posted at the time the contract is officially listed.

II. Flight Schedule Monitor (FSM)

The FSM displays a current picture of the air traffic demand using real-time data from Collaborative Decision Making (CDM) participant data aggregated by the TFM Processing Center (TPC). The FSM interactive cloud-based simulation platform must be as close as possible to the real world FSM. There may be some functionalities within the FSM simulation platform that are not necessary for training purposes. These functionalities should remain on the display image even if they are not operational. (See section 3 of the SOW.)

Please provide ROM Estimates for the following options that may be considered to complete the tasks specified in the SOW. Each estimate should be reported as a single number based on what the option describes. The FAA will consider the best option based off of the ROM estimates, the timeline, and the ability for the contractor to meet the requirements of the SOW using that particular option.

*If it becomes obvious that including all aspects of the functions list, regardless of priority, does not increase the overall total of the estimate drastically, vendors may provide estimates for only Options 1 and 3.

1) Option 1: Interfacing with the current FSM using the existing Graphic User Interface (GUI) and existing software. Refer to Appendix A: FSM Functions List, column F (Priority). This column indicates the priority level for each requirement of the FSM. The Option 1 ROM estimate should include ALL requirements regardless of priority level indicated on the Functions list.

Include an estimate for the length of time it may take to complete the work in the SOW utilizing option 1 including a brief description of your proposed timeline.

2) Option 2: Interfacing with the current FSM using the existing Graphic User Interface (GUI) and existing software. Refer to Appendix A: FSM Functions List, column F (Priority). This column indicates the priority level for each requirement of the FSM. The Option 2 ROM estimate should include only those requirements listed as CRITICAL in the priority section of the functions list.

Include an estimate for the length of time it may take to complete the work in the SOW utilizing option 2 including a brief description of your proposed timeline.

*Please note, it is important to keep the appearance of FSM as close to the real thing as possible. Some of the functionalities may not be required, but the display or image should be the same just without being operational.

3) Option 3: Create a representation of the real world FSM without use of the existing GUI and software. Refer to Appendix A: FSM Functions List, column F (Priority). This column indicates the priority level for each requirement of the FSM. The Option 3 ROM estimate should include ALL requirements regardless of priority level indicated on the Functions list.

Include an estimate for the length of time it may take to complete the work in the SOW utilizing option 3 including a brief description of your proposed timeline.

4) Option 4. Create a representation of the real world FSM without use of the existing GUI and software. Refer to Appendix A: FSM Functions List, column F (Priority). This column indicates the priority level for each requirement of the FSM. The Option 4 ROM estimate should include only those requirements listed as CRITICAL in the priority section of the functions list.

Include an estimate for the length of time it may take to complete the work in the SOW utilizing option 4 including a brief description of your proposed timeline.

*Please note, it is important to keep the appearance of FSM as close to the real thing as possible. Some of the functionalities may not be required, but the display or image should be the same just without being operational.

III. Traffic Situation Display (TSD)

The Traffic Situation Display (TSD) allows the traffic manager to graphically display the current position of all instrument flight rule (IFR) flights that are in the air. The TSD also displays the current status of alerts and weather, as well as map overlays such as sectors, fixes, NAVAIDs, and airports. The display allows traffic managers to make real time traffic management decisions. It is integrated within the Traffic Flow Management System (TFMS).

The TSD automatically refreshes the display with the most up to date flight positions and replays traffic situation data with alert and weather data. There are four ways to request data and control the way the data is displayed within the TSD: menus, dialog boxes, keyboard commands, and semicolon commands. (See section 4 Of the SOW.)

Please provide ROM Estimates for the following options that may be considered to complete the tasks specified in the SOW. Each estimate should be reported as a single number based on what the option describes. The FAA will consider the best option based off of the ROM estimates, the timeline, and the ability for the contractor to meet the requirements of the SOW using that particular option.

*If it becomes obvious that including all aspects of the functions list, regardless of priority, does not increase the overall total of the estimate drastically, vendors may provide estimates for only Options 1 and 3.

1) Option 1: Interfacing with the current TSD using the existing Graphic User Interface (GUI) and existing software. Refer to Appendix B: TSD Functions List, column F (Priority). This column indicates the priority level for each requirement of the TSD. The Option 1 ROM estimate should include ALL requirements regardless of priority level indicated on the Functions list.

Include an estimate for the length of time it may take to complete the work in the SOW utilizing option 1 including a brief description of your proposed timeline.

2) Option 2: Interfacing with the current TSD using the existing Graphic User Interface (GUI) and existing software. Refer to Appendix B: TSD Functions List, column F (Priority). This column indicates the priority level for each requirement of the TSD. The Option 2 ROM estimate should include only those requirements listed as CRITICAL in the priority section of the functions list.

Include an estimate for the length of time it may take to complete the work in the SOW utilizing option 2 including a brief description of your proposed timeline.

3) Option 3: Create a representation of the real world TSD without use of the existing GUI and software. Refer to Appendix B: TSD Functions List, column F (Priority). This column indicates the priority level for each requirement of the TSD. The Option 3 ROM estimate should include ALL requirements regardless of priority level indicated on the Functions list.

Include an estimate for the length of time it may take to complete the work in the SOW utilizing option 3 including a brief description of your proposed timeline.

4) Option 4. Create a representation of the real world TSD without use of the existing GUI and software. Refer to Appendix B: TSD Functions List, column F (Priority). This column indicates the priority level for each requirement of the FSM. The Option 4 ROM estimate should include only those requirements listed as CRITICAL in the priority section of the functions list.

Include an estimate for the length of time it may take to complete the work in the SOW utilizing option 4 including a brief description of your proposed timeline.

IV. Scenario Development

Please provide a ROM estimate for Terminal/SVRWX scenario development. Scenarios will be used for the FSM and TSD simulation platform. Please provide a rate for how much you estimate the cost of building a scenario. The FAA will determine how many scenarios are required and necessary based on the given rate estimates for development. See Appendix B: Terminal Scripted Simulation Example and Appendix D: Instructor Severe Weather Training Simulation DFW Weather Scenario in the SOW for a detailed description of scenarios.

*Seat hours for each scenario are not expected to exceed 1 hour. The intent is that each scenario should be able to be completed within an hour in class.

If a scenario covers a simulated time period longer than an hour, parts of it will be sped up. Trainees will be using the FSM and TSD long enough for live updates to occur. Simulation system updates should occur at the same time intervals as the live system. However, during running the scenario in the labs the time period that would normally occur in between implementing initiatives and thus between updates can be skipped/fast forwarded through. For example: updates occur, student reviews information, implements initiative, fast forwards to next update, reviews information, modifies or implements initiative, or simply decides to keep monitoring until next update, etc.

V. Additional Information

Refer to the SOW for details of the technical requirements when developing your ROM cost estimates.

The Contractor(s) should assume all items associated with completing the simulation platform as described in the SOW are their responsibility, and the ROM should reflect this.

Please be advised that the requestors are not warranted contracting officers and do not have the authority to obligate the government or government funds in any way; this request is for information-gathering purposes only to ensure that the government objectives for the SOW are met.

Appendix A

FSM Functions List

components from the Open With section to view the information.

Create, rename, and save a custom data set grouping in FSM (User Defined Groups - UDGs)

critical

critical

View Historical Pop-up Demand

GDP and be reflected in the GDT Setup)

component to model, issue, and send AFPs

• You cannot alter Data Time.

• You cannot include multiple instances of an element in a scenario.

• You cannot run Blanket or Compression TMIs.

• You cannot model AFPs before airports TMIs.

• AFP exemptions within a GDP are limited to existing AFPs.

• You cannot model re-controls in a purge.

• There is no support for Historical IPM mode.

critical

Actual

*Page refers to the page number in the Flight Schedule Monitor Users Guide.

Appendix B

TSD Functions List

Display Geographical Data

Display Geographical Data

Display Flight Data

Reroute

More to follow

Nice to have

Critical

Display flight departures by departure airport or departure fix

Nice to have

*Page refers to the page number in the TFMS Functional Description Guide.

References

Federal Aviation Administration. (2016). Traffic Management Applications. Flight Schedule Monitor User’s Guide. CSC Government Solutions LLC. A CSRA Company.