Unclassified

A Model-Driven Systems Engineering Approach for

Unmanned Aircraft Airspace Integration

Joe WolfromJennifer RaineyKen McKneely

October 26, 2006

Distribution Statement A

Approved for Public Release: Release is Unlimited

October 26, 2006

slide 2

Unclassified

Outline

PurposeProblem DescriptionUA Regional Airspace Integration StrategyApproachWhy MDSEProcessImportance of Activity DiagramsArchitecture ArtifactsProblem Areas IdentifiedFindingsConclusionsQuestions

October 26, 2006

slide 3

Unclassified

Purpose

Highlight the benefits of using a Model-Driven Systems Engineering (MDSE) approach to address the issue of integrating Unmanned Aircraft (UA) into the National Airspace System (NAS)Present a practical application of system model and architecture development

October 26, 2006

slide 4

Unclassified

Problem Description

Increasing need to operate UA in the NASDoD – TrainingDEA – Drug interdictionCBP – Border security

FAA has two primary safety issuesCommand and control redundancies“Sense and Avoid” capability

October 26, 2006

slide 5

Unclassified

Problem Description (cont’d)

Current NAS access for UA requires a Certification of Authorization (COA)

60 day review cycle1 year maximum life spanMay include special provisions or restrictions

UA technology advancing ahead of regulatory policyBeyond line of sight controlHigh altitudeLong range and endurance

October 26, 2006

slide 6

Unclassified

Global Hawk, Predator, and Fire Scout

Global Hawk

Predator

Fire Scout

October 26, 2006

slide 7

Unclassified

UA Regional Airspace Integration StrategyObjective

Gain or expand access in selected regions via COA processPatuxent River Naval Air Station, MDBeale AFB, CACreech AFB, NV Ft. Huachuca, AZ

ConstraintsUse of current technologiesComply with current FAA regulations

GoalFacilitate COA process

October 26, 2006

slide 8

Unclassified

Approach

Use a Model-Driven Systems Engineering (MDSE) methodologyBuild a system model of Global Hawk mission operations at Patuxent River, MDProduce architecture artifacts

Use artifacts to reach common understanding between ATC and Global Hawk operators in order to facilitate COA processUse artifacts to identify

Problem areasIssues that need clarification or resolution

October 26, 2006

slide 9

Unclassified

Why MDSE

Modeling is a formal way to visualize somethingAssists stakeholders in understanding something that is not easily comprehensibleA form of communication

Provide operators a means to convey their planned mission operationsProvide regional Air Traffic Controllers (ATC) a way to better visualize the planned operationsProvide a means to discuss and resolve contingencies

“If you don’t model it, you won’t understand it.”Ivar Jacobson

October 26, 2006

slide 10

Unclassified

Process

Decompose mission operations into Use CasesPlan Operational MissionFile Flight PlanStart, Taxi, TakeoffOperate in Patuxent River AirspaceLand, Taxi, Shutdown

Identify common Use CasesMonitor WeatherReport Health and StatusHandoff ControlTraffic DeconflictionPerform Sense and Avoid

October 26, 2006

slide 11

Unclassified

Process (cont’d)

Model Use CasesDevelop Activity Diagrams for each Use CaseValidate Activity Diagrams with stakeholdersIdentify problem areas and issuesRevise Activity Diagrams with proposed changesDevelop related architecture artifacts

October 26, 2006

slide 12

Unclassified

Importance of Activity Diagrams

Cornerstone of modelShows sequence of activitiesIdentifies actor responsible for each activityPrimary artifact used to communicate with stakeholdersEasy to understand (sequential)

Helps produce other artifactsOperational Node Connectivity DiagramOperational Information Exchange Matrix

October 26, 2006

slide 13

Unclassified

Architecture Artifacts

High-level Operational Concept Graphic (OV-1)Use Case DiagramsActivity Diagrams (OV-5)Operational Node Connectivity Diagram (OV-2)Operational Information Exchange Matrix (OV-3)Organizational Relationship Chart (OV-4)Overview and Summary Information (AV-1)Integrated Dictionary (AV-2)

October 26, 2006

slide 14

Unclassified

Architecture Artifacts High Level Operational Concept Graphic

October 26, 2006

slide 15

Unclassified

Architecture ArtifactsUse Case Relationships

October 26, 2006

slide 16

Unclassified

Architecture Artifacts Land, Taxi, Shutdown Use Case Diagram (1 of 13)

October 26, 2006

slide 17

Unclassified

Architecture Artifacts Land, Taxi, Shutdown Activity Diagram (1 of 13)

October 26, 2006

slide 18

Unclassified

Architecture Artifacts Operational Node Connectivity Diagram

October 26, 2006

slide 19

Unclassified

Architecture Artifacts Operational Node Connectivity Diagram

October 26, 2006

slide 20

Unclassified

Problem Areas Identified

No visual of traffic at Global Hawk ground stationRequired for “Sense and Avoid” capability

Contingency landings – requires flying through controlled airspace to use alternate runway

Provision – chase plane required for contingency landings

October 26, 2006

slide 21

Unclassified

Findings

MDSE process could serve as template to facilitate COA process in other regionsEach region needs its own model

Airspace configuration differs from one region to another

Use Case decomposition allows for some re-useMonitor WeatherReport Health and StatusTraffic Deconfliction

October 26, 2006

slide 22

Unclassified

Conclusions

Model-Driven System Engineering:Useful for facilitating communications among stakeholdersEasy to comprehend Assists in reaching mutual understanding between ATC and Global Hawk operatorsHelps to identify problem areas Provides building block approach for other regions

Activity Diagrams - key element of architecture

October 26, 2006

slide 23

Unclassified

Questions