General Aviation Support System GASS GMU SEOR Masters

General Aviation Support System (GASS) GMU SEOR Master’s Project SYST 798 John Glaeser Linda Jarusewski Mark Locher Mobeen Vaid 12 December 2008

The GASS Team § John Glaeser • VP Engineering, Chief Architect • MS SE – Architecture-Based Systems Integration § Linda Jarusewski • CIO, VP Operations • MS SE – C 4 I § Mark Locher • CFO, Lead Systems Integrator • MS SE – Systems Engineering Analysis; Ph. D Candidate § Mobeen Vaid • VP Marketing, VP Research & Development • MS SE – C 4 I § Role: Product Developer pitching to key industry heavyweights (e. g. Piper Aircraft) for investment and further development 2

Purpose & Objective Purpose § To present the General Aviation Support System (GASS) • • What is GASS? How does GASS work? How GASS will be implemented? Why is GASS a viable business opportunity? Objective § Obtain funding for future development § Demonstrate the systems engineering knowledge and skill set of the GASS Team 3

Overview § § § § 4 Background Solution GASS Market Plan & Costing System/Project Scope & Methodology System Architecture Systems Engineering Management Considerations Summary & Project Conclusions Q&A

The Problem & Background Aviation Accident Causes 1950 -2006* * Courtesy of the Aircraft Crashes Record Office; Geneva, Switzerland ** Courtesy of the U. S. National Safety Transportation Board § 220, 000 civilian aircraft and 624, 000 licensed pilots in the United States § 2007 - 1, 631 general aviation accidents resulting in 491 fatalities** § GASS Team identified need for additional safety; convenience promotes use & profit No single-source, user-friendly integrated solution of safety & convenience features available to General Aviation Public 5

The GASS Solution § GASS will provide the economic and user-friendly integration of pre-flight, in-flight, and post-flight services to reduce accidents and streamline flight operations § GASS Services • Flight Planning Support (FPS) • Real-Time Condition Monitoring (RACM) – Aircraft hull & systems, pilot physiology • In-Flight Support (IFS) – Notifications/alerts, recommendations, rerouting • Trend monitoring • Record maintenance – Pilot & aircraft Courtesy of the Aircraft Crashes Record Office; Geneva, Switzerland • Subscription-fee based service § Goal: To deliver a system with basic functionality in 2010, 6 with increments adding aircraft monitoring in 2011 and full system coverage in 2012

Concept of Operations (Fixed Base Operators) 7 (Federal Aviation Administration)

Bottom Line Up Front § GASS is a feasible system • Market analysis justifies implementation • Key risks identified & mitigation strategies identified • Critical technologies are mature and available for rapid system development • Base architecture developed with eye towards future incremental upgrades – system improvements/new markets § Costs • Development: $5. 8 M • Break-even: 4 years • Return on investment (IRR): 67% § Managerial concerns • GASS Team has corporate organizational structure in place • Groundwork laid for systems engineering management tactics 8

Potential Competitors / Partners / Suppliers § EDS Flight planning services • Automated route maintenance, pilot self-planning tools, crew briefing packages, flight tracking, NOTAMS (critical flight-specific information), weather/infrastructure status, and historical statistical data • Target market: commercial airlines § Fltplan. com • Produces flight plans, finds nearby airports, scours the map for area fuel prices, provides info on Navaids and fixes, and many other useful tools for pilots • Target market: corporate & business pilots § Boeing • Remote Management of Real-Time Airplane Health Monitoring system • Target market: commercial airlines § Intrusion-Free Physiological Condition Monitoring System • Target market: fighter & high performance aircraft pilots § Pilot Loss of Conscious (PLOC) Monitor • Target market: fighter & high performance aircraft pilots 9 Potential for buyout from competitors and partners

Market Segmentation * 4 Expand here 2 Start Here 1 3 10 * Courtesy of Piper Aircraft, Inc **Courtesy of the National Transportation Safety Board **

Market Growth and Segment Penetration 33% Penetration 11% Penetration 11

Cash Flow Analysis (Cumulative) Influence diagram used for cash flow sensitivity analyses § § 12 Payback in ~5 years, Up to 7 years if growth 60% of forecast Primary cost drivers are manpower & FAA certification

Cash Flow Variance Analysis (Annual Basis) Predicted Net Present Value (NPV) (25 years @ 18%): $52. 3 M § Predicted • • • § Investment Required: $5. 8 M Positive cash flow in year 4 64% IRR (1 st 10 years) 80% Growth Rate • • • Investment Required: $8. 4 M Positive cash flow in year 4 44% IRR § 60% Growth Rate • • • Investment Required: $10. 9 M Positive cash flow in year 5 29% IRR

Tornado Diagram Most significant factors affecting cost

NPV Risk Profile

Waterfall Development Process § Planning • • • Define Objectives Determine Scope Stakeholder analysis Assumption definition Project workplan Intent specification § Analysis • • Ao. A (Utility analyses) Market analyses Risk analyses Cost estimate § Design Planning Analysis 3 phases and deliverables iterated to obtain final design Design Construction Implementation Operation • System level design following the Department of Defense Architecture Framework (DODAF) § Construction, Implementation, & Operation beyond scope 16

Scope & Context Basic Architecture (Pilot) Aircraft Increment Basic Architecture (Pilot) Final Incremental development process to modularly add functionality in 3 phases Spiral or waterfall process could be used for future iterations Planning Analysis Design Construction Implementation Current status - investment and further design 17 Construction Implementation

Tracing System Form to Needs Problem System Review Documented Deliverable Intent Spec (ICD) OV-5 Requirements / Capabilities Operational Activities Needs Matrix Needs/Req Trace Matrix Architectural Choice Space Definition SV-5 A Map SV-4 SV-2 System Elements Definition Stakeholder Value Decomposition System Elements Choice Space Definition Utility Values And Weights Concept OV-2 Multiple OV -2 s System Functions Mission, Goals, Use Cases, Interviews Traceability Method Stakeholder Needs Architectural Choice Space Selection Morphological Box, Component Compatibility Matrix SV-5 B Map Complete traceability from system instantiation to problem achieved System Elements Choice Space Selection Utility Analysis Matrix

GASS Context Diagram * * * Key stakeholders including GASS Developers System Boundary §User §Associates* * 19 * *

Winning System Architectural Choice Semi-Centralized Operations DODAF OV-2 System Boundary 20 DODAF OV-1

GASS p-Diagram Summation of information elements and impact factors 21

Morphological Box § 2 – 20 potential solutions per element • § Incompatibility and Data Throughput analysis reduced 332. 5 M instantiations to 88. 2 M • § Initial reduction based on top level assessment Limiting factors = COTS equipment, wireless installations, and 32 kbs transmittal rate Downselection achieved through utility analysis 22

Utility Analysis Weighted evaluation of stakeholder value per area used to determine final utility function Weight. Utility(Relative)=∑Weight. Stakeholder*Value. Stakeholder 23

Management - Risk Top Risks Identified 1. Loss of contact/communications 2. Incompatibility with Existing Manufacturer-Installed Sensor Suite 3. FAA NOTAMs & TFR Procurement Issues 4. NWS Weather Data Procurement Issues 5. Physiological Sensor Suite Lack Robustness 6. Physiological Distress Sensitivity 7. Incompatibility with Manufacturer-Installed Display Unit 8. Investor Funding Reductions Worst risks not catastrophic; easily mitigated 9. FAA Approval through early stakeholder involvement 10. Electromagnetic Interference 24

Management – Structure § Vetted work breakdown structure (WBS) constructed based on system lifecycle • • • Currently developed to system acceptance Verification & Validation accomplished throughout Component Development Entrance/exit criteria and deliverables well defined § Corporate structure established • • 25 Small business ready for rapid expansion Matrix organization crosses technical capabilities with WBS Section 3 project areas Risks identified, WBS, corporate structure, and system development schedule in place provide strong management base

GASS Corporate Structure §Board of Directors Investors §President/CEO Investors to provide influence through or as a part of the GASS Board of Directors §CFO GASS Divisions 26 §Human Resources §Marketing & Sales §Operations §Engineering

GASS Matrix Organization Operations Manager 27 Matrix organization selected due to potential for rapid business expansion; free flow and access to information and personnel required

Legal Issues § Minimization of liability • • • Retain proper legal advice Terms and Conditions agreement Customer training Ensure business practices comply with state and federal regulations Provide a legal handbook to managers and employees Negotiate contracts that will protect our rights and help avoid disputes with our suppliers and customers • Corporate and officer insurance coverage § Intellectual Property • Trademark the GASS brand • Patent GASS processes, procedures, & arrangements • Copyright unique GASS software 28

GASS Summary § Market identified for a sole-source supplier of general aviation services § GASS automates value-added services that are done manually today and offers a logical joining of pre-flight, in-flight and postflight services § GASS will improve and promote safety through convenience § GASS is feasible business opportunity • • Incremental introduction into market in 2010, 2011, and 2012 $5. 8 M investment 67% return on investment 4 year breakeven point Minimal risks Basic architecture developed with eye towards expansion Organizational structure and development schedule established for strong start § Investment is the only roadblock to a successful venture 29 Join the GASS Team - Invest today and be a part of the future of aviation services!

Project Conclusions § § Translated systems engineering activities into a viable business case Broad range of GMU-instilled systems engineering & engineering management practices utilized • • § Keys to success • • • § Design: Traceability from system instantiation to original needs & problem statement necessary to achieve design solidarity Management: Gantt & PERT charts used to outline and track group progress Group: hard work, good ideas, and open communication Recommendation to future groups • 30 Architecture development Decision analysis Requirements generation Risk analysis Costing Scheduling Organization A business case provides an interesting and unique approach to integrating prior coursework and personal experience in a practical (although constrained) application

QUESTIONS? Questions? Many thanks to the following individuals for their contributions to our project Dr. Thomas Speller, GMU John Becker, Piper Aircraft Steven Josephson, FAA Syst 798 Classmates GMU SEOR Faculty 31 *Image courtesy of Piper Aircraft, Inc.

BACKUP SLIDES 32

GASS Process Implementation § Use cases and stakeholder discussions determine Needs § Concept of Operations developed § Intent specification (Initial Capabilities Document) map Requirements to Needs § 3 alternate general architectures developed: centralized, semicentralized, and decentralized operations § Architectures downselected via utility analysis § Target development of Department of Defense Architecture Framework (DODAF) deliverables to visualize GASS architecture § Operational capabilities/functions & system functions developed § Potential system elements identified via morphological box and downselected via utility analyses § Marketing, cost, and risk analyses conducted to 33 support system implementation

Needs Breakdown §Provide General Aviation Services §Preflight Needs §In-flight Needs §Postflight Needs §General §Quality Flight Plan Formulation §Pilot awareness of External Conditions §Notification of problems §Ease of access §Completeness of Support Services §Awareness of Incipient Inflight Problems §Notification of routine due events §Ubiquity of access §Support in case of emergency §High Availability §Aircraft Status Communicatio n with Associates §Timely Service Response §Accurate Service 34 §Cost Effective Installation & Services Needs derived from use cases and stakeholder discussions

Detailed Stakeholder Analysis From use cases 35 Weighted evaluation used in utility analyses From interviews, market analysis, & discussions

Concept § Provide both recreational pilots and small scale commercial operations an integrated range of services similar to those provided by a commercial airline company through its operations center. § This integrated system will combine: • Flight Planning Support (FPS) • Real-Time Condition Monitoring (RACM) of both aircraft systems and the pilot • In-Flight Support (IFS) for routine, advisory and safety-critical situations • Aircraft capability trend monitoring, with maintenance advisory notification • Pilot flight record maintenance § Services accessible remotely (away from aircraft) and from the aircraft cockpit 36

Use Case Development 5 Top level use cases developed 37

System Architectural Choice #1 Maximum Centralization System Boundary 38

System Architectural Choice #2 Decentralized System / Max on-aircraft processing System Boundary 39 Ring Network

Operational Function Decomposition §CONTINENTAL US FLIGHT OPERATIONS Level -1 §PROVIDE GENERAL AVIATION SERVICES Level 0 Level 1 §AIR & SPACE TRAVEL §PROVIDE FLIGHT PLANNING SUPPORT §PROVIDE INFLIGHT SUPPORT §PROVIDE POSTFLIGHT SUPPORT §Request Flight Plan §Provide Real-time Aircraft Condition Monitoring §Provide aircraft RACM data support §Initiate Flight Plan §Provide Pilot Assistance §Provide aircraft maintenance record service §Create Flight Plan §Communicate with Associates §Provide Pilot Flight Records Services Level -2 • Need: Safety & Convenience • Want: Convenient integration of the following safety oriented features: Flight Planning, Pilot/Aircraft Monitoring & Tracking, Pilot/Aircraft Post-flight Record Analysis • Mission: To help maximize flight safety and streamline flight operations by integrating an affordable solution of flight planning, monitoring, tracking, and record analysis features • Problem: Given 1, 631 general aviation accidents resulting in 491 fatalities in 2007 alone, it is evident the continued lack of a convenient, affordable, and integrated method of flight planning, flight tracking, and human/aircraft monitoring is required to help prevent the loss of life and aircraft. • Purpose: To promote safety and generate revenue via a sole-source integrated solution of flight planning, monitoring, tracking, and record analysis services • Goal: To field a commercially viable prototype by 2010 and to introduce the GASS system into the target market by 2011 Level 2 40 §. . . Operational functions finalized and decomposed down 4 levels; Top 2 levels shown

System Function Decomposition §Provide General Aviation Services §Provide Information Assurance §Provide User Interface §Provide telephonic user interface §Provide User Identification and Authentications §Provide email user §Provide data interface §Provide webbased user interface confidentiality §Provide data integrity §Acquire External Data (includes data updating) §Acquire user profile data §Acquire air navigation support data (maps, etc) §Acquire weather data §Acquire NOTAMs/TFRs §Acquire Aircraft Related Data §Acquire §Provide aircraft ground communications Navigation Data §Provide data communications §Prepare flight §Acquire Aircraft §Provide voice communications §Track On-going Condition Data §Acquire Pilot Physiology Data §Acquire air traffic data 41 §Support Operations System functions developed to 3 rd level detail; top 2 levels shown here plans flights §Record Operations Center Activity §Process Acquired data §Provide alerts and notifications §Provide system availability §Provide high assurance of communications §Provide high system availability

IDEF 0 Activity Diagrams OV-5 42

IDEF 0 Activity Diagrams OV-5 43

IDEF 0 Activity Diagrams OV-5 44

IDEF 0 Activity Diagrams OV-5 45

IDEF 0 Activity Diagrams OV-5 46

IDEF 1 X Data Model OV-7 47

SV-2 48

System Functions (SV-4 Format) Impetus of DODAF System View (SV) development 49

Request Flight Plan SV 10 b 50

Aircraft Communications SV-10 b 51

Maintain Records SV-10 b 52

Component Diagram for SV-10 b 53

Sample Utility Function 54

Stakeholder Utility Weighting 55

Data Throughput & Storage Analysis § GASS data link determined to be of critical importance to capability development and technology selection § Onboard (aircraft) data capture § 6 hr flight to generate ~3 Mb data § Data transmittal § § 30 bytes/min steady state burst 65, 536 bytes end-of-flight condition message 16 kbs for in-flight communications 32 kbs emergency data transmission § Ground data storage § 7. 2 Tb online storage § 30 Tb offline storage 56 Max transmittal rate of 32 kbs limited potential system solutions

Influence Diagram 57

GASS Summary Schedule 58