SOW Musts Cheeklist.pdf

PROCUREMENT SENSITIVE

FOR OFFICIAL USE ONLY 16

Phase 1: Technical Evaluation SOW “Musts” Checklist

Sect/ para #

Page # "Must" Statement Go/No Go

1 1.3 5 The contractor must demonstrate experience in the design and development of a high fidelity interactive simulation platform that allows for scenario development by instructors.

2 1.3 5 The contractor must demonstrate the aforementioned by providing evidence that their organization has previously constructed an air traffic control simulator, similar to that described in this SOW.

3 1.3 5 The simulation platform must be cloud-based such that trainees can access the simulation without specialized hardware.

4 1.3 5 Delivery must also include simulation of ten traffic scenarios (five for SVRWX and five for Terminal).

5 1.3 5

Scenarios and simulation fidelity must closely replicate the Graphical User Interface (GUI), display, and functionality of the FAA’s TSD and FSM. The FSM and TSD functions that must be simulated are listed in Appendices C and D of the SOW (Pg. 26-33)

6 1.3 5 The simulation platform must allow ATCSCC instructors to script training scenarios using archival data that can be fully independently by the instructors.

7 1.3 5

The simulator must enable scripted scenarios to allow both the SVRWX trainee and the Terminal trainee to interact with the simulated scenario and to see results of the decisions trainees make and the way in which the decisions were implemented.

8 1.3 4 Simulated traffic must respond to initiatives in a realistic fashion in real time and fast time modes.

9 1.3 5

The simulation platform must enable the SVRWX trainee to use simulated TSD weather and Traffic Flow Management Convective Forecast (TCF) to determine the most efficient use of airspace then build/send playbook and ad-hoc reroutes.

10 1.3 5 The simulation platform must enable the Terminal trainee the ability to model and send GDPs/GSs using manually constructed airport demand via the simulated interface.

11 1.3 5 The server for the cloud-based platform must reside at ATCSCC facilities in Warrenton Virginia and must be able to hold at least 500 scenarios.

FOR OFFICIAL USE ONLY 17

12 1.3 6

The simulator must record number of aircraft impacted by trainee initiatives, average delay per aircraft in minutes, and average distance per aircraft from original route. These metrics for a scenario must be made available to the instructor and trainee at the end of the scenario

13 1.3 6

The platform should also allow the instructor to provide text that will be displayed to the trainee at the end of a scenario for the purpose of allowing the student to compare their scenario response choices with other viable responses.

1.3.1 5 The contractor must provide the following labor support:

14 1.3.1 5

(a) This acquisition requires an experienced vendor familiar with ATCSCC operations, Traffic Management policies, procedures, TSD, and FSM equipment. The vendor should have at least one Subject Matter Expert (SME) on staff with TMC experience.

15 1.3.1 6

(b) This acquisition requires an experienced vendor familiar with simulation of air traffic situation displays.

16 1.3.1 6

(c) This acquisition requires an experienced vendor familiar with creating cloud-based applications.

1.3.2 6 The contractor must be required to provide the following technical support services:

17 1.3.2 6

(a) FSM Simulation– The vendor must provide a high fidelity simulation of the FAA’s FSM. The FSM functions required to be simulated are described and listed in section 3 and Appendix C.

18 1.3.2 6

(b) TSD Simulation– The vendor must provide a high fidelity simulation of the FAA’s TSD. The TSD functions required to be simulated are described and listed in section 4 and Appendix D.

19 1.3.2 6

(c) Integration with FSM and TSD GUIs – The vendor provided simulator must integrate with, display, and take input from, the GUI of the current FSM/TSD system.

20 1.3.2 6

(d) API – the vendor must provide an application programming interface or gateway to facilitate integration with future systems that provide the TSD and FSM functions in Appendices C and D.

21 1.3.2 6

(e) Interactive Simulation Capabilities – The vendor provided FSM and TSD simulations must be interactive such that ATCSCC and TMU trainees can model, send, and modify playbook and TSD reroutes and GDPs and GSs.

22 1.3.2 7

(f) Realistic Traffic Behavior - Simulated traffic must respond to initiatives in a realistic fashion in real time and fast time modes.

FOR OFFICIAL USE ONLY 18

23 1.3.2 7

(g) Performance Data Collection – The vendor provided simulation platform must record number of aircraft impacted by trainee initiatives, average delay per aircraft in minutes, and average distance per aircraft from original route for each scenario run. The trainee identity and recorded data must be clearly related and these must be easily accessible by the trainee and instructor for each trainee once each scenario is completed.

24 1.3.2 7

(h) Scenario Development – The vendor provided FSM and TSD simulation platform must incorporate the ability for ATCSCC instructors to script and fully manipulate SVRWX and Terminal scenarios including scripted responses from airlines and ATC facilities

25 1.3.2 7

(i) Archival Data - The simulation platform must allow ATCSCC instructors to script training scenarios using archival traffic data that can be fully manipulated by the instructors during scenario development.

26 1.3.2 7

(j) Scenario Scripting – The vendor provided FSM and TSD simulation platform must incorporate the ability for ATCSCC instructors to script responses from airlines and ATC facilities to occur during the scenarios.

26 1.3.2 7

(k) Scenario Feedback – The vendor provided FSM and TSD simulation platform must incorporate the ability for ATCSCC instructors to specify under what circumstance, during a scenario, trainees will receive feedback and what the content of the feedback will be.

27 1.3.2 7

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

28 1.3.2 7

(m) The vendor must provide simulations of five Terminal (see Appendix A in the SOW) and five SVRWX (See Appendix B in the SOW) scenarios that will enable the evaluation of the simulation platform.

29 1.3.2 7

(n) Weather Requirements - The minimum functions for weather requirements are:

• The FSM/TSD training platform must allow instructors to create scenarios from historical weather data

• Must have the ability to load and manipulate historical weather data for use in the scenarios

• Must be able to create high fidelity simulations of weather from scratch including depictions of the weather data on the TSD

30 1.3.2 7

(o) Cloud-Based Access – The vendor provided simulations must be cloud-based, available from inside the FAA network, such that trainees can access the simulation without specialized hardware.

31 1.3.2 7

(p) Location - The simulation capability must reside on servers at the ATCSCC in Warrenton VA or at an approved FAA data center.

32 1.3.2 7

(q) Cloud-Based server - Vendor must provide the specifications for what cloud-based platform they are using for government approval.

FOR OFFICIAL USE ONLY 19

1.3.3 8 Contractor must provide training to a minimum of 10 ATCSCC, CAMI and TMU personnel in the following areas:

1.3.3 8 (a) Operation/functionality of the simulator

1.3.3 8 (b) Inputting and exporting data to and from the simulator

1.3.3 8 (c) Outputting performance metrics from the simulator

1.3.3 8

(d) Scenario development using the newly developed simulation platform and taking into account the example scenarios provided in this

SOW

1.3.4 8 The vendor must provide documentation (text and images in pdf format) for operation of the training platform in the following areas

1.3.4 8 (a) Operation/functionality of the simulator

1.3.4 8 (b) Inputting and exporting data to and from the simulator

1.3.4 8 (c) Outputting performance metrics from the simulator

1.3.4 8

(d) Scenario development using the newly developed simulation platform and taking into account the example scenarios provided in this

SOW

2 8 Deliverables

2.1.1 8 Technical Project Kickoff

2.1.1 8

(a) The vendor must participate in a project kickoff meeting with ATCSCC management and the training department at the campus located in Warrenton, VA or through an approved virtual meeting platform.

FOR OFFICIAL USE ONLY 20

2.1.1 8 (b)The vendor must provide a draft Project Management Plan (PMP) and Integrated Master Schedule (IMS) within 10 days of technical project kickoff meeting.

2.1.2 8 Analysis

2.1.2 8 (a)The vendor must provide a draft analysis report detailing the findings of the GFI.

2.1.2 9 (b)The vendor must incorporate AJR-11 feedback on the draft analysis report and provide a final analysis report for AJR-11 acceptance and approval.

2.1.3 9 Design

2.1.3 9 (a)The vendor must draft and deliver a Simulation Design Guide that describes, at a minimum, the simulation platforms, Terminal/SVRWX scenarios, and any assessment/evaluation tool.

2.1.3 9

(b) The vendor must not begin Development tasks until directed by AJR- 11 or before receiving AJR-11 acceptance and approval of the final Simulation Design Guide.

2.1.4 9 Development

2.1.4 9

(a) The vendor must develop and deliver the simulation platform for AJR-11 review and comment via errata sheets.

2.1.4 9

(b) The vendor must solicit and track AJR-11’s comments and feedback via errata sheets and incorporate changes until training materials are finalized and accepted.

2.1.5 9 Validation

2.1.5 9

(a) The vendor must ensure the simulator is ready for validation according to FAA standards and policies before scheduled validation events.

2.1.5 9

(b) The vendor must participate in all AJR-11 validation events as requested. Validation events include Course Walk-Through (CWT), and First Course Conduct (FCC) for both TSD and FSM simulation. Vendor must make course modifications based on input from the validation meetings. Vendor must participate in all validation events.

2.1.5 9

(c) The vendor must capture AJR-11’s feedback via an errata sheet and make requested revisions after each validation event.

2.1.5 9

(d) The vendor must submit final simulation platforms and materials for AJR-11 final acceptance and approval.

FOR OFFICIAL USE ONLY 21

2.1.5 9

(e) The vendor must capture meeting notes from all meetings and provide notes to the FAA.

2.1.16 9 Task List

2.1.6 9 Technical Project Kickoff Meeting: The vendor must participate in a project kickoff meeting with ATCSCC management and the training department

2.1.6 8 Draft Project Management Plan and Integrated Master Schedule: The vendor must provide a draft Project Management Plan (PMP) and Integrated Master Schedule (IMS).

2.1.6 8 Project Management Plan and Integrated Master Schedule - The vendor must incorporate AJR-11 feedback into the draft PMP and IMS to present a final plan and schedule.

2.1.6 8 Draft Analysis Report - GFI Materials: Vendor must review all GFI materials and provide a draft analysis report (detailed in section 2.1.2 of this SOW).

2.1.6 8 Final Analysis Report - GFI Materials: Vendor must incorporate AJR-11 feedback into the draft analysis to present a final analysis report for acceptance and approval

2.1.6 10 Monthly Status Report (MSR): contractor must submit a detailed monthly and cumulative breakdown of funds expended and status for each major assigned task.

2.1.6 10 Simulation Design Guide: Vendor must draft and deliver a Simulation Design Guide. (Detailed in section 5.1.3 of this SOW).

2.1.6 10 Development of the simulation platform (First attempt for AJR-11 Feedback): The vendor must develop and deliver the simulation platform for AJR-11's comments and feedback via errata sheets.

2.1.6 10

Draft Instruction Manuals: The vendor must develop and deliver a draft set of instructions for operating the FSM and TSD simulations, inputting and exporting data from the simulators, and creating scenarios for the simulators.

2.1.6 10 Development of the simulation platform: The vendor must submit the final version of the simulation platforms and scenarios for approval from

AJR-11

FOR OFFICIAL USE ONLY 22

2.1.6 10

Instruction Manuals: The vendor must develop and deliver instruction manuals for operating the FSM and TSD simulations, inputting and exporting data from the simulators, and creating scenarios for the simulators. These manuals must incorporate feedback from AJR-11.

2.1.6 10 Simulation Validation: The vendor must participate in all AJR-11 validation events (Detailed in section 5.1.5 of this SOW)

2.1.6 10 Project Schedules: The vendor must submit project schedules as required by AJR-11 and the COR. The Project Schedules must be accurate, complete, and submitted on time in the COR approved format.

2.1.6 10

Software/ Database, including corrections, enhancements, and modifications: The vendor must submit software requirements to AJR- 11 for approval prior to moving forward with contract tasks.

Software/Database including corrections, enhancements, and modifications must meet the requirements provided in the SOW

2.1.6 10

Hardware: The vendor must ensure that all hardware requirements meet FAA regulations (If hardware is necessary to meet the SOW requirements) All hardware must be approved by AJR-11 prior to installation. The timeline for any necessary hardware installation must be established at the start of the contract by the CO, COR, CAMI, AJR- 11 and the contractor. All hardware must meet the requirements indicated in the SOW.

2.2 10 Task Schedule

2.2 11

(a) Within 10 business days of contract award - The vendor must participate in a project kickoff meeting with ATCSCC management and the training department.

2.2 11

(b) Within 10 business days of the technical project kickoff meeting – The vendor must provide a draft Project Management Plan (PMP) and Integrated Master Schedule (IMS).

2.2 11

(c) Within 10 business days of receiving AJR-11 feedback – The vendor must provide a final draft of the PMP and IMS incorporating all feedback from AJR-11.

2.2 11

(d) Within 25 business days of technical project kickoff meeting – The vendor must review all GFI materials and provide a draft analysis report (detailed in section 2.1.2 of this SOW)

FOR OFFICIAL USE ONLY 23

2.2 11

(e) Within 10 business days of receiving AJR-11 feedback – The vendor must incorporate AJR-11 feedback into the draft analysis to present a final analysis report for acceptance and approval.

2.2 11

(f) Within 70 business days of contract award – The vendor must draft and deliver a Simulation Design Guide. (Detailed in section 5.1.3 of this

SOW).

2.2 11

(g) Within 130 business days of contract award - The vendor must develop and deliver the simulation platform for AJR-11's comments and feedback via errata sheets.

2.2 11

(h) Within 130 business days of contract award - The vendor must develop and deliver a draft set of instructions for operating the FSM and

TSD

2.2 11

(i) Within 260 business days of contract award - The vendor must submit the final version of the simulation platform for approval from

AJR-11.

2.2 11

(j) Within 260 business days of contract award - The vendor must provide the final instruction manuals for operating the FSM and TSD simulations, inputting and exporting data from the simulators, and creating scenarios for the simulators. These manuals must incorporate feedback from AJR-11 and be in pdf format.

2.2 11

(k) Within TBD days of contract award - The vendor must participate in all AJR-11 validation events (Detailed in section 5.1.5 of this SOW).

6.1 14 Computer Program Deliverables

6.1 14 While it is expected that the contractor may copyright most or all of its own proprietary software, the contractor must give the Government an unlimited license to use and modify the software as required.

6.2 14

Cloud Based Deliverables: The cloud-based platform required for this statement of work must be accessible using a Microsoft Windows 10 computer via a desktop application that connects to a cloud based server. No special hardware should be required for access. The server must be located at the ATCSCC in Warrenton VA or at an approved FAA data center.

6.3 14 Software: Deliverables must include any necessary source code and libraries or object files needed to build the executable modules.

6.3 14 Any Commercial Off-The-Shelf (COTS) software delivered as part of the tasking must include all licenses and access rights necessary to accomplish the tasking.

FOR OFFICIAL USE ONLY 24

6.5 14 The Contractor must provide the hardware necessary to carry out tasks associated with this contract.

6.7 15 All work schedules must be coordinated with the Government Task Order Technical Manager.

6.8 15 All travel must have prior authorization of the COR or Contracting Officer.

6.8 15 All travel must be accomplished in accordance with Contract Travel Clause(s) and in accordance with Government Travel Regulations.

6.9 15 Contractor must provide all workspace, equipment, software, office supplies, and related services necessary to perform assigned tasks for work performed at the contractor's facility.

6.1 15 The program manager or project lead must be required to meet, at the discretion of the CO or COR, with the CO or COR at any time during the term of any identified task.

7.1 16 The Contractor must be responsible for safeguarding all Government property for contractor use. At the close of each work period, Government facilities, equipment, and materials must be secured.

7.2 16

In the event the contractor deems overtime necessary to meet work requirements, the contractor must submit a written request to the CO or COR for authorization of use of overtime and the payment of overtime.

The request must identify in detail what service requires overtime, how many work-hours are required, and for what segment of the organization, the work is being performed.

7.3 16 Contractor must normally not be required or allowed to work when their assigned facility is on holiday or closed.

7.4 17

Contractor personnel when on FAA facilities must be issued a contractor identification card identifying them as a contractor employee.

The identification cards must be worn while performing services under this contract.

7.5 17 While contractor personnel are at the Government site, they must comply with all rules and regulations in effect at that site.

7.5 17

Contractor personnel must comply with rules and regulations governing employee conduct with respect to health and safety, not only as they relate to themselves, but also to other Government employees or agents of the Government.

7.5 17 The contractor must also exercise proper care of all property at the Government site regardless of whether title to such vests with the Government or not.

FOR OFFICIAL USE ONLY 25

7.6 17 All applicable FAA Orders and FAA Acquisition Management System (AMS) policies, guidelines and processes must be used.

7.6 17 The Contractor must research and employ appropriate FAA Orders, where necessary, under the guidance of the Contracting Officer’s Representative (COR).

7.6 17 The Contractor must ensure all work is in full compliance with:

7.6 17 FAA standards and guidelines

7.6 17 CAMI policies, regulations, directives and procedures

7.6 17 FAA AMS guidelines

7.7 17 The contractor must develop a quality control plan to assure that development of the simulator provided under this contract meets industry standards.