## Appendix A Excerpts from NASA TCL Statements of Work  
TCL1.  
The TSO (Test Site Operator) shall use NASA's UTM construct and/or initial system and procedures to demonstrate safe multi-vehicle operations in the vicinity. The UTM system will contain and display all constraints (real and simulated), which will include geofenced areas, severe wind/weather, ongoing operations, etc. The users shall connect to UTM, provide an operational plan, connect trajectories, and track the progress of trajectories. NASA will provide the UTM interface control document. The test shall conduct an initial demonstration test (shakedown test) that includes at least two vehicles operating for 30 minutes.  
TCL2.  
The TSO shall use NASA's UTM construct and procedures to demonstrate safe multi-vehicle operations sharing the same airspace. This airspace may be beyond visual line of sight of the operator and the operations may be altitude stratified. Airspace management procedures may include dynamic replanning, contingency implementation, and support of public safety vehicles, amongst others. These procedures will be detailed and provided by NASA, potentially finalized through collaboration with the TSO.  
In addition to the procedures outlined above NASA requests each test site to focus on one or more of the following areas:  
* UAS service supplier technologies and procedures,
* Geofencing technologies/conformance monitoring,
* Ground-based surveillance/sense and avoid,
* Airborne sense and avoid,
* Communication, navigation, and surveillance,
* Human factors related to UTM data creation and display.  
Flight testing will exercise the following functionality, which the TSO will ensure that tools and processes are in place to efficiently execute. Note that this list is non-exhaustive and may expand based on discussions between NASA and the TSO:  
* Altitude stratified operations,
* Altitude stratified BVLOS operations,
* Dynamic (en route) replanning,
* Response to alerts from the UTM system,
* Implementation of contingencies (e.g., sudden need for RTB).  
TCL3.  
The following test descriptions are provided to allow the TSO to effectively determine its ability to execute this task order and properly estimate resources. A TSO may select the subset of these tests that fit the TSO's resources and technical capabilities.  
The following tests are grouped into four areas:  
1. CNS: Communication, Navigation, and Surveillance,
2. SAA: Sense and Avoid,
3. DAT: Data and Information Exchange,
4. CON: Concepts.  
Specific objectives for these were identified in detail within the SoW and accompanying Concept of Operations (ConOps) document.  
* CNS1, Maintaining Control of UAS with Redundant C2,
* CNS2, Remaining Within Flight Geography Using GNSS Navigation,
* CNS3, RF Interference Baseline Monitoring,
* SAA1, Conflict Mitigation Cooperative Technology for UAS-UAS Interaction,
* SAA2, Conflict Mitigation Cooperative Technology for UAS-Manned Interaction,
* SAA3, Conflict Mitigation Non-Cooperative Technology for UAS-Manned Interaction,
* SAA4, Conflict Mitigation Non-Cooperative Technology for UAS-UAS Interaction,
* SAA5, System Level Assessment and Off-Nominal Conditions,
* SAA6, Remote Identification and Interoperability with Automobiles Using Cooperative Technology,
* DAT1, End-to-End UREP,
* DAT2, FIMS Failover,
* DAT3, USS Failover,
* DAT4, UAS ID,
* DAT5, USS-USS Negotiation,
* DAT6, Weather Service,
* CON1, BVLOS Landing,
* CON2, Contingency Initiation,
* CON3, Public Portal,
* CON4, Multiple Operations for Sustained Period,
* CON5, FIMS/USS Interaction to Mitigate Undesired UAS Behavior.