Embed Size (px)
Citation preview
General Aviation Support System (GASS)
GMU SEOR Master’s Project
SYST 798John Glaeser
Linda JarusewskiMark LocherMobeen 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
Background Solution GASS Market Plan & Costing System/Project Scope & Methodology System Architecture Systems Engineering Management Considerations Summary & Project Conclusions Q&A
4
The Problem & Background
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
Aviation Accident Causes
0%
10%
20%
30%
40%
50%
60%
Pilot Error MechanicalFailure
Weather Other humanerror
Sabotage OtherCauses
Cause of Accident
Per
cent
age
Aviation Accident Causes 1950-2006*
* Courtesy of the Aircraft Crashes Record Office; Geneva, Switzerland
** Courtesy of the U.S. National Safety Transportation Board
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
• Subscription-fee based service Goal: To deliver a system with basic functionality in 2010,with increments adding aircraft monitoring in 2011 andfull system coverage in 2012
Courtesy of the Aircraft Crashes Record Office; Geneva, Switzerland
6
Concept of Operations
7
Pilot pre-flight
FAA Weather
Aircraft
Manufacturers
FBO
Ops Center
Intercomm
AircraftSystems
Flight Computer
Ops Center
Datalink
Controller
Recorder
Server Backup(different location)
Server Backup(different location)
(Fixed Base Operators)
(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 engineeringmanagement 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
Aircraft Market Segments120,000
41,000
1,5005,0007,000
30,000
0
20,000
40,000
60,000
80,000
100,000
120,000
140,000
Start Here1
Expand here
2
4
3
**
* Courtesy of Piper Aircraft, Inc **Courtesy of the National Transportation Safety Board
*
10
Market Growth and Segment Penetration
11
Market Penetration
0
5000
10000
15000
20000
25000
0 5 10 15 20 25Year
Siz
e
Full Service
Pilot Only
Aircraft Only
33% Penetration
3% Penetration
11% Penetration
($100,000,000)
$0
$100,000,000
$200,000,000
$300,000,000
$400,000,000
$500,000,000
$600,000,000
0 5 10 15 20 25 30
Ca
sh
Flo
w
Year
Cumulative Cash Flow
Cash Flow Analysis (Cumulative)
12
Payback in ~5 years, Up to 7 years if growth 60% of forecast
Primary cost drivers are manpower & FAA certification
Influence diagram used for cash flow sensitivity analyses
High end $109.95Pilot only $49.95Fleet only $89.95
High end $9,999Pilot only $3,999Fleet only $6,999
Pricing (monthly)
Equipment Revenue
($10,000,000.00)
($5,000,000.00)
$0.00
$5,000,000.00
$10,000,000.00
$15,000,000.00
$20,000,000.00
$25,000,000.00
$30,000,000.00
$35,000,000.00
0 5 10 15 20 25
Year
Sales Forecast Variance: Effects on Cash Flow
Predicted
80% Sales Growth
60% Sales Growth
Cash Flow Variance Analysis(Annual Basis)
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
Predicted Net Present Value (NPV)
(25 years @ 18%): $52.3M
Tornado Diagram
Most significant factors affecting cost
NPV Risk Profile
NPVDPL
SalesGrowth
RatePrice
Multiple
RoutineContact
FlyingRate
VoiceCost
SMSCost
UtilitiesCost Facilities
Cost
Planning• Define Objectives• Determine Scope• Stakeholder analysis• Assumption definition• Project workplan• Intent specification
Analysis• AoA (Utility analyses)• Market analyses• Risk analyses• Cost estimate
Design• System level design following the Department
of Defense Architecture Framework (DODAF) Construction, Implementation, & Operation
beyond scope
Waterfall Development Process
PlanningPlanning
AnalysisAnalysis
DesignDesign
ImplementationImplementation
ConstructionConstruction
3 phases and deliverables iterated to obtain final design
OperationOperation
16
Incremental development process to modularly add functionality in 3 phases
Scope & Context
PlanningPlanning
AnalysisAnalysis
DesignDesign
ImplementationImplementation
ConstructionConstruction
PlanningPlanning
AnalysisAnalysis
DesignDesign
ImplementationImplementation
ConstructionConstruction
PlanningPlanning
AnalysisAnalysis
DesignDesign
ImplementationImplementation
ConstructionConstruction
Basic Architecture
(Pilot)
Aircraft Increment
Current status - investment and further design
Spiral or waterfall process could be used for future iterations
17
Basic Architecture
(Pilot)
Basic Architecture
(Pilot)
Aircraft Increment
Fin
al I
nc
rem
ent
SV-5A Map
Tracing System Form to Needs
System
FunctionsSV-4
System
Elements
Definition
SV-2
System
Elements
Choice Space
Definition
Morphological
Box, Component Compatibility Matrix
Intent Spec
(ICD) Stakeholder
Value
Decomposition
Utility Values And Weights
Requirements / Capabilities Needs/Req Trace Matrix
Utility Analysis Matrix
System
Elements
Choice Space
SelectionSV-5B Map
Operational
Activities
Architectural
Choice Space
Definition
OV-5
Architectural
Choice Space
Selection
Concept
OV-2
Multiple OV-2s
ProblemMission, Goals, Use Cases, InterviewsStakeholder
Needs
Needs MatrixDocumented Deliverable Traceability
Method
System Review
Complete traceability from system instantiation to problem achieved
GASS Context Diagram
System Boundary
General Aviation Support System
Pre Flight Support
Pre Flight Support
In Flight Support
In Flight Support
Post FlightSupport
Post FlightSupport
Weather (NWS)
Air Traffic (FAA)
Aircraft Systems
Pilot
Aircraft Owners
Fixed Base Operators
Aircraft Manufacturers
* *
*
* *
* Key stakeholders including GASS Developers
UserAssociates*
19
Server Backup
Ops Center
AircraftUser
Interface
External Interfaces(Weather,
FAA, FBOs
Winning System Architectural ChoiceSemi-Centralized Operations
Pilot pre-flight
FAA Weather
Aircraft
Manufacturers
FBO
Ops Center
Intercomm
AircraftSystems
Flight Computer
Ops Center
Datalink
Controller
Recorder
Server Backup(different location)
Server Backup(different location)
System Boundary
First Downselection Utility Results
Potential Architectures Final Scores
Architecture 1
(Centralized) 0.48
Architecture 2
(Decentralized) 0.50
Architecture 3
(Semi-Centralized) 0.55
DODAF
OV-1
DODAF
OV-2
20
GASS p-Diagram
GASS System
Uncontrollables
•Weather•FAA Regulations•Network Delays/Interruptions•Pilot Condition•Aircraft Condition•System Use (Pilot/User)
•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
Controllables
Inputs
•Service Requests•Pilot Data•Pilot Currency•Aircraft Data•Maintenance Records•Destination•Flight Tracks•Pilot Comms Response•FAA NOTAMs & TFRs•NWS Weather Data
Outputs
•Flight Plans•Information Requests (FAA, NWS)•Pilot Comms•Notifications & Alerts•Maintenance Record Updates•Pilot Currency Updates•Concierge Service Arrangements
Summation of information elements and impact factors
21
Morphological Box 2 – 20 potential solutions
per element• Initial reduction based
on top level assessment
Incompatibility and Data Throughput analysis reduced 332.5 M instantiations to 88.2 M
• Limiting factors = COTS equipment, wireless installations, and 32 kbs transmittal rate
Downselection achieved through utility analysis
Onboard Processing
Pilot Visual Interface
Pilot Audio Interface
Integration Interface
Data RecorderPhysiological
SensingAircraft Hull &
Systems Sensing
Sensor Monitoring
HW/SWFlight Tracking
Hand-held Electronic Flight
BagUnique/Add-on Unique/Add-on Wireless Solid State
Flight Stick Biomedical
Sensors
Existing System Sensors
Passive SensingPiggy-back
Manufacturer Installed System
Board/card (inserted to aircraft
computer)Existing Interface Existing Interface Hardwired Digital Tape
Apparel Biomedial Sensors (e.g. flight
suit)
New, GASS-mandated sensors
Active SensingProprietary
Sattelite System
Coshare Existing Computer
Wireless & Hardwired
Hard Drive
Movement Sensing Suite Analysis (e.g.
control use & seat movement)
Existing sensors with new GASS
additions
Passive: Less-critical Data,
Active: Critical Data
Dedicated Computer/Box
Air-Based Systems & Services
Client InterfaceOperator 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 COTSCell Phone
Network
Internet Grouped Stations Optical Disk Optical DiskPrimary: Self, Secondary:
SourcedModified COTS
SATCOM - Iridium like
Email Shared StationsNetwork Attached
StorageNetwork Attached
StorageAll Sourced New Development
Satcom - wide bandwidth
AllStorage Area
NetworkStorage Area
NetworkLinkTV WADL
Tape Library Tape Library HFOptical Jukebox Optical Jukebox ACARS
NATSTerrestrial Flight
Telephone System (TFTS)GatelinkSkyLink
VHF Digital Link Mode 2
Ground-Based Systems & Services
22
Utility Analysis
Safe, Effective National Transportation System
Safe, Effective Air Transport System
Viable GASS System
Cost (25%) Ilities (50%) Performance (25%)
Expected Cost (12%)
Risk Impacts (13%) Expected Performance (16%)
Reliability (16%)
Usability (15%)
Feasibility (9%)
Complexity (11%)
Availability (8%)
Weights used for architectural-level
analysis
Weights used for system-level
analysis
Safe, Effective National Transportation System
Safe, Effective Air Transport System
Viable GASS System
Cost (25%) Ilities (50%) Performance (25%)
Expected Cost (12%)
Risk Impacts (13%) Expected Performance (16%)
Reliability (16%)
Usability (15%)
Feasibility (9%)
Complexity (11%)
Availability (8%)
Weights used for architectural-level
analysis
Weights used for system-level
analysis
Weighted evaluation of stakeholder value per area used to determine final utility function
23
WeightUtility(Relative)=∑WeightStakeholder*ValueStakeholder
Management - RiskPr
obab
ilit
y
Consequence
A B C D E
1
2
3
4
5 1, 7
2
5
8
10 3, 4, 6, 9
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
9. FAA Approval
10. Electromagnetic Interference
Top Risks Identified
LevelABCDE
Remote - 10 %Unlikely - 30 %Likely - 50 %
Highly Likely - 70 %Near Certainty - 90 %
Probability of Occurrence ScaleDescription
Level Cost Schedule Technical Performance
1Minimal or No
ImpactMinimal 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.
35-10% Cost
VarianceMinor schedule slip:
> 5%
Minor changes to functionality are required to prevent undesirable
work-arounds.
410-20% Cost
VarianceModerate schedule slip:
> 10%
Moderate changes for basic functions are
required to meet desired requirements. No work-
arounds available.
5> 20% Cost
VarianceMajor schedule slip:
> 15%
Major changes for basic functions are required due to user rejection or inability to meet major
requirements.
Consequence Scale
Worst risks not catastrophic; easily mitigated through early stakeholder involvement
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
• 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
25
General Aviation Support System
1. Project Management
1.1 Cost Management
1.2 Schedule Management
1.3 Performance Management
1.4 Integration Management
1.5 HR Management
1.6 Communication
Management
1.7 Risk Management
1.8 Procurement Management
2. System Definition &
Decomposition
2.1 CONOPS
2.2 Requirements
2.3 Specifications
2.4 Lifecycle Support
2.5 VV&A Plan
2.6 Milestone 2
3. Component Development
3.1 Flight Planning
3.2 External Interfaces
3.3 Records Maintenance &
Analysis
3.4 Data Management
3.5 Situational Monitoring
3.6 Aircraft Hull/Systems
Analysis
3.7 Physiological Monitoring &
Analysis
3.8 Data Transfer &
Communications
3.9 Milestone 3
4. System Integration & Qualification
4.1 Integration
4.2 Verification
4.3 Validation
4.4 Acceptance
4.5 Milestone 4
GASS Corporate Structure
26
Investors
Investors to provide influence through or as a part of the GASS Board of Directors
GASS
Divisions
GASS Matrix Organization
Records Maintenance & Analysis
(Project Manager)
Software Engineer
Project responsibility
Engineering Manager
Systems Engineer
Electrical Engineer
Mechanical Engineer
ComputerEngineer
Computer Scientist
Integrated Logistics Support
Flight Planning(Project Manager)
Data Management(Project Lead)
Situational Monitoring & Analysis
(Project Manager)
Aircraft Hull/Systems Monitoring & Analysis
(Project Manager)
Physiological Monitoring & Analysis
(Project Manager)
Data Transfer & Communications(Project Manager)
Project Support Office(Administration)
External Interfaces(Project Manager)
Quality Assurance
Production and Testing
Matrix organization selected due to potential for rapid business expansion; free flow and access to information and personnel required
27
Operations Manager
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 post-flight 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• Architecture development• Decision analysis• Requirements generation• Risk analysis• Costing• Scheduling• Organization
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• A business case provides an interesting and unique approach tointegrating prior coursework and personal experience in a practical(although constrained) application
30
QUESTIONS?
Questions?
*Image courtesy of Piper Aircraft, Inc.
31
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
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, semi-centralized, 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
support system implementation
33
Needs Breakdown
Needs derived from use cases and
stakeholder discussions
34
Detailed Stakeholder Analysis
Weighted evaluation used in utility analyses
From use cases
From interviews, market analysis, & discussions
4 Pilot/Customer4 Owner3 FAA2 Aircraft Manufacturer2 Fixed Base Operator1 GASS System Developer1 User Associates (Family, Friends, Business Partners)
Relative Stakeholder Weights
9/29/2008
Pilo
t
Ow
ner
FA
A
Air
cra
ft M
an
f
Fix
ed B
ase
Op
Sys
De
vlo
pe
r
As
so
cia
tes
N1N1.1 Thorough/Quality Flight Plan Formulation 4 3 4 3 1 4 0 52N1.2 Completeness of Support Services 4 3 4 3 4 4 2 60
N2N2.1 Pilot awareness of External Conditions 4 3 4 3 1 4 3 55N2.2 Awareness of Incipient In-flight Problems 4 4 4 4 3 4 3 65N2.3 Support in case of emergency 4 4 4 4 3 4 3 65
N2.4 Aircraft Status Communication with Associates 4 4 1 3 1 3 4 50
Re
lati
ve
We
igh
t
General Aviation Support System (GASS) Need Evaluation Matrix
Need No. Need
Stakeholders Value
In-flight Needs
Preflight Needs
4 Capability is critical to stakeholder satisfaction
3Capability has major marketable value to stakeholder
2Capability has some worthwhile marketable value to stakeholder
1Convenient, but unnecessary capability to stakeholder
0Provides no relative value to stakeholder/stakeholder indiferent
Value Scale
35
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
Concept
36
Use Case Development
37
Provide PreflightServices
Pilot
External Data Providers
Fixed Base Operator
Aircraft Owner
FAA
Aircraft Systems
Provide Real TimeCondition Monitoring
Provide EmergencySupport
Manage PilotRecords
Manage AircraftRecords
General Aviation Support System
«uses»
«uses»
«uses»
«uses»
«uses»
«uses»
«uses»
«uses»
«uses»
«uses»
«uses»
«uses»
«uses»
«uses»
5 Top level use cases developed
System Architectural Choice #1Maximum Centralization
1
Pilot pre-flight
FAA Weather
Aircraft
Manufacturers
FBO
Ops Center
High Data Rate Datalink
Intercomm
Controller
AircraftSystems
Flight Computer
Ops Center
Ops Center
#1
AircraftUser
Interface
External Interfaces(Weather,
FAA, FBOs
System Boundary
38
Ops Center
#3
Ops Center
#1
Ops Center
#2
Aircraft
User Interface
External Interfaces(Weather,
FAA, FBOs
System Architectural Choice #2Decentralized System / Max on-aircraft processing
Pilot pre-flight
FAA Weather
Aircraft
Manufacturers
FBO
AircraftSystems
Flight Computer
Datalink
Intercomm
Controller
Ops Center
Ops CenterEast
Ops CenterEast
Ops CenterEast
Ops CenterMid
Ops Center WestOps Center
MidOps Center
MidOps Center
Mid
Ops Center West
Ops Center West
Recorder
Ring
Network
System Boundary
39
Operational Function Decomposition
Operational functions finalized and decomposed down 4 levels; Top 2 levels shown
•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 -1
Level 0
Level 1
Level 2
Level -2
40
System Function Decomposition
System functions developed to 3rd level detail; top 2 levels shown here41
IDEF0 Activity DiagramsOV-5
TITLE:NODE: NO.: 1F-1 OV5 CONTEXT DIAGRAM
F0
Provide General Aviation Services
Onb
oard Processing H
ub
Operations C
enter
User Information, Destination, Flight Plan ApprovalFBO Service Appointment
Maintenance Update, Currency Update
FAA NOTAMs & TFRs, Weather UpdatesPilot Condition
Aircraft ConditionPilot Comms Response
Fligh
t Plan R
equest
Inflight S
upport R
eque
st
Issue Trig
ger
Con
cierge S
ervice Requ
est
Aircra
ft Availability
Associa
te Com
ms R
equest
User Information Request, Destination RequestFeasible Flight Plan, Flight Plan, Flight Plan SummaryFBO Service Request, Reservations, Maintenance Records
Weather Request, FAA NOTAM & TFR Request
Maintenance Notifications, Pilot Currency Notifications, Maintenance RecordsPilot Communications, Associate NotificationsSituational Monitoring Response, Emergency Services Alert
42
IDEF0 Activity DiagramsOV-5
User Information Request, Destination Request
Flight P
lan R
eque
st
User Information, Destination, Flight Plan
Approval
Pilot Records
Maintenance Records
F1
Provide Flight Planning Support
F2
Provide Inflight Support
F3
Provide Postflight Support
FBO Service AppointmentFeasible Flight Plan, Flight Plan, Flight Plan Summary
FBO Service Request, Reservations, Maintenance Records
Pilot Condition
Aircraft Condition
Pilot Comms ResponseIn
flight S
upport R
equest
Issue T
rigger
Situational Monitoring Response
Associate Notifications
Pilot Communications
Emergency Services Alert
Diagnostics
Flight Tracks
Onbo
ard P
rocessin
g Hu
b
Ope
rations C
enter
TITLE:NODE: NO.: 2F0 OV5 PROVIDE GENERAL AVIATION SERVICES
Pilot Records
Maintenance Records
Weather Request, FAA NOTAM & TFR Request
Con
cierge
Service
Re
quest
FAA NOTAMs & TFRs, Weather Updates
Aircra
ft Availability
( )
( ) ( )
( )
Associate C
omm
s Re
quest
Flight Plan FBO Service Request
Maintenance Records
Maintenance Notifications,Pilot Currency Notifications
Manual Maintenance Update, Manual Currency Update
43
IDEF0 Activity DiagramsOV-5
TITLE:NODE: NO.: 3F1 OV5 PROVIDE FLIGHT PLANNING SUPPORT
F1.1
Request Flight Plan
F1.2
Initiate Flight Plan
F1.3
Create Flight Plan
F1.4
Assess Flight Plan Feasibility
F1.5
Provide Concierge
Service
F1.6
Forward Flight Plan To User For
Review
F1.7
File With FAA
F1.8
Load Into Aircraft
Flight Plan RequestUser Information Request
Destination Request
Flight Plan Request
User Information
Destination
Weather Request
NOTAM & TFR Request
Flight Plan Request
Aircraft Data
Weather Updates
FAA NOTAMs & TFRs
Flight Plan
Destination Information
PilotRecords
Maintenance Records
Flight Plan Approval
Feasible Flight PlanC
oncierge Service R
equest
FBO Service Appointment
FBO Service Request, Reservations
Maintenance Records
Feasible Flight Plan
Approved Flight Plan
Approved Flight Plan
Flight Plan
Flight Plan Summary
Aircraft Availability
44
IDEF0 Activity DiagramsOV-5
TITLE:NODE: NO.: 4F2 OV5 PROVIDE INFLIGHT SUPPORT
F2.1
Provide Real-time Aircraft
Condition Monitoring (RACM)
F2.2
Provide Pilot Assistance
F2.3
Communicate With Associates
Inflight Supp
ort Req
uest
Issue T
rigger
Diagnostics
Alerts
Pilot Comms Response
Pilot Condition
Aircraft Condition
FAA NOTAMs & TFRsWeather Updates Pilot Communications
Asso
ciate Co
mm
s Req
uest
Inflight Support Request
Associate Notifications
Emergency Services Alert
Situational Monitoring Response
45
IDEF0 Activity DiagramsOV-5
TITLE:NODE: NO.: 5F3 OV5 PROVIDE POSTFLIGHT SUPPORT
F3.1
Provide Aircraft RACM Data
Support
F3.2
Provide Aircaft Record
Maintenance Service
F3.3
Provide Pilot Flight Records
Services
Maintenance Records
Pilot Records
Maintenance Notifications
Pilot Currency Notifications
Diagnostics
Flight Tracks
Incipient Failure Alerts
Flight Plan FBO Service Request
Maintenance Update
Currency Update
46
IDEF1X Data ModelOV-7
47
+UserID()+Password()
+Name (FK)+Pilot Currency (FK)+MaintenanceData (FK)+Currency Issue (FK)+Preferences
«enumeration»User Information
+Location+Time
«enumeration»Destination
+CustomerApproval+OperatorApproval
«enumeration»Flight Plan Approval
+AircraftID(FK)()+MaintenanceData(FK)()
+Name+AppointmentTime+ServiceType
«enumeration»FBO Service Appointment
+Location(FK)()+Time(FK)()
+NOTAM
«enumeration»FAA NOTAMs
+Position(FK)()+Time(FK)()
+WeatherReport
«enumeration»Weather Updates
+Location(FK)()+Time(FK)()
+TFR
«enumeration»FAA TFRs
+PhysiologicalData+Name(FK)+AircraftID(FK)+FlightPath(FK)
«enumeration»Pilot Condition
+HullData+SystemData+Name(FK)+AircraftID(FK)+FlightPath(FK)
«enumeration»Aircraft Condition
+AutomaticNotification(FK)()+AdvisoryResponse(FK)()+EmergencyResponse(FK)()
+VerbalResponse(FK)
«enumeration»Pilot Comms Response
+Name+MaintenanceData+AircraftID
«enumeration»Maintenance Update
+Name+Pilot Currency
«enumeration»Currency Update
+Name (FK)+Pilot Currency (FK)+Currency Issue (FK)
«enumeration»Pilot Records
+MaintenanceRequirements(FK)()
+Name (FK)+MaintenanceData (FK)+AircraftID (FK)+AircraftSpecs(FK)
«enumeration»Maintenance Records
+Name(FK)+PlanningServiceRequest
«enumeration»Flight Plan Request
+Preferences(FK)+Name(FK)+Location(FK)+Time(FK)+AircraftID(FK)+ConciergeRequest
«enumeration»Concierge Service Request
+AircraftID+Status
«enumeration»Aircraft Availability
+VerbalPilotRequest(FK)+AssociateID+Name(FK)+Location(FK)+Time(FK)
«enumeration»Associate Comms Request
+NOTAM(FK)()+TFR(FK)()+WeatherReport(FK)()+HullData(FK)()+SystemData(FK)()+PhysiologicalData(FK)()
+PhysiologicalTrigger+HullTrigger+SystemsTrigger+PathTrigger+Name(FK)+AircraftID(FK)+FlightPath(FK)
«enumeration»Issue Trigger
+WeatherConditionRequest+Location(FK)+Time(FK)
«enumeration»Weather Request
+FAARequest+Location(FK)+Time(FK)
«enumeration»FAA NOTAM & TFR Request
+UserIDRequest+PasswordRequest
«enumeration»User Information Request
+Constraints()+MaintenanceData(FK)()+MaintenanceRequirements(FK)()
+Name(FK)+Location(FK)+Time(FK)+NOTAM(FK)+TFR(FK)+WeatherReport(FK)+Aircraft(ID)+FlightPath(FK)
«enumeration»Feasible Flight Plan
+AircraftFormat()
+Name(FK)+Location(FK)+Time(FK)+NOTAM(FK)+TFR(FK)+WeatherReport(FK)+AircraftID(FK)+FlightPath(FK)
«enumeration»Flight Plan
+LocationRequest+Timeframe
«enumeration»Destination Request
+FAAFormat()
+Name(FK)+Location(FK)+Time(FK)+AircraftID(FK)+FlightPath(FK)
«enumeration»Flight Plan Summary
+Name(FK)+Location(FK)+Time(FK)+AircraftID(FK)+MaintenanceData(FK)+FBORequest
«enumeration»FBO Service Request
+Preferences(FK)()
+Name(FK)+ReservationTime+HotelInformation+RestaurantInformation
«enumeration»Reservations
+Name(FK)()+AircraftID(FK)()+FlightHeading(FK)()+Speed(FK)()+Lattitude(FK)()+Longitude(FK)()
+AutomaticNotification+AdvisoryResponse+EmergencyResponse+PhysiologicalAlert(FK)+HullAlert(FK)+SystemsAlert(FK)+HeadingAlert(FK)
«enumeration»Situational Monitoring Response
+Name(FK)()+Location(FK)()+Time(FK)()
+AssociateID
«enumeration»Associate Notifications +VerbalPilotRequest
+VerbalPilotResponse+AutomaticNotification(FK)+AdvisoryResponse(FK)+EmergencyResponse(FK)
«enumeration»Pilot Communications
+Name(FK)()+AircraftID(FK)()+FlightPath(FK)()+FlightHeading(FK)()+Speed(FK)()+Lattitude(FK)()+Longitude(FK)()
+AlertType+ServiceNeeded
«enumeration»Emergency Services Alert
+HullData(FK)()+SystemData(FK)()
+HullAnalysis+SystemAnalysis+Name(FK)+AircraftID(FK)
«enumeration»Diagnostics
+FlightHeading+Speed+Lattitude+Longitude
«enumeration»Flight Tracks
+AircraftID+AircraftSpecs
«enumeration»Aircraft Data
+PhysiologicalAlert+HullAlert+SystemsAlert+HeadingAlert+Name(FK)+AircraftID(FK)+FlightPath(FK)+FlightHeading(FK)+Speed(FK)+Lattitude(FK)+Longitude(FK)
«enumeration»Alerts
+VerbalPilotRequest(FK)()
+MonitorRequest+Name(FK)+AircraftID(FK)+FlightPath(FK)
«enumeration»Inflight Support Request
+HullAnalysis(FK)()+SystemAnalysis(FK)()+FlightHeading(FK)()+Speed(FK)()
+MaintenanceIssues+Name(FK)+AircraftID(FK)
«enumeration»Incipient Failure Alerts
+MaintenanceIssues(FK)()
+MaintenanceRequirements+Name(FK)+AircraftID(FK)
«enumeration»Maintenance Notifications
+Name (FK)+Pilot Currency (FK)+Currency Issue
«enumeration»Pilot Currency Notifications
-Initiated By 1
-Acquires *
-Found By 1
-Finds 1
-Utilizes
1
-Is a Part Of 1
-Pulls Up*
-Provides Input To*
+Status(FK)()
+Name(FK)+Location(FK)+Time(FK)+NOTAM(FK)+TFR(FK)+WeatherReport(FK)+AircraftID(FK)+FlightPath
«enumeration»Notional Flight Plan
+CustomerApproval(FK)()+OperatorApproval(FK)()
+Name(FK)+Location(FK)+Time(FK)+NOTAM(FK)+TFR(FK)+WeatherReport(FK)+AircraftID(FK)+FlightPath(FK)
«enumeration»Approved Flight Plan
-Approved By
1
-Approves 1
-Provided By
*
-Locates
*
-Provided By
*-Locates
*
-Provided By
*
-Locates
*
-End21
1
-End22
*
-End23
1
-End24
*
-Enabled By1-Enables*
-Incited By
*
-Incites
*
-Used In
*
-Basis Of
*
-Triggered By
*
-Triggers
*
-Located By
*
-Locates
*
-Triggered By *
-Triggers
*-Incited By
*
-Incites
*
-Initiated By
*-Initiates
*
-Initiated By
*
-Initiates *
-Initiated By 1
-Initiates
1
-Constrained By
1
-Constrains*
-Provides History To
*
-Checked For*
-Located By*
-Locates
*
-Defines
*
-Basis Of
*
-Defines
*
-Basis Of
* -End Determined From1
-Provides Input To
*
-Updated By
*
-Updates*
-Based On
* -Basis Of *
-Updated By*
-Updates*
-Enabled By*
-Enables*
-Enabled By1
-Enables
*
-Associated With *
-Locates *
-Developed From *
-Develops
*
-Incited By *
-Warns *
-Incited By *
-Warns *
-Incited By *
-Warns*
-Location Defined By
1
-Defines Location
*
-Constrained By
*
-Constrains
1
-Location Defined By
*
-Defines Location 1
-Provided By
1
-Utilized In1
-Initiated By *
-Initiates *-Determined By
*
-Determines*-Responds To *
-Initiates
*
-Info Obtained From
*
-Provides Info *
-Enabled By
*
-Enables*
-Enabled By *
-Enables *
-Tracking Started By
*
-Starts Tracking *
-Checked Against
*
-Identifies
1
-Notifies By *
-Notifies
*
-Enabled By 1-Enables
1
GASS OV7 IDEF1X DATA MODEL
-Constrained By1
-Constrains
*
-Updated By*
-Updates
*
-Summarized By1
-Summarizes
1
+Initiated By*
+Initiates
*
-Enabled By*
-Can Enable
*
-Enabled By
1
-Enables *
SV-2
48
Central Computer
Aircraft Node
Data Recorder
Aircraft Systems Sensors
Datalink
Physiologic Sensors
Aircraft Systems Interface
Central Computer
Aircraft Node
Data Recorder
Aircraft Systems Sensors
Datalink
Physiologic Sensors
Aircraft Systems Interface
User Interface Node
Telephone
Web-Enabled
FaxE-mail
User Interface Node
Telephone
Web-Enabled
FaxE-mail
External Interfaces
Weather FAA
Geographic FBOs
External Interfaces
Weather FAA
Geographic FBOs
Ground Node
Storage
Servers
Telecommunications Interface
Operator Workstations
Master Displays
Datalink
Ground Node
Storage
Servers
Telecommunications Interface
Operator Workstations
Master Displays
Datalink
Ground Node
Storage
Servers
Telecommunications Interface
Operator Workstations
Master Displays
DatalinkBackup Facility
Storage
Datalinks
Servers
Telecommunications Interfaces
System Functions (SV-4 Format)
Impetus of DODAF System View (SV) development
49
Support functions that undergird system
Support Operations
Provide User
Interface
Acquire External
Data
Acquire Aircraft Related
Data
Provide Air Ground Comms
Provide Information Assurance
Provide System
Availability
User (on ground)
FAA
A/C Systems Pilot (in
air)
Weather
Request Flight Plan SV10b
50
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 FAA
Delivery to Customer
Customer Updates
Final Plan
Final Plan
Loaded into aircraft
Aircraft Communications SV-10b
51
Data Manager Flight Tracker Analysis Manager Alert ManagerCommunications
Ground SideAircraft
ControllerCommunications
Aircraft Side
AircraftSystems Interface
External Data
Weather and FAA Updates
Aircraft Tracks
Flight Status UpdateAircraft StatusAircraft Updates
Alerts
Aircraft Data
Weather and FAA Updates
Alert Alert Alert
Pilot Interface
Pilot Physiology interface
Systems Trigger
Physiology Trigger
Alert
Aircraft EmergencyAircraft EmergencyAircraft EmergencyEmergency Evaluation
Emergency Update
Weather/FAA Updates
Pilot Communications
Pilot Response
Maintain Records SV-10b
52
Aircraft Manager Data Manager Alert ManagerAnalysis Manager Customer Interface
Flight Systems Records
Flight Duration Records
Pilot Records
Aircraft Systems History Record
Pilot Record Issues
Aircraft Systems Issues
Pilot Record Issues
Aircraft Systems Issues
Piot Record Notices
Aircraft Systems Issues
Pilot Record Updates
Aircraft Maintenance Updates
Data base Updates
Component Diagram for SV-10b
53
Map
Database Manager
NOTAMS / TFRs
Weather
FAA Traffic
Pilot Record
Customer Profile
FBOs
Aircraft Maintenance
Aircraft Systems History
Flight Plans
In-flight Conditions
Analysis Manager
Aircraft Systems History
Pilot Record
Flight Plan Feasibility
A/C Inflight (short-term)
Emergency Alert
Alert Manager
Advisory Alert
Routine Alert
Sample Utility Function
54
Rating Value0 102 54 2.56 1.258 0.62510 0
Description:
Function:
Ax3 Bx2 Cx D-0.0166 0.3807 -3.1428 9.9752
COMPLEXITY
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
y = -0.0166x3 + 0.3807x2 - 3.1428x + 9.9752R² = 0.9998
0123456789
10
0 2 4 6 8 10
Util
ity
Rating
Complexity
Stakeholder Utility Weighting
55
Pilo
t (3
)
Ow
ner
(3)
FA
A (
2)
Air
craf
t M
anf
(3)
Fix
ed B
ase
Op
(2
)
Sys
Dev
lop
er
(4)
Ass
oci
ates
(1)
4 4 1 4 0 4 0 54 0.12 Cost
1 2 1 2 1 4 1 36 0.08 Ility
4 4 4 4 3 4 4 70 0.16 Ility
1 1 1 4 1 4 1 39 0.09 Tech
3 2 1 4 1 4 1 48 0.11 Ility
4 4 1 4 4 4 4 66 0.15 Ility
4 4 4 4 3 4 3 69 0.16 Tech
3 3 4 4 1 4 1 57 0.13 CostTotal: 1.00
3 43 32 23 12 041
Rel
ativ
e W
eig
ht
Performance
Usability
Complexity
Feasibility
A weighted evaluation of stakeholder desires to determine overall Utility equation
Stakeholders Value
Indifferent or no relative value
FAAOwner
Pilot/Customer Driver is critical to stakeholder satisfactionDriver has major value to stakeholderDriver has some worthwhile value to stakeholder
Risk
Convenient or minimal to stakeholder satisfaction
User AssociatesGASS System Developer
Fixed Base OperatorAircraft Manufacturer
Value ScaleRelative Stakeholder Weights
Reliability
Availability
Cost
Uti
lity
Wei
gh
t
(% o
f T
ota
l)
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
Max transmittal rate of 32 kbs limited potential system solutions56
Influence Diagram
57
NPVFull
FacilitiesCost
UtilitiesCost
FlyingRate
SMSCost
VoiceCost
RoutineContact
PriceMultiple
GASS Summary Schedule
58
