nasa / utm-apis

The collection of APIs for NASA's UTM project in the form of OpenAPI documents.
55 stars 35 forks source link

Update ContingencyPlan per C+N Working Group #125

Closed nasajoey closed 5 years ago

nasajoey commented 5 years ago

The C+N working group has developed some improvements to the contingency plan model.

Here some some notes that were provided by that working group:

Use of ContingencyPlan Data Model for Safe Landing To support safe landing of UA, the followings are requested to USS developers.

  • Require operator to submit ContingencyPlan to USS (i.e., completed ContingencyPlan is a prerequisite for activating operation. v4 data model is shown in Table 1).
  • In ContingencyPlan, change the followings into mandatory data elements (i.e., operator must submit these information). -- contingency_point -- contingency_location_description -- valid_time_begin -- valid_time_end
  • Change "contingency_point" to polygon.
  • Change "contingency_location_description" to enum with the following values. [PRE_PROGRAMMED, OPERATOR_UPDATED, UA_IDENTIFIED, OTHER]. PRE_PROGRAMMED indicates location that is programed to UA prior to launch, OPERATOR_UPDATED indicates location that is updated during operation by operator (e.g., sent to UA), UA_IDENTIFIED indicates location that is identified to be safe to land by UA, and OTHER indicates location that belongs to none of the previous three categories. For research purpose, when UA lands at a position outside of contingency_point polygon designated as PRE_PROGRAMMED, OPERATOR_UPDATED, or UA_IDENTIFIED, this landing will be considered unsafe.

Implementing the above listed requests should enable USS to facilitate safe landing, especially in TCL4 environment where a limited safe to land locations may exist due to urban area layout (e.g., densely packed houses and buildings) and movement of people and property in the area. For example, Local USS Network can strategically de-conflict safe landing plans so that multiple UA will not attempt to land at the same location at the same time. In addition, use of ContingencyPlan data model as suggested will play a critical role in the discussion about off-nominal situations management and implementation of associated requirements. Table 2 shows these requirements and justifications as a reference.

nasajoey commented 5 years ago

Will close. Fixes/improvements should be a new issue.