operational concept description (ocd) › ... › ocd_dcp_f20a_t02_v1.1.pdfocd_dcp_f20a_t02_v1.1 9...

Operational Concept Description (OCD)

Agricultural Drone

Team 2

Luis Cuellar Requirements Engineer, Life-Cycle Plan

Jeremy Donde

Operational Concept Engineer, Feasibility Analyst

Marjorie Lucas Operation Concept Engineer, Software Architect, Feasibility Analyst

Steven Prockup

Project Manager, Requirements Engineer, Life-Cycle Planner

Chenyu Wang Software Architect, Prototyper, IV&V

Sheng Zhang

Prototyper, IV&V

George Zhong Requirements Engineer, Prototyper, IV&V, Quality Focal Point

Oct. 23 2020

Operational Concept Description (OCD) – Team 2 – Agricultural Drone Version 1.1

OCD_DCP_F20a_T02_V1.1 Version Date: 10/23/2020 ii

Version History Date Author Version Changes made Rationale

10/20/2020 JD, ML 1.0 Initial release 10/22/2020 ML, GZ 1.1 • Business flow diagram

updates • Added stakeholder

description table

Updated to include comments from presentation.


OCD_DCP_F20a_T02_V1.1 OCD_DCP_F20a_T02_V1.1.docxVersion Date: 10/23/2020

iii

Table of Contents Operational Concept Description (OCD) .................................................................................................................... i Version History ............................................................................................................................................................. ii Table of Contents ........................................................................................................................................................ iii Table of Tables ............................................................................................................................................................ iv Table of Figures ............................................................................................................................................................ v 1. Introduction ........................................................................................................................................................... 1

1.1 Purpose of the OCD ................................................................................................................................. 1 1.2 Status of the OCD ..................................................................................................................................... 1

2. Shared Vision ......................................................................................................................................................... 2 2.1 Benefits Chain ........................................................................................................................................... 3 2.2 System Capability Description ................................................................................................................ 4 2.2 System Boundary and Environment ...................................................................................................... 4

3. System Transformation ........................................................................................................................................ 6 3.1 Information on Current System .............................................................................................................. 6 3.2 System Objectives, Constraints and Priorities ...................................................................................... 8 3.3 Proposed New Operational Concept .................................................................................................... 12 3.4 Organizational and Operational Implications ..................................................................................... 18


OCD_DCP_F20a_T02_V1.1 Version Date: 10/23/2020 iv

Table of Tables Table 1: The UAV-IQ Agricultural Drone program model ........................................................................................... 2 Table 2: Description of critical stakeholders ................................................................................................................. 4 Table 3 UAV-IQ list of artifacts from current system .................................................................................................... 6 Table 4: Operational Capability Goals for the UAV-IQ program ................................................................................. 8 Table 5: Level of Service Goals ..................................................................................................................................... 9 Table 6: Organizational Goals .................................................................................................................................... 10 Table 7: Constraints ..................................................................................................................................................... 11 Table 8: Relation to Current System ............................................................................................................................ 11


OCD_DCP_F20a_T02_V1.1 Version Date: 10/23/2020 v

Table of Figures Figure 1: Benefits Chain Diagram for UAV-IQ proposed solution ............................................................................... 3 Figure 2: System Boundary and Environment Diagram for the Agricultural Drone program ..................................... 5 Figure 3: UAV-IQ current workflow .............................................................................................................................. 7 Figure 4: Element Relationship Diagram .................................................................................................................... 13 Figure 5: Business Workflow Diagram of Flight Request Creation ............................................................................ 14 Figure 6: Business Workflow Diagram of Integrated Pest Management .................................................................... 15 Figure 7: Business Workflow Diagram of Weather Check .......................................................................................... 16 Figure 8: Business Workflow Diagram of Pilot Coordination .................................................................................... 16 Figure 9: Mission execution ......................................................................................................................................... 17


OCD_DCP_F20a_T02_V1.1 Version Date: 10/23/2020 1

1. Introduction

1.1 Purpose of the OCD This document provides, in detail, the shared visions and goals of the stakeholders of the Agricultural Drone Operations Management System for Unmanned Aerial Vehicle Intelligence (UAV-IQ). The success-critical stakeholders of the project are Andreas Neuman (UAV-IQ CEO), Mike Clark (UAV-IQ CTO) acting as the UAV-IQ Project Managers for the context of this document, the UAV-IQ customers (can be the grower/farmer, farm owner, property manager, or consultant), the drone pilots (UAV-IQ pilots or contractors), and the suppliers (company that supplies the product dropped by the drones).

1.2 Status of the OCD The status of the OCD is currently at the version number 1.1, prepared for release with the Foundations Commitment Review. This document reflects the current knowledge of the operations of the system and will be updated as the system evolves throughout the development phase. Changes were made between this version and the initial release to include the feedback from the FCR ARB and are limited to improvements to diagram readability.



2. Shared Vision

The program model defined in Table 1 lists the stakeholders of the program, what initiatives will be undertaken to realize the listed value propositions, and the beneficiaries of these value propositions. Also listed are the assumptions under which the program will operate. The stakeholders were identified through conversations with UAV-IQ and through examination of UAV-IQ’s existing workflow. Users who interact with the existing workflow and UAV-IQ management have a vested interest in the new, integrated workflow and have therefore been listed as stakeholders. The initiatives were largely derived from the biggest pain points of UAV-IQ’s existing workflow, as identified by UAV-IQ. The value propositions are the benefits derived from the proposed solution through the initiatives and resolve the pain points from which the initiatives were derived.

Table 1: The UAV-IQ Agricultural Drone program model

Assumptions Stakeholders have mobile and/or desktop devices

Stakeholder devices have ability to connect to the internet

Stakeholders Initiatives Value Propositions Beneficiaries

• Project Manager • Drone Pilot • UAV-IQ

Customer • Supplier

• Create integrated, web-based workflow

• Trigger notifications based on predefined parameters

• Customize access based on user type

• Simplify customer request workflow

• Implement on scalable platform

• Reduce time spent on project administration

• Increase workflow robustness

• Improve user experience

• Centralize project communication

• Project Manager • Drone Pilot • UAV-IQ

Customer • Supplier



2.1 Benefits Chain The benefits chain diagram, shown in Figure 1, demonstrates the initiatives that will provide value to the proposed integrated workflow. Each initiative is executed by a primary stakeholder and generates a concrete benefit when realized. The critical stakeholders who execute these initiatives are defined in Table 2. Each initiative reduces to one of four, core benefits that drove the design of the integrated workflow. Notifications to all stakeholders are routed through the integrated workflow, creating centralized communication. This standardizes and simplifies communication, improving the user experience. Improved user experience reduces the time spent managing projects, which then allows project managers to focus more on long-term activities such as expansion of market and customer base.



Figure 1: Benefits Chain Diagram for UAV-IQ proposed solution

Table 2: Description of critical stakeholders

Stakeholder Description Project/Mission Manager Manages the projects Drone Pilot Flies the drone and administers the crop treatment Supplier Supplies UAV-IQ with the payload for crop treatment Customer/UAV-IQ Customer/Grower Person or organization who requests UAV-IQ services

2.2 System Capability Description

The UAV-IQ integrated workflow for precision agriculture offers a platform for mission management from customer request through post-flight operations that streamlines planning and execution. Users can use this platform as a “one stop shop” for communicating between



customers, pilots, and suppliers; receiving and sending customizable notifications; and tracking project status. Precision agriculture seeks to leverage existing technologies to yield greater crop production for fewer resources. Farmers and growers are looking for ways to more efficiently manage pest control without relying on pesticides. There is greater emphasis on renewable and environmentally-conscious farming from both a political and societal perspective, creating a market for organizations such as UAV-IQ to offer aerial biocontrol solutions. Since this is an emerging market, there are no integrated solutions on the market. Existing solutions are manually intensive, lack robustness, and have disjointed processes, making them inefficient and difficult to manage. This solution addresses these shortcomings and offers an exciting opportunity for market edge.

2.2 System Boundary and Environment The system boundary and environment diagram, shown in Figure 2, defines both the list of services the Agricultural Drone project team will develop and deliver, as well as the boundary of the system and its interfaces to the stakeholders and external systems. On the left of the diagram below, the stakeholders are listed showing the UAV-IQ Customers, UAV-IQ Project Managers, Drone Pilots, Suppliers all interfacing to the services provided by the system in the top box. The Maintainer is the only stakeholder to interact with the support infrastructure shown in the bottom box at the time of deployment. On the top right of the diagram, the list of APIs shows how the system will both retrieve mission planning data and register flights.

The system will have no hardware of its own and will utilize cloud storage and application hosting. The primary software technologies in use will be React Native for front end development, a relational SQL database for information storage and access, and the Django Template language for backend development. The system will also interface with the existing UAV-IQ website for integration with the existing infrastructure.



Figure 2: System Boundary and Environment Diagram for the Agricultural Drone program



3. System Transformation

3.1 Information on Current System

3.1.1 Infrastructure The infrastructure currently in use at UAV-IQ for managing orders and missions is limited, as the primary workflows are manual. The current system uses a combination of google forms for creating orders and manually organized google drive storage for current and past missions. The external websites used to gather mission planning data, such as AirMaps and Weather Underground, are accessed manually and screen shots are taken to save the information to the mission folder on google drive. G-Suite applications are used to create and edit documents for saving notes, generating quotes and other mission information. There is no hardware or software representing the current system besides company laptops and mobile devices to access the cloud storage and various websites.

3.1.2 Artifacts Table 3Table 3 below lists the artifacts used by the current system and its users to manage UAV-IQ drone operations.

Table 3 UAV-IQ list of artifacts from current system

Artifact Description

UAV-IQ Website Main website used by UAV-IQ to advertise their product and take preliminary order requests.

G-Suite Provides cloud storage for mission data and orders, web applications for creating and modifying documents, managing UAV-IQ calendar

Google Earth Used to create boundaries, check drone no-fly areas

AirNav Used to research airports and other airspace concerns



MyGeoData.cloud Used to transform application zone file to GeoJSON

AirMaps Used to create missions, document pilot info, check for airspace issues, submit flight plans, and check for needed approvals

FAA Drone Zone File airspace requests

UcGS Desktop Client Used to create individual routes within a mission

Weather Underground Used for pre-mission weather checks

3.1.3 Current Business Workflow Figure 3 below shows the current business workflow of managing UAV-IQ drone operations as provided by UAV-IQ.

Figure 3: UAV-IQ current workflow



3.2 System Objectives, Constraints and Priorities

3.2.1 Capability Goals

The operational capability goals are listed in Table 4. Each of these goals describes an action or a set of actions system users will be able to perform on the proposed system. Each capability goal may also be broken into smaller components which will map back to at least one win condition. OC-1 through OC-7 must be met for the program to be successful; OC-8 and OC-9 are not necessary for project success, however, they are capabilities UAV-IQ has expressed an interest in having.

Table 4: Operational Capability Goals for the UAV-IQ program

ID Capability Description Priority

OC-1 Application Zone Definition

Customers and UAV-IQ Project Managers have the ability to create boundaries on a map to clearly indicate where the product(s) should be dispersed from within the web application. See WC-187, WC-188, WC-189.

Must Have

OC-2 Integrated Customer Onboarding

Integrated Customer Onboarding allows for the use of existing projects to create new missions, based on the users or locations order history. See WC-191.

Must Have

OC-3 Project Tracking

All project and mission information will be tracked and visible through the web applications dashboard or a project specific dashboard. See WC-192, WC-201, WC-198.

Must Have

OC-4 Flight Conditions Discovery

Automated flight condition discovery integrates information from multiple APIs to determine if the application zone is a safe area for a drone flight. See WC-194, WC-208.

Must Have

OC-5 Automated Notification

All stakeholders will be able to customize notifications and monitor go/no-go conditions. Project Managers can define go/no-go conditions. See WC-195, WC-197, WC-200, WC-208

Must Have

OC-6 Flight Operations

To gather as much data as possible the web application will allow the drone pilots the ability to upload DJI formatted logs, as well as safety information and other flight notes. See WC-207, WC-202, WC-207.

Must Have



OC-7 Permissions Management

This will allow Project Managers to change the permissions of existing customers so they can associate old orders with new Customers. See WC-190, WC-199.

Must Have

OC-8 Procurement Project managers can place orders to suppliers through the web application. See WC-193.

Nice to Have

OC-9 Generate Quotes

The internal quotes will be a simple formula based on area to be covered and products used. See WC-196.

Nice to Have

3.2.2 Level of Service Goals Table 5 below lists the level of service goals for the system and their priority level. These were derived through interactions with UAV-IQ and understanding what expectations they have for the performance and availability of the integrated workflow. The solution must be accessible through mobile and desktop platforms to support stakeholder use cases. Some capabilities may be limited on mobile as mobile users are not expected to exercise all solution capabilities. The average response time for database or API queries should be minimized so there is no discernable delay to users interacting with the system. The solution should be up and accessible at all times with an exception for deployments or maintenance.

Table 5: Level of Service Goals

Level of Service Goals Priority Level

Referred Win-Win Agreements

LOS-1: Cross platform support (Mobile and Desktop support)

Must Have WC-198

LOS-2: Average response time below 500ms Nice to Have NA

LOS-3: Solution down time below



3.2.3 Organizational Goals The organizational goals describe a high-level objective that may be gained through use of the proposed solution. Each of the organizational goals defined in Table 6 satisfy at least one value proposition defined in Section 2.

Table 6: Organizational Goals

Value Proposition Organizational Goals Reduce time spent on project administration

OG-1: Reduce time spent on administration by providing project tracking functionality.

OG-2: Reduce time spent on administration by automating work- order creation.

Increase workflow robustness

OG-3: Increase robustness by standardizing application zone input. OG-4: Improve security by defining user-type access roles. OG-5: Increase robustness by standardizing flight artifacts uploads. Centralize project communication

OG-6: Improve communication by creating a centralized notification system.

OG-7: Improve notification by customizing parameters that define Go/No-Go conditions.

Improve user experience

OG-8: Improve operational management by centralizing API calls. OG-9: Increase customer participation by providing an intuitive

way to enter application zone definition.

3.2.4 Constraints The constraints placed on the UAV-IQ proposed solution were derived from conversations with UAV-IQ. These represent conditions that must be met in the proposed solution. The constraints and their rationale are outlined in Table 7.



Table 7: Constraints

Constraint Rationale CO-1: Mobile and Desktop Access: The solution must be accessible to mobile and desktop users.

Users may be in an office setting or out in the field so they need the ability to access the solution from different devices.

CO-2: Web-Based: The solution must be accessible remotely.

Users need to access the solution remotely as some may need to access project materials in the field.

CO-3: Website Integration: The solution should integrate with the existing UAV-IQ website.

The existing website is the landing page potential customers are brought to. This is the entry point to the proposed solution’s dashboard.

3.2.5 Relation to Current System The relationship between the old system and the proposed system is summarized in Table 8. The roles, responsibilities, and user interactions are largely similar, with the changes in these capabilities a result of adapting to the new infrastructure. The infrastructure in the proposed system will differ from that of the old system as it will be hosted on AWS.

Table 8: Relation to Current System

Capabilities Current System New System

Roles and Responsibilities

Project Manager (PM) • Creates project from UAV-IQ client request

• Manually assesses application zone for nearby points of interest and adverse weather conditions

• Creates project from UAV-IQ client request initiated outside UAV-IQ website

• Define parameters to search for points of interest or be notified of adverse weather conditions

UAV-IQ Customer • Requests crop treatment over application zone

• Requests crop treatment over application zone

Drone Pilot • Retrieves project flight plan • Provides flight logs

• Retrieves flight plan from the UAV-IQ website

• Provides flight logs UAV-IQ Supplier • Supplies product • Supplies product

User Interactions Project Manager (PM) • Creates project from UAV-IQ

client request received via email, text, phone, or web form

• Receives notification that project was automatically created based on UAV-IQ client request through the UAV-IQ website



• Searches application zone for nearby points of interest using 3rd party software

• Determines weather conditions using weather-reporting website

• Sets parameters to search for points of interest over a given application zone and automatically notify team of relevant weather information

UAV-IQ Customer • Submits form from the UAV-IQ website requesting crop treatment.

• Sends KML/geoJSON defining application zone to PM

• Submits form from the UAV-IQ website requesting crop treatment and provides the KML/geoJSON as part of this request.

Drone Pilot • Retrieves flight plan from PM or AirMaps

• Sends a flight log to PM

• Downloads flight plan from UAV-IQ website

• Uploads flight log to relevant project on UAV-IQ website

UAV-IQ Supplier • Receives email notifications requesting product

• Receives email notifications requesting product

Infrastructure Software • GSuite, GoogleMaps, various

API’s • AWS, GSuite, GoogleMaps,

various API’s Hardware • Personal computers • Personal computers Personnel • PM, drone pilot, supplier,

UAV-IQ customer • PM, drone pilot, supplier,

UAV-IQ customer Stakeholder Essentials and Amenities

• Must centralize communication • Must be scalable • Must provide project tracking

capabilities Future Capabilities • Machine learning applications

to flight data • Machine learning applications

to flight data

3.3 Proposed New Operational Concept This section contains information about the transformation of the new operational concept that will be introduced to the system.

3.3.1 Element Relationship Diagram

The element relationship diagram in Figure 4 shows the primary relationships between the elements of the proposed new system and the external entities. The elements that belong to the proposed solution are defined in the box with the dotted border and the elements that are outside



the system, but interact with it, are defined outside the dotted box. The external elements include the actors and the API’s; the internal elements include the AWS virtual machine that will host the solution and the PostgreSQL database that will store the solution data.

Figure 4: Element Relationship Diagram

3.3.2 Business Workflows The following series of diagrams illustrate the new business workflows of the system. Starting with the Flight Request Creation in Figure 5, the customer will start the process by filling in the flight request information and drawing the boundary on the provided map if it is a new location. Using these inputs, the application will be able to create a new project, or load data from an existing project to expedite the process. Once the project is created, the application will access data from airspace APIs to determine if the area is safe to fly. If the mission is accepted by the UAV-IQ management team, the system will store all information required and move the project into the next phase.



Figure 5: Business Workflow Diagram of Flight Request Creation

Figure 6 below shows the workflow of the integrated pest management process, where the customer has the option of requesting help developing an application plan. This will trigger a notification to the UAV-IQ entomologist to initiate the planning and quotation process. Once this plan is worked out and agreed to, information can be added to the project in the system and the project moved into the next phase.



Figure 6: Business Workflow Diagram of Integrated Pest Management

Continuing on to the monitoring phase in Figure 7, the system will automatically check for weather updates and send notifications to the stakeholders if the weather violates a no-go condition. These weather updates may be provided anywhere between ten days to one day before the mission is expected to deliver the crop treatment, depending on the location of the project or the discretion of the stakeholders. If there are no issues, the stakeholders can confirm the mission is a go, and the mission will proceed into the next phase. If there are concerns regarding the weather, the UAV-IQ customers will be notified and an attempt to reschedule the mission will be made. This may include notifying the supplier to determine whether the crop treatment shipment may be delayed long enough until weather conditions improve. If the mission cannot be rescheduled, the project will be archived.



Figure 7: Business Workflow Diagram of Weather Check

Figure 8: Business Workflow Diagram of Pilot Coordination



Figure 8 illustrates the pilot coordination workflow where the UAV-IQ team can assign pilots and the pilots can interact with the system to accept the mission and upload license and insurance information. If the pilots are available, they must upload their drone licenses and insurance if not already on file. UAV-IQ management will then verify the documents are valid before assigning the mission to the pilots. Once confirmed by UAV-IQ, the pilot will receive a notification that they have been assigned.

Figure 9: Mission execution



The workflow in Figure 9 depicts the day of mission execution. The application will send reminder notifications to the customer and the drone pilot, where they can re-confirm all mission information prior to flight. Upon mission completion, the drone pilot will be notified to upload flight logs, safety notes and any additional information. Additionally, the customer will be notified to upload a review. Once each step is completed by the stakeholders, UAV-IQ is notified of the completed mission.

3.4 Organizational and Operational Implications

3.4.1 Organizational Transformations There are no major organizational changes for our stakeholders to use our solution. At the time of deployment, a system maintainer will be required to take care of the system and perform upgrades beyond the initial delivery. The system maintainer can be an existing employee or new hire, and this has been concurred with by the UAV-IQ CEO and CTO.

3.4.2 Operational Transformations

Significant changes to operational procedures and workflows will be required to integrate our solution into day to day operations. The bulleted list below describes the operational changes and their impact to stakeholders:

• Customer ordering will transition from a google form to our new web application ordering. This will impact UAV-IQ project managers and UAV-IQ Customers. While the project managers are requesting this change, it will need to be rolled out to the existing customers and require training.

• Mission creation will no longer be manual, and all files and folders will be created from within our web application. This change is concurred with by UAV-IQ Project Managers.

• Airspace information retrieval will be automated using APIs instead of manually accessing websites, this information will be stored with the project folder. This change is concurred with by UAV-IQ Project Managers.

• Notifications will be automatically delivered to all stakeholders, with the ability to modify their settings. This change is concurred with by UAV-IQ Project Managers.

• All drone operations management will be done using the new web application, instead of interfacing manually with G-Suite. This change is concurred with by UAV-IQ Project Managers.

operational concept description (ocd) › ... › ocd_dcp_f20a_t02_v1.1.pdfocd_dcp_f20a_t02_v1.1 9...

Documents