The Role of Aviation in Urban Warfare

Think. Learn. Succeed.1

The Role of Aviation in Urban Warfare

Capstone Project Report18 December 2009

Team Sikorsky (#7):Michael Bovan, Bryan Driskell,

Michael Ingram, Jay Stewart, Damian Watson

http://mason.gmu.edu/[email protected]

2Think. Learn. Succeed.

Agenda

• Project Introduction• Requirements & Elicitation• System Architecture• System Analysis• Business Plan & Technology Assessment• Conclusion & Road Ahead


Background

• 80% of worldwide population in urban environments by 2030• Unified population of terrorists / enemy combatants and

civilians alike• Example: 2008 Mumbai terrorist attacks on Taj Mahal Hotel

• Urban Environment Vertical Takeoff & Landing (VTOL) Missions: – Search & Rescue (SAR)– Attack & Target Designation– Troop Transport– Reconnaissance– Logistical Resupply


Problem Statement & Objective

• Problem Statement– Increasingly Urban Battlefield– Unique Challenges for Aviation Assets– Red vs. Blue Warfare Model is Ineffective– Unknown / Undefined Roles

• Project Objective– Analyze the role of VTOL aviation for future military missions in

urban environments.– Evaluate current aviation platforms– Identify technology gaps– Develop mission and/or system requirements and conduct trade-off

analysis


Deliverables, Assumptions, & Scope

• Deliverables– Quantitative Analysis– System Requirements– System Architecture

• Assumptions & Scope– Focus on military operations and military vehicles– Focus on VTOL vehicles– Focus on SAR operations within the urban canyon (UC)

• Stakeholders


Supporting Documents (Developed)

• Proposal & Problem Statement• Operational Concepts Definition• Objectives Hierarchy Analysis• Stakeholder Elicitation Plan• Requirements Elicitation Plan• System Requirements Traceability Matrix• System Requirements Specification• System Analysis & Scorecard• Physical Architecture• Business Plan & Technology Assessment


Project Schedule

• Networked Schedule– Shows Critical Path

– Critical Path - Stakeholder Elicitation and Functional Architecture

• Gantt Chart– Start and Finish of Tasks

– Shows Progress on Tasks


Agenda

8



Requirements Elicitation - General Approach

• Understand the stakeholders and ‘capture’ their requirementsMeet with Prime Stakeholders WeeklyUse Conversational Methods (Interviews, Focus Groups)

• Analyzing stakeholder selectionsDefined High Level System AttributesUse interviews and an Attribute Ranking SystemRepeat process for lower level system attributes

• Communicating stakeholder ideasShare elicitation choices between stakeholdersReach agreement on top choices

• Agreeing on selections/requirementsNegotiate with stakeholders about requirementsEnsure Traceability between requirements and system attributes


Requirements Elicitation (Cont)

For the VTOL Project, Requirements Elicitation was accomplished primarily through:

• Weekly Meetings with Prime Stakeholder

• Use of Current Event Discussions

• Brain Storming Sessions• Attribute Ranking Elicitation• Scenario Discussions• Use Case /Activity Diagram

Development• Requirements Document

Reviews and Negotiations

Attribute Rank

Endurance 7

Autonomy 5

Safety (Survivability) 1

Payload 4

Modularity 6

Maneuverability 2

Logistics 8

Operational Effectiveness 3

Requirements


Requirements Management

r4.6

The VTOL vehicle shall avoid damage to surrounding structures. In the event that collision is unavoidable.

The VTOL vehicle shall avoid damage to surrounding structures.

Implemented Damian comment. Functional

Recommend removing second sentence.

Original RequirementRevised Requirement

Requirement Type

Action Taken

#Damian’s Comment

• MS Excel 2003

• 200+ Requirements

• Easy to Set up, Difficult to Manage

• Cumbersome Traceability

• Not easily Linked to other Architecture Modules

More

Requirements


Requirements in Enterprise Architectcustom Requirements

The Requirements model is a structured catalogue of end-user requirements. These are represented as either Requirement or Feature elements.

The model is divided into two sub-catalogues:

1. The Functional requirements package contains requirements and features that represent functional behavior and features that the system under development must support.

2. The Non-functional requirements package contains constraints and performance levels the system must meet. For example response times, transactions per second, security strength.

Read about Requirements

r2 - Functional Requirements

+ r2.01 - Determine Incident Area

+ r2.02 - Locate Survivors In Rubble

+ r2.03 - Excavate Rubble

+ r2.04 - Operate in a Narrow Corridor

+ r2.05 - Capable of Roof Rescue Operations

+ r2.06 - Capable of Window-Rescue Operations

+ r2.07 - Detect Persons Beyond Visual Obstructions

+ r2.08 - Manual Control via Pilot or Control Station

+ r2.09 - Autonomous Flight Control via Flight Plan

+ r2.10 - Navigable via VFR or IFR

+ r2.11 - Automatically Generate Flight Plan to Destination

+ r2.12 - Avoid Coll isions

+ r2.13 - Visual Indication of Maneuver Intent

+ r2.14 - Avoid Damage by Surrounding Structures

+ r2.15 - Autonomously Detect Unstable Flight

+ r2.16 - Capable of Withstanding Impact / Coll ision

+ r2.17 - Protect Passengers

+ r2.18 - Detect Persons in Need of Help

+ r2.19 - Detect Person of Interest

+ r2.20 - Detect Vehicle of Interest

+ r2.21 - Track Target or Point of Interest

+ r2.22 - Provide Video Stabalization

+ r2.23 - Covertly Track Target or Point of Interest

+ r2.24 - Detect Incoming Fire

+ r2.25 - Return Lethal Fire

+ r2.26 - Encrypt Outgoing Communications

+ r2.27 - Decrypt Incoming Communications

+ r2.28 - Capable of Unencrypted Communications

+ r2.29 - Configurable for Simplex, Half-Duplex, or Full Duplex Comms

+ r2.30 - Determine Own Position

+ r2.31 - Digitally Transmit Own Position

+ r2.32 - Penetrate Building Exterior

+ r2.33 - Extract Injured Personnel

+ r2.34 - Mitigate Effects of Small Arms

+ r2.35 - Detect Incoming Threats

+ r2.36 - Engage Detected Incoming Threat

+ r2.37 - Provide Means to Manually Eliminate Threat

+ r2.38 - Provide Means to Automatically Eliminate Threat

+ r2.39 - Vertical Take-off

+ r2.40 - Vertical Landing

+ r2.41 - Manuever in 3d space.

+ r2.42 - Hover

+ r2.43 - Auto-stabil ize

+ r2.44 - Avoid Coll ision with Horizontal Objects

+ r2.45 - Auto-hover upon Pilot Disengagement

r6 - Technology and System Wide Requirements

+ r6.01 - Transport Persons

+ r6.02 - Minimize Operators

+ r6.03 - Provide First Aide

+ r6.04 - Land on a Carrier

+ r6.05 - Capable of Desert Operations

+ r6.06 - Redundant Power Systems

+ r6.07 - Redundant Sensor Systems

+ r6.08 - Redundant Communication Systems

+ r6.09 - Operate in Windy Conditions

+ r6.10 - Deployabil ity

+ r6.11 - Reliabil ity

+ r6.12 - Flexibil ity

+ r6.13 - Manueverabil ity

+ r6.14 - Survivabil ity

+ r6.15 - Maintainabil ity

+ r6.16 - Modularity

+ r6.17 - Configurabil ity

+ r6.18 - Lethality

+ r6.19 - Capable of Continuous Operations

+ r6.20 - System Operational Altitude Ceiling

+ r6.21 - Horizontal Field of View

+ r6.22 - Low Light & No Light Operations

+ r6.23 - Rainy Conditions

+ r6.24 - Snow or Sleet Conditions

+ r6.25 - Temp Requirements

+ r6.26 - Minimize Acoustic Signature

+ r6.27 - Capable of Urban Operations

Tracing element dependencies

Using the Relationship Matrix

r5 - Output Requirements

+ r5.01 - Audible Warn of Fall ing Vehicle

+ r5.02 - The system shall provide the operator general navigation information.

+ r5.03 - Broadcast Message to Point of Interest

+ r5.04 - Warn Operator of Detected Lethal Fire

+ r5.05 - Report Arcminute to HUD

+ r5.06 - Display NGA Info on a Map

+ r5.07 - Display Own Unit Status

+ r5.08 - Display Own Position on Map

+ r5.09 - Display Adjacent Unit Positions

+ r5.10 - Emit Distress Signal

+ r5.11 - Perform ID Analysis on Person of Interest

+ r5.12 - Perform ID Analysis on Vehicle of Interest

The Functional Requirements package details behavioral requirements that specify how a proposed system will process and handle information. It details the features and rules that must be present to fully implement the functionality desired.

The Non-Functional Requirements package specifiesthe various operational parameters that define the environment in which the system will exist. These are criteria which define performance levels, scalabil ity, security requirements, backup, disaster recovery and other operational requirements.

r3 - Input Requirements

+ r3.1 - Allow for a Predetermined Street Search Pattern

+ r3.2 - Receive Video Input

+ r3.3 - Receive Data on Vehicle Attributes

+ r3.4 - Operator Lock on Target

+ r3.5 - Receive Digital Position Reports

r4 - Operational Concepts

+ r4.01 Performance Period

+ r4.02 - Design Activity Limitations

+ r4.03 - Define and Scope Problem

+ r4.04 - Develop Requirements

+ r4.05 - Develop Stakeholder Scorecard

+ r4.06 - Elicite Feedback from Stakeholders

+ r4.07 - Analyze Current Vehicle Capabilities

+ r4.08 - ID Capability Gaps

+ r4.09 - Develop System Architecture

+ r4.10 - Dell iver Final Paper

+ r4.11 - Deliver Final Brief

r1 - External interface

+ r1.1 Communicate with Similar Systems

+ r1.2 Controllable by Common Ground Station

+ r1.3 Communicate in UHF

+ r1.4 Communicate in VHF

+ r1.5 Operate on 5-10 Simultaneous Voice Comm Freqs

• Improved “Nested” Structure

• Configuration Management

• Enhanced Requirements Traceability

• Linkable to other Module Elements

Requirements

Input

Operational Concept

External Interface

Functional

Technology

System Wide

Output


Agenda



System Architecture Overview

• Referenced Department of Defense Architecture Framework (DoDAF) v1.5

• Used non-DoDAF diagram to model Physical Architecture

• Focus on applicable Systems and Services Views (SV-1 /4)

• Diagrams developed using Unified Modeling Language (UML)

• Tool: Enterprise Architect (EA) v7.1


System Architecture Process

Determine Use CaseScenarios

Expand Use Cases(as text sequence)

Model Use CasesIn EA UML diagram

Identify External SystemsIn Operating Environment

Specify SystemRequirements

IdentifySystem Functions

Detail Use CasesIn Activity Diagrams

Organize FunctionalHierarchy

Map Functions to Form(Logical Physical Components)


SV-1 System Interface Description deployment Nodes

VTOL

Police Vehicle

SWAT Team

Carrier/Amphib CIC Ground Control

Station

AWACS E-3 Sentry

(other) VTOL

City Command Station

GPS Satellite Air Traffic Control (ATC)

Interface Codes:

I-01 = Voice (UHF, VHF) I-02 = Data (UHF) I-03 = Voice (UHF SATCOM DAMA) I-04 = Data (UHF SATCOM non-DAMA) I-05 = Video Imagery

I-01

I-04

I-01

I-01

I-02

I-03I-01

I-02

I-03

I-05

I-01

I-02

I-01I-03

I-01 I-02 I-03 I-04

I-04

I-03

I-01


SV-4 Example uc BOLO

Victim

(from Actors)

VTOL

(from Actors)

Operator

(from Actors)

Patrols Streets

Scans Streets or within Buildings

Performs Image Recognition (on

faces & v ehicles)

Command Staff

(from Actors)

Change Flight or Search Plan

Locks in on Detected Target

Track Target

Employ Nonlethal Threat Elimination

Methods

Detects Object(s) or Person(s) of Interest

Vehicle of Interest

(from Actors)

Notify Command Staff of Detection

Enemy Combatant(s)

(from Actors)

sd Activ ...

Execute Current Flightand Search Plan

ObjectNode3

Mission Begins

View CommonOperational Picture

Receiv e NewFlight/Search Plan

Coordinates

Process and Confirm NewFlight Plan Coordinates

Search Plan Change Decision

Inv oke New Flight/SearchPlan Coordinates

Begin New Flight/SearchPlan

End

Next Mission Decision

Return to Base Station

Resume CurrentFlight/Search Plan

Change Flight/Search Plan Activity Diagram

End Search

Yes

Continue Search

No

(Use Case)

(Activity Diagram)


Functional Decomposition

bdd Physical Architecture [Functional Decomposition]

«process»Searching and

Rescuing

«process»Communicating

«process»Rescuing

(Extracting)

«process»Sensing

«process»Remov ing

Obstructions

«process»Nav igating

«process»Maneuvering

«process»Defending

«process»Loading/Unloading

«process»Transporting

«process»Locating

(Detecting)

«process»Tracking

«process»Operatings Inside the Urban Canyon

«process»Attacking and Designating

Targets

«process»Transporting

Troops

«process»Conducting

Reconnaissance

«process»Conducting

Logistical Resupply

«process»Transmitting/Receiv ing

«process»Encryping/Decrypting

«process»Converting

Analog/Digital

«process»Lifting (Vertically)

«process»Thrusting

(Horizontally)

«process»Penetrating

Partitions

«process»Grasping Objects

«process»Mov ing Objects

«process»Releasing

Objects

«process»Hovering

«process»Planning Flight

«process»Determining

Position

«process»Deflecting/Absorbing

Damage

«process»Engaging Enemy

«process»Detecting Heat

«process»Detecting

Reflected RF

«process»Detecting

Acoustic Effects

«process»Landing

«process»Camouflaging

«process»Illuminating

Target

«process»Imaging

«process»Displaying

«process»Mapping

«process»Plotting

«process»Avoiding Obstacles

«process»Gauging


Function To Form Map bdd Physical Architecture [Form to Function Mapping (Top Lev el)]

«process»Searching and

Rescuing


«process»Rescuing

(Extracting)

«process»Sensing

«process»Remov ing

Obstructions

«process»Nav igating Maneuv ering Defending

VTOL

Sensor Subsystem

Displaying

Communication Subsystem

Extraction Subsystem

Nav igation Subsystem

Demolition Subsystem

Mobility Subsystem

Self-Defense Subsystem

Display Subsystem

bdd Physical Architecture [Form to Function Mapping (Communicating)] ...


«process»Transmitting/Receiv ing

«process»Encryping/Decrypting

«process»Conv erting

Analog/Digital

Communication Subsystem

Analog/Digital Conv erter

Cryptographic Dev ice

UHF Radio VHF Radio

(Top Level)

(Communicating)


Agenda



Analysis [1]

• Data: Market Research & Sponsor Input

• Scenario Development via Use Cases


Analysis [2]

Vehicle Comparison

30%40%50%60%70%80%90%

V22 O

spre

y

F35

Ligh

tnin

g I I

Apache

AH

64A

Black

hawk

S-76

MD50

0

MD50

0 Def

ender

Camco

pter

S-1

00

Fire

Sco

ut MQ8

A-160

Hum

min

gbird

(YM

Q-18A

)

Eagle

Eye

Flyi

ng-Cam

Organi

c Air

Vehic

le

Smal

l Unm

anned

Air

Vehicl

e

X-50

Dragon

fly Cana

rd R

otor

...

RQ-16

T-Haw

k

Vigila

nte 4

96 (O

PV)

Vigila

nte 5

02

Baldw

in M

ono T

ilt R

otar

Vehicles

Res

ult

ing

Sco

re

Contested Evacuation

SAR Following Destruction

BOLO

Hostage Rescue

Comparison of Scenario Results

30%

40%

50%

60%

70%

80%

90%

Highest Ranking Vehicle to Lowest Ranking Vehicle

Sc

en

ari

o S

co

rin

g R

es

ult


Analysis [1]

• Data: Market Research & Sponsor Input

• Scenario Development via Use Cases


Analysis [2]

Vehicle Comparison

30%40%50%60%70%80%90%

V22 O

spre

y

F35

Ligh

tnin

g I I

Apache

AH

64A

Black

hawk

S-76

MD50

0

MD50

0 Def

ender

Camco

pter

S-1

00

Fire

Sco

ut MQ8

A-160

Hum

min

gbird

(YM

Q-18A

)

Eagle

Eye

Flyi

ng-Cam

Organi

c Air

Vehic

le

Smal

l Unm

anned

Air

Vehicl

e

X-50

Dragon

fly Cana

rd R

otor

...

RQ-16

T-Haw

k

Vigila

nte 4

96 (O

PV)

Vigila

nte 5

02

Baldw

in M

ono T

ilt R

otar

Vehicles

Res

ult

ing

Sco

re

Contested Evacuation

SAR Following Destruction

BOLO

Hostage Rescue

Comparison of Scenario Results

30%

40%

50%

60%

70%

80%

90%

Highest Ranking Vehicle to Lowest Ranking Vehicle

Sc

en

ari

o S

co

rin

g R

es

ult


Agenda



Business Plan

• Use• Investment

– Partnerships– S-curve

• Marketability– Consumer Use – Point-to-Point travel

Alleviate City street congestion

• Policy & Law– Protect Noise Pollution– Safety


Technology Assessment [1]

In Function to Form Mapping, certain functionality depends on “Critical Technologies”

class Critical Technologies

Demolition Subsystem

Extraction Subsystem

Passenger Cabin Passenger Retriev al

Component

Airframe Horizontal Propulsion Component

Mobility Subsystem

Vertical Lift Component

VTOL

Manipulation Component

Penetration Component


Technology Assessment [2]

28

Passenger Cabin

Passenger Retreival

ComponentManipulation Component


Airframe (landing gear)

Horizontal Propulsion Component


Internal Seats Telescoping Arm Magnet Laser Skids Air Propulsion Rocket

Internal Stretcher Hanging Basket Claw Explosives WheelsUse Vertical Lift Component Protected Fans

Internal Open Area

Door (requires system to be very close to Ramming Head Flotation Devices

Use Stabilization Arms (to push off) Ducted Fans

External Seats Retractable PlanksUse weapon system Posts with Springs

Use Grappling Hooks (to pull)

Gas (lighter than air)

External Stretcher (sidecar) Jointed Arms Circular Saw

Grid of Cables (above skyline) Heated Air

External Stretcher (hanging basket)

Zip Line (shot in direction of passenger) Compressed Gas Hypergolic FuelParachute (shot in direction of passenger) Grappling Hooks

StiltsNuclear Grid of Cables (above skyline)Magnetic Tracks (affixed to buildings)Compressed GasSpring-actuated Lift (like a pogo stick)

Design Combination Passenger Cabin

Passenger Retreival

ComponentManipulation Component


Airframe (landing gear)

Horizontal Propulsion Component


1Internal Open Area Jointed Arm Claw Laser Skids Compressed Gas

Gas (lighter than air)

2 Internal Stretcher

Zip Line (shot in direction of passenger) Magnet Circular Saw Skids

Use Vertical Lift Component Protected Fans

3 External Stretcher Hanging Basket Magnet Laser SkidsGrid of Cables (above skyline)

Grid of Cables (above skyline)

• Used Morphological Box to generate solutions for each critical technology

• Assessed feasibility and generated design combinations


Conclusions & Road Ahead

• No one vehicle currently suitable for SAR mission• VTOL Maneuverability Technology and Safety limit

SAR Mission Effectiveness• Communications Technology can support SAR

Missions within the UC• Identified capability gaps• Conduct Analysis of Alternatives on Future

Technologies• Develop Design Solutions


30

Acknowledgement

• Thank You Sikorsky for the Opportunity to Support Your Projects– Mr. Chris VanBuiten – Mr. John Burton– Mr. David Kingsbury

• Thanks to GMU Faculty


Backup Slides

Comdr. Frank A. Erickson, USCG & Dr. Igor Sikorsky, Sikorsky Helicopter HNS-1 C.G. #39040.

Igor Sikorsky & Orville Wright with Sikorsky XR-4 in 1942


Schedule


Schedule (Network Diagram 1 of 2)


Schedule (Network Diagram 2 of 2)


System Boundaries

• External: Humans (Operators, Maintenance), SAR Sensors.

• Internal:platform,sensors forvehicle health & navigation,mounts &rails

The Role of Aviation in Urban Warfare

Documents

Transcript of The Role of Aviation in Urban Warfare