Team: Whirlybird System: Adaptive Multi-Rotor UAV Platform Descriptive Statement The Adaptive Multi-Rotor UAV platform allows for multiple tasks to be performed with one system for a reasonable price. The platform features re-configurable HW and SW that enables the user to quickly respond to task changes. The platform is adaptable so that it can operate in many environments. This allows the platform to be used for commercial aspects such as farming, as well as military aspects such as surveillance. Strategic Values/Objectives Field Configurable User Friendly Secure Good Value High Utilization Multi-Task Capable Team members: Bryan Dallas, Swadha Mahabaleshwarkar, Adam Ringer, Elliot Rivers

CURVE High-Level System/Process Environment Consider both reactive threats & proactive opportunities to seize, within mission Caprice: unknowable situations Users might not pay attention or decided to do unknown tasks (reactive) New technologies (proactive/reactive) Users may assemble system incorrectly (reactive) Unknown user base (reactive/proactive) Uncertainty: randomness with unknowable probabilities Unexpected weather (reactive) Existing modules can be used for other tasks (proactive) People will want to infiltrate the system (reactive) The interaction between modules may effect the whole system (reactive) Risk: randomness with knowable probabilities Modules do not act as designed (reactive) Modules introduce security vulnerabilities (reactive) Modules can improve security (proactive) Variation: knowable variables and variance range Module/system breaks after period of use (reactive) Test facility availability (reactive) New sources of modules (proactive) Evolution: gradual (relatively) successive developments New missions that were not thought of before (reactive) New/upgraded technologies (proactive) Make sure everything is not a solution, but a thing that can happen

System: Adaptive Multi-Rotor UAV Platform Reality Factors Human (Including Customer) Behavior – Human error, whimsy, expediency, arrogance... Operator may try to operate while impaired, not trained, using it for unanticipated tasks Installation of unknown equipment Organizational Behavior – Survival rules rule, nobody's in absolute control... Ignores all FAA/FCC regulations Violates privacy laws Technology Pace – Accelerating technology and security-vulnerability introductions, sparse testing... All modules can be change with new technology System Complexity – Incomprehensible, highly networked, unintended consequences, emergence... All the modules need to interact in a standard method Externally developed modules can introduce new interactions in the system Standard module interfaces used for non-module interactions Globalization – Partners/customers/employees with different ethics, values, infrastructures, culture... Different aspects of privacy Different countries have different regulations/standards Make sure everything is not a solution, but a thing that can happen Partially-Agile Enterprise Faddish Practices – Outsourcing, web services, transparency, COTS policies/affects... COTS modules Forced compliance with standards Agile Customers/Competitors/Adversaries – Distributed, collaborative, self organizing, proactive, impatient, innovative... Adversaries try to hack/use the system Others can develop their own modules Customers may try to have multiple systems interact with each other in anticipated missions Other? ?

Response Situation Analysis for System: __________________________ with [t,c,p,s] metric-priorities for each issue, t = time of response, c = cost of response, p = predictability of response, s = scope of response Domain Response Issue Proactive Reactive Creation (and Elimination) What artifacts/data/knowledge must the system/process be creating or eliminating during operational activity? multiple task capable (s, t) Mission awareness (p, t) Improvement What process/system performance characteristics will be expected to improve during its operational life cycle? Ease of swapping out modules (t) Mission performance (c, p) Migration What major events coming down the road will require a change in the process/system infrastructure? New interconnection standards (t, c) Modification (Add/Sub Capability) What modifications to employable resources might need made as the process/system is used? Change in interface and material (t, s) Correction What will impair/obstruct process/system agility that will need an automatic systemic detection and response? Penetration detection (t, p) Weather conditions (t, p, s) Module component failure (t, p) Variation What process/system variables will range across what values and need accommodation? power requirements (t, c) external environmental (p, s) thermal management (p, c) Expansion (and Contraction of Capacity) What are “quantity-based” elastic-capacity range needs on resources/output/activity/other? Support 1 - 10 modules (c, s, p) Support missions up to 2 days in duration and as little as 5 minutes (s, p, c) Reconfigu-ration What types of resource relationship configurations will need changed during operation? Inter-module communication (t, p) Security trust of any module (t, p, s) Selective power connectivity (t, p, s)

System: Adaptive Multi-Rotor UAV Platform Resources Integrity Management Active Responders Sensor Modules Processor Modules Propulsion Modules Chassis Modules Power Modules Comm Modules Situational awareness Resource mix evolution Resource readiness Activity assembly Infrastructure evolution Operational Planner, Mission Planner Assembler Pilot, Assembler, Mission/Operational Planner Mission Planner Operational Planner Active Infrastructure Passive Farm Monitoring Weapon Mission Entertainment Sockets Signals Security Safety Service MAP Data Centric Bus Encryption/Signatures Data Integrity Check MAP Tools Rules/Standards

RRS Principles for System: Adaptive Multi-Rotor UAV Platform (Think: Plug-and-Play, Drag-and-drop) Reconfigurable Scalable Reusable Encapsulated Resources Resources are encapsulated independent units loosely coupled through the passive infrastructure. Sensors, Power Modules, Propulsion Modules, Processor Modules, Active Response Modules, Communication Modules Evolving Infrastructure Key elements of the infrastructure likely to evolve and need to be evolvable. Chassis, MAP interface, Data Centric Bus, Encryption/Signatures, MAP Design/Integration Tools Facilitated Interfacing (Pluggable) Resources & infrastructure have features facilitating easy resource insertion/removal. MAP Interface (Physical, Electrical, etc) Data Centric Bus Redundancy and Diversity Duplicate resources provide fail-soft & capacity options; diversity provides functional options. Redundant Module Capability COTS Modules Facilitated Reuse Resources are reusable and/or replicable; with supporting facilitation for finding and employing appropriate modules. MAP Interface allows swappable modules on all chassis Elastic Capacity Resource populations & functional capacity may be increased and decreased widely within the existing infrastructure. Resource Library of Heterogeneous Modules Multi-Module Chassis Peer-Peer Interaction Resources communicate directly on a peer-to-peer relationship; parallel rather than sequential relationships are favored. Data Centric Bus for inter-module/system communication Distributed Control & Information Decisions made at point of maximum knowledge; information accessible globally but kept locally. Data Centric Bus distributes information between all modules Deferred Commitment Resource relationships are transient when possible; decisions & fixed bindings are postponed until necessary. MAP/Data Centric Bus force black box view (SoA) Modules can be applied ad-hoc for a mission Modules are acquired as needed Self-Organization Resource relationships are self-determined; and resource interaction is self-adjusting or negotiated. Data Centric Bus allows any module to communicate with another Modules can be located in any MAP interface on the chassis