Transcript In Search Of Excellence In Project Management

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 – C4I
 Mark Locher
• CFO, Lead Systems Integrator
• MS SE – Systems Engineering Analysis; PhD Candidate
 Mobeen Vaid
• VP Marketing, VP Research & Development
• MS SE – C4I
 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
Aviation Accident
Causes 1950-2006*
60%
Percentage
50%
40%
30%
20%
10%
0%
Pilot Error
Mechanical
Failure
Weather
Other human
error
Sabotage
Other
Causes
Cause of Accident
* 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,
with increments adding aircraft monitoring in 2011 and
full system coverage in 2012
6
Concept of Operations
Server Backup
(different location)
Ops Center
Server Backup
Flight Computer
Intercomm
Aircraft
Systems
(different location)
Pilot pre-flight
Controller
Recorder
FBO
Datalink
(Fixed Base Operators)
Ops Center
Aircraft
Manufacturers
7
FAA
Weather
(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.8M
• 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
140,000
Aircraft Market Segments*
120,000
**
120,000
100,000
4
Expand here
80,000
2
60,000
41,000
Start Here
1
40,000
3
30,000
20,000
7,000
5,000
1,500
m
ut
er
Ty
pe
Co
m
Je
ts
Je
ts
Ai
rl i
ne
Bu
sin
es
s
En
d
Bu
sin
es
s
on
al
Pe
rs
so
na
l
Pe
r
Hi
gh
10
Lo
w
En
d
Bu
si n
es
s
Ho
bb
yi s
t/T
r
ain
er
s
0
* Courtesy of Piper Aircraft, Inc **Courtesy of the National Transportation Safety Board
Market Growth and Segment Penetration
25000
Market Penetration
33% Penetration
20000
3% Penetration
11% Penetration
Size
15000
Full Service
Pilot Only
Aircraft Only
10000
5000
0
0
11
5
10
Year
15
20
25
Cash Flow Analysis (Cumulative)
$600,000,000
Cumulative Cash Flow
$500,000,000
Pricing (monthly)
High end
$109.95
Pilot only
$49.95
Fleet only
$89.95
Equipment Revenue
High end
$9,999
Pilot only
$3,999
Fleet only
$6,999
Cash Flow
$400,000,000
$300,000,000
$200,000,000
Influence diagram used for
cash flow sensitivity analyses
$100,000,000
$0
($100,000,000)


12
0
5
10
15
Year
20
Payback in ~5 years, Up to 7 years if growth 60% of
forecast
Primary cost drivers are manpower & FAA certification
25
30
Cash Flow Variance Analysis
(Annual Basis)
$35,000,000.00
Sales Forecast Variance: Effects on Cash Flow
$30,000,000.00
Predicted
$25,000,000.00
$20,000,000.00
80% Sales Growth
60% Sales Growth
Predicted Net Present Value (NPV)
(25 years @ 18%): $52.3M
$15,000,000.00
$10,000,000.00
$5,000,000.00
$0.00
($5,000,000.00) 0
5
10
15
($10,000,000.00)
Year

Predicted
•
•
•

Investment Required: $5.8M
Positive cash flow in year 4
64% IRR (1st 10 years)
80% Growth Rate
•
•
•
Investment Required: $8.4M
Positive cash flow in year 4
44% IRR

60% Growth Rate
•
•
•
Investment Required:
$10.9M
Positive cash flow in
year 5
29% IRR
20
25
Tornado Diagram
Most significant
factors affecting
cost
NPV Risk Profile
Utilities
Cost
SMS
Cost
Facilities
Cost
Voice
Cost
NPV
DPL
Flying
Rate
Routine
Contact
Price
Multiple
Sales
Growth
Rate
Waterfall Development Process
 Planning
•
•
•
•
•
•
Define Objectives
Determine Scope
Stakeholder analysis
Assumption definition
Project workplan
Intent specification
 Analysis
•
•
•
•
AoA (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
Aircraft Increment
Basic
Architecture
(Pilot)
Basic
Architecture
(Pilot)
Final Increment
Incremental development process to modularly add functionality in 3 phases
Spiral or waterfall process could be used for future iterations
Planning
Planning
Planning
Analysis
Analysis
Analysis
Design
Design
Design
Construction
Implementation
Construction
Implementation
Current status - investment and further design
17
Construction
Implementation
Tracing System Form to Needs
Problem
System Review
Documented Deliverable
Needs Matrix
Traceability Method
Stakeholder
Needs
Intent Spec
(ICD)
OV-5
Requirements
/ Capabilities
Operational
Activities
Needs/Req Trace Matrix
Architectural
Choice Space
Definition
SV-5A Map
SV-4
SV-2
System
Elements
Choice Space
Definition
Utility Values
And Weights
Concept
OV-2
Multiple
OV-2s
System
Functions
System
Elements
Definition
Stakeholder
Value
Decomposition
Mission, Goals, Use
Cases, Interviews
Architectural
Choice Space
Selection
Morphological
Box, Component
Compatibility Matrix
SV-5B Map
Complete traceability
from system
instantiation to
problem achieved
System
Elements
Choice Space
Selection
Utility Analysis
Matrix
GASS Context Diagram
Weather
(NWS)
Pilot*
Air Traffic
(FAA)*
* Key
stakeholders
including
GASS
Developers
System Boundary
General Aviation Support System
Pre
PreFlight
Flight
Support
Support
Fixed Base
Operators*
19
In
InFlight
Flight
Support
Support
Post
PostFlight
Flight
Support
Support
Aircraft
Owners *
Aircraft
*
Manufacturers
User
Associates*
Aircraft
Systems
Winning System Architectural Choice
Semi-Centralized Operations
First Downselection Utility Results
Potential
Architectures
Architecture 1
(Centralized)
Architecture 2
(Decentralized)
Architecture 3
(Semi-Centralized)
Final Scores
Ops Center
0.48
Server Backup
Pilot pre-flight
Controller
0.50
Recorder
0.55
FBO
Datalink
Ops Center
Aircraft
Manufacturers
FAA
20
Aircraft
Server
Backup
Aircraft
Systems
(different location)
System Boundary
Ops
Center
Intercomm
(different location)
DODAF
OV-2
User
Interface
Flight Computer
Server Backup
External
Interfaces
(Weather,
FAA, FBOs
Weather
DODAF
OV-1
GASS p-Diagram
Uncontrollables
•Weather
•FAA Regulations
•Network Delays/Interruptions
•Pilot Condition
•Aircraft Condition
•System Use (Pilot/User)
Summation of information
elements and impact
factors
Inputs
•Service Requests
•Pilot Data
•Pilot Currency
•Aircraft Data
•Maintenance Records
•Destination
•Flight Tracks
•Pilot Comms Response
•FAA NOTAMs & TFRs
•NWS Weather Data
21
Outputs
GASS System
Controllables
•Aircraft System Sensor Suite
•Hull System Sensor Suite
•Physiological Sensor Suite
•Flight Planning Requirements
•Notification/Alert Requirements
•Recordkeeping Requirements
•Flight Tracking Requirements
•System Operation/Processing
•Add-on Functionality
•Flight Plans
•Information Requests (FAA, NWS)
•Pilot Comms
•Notifications & Alerts
•Maintenance Record Updates
•Pilot Currency Updates
•Concierge Service Arrangements
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
Ground-Based Systems & Services
Client Interface
Operator
Interface
Primary Data
Storage
Secondary Data
Storage
Data/Operations
Hosting
Flight Planning
SW
Aircraft-GASS
Comms Data Link
Telephone
Individual Stations
Magnetic Tape
Magnetic Tape
Self-hosted
COTS
Cell Phone
Network
Internet
Grouped Stations
Optical Disk
Optical Disk
Primary: Self,
Secondary:
Sourced
Modified COTS
SATCOM - Iridium
like
Email
Shared Stations
Network Attached
Storage
Storage Area
Network
Tape Library
Optical Jukebox
Network Attached
Storage
Storage Area
Network
Tape Library
Optical Jukebox
All Sourced
New Development
Satcom - wide
bandwidth
All
Limiting factors = COTS
equipment, wireless
installations, and 32 kbs
transmittal rate
LinkTV WADL
HF
ACARS
NATS
Terrestrial Flight
Telephone System
(TFTS)
Gatelink
SkyLink
VHF Digital Link
Mode 2
Downselection achieved
through utility analysis
Air-Based Systems & Services
Onboard
Processing
Pilot Visual
Interface
Pilot Audio
Interface
Integration
Interface
Data Recorder
Physiological
Sensing
Aircraft Hull &
Systems Sensing
Sensor
Monitoring
HW/SW
Flight Tracking
Hand-held
Electronic Flight
Bag
Unique/Add-on
Unique/Add-on
Wireless
Solid State
Flight Stick
Biomedical
Sensors
Existing System
Sensors
Passive Sensing
Piggy-back
Manufacturer
Installed System
Existing Interface
Hardwired
Digital Tape
Apparel Biomedial
New, GASSSensors (e.g. flight
mandated sensors
suit)
Active Sensing
Proprietary
Sattelite System
Hard Drive
Movement
Sensing Suite
Analysis (e.g.
control use & seat
movement)
Passive: Lesscritical Data,
Active: Critical
Data
Board/card
(inserted to aircraft Existing Interface
computer)
Coshare Existing
Computer
22
Dedicated
Computer/Box
Wireless &
Hardwired
Existing sensors
with new GASS
additions
Utility Analysis
Weighted evaluation of
stakeholder value per area
used to determine final utility
function
Safe, Effective National
Transportation System
Safe, Effective Air
Transport System
Weights used for
architectural-level
analysis
Viable GASS
System
Cost (25%)
Expected Cost (12%)
Risk Impacts (13%)
Weights used for
system-level
analysis
Performance (25%)
Ilities (50%)
Reliability (16%)
Usability (15%)
Complexity (11%)
Availability (8%)
WeightUtility(Relative)=∑WeightStakeholder*ValueStakeholder
23
Feasibility (9%)
Expected
Performance (16%)
Management - Risk
Probability
5
4
10
2
1, 7
Consequence Scale
3, 4,
6, 9
Level
Cost
Schedule
Technical Performance
1
Minimal or No
Impact
Minimal or No Impact
Negligable to no change
in functionality and
usability.
2
<5% Cost
Variance
Minimal schedule
change: 2% - 5%
Minimal change to
functionality and usability.
3
5-10% Cost
Variance
Minor schedule slip:
> 5%
Minor changes to
functionality are required
to prevent undesirable
work-arounds.
Moderate schedule slip:
> 10%
Moderate changes for
basic functions are
required to meet desired
requirements. No workarounds available.
Major schedule slip:
> 15%
Major changes for basic
functions are required
due to user rejection or
inability to meet major
requirements.
8
3
2
5
1
4
A
B
C
D
Consequence
Top Risks Identified
10-20% Cost
Variance
E
5
> 20% Cost
Variance
1. Loss of contact/communications
Probability of Occurrence Scale
2. Incompatibility with Existing Manufacturer-Installed Sensor Suite Level
Description
Remote - 10 %
A
3. FAA NOTAMs & TFR Procurement Issues
Unlikely - 30 %
B
Likely - 50 %
C
4. NWS Weather Data Procurement Issues
Highly Likely - 70 %
D
5. Physiological Sensor Suite Lack Robustness
Near Certainty - 90 %
E
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
General Aviation
Support System
1. Project
Management
2. System
Definition &
Decomposition
3. Component
Development
4. System
Integration &
Qualification
 Vetted work breakdown
structure (WBS) constructed
based on system lifecycle
•
1.1 Cost
Management
2.1 CONOPS
3.1 Flight
Planning
4.1 Integration
1.2 Schedule
Management
2.2 Requirements
3.2 External
Interfaces
4.2 Verification
1.3 Performance
Management
2.3 Specifications
3.3 Records
Maintenance &
Analysis
4.3 Validation
1.4 Integration
Management
2.4 Lifecycle
Support
3.4 Data
Management
4.4 Acceptance
1.5 HR
Management
2.5 VV&A Plan
3.5 Situational
Monitoring
4.5 Milestone 4
1.6
Communication
Management
2.6 Milestone 2
3.6 Aircraft
Hull/Systems
Analysis
•
1.7 Risk
Management
3.7 Physiological
Monitoring &
Analysis
1.8 Procurement
Management
3.8 Data Transfer
&
Communications
25
3.9 Milestone 3
•
Currently developed to system
acceptance
Verification & Validation
accomplished throughout
Component Development
Entrance/exit criteria and
deliverables well defined
 Corporate structure
established
•
•
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
Engineering
Manager
Operations
Manager
Systems
Engineer
Software
Engineer
Electrical
Engineer
Mechanical
Engineer
Computer
Engineer
Computer
Scientist
Production
and Testing
Flight Planning
(Project Manager)
External Interfaces
(Project Manager)
Records Maintenance
& Analysis
(Project Manager)
Data Management
(Project Lead)
Project responsibility
Situational Monitoring &
Analysis
(Project Manager)
Aircraft Hull/Systems
Monitoring & Analysis
(Project Manager)
Physiological Monitoring
& Analysis
(Project Manager)
Data Transfer &
Communications
(Project Manager)
27
Project Support Office
(Administration)
Matrix organization selected due to potential for
rapid business expansion; free flow and access
to information and personnel required
Quality
Assurance
Integrated
Logistics
Support
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 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
Quality Flight
Plan
Formulation
Pilot awareness
of External
Conditions
Notification of
problems
Completeness
of Support
Services
Awareness of
Incipient In-flight
Problems
Notification of
routine due
events
General
Ease of access
Ubiquity of
access
Support in case
of emergency
High Availability
Aircraft Status
Communication
with Associates
Timely Service
Response
Accurate
Service
34
Cost Effective
Installation &
Services
Needs derived from
use cases and
stakeholder
discussions
Detailed Stakeholder Analysis
General Aviation Support System (GASS) Need Evaluation Matrix
9/29/2008
Value Scale
4
3
2
1
0
35
Capability is critical to stakeholder satisfaction
Capability has major marketable value to
stakeholder
Capability has some worthwhile marketable value to
stakeholder
Convenient, but unnecessary capability to
stakeholder
Provides no relative value to
stakeholder/stakeholder indiferent
4
4
3
2
2
1
1
Associates
Relative Weight
Aircraft Status Communication with Associates
N2
Sys Devloper
N2.4
N1.1
N1.2
Fixed Base Op
N2.1
N2.2
N2.3
Preflight Needs
Thorough/Quality Flight Plan Formulation
Completeness of Support Services
In-flight Needs
Pilot awareness of External Conditions
Awareness of Incipient In-flight Problems
Support in case of emergency
N1
Aircraft Manf
Need
FAA
Need No.
Owner
From use
cases
Pilot
Stakeholders Value
4
4
3
3
4
4
3
3
1
4
4
4
0
2
52
60
4
4
4
3
4
4
4
4
4
3
4
4
1
3
3
4
4
4
3
3
3
55
65
65
4
4
1
3
1
3
4
50
Relative Stakeholder Weights
Pilot/Customer
Owner
FAA
Aircraft Manufacturer
Fixed Base Operator
GASS System Developer
User Associates (Family, Friends, Business Partners)
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
General Aviation Support System
5 Top level use
cases developed
«uses»
Provide Preflight
Services
«uses»
Pilot
«uses»
«uses»
«uses»
«uses»
Manage Pilot
Records
«uses»
Provide Real Time
Condition Monitoring
«uses»
«uses»
External Data Providers
«uses»
FAA
Provide Emergency
Support
«uses»
«uses»
«uses»
Manage Aircraft
Records
Aircraft Owner
«uses»
Fixed Base Operator
37
Aircraft Systems
System Architectural Choice #1
Maximum Centralization
Flight Computer
Intercomm
Ops Center
Aircraft
Systems
Pilot pre-flight
Controller
High Data Rate
Datalink
FBO
Ops Center
Aircraft
Manufacturers
System Boundary
1
User
Interface
Aircraft
Ops
Center
#1
38
External
Interfaces
(Weather,
FAA, FBOs
FAA
Weather
System Architectural Choice #2
Decentralized System / Max on-aircraft processing
Flight Computer
Pilot pre-flight
Ops Center
West
Ops Center
Mid
Intercomm
Aircraft
Systems
Ops Center
East
Controller
Recorder
Datalink
FBO
System Boundary
User
Interface
39
FAA
Ops
Center
#1
Ops
Center
#2
Aircraft
Manufacturers
Aircraft
Ops
Center
#3
Ring
Network
External
Interfaces
(Weather,
FAA, FBOs
Ops Center
Weather
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
Acquire External
Data (includes data
updating)
Acquire Aircraft
Related Data
Provide aircraft ground
communications
Support
Operations
Provide system
availability
Provide telephonic
user interface
Provide User
Identification and
Authentications
Acquire user
profile data
Acquire Navigation
Data
Provide data
communications
Prepare flight
plans
Provide high
assurance of
communications
Provide email user
interface
Provide data
confidentiality
Acquire air
navigation support
data (maps, etc)
Acquire Aircraft
Condition Data
Provide voice
communications
Track On-going
flights
Provide high
system availability
Provide web-based
user interface
Provide data
integrity
Acquire weather
data
Acquire
NOTAMs/TFRs
Acquire Pilot
Physiology Data
Acquire air traffic
data
41
System functions developed to 3rd level detail;
top 2 levels shown here
Record Operations
Center Activity
Process Acquired
data
Provide alerts and
notifications
IDEF0 Activity Diagrams
OV-5
Provide General
Aviation Services
F0
Issue Trigger
Inflight Support Request
Aircraft Availability
Associate Comms Request
Concierge Service Request
Flight Plan Request
User Information, Destination, Flight Plan Approval
FBO Service Appointment
FAA NOTAMs & TFRs, Weather Updates
Pilot Condition
Aircraft Condition
Pilot Comms Response
Maintenance Update, Currency Update
Weather Request, FAA NOTAM & TFR Request
User Information Request, Destination Request
Feasible Flight Plan, Flight Plan, Flight Plan Summary
FBO Service Request, Reservations, Maintenance Records
Situational Monitoring Response, Emergency Services Alert
Pilot Communications, Associate Notifications
Maintenance Notifications, Pilot Currency Notifications, Maintenance Records
Operations Center
Onboard Processing Hub
42
NODE:
F-1
TITLE:
OV5 CONTEXT DIAGRAM
NO.:
1
IDEF0 Activity Diagrams
OV-5
Issue Trigger
Provide Flight
Planning Support
Inflight Support Request
Associate Comms Request
Aircraft Availability
Concierge Service
Request
Flight Plan Request
User Information,
Destination, Flight Plan
Approval
Weather Request, FAA NOTAM & TFR Request
User Information Request, Destination Request
Feasible Flight Plan, Flight Plan, Flight Plan Summary
FBO Service Appointment
FBO Service Request, Reservations, Maintenance Records
F1
( )
FBO Service Request
Flight Plan
Maintenance Records
FAA NOTAMs & TFRs, Weather Updates
Pilot Communications
Situational Monitoring Response
Provide Inflight
Support
F2
( )
Pilot Comms Response
( )
Emergency Services Alert
Operations Center
Aircraft Condition
Onboard Processing Hub
Pilot Condition
Manual Maintenance Update,
Manual Currency Update
Associate Notifications
Maintenance Notifications,
Pilot Currency Notifications
Diagnostics
Flight Tracks
Provide
Postflight
Support
Maintenance Records
F3
( )
Pilot Records
Pilot Records
43
Maintenance Records
NODE:
F0
TITLE:
OV5 PROVIDE GENERAL AVIATION SERVICES
NO.:
2
IDEF0 Activity Diagrams
OV-5
Aircraft Availability
Flight Plan Request
Request Flight
Plan
User Information Request
Destination Request
Flight Plan Request
F1.1
Weather Request
User Information
NOTAM & TFR Request
Concierge Service Request
Destination
Initiate Flight
Plan
Flight Plan Request
F1.2
Destination Information
Aircraft Data
Weather Updates
Create Flight
Plan
Flight Plan
FAA NOTAMs & TFRs
F1.3
Approved Flight Plan
Feasible Flight Plan
Assess Flight
Plan Feasibility
PilotRecords
Maintenance Records
Load Into Aircraft
F1.8
F1.4
FBO Service Appointment
Flight Plan
Provide
Concierge
Service
FBO Service Request, Reservations
Maintenance Records
F1.5
Forward Flight
Plan To User For
Review
Flight Plan Approval
Feasible Flight Plan
F1.6
Approved Flight Plan
File With FAA
Flight Plan Summary
F1.7
44
NODE:
F1
TITLE:
OV5 PROVIDE FLIGHT PLANNING SUPPORT
NO.:
3
IDEF0 Activity Diagrams
OV-5
Provide Realtime Aircraft
Condition
Monitoring
(RACM)
Associate Comms Request
Aircraft Condition
Issue Trigger
Inflight Support Request
Pilot Condition
Inflight Support Request
Alerts
Diagnostics
F2.1
Emergency Services Alert
FAA NOTAMs & TFRs
Weather Updates
Provide Pilot
Assistance
Situational Monitoring Response
Pilot Communications
F2.2
Pilot Comms Response
Communicate
With Associates
Associate Notifications
F2.3
45
NODE:
F2
TITLE:
OV5 PROVIDE INFLIGHT SUPPORT
NO.:
4
IDEF0 Activity Diagrams
OV-5
Flight Plan
Provide Aircraft
RACM Data
Support
Diagnostics
Flight Tracks
FBO Service Request
Incipient Failure Alerts
F3.1
Maintenance Update
Provide Aircaft
Record
Maintenance
Service
Maintenance Notifications
Maintenance Records
F3.2
Provide Pilot
Flight Records
Services
Currency Update
Pilot Currency Notifications
Pilot Records
F3.3
46
NODE:
F3
TITLE:
OV5 PROVIDE POSTFLIGHT SUPPORT
NO.:
5
IDEF1X Data Model
OV-7
GASS OV7 IDEF1X DATA MODEL
1
«enumeration»
User Information Request
+UserIDRequest
+PasswordRequest
«enumeration»
Destination Request
+LocationRequest
+Timeframe
«enumeration»
Flight Plan Request
+Name(FK)
+PlanningServiceRequest
-Provided By
-Initiates
«enumeration»
FAA NOTAM & TFR Request
+FAARequest
+Location(FK)
+Time(FK)
*
-Acquires
-Finds
*
1
-Defines
«enumeration»
Weather Request
+WeatherConditionRequest
+Location(FK)
+Time(FK)
*
-Initiated By
1
-Defines
«enumeration»
Destination
+Location
+Time
*
*
*
-Basis OfInput To
-Provides
-Checked-Basis
For Of
«enumeration»
Pilot Records
+Name (FK)
+Pilot Currency (FK)
+Currency Issue (FK)
*
-Enables
-Constrained By
*
1
*
-Utilizes
-Notifies
«enumeration»
FBO Service Request
11
-Utilized In +Name(FK)
-Found By
+Location(FK)
+Time(FK)
«enumeration»
*
+AircraftID(FK)
User Information
+MaintenanceData(FK)
+Name (FK)
+FBORequest
+Pilot Currency (FK)
-Enables
+MaintenanceData (FK)
1
+Currency Issue (FK)
1
-Enabled By
+Preferences
+UserID()
-Constrains
+Password()
«enumeration»
Currency Update
+Name
+Pilot Currency
-Updated By
*
*
*
-Starts Tracking
-Enables
*
«enumeration»
Aircraft Data
+AircraftID
+AircraftSpecs
-Enabled By
47
*
*
*
-Incited By
-Enabled By
*
*
-Incites
*
*
-Basis Of
-Tracking Started By
-Checked Against
*
«enumeration»
Pilot Currency Notifications
+Name (FK)
+Pilot Currency (FK)
+Currency Issue
-Incites
-Incited By
*
-Used In
-Notifies By
*
-Enabled
By
-Enables
*
«enumeration»
Aircraft Condition
+HullData
+SystemData
+Name(FK)
+AircraftID(FK)
+FlightPath(FK)
-Warns
*
-Pulls Up
*
*
«enumeration»
Diagnostics
+HullAnalysis
+SystemAnalysis
+Name(FK)
+AircraftID(FK)
+HullData(FK)()
+SystemData(FK)()
*
*
-Developed From
By
-Enabled-Triggered
By
*
*
*
-Warns
*
*
«enumeration»
-Defines Location
Reservations
+Name(FK)
+ReservationTime
*
+HotelInformation
*
+RestaurantInformation
+Preferences(FK)()
«enumeration»
Alerts
*
+PhysiologicalAlert
+HullAlert
+SystemsAlert
-Initiates*
+HeadingAlert
+Name(FK)
+AircraftID(FK)
-Initiated By
+FlightPath(FK)
*
+FlightHeading(FK)
+Speed(FK)
+Lattitude(FK)
-Triggers
+Longitude(FK)
«enumeration»
Issue Trigger
+PhysiologicalTrigger
+HullTrigger
+SystemsTrigger
+PathTrigger
+Name(FK)
+AircraftID(FK)
+FlightPath(FK)
+NOTAM(FK)()
+TFR(FK)()
+WeatherReport(FK)()
+HullData(FK)()
-Initiates
+SystemData(FK)()
+PhysiologicalData(FK)()
1
-Enables
«enumeration»
Flight Plan
+Name(FK)
+Location(FK)
+Time(FK)
+NOTAM(FK)
+TFR(FK)
+WeatherReport(FK)
+AircraftID(FK)
+FlightPath(FK)
+AircraftFormat()
*
-Defines Location-Provides Info
1
«enumeration»
Emergency Services Alert
+AlertType
+ServiceNeeded
+Name(FK)()
+AircraftID(FK)()
+FlightPath(FK)()
+FlightHeading(FK)()
+Speed(FK)()
+Lattitude(FK)()
+Longitude(FK)()
*
*
-Triggers
-Located
By
«enumeration»
Situational Monitoring Response
+AutomaticNotification
+AdvisoryResponse
+EmergencyResponse
+PhysiologicalAlert(FK)
+HullAlert(FK)
+SystemsAlert(FK)
+HeadingAlert(FK)
+Name(FK)()
+AircraftID(FK)()
+FlightHeading(FK)()
+Speed(FK)()
+Lattitude(FK)()
+Longitude(FK)()
-Initiated By
*
«enumeration»
Associate Notifications
+AssociateID
+Name(FK)()
+Location(FK)()
+Time(FK)()
*
1
-Constrained By
«enumeration»
Flight Plan Approval
+CustomerApproval
+OperatorApproval
-Approves
«enumeration»
Approved Flight Plan
+Name(FK)
+Location(FK)
+Time(FK)
+NOTAM(FK)
+TFR(FK)
+WeatherReport(FK)
+AircraftID(FK)
+FlightPath(FK)
+CustomerApproval(FK)()
+OperatorApproval(FK)()
1
«enumeration»
Flight Plan Summary
+Name(FK)
+Location(FK)
+Time(FK)
+AircraftID(FK)
+FlightPath(FK)
+FAAFormat()
-Approved By
1
-Summarized By
11
-Summarizes
*
«enumeration»
-Info Obtained From
Associate Comms Request
+VerbalPilotRequest(FK)
+AssociateID
+Name(FK)
+Location(FK)
+Time(FK)
*
*
-Initiated By
«enumeration»
*
*
Incipient Failure Alerts
-Locates
+MaintenanceIssues
*
+Name(FK)
-Triggered By
-Locates
+AircraftID(FK)
*
+HullAnalysis(FK)()
-Constrains
+SystemAnalysis(FK)()
«enumeration»
+FlightHeading(FK)()
Maintenance
Notifications
-Updates
-Based
-Located
By On +Speed(FK)()
+MaintenanceRequirements
+Name(FK)
*
*
+AircraftID(FK)
-Basis Of
*
+MaintenanceIssues(FK)()
«enumeration»
Flight Tracks
+FlightHeading
+Speed
+Lattitude
+Longitude
-End21
1
«enumeration»
Feasible Flight Plan
+Name(FK)
+Location(FK)
+Time(FK)
*
+NOTAM(FK)
1
-Enabled
By
1
+TFR(FK)
*
-Enables
+WeatherReport(FK)
-Provides History To
1
1
-End Determined
From +Aircraft(ID)
«enumeration»
+FlightPath(FK)
Weather Updates
+Constraints()
-Constrained
By
+WeatherReport
+MaintenanceData(FK)()
+MaintenanceRequirements(FK)()
+Position(FK)()
*
-Develops
*
-Provides
Input To
-Updated
By
*
«enumeration»
Maintenance Update
+Name
+MaintenanceData
+AircraftID
«enumeration»
Pilot Condition
+PhysiologicalData
+Name(FK)
+AircraftID(FK)
+FlightPath(FK)
«enumeration»1
Inflight Support Request
+MonitorRequest
+Name(FK)
+AircraftID(FK)
+FlightPath(FK)
+VerbalPilotRequest(FK)()
-Updates
-End24
«enumeration»
FBO Service Appointment
+Name
+AppointmentTime
+ServiceType
+AircraftID(FK)()
+MaintenanceData(FK)()
-Enabled By
*
-End22
«enumeration»
Aircraft Availability
+AircraftID
+Status
+Time(FK)()
-Constrains
«enumeration»
Maintenance Records
+Name (FK)
+MaintenanceData (FK)
+AircraftID (FK)
+AircraftSpecs(FK)
+MaintenanceRequirements(FK)()
*
+Location(FK)()
+Time(FK)()
-Incited By
-Associated With
-Updates
*
«enumeration»
Notional Flight Plan
+Name(FK)
+Location(FK)
+Time(FK)
+NOTAM(FK)
+TFR(FK)
+WeatherReport(FK)
+AircraftID(FK)
+FlightPath
-Identifies
+Status(FK)()
1
-Provided By
*
*
-Provided
-Location Defined
ByBy
1
*
*
*
*
*
-Incited By
-Locates
«enumeration»
Concierge Service Request
+Preferences(FK)
+Name(FK)
+Location(FK)
+Time(FK)
-Location Defined By
+AircraftID(FK)
+ConciergeRequest
*
-End23
«enumeration»
-Warns
FAA TFRs
+TFR
-Incited By
* Of -Updated
-Is a Part
1 By
1
-Enables
+Location(FK)()
+Time(FK)()
-Provided By
-Locates
*
-Locates
*
«enumeration»
FAA NOTAMs
+NOTAM
*
*
*
-Locates
1
-Initiated By
-Enabled By
1
*
-Initiates
«enumeration»
Pilot Comms Response
-Determined By *
-Initiates
*
+VerbalResponse(FK)
+AutomaticNotification(FK)()
*
+AdvisoryResponse(FK)()
+EmergencyResponse(FK)()
-Responds To
*
*
-Determines
-Can Enable
*
«enumeration»
Pilot Communications
+VerbalPilotRequest
+VerbalPilotResponse
+AutomaticNotification(FK)
+AdvisoryResponse(FK)
+EmergencyResponse(FK)
*
+Initiates
+Initiated By
SV-2
Aircraft Node
User Interface
Node
Physiologic
Sensors
Aircraft
Systems
Sensors
Telephone
Fax
E-mail
Web-Enabled
Data
Recorder
Aircraft Systems Interface
Central Computer
Datalink
Ground Node
Datalink
Backup Facility
Telecommunications Interface
Operator
Workstations
Storage
Servers
Master Displays
48
Datalinks
External
Interfaces
Weather
FAA
Geographic
FBOs
Telecommunications
Interfaces
Servers
Storage
System Functions
(SV-4 Format)
User (on
ground)
A/C
Systems
Acquire
Aircraft
Related
Data
Provide
User
Interface
Impetus of DODAF
System View (SV)
development
FAA
Weather
Pilot (in
air)
Support
Operations
Provide Air
Ground
Comms
Acquire
External
Data
Support functions that undergird system
Provide
Information
Assurance
49
Provide
System
Availability
Request Flight Plan SV10b
Customer Interface
Ops Center Interface
Flight Planner
Database Manager
Analysis Manager
Delivery System
Request Flight Plan
Confirm Details
Initiate Planning
Request Planning Data
Planning Data
Initial Plan
Feasibility Check Results
Updated Plan
Delivery to Customer
Customer Updates
Final Plan
Final Plan
Delivery to FAA
Loaded into aircraft
50
Aircraft Communications SV-10b
Data Manager
Flight Tracker
Analysis Manager
External Data
Alert Manager
Communications
Aircraft Side
Communications
Ground Side
Aircraft Updates
Aircraft
Systems
Interface
Aircraft
Controller
Aircraft Status
Flight Status Update
Alert
Alert
Pilot
Physiology
interface
Aircraft Data
Weather and FAA Updates
Weather and FAA Updates
Aircraft Tracks
Alerts
Alert
Alert
Systems Trigger
Physiology Trigger
Emergency Evaluation Aircraft Emergency
Aircraft Emergency
Aircraft Emergency
Weather/FAA Updates
Emergency Update
Pilot Communications
Pilot Response
51
Pilot
Interface
Maintain Records SV-10b
Aircraft Manager
Data Manager
Analysis Manager
Alert Manager
Customer Interface
Flight Systems Records
Flight Duration Records
Pilot Records
Pilot Record Issues
Pilot Record Issues
Piot Record Notices
Aircraft Systems History Record
Pilot Record Updates
Aircraft Systems Issues
Aircraft Systems Issues
Aircraft Systems Issues
Aircraft Maintenance Updates
Data base Updates
52
Component Diagram for SV-10b
Database Manager
Analysis Manager
Alert Manager
Pilot Record
Routine Alert
In-flight Conditions
Advisory Alert
Flight Plan Feasibility
Emergency Alert
Map
FBOs
Weather
A/C Inflight (short-term)
FAA Traffic
Aircraft Systems History
Pilot Record
Flight Plans
Customer Profile
NOTAMS / TFRs
Aircraft Maintenance
53
Aircraft Systems History
COMPLEXITY
Rating
Value
0
10
2
5
4
2.5
6
1.25
8
0.625
10
0
Description:
An assessment of the level of effort required in the
development, integration, and/or installation of a
technology or item; higher complexity provides
less utility due to potential issues
Function:
Cx
D
Ax3
Bx2
-0.0166
0.3807
-3.1428
9.9752
54
Utility
Sample Utility Function
10
9
8
7
6
5
4
3
2
1
0
Complexity
y = -0.0166x3 + 0.3807x2 - 3.1428x + 9.9752
R² = 0.9998
0
2
4
6
Rating
8
10
3
3
2
3
2
4
1
55
Aircraft Manf (3)
Fixed Base Op
(2)
Sys Devloper
(4)
Associates (1)
4
1
4
1
3
4
4
3
4
2
4
1
2
4
4
3
1
1
4
1
1
1
4
4
4
2
4
4
4
4
4
4
0
1
3
1
1
4
3
1
4
4
4
4
4
4
4
4
0
1
4
1
1
4
3
1
Relative Stakeholder Weights
Pilot/Customer
Owner
FAA
Aircraft Manufacturer
Fixed Base Operator
GASS System Developer
User Associates
4
3
2
1
0
Utility Weight
(% of Total)
FAA (2)
Cost
Availability
Reliability
Feasibility
Complexity
Usability
Performance
Risk
Owner (3)
A weighted evaluation of
stakeholder desires to
determine overall Utility
equation
Pilot (3)
Stakeholders Value
Relative Weight
Stakeholder Utility Weighting
54
36
70
39
48
66
69
57
Total:
0.12
0.08
0.16
0.09
0.11
0.15
0.16
0.13
1.00
Value Scale
Driver is critical to stakeholder satisfaction
Driver has major value to stakeholder
Driver has some worthwhile value to stakeholder
Convenient or minimal to stakeholder satisfaction
Indifferent or no relative value
Cost
Ility
Ility
Tech
Ility
Ility
Tech
Cost
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
Flying
Rate
Facilities
Cost
Utilities
Cost
NPV
Full
SMS
Cost
Voice
Cost
Routine
Contact
57
Price
Multiple
GASS Summary Schedule
58