Beruflich Dokumente
Kultur Dokumente
Project
Prepared by
Louis R. Roig
Table of Contents
Project Objectives and Approach...
13
AFDIRTS CONOPS..
14
7.
After all operational objectives had been defined and decomposed, functional
analysis was performed to derive preliminary system functions; these functions were
uploaded into CORE.
A feasibility study was performed to establish feasibility criteria for the AFDIRTS concept.
Once feasibility criteria had been applied to eligible system concepts, a feasible system
concept was defined and effectiveness analysis was performed based upon the ability;
and feasibility of the preliminary system concept to meet the need within cost, time,
technological, operational, safety and regulatory constraints. From this, a preliminary
physical architecture was developed. After a multiple feasible system concepts were
defined the needs validation step was performed. During this phase Measures of
Effectiveness (MOE) were developed based upon interviews and discussions with
potential customers as well as research into the FAAs current FOD detection system
2
Measures of Effectiveness
1. Provide redundancy for components or subsystems deemed High Risk during Failure
Mode, Effects and Criticality Analysis (FMECA) (Binary MOE expressed as a metric of
operational objective 1.1 Provide system redundancy)
2. Detect an unpainted metal cylinder, measuring x inch high and x inches wide; and a
white, grey, or black sphere with the radius of x inches) any time day or night in clear
weather and inclement weather conditions*. (Measurement MOE expressed as a
measurement of operational objective 2.0 Provide automate FOD detection) This MOE
was based in part on current FAA FOD detection system guidance listed in AC
150/5220-24.
3. Capable of retrieving FOD from anywhere on the AOA in under 5 minutes after
detection night and day and in clear and inclement weather conditions* (Binary MOE
expressed as a metric of operational objective 3.0 provide automated FOD retrieval).
4. Capable of autonomous movement on AOAs at a speed of x MPH, during clear and
inclement weather conditions*. (Measurement MOE expressed as a metric of
operational objective 4.3 provide mobile unit locomotion)
5. Detect obstacles at a distance of x feet from mobile units, day and night during clear
and inclement weather conditions *. (Measurement MOE expressed as a metric of
operational objective 4.4 Provide obstacle detection and avoidance)
* Inclement weather conditions is defined as adverse weather that can still sustain flight operations.
At the end of the Needs Analysis phase enough information was available to develop
and submit the SM4 Project Proposal. Additionally, Operational Requirements that were
developed were then utilized as input to the Concept Exploration Phase. In order to
apply the Concept Exploration phase effectively, a system context and multiple
potential system concepts had to be clearly defined. It was necessary to consult with
potential users and subject matter experts so that initial functional and performance
requirements could be accurately formulated. This was accomplished by polling 28
subject matter experts with a questionnaire that was designed and implemented on
the SurveyMonkey web platform.
The analysis of Subject Matter Experts and Users revealed many factors that were
considered during Concept Development. After Operational Requirements Analysis
was performed Performance Requirements Formulation, Implementation Concept
Exploration, and Performance Requirements Validation were applied to the SM4 Project
and an initial set of performance requirements were developed and documented in
CORE. This step was utilized to develop the Requirements Analysis Report.
Finally, the Concept Definition phase of the systems engineering method was
performed by completing Performance Requirements Analysis, Functional Analysis and
Formulation, Concept Selection, and Concept Validation. During this process, three
competing concepts that could potentially solve the need for a FOD Detection and
Retrieval system were explored. The three options were; the Roomba Option, which
made use of roaming mobile units that would continuously search the airfield for FOD
(much like the vacuum Roomba). A ground retrieval option, which made use of existing
FOD detection systems that would continuously sweep the airfield for FOD and then
when found, location would be transmitted to the mobile units for retrieval. And finally,
the Airborne Option which operated much like the ground retrieval option except the
retrieval units were airborne.
Informal trade studies revealed many advantages to the Airborne Option. Some of
which were; mobile unit speed, ability to navigate above obstacles, ability to cross
unpaved surfaces and ease of FOD disposal. Additionally, it is believed that future
versions, could incorporate bird deterrent functionality. The Airborne Option was
selected and Functional and Physical architecture were developed. A System
4
AFDIRTS Description
FOD damage to aircraft occurring at critical moments in flight has led to loss of life and
complete destruction of aircraft. An example of this was Air Frances flight 4590, a
Concorde, on a scheduled international flight from Paris to New York City that crashed
killing all 109 people onboard after a titanium alloy strip, 17.1 inches long and about 1.3
inches wide ruptured a tire and sent a piece of it through the wing during takeoff.
The AFDIRTS was designed to provide a safe autonomous method of detecting,
identifying, removing and tracking FOD from Airport Operation Areas (AOAs) 24 hours
a day 7 days a week while not interfering with normal airport operations. The AFDIRTS is
capable of centralized command and control from the Air Traffic Control Tower and is
capable of operation in inclement weather. The AFDIRTS was designed to be reliable,
affordable and maintainable. AFDIRTS Key Performance Parameters have been listed
below.
System Segments
The AFDIRTS consists of six major segments; The Command and Control Segment,
System Health and Monitoring Segment, FOD Detection Segment, Air Retrieval Vehicle
(ARV) Segment, Power and Housing Segment and the FOD Analysis Segment.
11
12
Air Traffic
Control
Environment
Heat (E)
Sound (E)
Rain (M)
Resistance (E)
Wind (F)
Snow (M)
GPS Signals (D)
Gravity (F)
Inertia (F)
Barometric
Pressure
Obstacles
Airport
Managers
AFDIRTS
Aircraft
Operators
Forces (F)
Energy (E)
Data (D)
Signals (S)
Materials (M)
Parts (M)
Materials (M)
Fault Codes (D)
System Health (D)
Power
Parts (M)
Materials (M)
SW Update (S)
Maintenance Commands (D)
FOD
Maintainer
13
Command
and Control
Maintenance
FOD
Detection
Obstacle
Detection and
Avoidance
FOD
Disposal
FOD Retrieval
14
Originating Requirements
R Need Statement
Requirement Statement:
The Airfield FOD Detection, Identification, Removal and Tracking System (AFDIRTS)
is to provide a safe autonomous method of detecting, identifying, removing and
analyzing FOD trends from airports while not interfering with normal airport
operations. The AFDIRTS will provide a method of centralized command and
control (KPP R.2.1) and be capable of operation in inclement weather. The
AFDIRTS shall be reliable, maintainable and affordable.
Refined By Subordinate Requirements:
R.1 Safe Operation
R.2 System Command and Control
R.3 FOD Scanning and Detection
R.4 FOD Reporting
R.5 FOD Retrieval
R.6 Mobile Unit Locomotion
R.7 Provide FOD Trend Analysis
R.8 System Communication
R.9 Technical Support
R.10 Installation and Acceptance Standards
R.11 Reliability, Availability and Maintainability
R.12 Operate in Adverse Weather Conditions
15
Originating Requirements
R.1.1
R.1.1.1
refined by
verified by
Emergency
Demonstration
Requirement
VerificationRequ...
refined by
verified by
Execution Speed
Test
Requirement
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall not cause damage to airport personal or property; nor shall it
become a distraction to operations or support personnel.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.1.1 Emergency
Based Upon Operational Objective:
OO-1 Provide safe operation
16
Originating Requirements
R.2.1
refined by
refined by
R.2.2
R.2.3
refined by
R.2.4
refined by
verified by
Command and
Control System
System Command
Location of
Aircraft
Unsuitable FOD
Power Failure
Test
Function
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
Test
Test
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall be capable of centralized command and control of all system
elements.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.2.1 System Command
R.2.2 Location of Aircraft
R.2.3 Unsuitable FOD
R.2.4 Power Failure
Based Upon Operational Objective:
OO-2 Provide efficient and effective system command and control.
17
Originating Requirements
R.3.1
refined by
Airfield Scanning
verified by
Demonstration
FOD Detection
Requirement
R.3.1.1
refined by
R.3.2
VerificationRequ...
Requirement
verified by
refined by
Detection Time
Demonstration
Requirement
VerificationRequ...
verified by
basis of
R.3.2.1
refined by
Detect FOD
Group Object
Detection
Function
Requirement
Demonstration
R.3.2.2
R.3.2.4
refined by
Metal Cylinder
Detection
Requirement
verified by
R.3.2.3
refined by
Sphere Detection
Requirement
Test
R.3.2.5
refined by
verified by
Automated
Retrieval Suitabil...
Test
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
refined by
Lighting
Conditions
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall be capable of scanning the airfield and detecting single and
multiple FOD items.
Requirement Rationale:
This functional requirement originated from FAA AC 150/5220-24 Airport Foreign
Object Debris (FOD) Detection Equipment.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.3.1 Airfield Scanning
R.3.2 FOD Detection
Based upon Operational Objective:
OO-3 Provide a method of airfield scanning and FOD detection.
18
Originating Requirements
R.4 FOD Reporting
Figure 10. FOD Reporting Requirements Hierarchy Diagram
hier FOD Reporting
R.4
FOD Reporting
Requirement
R.4.1
R.4.1.1
refined by
R.4.1.2
refined by
verified by
FOD Location
Reporting
Demonstration
Requirement
VerificationRequ...
refined by
R.4.1.3
refined by
verified by
Active Reporting
Passive Reporting
Suitability
Reporting
Test
Requirement
Requirement
Requirement
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall be capable of reporting FOD location data and FOD
characteristics to the retrieval subsystem.
Requirement Rationale:
This performance requirement originated from FAA AC 150/5220-24 Airport Foreign
Object Debris (FOD) Detection Equipment.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.4.1 FOD Location Reporting
Based upon Operational Objective:
OO-4 Provide a method of FOD Reporting.
19
Originating Requirements
R.5.1
refined by
refined by
R.5.2
R.5.3
refined by
R.5.4
refined by
verified by
FOD Weight
Determination
FOD Weight
FOD location
FOD Dimensions
Demonstration
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
Test
Test
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall be capable autonomously retrieving FOD from both paved and
grass surfaces.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.5.1 FOD Weight Determination
R.5.2 FOD Weight
R.5.3 FOD location
R.5.4 FOD Dimensions
Based upon Operational Objective:
OO-05 Provide a method of FOD retrieval.
20
Originating Requirements
R.6.1
refined by
R.6.2
refined by
R.6.3
refined by
refined by
R.6.4
R.6.5
refined by
R.6.6
refined by
R.6.7
refined by
verified by
Mobile Unit
Navigation
Mobile Unit
Movement Clea...
Separation from
Obstacles
Separation from
Aircraft
Separation from
Personnel
Separation from
Vehicles
Test
Requirement
Requirement
Requirement
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
R.6.2.1
refined by
R.6.2.2
refined by
R.6.2.3
refined by
verified by
verified by
verified by
verified by
verified by
verified by
Demonstration
FOD Location
Emergency
Posture
Standby Location
Demonstration
Demonstration
Test
Test
Test
Test
VerificationRequ...
Requirement
Requirement
Requirement
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall provide a method of locomotion for mobile system elements.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.6.1 Mobile Unit Speed
R.6.2 Mobile Unit Navigation
R.6.3 Mobile Unit Movement Clearance
R.6.4 Separation from Obstacles
R.6.5 Separation from Aircraft
R.6.6 Separation from Personnel
R.6.7 Separation from Vehicles
Based upon Operational Objective:
OO-06 Facilitate mobile element locomotion.
21
Originating Requirements
refined by
R.7.1
verified by
Analyze FOD
Trends
Types of Data
Demonstration
Function
Requirement
VerificationRequ...
R.7.1.1
refined by
verified by
Storage of Data
Test
Requirement
VerificationRequ...
refined by
R.7.1.1.1
verified by
Data Retention
Test
Requirement
VerificationRequ...
verified by
Demonstration
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall provide a method of trend analysis.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.7.1 Types of Data
Based upon Operational Objective:
OO-07 Provide FOD trend analysis.
22
Originating Requirements
R.8.1
refined by
R.8.2
refined by
R.8.3
refined by
verified by
ATC
Communication
Airport
Management C...
Maintainer
Communication
Demonstration
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
Demonstration
Demonstration
Demonstration
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall provide a method of communicating with air traffic control,
airport management, and system maintainers.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.8.1 ATC Communication
R.8.2 Airport Management Communication
R.8.3 Maintainer Communication
Based upon Operational Objective:
OO-09 Provide a method of communicating with external system elements.
23
Originating Requirements
R.9.1
R.9.1.1
refined by
R.9.1.2
refined by
refined by
R.9.2
refined by
verified by
Maintenance
Procedures
Call Center
Analysis
Requirement
Requirement
VerificationRequ...
R.9.1.3
refined by
R.9.1.4
refined by
verified by
verified by
Cleaning
Procedures
Preventative
Maintenance Pr...
Recalibration Plan
Scheduled
Component Re...
Analysis
Demonstration
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
System users shall be provided with technical support.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.9.1 Maintenance Procedures
R.9.2 Call Center
Based upon Operational Objective:
OO-08 Provide technical support.
24
Originating Requirements
R.10.1
R.10.1.1
refined by
R.10.1.2
refined by
refined by
verified by
Elements Located
Near The Runway
Inspection
Requirement
VerificationRequ...
R.10.1.3
refined by
R.10.1.4
refined by
verified by
Breakaway
Connector
Element Height
Frangible Coupling
Wind Loading
Inspection
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall conform to applicable airport obstruction criteria, marking and
lighting, and equipment design and installation standards.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.10.1 Elements Located Near the Runway
Based upon Operational Objective:
OO-10 Comply with installation and acceptance standards.
25
Originating Requirements
R.11.1
refined by
R.11.2
refined by
verified by
System
Availability
System
Maintainability
Analysis
Requirement
Requirement
VerificationRequ...
verified by
R.11.2.1
refined by
R.11.2.2
refined by
verified by
Analysis
System Health
and Fault Notific...
Equipment
Located Outside...
Analysis
VerificationRequ...
Requirement
Requirement
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall provide a high level of reliability, availability and maintainability.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.11.1 System Availability
R.11.2 System Maintainability
Based upon Operational Objective:
OO-11 Provide a reliable, maintainable, and available system.
26
Originating Requirements
R.12.1
refined by
R.12.2
refined by
R.12.3
refined by
verified by
Performance in
Rain
Performance in
Snow
Performance in
Wind
Test
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
Test
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall be capable of operating in rain, wind and snow.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.12.1 Performance in Rain
R.12.2 Performance in Snow
R.12.3 Performance in Wind
Based upon Operational Objective:
OO-12 Facilitate adverse weather operation.
27
Functional Requirements
R.1.1 Emergency
R.1.1.1
refined by
verified by
Execution Speed
Test
Requirement
VerificationRequ...
verified by
Demonstration
VerificationRequ...
Date:
November 7, 2...
28
Functional Requirements
R.3.1.1
refined by
verified by
Detection Time
Demonstration
Requirement
VerificationRequ...
verified by
Demonstration
VerificationRequ...
Date:
November 7, 2...
29
Functional Requirements
Functional Requirement Statement:
The system shall be capable of scanning the runways, taxiways, aircraft ramps
and adjoining grass areas for FOD.
Refines Higher-Level Requirement:
R.3 FOD Scanning and Detection
Refined By Lower-Level Requirements:
R.3.1.1 Detection Time
R.4.1 FOD Location Reporting
Figure 21. FOD Location Reporting Requirements Hierarchy Diagram
hier FOD Location Reporting
R.4.1
FOD Location
Reporting
Requirement
R.4.1.1
refined by
R.4.1.2
refined by
R.4.1.3
refined by
verified by
Active Reporting
Passive Reporting
Suitability
Reporting
Test
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
Demonstration
Demonstration
Demonstration
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
30
Functional Requirements
R.4.1.1 Active Reporting
R.4.1.2 Passive Reporting
R.4.1.3 Suitability Reporting
R.5.1 FOD Weight Determination
Functional Requirement Statement:
The system shall be capable of determining when objects are too heavy for
retrieval.
Refines Higher-Level Requirement:
R.5 FOD Retrieval
R.6.2 Mobile Unit Navigation
R.6.2.1
refined by
R.6.2.2
refined by
R.6.2.3
refined by
verified by
FOD Location
Emergency
Posture
Standby Location
Demonstration
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
Demonstration
Demonstration
Demonstration
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Functional Requirements
Refined By Lower-Level Requirements:
R.6.2.1 FOD Location
R.6.2.2 Emergency Posture
R.6.2.3 Standby Location
R.6.2.1 FOD Location
Functional Requirement Statement:
Mobile system elements shall be capable of navigating to FOD locations.
Refines Higher-Level Requirement:
R.6.2 Mobile Unit Navigation
R.6.2.2 Emergency Posture
Functional Requirement Statement:
Mobile system elements shall be capable of navigating to predefined emergency
locations defined by airport managers.
Refines Higher-Level Requirement:
R.6.2 Mobile Unit Navigation
R.6.2.3 Standby Location
Functional Requirement Statement:
Mobile system elements shall be capable of navigating to standby locations that
will be determined by concept selection.
Refines Higher-Level Requirement:
R.6.2 Mobile Unit Navigation
32
Functional Requirements
R.7.1 Types of Data
R.7.1.1
refined by
verified by
Storage of Data
Test
Requirement
VerificationRequ...
refined by
R.7.1.1.1
verified by
Data Retention
Test
Requirement
VerificationRequ...
Date:
November 7, 2015
33
Functional Requirements
verified by
Data Retention
Test
Requirement
VerificationRequ...
verified by
Demonstration
VerificationRequ...
Date:
November 7, 2...
34
Functional Requirements
R.11.2.1
refined by
R.11.2.1.1
refined by
R.11.2.2
refined by
verified by
System Health
and Fault Notific...
Equipment
Located Outside...
Analysis
Requirement
Requirement
VerificationRequ...
refined by
R.11.2.1.2
verified by
verified by
System Health
Test
Demonstration
Requirement
Requirement
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
35
Functional Requirements
refined by
R.11.2.1.1.2
verified by
Mobile Element
System Health
Stationary
Element System...
Demonstration
Requirement
Requirement
VerificationRequ...
verified by
verified by
Demonstration
Demonstration
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
36
Functional Requirements
refined by
R.11.2.1.2.2
verified by
Mobile Element
Self-Test
Stationary
Element Self-Test
Demonstration
Requirement
Requirement
VerificationRequ...
refined by
R.11.2.1.2.1.1
verified by
refined by
R.11.2.1.2.2.1
verified by
Mobile Element
Self-Test Duration
Demonstration
Stationary
Element Self-Tes...
Demonstration
Requirement
VerificationRequ...
Requirement
VerificationRequ...
Date:
November 7, 2015
37
Functional Requirements
verified by
Mobile Element
Self-Test Duration
Demonstration
Requirement
VerificationRequ...
verified by
Test
VerificationRequ...
Date:
November 7, 2...
38
Functional Requirements
verified by
Stationary
Element Self-Tes...
Demonstration
Requirement
VerificationRequ...
verified by
verified by
Analysis
Demonstration
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
39
Performance Requirements
40
Performance Requirements
R.3.2.1
refined by
R.3.2.2
refined by
R.3.2.3
refined by
R.3.2.4
Detect FOD
Group Object
Detection
Metal Cylinder
Detection
Sphere Detection
Function
Requirement
Requirement
Requirement
verified by
verified by
verified by
refined by
R.3.2.5
refined by
Lighting
Conditions
Automated
Retrieval Suitabil...
Test
Requirement
Requirement
VerificationRequ...
verified by
verified by
Test
Test
Test
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
verified by
Date:
November 7, 2015
Performance Requirements
42
Performance Requirements
43
Performance Requirements
Performance Requirements
The FOD retrieval subsystem shall be capable of retrieving FOD with dimensions of
up to 12 inches in length 12 Inches in width and 12 inches in height.
Refines Higher-Level Requirement:
R.5 FOD Retrieval
R.6.3 Mobile Unit Movement Clearance
Performance Requirement Statement:
The system shall be capable of detecting, anticipating movement and avoiding
all airport traffic without input from air traffic control.
Refines Higher-Level Requirement:
R.6 Mobile Unit Locomotion
R.6.4 Separation from Obstacles
Performance Requirement Statement:
Mobile system elements shall maintain a minimum of ten feet (3.05 meters)
separation from all obstacles.
Refines Higher-Level Requirement:
R.6 Mobile Unit Locomotion
R.6.5 Separation from Aircraft
Performance Requirement Statement:
Mobile system elements shall maintain a minimum of fifty feet (15.24 meter)
separation from all aircraft.
Refines Higher-Level Requirement:
R.6 Mobile Unit Locomotion
R.6.6 Separation from Personnel
Performance Requirement Statement:
45
Performance Requirements
Mobile system elements shall maintain a minimum of fifty feet (15.24 meter)
separation from all personnel.
Refines Higher-Level Requirement:
R.6 Mobile Unit Locomotion
R.6.7 Separation from Vehicles
Performance Requirement Statement:
Mobile system elements shall maintain a minimum 25 feet (7.6 meter) separation
from all support vehicles.
Refines Higher-Level Requirement:
R.6 Mobile Unit Locomotion
R.8.1 ATC Communication
Performance Requirement Statement:
The system shall be capable of receiving and transmitting data to air traffic control
without causing any interference to existing systems.
Refines Higher-Level Requirement:
R.8 System Communication
R.8.2 Airport Management Communication
Performance Requirement Statement:
The system shall be capable of receiving and transmitting data to airport
managers without causing any interference to existing systems.
Refines Higher-Level Requirement:
R.8 System Communication
R.8.3 Maintainer Communication
Performance Requirement Statement:
46
Performance Requirements
The system shall be capable of receiving and transmitting data to maintenance
personnel without causing any interference to existing systems.
Refines Higher-Level Requirement:
R.8 System Communication
R.11.1 System Availability
Performance Requirement Statement:
The system should have an Operational Availability (AO) of 99.9%
Refines Higher-Level Requirement:
R.11 Reliability, Availability and Maintainability
R.11.2.1 System Health and Fault Notification
Figure 31. System Health and Fault Notification Requirements Hierarchy Diagram
hier System Health and Fault Notification
R.11.2.1
System Health
and Fault Notific...
Requirement
refined by
R.11.2.1.1
refined by
R.11.2.1.1.1
refined by
R.11.2.1.2
verified by
System Health
Test
Requirement
Requirement
VerificationRequ...
refined by
R.11.2.1.1.2
verified by
refined by
R.11.2.1.2.1
refined by
R.11.2.1.2.2
verified by
Mobile Element
System Health
Stationary
Element System...
Demonstration
Mobile Element
Self-Test
Stationary
Element Self-Test
Demonstration
Requirement
Requirement
VerificationRequ...
Requirement
Requirement
VerificationRequ...
Date:
November 7, 2015
47
Performance Requirements
Performance Requirement Statement:
The system shall be capable of automatically detecting faults in critical
subsystems and providing users with data regarding faults in non-critical
subsystems.
Refines Higher-Level Requirement:
R.11.2 System Maintainability
Refined By Lower-Level Requirements:
R.11.2.1.1 System Health
R.11.2.1.2 Self-Test & Fault Notification
R.11.2.1.1.1 Mobile Element System Health
Performance Requirement Statement:
Mobile subsystems shall be capable of continuously monitoring the health of
critical subsystems and compensating for faults in critical subsystems until they
can exit the airport operating area.
Refines Higher-Level Requirement:
R.11.2.1.1 System Health
R.11.2.1.1.2 Stationary Element System Health
Performance Requirement Statement:
Stationary elements shall employ a method of monitoring system health of critical
subsystems and employ a method of notifying users when faults are detected.
Refines Higher-Level Requirement:
R.11.2.1.1 System Health
R.11.2.1.2.1.1 Mobile Element Self-Test Duration
Performance Requirement Statement:
The self-test duration on mobile system elements should not exceed 30 seconds.
48
Performance Requirements
Refines Higher-Level Requirement:
R.11.2.1.2.1 Mobile Element Self-Test
R.11.2.1.2.2.1 Stationary Element Self-Test Performance
Performance Requirement Statement:
When stationary elements are asked to perform a self-test, the self-test shall not
interfere with the systems ability to operate safely; if the self-test takes a FOD
detection element off line it shall be capable of recovering in no longer than 60
seconds.
Refines Higher-Level Requirement:
49
Performance Requirements
R.11.2.1.2.2 Stationary Element Self-Test
R.12.1 Performance in Rain
Performance Requirement Statement:
The system shall be capable of detecting objects under rainfall conditions having
a specific intensity, duration, and frequency for a two-year category of storm in
the local region (as specified in CLIM 20, Climatology of the United States No. 20).
Refines Higher-Level Requirement:
R.12 Operate in Adverse Weather Conditions
R.12.2 Performance in Snow
Performance Requirement Statement:
The system shall be capable of detecting objects under snow conditions having a
specific intensity, duration, and frequency for a two-year category of storm in the
local region (as specified in CLIM 20, Climatology of the United States No. 20).
Refines Higher-Level Requirement:
R.12 Operate in Adverse Weather Conditions
R.12.3 Performance in Wind
Performance Requirement Statement:
The system shall be capable of operating in wind conditions up to 50 MPH with
gusts up to 70MPH.
Refines Higher-Level Requirement:
R.12 Operate in Adverse Weather Conditions
50
Programmatic Requirements
R.9.1.1
refined by
R.9.1.2
refined by
R.9.1.3
refined by
R.9.1.4
refined by
verified by
Cleaning
Procedures
Preventative
Maintenance Pr...
Recalibration Plan
Scheduled
Component Re...
Analysis
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
Analysis
Analysis
Analysis
Analysis
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
51
Programmatic Requirements
52
Programmatic Requirements
53
Design Constraints
R.6.1 Mobile Unit Speed
Design Constraint Statement:
Mobile system elements shall be capable of operating on the AOA at a speed of
no less than 20 mph (30 km/h).
Requirement Rationale:
This constraint originated from FAA AC 150/5220-24 Airport Foreign Object Debris
(FOD) Detection Equipment.
Refines Higher-Level Requirement:
R.6 Mobile Unit Locomotion
R.7.1.1.1 Data Retention
Design Constraint Statement:
Data systems shall have the capability to retain the data for at least two years
after the detection event.
Requirement Rationale:
This performance requirement originated from FAA AC 150/5220-24 Airport Foreign
Object Debris (FOD) Detection Equipment.
Refines Higher-Level Requirement:
R.7.1.1 Storage of Data
54
Design Constraints
R.10.1.1
refined by
R.10.1.2
refined by
R.10.1.3
refined by
R.10.1.4
refined by
verified by
Breakaway
Connector
Element Height
Frangible Coupling
Wind Loading
Inspection
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
Inspection
Inspection
Inspection
Inspection
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
55
Design Constraints
56
Design Constraints
57
Based on
R Need Statement
Command
F.1.4 Transmit Emergency Command
System Elements
F.1.7 Interface with Airport Managers
Personnel
58
Based on
Data
F.2.7 Provide Maintenance Personnel
Distance
Based on
FOD
Objects
R.1.1 Emergency
Location
Based on
61
Based on
62
F. AFDIRTS System
Figure 34. F. AFDIRTS N2 Diagram
n2 Perform AFDIRTS Functions
(Ext) Aircraft
Radar Data ...
(Ext) ATC ...
(Ext) Maint...
(Ext) FOD
Identification
from FOD
(Ext) FOD L...
(Ext) FOD
Identificatio...
(Ext) FOD L...
At FOD Loca...
(Ext) Aircraf...
(Ext) Obsta...
(Ext) Obsta...
Location Da...
(Ext)
Materials fr...
(Ext) Parts ...
(Ext) SW U...
(Ext)
Electrical
Energy from
Power
At FOD
Location
Signal (S)
F.1
System Context
System
Health (D)
Emergency...
Fault Codes...
System Hea...
System Hea...
Inbound
Aircraft Data
from Comm...
Navigation ...
Command and
Control System
F.2
Operate Safely
System Context
Unsuitable
FOD Location
Data
F.3
Scan Airfield for
FOD
System Context
Unsuitable
FOD (D)
Unsuitable
FOD Locatio...
FOD Location
Data to
Mobile Units
FOD
Characteristic
s (D)
Suitablity D...
FOD Charac...
Fod Illumina...
Suitablity D...
Unsuitable ...
Navigation
Modes (D)
FOD too
Large (S)
FOD too
Large (S)
Unsuitable
FOD Locatio...
FOD
Coordinates
Aircraft
Illumination ...
FOD Coordi...
Obstacle Ill...
F.4
Retrieve FOD
System Context
F.5
Navigate Airfield
System Context
Movement
Command to
Locomote
System Ele...
F.6
Heat to
Environment
Resistance t...
Sound to En...
Locomote System
Elements
System Context
F.7
Materials to
Maintainer
Parts to
Maintainer
Maintain System
System Context
Power Failure
Signal from
Power (S)
transferred...
transferred
Power (E)
transferred
Power (E)
transferred
Power (E)
transferred
Power (E)
transferred
Power (E)
transferred
Power (E)
F.8
transferred
Power (E)
Provide Power
System Context
F.9
Analyze FOD
Trends
Reports to
Airport
Managers (E)
System Context
Date:
63
(Ext) ATC
Command
from ATC
System Hea...
Emergency
Operation
Command (S)
System
Health (D)
Unsuitable
FOD Locatio...
(Ext) Aircraft
Radar Data
from ATC
(Ext)
Maintenance
Commands ...
System Hea...
Power Failure
Signal from
Power (S)
F.1.1
Interface with
ATC
System Context
System
Health to
ATC (E)
Command
Signal (S)
F.1.2
Initiate System
Modes
System Context
Normal
Operation
Command (S)
Emergency
Operation
Command (S)
F.1.3
Transmit Normal
Operation
Command
System Context
Navigation
Modes (D)
F.1.4
Transmit
Emergency
Command
System Context
Navigation
Modes (D)
F.1.5
Determine
Location,
Trajectory and
Speed of Inbou...
System Context
Aircraft
Location (D)
F.1.6
Inbound
Aircraft Data
from
Command a...
Transmit Inbound
Aircraft Data to
System Elements
System Context
F.1.7
System
Health to
Airport Man...
Unsuitable ...
Interface with
Airport Managers
System Context
F.1.8
System
Health Data
to Maintainer
(E)
Interface with
Maintenance
Personnel
System Context
System
Resume
Signal (S)
System
Resume
Signal (S)
System
Resume
Signal (S)
System
Resume
Signal (S)
System
Resume
Signal (S)
F.1.9
Restore System
System Context
Date:
64
Transmit Normal
Operation Command
(Ext) ATC
Command from
ATC
F.1.1
Command
Signal (S)
Interface with ATC
F.1.2
System Context
Initiate System Modes
OR
OR
F.1.4
(Ext) Aircraft
Radar Data from
ATC
F.1.5
System Context
System Context
System Context
F.1.6
Determine Location,
Trajectory and Speed of
Inbound Aircraft.
System Context
System Context
AND
AND
Unsuitable FOD
Location Data
F.1.7
System Health Data to
Maintainer (E)
(Ext) Maintenance
Commands from
Maintainer
System Context
F.1.8
Interface with
Maintenance Personnel
System Context
Ref.
OR
OR
Ref.
F.1.9
Restore System
System Context
Power Failure Signal
from Power (S)
System Resume
Signal (S)
Date:
65
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.1 Interface with ATC
Output From:
(External) ATC IOs
Command Signal
Input To:
F.1.2 Initiate System Modes
Output From:
F.1.1 Interface with ATC
System Health
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.1 Interface with ATC
66
Source / Destination
Input To:
F.1.2 Initiate System Modes
Output From:
F.1.1 Interface with ATC
Input To:
F.1.4 Transmit Emergency Command
Output From:
F.1 Command and Control System
F.1.2 Initiate System Modes
Input To:
F.1.3 Transmit Normal Operation
Command
Output From:
F.1.2 Initiate System Modes
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
67
Source / Destination
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Input To:
F.1.3 Transmit Normal Operation
Command
Output From:
F.1.2 Initiate System Modes
68
Source / Destination
Input To:
F.1.4 Transmit Emergency Command
Output From:
F.1 Command and Control System
F.1.2 Initiate System Modes
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
69
Input To:
F.1.6 Transmit Inbound Aircraft Data to
System Elements
Output From:
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
Source / Destination
Input To:
F.1.6 Transmit Inbound Aircraft Data to
System Elements
Output From:
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
Input To:
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
70
Source / Destination
Output From:
F.1 Command and Control System
F.1.6 Transmit Inbound Aircraft Data to
System Elements
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
Source / Destination
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
71
Source / Destination
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
72
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.8 Interface with Maintenance
Personnel
F.1.8.1 Initiate Self-Test
Output From:
(External) Maintainer IOs
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Input To:
F.1.2 Initiate System Modes
73
Source / Destination
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
Ref.
System Health
Data to Maintainer
(E)
System
Health (D)
F.1.8.1
F.1.8.2
Display Maintenance
Data
Initiate Self-Test
System Context
System Context
Ref.
Date:
74
(Ext)
Maintenance
Commands
from Mainta...
System
Health (D)
F.1.8.1
Initiate Self-Test
System Context
Fault Codes
(D)
F.1.8.2
Display
Maintenance Data
System Context
Fault Codes
to Maintainer
System
Health Data...
Date:
November 17, 2015
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.8 Interface with Maintenance
Personnel
F.1.8.1 Initiate Self-Test
Output From:
(External) Maintainer IOs
Input To:
F.1.8.2 Display Maintenance Data
Output From:
F.1.8.1 Initiate Self-Test
75
Source / Destination
Input To:
F.1.8.2 Display Maintenance Data
Output From:
F.1.8.1 Initiate Self-Test
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.8.2 Display Maintenance Data
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
76
Source / Destination
Input To:
F.1 Command and Control System
F.1.9 Restore System
Output From:
F.8 Provide Power
F.8.2 Detect External Power Failure
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
77
Source / Destination
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
78
F.2.5
Fault Data (D)
F.2.2
System
Initialization
Ref.
System Context
AND
Critical
Subsystem
Degraded Signal
F.2.3
AND
OR
F.2.4
OR
Ref.
System Context
System Context
Monitor the Health of
Mobile Element
Critical Subsystems
Compensate for
Failures in Mobile Unit
Critical Subsystems
System Context
System Context
F.2.7
Provide Maintenance
Personnel with System
Health Data
System Context
Critical Subsystem
Telemetry Data From
Mobile Elements
Self-Test Results
(D)
Date:
79
System
Initialization
Critical
Subsystem
Telemetry
Data from S...
Critical
Subsystem
Telemetry
Data From ...
F.2.1
Perform Self Test
Upon Initialization
System Context
F.2.2
Monitor the
Health of
Stationary
Element Critical ...
System Context
F.2.3
Monitor the
Health of Mobile
Element Critical
Subsystems
System Context
Self-Test
Results (D)
Self-Test
Results (D)
Self-Test
Results (D)
Critical
Subsystem
Degraded
Signal
F.2.4
Compensate for
Failures in Mobile
Unit Critical
Subsystems
System Context
F.2.5
Provide Airport
Managers with
System Health
Data
System Context
System
Health (D)
F.2.6
Provide ATC with
System Health
Data
System Context
Date:
System
Health (D)
F.2.7
Provide
Maintenance
Personnel with
System Health ...
System Context
System
Health (D)
80
Source / Destination
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.1 Perform Self-Test Upon Initialization
System Initialization
Input To:
F.2.1 Perform Self-Test Upon Initialization
Source / Destination
Input To:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
81
Source / Destination
with System Health Data
Output From:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Source / Destination
Input To:
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Output From:
F.2.3 Monitor the Health of Mobile
Element Critical Subsystems
Input To:
F.2.3 Monitor the Health of Mobile
Element Critical Subsystems
82
Source / Destination
Input To:
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Output From:
F.2.3 Monitor the Health of Mobile
Element Critical Subsystems
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Source / Destination
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
83
Source / Destination
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.1 Perform Self-Test Upon Initialization
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
84
Source / Destination
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.1 Perform Self-Test Upon Initialization
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
85
Source / Destination
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Source / Destination
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.1 Perform Self-Test Upon Initialization
86
Source / Destination
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
87
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Output From:
(External) FOD IOs
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.3 Grasp FOD
Output From:
(External) FOD IOs
Input To:
F.3.2 Determine FOD Suitability from a
Distance
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
Input To:
(External) FOD IOs
88
Source / Destination
Output From:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
Input To:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
Input To:
F.3.4 Process Suitability and Location of
FOD
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.2 Determine FOD Suitability from a
Distance
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
Input To:
F Perform AFDIRTS Functions
89
Source / Destination
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
90
FOD
Characteristics (D)
(Ext) FOD
Identification
from FOD
F.3.1
Determine FOD
Suitability from a
Distance
Detect FOD
System Context
Ref.
Unsuitable FOD
Location Data
F.3.2
F.3.4
System Context
AND
AND
F.3.3
Process Suitability
and Location of FOD
Ref.
System Context
Determine Location of
FOD
System Context
Fod Illumination to
FOD
Date:
91
(Ext) FOD
Identification
from FOD
FOD
Characteristic
s (D)
(Ext) FOD
Location from
FOD
Suitablity
Data (D)
F.3.1
Detect FOD
System Context
FOD
Characteristic
s (D)
FOD
Characteristic
s (D)
F.3.2
Determine FOD
Suitability from a
Distance
System Context
Suitablity
Data (D)
Suitablity
Data (D)
FOD Location
(D)
Fod
Illumination
to FOD
F.3.3
Determine
Location of FOD
System Context
F.3.4
Process
Suitability and
Location of FOD
System Context
Date:
FOD Location
Data to
Mobile Units
Unsuitable ...
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
92
Source / Destination
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Output From:
(External) FOD IOs
Input To:
F.3.2 Determine FOD Suitability from a
Distance
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
Source / Destination
Input To:
F.3.2 Determine FOD Suitability from a
Distance
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
Input To:
F.3.4 Process Suitability and Location of
FOD
F.9 Analyze FOD Trends
93
Source / Destination
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.2 Determine FOD Suitability from a
Distance
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.3 Grasp FOD
Output From:
(External) FOD IOs
Input To:
(External) FOD IOs
Output From:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
Input To:
F.3.4 Process Suitability and Location of
FOD
Output From:
94
Source / Destination
F.3.3 Determine Location of FOD
Source / Destination
Input To:
F.3.4 Process Suitability and Location of
FOD
Output From:
F.3.3 Determine Location of FOD
Input To:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
Input To:
F.3.4 Process Suitability and Location of
FOD
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.2 Determine FOD Suitability from a
Distance
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
95
Source / Destination
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
96
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Output From:
(External) FOD IOs
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.3 Grasp FOD
Output From:
(External) FOD IOs
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
Input To:
97
Source / Destination
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
Input To:
F.1 Command and Control System
Output From:
F.4 Retrieve FOD
Input To:
98
Source / Destination
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
99
Unsuitable FOD
Location Data
At FOD Location
Signal (S)
Ref.
Determine FOD
Dimensions
System Context
System Context
OR
OR
(Ext) FOD Location
from FOD
Notify Personnel of
Overweight Objects
F.4.4
F.4.3
(Ext) FOD
Identification from
FOD
Grasp FOD
Determine FOD
weight
System Context
System Context
FOD (M)
Grasped
FOD (F)
Ref.
F.4.5
Overweight
Signal
Navigation Modes
(D)
System Context
OR
OR
F.4.6
F.4.7
Transport FOD to
Disposal Area
Suitable for
Transport Signal
Release FOD
System Context
System Context
Date:
100
(Ext) FOD
Identificatio...
At FOD Loca...
FOD (M)
(Ext) FOD
Location from
FOD
FOD too La...
(Ext) FOD
Location from
FOD
FOD too
Large (S)
FOD (M)
At Disposal
Area Signal
F.4.1
Determine FOD
Dimensions
System Context
F.4.2
Notify Personnel
of Object too
Large for
Retrieval
System Context
FOD (M)
FOD too
Large (S)
Unsuitable
FOD Location
Data
F.4.3
Grasp FOD
System Context
Grasped FOD
(F)
F.4.4
Determine FOD
weight
System Context
Overweight
Signal
Suitable for
Transport
Signal
F.4.5
Notify Personnel
of Overweight
Objects
System Context
Unsuitable
FOD Location
Data
F.4.6
Transport FOD to
Disposal Area
System Context
Navigation
Modes (D)
F.4.7
Release FOD
System Context
Date:
101
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Output From:
(External) FOD IOs
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
FOD (M)
Input To:
F.4.1 Determine FOD Dimensions
F.4.3 Grasp FOD
Output From:
F.4.1 Determine FOD Dimensions
Input To:
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
102
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.3 Grasp FOD
Output From:
(External) FOD IOs
Input To:
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
103
Source / Destination
F.4.5 Notify Personnel of Overweight
Objects
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.3 Grasp FOD
Output From:
(External) FOD IOs
FOD (M)
Input To:
F.4.1 Determine FOD Dimensions
F.4.3 Grasp FOD
Output From:
F.4.1 Determine FOD Dimensions
Input To:
F.4.4 Determine FOD weight
Output From:
F.4.3 Grasp FOD
104
Source / Destination
Input To:
F.4.4 Determine FOD weight
Output From:
F.4.3 Grasp FOD
Overweight Signal
Input To:
F.4.5 Notify Personnel of Overweight
Objects
Output From:
F.4.4 Determine FOD weight
Input To:
F.4.6 Transport FOD to Disposal Area
Output From:
F.4.4 Determine FOD weight
F.4.6
Grasped
FOD (F)
Grasp FOD
Transport FOD to
Disposal Area
F.4.4
System Context
OR
Determine FOD
weight
System Context
OR
System Context
Ref.
Suitable for
Transport ...
Ref.
Overweight
Signal
Date:
105
Grasped FOD
(F)
F.4.4
Determine FOD
weight
System Context
Overweight
Signal
Suitable for
Transport S...
Date:
November ...
Source / Destination
Input To:
F.4.5 Notify Personnel of Overweight
Objects
Output From:
F.4.4 Determine FOD weight
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
106
Source / Destination
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Input To:
F.4.6 Transport FOD to Disposal Area
Output From:
F.4.4 Determine FOD weight
Source / Destination
Input To:
F.4.7 Release FOD
F.5.10 Control Motion
Output From:
F.5.4 Navigate to Disposal Area
107
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
Output From:
(External) Obstacles IOs
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
Output From:
(External) Obstacles IOs
Output From:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
FOD Coordinates
Input To:
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Input To:
108
Source / Destination
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
Input To:
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Output From:
F.1 Command and Control System
F.1.6 Transmit Inbound Aircraft Data to
System Elements
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.9 Determine Location
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
109
Source / Destination
F.4.6 Transport FOD to Disposal Area
Input To:
(External) Obstacles IOs
Output From:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
110
Navigate to Emergency
Standby Location
Standby
Emergency
Location
Coordinates
At Emergency
Location Signal
At Disposal Area
Signal
System Context
F.5.1
At FOD Location
Signal (S)
Obstacle Illumination
to Obstacle
F.5.3
FOD Coordinates
Process Navigation
Commands
(Ext) Obstacle
Location from
Obstacle
OR
OR
System Context
System Context
Movement Command
to Locomote System
Elements
F.5.4
Navigation
Commands
(Ext) Obstacle
Identification from
Obstacle
Disposal Area
Coordinates
System Context
Obstacle Path
F.5.5
F.5.7
Detect Obstacles
System Context
Ref.
AND
AND
AND
F.5.6
(Ext) Aircraft
Location from
Aircraft (E)
Inbound Aircraft
Data from
Command and
Control (D)
Anticipate Obstacle
Movement
Avoid Obstacles
Obstacle
Characteristics
Ref.
System Context
Obstacle
Trajectory
System Context
F.5.9
Determine Location
Control Motion
AND
System Context
System Context
Receive Aircraft
Trajectory Data
F.5.10
F.5.8
Aircraft Illumination to
Aircraft
Coordinates (D)
System Context
Date:
111
(Ext)
Obstacle
Identificatio...
(Ext) Obsta...
FOD Location
Data to
Mobile Units
Navigation
Modes (D)
(Ext) Aircraft
Location from
Aircraft (E)
Inbound Air...
Location
Data from
Environment
FOD
Coordinates
F.5.1
Process
Navigation
Commands
System Context
Navigation
Commands
Navigation
Commands
Navigation
Commands
F.5.2
At
Emergency
Location Si...
Standby Em...
Navigate to
Emergency
Standby Location
System Context
F.5.3
Navigate to FOD
Location
System Context
System Context
At Disposal
Area Signal
Disposal Area
Coordinates
At Disposal
Area Signal
F.5.5
Detect Obstacles
System Context
Obstacle
Characteristic
s
Obstacle
Illumination
to Obstacle
Obstacle
Characteristic
s
Aircraft
Illumination
to Aircraft
F.5.6
Receive Aircraft
Trajectory Data
System Context
F.5.7
Anticipate
Obstacle
Movement
System Context
Obstacle
Trajectory
F.5.8
Avoid Obstacles
System Context
Coordinates
(D)
At FOD
Location
Signal (S)
FOD Coordi...
F.5.4
Navigate to
Disposal Area
Coordinates
(D)
At FOD
Location
Signal (S)
FOD Coordi...
Coordinates
(D)
Coordinates
(D)
Obstacle Path
F.5.9
Determine
Location
Coordinates
(D)
System Context
F.5.10
Control Motion
System Context
Date:
Movement
Command to
Locomote
System Ele...
Source / Destination
Input To:
112
Source / Destination
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
Output From:
F.5.1 Process Navigation Commands
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Source / Destination
Input To:
F.5.10 Control Motion
Output From:
F.5.2 Navigate to Emergency Standby
Location
Coordinates (D)
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
113
Source / Destination
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
Navigation Commands
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
Output From:
F.5.1 Process Navigation Commands
Input To:
F.5.10 Control Motion
Output From:
F.5.2 Navigate to Emergency Standby
Location
Source / Destination
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
Coordinates (D)
Input To:
114
Source / Destination
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
FOD Coordinates
Input To:
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Input To:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
Navigation Commands
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
Output From:
F.5.1 Process Navigation Commands
115
Source / Destination
Input To:
F.4.7 Release FOD
F.5.10 Control Motion
Output From:
F.5.4 Navigate to Disposal Area
Coordinates (D)
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
Input To:
F.5.10 Control Motion
Output From:
F.5.4 Navigate to Disposal Area
Navigation Commands
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
Output From:
F.5.1 Process Navigation Commands
116
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
Output From:
(External) Obstacles IOs
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
Output From:
(External) Obstacles IOs
Obstacle Characteristics
Input To:
F.5.7 Anticipate Obstacle Movement
Output From:
F.5.5 Detect Obstacles
F.5.6 Receive Aircraft Trajectory Data
Input To:
(External) Obstacles IOs
Output From:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
117
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Output From:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Input To:
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Output From:
F.1 Command and Control System
F.1.6 Transmit Inbound Aircraft Data to
System Elements
Obstacle Characteristics
Input To:
F.5.7 Anticipate Obstacle Movement
Output From:
F.5.5 Detect Obstacles
F.5.6 Receive Aircraft Trajectory Data
Source / Destination
Input To:
118
Source / Destination
F.5.7 Anticipate Obstacle Movement
Output From:
F.5.5 Detect Obstacles
F.5.6 Receive Aircraft Trajectory Data
Obstacle Trajectory
Input To:
F.5.8 Avoid Obstacles
Output From:
F.5.7 Anticipate Obstacle Movement
Source / Destination
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
Obstacle Path
Input To:
F.5.10 Control Motion
Output From:
F.5.8 Avoid Obstacles
Obstacle Trajectory
Input To:
F.5.8 Avoid Obstacles
119
Source / Destination
Output From:
F.5.7 Anticipate Obstacle Movement
Source / Destination
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.9 Determine Location
Source / Destination
Input To:
F.4.7 Release FOD
F.5.10 Control Motion
120
Source / Destination
Output From:
F.5.4 Navigate to Disposal Area
Input To:
F.5.10 Control Motion
Output From:
F.5.2 Navigate to Emergency Standby
Location
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
Coordinates (D)
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
Input To:
F.5.10 Control Motion
Output From:
F.5.4 Navigate to Disposal Area
FOD Coordinates
Input To:
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
121
Source / Destination
Output From:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Obstacle Path
Input To:
F.5.10 Control Motion
Output From:
F.5.8 Avoid Obstacles
Input To:
F.5.10 Control Motion
Output From:
F.5.2 Navigate to Emergency Standby
Location
122
Source / Destination
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.3 Facilitate Braking
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Resistance to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
Sound to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.2 Facilitate Motion
123
Source / Destination
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
Mobile Unit
Energy Source
Mobile Unit
Power
F.6.1
Facilitate Power
System Context
Ref.
AND
Ref.
AND
F.6.2
Facilitate
Movement
System Context
Movement
Command to
Locomote System
Elements
Heat to
Environment
Sound to Environment
Resistance to Environment
Date:
124
Mobile Unit
Energy
Source
Movement
Command to
Locomote
System Ele...
F.6.1
Facilitate Power
System Context
Mobile Unit
Power
F.6.2
Facilitate
Movement
System Context
Heat to
Environment
Resistance t...
Sound to En...
Date:
November 18, 2015
Source / Destination
Input To:
F.6.1 Facilitate Power
Input To:
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Output From:
F.6.1 Facilitate Power
125
Source / Destination
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.3 Facilitate Braking
Input To:
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Output From:
F.6.1 Facilitate Power
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Resistance to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
126
Source / Destination
Sound to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.2 Facilitate Motion
Resistance to
Environment
F.6.2.1
Facilitate Directional
Control
F.6.2.3
System Context
Ref.
AND
Facilitate Braking
AND
Ref.
F.6.2.2
System Context
Facilitate Motion
Mobile Unit
Power
Heat to
Environment
System Context
Mobile Unit
Kinetic Energy
Sound to
Environment
Date:
127
Mobile Unit
Power
Movement
Command to...
Mobile Unit
Power
Movement
Command to...
Movement
Command to
Locomote
System Ele...
F.6.2.1
Facilitate
Directional Control
System Context
Mobile Unit
Kinetic Energy
Resistance to
Environment
Mobile Unit
Kinetic Energy
Sound to
Environment
F.6.2.2
Facilitate Motion
System Context
F.6.2.3
Facilitate Braking
Heat to
Environment
System Context
Date:
November 18, 2015
Source / Destination
Input To:
F.6.2.3 Facilitate Braking
Output From:
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Input To:
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Output From:
F.6.1 Facilitate Power
Input To:
128
Source / Destination
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Resistance to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
Source / Destination
Input To:
F.6.2.3 Facilitate Braking
Output From:
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Input To:
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Output From:
F.6.1 Facilitate Power
129
Source / Destination
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Sound to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.2 Facilitate Motion
Source / Destination
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.3 Facilitate Braking
Input To:
F.6.2.3 Facilitate Braking
Output From:
130
Source / Destination
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
131
Source / Destination
Input To:
F.7 Maintain System
F.7.2 Accept Materials
Output From:
(External) Maintainer IOs
Input To:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.1 Accept Parts
Output From:
(External) Maintainer IOs
Input To:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.3 Accept SW Updates
Output From:
(External) Maintainer IOs
Materials to Maintainer
Input To:
(External) Maintainer IOs
Output From:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.4 Eject Materials
Parts to Maintainer
Input To:
(External) Maintainer IOs
Output From:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.5 Eject Parts
132
Source / Destination
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
F.7.1
Accept Parts
System Context
(Ext) Materials
from Maintainer
F.7.2
Accept Materials
System Context
F.7.3
Ref.
AND
Accept SW
Updates
AND
Ref.
System Context
Materials to
Maintainer
F.7.4
(Ext) SW Update
from Maintainer
Eject Materials
System Context
Parts to Maintainer
F.7.5
Eject Parts
System Context
Date:
133
(Ext)
Materials
from
Maintainer
(Ext) Parts
from
Maintainer
(Ext) SW
Update from
Maintainer
F.7.1
Accept Parts
System Context
F.7.2
Accept Materials
System Context
F.7.3
Accept SW
Updates
System Context
F.7.4
Materials to
Maintainer
Eject Materials
System Context
F.7.5
Eject Parts
Parts to
Maintainer
System Context
Date:
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.1 Accept Parts
Output From:
(External) Maintainer IOs
134
Source / Destination
Input To:
F.7 Maintain System
F.7.2 Accept Materials
Output From:
(External) Maintainer IOs
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.3 Accept SW Updates
Output From:
(External) Maintainer IOs
135
Source / Destination
Input To:
(External) Maintainer IOs
Output From:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.4 Eject Materials
Source / Destination
Input To:
(External) Maintainer IOs
Output From:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.5 Eject Parts
136
Source / Destination
Input To:
F.8 Provide Power
F.8.1 Accept External Power
F.8.2 Detect External Power Failure
Output From:
(External) Power IOs
Input To:
F.1 Command and Control System
F.1.9 Restore System
Output From:
F.8 Provide Power
F.8.2 Detect External Power Failure
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
137
F.8.1
(Ext) Electrical
Energy from
Power
Power Failure
Signal from
Power (S)
Accept External
Power
System Context
AND
AND
F.8.2
Detect External
Power Failure
F.8.4
System Context
Ref.
OR
OR
F.8.3
Transfer Power
Ref.
System Context
Generate
Emergency Power
transferred
Power (E)
System Context
Generator Power
Date:
(Ext)
Electrical
Energy from
Power
(Ext)
Electrical
Energy from
Power
F.8.1
Accept External
Power
System Context
Power (E)
F.8.2
Power Failure
Signal from
Power (S)
Detect External
Power Failure
System Context
F.8.3
Generate
Emergency Power
System Context
Generator
Power
F.8.4
Transfer Power
transferred
Power (E)
System Context
Date:
138
Source / Destination
Input To:
F.8 Provide Power
F.8.1 Accept External Power
F.8.2 Detect External Power Failure
Output From:
(External) Power IOs
Power (E)
Input To:
F.8.4 Transfer Power
Output From:
F.8.1 Accept External Power
Source / Destination
Input To:
F.8 Provide Power
F.8.1 Accept External Power
F.8.2 Detect External Power Failure
Output From:
(External) Power IOs
Input To:
F.1 Command and Control System
F.1.9 Restore System
Output From:
139
Source / Destination
F.8 Provide Power
F.8.2 Detect External Power Failure
Source / Destination
Input To:
F.8.4 Transfer Power
Output From:
F.8.3 Generate Emergency Power
Source / Destination
Input To:
F.8.4 Transfer Power
Output From:
F.8.3 Generate Emergency Power
Power (E)
Input To:
F.8.4 Transfer Power
Output From:
F.8.1 Accept External Power
Input To:
F.1 Command and Control System
140
Source / Destination
F.2
F.3
F.4
F.5
F.6
F.7
F.9
Operate Safely
Scan Airfield for FOD
Retrieve FOD
Navigate Airfield
Locomote System Elements
Maintain System
Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
141
Source / Destination
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
Input To:
F.3.2 Determine FOD Suitability from a
Distance
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
FOD Coordinates
Input To:
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Input To:
F.4.2 Notify Personnel of Object too
142
Source / Destination
Large for Retrieval
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Input To:
(External) Airport Managers IOs
Output From:
F Perform AFDIRTS Functions
F.9 Analyze FOD Trends
F.9.4 Export FOD Reports
Input To:
F.3.4 Process Suitability and Location of
FOD
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.2 Determine FOD Suitability from a
Distance
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
143
Source / Destination
F.8.4 Transfer Power
144
FOD Coordinates
F.9.1
Ref.
F.9.2
F.9.4
F.9.3
Retain Data
System Context
System Context
System Context
FOD
Characteristics
(D)
Ref.
Reports to
Airport Managers
(E)
Raw FOD
Data
Date:
145
At FOD Loca...
FOD Charac...
FOD Coordi...
FOD too La...
F.9.1
Accept FOD alert
time and date,
location
coordinates and...
System Context
Raw FOD
Data
F.9.2
Perform Trend
Analysis
System Context
FOD Trend
Data (D)
FOD Trend
Data (D)
F.9.3
Retain Data
System Context
F.9.4
Reports to
Airport
Managers (E)
Export FOD
Reports
System Context
Date:
F.9.1 Accept FOD alert time and date, location coordinates and FOD image data
Based On:
R.8.1 Types of Data
Table 63. F.9.1 Accept FOD alert time and date, location coordinates and FOD image
data Interfacing Items
Interfacing Items
At FOD Location Signal (S)
Source / Destination
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
146
Source / Destination
data
Output From:
F.5.3 Navigate to FOD Location
Input To:
F.3.2 Determine FOD Suitability from a
Distance
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
FOD Coordinates
Input To:
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Input To:
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Input To:
F.9.2 Perform Trend Analysis
Output From:
147
Source / Destination
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Input To:
F.3.4 Process Suitability and Location of
FOD
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.2 Determine FOD Suitability from a
Distance
Source / Destination
Input To:
F.9.3 Retain Data
F.9.4 Export FOD Reports
Output From:
F.9.2 Perform Trend Analysis
Input To:
F.9.2 Perform Trend Analysis
Output From:
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
148
Source / Destination
Input To:
F.9.3 Retain Data
F.9.4 Export FOD Reports
Output From:
F.9.2 Perform Trend Analysis
Source / Destination
Input To:
F.9.3 Retain Data
F.9.4 Export FOD Reports
Output From:
F.9.2 Perform Trend Analysis
Input To:
(External) Airport Managers IOs
Output From:
F Perform AFDIRTS Functions
F.9 Analyze FOD Trends
F.9.4 Export FOD Reports
149
150
151
COMP.3.1
IFerret TM &
AFDIRTS Interface
Unit
Maintenance IUser
Interface (MUI)
Airport Management
Display Unit (AMDU)
Subsystem
Subsystem
Subsystem
HWCI
HWCI
COMP.1.5
ATC Radar Interface
Unit (ARIU)
Subsystem
COMP.1.6
(CCR) Command and
Control Radio
COMP.1.3
HWCI
Command and
Control Computer
(CCC)
HWCI
BACKUP CPU <-> CPU
NAV Radio
HWCI
COMP.6.1
COMP.4.2.5
Retrieval Telemetry
Radio
ARIU-> CPU
Command and Control Computer (CCC) -> IFerret TM & AFDIRTS Interface U...
COMP.1.1
COMP.1.7
COMP.4.4.1
Command and
Control Interface Unit
(CCIU)
COMP.1.2
COMP.2.4
External System
External System
Airport Managers
External System
Subsystem
ENV.3
Maintainer
ENV.6
ENV.1
COMP.1.4
Backup CPU
Analysis Computer
Subsystem
HWCI
Date:
December 4, 2015
Table 67. COMP.1 Command and Control Segment Functional Traceability Matrix
Number
Name
Type
Performs
COMP.1
Segment
COMP.1.1
Airport Management
Display Unit (AMDU)
Subsystem
COMP.1.2
Subsystem
152
Name
Type
Performs
COMP.1.3
HWCI
COMP.1.3.1
SWCI
COMP.1.4
Backup CPU
Subsystem
COMP.1.5
Subsystem
COMP.1.6
HWCI
COMP.1.7
Maintenance User
Interface (MUI)
Subsystem
Name
Transfers
Connects to
L.1.1
Item System
Health to ATC
Component
COMP.1.2 ATC User
Interface (AUI)
Component
ENV.1 Air Traffic
Control
153
Name
Transfers
Connects to
L.1.2
Component
COMP.1.2 ATC User
Interface (AUI)
L.1.3
L.1.4
L.1.5
L.1.6
Command and
Control Computer
(CCC) -> IFerret TM
& AFDIRTS Interface
Unit
Item (Ext)
Maintenance
Commands from
Maintainer
Item System
Health Data to
Maintainer
Item System
Health to Airport
Managers
Item Unsuitable
FOD Data to Airport
Managers
Item FOD
Location
Item Unsuitable
FOD Location Data
Item Navigation
Modes
Component
ENV.1 Air Traffic
Control
Component
COMP.1.7
Maintenance User
Interface (MUI)
Component
ENV.6 Maintainer
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
ENV.3 Airport
Managers
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
154
Name
Transfers
Connects to
L.1.7
Item (Ext)
Aircraft Radar Data
from ATC
Component
COMP.1.5 ATC
Radar Interface
Unit (ARIU)
L.1.8
L.1.9
L.1.10
CCIU ->
COMMAND AND
CONTROL CPU
ARIU-> CPU
Item Self-Test
Results
Item System
Health
Item Aircraft
Trajectory Data
Item
Maintenance
Commands
Item Self-Test
Results
Item System
Health Data to
Maintainer
Component
ENV.1 Air Traffic
Control
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.2.4
Command and
Control Interface
Unit (CCIU)
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.5 ATC
Radar Interface
Unit (ARIU)
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.7
Maintenance User
Interface (MUI)
155
Name
Transfers
Connects to
L.1.11
Item Self-Test
Results
Item System
Health to Airport
Managers
L.1.12
Item Command
Signal
Item Self-Test
Results
Item System
Health to ATC
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.2 ATC User
Interface (AUI)
L.1.13
L.1.14
Item Reports to
Airport Managers
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
COMP.6.1 Analysis
Computer
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.4 Backup
CPU
156
Name
Transfers
Connects to
L.1.15
Item Aircraft
Trajectory Data
Item Emergency
Operation
Command
Item
Maintenance
Commands
Item Normal
Operation
Command
Item Unsuitable
FOD Location Data
Item Unsuitable
FOD Location Data
From ARV
Component
COMP.1.3
Command and
Control Computer
(CCC)
L.1.16
L.1.17
L.1.18
CCR-> Airport
Management
Display Unit
Retrieval Telemetry
Radio -> CCR
Item Unsuitable
FOD Location Data
Item Inbound
Aircraft Data to
ARV
Item Navigation
Modes
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.4.4.1
Retrieval Telemetry
Radio
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.4.2.5 NAV
Radio
157
158
HWCI
COMP.2.1
COMP.2.4
HWCI
HWCI
SHR -> SHC
Date:
December 4, 2015
159
Name
Type
Performs
COMP.2
System Health
Monitoring
Segment
Segment
Function F.2
Operate Safely
COMP.2.1
System Heath
Radio (SHR)
HWCI
COMP.2.2
System Health
Computer (SHC)
HWCI
COMP.2.2.1
System Health
Software
SWCI
COMP.2.3
Components
Defined as "Critical"
During Advanced
Development
HWCI
COMP.2.4
Command and
Control Interface
Unit (CCIU)
HWCI
Function F.2.1
Receive Telemetry
Signal From
Stationary Elements
Function F.2.3
Receive Telemetry
Data from Mobile
Elements
Function F.2.2
Monitor the Health
of Stationary
Element Critical
Subsystems
Function F.2.4
Monitor the Health
of Mobile Element
Critical
Components
Function F.2.4.1
Direct SHC
operation
Function F.2.5
Compensate for
Failures in Mobile
Unit Critical
Components
Function F.2.6
Provide Airport
Managers with
System Health Data
Function F.2.7
Provide ATC with
System Health Data
Function F.2.8
Provide
Maintenance
160
Table 70. COMP.2 System Health and Monitoring Segment Interface Descriptions
Number
Name
L.2.1
Critical
Item Critical
Components -> SHR Subsystem
Telemetry Signal
From Mobile
Elements
Item Critical
Subsystem
Telemetry Signal
from Stationary
Elements
SHR -> SHC
Item Critical
Subsystem
Telemetry Data
From Mobile
Elements
Item Critical
Subsystem
Telemetry Data
from Stationary
Elements
SHC -> CCIU
Item Fault Data
L.2.2
L.2.3
Transfers
Connects to
Component
COMP.2.1 System
Heath Radio (SHR)
Component
COMP.2.3
Components
Defined as "Critical"
During Advanced
Development
Component
COMP.2.1 System
Heath Radio (SHR)
Component
COMP.2.2 System
Health Computer
(SHC)
Component
COMP.2.2 System
Health Computer
(SHC)
Component
COMP.2.4
161
L.2.4
SHC-> Critical
Components
Item Critical
Component
Degraded Signal
Command and
Control Interface
Unit (CCIU)
Component
COMP.2.2 System
Health Computer
(SHC)
Component
COMP.2.3
Components
Defined as "Critical"
During Advanced
Development
162
163
COMP.1.1
Airport Management
Display Unit (AMDU)
Subsystem
Analysis Radio
HWCI
COMP.3.1
IFerret TM &
AFDIRTS Interface
Unit
Command and Control Computer (CCC) -> IFerret TM & AFDIRTS Interface Unit
Command and
Control Computer
(CCC)
HWCI
Subsystem
Date:
December 4, 2015
164
Name
Type
Performs
COMP.3
Detection Segment
Segment
COMP.3.1
Subsystem
Function F.3.1
Detect FOD
Function F.3.2
Determine FOD
Suitability from a
Distance
Function F.3.3
Determine Location
of FOD
Function F.3.4
Process Suitability
and Location of
FOD
Transfers
Connects to
L.3.1
Item FOD
Location Data to
Mobile Units
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
L.3.2
Item FOD
Characteristics
Item Suitability
Data
Component
COMP.4 Air
Retrieval Vehicle
(ARV) Segment
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
Component
COMP.6.2 Analysis
Radio
165
Transfers
Connects to
L.1.6
Item Navigation
Modes
Component
COMP.1.3
Command and
Control Computer
(CCC)
L.1.5
Item FOD
Location
Item Unsuitable
FOD Location Data
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
166
167
168
ENV.4
Environment
Electric Motor
(EM)_4
HWCI
HWCI
HWCI
HWCI
ESC4 -> EM4
COMP.4.1.13
COMP.4.1.20
Movement and Control
GPS Unit (MCGPS)
COMP.4.1.14
Electronic Speed
Controller (ESC)_2
Electronic Speed
Controller (ESC)_3
Electronic Speed
Controller (ESC)_4
HWCI
HWCI
HWCI
HWCI
COMP.4.1.10
COMP.4.1.9
Electric Motor
(EM)_6
Electric Motor
(EM)_7
Electric Motor
(EM)_8
HWCI
HWCI
HWCI
HWCI
COMP.4.1.1
Attitude and Heading
Reference Systems
(AHRS)
COMP.4.1.8
Electric Motor
(EM)_5
COMP.4.1.15
COMP.4.1.16
COMP.4.1.17
COMP.4.1.18
Electronic Speed
Controller (ESC)_5
Electronic Speed
Controller (ESC)_6
Electronic Speed
Controller (ESC)_7
Electronic Speed
Controller (ESC)_8
HWCI
HWCI
HWCI
HWCI
HWCI
AHARS -> MCCPU
HWCI
Electronic Speed
Controller (ESC)_1
COMP.4.1.12
HWCI
Electric Motor
(EM)_3
Electric Motor
(EM)_2
COMP.4.1.11
COMP.4.1.7
Barometric Altimeter
Electric Motor
(EM)_1
Part
COMP.4.1.2
COMP.4.1.6
Part
COMP.4.1.5
Propeller_8
Part
COMP.4.1.4
COMP.4.1.3
Part
COMP.4.1.28
Propeller_7
Part
COMP.4.1.27
Propeller_6
Part
COMP.4.1.26
Part
Propeller_5
Part
COMP.4.1.25
Propeller_4
Propeller_3
Propeller_2
COMP.4.1.24
COMP.4.1.23
Propeller_1
COMP.4.1.22
COMP.4.1.21
COMP.4.1.19
COMP.4.3.1
Power Distribution
Board (PDB)
HWCI
PDB -> ESC_7
HWCI
PDB-> ESC_3
COMP.4.2.1
NAV Computer
HWCI
Date:
December 4, 2015
169
Name
Type
Performs
COMP.4.1
Movement and
Control Subsystem
Subsystem
COMP.4.1.1
Attitude and
Heading Reference
Systems (AHRS)
HWCI
Function F.4.1
Move and Control
ARV
Function F.4.1.27
Determine Position
in Space
COMP.4.1.2
Barometric
Altimeter
HWCI
COMP.4.1.3
Electric Motor
(EM)_1
HWCI
COMP.4.1.4
Electric Motor
(EM)_2
HWCI
Function F.4.1.6
Spin #2 Propeller
COMP.4.1.5
Electric Motor
(EM)_3
HWCI
Function F.4.1.9
Spin #3 Propeller
COMP.4.1.6
Electric Motor
(EM)_4
HWCI
Function F.4.1.12
Spin #4 Propeller
COMP.4.1.7
Electric Motor
(EM)_5
HWCI
Function F.4.1.15
Spin #5 Propeller
COMP.4.1.8
Electric Motor
(EM)_6
HWCI
Function F.4.1.18
Spin #6 Propeller
COMP.4.1.9
Electric Motor
(EM)_7
HWCI
Function F.4.1.21
Spin #7 Propeller
COMP.4.1.10
Electric Motor
(EM)_8
HWCI
Function F.4.1.24
Spin #8 Propeller
COMP.4.1.11
Electronic Speed
Controller (ESC)_1
HWCI
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
HWCI
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
HWCI
COMP.4.1.14
Electronic Speed
Controller (ESC)_4
HWCI
Function F.4.1.2
Control #1 Motor
Speed
Function F.4.1.5
Control #2 Motor
Speed
Function F.4.1.8
Control #3 Motor
Speed
Function F.4.1.11
Control #4 Motor
Speed
Function F.4.1.28
Determine
Barometric Pressure
Function F.4.1.3
Spin #1 Propeller
170
Name
Type
Performs
COMP.4.1.15
Electronic Speed
Controller (ESC)_5
HWCI
COMP.4.1.16
Electronic Speed
Controller (ESC)_6
HWCI
COMP.4.1.17
Electronic Speed
Controller (ESC)_7
HWCI
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
HWCI
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
HWCI
COMP.4.1.19.1
MCCOPM Software
SWCI
COMP.4.1.20
Movement and
Control GPS Unit
(MCGPS)
HWCI
Function F.4.1.14
Control #5 Motor
Speed
Function F.4.1.17
Control #6 Motor
Speed
Function F.4.1.20
Control #7 Motor
Speed
Function F.4.1.23
Control #8 Motor
Speed
Function F.4.1.1
Carry out
Movement and
Control Instructions
Function F.4.1.1.1
Supply MCCOMP
Instructions
Function F.4.1.26
Determine GPS
Location
COMP.4.1.21
Propeller_1
Part
COMP.4.1.22
Propeller_2
Part
COMP.4.1.23
Propeller_3
Part
COMP.4.1.24
Propeller_4
Part
COMP.4.1.25
Propeller_5
Part
COMP.4.1.26
Propeller_6
Part
Function F.4.1.4
Generate #1 Motor
Thrust
Function F.4.1.7
Generate #2 Motor
Thrust
Function F.4.1.10
Generate #3 Motor
Thrust
Function F.4.1.13
Generate #4 Motor
Thrust
Function F.4.1.16
Generate #5 Motor
Thrust
Function F.4.1.19
Generate #6 Motor
Thrust
171
Name
Type
Performs
COMP.4.1.27
Propeller_7
Part
COMP.4.1.28
Propeller_8
Part
Function F.4.1.22
Generate #7 Motor
Thrust
Function F.4.1.25
Generate #8 Motor
Thrust
L.4.1.2
L.4.1.3
L.4.1.4
L.4.1.5
#2 Propeller <->
Environment
#3 Propeller <->
Environment
#4 Propeller <->
Environment
Barometric Altimeter /
Environment
Transfers
Item #1 Motor Thrust
Connects to
Component
COMP.4.1.21
Propeller_1
Component
ENV.4 Environment
Component
COMP.4.1.22
Propeller_2
Component
ENV.4 Environment
Component
COMP.4.1.23
Propeller_3
Component
ENV.4 Environment
Component
COMP.4.1.24
Propeller_4
Item Barometric
Pressure
Component
ENV.4 Environment
Component
COMP.4.1.2
Barometric
Altimeter
Component
ENV.4 Environment
172
L.4.1.7
L.4.1.8
L.4.1.9
L.4.1.10
L.4.1.11
L.4.1.12
#6 Propeller <->
Environment
#7 Propeller <->
Environment
#8 Propeller <->
Environment
Transfers
Item #5 Motor Thrust
Connects to
Component
COMP.4.1.25
Propeller_5
Component
ENV.4 Environment
Component
COMP.4.1.26
Propeller_6
Component
ENV.4 Environment
Component
COMP.4.1.27
Propeller_7
Component
ENV.4 Environment
Component
COMP.4.1.28
Propeller_8
Item #1 Propeller
Rotation
Item #2 Propeller
Rotation
Item #3 Propeller
Rotation
Component
ENV.4 Environment
Component
COMP.4.1.3 Electric
Motor (EM)_1
Component
COMP.4.1.21
Propeller_1
Component
COMP.4.1.4 Electric
Motor (EM)_2
Component
COMP.4.1.22
Propeller_2
Component
COMP.4.1.5 Electric
Motor (EM)_3
173
Transfers
L.4.1.13
Item #4 Propeller
Rotation
L.4.1.14
L.4.1.15
L.4.1.16
L.4.1.17
L.4.1.18
Item #5 Propeller
Rotation
Item #6 Propeller
Rotation
Item #7 Propeller
Rotation
Item #8 Propeller
Rotation
Connects to
Component
COMP.4.1.23
Propeller_3
Component
COMP.4.1.6 Electric
Motor (EM)_4
Component
COMP.4.1.24
Propeller_4
Component
COMP.4.1.7 Electric
Motor (EM)_5
Component
COMP.4.1.25
Propeller_5
Component
COMP.4.1.8 Electric
Motor (EM)_6
Component
COMP.4.1.26
Propeller_6
Component
COMP.4.1.9 Electric
Motor (EM)_7
Component
COMP.4.1.27
Propeller_7
Component
COMP.4.1.10
Electric Motor
(EM)_8
Component
COMP.4.1.28
Propeller_8
Component
COMP.4.1.3 Electric
Motor (EM)_1
174
Transfers
L.4.1.19
L.4.1.20
L.4.1.21
L.4.1.22
L.4.1.23
Connects to
Component
COMP.4.1.11
Electronic Speed
Controller (ESC)_1
Component
COMP.4.1.4 Electric
Motor (EM)_2
Component
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
Component
COMP.4.1.5 Electric
Motor (EM)_3
Component
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
Component
COMP.4.1.6 Electric
Motor (EM)_4
Component
COMP.4.1.14
Electronic Speed
Controller (ESC)_4
Component
COMP.4.1.7 Electric
Motor (EM)_5
Component
COMP.4.1.15
Electronic Speed
Controller (ESC)_5
Component
COMP.4.1.8 Electric
Motor (EM)_6
Component
COMP.4.1.16
175
Transfers
L.4.1.24
L.4.1.25
L.4.1.26
L.4.1.27
L.4.1.28
Connects to
Electronic Speed
Controller (ESC)_6
Component
COMP.4.1.9 Electric
Motor (EM)_7
Component
COMP.4.1.17
Electronic Speed
Controller (ESC)_7
Component
COMP.4.1.10
Electric Motor
(EM)_8
Component
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
Component
COMP.4.1.11
Electronic Speed
Controller (ESC)_1
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
176
L.4.1.29
L.4.1.30
L.4.1.31
L.4.1.32
Transfers
Connects to
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.14
Electronic Speed
Controller (ESC)_4
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.15
Electronic Speed
Controller (ESC)_5
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.16
Electronic Speed
Controller (ESC)_6
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.17
Electronic Speed
Controller (ESC)_7
Component
COMP.4.1.19
177
Transfers
L.4.1.33
L.4.1.34
L.4.1.35
L.4.1.36
Item AHRS
Coordinates
Item Digitized
Barometric Pressure
Connects to
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.1
Attitude and
Heading Reference
Systems (AHRS)
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.2
Barometric
Altimeter
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.20
Movement and
178
Transfers
L.4.1.37
Item XX Volts DC to
ESC_1
L.4.1.38
L.4.1.39
L.4.1.40
L.4.1.41
PDB-> ESC_3
Item XX Volts DC to
ESC_2
Item XX Volts DC to
ESC_3
Item XX Volts DC to
ESC_4
Item XX Volts DC to
ESC_5
Connects to
Control GPS Unit
(MCGPS)
Component
COMP.4.1.11
Electronic Speed
Controller (ESC)_1
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
Component
COMP.4.3.1
Power Distribution
Board (PDB)
Component
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.14
Electronic Speed
Controller (ESC)_4
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.15
Electronic Speed
Controller (ESC)_5
179
Transfers
L.4.1.42
Item XX Volts DC to
ESC_6
L.4.1.43
L.4.1.44
L.4.1.45
L.4.1.46
VR -> MCCPU
Item XX Volts DC to
ESC_7
Item XX Volts DC to
ESC_8
Item Navigation
Instructions
Item Obstacle Path
Connects to
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.16
Electronic Speed
Controller (ESC)_6
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.17
Electronic Speed
Controller (ESC)_7
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.1.20
Movement and
180
L.4.1.47
VR -> BARALT
Transfers
Connects to
Control GPS Unit
(MCGPS)
Component
COMP.4.3.3
Voltage Regulator
Component
COMP.4.1.2
Barometric
Altimeter
Component
COMP.4.3.3
Voltage Regulator
181
182
GPS Satellites
External System
HWCI
nil
Analysis Computer
COMP.4.2.3
NAV RADAR Unit
HWCI
HWCI
HWCI
HWCI
COMP.4.2.1
NAV Computer
Weight Sensor
HWCI
COMP.4.2.4
NAV GPS
HWCI
COMP.1.6
Analysis Radio
COMP.4.4.4
COMP.4.2.2
COMP.6.2
ENV.9
COMP.6.1
Obstacles
COMP.4.4.3
FOD Camera Unit
HWCI
HWCI
COMP.4.1.19
NAV Computer -> MCCPU
HWCI
COMP.4.2.5
NAV Radio
COMP.4.4.2
NAV Computer -> VERSABALL System
HWCI
VERSABALL System
HWCI
Date:
December 4, 2015
183
Name
Type
Performs
COMP.4.2
Subsystem
Function F.4.2
Navigate Airfield
COMP.4.2.1
NAV Computer
HWCI
COMP.4.2.2
HWCI
Function F.4.2.2
Process Navigation
Commands
Function F.4.2.6
Anticipate
Obstacle
Movement
Function F.4.2.7
Determine Path
Around Obstacles
Function F.4.2.3
Detect Obstacles
COMP.4.2.3
HWCI
COMP.4.2.4
NAV GPS
HWCI
COMP.4.2.5
NAV Radio
HWCI
Function F.4.2.4
Determine
Obstacle Location
Function F.4.2.8
Determine Location
Function F.4.2
Navigate Airfield
Function F.4.2.1
Receive Navigation
Commands
Function F.4.2.5
Receive Aircraft
Trajectory Data
from ATC
184
L.4.2.2
L.4.2.3
L.4.2.4
L.4.2.5
L.4.2.6
Transfers
Item (Ext)
Obstacle
Identification from
Obstacle
Item (Ext)
Aircraft Location
from Aircraft
Item (Ext)
Obstacle Location
from Obstacle
Item Obstacle
Illumination to
Obstacle
Item Location
Data from GPS
Satellites
Item At FOD
Location Signal
Item At FOD
Location Signal
Item
Coordinates
Connects to
Component
COMP.4.2.2 NAV
Camera & Image
Processing Unit
(NCIPU)
Component
ENV.7 Obstacles
Component
COMP.4.2.3 NAV
RADAR Unit
Component
ENV.7 Obstacles
Component
COMP.4.2.4 NAV
GPS
Component
ENV.9 GPS Satellites
Component
COMP.4.2.4 NAV
GPS
Component
COMP.6.1 Analysis
Computer
Component
COMP.4.2.4 NAV
GPS
Component
COMP.4.4.3 FOD
Camera Unit
Component
COMP.4.2.1 NAV
Computer
185
Transfers
L.4.2.7
Item **NAV
RADAR UNIT<->
NAV Computer**
L.4.2.8
Item Obstacle
Characteristics
L.4.2.9
L.4.2.10
L.4.2.11
Item Transport to
Disposal Location
Signal
Item At Disposal
Location Signal
Item Navigation
Instructions
Item Obstacle
Path
Connects to
Component
COMP.4.2.4 NAV
GPS
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.2.3 NAV
RADAR Unit
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.2.2 NAV
Camera & Image
Processing Unit
(NCIPU)
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.4.4 Weight
Sensor
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.4.2
VERSABALL System
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.2.1 NAV
Computer
186
L.4.2.13
L.1.18
Transfers
Item Inbound
Aircraft Trajectory
Item Navigation
Command
Item Inbound
Aircraft Data to
ARV
Item Navigation
Modes
Connects to
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.2.5 NAV
Radio
Component
COMP.4.2.5 NAV
Radio
Component
COMP.6.2 Analysis
Radio
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.4.2.5 NAV
Radio
187
188
COMP.4.1
Subsystem
Retrieval Subsystem
Subsystem
Movement and
Control Subsystem
VR - > AHRS
COMP.5.5
COMP.4.3.3
Battery Charger
HWCI
Voltage Regulator
BATT -> VR
HWCI
COMP.4.3.2
Battery
COMP.4.1.11
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
Electronic Speed
Controller (ESC)_4
HWCI
HWCI
Electronic Speed
Controller (ESC)_7
HWCI
COMP.4.1.16
Electronic Speed
Controller (ESC)_6
HWCI
COMP.4.1.14
HWCI
Power Distribution
Board (PDB)
PDB-> ESC_3
HWCI
Electronic Speed
Controller (ESC)_5
COMP.4.1.17
COMP.4.3.1
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
HWCI
Electronic Speed
Controller (ESC)_1
HWCI
COMP.4.1.15
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
HWCI
HWCI
Date:
December 4, 2015
189
Name
Type
Performs
COMP.4.3
Power Subsystem
Subsystem
COMP.4.3.1
HWCI
COMP.4.3.2
Battery
HWCI
COMP.4.3.3
Voltage Regulator
HWCI
Function F.4.3
Provide ARV
Electrical Power
Function F.4.3.9
Provide Power to
ESC_1
Function F.4.3.10
Provide Power to
ESC_2
Function F.4.3.11
Provide Power to
ESC_3
Function F.4.3.12
Provide Power to
ESC_4
Function F.4.3.13
Provide Power to
ESC_5
Function F.4.3.14
Provide Power to
ESC_6
Function F.4.3.15
Provide Power to
ESC_7
Function F.4.3.16
Provide Power to
ESC_8
Function F.4.3.1
Provide Stored
Electricity to ARV
Function F.4.3.2
Regulate NAV
Subsystem Voltage
Function F.4.3.3
Regulate
Movement and
Control Subsystem
Voltage
Function F.4.3.4
Regulate Retrieval
Subsystem Voltage
190
Transfers
Connects to
L.4.3.1
Item XX Volts DC
Regulated
Movement and
Control Subsystem
Component
COMP.4.1
Movement and
Control Subsystem
L.4.3.2
L.4.3.3
L.4.3.4
L.4.3.5
L.4.3.6
VR - > AHRS
BATT -> VR
Item XX Volts DC
Regulated NAV
Subsystem Voltage
Component
COMP.4.3.3
Voltage Regulator
Component
COMP.4.2 ARV
Navigation
Subsystem
Item XX Volts DC
Regulated Retrieval
Subsystem Voltage
Component
COMP.4.3.3
Voltage Regulator
Component
COMP.4.3.3
Voltage Regulator
Item Electrical
Energy from Battery
Component
COMP.4.4 Retrieval
Subsystem
Component
COMP.4.3.2 Battery
Item Electrical
Energy from Battery
Item XX Volts DC
to ESC_1
Component
COMP.4.3.3
Voltage Regulator
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.3.2 Battery
Component
COMP.4.1.11
Electronic Speed
Controller (ESC)_1
191
L.4.3.7
L.4.3.8
L.4.3.9
L.4.3.10
L.4.3.11
PDB-> ESC_3
Transfers
Item XX Volts DC
to ESC_2
Item XX Volts DC
to ESC_3
Item XX Volts DC
to ESC_4
Item XX Volts DC
to ESC_8
Item XX Volts DC
to ESC_6
Connects to
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.14
Electronic Speed
Controller (ESC)_4
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.16
192
Transfers
Connects to
Electronic Speed
Controller (ESC)_6
L.4.3.12
L.4.3.13
L.5.5.1
Item XX Volts DC
to ESC_7
Item XX Volts DC
to ESC_5
Item Electrical
Energy from
Charger
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.17
Electronic Speed
Controller (ESC)_7
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.15
Electronic Speed
Controller (ESC)_5
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.3.2 Battery
Component
COMP.5.5 Battery
Charger
193
194
COMP.4.4.4
Weight Sensor
COMP.4.2.4
NAV GPS
ENV.5
HWCI
FOD
External System
HWCI
COMP.4.4.1
COMP.4.2.1
HWCI
HWCI
NAV Computer
HWCI
COMP.4.4.2
VERSABALL System
Retrieval Telemetry
Radio
COMP.4.4.3
FOD Camera Unit
HWCI
Date:
December 4, 2015
195
Name
Type
Performs
COMP.4.4
Retrieval Subsystem
Subsystem
COMP.4.4.1
HWCI
COMP.4.4.2
VERSABALL System
HWCI
COMP.4.4.3
HWCI
COMP.4.4.4
Weight Sensor
HWCI
Function F.4.4
Retrieve FOD
Function F.4.4.3
Notify Personnel of
Object too Large
for Retrieval
Function F.4.4.6
Notify Personnel of
Overweight
Objects
Function F.4.4.4
Grasp FOD
Function F.4.4.7
Release FOD
Function F.4.4.1
Determine FOD
Characteristics
Function F.4.4.5
Determine FOD
weight
Name
Transfers
Connects to
L.4.4.1
Item Transport to
Disposal Location
Signal
Component
COMP.4.2.1 NAV
Computer
L.4.4.2
Item Overweight
Signal
Component
COMP.4.4.4 Weight
Sensor
Component
COMP.4.4.1
Retrieval Telemetry
Radio
Component
COMP.4.4.4 Weight
Sensor
196
Name
Transfers
Connects to
L.4.4.3
Item Grasped
FOD's Weight
Component
COMP.4.4.2
VERSABALL System
L.4.4.4
L.4.4.5
L.4.4.6
L.4.4.7
L.4.2.5
Item FOD
Item FOD
Identification from
FOD
Item Unsuitable
FOD Location Data
Item At FOD
Location Signal
Component
COMP.4.4.4 Weight
Sensor
Component
COMP.4.4.2
VERSABALL System
Component
ENV.5 FOD
Component
COMP.4.4.3 FOD
Camera Unit
Component
ENV.5 FOD
Component
COMP.4.4.1
Retrieval Telemetry
Radio
Component
COMP.4.4.3 FOD
Camera Unit
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.4.4.1
Retrieval Telemetry
Radio
Component
COMP.4.2.4 NAV
GPS
Component
COMP.4.4.3 FOD
Camera Unit
197
Name
Transfers
Connects to
L.4.2.10
Item At Disposal
Location Signal
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.4.2
VERSABALL System
198
199
Command and
Control Segment
Segment
COMP.3
Detection Segment
External System
COMP.5.1
Power Transfer Panel
HWCI
HWCI
COMP.5.3
HWCI
Power Transfer Panel - > AV Housing Unit
Generator
HWCI
COMP.5.6
COMP.5.4
AV Housing Unit
Transfer Switch
Environment
COMP.5.2
ENV.4
Segment
Charging Receptacle
HWCI
COMP.4.3.2
COMP.5.5
Charging Receptacle -> Battery Char...
Battery Charger
HWCI
Date:
Battery
HWCI
December 4, 2015
200
Table 81. COMP.5 Power and Housing Segment Functional Traceability Matrix
Number
Name
Type
Performs
COMP.5
Power and AV
Housing Segment
Subsystem
COMP.5.1
HWCI
COMP.5.2
Power Transfer
Panel
Transfer Switch
COMP.5.3
Generator
HWCI
COMP.5.4
AV Housing Unit
HWCI
COMP.5.5
Battery Charger
HWCI
COMP.5.6
Charging
Receptacle
HWCI
Function F.5
Provide AV Housing
and System Power
Function F.5.4
Transfer Power
Function F.5.1
Accept External
Power
Function F.5.2
Detect External
Power Failure
Function F.5.3
Generate
Emergency Power
Function F.5.5
Provide Air Vehicle
Housing
Function F.5.6
Secure AV
Function F.5.8
Recharge Air
Vehicle
Function F.5.7
Make Charging
Connection
HWCI
Name
Transfers
Connects to
L.5.1
Component
COMP.5.4 AV
Housing Unit
Item Electricity
Component
ENV.4 Environment
Component
COMP.5.1 Power
Transfer Panel
L.5.2
201
L.5.3
L.5.4
L.5.5
L.5.6
L.5.7
L.5.8
Name
Transfers
Item Electricity
Item Electricity
Item Electricity
Item Electricity
Item Generator
Power
Item Electricity
Connects to
Component
COMP.5.4 AV
Housing Unit
Component
COMP.3 Detection
Segment
Component
COMP.5.1 Power
Transfer Panel
Component
COMP.1 Command
and Control
Segment
Component
COMP.5.1 Power
Transfer Panel
Component
COMP.5.1 Power
Transfer Panel
Component
COMP.6 FOD
Analysis Segment
Component
COMP.5.1 Power
Transfer Panel
Component
COMP.5.2 Transfer
Switch
Component
COMP.5.1 Power
Transfer Panel
Component
COMP.5.3
Generator
Component
COMP.5.5 Battery
Charger
202
L.5.9
L.5.10
L.5.11
L.5.12
Name
Transfers
Connects to
Item (Ext)
Electrical Energy
from Power
Component
COMP.5.6
Charging
Receptacle
Component
COMP.5.2 Transfer
Switch
Item Power
Failure Signal from
Power
Component
ENV.8 Power
Component
COMP.5.2 Transfer
Switch
Item Electrical
Energy from
Charger
Item Electrical
Energy from
Charger
Component
COMP.5.3
Generator
Component
COMP.4.3.2 Battery
Component
COMP.5.5 Battery
Charger
Component
COMP.5.4 AV
Housing Unit
Component
COMP.5.6
Charging
Receptacle
203
204
IFerret TM &
AFDIRTS Interface
Unit
COMP.4.2.5
COMP.4.2.4
NAV Radio
HWCI
Subsystem
COMP.1.1
NAV GPS
Airport Management
Display Unit (AMDU)
HWCI
Subsystem
COMP.6.2
COMP.6.1
COMP.3.1
Analysis Radio
Analysis Computer
HWCI
HWCI
December 4, 2015
Name
Type
Performs
COMP.6
HWCI
COMP.6.1
Analysis Computer
HWCI
Function F.6
Analyze FOD Trends
Function F.6.2
Perform Trend
Analysis
Function F.6.3
Retain Data
Function F.6.4
Export FOD Reports
205
Name
Type
Performs
COMP.6.1.1
Analysis Software
SWCI
COMP.6.2
Analysis Radio
HWCI
Function Carry
Out Operating
Instructions
Function F.6.1
Accept FOD alert
time and date,
location
coordinates and
FOD image data
Transfers
Connects to
L.1.13
Item Reports to
Airport Managers
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
L.3.2
L.4.2.4
L.4.2.13
Item FOD
Characteristics
Item Suitability
Data
Item At FOD
Location Signal
Component
COMP.6.1 Analysis
Computer
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
Component
COMP.6.2 Analysis
Radio
Component
COMP.4.2.4 NAV
GPS
Component
COMP.6.1 Analysis
Computer
Component
COMP.4.2.5 NAV
Radio
206
L.6.1
Component
COMP.6.2 Analysis
Radio
Component
COMP.6.1 Analysis
Computer
Component
COMP.6.2 Analysis
Radio
207
This trade study was performed to make certain that the best type of battery was
selected for the Air Retrieval Vehicle (ARV) Subsystem. The battery criteria selected for
this study was based upon the characteristics ability to help best meet AFDIRTS
requirements. The selection criteria were battery gravimetric energy density (Wh/kg),
Fast Charge Time, Maintenance Requirements, and Operating Temperature Range.
While cost was not calculated into operational utility functions, cost was a factor for
selection and taken into consideration upon ARV battery type selection.
208
Battery Alternatives
Nickel Cadmium (NiCd)
The NiCd battery was the preferred choice for industrial electronics for many years.
Then in the late 1980s the ultra-high-capacity NiCd was released that gave industry a
battery that was able to hold a 60 percent higher charge than the standard NiCd
battery (Battery University, 2015). The tradeoff for this higher capacity was higher
internal resistance and a reduced cycle count (Battery University, 2015). The standard
NiCd is one of the most rugged and forgiving batteries to this day; however, it needs
appropriate maintenance to achieve a long life (Battery University, 2015). NiCd
batteries have a memory effect that causes a capacity reduction over time if the
battery is not given a full discharge cycle periodically (Battery University, 2015).
Table 85. Nickel Cadmium (NiCd) battery specifications.
Nickel Cadmium (NiCd) Battery Specifications
45-80
100 to 200 (6V pack)
1500
1h typical
moderate
20%
1.25V6
20C
1C
-40 to 60C
30 to 60 days
$50
(7.2V)
$0.04
1950
209
Battery Alternatives
Nickel-Metal Hydride (NiMH)
The Nickel-Metal Hydride (NiMH) battery was improved in the 1980s when new hydride
alloys improved past stability issues (Battery University, 2015). Today the NiMH battery
provides 40 percent higher specific energy than the standard NiCd with the absence of
toxic metals. The NiMH battery does have its disadvantages (Battery University, 2015). It
is more delicate and complicated to charge than NiCd batteries; additionally the
battery self-discharges 20 percent or more in the first 24 hours after charge (Battery
University, 2015). The NiMH battery is one of the lowest costing and most readily
available and batteries for portable devices (Battery University, 2015).
Table 86. Nickel-Metal Hydride (NiMH) battery specifications.
Nickel-Metal Hydride (NiMH) Battery Specifications
60-120
200 to 300 (6V pack)
300 to 500
2-4h
low
30%
1.25V6
5C
0.5C or lower
-20 to 60C
60 to 90 days
$60
(7.2V)
$0.12
1990
210
Battery Alternatives
Lead Acid
Lead acid batteries are heavy and is less durable than nickel- and lithium-based
systems when deep-cycled (Battery University, 2015). When the battery is fully
discharged, it causes strain on the battery and subsequently robs the battery of a small
amount of storage capacity (Battery University, 2015). While this loss is small, the weardown characteristic eventually effects the battery that its performance drops to half
the nominal capacity. Depending this depth of discharge, lead acid for deep-cycle
applications provides 200 to 300 discharge/charge cycles (Battery University, 2015).
Lead acid batteries do not charge fast. Most types can take, a full charge can take 8
to16 hours to receive a full charge. Additionally, Lead Acid batteries must always be
stored at full state-of-charge.
Table 87. Lead Acid battery specification
Lead Acid Battery Specifications
30-50
<100 (12V pack)
200 to 300
8-16h
high
5%
2V
5C
0.2C
-20 to 60C
3 to 6 months
$25
(6V)
$0.10
1970
211
Battery Alternatives
Lithium-ion (Li-ion)
Lithium is the lightest of all metals and as such it provides the greatest electrochemical
potential providing the greatest specific energy per weight (Battery University, 2015).
However, it was discovered that cycling had the potential to causing thermal runaway
in the battery released flaming gases potentially causing fires or inflicting burns (Battery
University, 2015). This inherent instability, especially while charging, forced researchers to
search for a non-metallic solution (Battery University, 2015). This solution came by utilizing
lithium ions and while lower in specific energy than lithium-metal, Li ion proved to be a
safer alternative (Battery University, 2015). Today the Lithium-ion battery is the most
promising and fastest growing battery on the market (Battery University, 2015). In
addition, Li-ion is a low-maintenance battery, has no memory and does not need to be
fully discharged to maintain good health (Battery University, 2015).
Table 88. Lithium-ion (Li-ion) Battery Specifications
Lithium-ion (Li-ion) Battery Specifications
Gravimetric Energy Density (Wh/kg)
Internal Resistance
Cycle Life (to 80% of initial capacity)
Fast Charge Time
Overcharge Tolerance
Self-discharge / Month (room temperature)
Cell Voltage(nominal)
Load Current Peak
Load Current (best result)
Operating Temperature(discharge only)
Maintenance Requirement
Typical Battery Cost
(US$, reference only)
Cost per Cycle(US$)
Commercial use since
Data retrieved from (Battery University, 2015)
110-160
150 to 250 (7.2V pack)
500 to 1000
2-4h
very low
10%
3.6V
>2C
1C or lower
-20 to 60C
not req.
$100
(7.2V)
$0.14
1991
212
Battery Alternatives
Lithium-Polymer (LiPo)
Lithium polymer batteries are similar to lithium-ion batteries (Battery University, 2015).
Both use the same cathode and anode material and consist of a similar amount of
electrolyte (Battery University, 2015). Lithium polymer is distinctive from lithium-ion in that
a micro porous electrolyte replaces the traditional porous separator (Battery University,
2015). Lithium polymer batteries have a higher specific energy (only slightly) but can be
made thinner than conventional lithium-ion cells (Battery University, 2015). Lithium
polymer cells and can be made into a flexible foil-type case, while lithium-ion batteries
need a rigid case to press their electrodes together (Battery University, 2015). This type
of rigid case can increase battery weight by 25% (Battery University, 2015). In addition to
being lighter Lithium-Polymer batteries can be made into any shape including
extremely slim designs resembling a credit card (Battery University, 2015).
Table 89. Lithium-Polymer (LiPo) Battery Specifications
Lithium-Polymer (LiPo) Battery Specifications
Gravimetric Energy Density (Wh/kg)
Internal Resistance
Cycle Life (to 80% of initial capacity)
Fast Charge Time
Overcharge Tolerance
Self-discharge / Month (room temperature)
Cell Voltage(nominal)
Load Current Peak
Load Current (best result)
Operating Temperature(discharge only)
Maintenance Requirement
Typical Battery Cost
(US$, reference only)
Cost per Cycle(US$)
Commercial use since
Data retrieved from (Battery University, 2015
100-130
200 to 300 (7.2V pack)
300 to 500
2-4h
low
~10%
3.6V
>2C
1C or lower
0 to 60C
not req.
$100
(7.2V)
$0.29
1999
213
Selection Criteria
Selection criteria for the Air Retrieval Vehicle battery type was based upon the
characteristics ability to better meet AFDIRTS system performance requirements. The
selection criteria, and their relation to system requirements have been discussed in
further detail below.
Table 90. Battery Alternatives Selection Criteria Values
Nickel
Cadmium
(NiCd)
Nickel-Metal
Hydride
(NiMH)
Lead Acid
Lithium-ion
LiPo
(LithiumPolymer)
62.5
90
40
135
115
Maintenance
Requirement
1h
3h
12H
3H
2.5h
45 days
75 days
135 Days
Operating
Temperature
Range
100 C
80 C
80 C
80 C
60 C
Gravimetric Energy
Density(Wh/kg)
Fast Charge Time
214
Selection Criteria
Maintenance Requirement
Not only does more maintenance increase Operations & Maintenance (O&M) Costs;
but it decreases the amount of time the system is available again adversely affecting
R.11 Operational Availability.
215
Weightings
The Analytical Hierarchy Process was utilized to develop weightings for selection criteria.
A pairwise comparison was performed on the battery criteria listed above and has
been listed in the chart below.
Table 91. Numerical criteria importance values
Gravimetric
Energy Density
(Wh/kg)
Operating
Temperature
Range
Fast Charge
Time
Maintenance
Requirement
0.33333
0.2
0.33333
Maintenance Requirement
0.11111
0.2
0.33333
Sum
1.64444
4.53333
9.33333
18
216
Weightings
Table 93. Normalized Criteria Comparison Matrix
Gravimetric
Energy Density
(Wh/kg)
Operating
Temperature
Range
Fast Charge
Time
Maintenance
Requirement
0.60811
0.66176
0.53571
0.5
0.2027
0.22059
0.32143
0.27778
0.12162
0.07353
0.10714
0.16667
Maintenance Requirement
0.06757
0.04412
0.03571
0.05556
Sum
Operating
Temperature
Range
Fast Charge
Time
0.60811
0.66176
0.53571
0.5
0.5763968
0.2027
0.22059
0.32143
0.27778
0.2556238
0.12162
0.07353
0.10714
0.16667
0.11724
Maintenance Requirement
0.06757
0.04412
0.03571
0.05556
0.0507385
Gravimetric Energy
Density(Wh/kg)
Operating Temperature
Range
Sum
Maintenance
Requirement
Gravimetric
Energy Density
(Wh/kg)
Criteria Weights
(W)
217
Utility Functions
Table 95. Gravimetric Energy Density Utility Function Curve
LiPo
(LithiumPolymer)
Gravimetric Energy
Density(Wh/kg)
62.5
90
40
135
115
Utility Value
0.462
0.666
0.296
0.851
218
Utility Functions
Table 97. Operating Temperature Range Utility Function Curve
Nickel-Metal
Hydride
(NiMH)
Lead Acid
Lithiumion
LiPo
(LithiumPolymer)
Operating
Temperature
Range C
100 C
80 C
80 C
80 C
60 C
Utility Value
.8
.8
.8
.6
219
Utility Functions
Utility Value
Nickel-Metal
Hydride
(NiMH)
Lead Acid
Lithiumion
LiPo
(LithiumPolymer)
1 Hour
3 Hour
12 Hour
3 Hour
2.5 Hour
.833
.0833
.833
.875
220
Utility Functions
Nickel-Metal
Hydride (NiMH)
Lead Acid
Lithiumion
LiPo
(LithiumPolymer)
Maintenance
Requirement
(in Days)
45
75
135
Utility Value
.3
.5
.9
221
Rankings
Nickel-Metal Hydride
(NiMH)
Lead Acid
Lithium-ion (Li-ion)
LiPo (Lithium-Polymer)
0.576
0.266112
0.3836
0.1705
0.576
0.49
0.255
0.255
0.204
0.204
0.204
0.153
0.117
0.117
0.0975
0.00975
0.097
0.102
0.0507
0.01521
0.0254
0.04563
0.051
0.051
Weighted SUM
0.653322
0.7105
0.42988
0.928
0.796
$0.04
$0.12
$0.10
$0.14
$0.29
Weighted Utility
Scores
Weight
Gravimetric Energy
Density(Wh/kg)
Operating
Temperature Range
Fast Charge Time
Maintenance
Requirement
$0.04
$0.12
$0.1
$0.14
$0.29
0.65332
0.71043
0.42987
0.92816
0.79625
Cost Effectiveness
Function (Operational Utility
Effectiveness Matrix
Operational Utility
Function
16.3331
5.92023
4.29872
6.62972
2.74569
222
Rankings
Table 105. Effectiveness Rankings
Effectiveness Rankings
1 Lithium-ion (Li-ion)
2
3
4
5
LiPo (Lithium-Polymer)
0.7963
0.7104
0.6533
Lead Acid
0.4299
1
2
3
5
4
Nickel Cadmium
(NiCd)
16.3331
Lithium-ion (Li-ion)
6.62972
Nickel-Metal Hydride
(NiMH)
5.92023
Lead Acid
4.29872
LiPo (LithiumPolymer)
2.74569
223
Sensitivity Analysis
Gravimetric Energy
Density(Wh/kg)
Operating
Temperature Range
Fast Charge Time
Maintenance
Requirement
LiPo (Lithium-Polymer)
Lithium-ion (Li-ion)
Lead Acid
Nickel-Metal Hydride
(NiMH)
Utility Scores
Varied by 10%
0.508
0.733
0.325
1.1
0.936
1.1
0.88
0.88
0.88
0.66
0.833
0.0833
0.833
0.875
0.3
0.5
0.9
Lithium-ion (Li-ion)
Maintenance
Requirement
Varied Weighted SUM
Original Weighted Sum
LiPo (Lithium-Polymer)
Lead Acid
Nickel-Metal Hydride
(NiMH)
0.576
0.292608
0.422208
0.1872
0.6336
0.53914
0.255
0.2805
0.2244
0.2244
0.2244
0.1683
0.117
0.117
0.097461
0.0097461
0.097461
0.10238
0.0507
0.01521
0.02535
0.04563
0.0507
0.0507
0.705318
0.769419
0.4669761
1.006161
0.86051
0.653322
0.710427
0.4298721
0.928161
0.79625
Gravimetric Energy
Density(Wh/kg)
Operating
Temperature Range
Weight
224
Selection
The Lithium-ion (Li-ion) battery ranked the highest in effectiveness and second in cost
effectiveness. The lithium-ion battery has the highest power output per kilogram, the
second greatest in operational temperature Range -20 to 60C (-4 to 140F) and
requires zero maintenance. In addition, the Lithium-ion (Li-ion) battery ranked second in
cost effectiveness with an operating cost of 0.14 cents per cycle and has a cycle life
between 500 and1000 cycles.
A sensitivity analysis was performed by varying Gravimetric Energy Density (Wh/kg) and
Operating Temperature Range; the results did not change. The Lithium-ion (Li-ion)
battery is recommended as the battery to provide power to the ARV.
225
Risk Management
At the beginning of the SM4 Project, 5 risks were identified and subsequently tracked
throughout AFDIRTS development. Initial risks have been listed below:
1. If stakeholder interviews do not uncover all potential problems; or gather
enough information about the operating environment then these issues will
become more expensive to solve in the latter stages of AFDIRTS development;
because the design will be more complex and difficult to change.
2. If care is not taken to ensure traceability throughout system development,
then system architectural questions may go unanswered during the SM4
presentation; because a traceability matrix was unavailable.
3. If the triumvirate of conceptual design; as described by Kossiakoff et al. (2011,
p.175) is not applied to requirements analysis, then system requirements may be
developed as ambiguous and difficult to decompose into subordinate
requirements,; or just not make sense; because requirements analysis was not
properly performed.
4. If lessons learned are not documented as the project progresses, then they
may become difficult to recall during development of the final report; because
a lessons learned document was not available.
5. If the ATC interface requires too much of the controllers attention, it may
hinder their ability to control air/ground traffic; because they will be overtasked.
Risk Worksheets were developed along with one risk waterfall chart to aid in tracking
and documenting these initial risks.
226
Level
Likelihood
Probability of
Occurrence
Not Likely
~10%
Low likelihood
~30%
likely
~50
Highly Likely
~70
Near Certainty
~90
Consequence of Failure (C f )
Likelihood of Failure(L f )
Level
Performance/Technical
Schedule
Cost
Minimal or no impact
Minimal or no impact
Minimal or no impact
Minor
technical/performance
shortfall
Moderate
technical/performance
shortfall
Major
technical/performance
shortfall
227
Type:
Risk Title:
Design Flaws
Cost
Schedule
Performance
Description of Risk:
The AFDIRTS system concept does not address all
operational objectives; or some operational objectives
required to meet users needs go undocumented.
Consequence if Realized:
The systems specification could be submitted to
developers without necessary system specifications. This
can become an expensive fix later in system
development.
Success Criteria
Risk Level if
Successful
Cf
Lf
228
Type:
Risk Title:
Need -> Objective ->
Requirement -> Function ->
Component Traceability
Cost
Schedule
Performance
Description of Risk:
Traceability is not maintained throughout concept
development.
Consequence if Realized:
The project schedule may be threatened because it will
require extra resources to incorporate tractability in the
end.
Success Criteria
All CORE videos developed by
Christopher Olson have been
watched.
At the end of each workday, the
project has been exported under
the filename date_Roig.
Risk Level if
Successful
Cf
Lf
229
Type:
Risk Title:
ATC interface
Cost
Schedule
Performance
Description of Risk:
The ATC interface is designed to be too complex and
requires too much of the controllers attention.
Consequence if Realized:
The complexity of the ATC interface may hinder Air Traffic
Controllers ability to control air/ground traffic because
they will be distracted. This could lead to ground or air
incursions.
Success Criteria
The ATC interface design shall
provide only two options for ATC
to select. Additionally, the
interface shall be evaluated
utilizing Usability Heuristics for
User Interface Design developed
by Jakob Nielsen and zero
usability problems shall be
discovered.
Risk Level if
Successful
Cf
Lf
230
Type:
Risk Title:
Cost
Schedule
Performance
Description of Risk:
Lessons learned are not documented as the project
progresses.
Consequence if Realized:
They may become difficult to recall during development
of the final report.
Date
Scheduled
Success Criteria
Actual
Risk Level if
Successful
Cf
Lf
231
Type:
Risk Title:
Cost
Schedule
Performance
Substandard Requirements
Description of Risk:
System requirements are ambiguous, difficult to
understand or difficult to decompose into subordinate
requirements.
Consequence if Realized:
The development of inadequate requirements may lead
to a system that does not meet users needs.
Action/Event
Success Criteria
A survey is developed on
SurveyMonkey and at least 25
Users, SMEs and Stakeholders
participate.
2.5
232
Mitigation Strategies
Likelihood of Failure (L f )
2
3
4
5
6
Concept
Validation
Functional
Analysis and
Formulation
Performance
Requirements
Analysis
Performance
Requirements
Validation
Implementation
Concept
Exploration
Performance
Requirements
Formulation
Operational
Requirements
Analysis
Needs Validation
Feasibility
Definition
Functional
Analysis
Operational
Analysis
Project Proposal
233
Number
Composite
Functional
18
Performance
93
Programmatic
Total
124
Programmatic, 7
Composite, 6
Functional, 18
Performance, 93
234
Number
Qualitative
Binary
19
Quantitative
96
Total
124
Qualitative
7%
Binary
15%
Quantitative
78%
235
Type
Description
Metric
Verified By
R.1.1
Reliability
Composite
Quantitative
Analysis
R.1.2
System Availability
Performance
Quantitative
Analysis
R.1.3
System
Maintainability
Performance
Quantitative
Analysis
R.1.4
Electromagnetic
Interference
Performance
Quantitative
Test
R.1.5
Equipment Located
Outside of Paved
Surfaces
Programmatic
Binary
Demonstration
236
Type
Description
Metric
Verified By
R.1.6
Installation and
Acceptance
Standards
Composite
Binary
Inspection
R.1.7
Breakaway
Connector
Constraint
Binary
Inspection
R.1.8
Wind Loading
Constraint
Quantitative
Test
R.1.9
Performance in
Rain
Performance
Quantitative
Test
R.1.10
Performance in
Snow
Performance
Quantitative
Test
R.1.11
Performance in
Wind
Performance
Quantitative
Test
237
Type
Description
Metric
Verified By
R.1.12
Maintenance
Procedures
Programmatic
Quantitative
Analysis
R.1.13
Cleaning
Procedures
Programmatic
Qualitative
Analysis
R.1.14
Preventative
Maintenance
Procedures
Programmatic
Qualitative
Analysis
R.1.15
Recalibration Plan
Programmatic
Quantitative
Analysis
R.1.16
Scheduled
Component
Removals
Programmatic
Qualitative
Analysis
R.1.17
Call Center
Programmatic
Quantitative
Demonstration
238
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
User Interviews
Requirements
User Surveys
R.1.1 Reliability
R.1.2 System Availability
R.1.3 System Maintainability
R.1.4 Electromagnetic Interference
R.1.5 Equipment Located Outside of Paved Surfaces
R.1.6 Installation and Acceptance Standards
R.1.7 Breakaway Connector
R.1.8 Wind Loading
R.1.9 Performance in Rain
R.1.10 Performance in Snow
R.1.11 Performance in Wind
R.1.12 Maintenance Procedures
239
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
Name
Type
Basis of
Description
Metric
Verified By
R.1.18
LINK.1.2
ATC -> AUI
Performance
F.1.9 Interface
with Air Traffic
Control
Quantitative
Analysis
Requirements
User Interviews
Number
User Surveys
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
240
R.1.19
LINK.5.9
External
Power ->
Power
Transfer
Panel
Performance
F.5.4 Transfer
Power
Quantitative
Test
241
Name
Type
Basis of
Description
Metric
Verified By
R.2
AFDIRTS
Command and
Control
Functional
Qualitative
Test
R.2.1
(KPP)
Power Failure
Performance
F.1.11 Restore
System
Binary
Test
R.2.2
Navigation Data
Functional
F.1.7 Transmit
Inbound Aircraft
Data to System
Elements
Quantitative
Test
R.2.3
Navigation Modes
Functional
Binary
Test
R.2.4
AFDIRTS
Communication
Composite
Qualitative
Demonstration
242
R.2.5
Name
Command and
Control Segment
Specification
Type
Performance
Basis of
Description
Metric
Verified By
Quantitative
Test
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
User Interviews
Requirements
User Surveys
243
Name
Type
Basis of
Description
Metric
Verified By
R.2.5.1
COMP.1.2
ATC Interface
Unit (AIU)
Specification
Performance
F.1.1
Interface
with ATC
Quantitative
Demonstration
R.2.5.2
COMP.1.1
Airport
Management
Display Unit
(AMDU)
Specification
Performance
F.1.9
Interface
with Airport
Managers
Quantitative
Demonstration
244
Name
Type
Basis of
Description
Metric
Verified By
R.2.5.3
COMP.1.3
Command
and Control
CPU
Specification
Performance
F.1.2 Initiate
System
Modes
Quantitative
Test
R.2.5.4
COMP.1.6
Command
and Control
Data Link
Specification
Performance
F.1.7 Transmit
Inbound
Aircraft Data
to System
Elements
Quantitative
Test
R.2.5.5
COMP.1.7
Maintenance
User Interface
(MIU)
Specification
Performance
F.1.10.2
Display
Maintenance
Data
Quantitative
Test
R.2.5.6
COMP.1.4
Backup CPU
Specification
Performance
F.1.11 Restore
System
Quantitative
Test
245
Name
Type
Basis of
Description
Metric
Verified By
R.2.5.7
COMP.1.3.1
Command
and Control
Software
Specification
Performance
F.1
Command
and Control
System
Quantitative
Test
Name
Type
Basis of
Description
Metric
Verified By
R.2.6
LINK.1.5
Iferret ->
AMDU Link
Specification
Performance
F.1.9
Interface
with Airport
Managers
Quantitative
Demonstration
246
Name
Type
Basis of
Description
Metric
Verified By
R.3
Safe
Operation
Composite
Qualitative
Demonstration
R.3.1
ATC
Emergency
Control
Performance
Quantitative
Test
R.3.2
Self-Test
Functional
Binary
Demonstration
R.3.3
Self-Test
Duration
Performance
Quantitative
Test
R.3.4
Maintainer
Self-Test
Functional
Binary
Test
R.3.5
System
Health
Specification
Functional
Binary
Demonstration
Test
247
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
User Interviews
Requirements
User Surveys
Table 118. System Health and Monitoring Segment Requirement Origin Map
248
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
Requirements
User Interviews
User Surveys
Name
Type
Basis of
Description
Metric
Verified By
R.3.5.1
COMP.2.4
Command and
Control
Interface Unit
(CCIU)
specification
Performance
F.2.6 Provide
Airport
Managers with
System Health
Data
F.3.2 Determine
FOD Suitability
from a
Distance
F.4.3.2 Notify
Personnel of
Object too
Quantitative
Analysis
249
Name
Type
Basis of
Description
Metric
Verified By
Large for
Retrieval
F.4.3.5 Notify
Personnel of
Overweight
Objects
R.3.5.2
COMP.2.2
System Health
Computer
(SHC)
Specification
Performance
F.2.2 Monitor
the Health of
Stationary
Element
Critical
Subsystems
Quantitative
Test
R.3.5.3
COMP.2.1
System Health
Data Link (SHR)
Specification
Performance
F.2.1 Receive
Telemetry
Signal From
Stationary
Elements
F.2.3 Receive
Telemetry Data
from Mobile
Elements
Quantitative
Demonstration
R.3.5.4
COMP.2.2.1
System Health
Software
Specification
Performance
F.2.4.1 Direct
SHC operation
Quantitative
Test
250
Name
Type
Basis of
Description
Metric
Verified By
Name
Type
Description
Metric
Verified By
R.3.5.5
L.INK.2.2
SHR -> SHC
Internal Interface
Requirement
Performance
Quantitative
Test
251
Type
Basis of
Description
Metric
Verified By
R.4
FOD
Detection
Segment
Composite
F.3 Scan
Airfield for
FOD
Binary
Demonstration
R.4.1.1
FOD
Location
Reporting
Performance
Quantitative
Test
R.4.1.2
Suitability
Reporting
Performance
F.3.3
Determine
Location of
FOD
F.4.3.2 Notify
Personnel of
Object too
Large for
Retrieval
Quantitative
Demonstration
R.4.1.3
FOD
Detection
Performance
F.3.1 Detect
FOD
Binary
Test
R.4.1.4
Group
Object
Detection
Performance
F.3.1 Detect
FOD
Quantitative
Test
252
Type
Basis of
Description
asphalt or concrete, Any portion of a
runway light fixture (in-pavement or
edge light), An adjustable crescent
wrench up to 8 in. (20 cm) in length), A
deep socket (at least 2 in. (5 cm) in
length), A piece of rubber from an
aircraft tire, A distorted metal strip (up to
8 in. (20 cm) in length), Fuel cap (aircraft
or automotive), Lug nut, Hydraulic line
(from aircraft or GSE, up to 8 in. (20 cm)
in length).
The system shall have the ability to
detect an unpainted, metal cylinder,
measuring 1.2 in (3.1 cm) high and 1.5 in
(3.8 cm) in diameter.
Metric
Verified By
Quantitative
Test
R.4.1.5
Metal
Cylinder
Detection
Performance
F.3.1 Detect
FOD
R.4.1.6
Sphere
Detection
Performance
F.3.1 Detect
FOD
Quantitative
Test
R.4.1.7
Lighting
Conditions
Performance
F.3.1 Detect
FOD
Qualitative
Test
R.4.1.8
Automated
Retrieval
Suitability
Functional
F.3.2
Determine
FOD Suitability
from a
Distance
Qualitative
Test
253
Type
Basis of
Description
Metric
Verified By
R.4.1.9
Performance
F.3.1 Detect
FOD
Quantitative
Demonstration
Detection
Time
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
User Interviews
Requirements
User Surveys
254
Name
Type
Basis of
Description
Metric
Verified By
R.4.1.10
COMP.3.1
IFerret
Specification
&AFDIRTS
Interface
Unit
Performance
F.3 Scan
Airfield for
FOD
Binary
Demonstration
Name
Type
R.4.1.11
LINK.3.1
IFerret &
AFDIRTS
Interface
Unit <-> NAV
Radio
Internal
Interface
Specification
Performance
Basis of
Description
Metric
Quantitative
Verified
By
Test
255
Name
Type
Description
Metric
R.5.1.1
Performance
Quantitative
Verified
By
Analysis
*Units in inches
R.5.1.2
Maximum All-Up
Weight (AUW)
Performance
Quantitative
Analysis
R.5.1.3
MAX Operational
Flight Time
Performance
Quantitative
Test
R.5.1.4
Performance
Quantitative
Test
R.5.1.5
MAX Operating
Wind Speed
Performance
Quantitative
Test
256
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD) Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
SME Interviews
User Surveys
Requirements
Table 126. Air Retrieval Vehicle (ARV) Segment Requirement Origin Map
257
Name
Type
Basis of
Description
Metric
Verified By
R.5.1
COMP.4
Air Retrieval
Vehicle
Composite
F.4 Transport
Retrieval
Subsystem (ARV)
Quantitative
R.5.2
COMP.4.1
Movement
and Control
Subsystem
Specification
Performance
Quantitative
Demonstration
Test
R.5.3
COMP.4.2
Navigation
Subsystem
Functional
F.4.2 Navigate
Airfield
F.4.2.2 Process
Navigation
Commands
F.4.2.3 Detect
Obstacles
F.4.2.5 Receive
Aircraft
Trajectory Data
from ATC F.4.2.6
Anticipate
Quantitative
Demonstration
Test
258
Name
Type
R.5.4
COMP.4.3
Power
Subsystem
Performance
R.5.5
COMP.4.4
FOD Retrieval
Subsystem
Functional
Basis of
Obstacle
Movement
F.4.2.7 Determine
Path Around
Obstacles
F.4.2.8 Determine
Location
F.4.4 Provide ARV
Electrical Power
F.4.3 Retrieve
FOD
F.4.3.5 Notify
Personnel of
Overweight
Objects
Description
Metric
Verified By
Quantitative
Test
Binary
Demonstration
259
Type
Description
Metric
Verified By
R.5.2
Performance
Quantitative
Demonstration
Test
Movement
and Control
Subsystem
Specification
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD) Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
SME Interviews
User Surveys
Requirements
Table 129. Air Retrieval Vehicle (ARV) Movement and Control Subsystem Requirement Origin Map
260
Name
Type
Basis of
Description
Metric
R.5.1.1
COMP.4.1.3
COMP.4.1.4
COMP.4.1.5
COMP.4.1.6
COMP.4.1.7
COMP.4.1.8
COMP.4.1.9
COMP.4.1.10
Electric Motor
Specification
Performance
Quantitative
Verified
By
Test
R.5.1.2
COMP.4.1.11
COMP.4.1.12
COMP.4.1.13
COMP.4.1.14
COMP.4.1.15
COMP.4.1.16
COMP.4.1.17
COMP.4.1.18
Electronic
Speed
Controller
Specification
Performance
F.4.1.2 Control #1
Motor Speed
F.4.1.5 Control #2
Motor Speed
F.4.1.8 Control #3
Motor Speed
F.4.1.11 Control #4
Motor Speed
F.4.1.14 Control #5
Motor Speed
F.4.1.17 Control #6
Motor Speed
F.4.1.20 Control #7
Motor Speed
Quantitative
Test
261
Name
Type
Basis of
Description
Metric
F.4.1.23 Control #8
Motor Speed
Verified
By
R.5.1.3
COMP.4.1.19.1
MCCOMP
Software
Specification
Performance
Quantitative
R.5.1.4
COMP.4.1.25
COMP.4.1.25
COMP.4.1.25
COMP.4.1.25
Propeller
Specification
Performance
F.4.1.16 Generate #5
Motor Thrust
F.4.1.19 Generate #6
Motor Thrust
F.4.1.22 Generate #7
Motor Thrust
F.4.1.25 Generate #8
Motor Thrust
Quantitative
Inspection
R.5.1.5
COMP.4.1.21
COMP.4.1.22
COMP.4.1.23
COMP.4.1.24
Pusher
Propeller
Specification
Performance
F.4.1.4 Generate #1
Motor Thrust
F.4.1.7 Generate #2
Motor Thrust
F.4.1.10 Generate #3
Motor Thrust
F.4.1.13 Generate #4
Motor Thrust
Quantitative
Inspection
Test
262
Name
Type
Basis of
Description
Metric
Verified
By
R.5.1.7
COMP.4.1.19
Movement
and Control
Computer
(MCCOMP)
Specification
COMP.4.1.20
Movement
and Control
GPS Unit
(MCGPS)
Specification
Performance
Quantitative
Test
Performance
Quantitative
Test
R.5.1.8
Table 131. Air Retrieval Vehicle (ARV) Movement and Control Subsystem Internal Interface Specification
Number
Name
Type
Description
Metric
R.5.1.6
LINK.4.1.18
ESC1 -> EM1 Internal
Interface Requirement
Performance
Quantitative
Verified
By
Inspection
263
Name
Type
Description
Metric
Verified By
R.5.2
Mobile Unit
Navigation
Functional
Binary
Demonstration
R.5.2.1
Performance
Quantitative
Demonstration
R.5.2.2
(KPP)
Mobile Unit
Movement
Clearance
Performance
Quantitative
Demonstration
R.5.2.2.1
Separation from
Obstacles
Performance
Quantitative
Test
R.5.2.2.2
Separation from
Aircraft
Performance
Quantitative
Test
R.5.2.2.3
Separation from
Personnel
Performance
Quantitative
Test
R.5.2.2.4
Separation from
Vehicles
Performance
Quantitative
Test
R.5.2.3
Emergency
Posture
Functional
Binary
Demonstration
264
Name
Type
Description
Metric
Verified By
R.5.2.4
FOD Location
Functional
Binary
Demonstration
R.5.2.5
Navigation
Commands
Functional
Binary
Demonstration
R.5.2.6
Disposal Area
Functional
Binary
Test
User Interviews
Requirements
User Surveys
Table 133. Air Retrieval Vehicle (ARV) Navigation Subsystem Requirement Origin Map
265
Requirements
User Interviews
User Surveys
Name
Type
Basis of
Description
Metric
R.5.2.8
COMP.4.2.1
NAV Computer
Specification
Performance
F.4.2.2 Process
Navigation
Commands
Quantitative
Verified
By
Test
266
Name
Type
Basis of
Description
Metric
R.5.2.9
COMP.4.2.4
NAV GPS
Specification
Performance
F.4.2.8 Determine
Location
Quantitative
R.5.2.10
COMP.4.2.3
NAV RADAR Unit
Specification
Performance
F.4.2.4 Determine
Obstacle
Location
Verified
By
Test
Quantitative
Test
R.5.2.11
COMP.4.2.5
NAV Radio
Specification
Performance
F.4.2.1 Receive
Navigation
Command
F.4.2.5 Receive
Aircraft Trajectory
Data from ATC
Quantitative
Test
R.5.2.12
COMP.4.1.1
Attitude and
Heading
Performance
F.4.1.27 Determine
Position in Space
Quantitative
Test
267
Name
Type
Basis of
Reference
Systems (AHRS)
R.5.2.13
COMP.4.1.2
Barometric
Altimeter Unit
Specification
Description
Metric
Verified
By
Quantitative
Test
F.4.1.28 Determine
Barometric
Pressure
Table 135. Air Retrieval Vehicle (ARV) Navigation Subsystem Internal Interface Specification
Number
Name
Type
Description
Metric
R.5.2.14
LINK.4.2.6
NAV GPS -> NAV Computer
Internal Interface Requirement
Performance
Quantitative
Verified
By
Inspection
Test
268
Name
Type
Basis of
Description
Metric
R.5.3
Power Subsystem
Specification
Performance
F.4.4 Provide
ARV
Electrical
Power
Quantitative
Verifi
ed By
Test
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD) Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
SME Interviews
User Surveys
Requirements
Table 137. Air Retrieval Vehicle (ARV) Power Subsystem Requirement Origin Map
269
Name
Type
Basis of
Description
Metric
R.5.3.1
COMP.4.3.2
Battery
Specification
Performance
F.4.4.1 Provide
Stored Electricity
to ARV
Quantitative
Verified
By
Test
R.5.3.2
COMP.4.3.1
Power Distribution
Board (PDB)
Specification
Performance
F.4.4.5 Provide
Power to ESC_1
F.4.4.6 Provide
Power to ESC_2
F.4.4.7 Provide
Power to ESC_3
F.4.4.8 Provide
Power to ESC_4
F.4.4.9 Provide
Power to ESC_5
F.4.4.10 Provide
Power to ESC_6
F.4.4.11 Provide
Power to ESC_7
F.4.4.12 Provide
Power to ESC_8
Quantitative
Test
R.5.3.3
COMP.4.3.3
Voltage
Regulator
Specification
Performance
F.4.4.2 Regulate
NAV Subsystem
Voltage
Quantitative
Test
270
Name
Type
Description
Metric
R.5.3.4
LINK.4.3.4
BATT -> VR
Internal Interface
Specification
Performance
Quantitative
Verified
By
Test
271
Table 140. Air Retrieval Vehicle (ARV) FOD Gripping Subsystem Requirements
Number
Name
Type
Basis of
Description
Metric
Verified By
R.5.4
FOD
Retrieval
Functional
Binary
Demonstration
R.5.4.2
FOD
Weighing
Functional
Quantitative
Test
R.5.4.3
(KPP)
FOD Max
Weight
Performance
Quantitative
Test
R.5.4.4
FOD
location
Performance
Quantitative
Test
R.5.4.5
(KPP)
FOD
Dimensions
Performance
Quantitative
Test
272
Name
Type
Basis of
Description
Metric
Verified By
R.5.4.6
FOD
Grasping
Performance
Quantitative
Test
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD)
Detection Equipment
User Interviews
Requirements
User Surveys
Table 141. Air Retrieval Vehicle (ARV) FOD Gripping Subsystem Requirement Origin Map
273
Name
Type
Basis of
Description
Metric
R.5.4.1.1
COMP.4.4.3
FOD
Camera Unit
Specification
Performance
F.4.3.1
Determine
FOD
Characteristics
Quantitative
Verified
By
Test
R.5.4.1.2
COMP.4.4.4
Weight
Sensor
Specification
COMP.4.4.2
VERSABALL
System
Specification
Performance
F.4.3.4
Determine
FOD weight
Quantitative
Test
Quantitative
Test
R.5.4.6.1
Performance
274
COMP.4.4.1
Retrieval
Telemetry
Radio
Specification
Performance
F.4.3.2 Notify
Personnel of
Object too
Large for
Retrieval
Quantitative
Test
Table 143. Air Retrieval Vehicle (ARV) FOD Retrieval Subsystem Internal Interface Specifications
Number
Name
Type
Description
Metric
R.5.4.8
LINK.4.4.3
Weight Sensor <-> Versaball System
Internal Interface Specification
Performance
Quantitative
Verified
By
Test
275
Name
Type
Description
Metric
Verified By
R.6
AV Housing
and Power
Specification
Performance
Quantitative
Test
R.6.1
Back-Up
Power
Performance
Quantitative
Test
R.6.2
Loss of
External
Power
Performance
Quantitative
Test
276
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
Requirements
User Interviews
User Surveys
Table 145. ARV Housing and Power Segment Requirement Origin Map
Name
Type
Basis of
Description
Metric
R.6.3
COMP.5.4
ARV housing
Specification
Performance
F.5 Provide
AV Housing
F.5.6
Secure ARV
Quantitative
Verified
By
Test
R.6.4
COMP.5.5
Battery
Charger
Specification
Performance
F.5.8
Recharge
Air Vehicle
Quantitative
Test
277
Name
Type
Basis of
Description
Metric
R.6.5
COMP.5.3
Generator
Specification
Performance
F.5.3
Generate
Emergency
Power
Quantitative
Verified
By
Test
R.6.6
COMP.5.1
Power
Transfer
Panel
Specification
Performance
F.5.1
Accept
External
Power
F.5.4
Transfer
Power
Quantitative
Test
R.6.7
COMP.5.2
Transfer
Switch
Specification
Performance
F.5.2
Detect
External
Power
Failure
Quantitative
Test
R.6.8
COMP.5.6
Charging
Receptacle
Specification
Performance
F.5.7
Make
Charging
Connection
Quantitative
Test
278
Name
Type
Description
Metric
R.6.9
LINK.5.7
Gen -> PWR
Transfer PNL
Int. Interface
Spec
Performance
Quantitative
Verified
By
Test
279
Name
Type
Basis of
Description
Metric
Verified By
R.7
FOD Analysis
Segment
Functional
F.6 Analyze
FOD Trends
F.6.2 Perform
Trend Analysis
F.6.4 Export
FOD Reports
Qualitative
R.7.1
Types of Data
Functional
Binary
Test
R.7.1.1
Storage of
Data
Performance
F.6.1 Accept
FOD alert time
and date,
location
coordinates
and FOD
image data
F.6.3 Retain
Data
Quantitative
Test
Demonstration
280
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD) Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
Requirements
User Interviews
User Surveys
Name
Type
R.7.2
COMP.6.1
Analysis
Computer
Specification
Performance
Basis
of
Description
Metric
Quantitative
Verified
By
Test
281
Name
Type
R.7.3
COMP.6.2
Analysis Radio
Specification
Performance
R.7.4
COMP.6.1.1
Analysis
Software
Specification
Performance
Basis
of
Description
Metric
Quantitative
Verified
By
Test
Quantitative
Test
Name
Type
Description
Metric
R.7.5
LINK.6.1
Analysis Radio -> Analysis
Computer Internal
Interface Specification
Performance
Quantitative
Verified
By
Test
282
The SM4 project is representative of a real world contract between a user and system
developer. In this case, the contract is between the Johns Hopkins University and the
Student. Since calendar dates are not contractually binding, the decision was made to
use a contractual document (the Integrated Master Plan) versus an Integrated Master
Schedule (IMS).
I initially estimated that the project would be complete in 326 hours. This was based
upon other students projects; however, my project required approximately 602 hours to
complete. The reasons for the difference in time is multifaceted. First, my initial concept
was impractical. I selected a problem that I was passionate about solving; this led to a
strong (and unintentional) desire to develop solutions to the problem without the proper
elicitation of requirements from users and SMEs. My concept was reworked several
times until I had a good grasp of the needs analysis phase of the SE Method, and my
new concept was properly validated utilizing this method.
Second, the concept definition phase took longer than planned due to an incomplete
functional architecture. I did not perform functional analysis and formulation down to
the level necessary to make the make or buy decision and had to redo the functional
architecture. Even though the project took me longer than planned to complete. I
believe it allowed me to gain an excellent understanding of the systems engineering
discipline. I feel that I still have much to learn and am reluctant to say I am a Master. I
will continue to strive to become more knowledgeable through on the job training, and
research. Even though I do not feel that I have yet Mastered the SE discipline, I do
feel I have earned the M.S. Degree.
283
Activity Number
Activities
Planned
A
A01
A01a
A01a1
A01a1.
1
141
312
141
312
39
A01a3
10
34
A01b1
20
A01b2
14
A01c
34
A01c1
15
A01c2
10
A01c2.
1
A01d
+176
67
+33
20
-14
10
-24
215
15
A01a2
A01b
+171
34
284
Activity Number
Activities
Planned
A01d1
14
A01d2
20
A01d3
10
D01
D01a
80
110
80
110
20
D01a1
10
D01a2
10
D01b
20
D01b1
10
D01b2
10
D01b2.
1
d01c
+30
60
+40
20
20
5
20
d01c1
10
d01c2
10
285
Activity Number
d01c2.
1
D01d
Activities
Planned
10
20
D01d1
10
D01d2
10
D01d2.
2
D02
D02a
E
E01
E01a
Concept Selected
Performance Requirements Analysis
E01a1
E01a2
E01a2.
1
10
105
206
+101
20
60
+40
20
86
+66
105
E01b1
10
E01b2
10
E01b2.
1
-10
286
Activity Number
Activities
Planned
E01c
E01d
(CDRL) Functional Analysis Report Complete *should have performed after concept selection
29th, 2015
Concept Selection
30
20
E01d1
10
E01d2
10
E01e
E01e1
E01f
30
45
E01f2
15
F01
G
G01
H
+10
December 7th,2015
E01f1
November
-15
15
15
0
January 3rd, 2016
Totals
326
602
+276
Hours
Hours
Hours
287
Lessons Learned
Let the SMEs contribute to requirements development, but dont overdo data
collection.
I used an online survey (surveymonkey) to collect responses from SMEs. This was a
mistake. It took time soliciting participation and later, more time sorting through the
data. If the project was real or I was contributing to the body of knowledge it would
have been appropriate. Since it wasnt, my time spent in this area could have been
better utilized elsewhere. 1 or 2 experts in each domain should suffice.
3. Watch Christopher Olsons CORE videos before you enroll in 645.800
When I started the project, I did believe it was necessary to apply the SE method to
develop the concept and proposal papers. In my view, these deliverables were just
precursors to the project. Christopher Olson puts this into perspective by demonstrating
how the SE method should be applied to the project from the concept paper to the ASpec.
4. Perform the SE process (Requirements Analysis -> Functional Analysis - > Physical
Definition -> Design Validation) for each phase of the SE-Method whether your
deliverable requires it or not!
Some deliverables do not require all of the steps be performed to complete. For
example functional analysis is not required to produce the proposal; but it is required to
define feasibility and validate the need. Therefore, follow the steps of the SE Method
and let your deliverables become by-products of the process. If you use CORE, it will
help you move into the next phase of the SE Method.
288
289
Appendix A
290
Table of Contents
Student Biography. 292
Capability Gap/System Justification 293
Needs Statement. 294
AFDIRTS Description.... 294
Existing Technologies.. 294
AFDIRTS Preliminary Context/N2 Diagrams.. 296
Stakeholders............... 299
Risks.. 300
Schedule. 302
Systems Engineering Justification 305
Operational Objectives. 306
Measures of Effectiveness.. 307
291
Student Biography
Penniless after utilizing most of my earnings to obtain a private pilots license while
fueling general aviation aircraft at a small Fixed Based Operation (FBO)/flight training
center on Fort Lauderdale Executive Airport, I fell in love with aviation and decided to
enlist in the U.S. Navy. After completion of basic training I attended Aviation Electronics
Technician Intermediate (I) Level Repair A School, I performed three deployments on
various aircraft carriers as part of the Aircraft Intermediate Maintenance Departments
(AIMD) Sea Operational Detachment (SEAOPDET). While there, I became proficient in
the component level troubleshooting and repair of communication/navigation avionics
installed on various type/model/series (T/M/S) aircraft.
In 2004, I received orders to Helicopter Anti-Submarine Squadron Seven (HS-7) where I
performed Organizational maintenance for the first time. This was an unconventional
career move for an I Level Aviation Electronics Technician, but I had a strong desire to
work with the aircraft and despite the steep learning curve, I eventually became
proficient in all aspects of HH-60H and SH-60F maintenance.
In 2005 I was selected to lead the squadrons Avionics Shop where I successfully
supported the squadron through two demanding Arabian Gulf deployments. In this
position, I was crucial in helping the squadron attain many of its operational goals,
including the rapid integration of the HH-60H Fast Tactical Imaging (FTI) system into a
hostile environment. This involved technical coordination with the USS Harry S. Trumans
(CVN-75) Carrier Intelligence Center (CVIC) to solve compatibility problems that existed
between the aircraft and the ships user interface (just prior to the battle group transiting
the Hormuz Strait). The FTI integration was a success, which facilitated the first ever
forward looking inferred (FLIR) video of Iranian surface threats while entering the
Arabian Gulf.
In 2008, I was assigned to the Center for Naval Aviation Technical Training Unit
(CNATTU) Jacksonville, Florida where I earned my Master Training Specialist Designation.
While at CNATTU, I was responsible for leading 18 instructors as the Avionics I Level
Maintenance Training Unit (MTU) LPO, in this position I supervised the instruction and
curriculum development of 22 aviation I level maintenance courses. I also served as
292
the Lead Instructor and Course Curriculum Model Manager for the U.S. Navys I Level
IFF Maintenance Course (C-102-4052). In this role I was responsible for the local
Instruction and Navy-wide curriculum development for the course.
In 2010, I earned a Bachelors Degree in Liberal Studies with a focus in Electronic
Instrumentation from Excelsior College and nearly completed a Masters in Aeronautical
Science from Embry Riddle. I made the decision to switch graduate programs after
receiving orders to Air Test and Evaluation Squadron 23 (VX-23), Patuxent River, MD. This
decision was based on my realization of how my love for technology, solving problems
and leading people could be intertwined with aviation through the Systems Engineering
discipline.
I began the Masters in Systems Engineering Program at Johns Hopkins University
Engineering for Professionals in the fall of 2012 and have been steadily working the
program while simultaneously performing government contract maintenance oversight
at VX-23.
This program has allowed me to see the big picture not only through the eyes of a
sailor/government employee, but from the perspectives of a taxpayer, hardware
engineer, software engineer, maintainer, logistician, analyst, project manager, and
finally; a systems engineer.
I look forward to completing the project and demonstrating my mastery of the
discipline.
293
enable airports to autonomously detect, remove and track FOD on Aircraft Operating
Areas (AOA) 24 hours a day, 7 days a week.
Needs Statement
The Airfield FOD Detection, Identification, Removal and Tracking System (AFDIRTS) is to
provide a safe autonomous method of detecting, removing and tracking FOD from
AOAs 24 hours a day 7 days a week while not interfering with normal airport
operations. The AFDIRTS will be capable of command and control from the tower
allowing the airport to focus FOD searches in specific areas; or halt operations as
necessary. The AFDIRTS will be capable of operation in inclement weather. The AFDIRTS
shall be reliable, affordable and maintainable. The AFDIRTS will comply with all FAA
Regulations.
AFDIRTS Description
The AFDIRTS will be designed to autonomously detect, remove and track FOD on
Airport Operating Areas. The FAA has been testing and evaluating FOD detection
systems that automatically detect FOD and notify airport personnel when discovered
(Weller, 2014); however, automated retrieval is a new concept.
Analysis shows that automated vehicle technology is mature enough to be combined
with automated FOD detection systems to provide airports with a fully automated
method of detecting, retrieving and tracking FOD on Airport Operating Areas. The
needs analysis phase of the SE method produced a preliminary physical architecture
(Context Diagram) and the functional architecture (N2 Diagram) shown in section 3.
Existing Technologies
The FAA is currently evaluating a few different FOD detection technologies placed at
four different airfields (Weller, 2014). These technologies are listed below.
Tarsier Radar Currently being tested at T.F. Green Airport (PVD) in Providence, RI
(PVD). Developed by QinetiQ Corporation, Tarsier utilizes millimeter wave radars that
are mounted on rigid towers to sweep runways. Once FOD is detected, the integrated
294
day/night camera zooms in to identify it and ultimately have airport personnel retrieve it
(QinetiQ, 2015).
IFerret Is currently being evaluated at Chicago OHare (ORD) International Airport.
Developed by Stratech Inc., IFerret consists of a high resolution camera mounted on
rigid towers that scan for and detect FOD on Runways, Taxiways and Aircraft Aprons.
Once the FOD is detected, personnel are notified to retrieve it (Stratech, 2015).
FODetect - Is currently being tested at Boston Logan (BOS) international Airport.
Developed by XSight Systems, FODetect utilized a high resolution camera combined
with millimeter wave radar mounted on airport lighting fixtures (XSight, 2015).
FOD Finder Is currently being tested at Chicago OHare (ORD) International Airport.
Developed by Trex Enterprises Corporation, FOD Finder utilizes a Millimeter Wave Radar
and Infrared Cameras that are mounted on top of Airport Vehicles that scout AOAs for
FOD.
The most technically challenging of the operational objectives will be to provide
automated FOD retrieval. The reason for this it that it will require the use of an
autonomous vehicle to perform the functions necessary to meet the operational
objective.
According to the Automated Vehicle Institute (2013) an autonomous vehicle should
drive itself in a manner similar to that driven by a safe human driver. To do this they
outline a four step functional loop that the vehicle must perform to be effective. These
steps are:
1.
2.
3.
4.
manual driving on the road with all 13 accidents reportedly caused by human error
(Swartz, 2015). However, autonomous driving on an active airfield will be more
complicated with function 3 plan its next move having to be decomposed further
into functions that interface with the tower and ground controllers. This will make the
already difficult job of the air traffic controller even harder by giving the controllers
additional responsibilities.
A possible solution to this problem might be to eliminate the need for Air Traffic Control
to give automated vehicles clearance. This might be accomplished by designing even
more autonomy into the vehicle. For example, the vehicle might be able to decide on
its own whether or not to enter a taxiway by obtaining data from sensors. Or, make the
decision to enter an active runway based on logic i.e. once an aircraft enters the
pattern the vehicle must exit the runway. This could be made feasible by designing
vehicle loiter points adjacent to active runways.
296
Obstacles
Government
Organizations
Environment
Air Traffic
Control
Physical Obstacle
Location
Regulations
Heat Energy
Sand Material
Salt Material
Ice Material
Rain Material
Snow Material
Wind Force
UV Rays Energy
Active Obstacle
Detection Signal?
Reports
Heat Energy
RF Energy
Sound Energy
Resistance Force
Exhaust Material
Obstacles
Government
Organizations
Environment
FOD Data
Location Data
Status Data
Air Traffic
Control
Airport
Managers
Constraint Data
Status Data
Reports Data
Airport
Managers
Aircraft
Operators
Found Item
Notification Data
FOD Material
Aircraft
Operators
Power
Maintainer
FOD
Electrical
Energy
Excess
Electrical Energy
Power
Good Parts
Good Material
SW Update
Signal
Query Signal
Bad Parts
Used Material
Fault Codes
Status Data
Maintainer
Physical FOD
Location
Active FOD
Detection Signal?
FOD
297
Airport
Managers
Constraint Data
Government
Organizations
Air Traffic
Control
FOD
Power
Aircraft
Operators
Maintainer
Environment
Obstacles
Regulations
Electrical
Energy
Physical
Obstacle Location
Active Obstacle
Detection Signal?
F.1
Operate
Safely
Heat Energy
Sand Material
Salt Material
Ice Material
Rain Material
Snow Material
Wind Force
UV Rays Energy
F.2
Perform System
Command and
Control
Functions
Good Parts
Good Material
SW Update Signal
Query Signal
Physical FOD
Location
F.3
Operate in
Extreme
Weather
Heat Energy
RF Energy
Sound Energy
Resistance Force
Exhaust Material
Bad Parts
Fault Codes
Used Material
Obstacles
Maintainer
Power
Aircraft
Operators
Environment
F.4
Perform
Reliability,
Availability and
Maintainability
Functions
FOD Data
Location Data
Status Data
Active FOD
Detection
Emission?
F.5
Detect FOD
FOD Material
F.6
Retrieve FOD
AAFDRTS
F.7
Perform FOD
Trend Analysis
FOD Data
Found Item
Notification
Location Data
Reports Data
Air Traffic
Control
FOD
Airport
Managers
Government
Organizations
298
Stakeholders
During the needs analysis phase potential stakeholders were contacted as a means of
gathering information for operational and functional analysis. The stakeholders are
listed below will continue to be utilized throughout the development of the AFDIRTS
system.
Sean Mulholland
Safety Director, SevenBar Aviation
Sean has experience as the safety director for SevenBar Aviation. His operational and
employee safety experience in airline terminal / ramp / flight settings will be a benefit to
system development.
Unnamed
Operations and Maintenance Manager
Unnamed manages a staff of 9 field and building maintenance workers in the
performance of daily airport maintenance activities. These activities include snow and
FOD removal. He functions as a primary liaison with airlines, airport tenants and users.
The AFDIRTS will perform some of the functions he is currently responsible for; therefore,
his experience will aid in the elicitation of requirements.
Michael Villarreal
Airline Pilot/Captain, United Parcel Service (UPS)
Michaels 30+ year career as a commercial pilot will help identify system constraints,
elicit requirements and help address safety concerns from a pilots perspective.
Dillon Stewart
A&P Apprentice, CFDI Aero
Dillon is an A&P Apprentice and participates in daily FOD checks of hangar bays and
aircraft ramps in his area of responsibility. His perspective will be utilized during the
elicitation of requirements.
299
Unknown
Air Traffic Controller
An Air Traffic Controller has yet to be identified, but it is expected that one will be
contacted prior to the start of operational requirements analysis.
Risks
A preliminary risk assessment was conducted to identify risks that will have to be
addressed during the SM4 project. These risk have been documented below.
1. If stakeholder interviews do not uncover all potential problems; or gather enough
information about the operating environment then these issues will become more
expensive to solve in the latter stages of AFDIRTS development; because the design will
be more complex and difficult to change.
2. If care is not taken to ensure traceability throughout system development, then
system architectural questions may go unanswered during the SM4 presentation;
because a traceability matrix was unavailable.
3. If the triumvirate of conceptual design; as described by Kossiakoff et al. (2011, p.175)
is not applied to requirements analysis, then system requirements may be developed as
ambiguous and difficult to decompose into subordinate requirements,; or just not make
sense; because requirements analysis was not properly performed.
4. If lessons learned are not documented as the project progresses, then they may
become difficult to recall during development of the final report; because a lessons
learned document was not available.
5. If the ATC interface requires too much of the controllers attention, it may hinder their
ability to control air/ground traffic; because they will be overtasked.
Schedule
The Merged SM4 concept and proposal paper is representative of a real world
contract between a user and system developer. In this case, the contract is between
the Johns Hopkins University and the Student. Calendar dates are not contractually
300
binding (DOD, 2005); therefore, the decision was made to use a contractual document
(the Integrated Master Plan) versus an Integrated Master Schedule (IMS). I hope to
deliver the final report and presentation by November 16, 2015.
301
Difference
Activities
Actual
312
176
215
181
210
195
10
10
34
Planned
Activity
Number
A
A01
A01a
A01a1
A01a1.1
136
34
15
A01a2
A01a3
A01b
136
34
A01b1
20
20
A01b2
14
14
34
A01c
34
A01c1
15
15
A01c2
10
10
34
A01c2.1
A01d
34
A01d1
14
14
A01d2
20
20
10
A01d3
B
B01
C
10
6
302
Activities
Actual
Planned
Activity
Number
D
D01
D01a
100
20
D01a1
10
D01a2
10
D01b
20
D01b1
10
D01b2
10
D01b2.1
d01c
5
20
d01c1
10
d01c2
10
d01c2.1
D01d
5
20
D01d1
10
D01d2
10
D01d2.2
D02
D02a
Difference
5
20
10
303
Activities
Actual
Planned
Activity
Number
E
E01
E01a
E01b2
E01d2
E01f1
E01f2
G
G01
H
20
E01e1
F01
20
E01d1
E01c1
E01f
20
E01b2.1
E01e
20
E01b1
E01d
100
E01a2
E01c
180
Concept Selected
E01a1
E01b
Difference
15
0
15
20
20
20
20
H01
Total
430
304
The AFDIRTS will be an engineered product and will satisfy a specied need.
The AFDIRTS consists of diversified components that will have intricate relationships
with one another; it is multidisciplinary and relatively complex.
The AFDIRTS will use advanced technology in ways that are central to the
performance of its primary functions and therefore involves development risk, while
relatively high in cost.
To ensure the AFDIRTS met the feasibility and demonstrable need criterion, the
needs analysis phase of the SE method was applied to the SM4 proposed project
concept. By taking this approach, these criterion were validated during the feasibility
definition and needs validation steps of the needs analysis phase.
When applying the systems engineering method to the FOD detection and retrieval
problem, operational analysis was performed through discussions with potential
stakeholders. Research was conducted to determine the FAAs current capabilities and
future plans regarding FOD detection. This led to the identification of a capability gap
of current FOD detection systems.
After the capability gap was identified, a needs statement was developed and
overarching operational objectives were derived from the perceived users needs.
Once operational objectives were defined, they were uploaded into CORE;
operational objectives are listed below:
305
Operational Objectives
1.
1.2.
1.3.
1.4.
1.5.
2.
3.
4.
5.
6.
4.1.
4.2.
4.3.
4.4.
5.2.
5.3.
5.4.
5.5.
5.6.
5.7.
6.2.
6.3.
7.2.
7.3.
After all operational objectives had been defined and decomposed, functional
analysis was performed to derive preliminary system functions; these functions were
uploaded into CORE (overarching system functions are documented in Figure 2.)
A feasibility study was performed to establish feasibility criteria for the AFDIRTS concept.
Once feasibility criteria had been applied to eligible system concepts, a feasible system
concept was defined and effectiveness analysis was performed based upon the ability;
and feasibility of the preliminary system concept to meet the customer needs within
cost, time, technological, operational, safety and regulatory constraints. From this, a
preliminary physical architecture was developed that facilitated the creation of the
preliminary context diagram (shown in Figure 1.). After a feasible system concept was
defined the needs validation step was performed. During this phase Measures of
Effectiveness (MOE) were developed based upon interviews and discussions with
potential customers as well as research into the FAAs current FOD detection system
guidance published in Advisory Circular 150/5220-24 and FOD Management guidance
published in Advisory Circular 150/5210-24. The top five MOEs are listed below:
Measures of Effectiveness
1. Provide redundancy for components or subsystems deemed High Risk during Failure
Mode, Effects and Criticality Analysis (FMECA) (Binary MOE expressed as a metric of
operational objective 1.1 Provide system redundancy)
2. Detect an unpainted metal cylinder, measuring x inch high and x inches wide; and a
white, grey, or black sphere with the radius of x inches) any time day or night in clear
weather and inclement weather conditions*. (Measurement MOE expressed as a
measurement of operational objective 2.0 Provide automate FOD detection) This MOE
was based in part on current FAA FOD detection system guidance listed in AC
150/5220-24.
3. Capable of retrieving FOD from anywhere on the AOA in under 5 minutes after
detection night and day and in clear and inclement weather conditions* (Binary MOE
expressed as a metric of operational objective 3.0 provide automated FOD retrieval).
307
In the event that FOD is detected on an active runway the system must take action. This
event will trigger the initiation of function 6.0 Retrieve FOD. How this Function is
accomplished will depend on feedback from stakeholders. These stakeholders will help
answer questions; such as when, if ever, should ATC be alerted of FOD detection on the
AOA? Should the system request clearance to enter an active runway? How about
Taxiways? What does the system do if it detects FOD too large to be retrieved? What
does it do with biological FOD (i.e. animal feces)? Technical research will have to be
performed to determine if the system can even distinguish between biological FOD and
hard FOD? Input from stakeholders on questions like these will be crucial to developing
a system that meets user needs.
2.
If a system element becomes immobilized on the AOA it becomes a hazard to not only
arriving and departing aircraft, but ground traffic as well. Stakeholders will be consulted
to determine the appropriate response to this type of failure. A few different options
can be analyzed. First, the mobile system element could be designed to fail in a certain
manner (i.e. when a BIT failure is experienced the mobile system elements will maneuver
onto an unpaved section of the AOA). Another option is for the mobile unit to
308
immediately stop and flash emergency lights until airport personnel can retrieve the
unit.
3.
Once FOD is retrieved it will be analyzed; complying with function 7.0 Provide trend
analysis functions. As this function is decomposed further (in the concept exploration
stage) questions will have to be answered about how the AFDIRTS interfaces with
retrieved FOD. For example, should the system try to account for missing components
reported by aircraft operators/support personnel? For example, if a fuel truck driver
notices a missing part on his truck, and reports it; how is this handled?
This scenario has many potentially solutions. First, the system could automatically take a
picture of the FOD and sent it electronically to aircraft operators/support personnel for
identification; or have personnel manually sort through all FOD retrieved from AOAs; or
is any of this necessary? Can the FOD just be disposed of? Feedback from stakeholders
as well as guidance from FAA Advisory Circular 150/5210-24 Airport FOD
Management will help determine how the system performs these functions.
Once operational scenarios were evaluated preliminary operational objectives were
translated into preliminary operational requirements which were subsequently
uploaded into CORE, and will be refined even further with inputs from the stakeholders
and documented in the Requirements Analysis Report during operational requirements
analysis.
Once the needs analysis phase had been completed, the system concept and
proposal paper was submitted to project mentor Jonathan Selby, Ph.D. for review.
309
Appendix B
310
Table of Contents
Overview. 312
Needs Statement. 312
AFDIRTS Description. 312
Systems Engineering 312
Requirements Elicitation. 315
Section I:
Section II:
Section III:
Section IV:
Section V:
Section VI:
Section VII:
Section VIII:
Bibliography .. 408
311
Overview
The aviation industry spends approximately $7 billion dollars per year in non-bird strike
FOD damage to aircraft (McCreary, 2010). In addition to the financial burden, FOD
damage to aircraft occurring at critical moments in flight has led to loss of life and
complete destruction of aircraft. An automated FOD detection and retrieval system
would enable airports to autonomously detect, remove and track FOD on Aircraft
Operating Areas (AOA) 24 hours a day, 7 days a week.
Needs Statement
The Airfield FOD Detection, Identification, Removal and Tracking System (AFDIRTS) is to
provide a safe autonomous method of detecting, identifying, removing and analyzing
FOD trends from airports while not interfering with normal airport operations. The AFDIRTS
will provide a method of centralized command and control and be capable of
operation in inclement weather. The AFDIRTS shall be reliable, maintainable and
affordable.
AFDIRTS Description
The AFDIRTS will be designed to autonomously detect, remove and track FOD on
Airport Operating Areas. The FAA has been testing and evaluating FOD detection
systems that automatically detect FOD and notify airport personnel when discovered;
however, automated retrieval is a new concept. Analysis shows that automated
vehicle technology is mature enough to be combined with automated FOD detection
systems to provide airports with a fully automated method of detecting, retrieving and
tracking FOD on Airport Operating Areas. The Needs Analysis phase of the SE method
produced Operational Requirements that have been further refined during the
Concept Exploration phase and listed in this report.
Systems Engineering
The Requirements Analysis Report (RAR) documents the results of the Concept
Exploration Phase of the systems engineering method. The four steps of the Concept
312
have been listed in Appendix C). These Operational Objectives state the goal of the
system and helped facilitate the creation of Operational Requirements, which in turn;
help answer the why question.
To fully develop the system concept, the remaining interrogatives; how, who, where,
when, and what were addressed by developing Operational Scenarios (system
context) and the development of multiple competing operational concepts (CONOPS)
that could meet AFDIRTS mission needs. The refinement of Operational Scenarios (Listed
in Appendix D) helped address the where and when interrogative; while the
updated competing Concepts of Operations (Listed in Appendix E) helped address the
potential hows and whos.
According to Kossiakoff et al. (2011) requirements documentation is not carved in
stone requirements documents are living documents that are continually evolving as
the system is developed. As the AFDIRTS system concept progresses into the Concept
Definition phase, the requirement document listed in Appendix G will be refined even
further.
314
Requirements Elicitation
315
Aircraft Operators
The discussions and polling of aircraft operators revealed that they had major concerns
with the maturity of retrieval subsystem technology. More specifically, the ability of
these elements to remain clear of airport traffic. This is a concern because if aircraft
operators are uncomfortable sharing the airfield with unmanned system elements then
their animosity may result in the overutilization of crew resources (allocating them to
detect and avoid unmanned system elements versus other manned traffic); moreover,
it may have unintended consequences such as underutilization of the airfield. These
concerns lead to the realization and documentation of Risk 1.0 If aircraft operators do
not trust the systems ability to keep mobile elements clear of their aircraft, then aircraft
operators may make unnecessary errors; because they were utilizing excessive crew
resources to spot mobile system elements. and 2.0 If aircraft operators do not trust the
systems ability to keep mobile elements clear of their aircraft, then they may decide to
utilize neighboring airfields; because they feel airfields without automated FOD
detection and retrieval systems are safer. These risks along with others will be listed in
the Risk Management Report.
Aircraft Maintainers
A detailed study of the characteristics of FOD found on airfields was unrealistic for the
SM4 project. In naval aviation, maintenance personnel are utilized to perform FOD
searches on all aircraft operating areas. Since this is the case, and for the purpose of
this project; 28 Naval Aviation Maintainers from across the country were polled to help
determine the characteristics of FOD commonly found on aircraft operating areas.
The survey results show that each naval aircraft maintainer spends an average of 28
minutes a day searching for FOD on military airfields. The large amount of time
searching for FOD on airfields not only reinforces the need for an Airfield FOD Detection,
Identification, Removal and Tracking System; but gives credibility to the naval aircraft
maintainers ability to make accurate assessments regarding the characteristics of FOD
found on airfields.
316
The results of Naval Aircraft Maintainer polling estimates that the percentage of FOD
found weighing over 1lb is less than .24 percent on aircraft ramps, less than .25 percent
on airport taxiways, and less than .19 percent on runways.
From these results, it is believed that a FOD retrieval system should be capable of
retrieve FOD weighing at least 1 pound to be effective. This would permit the
automated retrieval of over 99.75 percent of all FOD and led to the development of
KPP R.5.2 The FOD retrieval subsystem shall be capable of retrieving FOD weighing up
to 1 pound or .45359237 kilograms.
Respondent #MilMaint-27 discussed the commonalities of the majority of FOD found on
airfields; stating that The most common FOD I've found in 14 years experience is 99%
random hardware such as nuts, bolts, rivets, safety wire & rocks. His statement along
with discussions from other SMEs and feasibility constraints placed upon the physical
characteristics of retrieval sub-system concepts led to the development of KPP R.5.4
The FOD retrieval subsystem shall be capable of retrieving FOD with dimensions of up
to 12 inches in length 12 Inches in width and 12 inches in height.
317
Section I
Survey Results
318
Survey Results
Participant Qualifications
Respondent #ATC-1
Name: Colleen Raney
Occupation: Air Traffic Control
Job Title: Military Radar
Unit/Mission Controller
Respondent #MilMaint-1
Name: John Laine
Occupation: Military Aircraft
Maintenance
Job Title: : NAVAIR Corrosion
Analyst
Respondent #MilMaint-2
Name: Armando Rodriguez
Occupation: Military Aircraft
Maintenance
Job Title: Maintenance Master
Chief
Respondent #MilMaint-3
Name: Martin J. Wydra
Occupation: Military Aircraft
Maintenance
Job Title: VX-23 FOD Program
Manager
Respondent #MilMaint-4
Name: John Svoboda
Occupation: Military Aircraft
Maintenance
Job Title: QA Inspector
Respondent #MilMaint-5
Name: Steve B.
Occupation: Military Aircraft
Maintenance
Job Title: QA Inspector
Respondent #MilMaint-6
Name: Kristopher Micon
Occupation: Military Aircraft
Maintenance
Job Title: Maintenance Chief
Respondent #MilMaint-7
Name: Anonymous
Occupation: Military Aircraft
Maintenance
Job Title: Maintenance Officer
Respondent #MilMaint-8
Name: Bauer, Edgar
Occupation: Military Aircraft
Maintenance
Job Title: Workcenter Supervisor
Respondent #MilMaint-9
Name: Gary Wilson
Occupation: Military Aircraft
Maintenance
Job Title: Avionics Tech
Respondent #MilMaint-10
Name: Scott
Occupation: Military Aircraft
Maintenance
Job Title: A/C Mechanic
Respondent #MilMaint-11
Name: Ronnie E Mendoza
Occupation: Military Aircraft
Maintenance
Job Title: Maintenance Control
Chief
Respondent #MilMaint-12
Name: Aaron R Graybill
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Electronics
Technician
Respondent #MilMaint-13
Name: Michael Muncy
Occupation: Military Aircraft
Maintenance
Job Title: Division Chief
Respondent #MilMaint-14
Name: Quentin Salmons
Occupation: Military Aircraft
Maintenance
Job Title: Maintenance Chief
319
Respondent #MilMaint-15
Name: Justin Monahan
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Electronics
Technician
Respondent #MilMaint-16
Name: Jay Daniel Oliver
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Structural
Mechanic
Respondent #MilMaint-17
Name: William
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Electronics
Technician
Respondent #MilMaint-18
Name: Anonymous
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Mechanic
Respondent #MilMaint-19
Name: Chris Reynolds
Occupation: Military Aircraft
Maintenance
Job Title: Quality Assurance
Supervisor
Respondent #MilMaint-20
Name: Anonymous
Occupation: Military Aircraft
Maintenance
Job Title: Aircrew Survival
Equipment
Respondent #MilMaint-21
Name: Anonymous
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Electronics
Technician
Respondent #MilMaint-22
Name: Jennifer
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Electrician
Respondent #MilMaint-23
Name: Melissa Phaff
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Structural
Mechanic
Respondent #MilMaint-24
Name: Dan Crivello
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Machinist Mate
Respondent #MilMaint-25
Name: Anonymous
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Mechanic
Respondent #MilMaint-26
Name: Mark Ugi
Occupation: Military Aircraft
Maintenance
Job Title: Quality Assurance
Supervisor
Respondent #MilMaint-27
Name: Anonymous
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Structural
Mechanic
Respondent #MilMaint-28
Name: Anonymous
Occupation: Military Aircraft
Maintenance
Job Title: Aviation Structural
Mechanic
320
321
again, so there is that to think about if the vehicle is in fact capable of non-movement
area cleanup
Takeaways: A major concern for Air traffic Controllers is that they retain the ability of
have complete control of all operations conducted on the movement areas. However,
when asked how much of a burden would it be on controllers to grant clearance to
FOD vehicles respondent #1 replied somewhat of a burden.
If the system is designed to automatically detect and avoid aircraft movement,
controllers would not have the additional burden of granting clearance to automated
system elements. However, since the controllers orchestrate movement along the
airfield, controllers should have the ability to remove system elements from the airfield
when the need arises.
ATC -1 expressed concerns about FOD retrieval on grass and used a plastic bag as an
example. This capability should be incorporated into the system if possible.
323
Aircraft Operators
Overview:
Number of respondents: 6
Question #1: If a fully automated FOD detection and retrieval system was made
available to autonomously detect and avoid aircraft while searching for and retrieving
FOD. What level of reliability should it have for you as an operator to feel comfortable
sharing the airfield with these units? This can be expressed however you choose. (i.e. 1
incident per 365 days of operation, 100 percent reliable....etc.)
Answers
Aircraft Operator - 1:
99.5%
Aircraft Operator - 2:
50% reliable
Aircraft Operator - 3:
Aircraft Operator - 4:
99.9%
Aircraft Operator - 5:
Aircraft Operator - 6:
100%
Question #2: Please add any thoughts you have in regards to the development of an
automated FOD detection and retrieval system from an Airline Pilot perspective. This
could be anything... functions you think would be required, problems you would expect
to encounter or elaborate on risk.
Answers
Aircraft Operator 1:
Aircraft Operator 2:
324
Make it simple. Red light means don't taxi onto, cross the
runway or takeoff. Light goes out or turns green - go.
Aircraft Operator 3:
Aircraft Operator 4:
Aircraft Operator 5:
Aircraft Operator 6:
Takeaways: System reliability is a big concern for pilots with 4 out of 6 aircraft operators
responding that the system should have near %100 reliability regarding the avoidance
of aircraft.
In order for the system to be safe and effective, users must have complete trust that
mobile system elements will remain clear of traffic. If operators begin to second guess
mobile system element reliability, then the crew resources required to avoid a possible
incursion between mobile system elements and aircraft could distract aircrew to the
point of jeopardizing safe airfield navigation. It is expected that upon initial operating
capability aircraft operators may be speculative (and therefore distracted) of sharing
the airfield with unmanned mobile system elements; however, this risk can be minimized
over time by a combination of training, successful operations and the minimization of
the mobile elements potential to damage aircraft by its design.
325
MilMaint-12: 11 to 20 min
MilMaint-23: 21 to 30 min
MilMaint-2: 11 to 20 min
MilMaint-13: 21 to 30 min
MilMaint-24: 21 to 30 min
MilMaint-3: 31 to 45 min
MilMaint-14: 21 to 30 min
MilMaint-25: 11 to 20 min
MilMaint-15: 21 to 30 min
MilMaint-26: 1 hour
MilMaint-16: 21 to 30 min
MilMaint-27: 11 to 20 min
MilMaint-17: 31 to 45 min
MilMaint-28: 11 to 20 min
MilMaint-7: 21 to 30 min
MilMaint-18: 21 to 30 min
MilMaint-8: 21 to 30 min
MilMaint-19: 11 to 20 min
MilMaint-20: 31 to 45 min
MilMaint-10 1 hour
MilMaint-21: 21 to 30 min
MilMaint-11: 21 to 30 min
MilMaint-22: 11 to 20 min
10
25.5
25.5
25.5
60
15.5
25.5
15.5
35.5
15.5
15.5
35.5
25.5
25.5
25.5
25.5
15.5
45
45
25.5
15.5
25.5
45
60
25.5
35.5
15.5
326
Average:
28 Minutes
Question #2: On average how many personnel participate in ALL daily command FOD
walkdowns? For example, if 15 participate on days and 20 participate on nights; 35
personnel would have participated in that days FOD walkdown.
Answers
MilMaint-1: 35
MilMaint-12: 25
MilMaint-23: 20
MilMaint-2: 35
MilMaint-13: 30
MilMaint-24: 35
MilMaint-3: 35
MilMaint-14: 35
MilMaint-25: 35
MilMaint-4: 35
MilMaint-15: 35
MilMaint-26: 35
MilMaint-5: 35
MilMaint-16: 35
MilMaint-27: 25
MilMaint-6: 5
MilMaint-17: 35
MilMaint-28: 25
MilMaint-7: 35
MilMaint-18: 25
MilMaint-8: 35
MilMaint-19: 25
MilMaint-9: 35
MilMaint-20: 30
MilMaint-10: 100
MilMaint-21: 30
MilMaint-11: 35
MilMaint-22: 20
35
35
30
35
35
35
25
35
20
25
35
35
30
25
20
25
35
35
35
25
35
35
100
35
30
35
Average:
33 Personnel
327
Question #3: During FOD walkdown on respective airfield locations; please estimate the
percentage of FOD found weighing over 8 oz. or 1/2 of a pound.
Answers
Respondent
Aircraft Ramp
Taxiway
Runway
MilMaint-1:
<0%
<0%
<0%
MilMaint-2:
<2%
<2%
<2%
MilMaint-3:
<20%
<0%
<0%
MilMaint-4:
<0%
<0%
<0%
MilMaint-5:
<2%
<2%
<2%
MilMaint-6:
<10%
<0%
<0%
MilMaint-7:
<2%
<2%
Dont Know
MilMaint-8:
<5%
<2%
<0%
MilMaint-9:
<2%
<2%
<10%
MilMaint-10:
<2%
<2%
<2%
MilMaint-11:
<2%
<5%
<5%
MilMaint-12:
<0%
<0%
<0%
MilMaint-13:
<0%
<0%
<0%
MilMaint-14:
<2%
<2%
<2%
MilMaint-15:
<2%
<0%
<0%
MilMaint-16:
<0%
<0%
<0%
MilMaint-17:
<0%
<0%
<0%
MilMaint-18:
<2%
<0%
<0%
MilMaint-19:
<20%
<20%
Dont Know
MilMaint-20:
<5%
<2%
<2%
MilMaint-21:
Dont Know
Dont Know
Dont Know
MilMaint-22:
<2%
<2%
<2%
MilMaint-23:
<10%
<5%
<0%
MilMaint-24:
<0%
<0%
<0%
MilMaint-25:
<0%
<0%
<0%
MilMaint-26:
<0%
<0%
<0%
328
MilMaint-27:
<2%
Dont Know
Dont Know
MilMaint-28:
Dont Know
Dont Know
Dont Know
<2.62%
<1.41%
<.84%
Average:
Question #4: During FOD walkdown on respective airfield locations; please estimate the
percentage of FOD found weighing over 1 pound.
Answers
Respondent
Aircraft Ramp
Taxiway
Runway
MilMaint-1:
<0%
<0%
<0%
MilMaint-2:
<2%
2%
2%
MilMaint-3:
<0%
<0%
<0%
MilMaint-4:
<0%
<0%
<0%
MilMaint-5:
<0%
<0%
<0%
MilMaint-6:
<0%
<0%
<0%
MilMaint-7:
<0%
<0%
<0%
MilMaint-8:
<2%
<2%
<0%
MilMaint-9:
<0%
<0%
<2%
MilMaint-10:
<0%
<0%
<0%
MilMaint-11:
Dont Know
Dont Know
Dont Know
MilMaint-12:
<0%
<0%
<0%
MilMaint-13:
<0%
<0%
<0%
MilMaint-14:
<0%
<0%
<0%
MilMaint-15:
<0%
<0%
<0%
MilMaint-16:
<0%
<0%
<0%
MilMaint-17:
<0%
<0%
<0%
MilMaint-18:
<0%
<0%
<0%
MilMaint-19:
<2%
<2%
Dont Know
MilMaint-20:
<0%
<0%
<0%
329
MilMaint-21:
Dont Know
MilMaint-22:
<2%
<2%
MilMaint-23:
<0%
<0%
MilMaint-24:
Dont Know
MilMaint-25:
<0%
<0%
MilMaint-26:
<0%
<0%
MilMaint-27:
<0%
Dont Know
Dont Know
MilMaint-28:
Dont Know
Dont Know
Dont Know
Dont Know
Dont Know
Dont Know
Dont Know
Average:
< .24%
< .25%
< .19%
Question #5: Please add any thoughts you have in regards to the development of an
automated FOD detection and retrieval system from a military aircraft maintenance
perspective. This could be anything... functions you think would be required, problems
you would expect to encounter or elaborate on risk.
***Only Respondents that answered the question have been listed***
Answers
MilMaint-2:
MilMaint-7:
MilMaint-9:
I believe that the expense to install this system will make this a low
priority and may never actually happen in this current cost slashing
government.
MilMaint-10:
MilMaint-12:
MilMaint-20:
MilMaint-26:
MilMaint-27:
Takeaways:
28 Military maintenance personnel were polled from Navy organizational aircraft
maintenance squadrons across the country. The survey reviled that Military personal
spend an average of 28 Minutes per shift utilizing 33 personnel to search for FOD on
aircraft operating areas. This results in 15.4 man-hours per day per Navy unit.
331
Section II.
Updated User Needs
332
MN-AU-01
MN-AU-02
OO-01
OO-01
OO-01
MN-ATC-04
distractions.
333
MN-ATC-05
OO-09
OO-01
OO-07
OO-08
MN-AM-04
OO-09
system.
MN-AM-05
OO-10
standards.
334
MN-AW-02
OO-01
OO-11
elements.
OO-11
OO-11
maintenance.
MN-SM-03
OO-08
MN-SM-04
OO-08
components.
MN-SM-05
OO-08, OO-11
OO-09
335
SECTION III.
Updated Operational Objectives
336
Operational Objectives
Number
OO-01
OO-02
OO-03
OO-04
OO-05
OO-06
OO-07
OO-08
OO-09
OO-10
OO-11
OO-012
337
Section IV.
Updated Operational Scenarios
338
Section V.
Competing CONOPS
340
Utilizing the combined FOD detection and retrieval subsystem configuration will
eliminate the need to transmit the precise location of FOD to retrieval subsystems
since the retrieval system will already be at the location of the detected FOD.
Since both retrieval and detection subsystems are mobile they can be easily
integrated into existing airfields.
System elements can be easily removed from the airfield in the case of inclement
weather.
Disadvantages
-
The mobile detection system will unlikely be capable of detecting and retrieving
quickly moving FOD (such as a plastic bag).
In order for the mobile units to travel over unpaved airport surfaces (such as a grass
area), a method of removing FOD from the units themselves; must be developed to
prevent FOD from migrating onto the airfield.
The system will not be able to make use of existing Commercial off the Shelf (COTS)
FOD detection systems.
In order to meet requirement R.3.1.1 The system shall be capable of detecting FOD
within 4 minutes of a FOD occurrence will require many units.
341
Command
and Control
Elements
Reports
Maintenance
Obstacle
Detection and
Avoidance
342
Utilizing existing FOD detection technology will minimize development costs normally
associated with new system development.
Since there will be many detectors operating from a distance, the system will be
capable of quickly sweeping the airfield for FOD.
The maturity of mobile retrieval subsystem locomotion elements will maximize system
reliability.
Disadvantages
-
The mobile retrieval system element will unlikely be capable of retrieving fast moving
FOD (such as a plastic bag).
In order for the mobile retrieval units to travel over unpaved airport surfaces (such as
a grass area), a method of removing FOD from the units themselves; must be
developed to prevent FOD from migrating onto the airfields.
343
Command
and Control
Elements
Reports
Maintenance
Obstacle
Detection and
Avoidance
FOD
Detection
FOD Retrieval
344
The ability of retrieval units to navigate over obstacles can decrease retrieval time
and minimize navigation complexity.
The potential for airborne retrieval units to nimbly transverse the airfield over paved
and unpaved surfaces; may allow the airborne units to retrieve migrating FOD (i.e.
plastic bags, cardboard, and paper)
Once FOD was retrieved from grassy areas dragging FOD back onto the airfield as a
result of surface contact would not be a concern.
If the system is successful, the FAA may see drones as an advantage to the
aviation community.
Disadvantages
-
The drone technology may be frowned upon by the FAA; and getting approval
for the units to operate may involve too much time navigating bureaucratic red
tape.
Airborne units will be more susceptible to course deviation due to wind gusts and jetblast.
345
Command
and Control
Reports
Maintenance
FOD
Detection
Obstacle
Detection and
Avoidance
FOD
Disposal
FOD Retrieval
346
SECTION VI.
Updated Context Diagram
347
Air Traffic
Control
Environment
Command (D)
Heat (E) Sand (M)
Salt (M) Hail (M)
Ice (M) Water (M)
Wind (F) Cold (E)
FAA
Airport
Managers
Health (D)
Unsuitable FOD
Location (D)
Heat (E)
Sound (E)
Resistance (F)
Unsuitable FOD
Location (D)
Status (D)
Reports (D)
Reports (D)
Obstacles
Location (D)
AFDIRTS
Electrical
Energy (E)
Forces (F)
Energy (E)
Data (D)
Signals (S)
Materials (M)
Visual FOD
Location (E)
Visual FOD
Identification (D)
Aircraft
Operators
Parts (M)
Materials (M)
Fault Codes (D)
FOD
Excess
Electrical (E)
Parts (M)
Materials (M)
SW Update (S)
Query (S)
Power
Maintainer
348
Section VII.
Requirements Document
349
350
R Need Statement
Requirement Statement:
The Airfield FOD Detection, Identification, Removal and Tracking System (AFDIRTS)
is to provide a safe autonomous method of detecting, identifying, removing and
analyzing FOD trends from airports while not interfering with normal airport
operations. The AFDIRTS will provide a method of centralized command and
control (KPP R.2.1) and be capable of operation in inclement weather. The
AFDIRTS shall be reliable, maintainable and affordable.
Refined By Subordinate Requirements:
R.1 Safe Operation
R.2 System Command and Control
R.3 FOD Scanning and Detection
R.4 FOD Reporting
R.5 FOD Retrieval
R.6 Mobile Unit Locomotion
R.7 Provide FOD Trend Analysis
R.8 System Communication
R.9 Technical Support
R.10 Installation and Acceptance Standards
R.11 Reliability, Availability and Maintainability
R.12 Operate in Adverse Weather Conditions
351
R.1.1
R.1.1.1
verified by
refined by
Emergency
Demonstration
Requirement
VerificationRequ...
refined by
verified by
Execution Speed
Test
Requirement
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall not cause damage to airport personal or property; nor shall it
become a distraction to operations or support personnel.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.1.1 Emergency
Based Upon Operational Objective:
OO-1 Provide safe operation
352
R.2.1
refined by
refined by
R.2.2
R.2.3
refined by
R.2.4
refined by
verified by
Command and
Control System
System Command
Location of
Aircraft
Unsuitable FOD
Power Failure
Test
Function
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
Test
Test
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall be capable of centralized command and control of all system
elements.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.2.1 System Command
R.2.2 Location of Aircraft
R.2.3 Unsuitable FOD
R.2.4 Power Failure
Based Upon Operational Objective:
OO-2 Provide efficient and effective system command and control.
353
R.3.1
refined by
Airfield Scanning
verified by
Demonstration
FOD Detection
Requirement
R.3.1.1
refined by
R.3.2
VerificationRequ...
Requirement
verified by
refined by
Detection Time
Demonstration
Requirement
VerificationRequ...
verified by
basis of
R.3.2.1
refined by
Detect FOD
Group Object
Detection
Function
Requirement
Demonstration
R.3.2.2
R.3.2.4
refined by
Metal Cylinder
Detection
Requirement
verified by
R.3.2.3
refined by
Sphere Detection
Requirement
Test
R.3.2.5
refined by
verified by
Automated
Retrieval Suitabil...
Test
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
refined by
Lighting
Conditions
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall be capable of scanning the airfield and detecting single and
multiple FOD items.
Requirement Rationale:
This functional requirement originated from FAA AC 150/5220-24 Airport Foreign
Object Debris (FOD) Detection Equipment.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.3.1 Airfield Scanning
R.3.2 FOD Detection
Based upon Operational Objective:
OO-3 Provide a method of airfield scanning and FOD detection.
354
R.4.1
R.4.1.1
refined by
R.4.1.2
refined by
verified by
FOD Location
Reporting
Demonstration
Requirement
VerificationRequ...
refined by
R.4.1.3
refined by
verified by
Active Reporting
Passive Reporting
Suitability
Reporting
Test
Requirement
Requirement
Requirement
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall be capable of reporting FOD location data and FOD
characteristics to the retrieval subsystem.
Requirement Rationale:
This performance requirement originated from FAA AC 150/5220-24 Airport Foreign
Object Debris (FOD) Detection Equipment.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.4.1 FOD Location Reporting
Based upon Operational Objective:
OO-4 Provide a method of FOD Reporting.
355
R.5.1
refined by
R.5.2
refined by
R.5.3
refined by
R.5.4
refined by
verified by
FOD Weight
Determination
FOD Weight
FOD location
FOD Dimensions
Demonstration
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
Test
Test
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall be capable autonomously retrieving FOD from both paved and
grass surfaces.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.5.1 FOD Weight Determination
R.5.2 FOD Weight
R.5.3 FOD location
R.5.4 FOD Dimensions
Based upon Operational Objective:
OO-05 Provide a method of FOD retrieval.
356
R.6.1
refined by
R.6.2
refined by
R.6.3
refined by
refined by
R.6.4
R.6.5
refined by
R.6.6
refined by
R.6.7
refined by
verified by
Mobile Unit
Navigation
Mobile Unit
Movement Clea...
Separation from
Obstacles
Separation from
Aircraft
Separation from
Personnel
Separation from
Vehicles
Test
Requirement
Requirement
Requirement
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
R.6.2.1
refined by
R.6.2.2
refined by
Demonstration
FOD Location
Emergency
Posture
VerificationRequ...
Requirement
Requirement
R.6.2.3
refined by
verified by
verified by
verified by
verified by
verified by
verified by
Standby Location
Demonstration
Demonstration
Test
Test
Test
Test
Requirement
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall provide a method of locomotion for mobile system elements.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.6.1 Mobile Unit Speed
R.6.2 Mobile Unit Navigation
R.6.3 Mobile Unit Movement Clearance
R.6.4 Separation from Obstacles
R.6.5 Separation from Aircraft
R.6.6 Separation from Personnel
R.6.7 Separation from Vehicles
Based upon Operational Objective:
OO-06 Facilitate mobile element locomotion.
357
refined by
R.7.1
verified by
Analyze FOD
Trends
Types of Data
Demonstration
Function
Requirement
VerificationRequ...
R.7.1.1
refined by
verified by
Storage of Data
Test
Requirement
VerificationRequ...
refined by
R.7.1.1.1
verified by
Data Retention
Test
Requirement
VerificationRequ...
verified by
Demonstration
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall provide a method of trend analysis.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.7.1 Types of Data
Based upon Operational Objective:
OO-07 Provide FOD trend analysis.
358
R.8.1
refined by
R.8.2
refined by
R.8.3
refined by
verified by
ATC
Communication
Airport
Management C...
Maintainer
Communication
Demonstration
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
Demonstration
Demonstration
Demonstration
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall provide a method of communicating with air traffic control,
airport management, and system maintainers.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.8.1 ATC Communication
R.8.2 Airport Management Communication
R.8.3 Maintainer Communication
Based upon Operational Objective:
OO-09 Provide a method of communicating with external system elements.
359
R.9.1
R.9.1.1
refined by
R.9.1.2
refined by
refined by
R.9.2
refined by
verified by
Maintenance
Procedures
Call Center
Analysis
Requirement
Requirement
VerificationRequ...
R.9.1.3
refined by
R.9.1.4
refined by
verified by
verified by
Cleaning
Procedures
Preventative
Maintenance Pr...
Recalibration Plan
Scheduled
Component Re...
Analysis
Demonstration
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
System users shall be provided with technical support.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.9.1 Maintenance Procedures
R.9.2 Call Center
Based upon Operational Objective:
OO-08 Provide technical support.
360
R.10.1
R.10.1.1
refined by
R.10.1.2
refined by
refined by
verified by
Elements Located
Near The Runway
Inspection
Requirement
VerificationRequ...
R.10.1.3
refined by
R.10.1.4
refined by
verified by
Breakaway
Connector
Element Height
Frangible Coupling
Wind Loading
Inspection
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall conform to applicable airport obstruction criteria, marking and
lighting, and equipment design and installation standards.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.10.1 Elements Located Near the Runway
Based upon Operational Objective:
OO-10 Comply with installation and acceptance standards.
361
R.11.1
refined by
R.11.2
refined by
verified by
System
Availability
System
Maintainability
Analysis
Requirement
Requirement
VerificationRequ...
verified by
R.11.2.1
refined by
R.11.2.2
refined by
verified by
Analysis
System Health
and Fault Notific...
Equipment
Located Outside...
Analysis
VerificationRequ...
Requirement
Requirement
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall provide a high level of reliability, availability and maintainability.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.11.1 System Availability
R.11.2 System Maintainability
Based upon Operational Objective:
OO-11 Provide a reliable, maintainable, and available system.
362
R.12.1
refined by
R.12.2
refined by
R.12.3
refined by
verified by
Performance in
Rain
Performance in
Snow
Performance in
Wind
Test
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
Test
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Requirement Statement:
The system shall be capable of operating in rain, wind and snow.
Refines Higher-Level Requirement:
R Need Statement
Refined By Subordinate Requirements:
R.12.1 Performance in Rain
R.12.2 Performance in Snow
R.12.3 Performance in Wind
Based upon Operational Objective:
OO-12 Facilitate adverse weather operation.
363
R.1.1 Emergency
hier Emergency
R.1.1
Emergency
Requirement
R.1.1.1
refined by
verified by
Execution Speed
Test
Requirement
VerificationRequ...
verified by
Demonstration
VerificationRequ...
Date:
November 7, 2...
364
R.3.1.1
refined by
verified by
Detection Time
Demonstration
Requirement
VerificationRequ...
verified by
Demonstration
VerificationRequ...
Date:
November 7, 2...
365
R.4.1.1
refined by
R.4.1.2
refined by
R.4.1.3
refined by
verified by
Active Reporting
Passive Reporting
Suitability
Reporting
Test
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
Demonstration
Demonstration
Demonstration
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
R.6.2.1
refined by
R.6.2.2
refined by
R.6.2.3
refined by
verified by
FOD Location
Emergency
Posture
Standby Location
Demonstration
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
Demonstration
Demonstration
Demonstration
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
368
R.7.1.1
refined by
verified by
Storage of Data
Test
Requirement
VerificationRequ...
refined by
R.7.1.1.1
verified by
Data Retention
Test
Requirement
VerificationRequ...
Date:
November 7, 2015
369
verified by
Data Retention
Test
Requirement
VerificationRequ...
verified by
Demonstration
VerificationRequ...
Date:
November 7, 2...
370
R.11.2.1
refined by
R.11.2.1.1
refined by
R.11.2.2
refined by
verified by
System Health
and Fault Notific...
Equipment
Located Outside...
Analysis
Requirement
Requirement
VerificationRequ...
refined by
R.11.2.1.2
verified by
verified by
System Health
Test
Demonstration
Requirement
Requirement
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
371
refined by
R.11.2.1.1.2
verified by
Mobile Element
System Health
Stationary
Element System...
Demonstration
Requirement
Requirement
VerificationRequ...
verified by
verified by
Demonstration
Demonstration
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
372
refined by
R.11.2.1.2.2
verified by
Mobile Element
Self-Test
Stationary
Element Self-Test
Demonstration
Requirement
Requirement
VerificationRequ...
refined by
R.11.2.1.2.1.1
verified by
refined by
R.11.2.1.2.2.1
verified by
Mobile Element
Self-Test Duration
Demonstration
Stationary
Element Self-Tes...
Demonstration
Requirement
VerificationRequ...
Requirement
VerificationRequ...
Date:
November 7, 2015
373
verified by
Mobile Element
Self-Test Duration
Demonstration
Requirement
VerificationRequ...
verified by
Test
VerificationRequ...
Date:
November 7, 2...
374
verified by
Stationary
Element Self-Tes...
Demonstration
Requirement
VerificationRequ...
verified by
verified by
Analysis
Demonstration
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
375
376
R.3.2.1
refined by
R.3.2.2
refined by
R.3.2.3
refined by
R.3.2.4
refined by
R.3.2.5
refined by
verified by
Detect FOD
Group Object
Detection
Metal Cylinder
Detection
Sphere Detection
Lighting
Conditions
Automated
Retrieval Suitabil...
Test
Function
Requirement
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
verified by
Test
Test
Test
Test
Test
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
377
381
382
refined by
R.11.2.1.1.1
refined by
R.11.2.1.2
verified by
System Health
Test
Requirement
Requirement
VerificationRequ...
refined by
R.11.2.1.1.2
verified by
refined by
R.11.2.1.2.1
refined by
R.11.2.1.2.2
verified by
Mobile Element
System Health
Stationary
Element System...
Demonstration
Mobile Element
Self-Test
Stationary
Element Self-Test
Demonstration
Requirement
Requirement
VerificationRequ...
Requirement
Requirement
VerificationRequ...
Date:
November 7, 2015
Figure 24. System Health and Fault Notification Requirements Hierarchy Diagram
383
384
386
PROGRAMMATIC REQUIREMENTS
R.9.1.1
refined by
R.9.1.2
refined by
R.9.1.3
refined by
R.9.1.4
refined by
verified by
Cleaning
Procedures
Preventative
Maintenance Pr...
Recalibration Plan
Scheduled
Component Re...
Analysis
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
Analysis
Analysis
Analysis
Analysis
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
387
PROGRAMMATIC REQUIREMENTS
388
PROGRAMMATIC REQUIREMENTS
389
390
R.10.1.1
refined by
R.10.1.2
refined by
R.10.1.3
refined by
R.10.1.4
refined by
verified by
Breakaway
Connector
Element Height
Frangible Coupling
Wind Loading
Inspection
Requirement
Requirement
Requirement
Requirement
VerificationRequ...
verified by
verified by
verified by
verified by
Inspection
Inspection
Inspection
Inspection
VerificationRequ...
VerificationRequ...
VerificationRequ...
VerificationRequ...
Date:
November 7, 2015
Figure 26. Elements Located Near the Runway Requirements Hierarchy Diagram
391
392
393
Section VIII.
Requirements Traceability & Verification Matrix
394
Number
R
Name
Need Statement
Type
Composite
Origin
Originating
Refines
Refined by
Requirement R.1
Safe Operation
Requirement R.2
System Command
and Control
Requirement R.3
FOD Scanning and
Detection
Requirement R.4
FOD Reporting
Requirement R.5
FOD Retrieval
Requirement R.6
Mobile Unit
Locomotion
Requirement R.7
Provide FOD Trend
Analysis
Requirement R.8
System
Communication
Requirement R.9
Technical Support
Requirement R.10
Installation and
Acceptance
Standards
Requirement R.11
Reliability,
Availability and
Maintainability
Requirement R.12
Verified by
Analysis
Demonstration
Inspection
Test
395
Number
Name
Type
Origin
R.1
Safe Operation
Composite
Originating
R.1.1
Emergency
Functional
Derived
R.1.1.1
Execution
Speed
System
Command and
Control
Performance
Derived
Composite
Originating
R.2.1
System
Command
Functional
Design
Decision
R.2.2
Location of
Aircraft
Functional
Derived
R.2.3
Unsuitable FOD
Functional
Derived
R.2.4
Power Failure
Performance
Derived
R.2
Refines
Requirement R
Need Statement
Requirement
R.1 Safe
Operation
Requirement
R.1.1 Emergency
Requirement R
Need Statement
Requirement
R.2 System
Command and
Control
Requirement
R.2 System
Command and
Control
Requirement
R.2 System
Command and
Control
Requirement
R.2 System
Refined by
Operate in Adverse
Weather Conditions
Requirement R.1.1
Emergency
Requirement R.1.1.1
Execution Speed
Verified by
Demonstration
Test
Demonstration
Requirement R.2.1
System Command
Requirement R.2.2
Location of Aircraft
Requirement R.2.3
Unsuitable FOD
Requirement R.2.4
Power Failure
Test
Test
Test
Test
Test
396
Number
Name
Type
Composite
Origin
R.3
FOD Scanning
and Detection
Originating
R.3.1
Derived
R.3.1.1
Detection Time
Performance
Derived
R.3.2
FOD Detection
Performance
Derived
R.3.2.1
Group Object
Detection
Performance
Derived
R.3.2.2
Metal Cylinder
Detection
Performance
Derived
Refines
Command and
Control
Requirement R
Need Statement
Requirement
R.3 FOD
Scanning and
Detection
Requirement
R.3.1 Airfield
Scanning
Requirement
R.3 FOD
Scanning and
Detection
Requirement
R.3.2 FOD
Detection
Requirement
R.3.2 FOD
Detection
Refined by
Verified by
Requirement R.3.1
Airfield Scanning
Requirement R.3.2
FOD Detection
Requirement R.3.1.1
Detection Time
Demonstration
Demonstration
Demonstration
Requirement R.3.2.1
Group Object
Detection
Requirement R.3.2.2
Metal Cylinder
Detection
Requirement R.3.2.3
Sphere Detection
Requirement R.3.2.4
Lighting Conditions
Requirement R.3.2.5
Automated
Retrieval Suitability
Test
Test
Test
397
Number
Name
Type
Origin
Refines
R.3.2.3
Sphere
Detection
Performance
Derived
R.3.2.4
Lighting
Conditions
Performance
Derived
R.3.2.5
Automated
Retrieval
Suitability
FOD Reporting
Functional
Derived
Composite
Originating
R.4.1
FOD Location
Reporting
Functional
Derived
Requirement
R.4 FOD
Reporting
R.4.1.1
Active
Reporting
Performance
Derived
R.4.1.2
Passive
Reporting
Performance
Derived
R.4.1.3
Suitability
Reporting
Performance
Derived
R.5
FOD Retrieval
Composite
Originating
Requirement
R.4.1 FOD
Location
Reporting
Requirement
R.4.1 FOD
Location
Reporting
Requirement
R.4.1 FOD
Location
Reporting
Requirement R
Need Statement
R.4
Requirement
R.3.2 FOD
Detection
Requirement
R.3.2 FOD
Detection
Requirement
R.3.2 FOD
Detection
Requirement R
Need Statement
Refined by
Verified by
Test
Test
Test
Requirement R.4.1
FOD Location
Reporting
Requirement R.4.1.1
Active Reporting
Requirement R.4.1.2
Passive Reporting
Requirement R.4.1.3
Suitability Reporting
Demonstration
Test
Demonstration
Demonstration
Demonstration
Requirement R.5.1
FOD Weight
Demonstration
398
Number
Name
Type
Origin
R.5.1
FOD Weight
Determination
Functional
Design
Decision
R.5.2
FOD Weight
Performance
Derived
R.5.3
FOD location
Functional
Derived
R.5.4
FOD Dimensions
Performance
Derived
R.6
Mobile Unit
Locomotion
Composite
Originating
Refines
Requirement
R.5 FOD
Retrieval
Requirement
R.5 FOD
Retrieval
Requirement
R.5 FOD
Retrieval
Requirement
R.5 FOD
Retrieval
Requirement R
Need Statement
Refined by
Determination
Requirement R.5.2
FOD Weight
Requirement R.5.3
FOD location
Requirement R.5.4
FOD Dimensions
Verified by
Test
Test
Test
Test
Requirement R.6.1
Mobile Unit Speed
Requirement R.6.2
Mobile Unit
Navigation
Requirement R.6.3
Mobile Unit
Movement
Clearance
Requirement R.6.4
Separation from
Obstacles
Requirement R.6.5
Separation from
Test
399
Number
Name
Type
Origin
R.6.1
Mobile Unit
Speed
Constraint
Derived
R.6.2
Mobile Unit
Navigation
Functional
Derived
R.6.2.1
FOD Location
Functional
Derived
R.6.2.2
Emergency
Posture
Functional
Derived
R.6.2.3
Standby
Location
Functional
Derived
R.6.3
Mobile Unit
Movement
Clearance
Separation from
Obstacles
Functional
Design
Decision
Performance
Derived
R.6.4
Refines
Requirement
R.6 Mobile Unit
Locomotion
Requirement
R.6 Mobile Unit
Locomotion
Requirement
R.6.2 Mobile Unit
Navigation
Requirement
R.6.2 Mobile Unit
Navigation
Requirement
R.6.2 Mobile Unit
Navigation
Requirement
R.6 Mobile Unit
Locomotion
Requirement
R.6 Mobile Unit
Locomotion
Refined by
Aircraft
Requirement R.6.6
Separation from
Personnel
Requirement R.6.7
Separation from
Vehicles
Requirement R.6.2.1
FOD Location
Requirement R.6.2.2
Emergency Posture
Requirement R.6.2.3
Standby Location
Verified by
Demonstration
Demonstration
Demonstration
Demonstration
Demonstration
Demonstration
Test
400
Number
Name
Type
Origin
R.6.5
Separation from
Aircraft
Performance
Derived
R.6.6
Separation from
Personnel
Performance
Derived
R.6.7
Separation from
Vehicles
Performance
Derived
R.7
Composite
Originating
R.7.1
Provide FOD
Trend Analysis
Types of Data
Functional
Derived
R.7.1.1
Storage of Data
Functional
Derived
R.7.1.1.1
Data Retention
Constraint
Derived
R.8
System
Communication
Composite
Originating
Refines
Requirement
R.6 Mobile Unit
Locomotion
Requirement
R.6 Mobile Unit
Locomotion
Requirement
R.6 Mobile Unit
Locomotion
Requirement R
Need Statement
Requirement
R.7 Provide FOD
Trend Analysis
Requirement
R.7.1 Types of
Data
Requirement
R.7.1.1 Storage
of Data
Requirement R
Need Statement
Refined by
Verified by
Test
Test
Test
Requirement R.7.1
Types of Data
Requirement R.7.1.1
Storage of Data
Demonstration
Requirement
R.7.1.1.1 Data
Retention
Test
Requirement R.8.1
ATC
Communication
Requirement R.8.2
Airport
Management
Communication
Requirement R.8.3
Maintainer
Communication
Demonstration
Test
Demonstration
401
Number
Name
Type
Origin
Refines
R.8.1
ATC
Communication
Performance
Derived
R.8.2
Airport
Management
Communication
Maintainer
Communication
Performance
Derived
Performance
Derived
R.9
Technical
Support
Composite
Originating
R.9.1
Maintenance
Procedures
Programmatic Derived
Requirement
R.9 Technical
Support
R.9.1.1
Cleaning
Procedures
Programmatic Derived
Requirement
R.9.1
Maintenance
Procedures
R.8.3
Requirement
R.8 System
Communication
Requirement
R.8 System
Communication
Requirement
R.8 System
Communication
Requirement R
Need Statement
Refined by
Verified by
Demonstration
Demonstration
Demonstration
Requirement R.9.1
Maintenance
Procedures
Requirement R.9.2
Call Center
Requirement R.9.1.1
Cleaning
Procedures
Requirement R.9.1.2
Preventative
Maintenance
Procedures
Requirement R.9.1.3
Recalibration Plan
Requirement R.9.1.4
Scheduled
Component
Removals
Analysis
Analysis
Analysis
402
Number
Name
Type
Origin
Refines
R.9.1.2
Preventative
Maintenance
Procedures
Programmatic Derived
R.9.1.3
Recalibration
Plan
Programmatic Derived
R.9.1.4
Scheduled
Component
Removals
Programmatic Derived
R.9.2
Call Center
Programmatic Derived
R.10
Installation and
Acceptance
Standards
Elements
Located Near
The Runway
Composite
Originating
Constraint
Derived
Requirement
R.10 Installation
and
Acceptance
Standards
Breakaway
Connector
Constraint
Derived
Requirement
R.10.1 Elements
Located Near
The Runway
R.10.1
R.10.1.1
Requirement
R.9.1
Maintenance
Procedures
Requirement
R.9.1
Maintenance
Procedures
Requirement
R.9.1
Maintenance
Procedures
Requirement
R.9 Technical
Support
Requirement R
Need Statement
Refined by
Verified by
Analysis
Analysis
Analysis
Demonstration
Requirement R.10.1
Elements Located
Near The Runway
Requirement
R.10.1.1 Breakaway
Connector
Requirement
R.10.1.2 Element
Height Requirement
R.10.1.3 Frangible
Coupling
Requirement
R.10.1.4 Wind
Loading
Inspection
Inspection
Inspection
403
Number
Name
Type
Origin
R.10.1.2
Element Height
Constraint
Derived
R.10.1.3
Frangible
Coupling
Constraint
Derived
R.10.1.4
Wind Loading
Constraint
Derived
R.11
Reliability,
Availability and
Maintainability
Composite
Originating
R.11.1
System
Availability
Performance
Derived
R.11.2
System
Maintainability
Functional
Derived
R.11.2.1
System Health
and Fault
Notification
Performance
Derived
Refines
Requirement
R.10.1 Elements
Located Near
The Runway
Requirement
R.10.1 Elements
Located Near
The Runway
Requirement
R.10.1 Elements
Located Near
The Runway
Requirement R
Need Statement
Requirement
R.11 Reliability,
Availability and
Maintainability
Requirement
R.11 Reliability,
Availability and
Maintainability
Requirement
R.11.2 System
Maintainability
Refined by
Verified by
Inspection
Inspection
Inspection
Requirement R.11.1
System Availability
Requirement R.11.2
System
Maintainability
Analysis
Requirement
R.11.2.1 System
Health and Fault
Notification
Requirement
R.11.2.2 Equipment
Located Outside of
Paved Surfaces
Requirement
R.11.2.1.1 System
Health Requirement
Analysis
Analysis
Test
404
Number
Name
Type
Origin
Refines
R.11.2.1.1
System Health
Functional
Derived
Requirement
R.11.2.1 System
Health and Fault
Notification
R.11.2.1.1.1
Mobile Element
System Health
Performance
Derived
R.11.2.1.1.2
Stationary
Element System
Health
Self-Test & Fault
Notification
Performance
Derived
Functional
Derived
Requirement
R.11.2.1.1 System
Health
Requirement
R.11.2.1.1 System
Health
Requirement
R.11.2.1 System
Health and Fault
Notification
Mobile Element
Self-Test
Functional
Derived
Performance
Derived
R.11.2.1.2.2
Functional
Derived
R.11.2.1.2
R.11.2.1.2.1
Stationary
Element Self-Test
Requirement
R.11.2.1.2 SelfTest & Fault
Notification
Requirement
R.11.2.1.2.1
Mobile Element
Self-Test
Requirement
R.11.2.1.2 Self-
Refined by
R.11.2.1.2 Self-Test &
Fault Notification
Requirement
R.11.2.1.1.1 Mobile
Element System
Health Requirement
R.11.2.1.1.2
Stationary Element
System Health
Verified by
Demonstration
Demonstration
Demonstration
Requirement
R.11.2.1.2.1 Mobile
Element Self-Test
Requirement
R.11.2.1.2.2
Stationary Element
Self-Test
Requirement
R.11.2.1.2.1.1 Mobile
Element Self-Test
Duration
Demonstration
Requirement
R.11.2.1.2.2.1
Stationary Element
Demonstration
Demonstration
Test
405
Number
Name
Type
Origin
Refined by
Self-Test
Performance
Requirement R.12.1
Performance in Rain
Requirement R.12.2
Performance in
Snow Requirement
R.12.3 Performance
in Wind
R.11.2.1.2.2.1 Stationary
Element Self-Test
Performance
Performance
R.11.2.2
Equipment
Located
Outside of
Paved Surfaces
Operate in
Adverse
Weather
Conditions
Programmatic Derived
Composite
Originating
Requirement R
Need Statement
R.12.1
Performance in
Rain
Performance
Derived
R.12.2
Performance in
Snow
Performance
Derived
R.12.3
Performance in
Wind
Performance
Derived
Requirement
R.12 Operate in
Adverse
Weather
Conditions
Requirement
R.12 Operate in
Adverse
Weather
Conditions
Requirement
R.12 Operate in
Adverse
Weather
Conditions
R.12
Derived
Refines
Verified by
Analysis
Demonstration
Demonstration
Test
Test
Test
Test
406
407
References
FAA. (2009, September 30). Advisory Circular150/5220-24 Airport Foreign Object Debris
(FOD) Detection Equipment. Retrieved
from: http://www.faa.gov/documentLibrary/media/Advisory_Circular/150_5220_
24.pdf
FAA. (2010, September 30). Advisory Circular 150/5210-24 Airport Foreign Object Debris.
Retrieved
from: http://www.faa.gov/documentLibrary/media/Advisory_Circular/150_5210_
24.pdf
Kossiakoff, A., Sweet, W. N., Seymour, S. J., & Biemer, S. M. (2011). Sysytems Engineering
Principles and Practice (2nd edition). Hoboken: John Wiley & Sons.
408
Appendix C
409
Table of Contents
Systems Engineering 411
Updated Context Diagram 412
AFDIRTS Function Tree.. 413
Functional Tractability Matrix 414
AFDIRTS Requirement/Functional Map. 418
AFDIRTS Functional Architecture. 419
410
Systems Engineering
The Systems Engineering Method as described by Kossiakoff et al. (2011) is being utilized
to assist in completion of the SM4 project. At this point, user needs have been identified,
operational objectives have been defined, and operational and performance
requirements have been developed that would satisfy operational objectives. These
requirements were documented in the Requirements Analysis Report (RAR).
The Functional Analysis Report (FAR) documents the results of both the Performance
Requirements Analysis and Functional Analysis and Formulation steps of Concept
Definition phase. At this point, performance requirements have been analyzed and
refined while functions have been allocated to the component level. Even though
some functions have been allocated to the component level, the preliminary
functional architecture listed in this report has been designed to facilitate a wide-range
of physical solutions. In the RAR (Concept Exploration), three competing CONOPS were
explored, as system development continues and a concept is selected; both the
functional architecture and requirements document will be refined to reflect the
progress made through Concept Definition. These requirements will ultimately be
documented in the A-Spec.
411
Air Traffic
Control
Environment
Rain (M)
Wind (F)
Snow (M)
Location Data (D)
Heat (E)
Sound (E)
Resistance (E)
Obstacles
Airport
Managers
AFDIRTS
Aircraft
Operators
Forces (F)
Energy (E)
Data (D)
Signals (S)
Materials (M)
Parts (M)
Materials (M)
Fault Codes (D)
System Health (D)
Power
Parts (M)
Materials (M)
SW Update (S)
Maintenance Commands (D)
FOD
Maintainer
Figure 1. Updated AFDIRTS Context Diagram
412
413
Number Name
Based on
R Need Statement
F.1.1
Perform AFDIRTS
Functions
Command and Control
System
Interface with ATC
F.1.2
F.1.3
F.1.9
Transmit Normal
Operation Command
Transmit Emergency
Command
Determine Location,
Trajectory and Speed
of Inbound Aircraft.
Transmit Inbound
Aircraft Data to System
Elements
Interface with Airport
Managers
Interface with
Maintenance Personnel
Initiate Self-Test
Display Maintenance
Data
Restore System
F.2
Operate Safely
F.2.1
F.2.2
F.1
F.1.4
F.1.5
F.1.6
F.1.7
F.1.8
F.1.8.1
F.1.8.2
F.2.3
F.2.4
R.9.2
R.9.3
414
Number Name
Based on
F.2.5
F.3
Provide Airport
Managers with System
Health Data
Provide ATC with
System Health Data
Provide Maintenance
Personnel with System
Health Data
Scan Airfield for FOD
F.3.1
Detect FOD
F.3.2
Determine FOD
Suitability from a
Distance
Determine Location of
FOD
Process Suitability and
Location of FOD
Retrieve FOD
F.2.6
F.2.7
F.3.3
F.3.4
F.4
F.4.1
F.4.2
F.4.3
F.4.4
F.4.5
Determine FOD
Dimensions
Notify Personnel of
Object too Large for
Retrieval
Grasp FOD
F.4.7
F.5
Navigate Airfield
F.5.1
Process Navigation
Commands
F.4.6
415
Number Name
Based on
F.5.2
R.1.1 Emergency
R.1.1.1 Execution
Speed
R.7.2 Emergency Posture
F.5.3
F.5.4
F.5.5
F.5.6
F.5.7
F.5.8
Navigate to
Emergency Standby
Location
Navigate to FOD
Location
Navigate to Disposal
Area
Detect Obstacles
Receive Aircraft
Trajectory Data
Anticipate Obstacle
Movement
Avoid Obstacles
F.5.9
Determine Location
F.5.10
Control Motion
F.6
F.6.2.2
F.6.2.3
F.7
F.7.1
F.7.2
F.7.3
F.7.4
F.7.5
F.8
Locomote System
Elements
Facilitate Power
Facilitate Movement
Facilitate Directional
Control
Facilitate Motion
Facilitate Braking
Maintain System
Accept Parts
Accept Materials
Accept SW Updates
Eject Materials
Eject Parts
Provide Power
F.8.1
F.8.2
F.6.1
F.6.2
F.6.2.1
R.7.1.4
416
Number Name
Based on
F.8.3
Generate Emergency
Power
Transfer Power
F.8.4
F.9
F.9.1
F.9.2
F.9.3
F.9.4
417
418
F. AFDIRTS System
n2 Perform AFDIRTS Functions
(Ext) Aircraft
Radar Data ...
(Ext) ATC ...
(Ext) Maint...
(Ext) FOD
Identification
from FOD
(Ext) FOD L...
(Ext) FOD
Identificatio...
(Ext) FOD L...
At FOD Loca...
(Ext) Aircraf...
(Ext) Obsta...
(Ext) Obsta...
Location Da...
(Ext)
Materials fr...
(Ext) Parts ...
(Ext) SW U...
(Ext)
Electrical
Energy from
Power
At FOD
Location
Signal (S)
F.1
System Context
System
Health (D)
Emergency...
Fault Codes...
System Hea...
System Hea...
Inbound
Aircraft Data
from Comm...
Navigation ...
Command and
Control System
F.2
Operate Safely
System Context
Unsuitable
FOD Location
Data
F.3
Scan Airfield for
FOD
System Context
FOD Location
Data to
Mobile Units
FOD
Characteristic
s (D)
Suitablity D...
FOD Charac...
Fod Illumina...
Suitablity D...
Unsuitable ...
Navigation
Modes (D)
FOD too
Large (S)
FOD too
Large (S)
Unsuitable
FOD Locatio...
FOD
Coordinates
Aircraft
Illumination ...
FOD Coordi...
Obstacle Ill...
F.4
Unsuitable
FOD (D)
Unsuitable
FOD Locatio...
Retrieve FOD
System Context
F.5
Navigate Airfield
System Context
Movement
Command to
Locomote
System Ele...
F.6
Heat to
Environment
Resistance t...
Sound to En...
Locomote System
Elements
System Context
F.7
Materials to
Maintainer
Parts to
Maintainer
Maintain System
System Context
Power Failure
Signal from
Power (S)
transferred...
transferred
Power (E)
transferred
Power (E)
transferred
Power (E)
transferred
Power (E)
transferred
Power (E)
transferred
Power (E)
F.8
transferred
Power (E)
Provide Power
System Context
F.9
Analyze FOD
Trends
Reports to
Airport
Managers (E)
System Context
Date:
419
(Ext) ATC
Command
from ATC
System Hea...
Emergency
Operation
Command (S)
System
Health (D)
Unsuitable
FOD Locatio...
(Ext) Aircraft
Radar Data
from ATC
(Ext)
Maintenance
Commands ...
System Hea...
Power Failure
Signal from
Power (S)
F.1.1
Interface with
ATC
System Context
System
Health to
ATC (E)
Command
Signal (S)
F.1.2
Initiate System
Modes
System Context
Normal
Operation
Command (S)
Emergency
Operation
Command (S)
F.1.3
Transmit Normal
Operation
Command
System Context
Navigation
Modes (D)
F.1.4
Transmit
Emergency
Command
System Context
Navigation
Modes (D)
F.1.5
Determine
Location,
Trajectory and
Speed of Inbou...
System Context
Aircraft
Location (D)
F.1.6
Inbound
Aircraft Data
from
Command a...
Transmit Inbound
Aircraft Data to
System Elements
System Context
F.1.7
System
Health to
Airport Man...
Unsuitable ...
Interface with
Airport Managers
System Context
F.1.8
System
Health Data
to Maintainer
(E)
Interface with
Maintenance
Personnel
System Context
System
Resume
Signal (S)
System
Resume
Signal (S)
System
Resume
Signal (S)
System
Resume
Signal (S)
System
Resume
Signal (S)
F.1.9
Restore System
System Context
Date:
420
Transmit Normal
Operation Command
(Ext) ATC
Command from
ATC
F.1.1
Command
Signal (S)
Interface with ATC
F.1.2
System Context
Initiate System Modes
OR
OR
F.1.4
(Ext) Aircraft
Radar Data from
ATC
F.1.5
System Context
System Context
System Context
F.1.6
Determine Location,
Trajectory and Speed of
Inbound Aircraft.
System Context
System Context
AND
AND
Unsuitable FOD
Location Data
F.1.7
System Health Data to
Maintainer (E)
(Ext) Maintenance
Commands from
Maintainer
System Context
F.1.8
Interface with
Maintenance Personnel
System Context
Ref.
OR
OR
Ref.
F.1.9
Restore System
System Context
Power Failure Signal
from Power (S)
System Resume
Signal (S)
Date:
421
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.1 Interface with ATC
Output From:
(External) ATC IOs
Input To:
F.1.2 Initiate System Modes
Output From:
F.1.1 Interface with ATC
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.1 Interface with ATC
422
Interfacing Items
Command Signal (S)
Source / Destination
Input To:
F.1.2 Initiate System Modes
Output From:
F.1.1 Interface with ATC
Input To:
F.1.4 Transmit Emergency Command
Output From:
F.1 Command and Control System
F.1.2 Initiate System Modes
Input To:
F.1.3 Transmit Normal Operation
Command
Output From:
F.1.2 Initiate System Modes
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
423
Interfacing Items
Navigation Modes (D)
Source / Destination
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Input To:
F.1.3 Transmit Normal Operation
Command
Output From:
F.1.2 Initiate System Modes
424
Interfacing Items
Emergency Operation Command (S)
Source / Destination
Input To:
F.1.4 Transmit Emergency Command
Output From:
F.1 Command and Control System
F.1.2 Initiate System Modes
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Interfacing Items
(Ext) Aircraft Radar Data from ATC
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
Output From:
(External) Aircraft Operators IOs
Input To:
F.1.6 Transmit Inbound Aircraft Data to
425
System Elements
Output From:
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
System Resume Signal (S)
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
Interfacing Items
Aircraft Location (D)
Source / Destination
Input To:
F.1.6 Transmit Inbound Aircraft Data to
System Elements
Output From:
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
Input To:
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Output From:
F.1 Command and Control System
F.1.6 Transmit Inbound Aircraft Data to
System Elements
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
426
Table 7. F.1.6 Transmit Inbound Aircraft Data to System Elements Interfacing Items
Interfacing Items
Source / Destination
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
Interfacing Items
System Health (D)
Source / Destination
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
427
Interfacing Items
Source / Destination
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
Interfacing Items
(Ext) Maintenance Commands from
Maintainer
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.8 Interface with Maintenance
428
Interfacing Items
Source / Destination
Personnel
F.1.8.1 Initiate Self-Test
Output From:
(External) Maintainer IOs
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
429
F.1.8.1
F.1.8.2
Display Maintenance
Data
Initiate Self-Test
Ref.
System Health
Data to Maintainer
(E)
System
Health (D)
Ref.
System Context
System Context
Date:
(Ext)
Maintenance
Commands
from Mainta...
System
Health (D)
F.1.8.1
Initiate Self-Test
System Context
Fault Codes
(D)
F.1.8.2
Display
Maintenance Data
System Context
Fault Codes
to Maintainer
System
Health Data...
Date:
November 17, 2015
Interfacing Items
(Ext) Maintenance Commands from
Maintainer
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
430
Interfacing Items
Source / Destination
F.1.8 Interface with Maintenance
Personnel
F.1.8.1 Initiate Self-Test
Output From:
(External) Maintainer IOs
Input To:
F.1.8.2 Display Maintenance Data
Output From:
F.1.8.1 Initiate Self-Test
Interfacing Items
Fault Codes (D)
Source / Destination
Input To:
F.1.8.2 Display Maintenance Data
Output From:
F.1.8.1 Initiate Self-Test
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.8.2 Display Maintenance Data
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
431
Interfacing Items
Source / Destination
with System Health Data
Output From:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Interfacing Items
Power Failure Signal from Power (S)
Source / Destination
Input To:
F.1 Command and Control System
F.1.9 Restore System
Output From:
F.8 Provide Power
F.8.2 Detect External Power Failure
Input To:
F.1.2 Initiate System Modes
F.1.5 Determine Location, Trajectory and
Speed of Inbound Aircraft.
F.1.6 Transmit Inbound Aircraft Data to
System Elements
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
Output From:
F.1.9 Restore System
432
Source / Destination
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
433
F.2.5
Fault Data (D)
F.2.2
System
Initialization
Ref.
System Context
AND
Critical
Subsystem
Degraded Signal
F.2.3
AND
OR
F.2.4
OR
Ref.
System Context
System Context
Monitor the Health of
Mobile Element
Critical Subsystems
Compensate for
Failures in Mobile Unit
Critical Subsystems
System Context
System Context
F.2.7
Provide Maintenance
Personnel with System
Health Data
System Context
Critical Subsystem
Telemetry Data From
Mobile Elements
Self-Test Results
(D)
Date:
434
n2 Operate Safely
System
Initialization
Critical
Subsystem
Telemetry
Data from S...
Critical
Subsystem
Telemetry
Data From ...
F.2.1
Perform Self Test
Upon Initialization
System Context
F.2.2
Monitor the
Health of
Stationary
Element Critical ...
System Context
F.2.3
Monitor the
Health of Mobile
Element Critical
Subsystems
System Context
Self-Test
Results (D)
Self-Test
Results (D)
Self-Test
Results (D)
Critical
Subsystem
Degraded
Signal
F.2.4
Compensate for
Failures in Mobile
Unit Critical
Subsystems
System Context
F.2.5
Provide Airport
Managers with
System Health
Data
System Context
System
Health (D)
F.2.6
Provide ATC with
System Health
Data
System Context
Date:
System
Health (D)
F.2.7
Provide
Maintenance
Personnel with
System Health ...
System Context
System
Health (D)
435
Interfacing Items
Self-Test Results (D)
Source / Destination
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.1 Perform Self-Test Upon Initialization
System Initialization
Input To:
F.2.1 Perform Self-Test Upon Initialization
Interfacing Items
Source / Destination
Input To:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.2 Monitor the Health of Stationary
436
Table 15. F.2.2 Monitor the Health of Stationary Element Critical Subsystems Interfacing Items
Interfacing Items
Source / Destination
Element Critical Subsystems
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Interfacing Items
Critical Subsystem Degraded Signal
Source / Destination
Input To:
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Output From:
F.2.3 Monitor the Health of Mobile
Element Critical Subsystems
Input To:
F.2.3 Monitor the Health of Mobile
Element Critical Subsystems
Interfacing Items
Critical Subsystem Degraded Signal
Source / Destination
Input To:
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Output From:
F.2.3 Monitor the Health of Mobile
Element Critical Subsystems
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
437
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Source / Destination
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.1 Perform Self-Test Upon Initialization
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
438
Table 18. F.2.5 Provide Airport Managers with System Health Data Interfacing Items
Interfacing Items
Source / Destination
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Interfacing Items
Fault Data (D)
Source / Destination
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
439
Table 19. F.2.6 Provide ATC with System Health Data Interfacing Items
Interfacing Items
Source / Destination
F.2.1 Perform Self-Test Upon Initialization
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Interfacing Items
Fault Data (D)
Source / Destination
Input To:
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.2 Monitor the Health of Stationary
Element Critical Subsystems
F.2.4 Compensate for Failures in Mobile
Unit Critical Subsystems
Input To:
F.2.5 Provide Airport Managers with
System Health Data
440
Table 20. F.2.7 Provide Maintenance Personnel with System Health Data Interfacing Items
Interfacing Items
Source / Destination
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
Output From:
F.2.1 Perform Self-Test Upon Initialization
Input To:
F.1 Command and Control System
F.1.1 Interface with ATC
F.1.7 Interface with Airport Managers
F.1.8 Interface with Maintenance
Personnel
F.1.8.2 Display Maintenance Data
Output From:
F.2 Operate Safely
F.2.5 Provide Airport Managers with
System Health Data
F.2.6 Provide ATC with System Health
Data
F.2.7 Provide Maintenance Personnel
with System Health Data
441
Interfacing Items
(Ext) FOD Identification from FOD
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Output From:
(External) FOD IOs
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.3 Grasp FOD
Output From:
(External) FOD IOs
Input To:
F.3.2 Determine FOD Suitability from a
Distance
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
Input To:
(External) FOD IOs
Output From:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
442
Interfacing Items
Source / Destination
F.3.3 Determine Location of FOD
Input To:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
Input To:
F.3.4 Process Suitability and Location of
FOD
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.2 Determine FOD Suitability from a
Distance
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
443
Interfacing Items
Source / Destination
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
444
FOD
Characteristics (D)
(Ext) FOD
Identification
from FOD
F.3.1
Determine FOD
Suitability from a
Distance
Detect FOD
System Context
Ref.
Unsuitable FOD
Location Data
F.3.2
F.3.4
System Context
AND
AND
F.3.3
Process Suitability
and Location of FOD
Ref.
System Context
Determine Location of
FOD
System Context
Fod Illumination to
FOD
Date:
445
(Ext) FOD
Identification
from FOD
FOD
Characteristic
s (D)
(Ext) FOD
Location from
FOD
Suitablity
Data (D)
F.3.1
Detect FOD
System Context
FOD
Characteristic
s (D)
FOD
Characteristic
s (D)
F.3.2
Determine FOD
Suitability from a
Distance
System Context
Suitablity
Data (D)
Suitablity
Data (D)
FOD Location
(D)
Fod
Illumination
to FOD
F.3.3
Determine
Location of FOD
System Context
F.3.4
Process
Suitability and
Location of FOD
System Context
Date:
FOD Location
Data to
Mobile Units
Unsuitable ...
Interfacing Items
(Ext) FOD Identification from FOD
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Output From:
(External) FOD IOs
446
Interfacing Items
FOD Characteristics (D)
Source / Destination
Input To:
F.3.2 Determine FOD Suitability from a
Distance
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
Interfacing Items
FOD Characteristics (D)
Source / Destination
Input To:
F.3.2 Determine FOD Suitability from a
Distance
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
Input To:
F.3.4 Process Suitability and Location of
FOD
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.2 Determine FOD Suitability from a
Distance
447
Interfacing Items
(Ext) FOD Location from FOD
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.3 Grasp FOD
Output From:
(External) FOD IOs
Input To:
(External) FOD IOs
Output From:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
Input To:
F.3.4 Process Suitability and Location of
FOD
Output From:
F.3.3 Determine Location of FOD
Interfacing Items
FOD Location (D)
Source / Destination
Input To:
F.3.4 Process Suitability and Location of
448
Table 25. F.3.4 Process Suitability and Location of FOD Interfacing Items
Interfacing Items
Source / Destination
FOD
Output From:
F.3.3 Determine Location of FOD
Input To:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
Input To:
F.3.4 Process Suitability and Location of
FOD
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.2 Determine FOD Suitability from a
Distance
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
449
Interfacing Items
(Ext) FOD Identification from FOD
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Output From:
(External) FOD IOs
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.3 Grasp FOD
Output From:
(External) FOD IOs
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
Input To:
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.9 Analyze FOD Trends
450
Interfacing Items
Source / Destination
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
Input To:
F.1 Command and Control System
Output From:
F.4 Retrieve FOD
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
451
Interfacing Items
Source / Destination
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
452
Unsuitable FOD
Location Data
At FOD Location
Signal (S)
Ref.
Determine FOD
Dimensions
System Context
System Context
OR
OR
(Ext) FOD Location
from FOD
Notify Personnel of
Overweight Objects
F.4.4
F.4.3
(Ext) FOD
Identification from
FOD
Determine FOD
weight
Grasp FOD
System Context
System Context
FOD (M)
Grasped
FOD (F)
Ref.
F.4.5
Overweight
Signal
Navigation Modes
(D)
System Context
OR
OR
F.4.6
F.4.7
Transport FOD to
Disposal Area
Suitable for
Transport Signal
Release FOD
System Context
System Context
Date:
453
n2 Retrieve FOD
(Ext) FOD
Identificatio...
At FOD Loca...
FOD (M)
(Ext) FOD
Location from
FOD
FOD too La...
(Ext) FOD
Location from
FOD
FOD too
Large (S)
FOD (M)
At Disposal
Area Signal
F.4.1
Determine FOD
Dimensions
System Context
F.4.2
Notify Personnel
of Object too
Large for
Retrieval
System Context
FOD (M)
FOD too
Large (S)
Unsuitable
FOD Location
Data
F.4.3
Grasped FOD
(F)
Grasp FOD
System Context
F.4.4
Determine FOD
weight
System Context
Suitable for
Transport
Signal
Overweight
Signal
F.4.5
Notify Personnel
of Overweight
Objects
System Context
Unsuitable
FOD Location
Data
F.4.6
Transport FOD to
Disposal Area
System Context
Navigation
Modes (D)
F.4.7
Release FOD
System Context
Date:
Interfacing Items
(Ext) FOD Identification from FOD
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
454
Interfacing Items
Source / Destination
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Output From:
(External) FOD IOs
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
FOD (M)
Input To:
F.4.1 Determine FOD Dimensions
F.4.3 Grasp FOD
Output From:
F.4.1 Determine FOD Dimensions
Input To:
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
455
Interfacing Items
(Ext) FOD Location from FOD
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.3 Grasp FOD
Output From:
(External) FOD IOs
Input To:
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
456
Interfacing Items
(Ext) FOD Location from FOD
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.3 Scan Airfield for FOD
F.3.3 Determine Location of FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.3 Grasp FOD
Output From:
(External) FOD IOs
FOD (M)
Input To:
F.4.1 Determine FOD Dimensions
F.4.3 Grasp FOD
Output From:
F.4.1 Determine FOD Dimensions
Input To:
F.4.4 Determine FOD weight
Output From:
F.4.3 Grasp FOD
457
Interfacing Items
Source / Destination
Input To:
F.4.4 Determine FOD weight
Output From:
F.4.3 Grasp FOD
Overweight Signal
Input To:
F.4.5 Notify Personnel of Overweight
Objects
Output From:
F.4.4 Determine FOD weight
Input To:
F.4.6 Transport FOD to Disposal Area
Output From:
F.4.4 Determine FOD weight
F.4.6
Grasped
FOD (F)
Grasp FOD
Transport FOD to
Disposal Area
F.4.4
System Context
OR
Determine FOD
weight
System Context
OR
System Context
Ref.
Suitable for
Transport ...
Ref.
Overweight
Signal
Date:
458
Grasped FOD
(F)
F.4.4
Determine FOD
weight
System Context
Overweight
Signal
Suitable for
Transport S...
Date:
November ...
Interfacing Items
Overweight Signal
Source / Destination
Input To:
F.4.5 Notify Personnel of Overweight
Objects
Output From:
F.4.4 Determine FOD weight
Input To:
F Perform AFDIRTS Functions
F.1 Command and Control System
F.1.7 Interface with Airport Managers
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
F.4 Retrieve FOD
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.4.5 Notify Personnel of Overweight
Objects
459
Interfacing Items
Navigation Modes (D)
Source / Destination
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Input To:
F.4.6 Transport FOD to Disposal Area
Output From:
F.4.4 Determine FOD weight
Interfacing Items
At Disposal Area Signal
Source / Destination
Input To:
F.4.7 Release FOD
F.5.10 Control Motion
Output From:
F.5.4 Navigate to Disposal Area
Interfacing Items
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
Output From:
(External) Obstacles IOs
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
Output From:
(External) Obstacles IOs
Output From:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
FOD Coordinates
Input To:
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Input To:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
Input To:
461
Interfacing Items
and Control (D)
Source / Destination
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Output From:
F.1 Command and Control System
F.1.6 Transmit Inbound Aircraft Data to
System Elements
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.9 Determine Location
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Input To:
(External) Obstacles IOs
Output From:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
Input To:
F.1 Command and Control System
F.2 Operate Safely
462
Interfacing Items
Source / Destination
F.3
F.4
F.5
F.6
F.7
F.9
Output From:
F.8 Provide Power
F.8.4 Transfer Power
463
Navigate to Emergency
Standby Location
Standby
Emergency
Location
Coordinates
At Emergency
Location Signal
At Disposal Area
Signal
System Context
F.5.1
At FOD Location
Signal (S)
Obstacle Illumination
to Obstacle
F.5.3
FOD Coordinates
Process Navigation
Commands
(Ext) Obstacle
Location from
Obstacle
OR
OR
System Context
System Context
Movement Command
to Locomote System
Elements
F.5.4
Navigation
Commands
(Ext) Obstacle
Identification from
Obstacle
Disposal Area
Coordinates
System Context
Obstacle Path
F.5.5
F.5.7
Detect Obstacles
System Context
Ref.
AND
AND
AND
F.5.6
(Ext) Aircraft
Location from
Aircraft (E)
Inbound Aircraft
Data from
Command and
Control (D)
Anticipate Obstacle
Movement
Avoid Obstacles
Control Motion
AND
System Context
Obstacle
Trajectory
System Context
Obstacle
Characteristics
F.5.9
Determine Location
Ref.
System Context
System Context
Receive Aircraft
Trajectory Data
F.5.10
F.5.8
Aircraft Illumination to
Aircraft
Coordinates (D)
System Context
Date:
464
n2 Navigate Airfield
(Ext) Aircraft
Location from
Aircraft (E)
Inbound Air...
(Ext)
Obstacle
Identificatio...
(Ext) Obsta...
FOD Location
Data to
Mobile Units
Navigation
Modes (D)
Location
Data from
Environment
FOD
Coordinates
F.5.1
Process
Navigation
Commands
System Context
Navigation
Commands
Navigation
Commands
Navigation
Commands
F.5.2
At
Emergency
Location Si...
Standby Em...
Navigate to
Emergency
Standby Location
System Context
F.5.3
Navigate to FOD
Location
System Context
System Context
At Disposal
Area Signal
Disposal Area
Coordinates
At Disposal
Area Signal
F.5.5
Detect Obstacles
System Context
Obstacle
Characteristic
s
Obstacle
Illumination
to Obstacle
Obstacle
Characteristic
s
Aircraft
Illumination
to Aircraft
F.5.6
Receive Aircraft
Trajectory Data
System Context
F.5.7
Anticipate
Obstacle
Movement
System Context
Obstacle
Trajectory
F.5.8
Avoid Obstacles
System Context
Coordinates
(D)
At FOD
Location
Signal (S)
FOD Coordi...
F.5.4
Navigate to
Disposal Area
Coordinates
(D)
At FOD
Location
Signal (S)
FOD Coordi...
Coordinates
(D)
Coordinates
(D)
Obstacle Path
F.5.9
Determine
Location
Coordinates
(D)
System Context
F.5.10
Control Motion
System Context
Date:
Movement
Command to
Locomote
System Ele...
Interfacing Items
Navigation Commands
Source / Destination
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
465
Interfacing Items
Source / Destination
Output From:
F.5.1 Process Navigation Commands
Input To:
F.5 Navigate Airfield
F.5.1 Process Navigation Commands
Output From:
F.1 Command and Control System
F.1.3 Transmit Normal Operation
Command
F.1.4 Transmit Emergency Command
F.4 Retrieve FOD
F.4.6 Transport FOD to Disposal Area
Interfacing Items
At Emergency Location Signal
Source / Destination
Input To:
F.5.10 Control Motion
Output From:
F.5.2 Navigate to Emergency Standby
Location
Coordinates (D)
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
Navigation Commands
Input To:
F.5.2 Navigate to Emergency Standby
466
Interfacing Items
Source / Destination
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
Output From:
F.5.1 Process Navigation Commands
Input To:
F.5.10 Control Motion
Output From:
F.5.2 Navigate to Emergency Standby
Location
Interfacing Items
At FOD Location Signal (S)
Source / Destination
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
Coordinates (D)
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
FOD Coordinates
Input To:
467
Interfacing Items
Source / Destination
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Input To:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Output From:
F.3 Scan Airfield for FOD
F.3.4 Process Suitability and Location of
FOD
Navigation Commands
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
Output From:
F.5.1 Process Navigation Commands
468
Interfacing Items
At Disposal Area Signal
Source / Destination
Input To:
F.4.7 Release FOD
F.5.10 Control Motion
Output From:
F.5.4 Navigate to Disposal Area
Coordinates (D)
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
Input To:
F.5.10 Control Motion
Output From:
F.5.4 Navigate to Disposal Area
Navigation Commands
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
Output From:
F.5.1 Process Navigation Commands
469
Interfacing Items
(Ext) Obstacle Identification from
Obstacle
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
Output From:
(External) Obstacles IOs
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
Output From:
(External) Obstacles IOs
Obstacle Characteristics
Input To:
F.5.7 Anticipate Obstacle Movement
Output From:
F.5.5 Detect Obstacles
F.5.6 Receive Aircraft Trajectory Data
Input To:
(External) Obstacles IOs
Output From:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.5 Detect Obstacles
470
Interfacing Items
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Output From:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Input To:
F.5 Navigate Airfield
F.5.6 Receive Aircraft Trajectory Data
Output From:
F.1 Command and Control System
F.1.6 Transmit Inbound Aircraft Data to
System Elements
Obstacle Characteristics
Input To:
F.5.7 Anticipate Obstacle Movement
Output From:
F.5.5 Detect Obstacles
F.5.6 Receive Aircraft Trajectory Data
Interfacing Items
Obstacle Characteristics
Source / Destination
Input To:
F.5.7 Anticipate Obstacle Movement
Output From:
F.5.5 Detect Obstacles
471
Interfacing Items
Source / Destination
F.5.6 Receive Aircraft Trajectory Data
Obstacle Trajectory
Input To:
F.5.8 Avoid Obstacles
Output From:
F.5.7 Anticipate Obstacle Movement
Interfacing Items
Coordinates (D)
Source / Destination
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
Obstacle Path
Input To:
F.5.10 Control Motion
Output From:
F.5.8 Avoid Obstacles
Obstacle Trajectory
Input To:
F.5.8 Avoid Obstacles
Output From:
F.5.7 Anticipate Obstacle Movement
Interfacing Items
Coordinates (D)
Source / Destination
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
Input To:
F Perform AFDIRTS Functions
F.5 Navigate Airfield
F.5.9 Determine Location
Interfacing Items
At Disposal Area Signal
Source / Destination
Input To:
F.4.7 Release FOD
F.5.10 Control Motion
Output From:
F.5.4 Navigate to Disposal Area
Input To:
F.5.10 Control Motion
Output From:
F.5.2 Navigate to Emergency Standby
Location
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
473
Interfacing Items
Source / Destination
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
Coordinates (D)
Input To:
F.5.2 Navigate to Emergency Standby
Location
F.5.3 Navigate to FOD Location
F.5.4 Navigate to Disposal Area
F.5.8 Avoid Obstacles
F.5.10 Control Motion
Output From:
F.5.9 Determine Location
Input To:
F.5.10 Control Motion
Output From:
F.5.4 Navigate to Disposal Area
FOD Coordinates
Input To:
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Obstacle Path
Input To:
474
Interfacing Items
Source / Destination
F.5.10 Control Motion
Output From:
F.5.8 Avoid Obstacles
Input To:
F.5.10 Control Motion
Output From:
F.5.2 Navigate to Emergency Standby
Location
475
Interfacing Items
Heat to Environment
Source / Destination
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.3 Facilitate Braking
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Resistance to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
Sound to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.2 Facilitate Motion
Input To:
F.1 Command and Control System
476
Interfacing Items
Source / Destination
F.2
F.3
F.4
F.5
F.6
F.7
F.9
Operate Safely
Scan Airfield for FOD
Retrieve FOD
Navigate Airfield
Locomote System Elements
Maintain System
Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
Mobile Unit
Energy Source
Mobile Unit
Power
F.6.1
Facilitate Power
System Context
Ref.
AND
Ref.
AND
F.6.2
Facilitate
Movement
System Context
Movement
Command to
Locomote System
Elements
Heat to
Environment
Sound to Environment
Resistance to Environment
Date:
477
Mobile Unit
Energy
Source
Movement
Command to
Locomote
System Ele...
F.6.1
Facilitate Power
System Context
Mobile Unit
Power
F.6.2
Facilitate
Movement
System Context
Heat to
Environment
Resistance t...
Sound to En...
Date:
November 18, 2015
Interfacing Items
Source / Destination
Input To:
F.6.1 Facilitate Power
Input To:
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Output From:
F.6.1 Facilitate Power
478
Interfacing Items
Heat to Environment
Source / Destination
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.3 Facilitate Braking
Input To:
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Output From:
F.6.1 Facilitate Power
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Resistance to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
Sound to Environment
Input To:
(External) Environment IOs
Output From:
479
Interfacing Items
Source / Destination
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.2 Facilitate Motion
Resistance to
Environment
F.6.2.1
Facilitate Directional
Control
F.6.2.3
System Context
Ref.
Facilitate Braking
AND
AND
Ref.
F.6.2.2
System Context
Facilitate Motion
Mobile Unit
Power
Heat to
Environment
System Context
Mobile Unit
Kinetic Energy
Sound to
Environment
Date:
480
n2 Facilitate Movement
Mobile Unit
Power
Movement
Command to...
Mobile Unit
Power
Movement
Command to...
Movement
Command to
Locomote
System Ele...
F.6.2.1
Facilitate
Directional Control
System Context
Mobile Unit
Kinetic Energy
Resistance to
Environment
Mobile Unit
Kinetic Energy
Sound to
Environment
F.6.2.2
Facilitate Motion
System Context
F.6.2.3
Facilitate Braking
Heat to
Environment
System Context
Date:
November 18, 2015
Interfacing Items
Mobile Unit Kinetic Energy
Source / Destination
Input To:
F.6.2.3 Facilitate Braking
Output From:
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Input To:
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Output From:
F.6.1 Facilitate Power
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
481
Interfacing Items
Source / Destination
F.6.2.3 Facilitate Braking
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Resistance to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
Interfacing Items
Mobile Unit Kinetic Energy
Source / Destination
Input To:
F.6.2.3 Facilitate Braking
Output From:
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Input To:
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Output From:
F.6.1 Facilitate Power
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
482
Interfacing Items
Source / Destination
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
Sound to Environment
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.2 Facilitate Motion
Interfacing Items
Heat to Environment
Source / Destination
Input To:
(External) Environment IOs
Output From:
F Perform AFDIRTS Functions
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.3 Facilitate Braking
Input To:
F.6.2.3 Facilitate Braking
Output From:
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
Input To:
F.6 Locomote System Elements
F.6.2 Facilitate Movement
F.6.2.1 Facilitate Directional Control
F.6.2.2 Facilitate Motion
F.6.2.3 Facilitate Braking
483
Interfacing Items
Source / Destination
Output From:
F.5 Navigate Airfield
F.5.10 Control Motion
484
Interfacing Items
(Ext) Materials from Maintainer
Source / Destination
Input To:
F.7 Maintain System
F.7.2 Accept Materials
Output From:
(External) Maintainer IOs
Input To:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.1 Accept Parts
Output From:
(External) Maintainer IOs
Input To:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.3 Accept SW Updates
Output From:
(External) Maintainer IOs
Materials to Maintainer
Input To:
(External) Maintainer IOs
Output From:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.4 Eject Materials
Parts to Maintainer
Input To:
(External) Maintainer IOs
Output From:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.5 Eject Parts
Input To:
F.1 Command and Control System
F.2 Operate Safely
485
Interfacing Items
Source / Destination
F.3
F.4
F.5
F.6
F.7
F.9
Output From:
F.8 Provide Power
F.8.4 Transfer Power
F.7.1
Accept Parts
System Context
(Ext) Materials
from Maintainer
F.7.2
Accept Materials
System Context
F.7.3
Ref.
AND
Accept SW
Updates
AND
Ref.
System Context
Materials to
Maintainer
F.7.4
(Ext) SW Update
from Maintainer
Eject Materials
System Context
Parts to Maintainer
F.7.5
Eject Parts
System Context
Date:
486
n2 Maintain System
(Ext)
Materials
from
Maintainer
(Ext) Parts
from
Maintainer
(Ext) SW
Update from
Maintainer
F.7.1
Accept Parts
System Context
F.7.2
Accept Materials
System Context
F.7.3
Accept SW
Updates
System Context
F.7.4
Materials to
Maintainer
Eject Materials
System Context
F.7.5
Eject Parts
Parts to
Maintainer
System Context
Date:
Interfacing Items
(Ext) Parts from Maintainer
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.1 Accept Parts
Output From:
(External) Maintainer IOs
Interfacing Items
(Ext) Materials from Maintainer
Source / Destination
Input To:
F.7 Maintain System
F.7.2 Accept Materials
Output From:
(External) Maintainer IOs
Interfacing Items
(Ext) SW Update from Maintainer
Source / Destination
Input To:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.3 Accept SW Updates
Output From:
(External) Maintainer IOs
Interfacing Items
Materials to Maintainer
Source / Destination
Input To:
(External) Maintainer IOs
Output From:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.4 Eject Materials
488
Interfacing Items
Parts to Maintainer
Source / Destination
Input To:
(External) Maintainer IOs
Output From:
F Perform AFDIRTS Functions
F.7 Maintain System
F.7.5 Eject Parts
489
Interfacing Items
(Ext) Electrical Energy from Power
Source / Destination
Input To:
F.8 Provide Power
F.8.1 Accept External Power
F.8.2 Detect External Power Failure
Output From:
(External) Power IOs
Input To:
F.1 Command and Control System
F.1.9 Restore System
Output From:
F.8 Provide Power
F.8.2 Detect External Power Failure
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
490
F.8.1
(Ext) Electrical
Energy from
Power
Power Failure
Signal from
Power (S)
Accept External
Power
System Context
AND
AND
F.8.2
Detect External
Power Failure
F.8.4
System Context
Ref.
Transfer Power
OR
OR
F.8.3
Ref.
System Context
Generate
Emergency Power
transferred
Power (E)
System Context
Generator Power
Date:
n2 Provide Power
(Ext)
Electrical
Energy from
Power
(Ext)
Electrical
Energy from
Power
F.8.1
Accept External
Power
Power (E)
System Context
F.8.2
Power Failure
Signal from
Power (S)
Detect External
Power Failure
System Context
F.8.3
Generate
Emergency Power
System Context
Generator
Power
F.8.4
Transfer Power
transferred
Power (E)
System Context
Date:
Interfacing Items
(Ext) Electrical Energy from Power
Source / Destination
Input To:
F.8 Provide Power
F.8.1 Accept External Power
F.8.2 Detect External Power Failure
Output From:
(External) Power IOs
Power (E)
Input To:
F.8.4 Transfer Power
Output From:
F.8.1 Accept External Power
Interfacing Items
(Ext) Electrical Energy from Power
Source / Destination
Input To:
F.8 Provide Power
F.8.1 Accept External Power
F.8.2 Detect External Power Failure
Output From:
(External) Power IOs
Input To:
F.1 Command and Control System
F.1.9 Restore System
Output From:
F.8 Provide Power
F.8.2 Detect External Power Failure
Interfacing Items
Generator Power
Source / Destination
Input To:
F.8.4 Transfer Power
Output From:
F.8.3 Generate Emergency Power
Interfacing Items
Generator Power
Source / Destination
Input To:
F.8.4 Transfer Power
Output From:
F.8.3 Generate Emergency Power
Power (E)
Input To:
F.8.4 Transfer Power
Output From:
F.8.1 Accept External Power
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
493
Interfacing Items
At FOD Location Signal (S)
Source / Destination
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
Input To:
F.3.2 Determine FOD Suitability from a
Distance
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
FOD Coordinates
Input To:
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Input To:
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.9 Analyze FOD Trends
494
Interfacing Items
Source / Destination
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Input To:
(External) Airport Managers IOs
Output From:
F Perform AFDIRTS Functions
F.9 Analyze FOD Trends
F.9.4 Export FOD Reports
Input To:
F.3.4 Process Suitability and Location of
FOD
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.2 Determine FOD Suitability from a
Distance
Input To:
F.1 Command and Control System
F.2 Operate Safely
F.3 Scan Airfield for FOD
F.4 Retrieve FOD
F.5 Navigate Airfield
F.6 Locomote System Elements
F.7 Maintain System
F.9 Analyze FOD Trends
Output From:
F.8 Provide Power
F.8.4 Transfer Power
495
FOD Coordinates
F.9.1
Ref.
F.9.2
F.9.4
F.9.3
Retain Data
System Context
System Context
System Context
System Context
FOD
Characteristics
(D)
Ref.
Reports to
Airport Managers
(E)
Raw FOD
Data
Date:
496
At FOD Loca...
FOD Charac...
FOD Coordi...
FOD too La...
F.9.1
Accept FOD alert
time and date,
location
coordinates and...
System Context
Raw FOD
Data
F.9.2
Perform Trend
Analysis
System Context
FOD Trend
Data (D)
FOD Trend
Data (D)
F.9.3
Retain Data
System Context
F.9.4
Reports to
Airport
Managers (E)
Export FOD
Reports
System Context
Date:
F.9.1 Accept FOD alert time and date, location coordinates and FOD image data
Based On:
R.8.1 Types of Data
Table 63. F.9.1 Accept FOD alert time and date, location coordinates and FOD image data
Interfacing Items
Interfacing Items
At FOD Location Signal (S)
Source / Destination
Input To:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5.3 Navigate to FOD Location
497
Table 63. F.9.1 Accept FOD alert time and date, location coordinates and FOD image data
Interfacing Items
Interfacing Items
FOD Characteristics (D)
Source / Destination
Input To:
F.3.2 Determine FOD Suitability from a
Distance
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.1 Detect FOD
FOD Coordinates
Input To:
F.5.10 Control Motion
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.5 Navigate Airfield
F.5.3 Navigate to FOD Location
Input To:
F.4.2 Notify Personnel of Object too
Large for Retrieval
F.9 Analyze FOD Trends
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.4 Retrieve FOD
F.4.1 Determine FOD Dimensions
Input To:
F.9.2 Perform Trend Analysis
Output From:
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Input To:
F.3.4 Process Suitability and Location of
FOD
F.9 Analyze FOD Trends
498
Table 63. F.9.1 Accept FOD alert time and date, location coordinates and FOD image data
Interfacing Items
Interfacing Items
Source / Destination
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
Output From:
F.3 Scan Airfield for FOD
F.3.2 Determine FOD Suitability from a
Distance
Interfacing Items
FOD Trend Data (D)
Source / Destination
Input To:
F.9.3 Retain Data
F.9.4 Export FOD Reports
Output From:
F.9.2 Perform Trend Analysis
Input To:
F.9.2 Perform Trend Analysis
Output From:
F.9.1 Accept FOD alert time and date,
location coordinates and FOD image
data
499
Source / Destination
Input To:
F.9.3 Retain Data
F.9.4 Export FOD Reports
Output From:
F.9.2 Perform Trend Analysis
Interfacing Items
FOD Trend Data (D)
Source / Destination
Input To:
F.9.3 Retain Data
F.9.4 Export FOD Reports
Output From:
F.9.2 Perform Trend Analysis
Input To:
(External) Airport Managers IOs
Output From:
F Perform AFDIRTS Functions
F.9 Analyze FOD Trends
F.9.4 Export FOD Reports
500
Appendix D
501
Table of Contents
Updated Context Diagram....
504
516
519
502
544
548
550
553
554
555
555
558
558
558
560
503
Air Traffic
Control
Environment
Heat (E)
Sound (E)
Rain (M)
Resistance (E)
Wind (F)
Snow (M)
GPS Signals (D)
Gravity (F)
Inertia (F)
Barometric
Pressure
Obstacles
Airport
Managers
AFDIRTS
Aircraft
Operators
Forces (F)
Energy (E)
Data (D)
Signals (S)
Materials (M)
Parts (M)
Materials (M)
Fault Codes (D)
System Health (D)
Power
Parts (M)
Materials (M)
SW Update (S)
Maintenance Commands (D)
FOD
Maintainer
Figure 1. Updated AFDIRTS Context Diagram
504
The Concept Exploration phase of the systems engineering method produced three
concepts that could potentially solve the need for a FOD Detection and Retrieval
system. The three options were; the Roomba Option, which made use of roaming
mobile units that would continuously search the airfield for FOD (much like the vacuum
Roomba). The ground retrieval option, which made use of existing FOD detection
systems that would continuously sweep the airfield for FOD and then when found,
location would be transmitted to the mobile units for retrieval. And finally, the Airborne
Option which operated much like the ground retrieval option except the retrieval units
were airborne.
The Airborne Option was selected during the Concept Selection step of the systems
engineering method and the physical architecture has been documented in this report.
Informal trade studies revealed many advantages to the Airborne Option. Some of the
factors of selection were; mobile unit speed, ability to navigate above obstacles, ability
to cross unpaved surfaces and ease of FOD disposal. Additionally, it is believed that in
future versions, could incorporate bird deterrent functionality.
The AFDIRTS consists of six major subsystems that are discussed in more detail below.
505
506
COMP.3.1
IFerret TM &
AFDIRTS Interface
Unit
Maintenance IUser
Interface (MUI)
Airport Management
Display Unit (AMDU)
Subsystem
Subsystem
Subsystem
HWCI
COMP.1.5
ATC Radar Interface
Unit (ARIU)
Subsystem
COMP.1.6
(CCR) Command and
Control Radio
COMP.1.3
HWCI
Command and
Control Computer
(CCC)
HWCI
BACKUP CPU <-> CPU
NAV Radio
HWCI
COMP.6.1
COMP.4.2.5
Retrieval Telemetry
Radio
HWCI
ARIU-> CPU
Command and Control Computer (CCC) -> IFerret TM & AFDIRTS Interface U...
COMP.1.1
COMP.1.7
COMP.4.4.1
Command and
Control Interface Unit
(CCIU)
COMP.1.2
COMP.2.4
External System
External System
Airport Managers
External System
Subsystem
ENV.3
Maintainer
ENV.6
ENV.1
COMP.1.4
Backup CPU
Analysis Computer
Subsystem
HWCI
Date:
December 4, 2015
Number
Name
Type
Performs
COMP.1
Segment
COMP.1.1
Airport Management
Display Unit (AMDU)
Subsystem
COMP.1.2
Subsystem
507
COMP.1.3
HWCI
COMP.1.3.1
SWCI
COMP.1.4
Backup CPU
Subsystem
COMP.1.5
Subsystem
COMP.1.6
HWCI
COMP.1.7
Maintenance User
Interface (MUI)
Subsystem
Number
Name
Transfers
Connects to
L.1.1
Item System
Health to ATC
Component
COMP.1.2 ATC User
Interface (AUI)
Component
ENV.1 Air Traffic
Control
508
L.1.2
L.1.3
L.1.4
L.1.5
L.1.6
Command and
Control Computer
(CCC) -> IFerret TM
& AFDIRTS Interface
Unit
Item (Ext)
Maintenance
Commands from
Maintainer
Item System
Health Data to
Maintainer
Item System
Health to Airport
Managers
Item Unsuitable
FOD Data to Airport
Managers
Item FOD
Location
Item Unsuitable
FOD Location Data
Item Navigation
Modes
Component
COMP.1.2 ATC User
Interface (AUI)
Component
ENV.1 Air Traffic
Control
Component
COMP.1.7
Maintenance User
Interface (MUI)
Component
ENV.6 Maintainer
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
ENV.3 Airport
Managers
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
509
L.1.7
L.1.8
L.1.9
L.1.10
CCIU ->
COMMAND AND
CONTROL CPU
ARIU-> CPU
Item (Ext)
Aircraft Radar Data
from ATC
Item Self-Test
Results
Item System
Health
Item Aircraft
Trajectory Data
Item
Maintenance
Commands
Item Self-Test
Results
Item System
Health Data to
Maintainer
Component
COMP.1.5 ATC
Radar Interface
Unit (ARIU)
Component
ENV.1 Air Traffic
Control
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.2.4
Command and
Control Interface
Unit (CCIU)
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.5 ATC
Radar Interface
Unit (ARIU)
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.7
Maintenance User
Interface (MUI)
510
L.1.11
Item Self-Test
Results
Item System
Health to Airport
Managers
L.1.12
Item Command
Signal
Item Self-Test
Results
Item System
Health to ATC
L.1.13
L.1.14
Item Reports to
Airport Managers
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.2 ATC User
Interface (AUI)
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
COMP.6.1 Analysis
Computer
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.4 Backup
CPU
511
L.1.15
L.1.16
L.1.17
L.1.18
CCR-> Airport
Management
Display Unit
Retrieval Telemetry
Radio -> CCR
Item Aircraft
Trajectory Data
Item Emergency
Operation
Command
Item
Maintenance
Commands
Item Normal
Operation
Command
Item Unsuitable
FOD Location Data
Item Unsuitable
FOD Location Data
From ARV
Item Unsuitable
FOD Location Data
Item Inbound
Aircraft Data to
ARV
Item Navigation
Modes
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.4.4.1
Retrieval Telemetry
Radio
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.4.2.5 NAV
Radio
512
The System Health and Monitoring Segment is comprised of 4 HWCI and 1 SWCI which
come together to perform the Operate Safely Function. During this stage of system
development there was not enough information to determine critical subsystems to
satisfy requirement R.11.2.1.1 The system shall be capable of continuously monitoring
system health of critical subsystems therefore, COMP.2.3 and the identification of
critical components was reserved for the Engineering Development Stage.
Figure 4. COMP.2 System Health and Monitoring Segment Physical Tree
513
Figure 5. COMP.2 System Health and Monitoring Segment Physical Block Diagram
pbd System Health Monitoring Segment
COMP.1.3
Command and
Control Computer
(CCC)
HWCI
COMP.2.1
COMP.2.4
HWCI
HWCI
SHR -> SHC
Date:
December 4, 2015
514
Table 3. COMP.2 System Health and Monitoring Segment Functional Traceability Matrix
Number
Name
Type
Performs
COMP.2
System Health
Monitoring
Segment
Segment
Function F.2
Operate Safely
COMP.2.1
System Heath
Radio (SHR)
HWCI
COMP.2.2
System Health
Computer (SHC)
HWCI
COMP.2.2.1
System Health
Software
SWCI
COMP.2.3
Components
Defined as "Critical"
During Advanced
Development
HWCI
COMP.2.4
Command and
Control Interface
Unit (CCIU)
HWCI
Function F.2.1
Receive Telemetry
Signal From
Stationary Elements
Function F.2.3
Receive Telemetry
Data from Mobile
Elements
Function F.2.2
Monitor the Health
of Stationary
Element Critical
Subsystems
Function F.2.4
Monitor the Health
of Mobile Element
Critical
Components
Function F.2.4.1
Direct SHC
operation
Function F.2.5
Compensate for
Failures in Mobile
Unit Critical
Components
Function F.2.6
Provide Airport
Managers with
System Health Data
Function F.2.7
Provide ATC with
System Health Data
Function F.2.8
Provide
Maintenance
515
Personnel with
System Health Data
Number
Name
L.2.1
Critical
Item Critical
Components -> SHR Subsystem
Telemetry Signal
From Mobile
Elements
Item Critical
Subsystem
Telemetry Signal
from Stationary
Elements
SHR -> SHC
Item Critical
Subsystem
Telemetry Data
From Mobile
Elements
Item Critical
Subsystem
Telemetry Data
from Stationary
Elements
SHC -> CCIU
Item Fault Data
L.2.2
L.2.3
Transfers
Connects to
Component
COMP.2.1 System
Heath Radio (SHR)
Component
COMP.2.3
Components
Defined as "Critical"
During Advanced
Development
Component
COMP.2.1 System
Heath Radio (SHR)
Component
COMP.2.2 System
Health Computer
(SHC)
Component
COMP.2.2 System
Health Computer
(SHC)
Component
COMP.2.4
516
L.2.4
SHC-> Critical
Components
Item Critical
Component
Degraded Signal
Command and
Control Interface
Unit (CCIU)
Component
COMP.2.2 System
Health Computer
(SHC)
Component
COMP.2.3
Components
Defined as "Critical"
During Advanced
Development
517
The FOD Detection Segment will be comprised of a Commercial off the Shelf (COTS)
FOD Detection system. The Stratech Group, whom developed the IFerret will be
contracted to develop an Interface Unit that can transfer FOD information to the
AFDIRTS. This will be done during the Engineering Development Stage and will enable
automated FOD retrieval.
518
COMP.1.1
Airport Management
Display Unit (AMDU)
Subsystem
Analysis Radio
HWCI
COMP.3.1
IFerret TM &
AFDIRTS Interface
Unit
Command and Control Computer (CCC) -> IFerret TM & AFDIRTS Interface Unit
Command and
Control Computer
(CCC)
HWCI
Subsystem
Date:
December 4, 2015
519
Number
Name
Type
Performs
COMP.3
Detection Segment
Segment
COMP.3.1
Subsystem
Function F.3.1
Detect FOD
Function F.3.2
Determine FOD
Suitability from a
Distance
Function F.3.3
Determine Location
of FOD
Function F.3.4
Process Suitability
and Location of
FOD
Number Name
Transfers
Connects to
L.3.1
Item FOD
Location Data to
Mobile Units
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
L.3.2
Item FOD
Characteristics
Item Suitability
Data
Component
COMP.4 Air
Retrieval Vehicle
(ARV) Segment
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
Component
COMP.6.2 Analysis
Radio
520
L.1.6
L.1.5
Item Navigation
Modes
Item FOD
Location
Item Unsuitable
FOD Location Data
Component
COMP.1.3
Command and
Control Computer
(CCC)
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
521
The Air Retrieval Vehicle (ARV) is designed to transport the Retrieval Subsystem System
to the FODs location on the airfield and grasp it with a COTS gripper, the VERSABALL
developed by Empire Robotics. The ARV consists of four Subsystems; the Movement and
Control Subsystem, the Navigation Subsystem, ARV Power Subsystem, and the Retrieval
Subsystem. These subsystems will be discussed in detail below.
Figure 9. COMP.4 Air Retrieval Vehicle (ARV) Conceptual Image
522
The Movement and Control Subsystem has been designed to facilitate movement and
stability of the ARV while maneuvering to waypoints. It consists of an Attitude and
Heading Reference System (AHARS), Barometric Altimeter, GPS Unit, Movement and
Control Computer, 8 Propellers, 8 Electric Motors and 8 Electronic Speed Controllers.
Figure 11. COMP.4.1 Movement and Control Subsystem Physical Tree
ENV.4
Environment
Electronic Speed
Controller (ESC)_3
Electronic Speed
Controller (ESC)_4
HWCI
HWCI
HWCI
HWCI
HWCI
COMP.4.1.10
COMP.4.1.9
Electric Motor
(EM)_6
Electric Motor
(EM)_7
Electric Motor
(EM)_8
HWCI
HWCI
HWCI
HWCI
COMP.4.1.1
Attitude and Heading
Reference Systems
(AHRS)
COMP.4.1.8
Electric Motor
(EM)_5
COMP.4.1.15
COMP.4.1.16
COMP.4.1.17
COMP.4.1.18
Electronic Speed
Controller (ESC)_5
Electronic Speed
Controller (ESC)_6
Electronic Speed
Controller (ESC)_7
Electronic Speed
Controller (ESC)_8
HWCI
HWCI
HWCI
HWCI
HWCI
AHARS -> MCCPU
Electronic Speed
Controller (ESC)_2
Part
Electronic Speed
Controller (ESC)_1
COMP.4.1.20
COMP.4.1.14
Propeller_8
Part
HWCI
COMP.4.1.28
Propeller_7
Part
HWCI
COMP.4.1.27
Propeller_6
HWCI
HWCI
COMP.4.1.26
HWCI
ESC1 -> EM1
Electric Motor
(EM)_4
COMP.4.1.13
COMP.4.1.7
Barometric Altimeter
Electric Motor
(EM)_3
Part
COMP.4.1.2
COMP.4.1.6
Electric Motor
(EM)_2
COMP.4.1.12
Propeller_5
COMP.4.1.5
Electric Motor
(EM)_1
COMP.4.1.11
COMP.4.1.25
COMP.4.1.4
Propeller_4
Part
COMP.4.1.3
Propeller_3
Part
Part
Part
COMP.4.1.24
COMP.4.1.23
Propeller_2
COMP.4.1.22
Propeller_1
COMP.4.1.21
COMP.4.1.19
COMP.4.3.1
Power Distribution
Board (PDB)
HWCI
PDB -> ESC_7
HWCI
PDB-> ESC_3
COMP.4.2.1
NAV Computer
HWCI
Date:
December 4, 2015
523
Number
Name
Type
Performs
COMP.4.1
Movement and
Control Subsystem
Subsystem
COMP.4.1.1
Attitude and
Heading Reference
Systems (AHRS)
HWCI
Function F.4.1
Move and Control
ARV
Function F.4.1.27
Determine Position
in Space
COMP.4.1.2
Barometric
Altimeter
HWCI
COMP.4.1.3
Electric Motor
(EM)_1
HWCI
COMP.4.1.4
Electric Motor
(EM)_2
HWCI
Function F.4.1.6
Spin #2 Propeller
COMP.4.1.5
Electric Motor
(EM)_3
HWCI
Function F.4.1.9
Spin #3 Propeller
COMP.4.1.6
Electric Motor
(EM)_4
HWCI
Function F.4.1.12
Spin #4 Propeller
COMP.4.1.7
Electric Motor
(EM)_5
HWCI
Function F.4.1.15
Spin #5 Propeller
COMP.4.1.8
Electric Motor
(EM)_6
HWCI
Function F.4.1.18
Spin #6 Propeller
COMP.4.1.9
Electric Motor
(EM)_7
HWCI
Function F.4.1.21
Spin #7 Propeller
COMP.4.1.10
Electric Motor
(EM)_8
HWCI
Function F.4.1.24
Spin #8 Propeller
COMP.4.1.11
Electronic Speed
Controller (ESC)_1
HWCI
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
HWCI
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
HWCI
Function F.4.1.2
Control #1 Motor
Speed
Function F.4.1.5
Control #2 Motor
Speed
Function F.4.1.8
Control #3 Motor
Speed
Function F.4.1.28
Determine
Barometric Pressure
Function F.4.1.3
Spin #1 Propeller
524
COMP.4.1.14
Electronic Speed
Controller (ESC)_4
HWCI
COMP.4.1.15
Electronic Speed
Controller (ESC)_5
HWCI
COMP.4.1.16
Electronic Speed
Controller (ESC)_6
HWCI
COMP.4.1.17
Electronic Speed
Controller (ESC)_7
HWCI
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
HWCI
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
HWCI
COMP.4.1.19.1
MCCOPM Software
SWCI
COMP.4.1.20
Movement and
Control GPS Unit
(MCGPS)
HWCI
COMP.4.1.21
Propeller_1
Part
COMP.4.1.22
Propeller_2
Part
COMP.4.1.23
Propeller_3
Part
COMP.4.1.24
Propeller_4
Part
COMP.4.1.25
Propeller_5
Part
Function F.4.1.11
Control #4 Motor
Speed
Function F.4.1.14
Control #5 Motor
Speed
Function F.4.1.17
Control #6 Motor
Speed
Function F.4.1.20
Control #7 Motor
Speed
Function F.4.1.23
Control #8 Motor
Speed
Function F.4.1.1
Carry out
Movement and
Control Instructions
Function F.4.1.1.1
Supply MCCOMP
Instructions
Function F.4.1.26
Determine GPS
Location
Function F.4.1.4
Generate #1 Motor
Thrust
Function F.4.1.7
Generate #2 Motor
Thrust
Function F.4.1.10
Generate #3 Motor
Thrust
Function F.4.1.13
Generate #4 Motor
Thrust
Function F.4.1.16
Generate #5 Motor
Thrust
525
COMP.4.1.26
Propeller_6
Part
COMP.4.1.27
Propeller_7
Part
COMP.4.1.28
Propeller_8
Part
Function F.4.1.19
Generate #6 Motor
Thrust
Function F.4.1.22
Generate #7 Motor
Thrust
Function F.4.1.25
Generate #8 Motor
Thrust
Number Name
L.4.1.1
#1 Propeller <->
Environment
L.4.1.2
L.4.1.3
L.4.1.4
L.4.1.5
#2 Propeller <->
Environment
#3 Propeller <->
Environment
#4 Propeller <->
Environment
Barometric Altimeter /
Environment
Transfers
Item #1 Motor Thrust
Connects to
Component
COMP.4.1.21
Propeller_1
Component
ENV.4 Environment
Component
COMP.4.1.22
Propeller_2
Component
ENV.4 Environment
Component
COMP.4.1.23
Propeller_3
Component
ENV.4 Environment
Component
COMP.4.1.24
Propeller_4
Item Barometric
Pressure
Component
ENV.4 Environment
Component
COMP.4.1.2
Barometric
Altimeter
526
L.4.1.6
L.4.1.7
L.4.1.8
L.4.1.9
L.4.1.10
L.4.1.11
L.4.1.12
#5 Propeller <->
Environment
#6 Propeller <->
Environment
#7 Propeller <->
Environment
#8 Propeller <->
Environment
Component
ENV.4 Environment
Component
COMP.4.1.25
Propeller_5
Component
ENV.4 Environment
Component
COMP.4.1.26
Propeller_6
Component
ENV.4 Environment
Component
COMP.4.1.27
Propeller_7
Component
ENV.4 Environment
Component
COMP.4.1.28
Propeller_8
Item #1 Propeller
Rotation
Item #2 Propeller
Rotation
Item #3 Propeller
Rotation
Component
ENV.4 Environment
Component
COMP.4.1.3 Electric
Motor (EM)_1
Component
COMP.4.1.21
Propeller_1
Component
COMP.4.1.4 Electric
Motor (EM)_2
Component
COMP.4.1.22
Propeller_2
Component
COMP.4.1.5 Electric
Motor (EM)_3
527
L.4.1.13
L.4.1.14
L.4.1.15
L.4.1.16
L.4.1.17
L.4.1.18
Item #4 Propeller
Rotation
Item #5 Propeller
Rotation
Item #6 Propeller
Rotation
Item #7 Propeller
Rotation
Item #8 Propeller
Rotation
Component
COMP.4.1.23
Propeller_3
Component
COMP.4.1.6 Electric
Motor (EM)_4
Component
COMP.4.1.24
Propeller_4
Component
COMP.4.1.7 Electric
Motor (EM)_5
Component
COMP.4.1.25
Propeller_5
Component
COMP.4.1.8 Electric
Motor (EM)_6
Component
COMP.4.1.26
Propeller_6
Component
COMP.4.1.9 Electric
Motor (EM)_7
Component
COMP.4.1.27
Propeller_7
Component
COMP.4.1.10
Electric Motor
(EM)_8
Component
COMP.4.1.28
Propeller_8
Component
COMP.4.1.3 Electric
Motor (EM)_1
528
L.4.1.19
L.4.1.20
L.4.1.21
L.4.1.22
L.4.1.23
Component
COMP.4.1.11
Electronic Speed
Controller (ESC)_1
Component
COMP.4.1.4 Electric
Motor (EM)_2
Component
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
Component
COMP.4.1.5 Electric
Motor (EM)_3
Component
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
Component
COMP.4.1.6 Electric
Motor (EM)_4
Component
COMP.4.1.14
Electronic Speed
Controller (ESC)_4
Component
COMP.4.1.7 Electric
Motor (EM)_5
Component
COMP.4.1.15
Electronic Speed
Controller (ESC)_5
Component
COMP.4.1.8 Electric
Motor (EM)_6
Component
COMP.4.1.16
Electronic Speed
Controller (ESC)_6
529
L.4.1.24
L.4.1.25
L.4.1.26
L.4.1.27
L.4.1.28
Component
COMP.4.1.9 Electric
Motor (EM)_7
Component
COMP.4.1.17
Electronic Speed
Controller (ESC)_7
Component
COMP.4.1.10
Electric Motor
(EM)_8
Component
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
Component
COMP.4.1.11
Electronic Speed
Controller (ESC)_1
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
Component
COMP.4.1.19
530
L.4.1.29
L.4.1.30
L.4.1.31
L.4.1.32
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.14
Electronic Speed
Controller (ESC)_4
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.15
Electronic Speed
Controller (ESC)_5
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.16
Electronic Speed
Controller (ESC)_6
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.17
Electronic Speed
Controller (ESC)_7
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
531
L.4.1.33
L.4.1.34
L.4.1.35
L.4.1.36
L.4.1.37
Item AHRS
Coordinates
Item Digitized
Barometric Pressure
Item XX Volts DC to
ESC_1
Component
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.1
Attitude and
Heading Reference
Systems (AHRS)
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.2
Barometric
Altimeter
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.1.20
Movement and
Control GPS Unit
(MCGPS)
Component
COMP.4.1.11
532
Electronic Speed
Controller (ESC)_1
L.4.1.38
L.4.1.39
L.4.1.40
L.4.1.41
PDB-> ESC_3
Item XX Volts DC to
ESC_2
Item XX Volts DC to
ESC_3
Item XX Volts DC to
ESC_4
Item XX Volts DC to
ESC_5
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
Component
COMP.4.3.1
Power Distribution
Board (PDB)
Component
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.14
Electronic Speed
Controller (ESC)_4
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.15
Electronic Speed
Controller (ESC)_5
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
533
L.4.1.42
L.4.1.43
L.4.1.44
L.4.1.45
L.4.1.46
VR -> MCCPU
Item XX Volts DC to
ESC_6
Item XX Volts DC to
ESC_7
Item XX Volts DC to
ESC_8
Item Navigation
Instructions
Item Obstacle Path
Component
COMP.4.1.16
Electronic Speed
Controller (ESC)_6
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.17
Electronic Speed
Controller (ESC)_7
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.1.20
Movement and
Control GPS Unit
(MCGPS)
534
L.4.1.47
VR -> BARALT
Component
COMP.4.3.3
Voltage Regulator
Component
COMP.4.1.2
Barometric
Altimeter
Component
COMP.4.3.3
Voltage Regulator
535
The ARV Navigation Subsystem is designed to receive ARV navigation instructions from
the Command and Control Subsystem. It will enable the ARV to navigate the airfield
avoiding obstacles and airport traffic while executing movement commands.
536
GPS Satellites
External System
HWCI
nil
Analysis Computer
COMP.4.2.3
NAV RADAR Unit
HWCI
HWCI
HWCI
HWCI
COMP.4.2.1
NAV Computer
Weight Sensor
HWCI
COMP.4.2.4
NAV GPS
HWCI
COMP.1.6
Analysis Radio
COMP.4.4.4
COMP.4.2.2
COMP.6.2
ENV.9
COMP.6.1
Obstacles
COMP.4.4.3
FOD Camera Unit
HWCI
HWCI
COMP.4.1.19
NAV Computer -> MCCPU
HWCI
COMP.4.2.5
NAV Radio
COMP.4.4.2
NAV Computer -> VERSABALL System
HWCI
VERSABALL System
HWCI
Date:
December 4, 2015
537
Number
Name
Type
Performs
COMP.4.2
Subsystem
Function F.4.2
Navigate Airfield
COMP.4.2.1
NAV Computer
HWCI
COMP.4.2.2
HWCI
Function F.4.2.2
Process Navigation
Commands
Function F.4.2.6
Anticipate
Obstacle
Movement
Function F.4.2.7
Determine Path
Around Obstacles
Function F.4.2.3
Detect Obstacles
COMP.4.2.3
HWCI
COMP.4.2.4
NAV GPS
HWCI
COMP.4.2.5
NAV Radio
HWCI
Function F.4.2.4
Determine
Obstacle Location
Function F.4.2.8
Determine Location
Function F.4.2
Navigate Airfield
Function F.4.2.1
Receive Navigation
Commands
Function F.4.2.5
Receive Aircraft
Trajectory Data
from ATC
538
Number Name
L.4.2.1
(EXT) Obstacle -> NCIPU
L.4.2.2
L.4.2.3
L.4.2.4
L.4.2.5
L.4.2.6
Transfers
Item (Ext)
Obstacle
Identification from
Obstacle
Item (Ext)
Aircraft Location
from Aircraft
Item (Ext)
Obstacle Location
from Obstacle
Item Obstacle
Illumination to
Obstacle
Item Location
Data from GPS
Satellites
Item At FOD
Location Signal
Item At FOD
Location Signal
Item
Coordinates
Connects to
Component
COMP.4.2.2 NAV
Camera & Image
Processing Unit
(NCIPU)
Component
ENV.7 Obstacles
Component
COMP.4.2.3 NAV
RADAR Unit
Component
ENV.7 Obstacles
Component
COMP.4.2.4 NAV
GPS
Component
ENV.9 GPS Satellites
Component
COMP.4.2.4 NAV
GPS
Component
COMP.6.1 Analysis
Computer
Component
COMP.4.2.4 NAV
GPS
Component
COMP.4.4.3 FOD
Camera Unit
Component
COMP.4.2.1 NAV
Computer
539
L.4.2.7
Item **NAV
RADAR UNIT<->
NAV Computer**
L.4.2.8
Item Obstacle
Characteristics
L.4.2.9
L.4.2.10
L.4.2.11
L.4.2.12
Item Transport to
Disposal Location
Signal
Item At Disposal
Location Signal
Item Navigation
Instructions
Item Obstacle
Path
Item Inbound
Aircraft Trajectory
Component
COMP.4.2.4 NAV
GPS
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.2.3 NAV
RADAR Unit
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.2.2 NAV
Camera & Image
Processing Unit
(NCIPU)
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.4.4 Weight
Sensor
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.4.2
VERSABALL System
Component
COMP.4.1.19
Movement and
Control Computer
(MCCOMP)
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.2.1 NAV
Computer
540
Item Navigation
Command
L.4.2.13
L.1.18
Item Inbound
Aircraft Data to
ARV
Item Navigation
Modes
Component
COMP.4.2.5 NAV
Radio
Component
COMP.4.2.5 NAV
Radio
Component
COMP.6.2 Analysis
Radio
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.4.2.5 NAV
Radio
541
The ARV Power Subsystem supplies stored power to ARV Components. It consists of a
Battery, a Power Distribution Board, and a Voltage Regulator.
**The Type of Battery that will be utilized (Nickel Cadmium (NiCd), Nickel-Metal Hydride
(NiMH), Lead Acid, Lithium-Ion (Li-Ion) Lithium-Polymer (LiPo) will be determined in a formal trade
study and submitted as a SM4 deliverable**
Figure 15. COMP.4.3 ARV Power Subsystem Physical Tree
542
COMP.4.1
Subsystem
Retrieval Subsystem
Subsystem
Movement and
Control Subsystem
VR - > AHRS
COMP.5.5
COMP.4.3.3
Battery Charger
HWCI
Voltage Regulator
BATT -> VR
HWCI
COMP.4.3.2
Battery
COMP.4.1.11
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
Electronic Speed
Controller (ESC)_4
HWCI
HWCI
Electronic Speed
Controller (ESC)_7
HWCI
COMP.4.1.16
Electronic Speed
Controller (ESC)_6
HWCI
COMP.4.1.14
HWCI
Power Distribution
Board (PDB)
PDB-> ESC_3
HWCI
Electronic Speed
Controller (ESC)_5
COMP.4.1.17
COMP.4.3.1
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
HWCI
Electronic Speed
Controller (ESC)_1
HWCI
COMP.4.1.15
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
HWCI
HWCI
Date:
December 4, 2015
543
Number
Name
Type
Performs
COMP.4.3
Power Subsystem
Subsystem
COMP.4.3.1
HWCI
COMP.4.3.2
Battery
HWCI
COMP.4.3.3
Voltage Regulator
HWCI
Function F.4.3
Provide ARV
Electrical Power
Function F.4.3.9
Provide Power to
ESC_1
Function F.4.3.10
Provide Power to
ESC_2
Function F.4.3.11
Provide Power to
ESC_3
Function F.4.3.12
Provide Power to
ESC_4
Function F.4.3.13
Provide Power to
ESC_5
Function F.4.3.14
Provide Power to
ESC_6
Function F.4.3.15
Provide Power to
ESC_7
Function F.4.3.16
Provide Power to
ESC_8
Function F.4.3.1
Provide Stored
Electricity to ARV
Function F.4.3.2
Regulate NAV
Subsystem Voltage
Function F.4.3.3
Regulate
Movement and
Control Subsystem
Voltage
544
Function F.4.3.4
Regulate Retrieval
Subsystem Voltage
Table 12. COMP.3.2 ARV Power Subsystem Interface Descriptions
Number Name
Transfers
Connects to
L.4.3.1
Item XX Volts DC
Regulated
Movement and
Control Subsystem
Component
COMP.4.1
Movement and
Control Subsystem
L.4.3.2
L.4.3.3
L.4.3.4
L.4.3.5
VR - > AHRS
BATT -> VR
Item XX Volts DC
Regulated NAV
Subsystem Voltage
Component
COMP.4.3.3
Voltage Regulator
Component
COMP.4.2 ARV
Navigation
Subsystem
Item XX Volts DC
Regulated Retrieval
Subsystem Voltage
Component
COMP.4.3.3
Voltage Regulator
Component
COMP.4.3.3
Voltage Regulator
Item Electrical
Energy from Battery
Component
COMP.4.4 Retrieval
Subsystem
Component
COMP.4.3.2 Battery
Item Electrical
Energy from Battery
Component
COMP.4.3.3
Voltage Regulator
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.3.2 Battery
545
L.4.3.6
L.4.3.7
L.4.3.8
L.4.3.9
L.4.3.10
PDB-> ESC_3
Item XX Volts DC
to ESC_1
Item XX Volts DC
to ESC_2
Item XX Volts DC
to ESC_3
Item XX Volts DC
to ESC_4
Item XX Volts DC
to ESC_8
Component
COMP.4.1.11
Electronic Speed
Controller (ESC)_1
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.12
Electronic Speed
Controller (ESC)_2
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.13
Electronic Speed
Controller (ESC)_3
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.14
Electronic Speed
Controller (ESC)_4
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.18
Electronic Speed
Controller (ESC)_8
Component
COMP.4.3.1 Power
546
L.4.3.11
L.4.3.12
L.4.3.13
L.5.5.1
Item XX Volts DC
to ESC_6
Item XX Volts DC
to ESC_7
Item XX Volts DC
to ESC_5
Item Electrical
Energy from
Charger
Distribution Board
(PDB)
Component
COMP.4.1.16
Electronic Speed
Controller (ESC)_6
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.17
Electronic Speed
Controller (ESC)_7
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.1.15
Electronic Speed
Controller (ESC)_5
Component
COMP.4.3.1 Power
Distribution Board
(PDB)
Component
COMP.4.3.2 Battery
Component
COMP.5.5 Battery
Charger
547
The Retrieval Subsystem consists of 3 HWCI and 1 Subsystem. It is designed to allow the
ARV to perform the Grasp FOD and Release FOD Functions. In order to perform
these functions, the camera unit will allow the ARV to maneuver to the precise location
of the FOD, while the Weight Sensor and Telemetry Radio will weigh and notify
personnel of FOD that cannot be retrieved due to its weight.
**The Versaball Gripper is a COTS component that was selected to perform the as the result of
an informal trade study**
Figure 17. Versaball Gripper
548
COMP.4.4.4
Weight Sensor
COMP.4.2.4
NAV GPS
ENV.5
HWCI
FOD
External System
HWCI
COMP.4.4.1
COMP.4.2.1
HWCI
HWCI
NAV Computer
HWCI
COMP.4.4.2
VERSABALL System
Retrieval Telemetry
Radio
COMP.4.4.3
FOD Camera Unit
HWCI
Date:
December 4, 2015
549
Number
Name
Type
Performs
COMP.4.4
Retrieval Subsystem
Subsystem
COMP.4.4.1
HWCI
COMP.4.4.2
VERSABALL System
HWCI
COMP.4.4.3
HWCI
COMP.4.4.4
Weight Sensor
HWCI
Function F.4.4
Retrieve FOD
Function F.4.4.3
Notify Personnel of
Object too Large
for Retrieval
Function F.4.4.6
Notify Personnel of
Overweight
Objects
Function F.4.4.4
Grasp FOD
Function F.4.4.7
Release FOD
Function F.4.4.1
Determine FOD
Characteristics
Function F.4.4.5
Determine FOD
weight
Number
Name
Transfers
Connects to
L.4.4.1
Item Transport to
Disposal Location
Signal
Component
COMP.4.2.1 NAV
Computer
L.4.4.2
Item Overweight
Signal
Component
COMP.4.4.4 Weight
Sensor
Component
COMP.4.4.1
Retrieval Telemetry
Radio
550
L.4.4.3
L.4.4.4
L.4.4.5
L.4.4.6
L.4.4.7
L.4.2.5
Item Grasped
FOD's Weight
Item FOD
Item FOD
Identification from
FOD
Item Unsuitable
FOD Location Data
Item At FOD
Location Signal
Component
COMP.4.4.4 Weight
Sensor
Component
COMP.4.4.2
VERSABALL System
Component
COMP.4.4.4 Weight
Sensor
Component
COMP.4.4.2
VERSABALL System
Component
ENV.5 FOD
Component
COMP.4.4.3 FOD
Camera Unit
Component
ENV.5 FOD
Component
COMP.4.4.1
Retrieval Telemetry
Radio
Component
COMP.4.4.3 FOD
Camera Unit
Component
COMP.1.6 (CCR)
Command and
Control Radio
Component
COMP.4.4.1
Retrieval Telemetry
Radio
Component
COMP.4.2.4 NAV
GPS
551
L.4.2.10
Item At Disposal
Location Signal
Component
COMP.4.4.3 FOD
Camera Unit
Component
COMP.4.2.1 NAV
Computer
Component
COMP.4.4.2
VERSABALL System
552
The Power and Housing Segment is designed to house and power the ARV when not in
use. The figure below (Figure 21) is a conceptual image and not intended to be the
actual structural design. The structural design will be developed in the Advanced
Development Phase and it will result from prototypes that can withstand the elements
and are easily integrated with the IFerret Detection System. It may even be attached to
the IFerret Structure.
553
Command and
Control Segment
Segment
COMP.3
Detection Segment
External System
COMP.5.1
Power Transfer Panel
HWCI
HWCI
COMP.5.3
HWCI
Power Transfer Panel - > AV Housing Unit
Generator
HWCI
COMP.5.6
COMP.5.4
AV Housing Unit
Transfer Switch
Environment
COMP.5.2
ENV.4
Segment
Charging Receptacle
HWCI
COMP.4.3.2
COMP.5.5
Charging Receptacle -> Battery Char...
Battery Charger
HWCI
Date:
Battery
HWCI
December 4, 2015
554
Table 15. COMP.5 Power and Housing Segment Functional Traceability Matrix
Number
Name
Type
Performs
COMP.5
Power and AV
Housing Segment
Subsystem
COMP.5.1
HWCI
COMP.5.2
Power Transfer
Panel
Transfer Switch
COMP.5.3
Generator
HWCI
COMP.5.4
AV Housing Unit
HWCI
COMP.5.5
Battery Charger
HWCI
COMP.5.6
Charging
Receptacle
HWCI
Function F.5
Provide AV Housing
and System Power
Function F.5.4
Transfer Power
Function F.5.1
Accept External
Power
Function F.5.2
Detect External
Power Failure
Function F.5.3
Generate
Emergency Power
Function F.5.5
Provide Air Vehicle
Housing
Function F.5.6
Secure AV
Function F.5.8
Recharge Air
Vehicle
Function F.5.7
Make Charging
Connection
HWCI
Number
Name
Transfers
Connects to
L.5.1
Component
COMP.5.4 AV
Housing Unit
Item Electricity
Component
ENV.4 Environment
Component
COMP.5.1 Power
Transfer Panel
L.5.2
555
L.5.3
L.5.4
L.5.5
L.5.6
L.5.7
L.5.8
Item Electricity
Item Electricity
Item Electricity
Item Electricity
Item Generator
Power
Item Electricity
Component
COMP.5.4 AV
Housing Unit
Component
COMP.3 Detection
Segment
Component
COMP.5.1 Power
Transfer Panel
Component
COMP.1 Command
and Control
Segment
Component
COMP.5.1 Power
Transfer Panel
Component
COMP.5.1 Power
Transfer Panel
Component
COMP.6 FOD
Analysis Segment
Component
COMP.5.1 Power
Transfer Panel
Component
COMP.5.2 Transfer
Switch
Component
COMP.5.1 Power
Transfer Panel
Component
COMP.5.3
Generator
Component
COMP.5.5 Battery
Charger
556
L.5.9
L.5.10
L.5.11
L.5.12
Item (Ext)
Electrical Energy
from Power
Component
COMP.5.6
Charging
Receptacle
Component
COMP.5.2 Transfer
Switch
Item Power
Failure Signal from
Power
Component
ENV.8 Power
Component
COMP.5.2 Transfer
Switch
Item Electrical
Energy from
Charger
Item Electrical
Energy from
Charger
Component
COMP.5.3
Generator
Component
COMP.4.3.2 Battery
Component
COMP.5.5 Battery
Charger
Component
COMP.5.4 AV
Housing Unit
Component
COMP.5.6
Charging
Receptacle
557
The FOD analysis segment is designed to provide airport management with data that
can help them identify trends in Airfield Debris, so that they can formulate and
implement corrective measures to minimize FOD on the airfield. It consists of a telemetry
radio that will receive FOD Data and a computer and software to process this data.
Figure 23. COMP.6 FOD Analysis Segment Physical Tree
Figure 24. COMP.6 Power and Housing Segment Physical Block Diagram
558
IFerret TM &
AFDIRTS Interface
Unit
COMP.4.2.5
COMP.4.2.4
NAV Radio
HWCI
Subsystem
COMP.1.1
NAV GPS
Airport Management
Display Unit (AMDU)
HWCI
Subsystem
COMP.6.2
COMP.6.1
COMP.3.1
Analysis Radio
Analysis Computer
HWCI
HWCI
December 4, 2015
Number
Name
Type
Performs
COMP.6
HWCI
COMP.6.1
Analysis Computer
HWCI
Function F.6
Analyze FOD Trends
Function F.6.2
Perform Trend
Analysis
Function F.6.3
Retain Data
Function F.6.4
Export FOD Reports
559
COMP.6.1.1
Analysis Software
SWCI
COMP.6.2
Analysis Radio
HWCI
Function Carry
Out Operating
Instructions
Function F.6.1
Accept FOD alert
time and date,
location
coordinates and
FOD image data
Number Name
Transfers
Connects to
L.1.13
Item Reports to
Airport Managers
Component
COMP.1.1 Airport
Management
Display Unit (AMDU)
L.3.2
L.4.2.4
L.4.2.13
Item FOD
Characteristics
Item Suitability
Data
Item At FOD
Location Signal
Component
COMP.6.1 Analysis
Computer
Component
COMP.3.1 IFerret
TM & AFDIRTS
Interface Unit
Component
COMP.6.2 Analysis
Radio
Component
COMP.4.2.4 NAV
GPS
Component
COMP.6.1 Analysis
Computer
Component
COMP.4.2.5 NAV
Radio
Component
COMP.6.2 Analysis
Radio
560
L.6.1
Component
COMP.6.1 Analysis
Computer
Component
COMP.6.2 Analysis
Radio
561
Appendix E
562
Table of Contents
Overview... 564
Battery Alternatives . 565
Nickel Cadmium (NiCd).. 565
Nickel-Metal Hydride (NiMH).. 566
Lead Acid 567
Lithium-ion (Li-Ion).
568
563
Overview
This trade study was performed to make certain that the best type of battery was
selected for the Air Retrieval Vehicle (ARV) Subsystem. The battery criteria selected for
this study was based upon the characteristics ability to help best meet AFDIRTS
requirements. The selection criteria were battery gravimetric energy density (Wh/kg),
Fast Charge Time, Maintenance Requirements, and Operating Temperature Range.
While cost was not calculated into operational utility functions, cost was a factor for
selection and taken into consideration upon ARV battery type selection.
564
Battery Alternatives
45-80
100 to 200 (6V pack)
1500
1h typical
moderate
20%
1.25V6
20C
1C
-40 to 60C
30 to 60 days
$50
(7.2V)
$0.04
1950
565
Battery Alternatives
Nickel-Metal Hydride (NiMH)
The Nickel-Metal Hydride (NiMH) battery was improved in the 1980s when new hydride
alloys improved past stability issues (Battery University, 2015). Today the NiMH battery
provides 40 percent higher specific energy than the standard NiCd with the absence of
toxic metals. The NiMH battery does have its disadvantages (Battery University, 2015). It
is more delicate and complicated to charge than NiCd batteries; additionally the
battery self-discharges 20 percent or more in the first 24 hours after charge (Battery
University, 2015). The NiMH battery is one of the lowest costing and most readily
available and batteries for portable devices (Battery University, 2015).
Table 2. Nickel-Metal Hydride (NiMH) battery specifications.
Nickel-Metal Hydride (NiMH) Battery Specifications
60-120
200 to 300 (6V pack)
300 to 500
2-4h
low
30%
1.25V6
5C
0.5C or lower
-20 to 60C
60 to 90 days
$60
(7.2V)
$0.12
1990
566
Battery Alternatives
Lead Acid
Lead acid batteries are heavy and is less durable than nickel- and lithium-based
systems when deep-cycled (Battery University, 2015). When the battery is fully
discharged, it causes strain on the battery and subsequently robs the battery of a small
amount of storage capacity (Battery University, 2015). While this loss is small, the weardown characteristic eventually effects the battery that its performance drops to half
the nominal capacity. Depending this depth of discharge, lead acid for deep-cycle
applications provides 200 to 300 discharge/charge cycles (Battery University, 2015).
Lead acid batteries do not charge fast. Most types can take, a full charge can take 8
to16 hours to receive a full charge. Additionally, Lead Acid batteries must always be
stored at full state-of-charge.
Table 3. Lead Acid battery specification
Lead Acid Battery Specifications
30-50
<100 (12V pack)
200 to 300
8-16h
high
5%
2V
5C
0.2C
-20 to 60C
3 to 6 months
$25
(6V)
$0.10
1970
567
Battery Alternatives
Lithium-ion (Li-ion)
Lithium is the lightest of all metals and as such it provides the greatest electrochemical
potential providing the greatest specific energy per weight (Battery University, 2015).
However, it was discovered that cycling had the potential to causing thermal runaway
in the battery released flaming gases potentially causing fires or inflicting burns (Battery
University, 2015). This inherent instability, especially while charging, forced researchers to
search for a non-metallic solution (Battery University, 2015). This solution came by utilizing
lithium ions and while lower in specific energy than lithium-metal, Li ion proved to be a
safer alternative (Battery University, 2015). Today the Lithium-ion battery is the most
promising and fastest growing battery on the market (Battery University, 2015). In
addition, Li-ion is a low-maintenance battery, has no memory and does not need to be
fully discharged to maintain good health (Battery University, 2015).
Table 4. Lithium-ion (Li-ion) Battery Specifications
110-160
150 to 250 (7.2V pack)
500 to 1000
2-4h
very low
10%
3.6V
>2C
1C or lower
-20 to 60C
not req.
$100
(7.2V)
$0.14
1991
568
Battery Alternatives
Lithium-Polymer (LiPo)
Lithium polymer batteries are similar to lithium-ion batteries (Battery University, 2015).
Both use the same cathode and anode material and consist of a similar amount of
electrolyte (Battery University, 2015). Lithium polymer is distinctive from lithium-ion in that
a micro porous electrolyte replaces the traditional porous separator (Battery University,
2015). Lithium polymer batteries have a higher specific energy (only slightly) but can be
made thinner than conventional lithium-ion cells (Battery University, 2015). Lithium
polymer cells and can be made into a flexible foil-type case, while lithium-ion batteries
need a rigid case to press their electrodes together (Battery University, 2015). This type
of rigid case can increase battery weight by 25% (Battery University, 2015). In addition to
being lighter Lithium-Polymer batteries can be made into any shape including
extremely slim designs resembling a credit card (Battery University, 2015).
Table 5. Lithium-Polymer (LiPo) Battery Specifications
100-130
200 to 300 (7.2V pack)
300 to 500
2-4h
low
~10%
3.6V
>2C
1C or lower
0 to 60C
not req.
$100
(7.2V)
$0.29
1999
569
Selection Criteria
Selection criteria for the Air Retrieval Vehicle battery type was based upon the
characteristics ability to better meet AFDIRTS system performance requirements. The
selection criteria, and their relation to system requirements have been discussed in
further detail below.
Table 6. Battery Alternatives Selection Criteria Values
Gravimetric Energy
Density(Wh/kg)
Fast Charge Time
Nickel
Cadmium
(NiCd)
Nickel-Metal
Hydride
(NiMH)
Lead Acid
Lithium-ion
LiPo
(LithiumPolymer)
62.5
90
40
135
115
Maintenance
Requirement
1h
3h
12H
3H
2.5h
45 days
75 days
135 Days
Operating
Temperature
Range
100 C
80 C
80 C
80 C
60 C
570
Selection Criteria
Maintenance Requirement
Not only does more maintenance increase Operations & Maintenance (O&M) Costs;
but it decreases the amount of time the system is available again adversely affecting
R.11 Operational Availability.
571
Weightings
The Analytical Hierarchy Process was utilized to develop weightings for selection criteria.
A pairwise comparison was performed on the battery criteria listed above and has
been listed in the chart below.
Table 7. Numerical criteria importance values
Gravimetric
Energy Density
(Wh/kg)
Operating
Temperature
Range
Fast Charge
Time
Maintenance
Requirement
0.33333
0.2
0.33333
Maintenance Requirement
0.11111
0.2
0.33333
Sum
1.64444
4.53333
9.33333
18
572
Weightings
Table 9. Normalized Criteria Comparison Matrix
Gravimetric
Energy Density
(Wh/kg)
Operating
Temperature
Range
Fast Charge
Time
Maintenance
Requirement
0.60811
0.66176
0.53571
0.5
0.2027
0.22059
0.32143
0.27778
0.12162
0.07353
0.10714
0.16667
Maintenance Requirement
0.06757
0.04412
0.03571
0.05556
Sum
Operating
Temperature
Range
Fast Charge
Time
0.60811
0.66176
0.53571
0.5
0.5763968
0.2027
0.22059
0.32143
0.27778
0.2556238
0.12162
0.07353
0.10714
0.16667
0.11724
Maintenance Requirement
0.06757
0.04412
0.03571
0.05556
0.0507385
Gravimetric Energy
Density(Wh/kg)
Operating Temperature
Range
Sum
Maintenance
Requirement
Gravimetric
Energy Density
(Wh/kg)
Criteria Weights
(W)
573
Utility Functions
Table 11. Gravimetric Energy Density Utility Function Curve
LiPo
(LithiumPolymer)
Gravimetric Energy
Density(Wh/kg)
62.5
90
40
135
115
Utility Value
0.462
0.666
0.296
0.851
574
Utility Functions
Table 13. Operating Temperature Range Utility Function Curve
Nickel-Metal
Hydride
(NiMH)
Lead Acid
Lithiumion
LiPo
(LithiumPolymer)
Operating
Temperature
Range C
100 C
80 C
80 C
80 C
60 C
Utility Value
.8
.8
.8
.6
575
Utility Functions
Utility Value
Nickel-Metal
Hydride
(NiMH)
Lead Acid
Lithiumion
LiPo
(LithiumPolymer)
1 Hour
3 Hour
12 Hour
3 Hour
2.5 Hour
.833
.0833
.833
.875
576
Utility Functions
Nickel-Metal
Hydride (NiMH)
Lead Acid
Lithiumion
LiPo
(LithiumPolymer)
Maintenance
Requirement
(in Days)
45
75
135
Utility Value
.3
.5
.9
577
Rankings
Nickel-Metal Hydride
(NiMH)
Lead Acid
Lithium-ion (Li-ion)
LiPo (Lithium-Polymer)
0.576
0.266112
0.3836
0.1705
0.576
0.49
0.255
0.255
0.204
0.204
0.204
0.153
0.117
0.117
0.0975
0.00975
0.097
0.102
0.0507
0.01521
0.0254
0.04563
0.051
0.051
Weighted SUM
0.653322
0.7105
0.42988
0.928
0.796
$0.04
$0.12
$0.10
$0.14
$0.29
Weighted Utility
Scores
Weight
Gravimetric Energy
Density(Wh/kg)
Operating
Temperature Range
Fast Charge Time
Maintenance
Requirement
$0.04
$0.12
$0.1
$0.14
$0.29
0.65332
0.71043
0.42987
0.92816
0.79625
Cost Effectiveness
Function (Operational Utility
Effectiveness Matrix
Operational Utility
Function
16.3331
5.92023
4.29872
6.62972
2.74569
578
Rankings
Table 21. Effectiveness Rankings
Effectiveness Rankings
1 Lithium-ion (Li-ion)
2
3
4
5
LiPo (Lithium-Polymer)
0.7963
0.7104
0.6533
Lead Acid
0.4299
1
2
3
5
4
Nickel Cadmium
(NiCd)
16.3331
Lithium-ion (Li-ion)
6.62972
Nickel-Metal Hydride
(NiMH)
5.92023
Lead Acid
4.29872
LiPo (LithiumPolymer)
2.74569
579
Sensitivity Analysis
Gravimetric Energy
Density(Wh/kg)
Operating
Temperature Range
Fast Charge Time
Maintenance
Requirement
LiPo (Lithium-Polymer)
Lithium-ion (Li-ion)
Lead Acid
Nickel-Metal Hydride
(NiMH)
Utility Scores
Varied by 10%
0.508
0.733
0.325
1.1
0.936
1.1
0.88
0.88
0.88
0.66
0.833
0.0833
0.833
0.875
0.3
0.5
0.9
Lithium-ion (Li-ion)
Maintenance
Requirement
Varied Weighted SUM
Original Weighted Sum
LiPo (Lithium-Polymer)
Lead Acid
Nickel-Metal Hydride
(NiMH)
0.576
0.292608
0.422208
0.1872
0.6336
0.53914
0.255
0.2805
0.2244
0.2244
0.2244
0.1683
0.117
0.117
0.097461
0.0097461
0.097461
0.10238
0.0507
0.01521
0.02535
0.04563
0.0507
0.0507
0.705318
0.769419
0.4669761
1.006161
0.86051
0.653322
0.710427
0.4298721
0.928161
0.79625
Gravimetric Energy
Density(Wh/kg)
Operating
Temperature Range
Weight
580
Selection
The Lithium-ion (Li-ion) battery ranked the highest in effectiveness and second in cost
effectiveness. The lithium-ion battery has the highest power output per kilogram, the
second greatest in operational temperature Range -20 to 60C (-4 to 140F) and
requires zero maintenance. In addition, the Lithium-ion (Li-ion) battery ranked second in
cost effectiveness with an operating cost of 0.14 cents per cycle and has a cycle life
between 500 and1000 cycles.
A sensitivity analysis was performed by varying Gravimetric Energy Density (Wh/kg) and
Operating Temperature Range; the results did not change. The Lithium-ion (Li-ion)
battery is recommended as the battery to provide power to the ARV.
581
References
Battery University. (2015, December). Learn About Batteries. Retrieved from Battery
University: http://batteryuniversity.com/learn/article/whats_the_best_battery
582
Appendix F
583
Table of Contents
Introduction
586
System Description
587
Summary of Requirements
590
592
604
612
617
618
629
633
585
Introduction
586
System Description
The AFDIRTS consists of six major segments; The Command and Control Segment, the
System Health and Monitoring Segment, the FOD Detection Segment, the Air Retrieval
Vehicle (ARV), the Power and Housing Segment and the FOD analysis segment.
The Command and Control Segment is made up of 7 Hardware Configuration Items
(HWCI) and 1 Software Configuration Item (SWCI) integrated to perform function F.1
Command and Control the System. In addition to command and control the Segment
allows users to interface with the AFDIRTS.
The System Health and Monitoring Segment is comprised of 4 HWCI and 1 SWCI which
come together to perform the Operate Safely Function. During this stage of system
development there was not enough information to determine critical subsystems to
satisfy requirement R.11.2.1.1 The system shall be capable of continuously monitoring
system health of critical subsystems therefore, COMP.2.3 and the identification of
critical components was reserved for the Engineering Development Stage.
The FOD Detection Segment will be comprised of a Commercial off the Shelf (COTS)
FOD Detection system. The Stratech Group, whom developed the IFerret will be
contracted to develop an Interface Unit that can transfer FOD information to the
AFDIRTS. This will be done during the Engineering Development Stage and will enable
automated FOD retrieval.
The Air Retrieval Vehicle (ARV) (shown below in figure 1) is designed to transport the
Retrieval Subsystem System to the FODs location on the airfield and grasp it with a COTS
gripper. The ARV consists of four Subsystems; the Movement and Control Subsystem, the
Navigation Subsystem, ARV Power Subsystem, and the Retrieval Subsystem.
587
System Description
Figure 1. COMP.4 Air Retrieval Vehicle (ARV) Conceptual Image
The ARV Movement and Control Subsystem has been designed to facilitate movement
and stability of the ARV while maneuvering to waypoints. It consists of an Attitude and
Heading Reference System (AHARS), Barometric Altimeter, GPS Unit, Movement and
Control Computer, 8 Propellers, 8 Electric Motors and 8 Electronic Speed Controllers.
The ARV Navigation Subsystem is designed to receive ARV navigation instructions from
the Command and Control Subsystem. It will enable the ARV to navigate the airfield
avoiding obstacles and airport traffic while executing movement commands.
The ARV Power Subsystem supplies stored power to ARV Components. It consists of a
Lithium-Ion Battery, a Power Distribution Board, and a Voltage Regulator.
The Retrieval Subsystem consists of 3 HWCI and 1 Subsystem. It is designed to allow the
ARV to perform the Grasp FOD and Release FOD Functions. It utilizes the COTS
VERSABALL Gripper manufactured by Empire Robotics and shown below in figure 2. To
perform these functions, the camera unit will allow the ARV to maneuver to the precise
location of the FOD, while the Weight Sensor and Telemetry Radio will weigh and notify
personnel of FOD that cannot be retrieved due to its weight of physical characteristics.
588
System Description
Figure 2. Versaball Gripper
The Power and Housing Segment is designed to house and power the ARV when not in
use. The figure below (Figure 3) is a conceptual image and not intended to be the
actual structural design. The structural design will be developed in the Advanced
Development Phase and it will result from prototypes that can withstand the elements
and are easily integrated with the IFerret Detection System. It may even be attached to
the IFerret Structure.
Figure 3. COMP.5 Power and Housing Segment Conceptual Image
The FOD analysis segment is designed to provide airport management with data that
can help them identify trends in Airfield Debris, so that they can formulate and
implement corrective measures to minimize FOD on the airfield. It consists of a telemetry
radio that will receive FOD Data and a computer and software to process this data.
589
Summary of Requirements
Table 1. Requirements
Type
Number
Composite
Functional
18
Performance
93
Programmatic
Total
124
Programmatic, 7
Composite, 6
Functional, 18
Performance, 93
590
Summary of Requirements
Table 2. Quantitative vs Qualitative
Type
Number
Qualitative
Binary
19
Quantitative
96
Total
124
Qualitative
7%
Binary
15%
Quantitative
78%
591
592
Type
Description
Metric
Verified By
R.1.1
Reliability
Composite
Quantitative
Analysis
R.1.2
System Availability
Performance
Quantitative
Analysis
R.1.3
System
Maintainability
Performance
Quantitative
Analysis
R.1.4
Electromagnetic
Interference
Performance
Quantitative
Test
R.1.5
Equipment Located
Outside of Paved
Surfaces
Programmatic
Binary
Demonstration
593
Number Name
Type
Description
Metric
Verified By
R.1.6
Installation and
Acceptance
Standards
Composite
Binary
Inspection
R.1.7
Breakaway
Connector
Constraint
Binary
Inspection
R.1.8
Wind Loading
Constraint
Quantitative
Test
R.1.9
Performance in
Rain
Performance
Quantitative
Test
R.1.10
Performance in
Snow
Performance
Quantitative
Test
R.1.11
Performance in
Wind
Performance
Quantitative
Test
R.1.12
Maintenance
Procedures
Programmatic
Quantitative
Analysis
594
Number Name
Type
Description
Metric
Verified By
R.1.13
Cleaning
Procedures
Programmatic
Qualitative
Analysis
R.1.14
Preventative
Maintenance
Procedures
Programmatic
Qualitative
Analysis
R.1.15
Recalibration Plan
Programmatic
Quantitative
Analysis
R.1.16
Scheduled
Component
Removals
Programmatic
Qualitative
Analysis
R.1.17
Call Center
Programmatic
Quantitative
Demonstration
595
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
User Interviews
Requirements
User Surveys
R.1.1 Reliability
R.1.2 System Availability
R.1.3 System Maintainability
R.1.4 Electromagnetic Interference
R.1.5 Equipment Located Outside of Paved Surfaces
R.1.6 Installation and Acceptance Standards
R.1.7 Breakaway Connector
R.1.8 Wind Loading
R.1.9 Performance in Rain
R.1.10 Performance in Snow
R.1.11 Performance in Wind
R.1.12 Maintenance Procedures
R.1.13 Cleaning Procedures
R.1.14 Preventative Maintenance Procedures
596
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
Type
Basis of
Description
Metric
Verified By
R.1.18
LINK.1.2
ATC -> AUI
Performance
F.1.9 Interface
with Air Traffic
Control
Quantitative
Analysis
R.1.19
LINK.5.9
External
Power ->
Power
Performance
F.5.4 Transfer
Power
Quantitative
Test
User Interviews
Name
User Surveys
Number
Requirements
R.1.15 Recalibration Plan
R.1.16 Scheduled Component Removals
R.1.17 Call Center
597
Transfer
Panel
598
Name
Type
Basis of
Description
Metric
Verified By
R.2
AFDIRTS
Command and
Control
Functional
Qualitative
Test
R.2.1
Power Failure
Performance
F.1.11 Restore
System
Binary
Test
R.2.2
Navigation Data
Functional
F.1.7 Transmit
Inbound Aircraft
Data to System
Elements
Quantitative
Test
R.2.3
Navigation Modes
Functional
Binary
Test
R.2.4
AFDIRTS
Communication
Composite
Qualitative
Demonstration
599
Number
R.2.5
Name
Command and
Control Segment
Specification
Type
Performance
Basis of
Description
Metric
Verified By
Quantitative
Test
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
User Interviews
Requirements
User Surveys
600
Name
Type
Basis of
Description
Metric
Verified By
R.2.5.1
COMP.1.2
ATC Interface
Unit (AIU)
Specification
Performance
F.1.1
Interface
with ATC
Quantitative
Demonstration
R.2.5.2
COMP.1.1
Airport
Management
Display Unit
(AMDU)
Specification
Performance
F.1.9
Interface
with Airport
Managers
Quantitative
Demonstration
R.2.5.3
COMP.1.3
Command
and Control
CPU
Specification
Performance
F.1.2 Initiate
System
Modes
Quantitative
Test
R.2.5.4
COMP.1.6
Command
and Control
Data Link
Specification
Performance
F.1.7 Transmit
Inbound
Aircraft Data
to System
Elements
Quantitative
Test
601
Number
Name
Type
Basis of
Description
(MOPS) for Unmanned Aircraft System
(UAS) Command and Control Data Links.
The MIU shall be capable of accepting
self-test commands from maintenance
personnel as well as displaying self-test
results and faults in critical/non-critical
subsystems. The MIU shall be evaluated
utilizing the usability heuristic evaluation
developed by Jakob Nielsen. If usability
problems are discovered they shall not
receive a usability severity rating of
greater than 1.
Metric
Verified By
Quantitative
Test
R.2.5.5
COMP.1.7
Maintenance
User Interface
(MIU)
Specification
Performance
F.1.10.2
Display
Maintenance
Data
R.2.5.6
COMP.1.4
Backup CPU
Specification
Performance
F.1.11 Restore
System
Quantitative
Test
R.2.5.7
COMP.1.3.1
Command
and Control
Software
Specification
Performance
F.1
Command
and Control
System
Quantitative
Test
602
Name
Type
Basis of
Description
Metric
Verified By
R.2.6
LINK.1.5
Iferret ->
AMDU Link
Specification
Performance
F.1.9
Interface
with Airport
Managers
Quantitative
Demonstration
603
Name
Type
Basis of
Description
Metric
Verified By
R.3
Safe
Operation
Composite
Qualitative
Demonstration
R.3.1
ATC
Emergency
Control
Performance
Quantitative
Test
R.3.2
Self-Test
Functional
Binary
Demonstration
R.3.3
Self-Test
Duration
Performance
Quantitative
Test
R.3.4
Maintainer
Self-Test
Functional
Binary
Test
R.3.5
System
Health
Specification
Functional
Binary
Demonstration
Test
604
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
User Interviews
Requirements
User Surveys
Table 11. System Health and Monitoring Segment Requirement Origin Map
605
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
User Interviews
User Surveys
Requirements
R.3.4 Maintainer Self-Test
R.3.5 System Health
Name
Type
Basis of
Description
Metric
Verified By
R.3.5.1
COMP.2.4
Command and
Control
Interface Unit
(CCIU)
specification
Performance
F.2.6 Provide
Airport
Managers with
System Health
Data
F.3.2 Determine
FOD Suitability
from a
Distance
F.4.3.2 Notify
Personnel of
Object too
Large for
Retrieval
F.4.3.5 Notify
Personnel of
Quantitative
Analysis
606
Number
Name
Type
Basis of
Description
Metric
Verified By
Overweight
Objects
R.3.5.2
COMP.2.2
System Health
Computer
(SHC)
Specification
Performance
F.2.2 Monitor
the Health of
Stationary
Element
Critical
Subsystems
Quantitative
Test
R.3.5.3
COMP.2.1
System Health
Data Link (SHR)
Specification
Performance
F.2.1 Receive
Telemetry
Signal From
Stationary
Elements
F.2.3 Receive
Telemetry Data
from Mobile
Elements
Quantitative
Demonstration
R.3.5.4
COMP.2.2.1
System Health
Software
Specification
Performance
F.2.4.1 Direct
SHC operation
Quantitative
Test
607
Name
Type
Description
Metric
Verified By
R.3.5.5
L.INK.2.2
SHR -> SHC
Internal Interface
Requirement
Performance
Quantitative
Test
608
Type
Basis of
Description
Metric
Verified By
R.4
FOD
Detection
Segment
Composite
F.3 Scan
Airfield for
FOD
Binary
Demonstration
R.4.1.1
FOD
Location
Reporting
Performance
Quantitative
Test
R.4.1.2
Suitability
Reporting
Performance
F.3.3
Determine
Location of
FOD
F.4.3.2 Notify
Personnel of
Object too
Large for
Retrieval
Quantitative
Demonstration
R.4.1.3
FOD
Detection
Performance
F.3.1 Detect
FOD
Binary
Test
R.4.1.4
Group
Object
Detection
Performance
F.3.1 Detect
FOD
Quantitative
Test
609
Number Name
Type
Basis of
Description
runway light fixture (in-pavement or
edge light), An adjustable crescent
wrench up to 8 in. (20 cm) in length), A
deep socket (at least 2 in. (5 cm) in
length), A piece of rubber from an
aircraft tire, A distorted metal strip (up to
8 in. (20 cm) in length), Fuel cap (aircraft
or automotive), Lug nut, Hydraulic line
(from aircraft or GSE, up to 8 in. (20 cm)
in length).
The system shall have the ability to
detect an unpainted, metal cylinder,
measuring 1.2 in (3.1 cm) high and 1.5 in
(3.8 cm) in diameter.
Metric
Verified By
Quantitative
Test
R.4.1.5
Metal
Cylinder
Detection
Performance
F.3.1 Detect
FOD
R.4.1.6
Sphere
Detection
Performance
F.3.1 Detect
FOD
Quantitative
Test
R.4.1.7
Lighting
Conditions
Performance
F.3.1 Detect
FOD
Qualitative
Test
R.4.1.8
Automated
Retrieval
Suitability
Functional
F.3.2
Determine
FOD Suitability
from a
Distance
Qualitative
Test
R.4.1.9
Detection
Time
Performance
F.3.1 Detect
FOD
Quantitative
Demonstration
610
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
User Interviews
Requirements
User Surveys
611
Name
Type
Basis of
Description
Metric
Verified By
R.4.1.10
COMP.3.1
IFerret
Specification
&AFDIRTS
Interface
Unit
Performance
F.3 Scan
Airfield for
FOD
Binary
Demonstration
Name
Type
R.4.1.11
LINK.3.1
IFerret &
AFDIRTS
Interface
Unit <-> NAV
Radio
Internal
Interface
Specification
Performance
Basis of
Description
Metric
Quantitative
Verified
By
Test
612
Name
Type
Description
Metric
R.5.1.1
Performance
Quantitative
Verified
By
Analysis
*Units in inches
R.5.1.2
Maximum All-Up
Weight (AUW)
Performance
Quantitative
Analysis
R.5.1.3
MAX Operational
Flight Time
Performance
Quantitative
Test
R.5.1.4
Performance
Quantitative
Test
R.5.1.5
MAX Operating
Wind Speed
Performance
Quantitative
Test
613
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD) Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
SME Interviews
User Surveys
Requirements
Table 19. Air Retrieval Vehicle (ARV) Segment Requirement Origin Map
614
Name
Type
Basis of
Description
Metric
Verified By
R.5.1
COMP.4
Air Retrieval
Vehicle
Composite
F.4 Transport
Retrieval
Subsystem (ARV)
Quantitative
R.5.2
COMP.4.1
Movement
and Control
Subsystem
Specification
Performance
Quantitative
Demonstration
Test
R.5.3
COMP.4.2
Navigation
Subsystem
Functional
F.4.2 Navigate
Airfield
F.4.2.2 Process
Navigation
Commands
F.4.2.3 Detect
Obstacles
F.4.2.5 Receive
Aircraft
Trajectory Data
from ATC F.4.2.6
Anticipate
Obstacle
Movement
Quantitative
Demonstration
Test
615
Number
Name
Type
R.5.4
COMP.4.3
Power
Subsystem
Performance
R.5.5
COMP.4.4
FOD Retrieval
Subsystem
Functional
Basis of
F.4.2.7 Determine
Path Around
Obstacles
F.4.2.8 Determine
Location
F.4.4 Provide ARV
Electrical Power
F.4.3 Retrieve
FOD
F.4.3.5 Notify
Personnel of
Overweight
Objects
Description
Metric
Verified By
Quantitative
Test
Binary
Demonstration
616
Table 21. Air Retrieval Vehicle (ARV) Movement and Control Subsystem Requirements
Number Name
Type
Description
Metric
Verified By
R.5.2
Performance
Quantitative
Demonstration
Test
Movement
and Control
Subsystem
Specification
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD) Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
SME Interviews
User Surveys
Requirements
Table 22. Air Retrieval Vehicle (ARV) Movement and Control Subsystem Requirement Origin Map
617
Table 23. Air Retrieval Vehicle (ARV) Movement and Control Subsystem Specifications
Number
Name
Type
Basis of
Description
Metric
R.5.1.1
COMP.4.1.3
COMP.4.1.4
COMP.4.1.5
COMP.4.1.6
COMP.4.1.7
COMP.4.1.8
COMP.4.1.9
COMP.4.1.10
Electric Motor
Specification
Performance
Quantitative
Verified
By
Test
R.5.1.2
COMP.4.1.11
COMP.4.1.12
COMP.4.1.13
COMP.4.1.14
COMP.4.1.15
COMP.4.1.16
COMP.4.1.17
COMP.4.1.18
Electronic
Speed
Controller
Specification
Performance
F.4.1.2 Control #1
Motor Speed
F.4.1.5 Control #2
Motor Speed
F.4.1.8 Control #3
Motor Speed
F.4.1.11 Control #4
Motor Speed
F.4.1.14 Control #5
Motor Speed
F.4.1.17 Control #6
Motor Speed
F.4.1.20 Control #7
Motor Speed
F.4.1.23 Control #8
Motor Speed
Quantitative
Test
618
Number
Name
Type
Basis of
Description
Metric
R.5.1.3
COMP.4.1.19.1
MCCOMP
Software
Specification
Performance
Quantitative
Verified
By
Test
R.5.1.4
COMP.4.1.25
COMP.4.1.25
COMP.4.1.25
COMP.4.1.25
Propeller
Specification
Performance
F.4.1.16 Generate #5
Motor Thrust
F.4.1.19 Generate #6
Motor Thrust
F.4.1.22 Generate #7
Motor Thrust
F.4.1.25 Generate #8
Motor Thrust
Quantitative
Inspection
R.5.1.5
COMP.4.1.21
COMP.4.1.22
COMP.4.1.23
COMP.4.1.24
Pusher
Propeller
Specification
Performance
F.4.1.4 Generate #1
Motor Thrust
F.4.1.7 Generate #2
Motor Thrust
F.4.1.10 Generate #3
Motor Thrust
F.4.1.13 Generate #4
Motor Thrust
Quantitative
Inspection
R.5.1.7
COMP.4.1.19
Movement
and Control
Computer
Performance
Quantitative
Test
619
Number
R.5.1.8
Name
(MCCOMP)
Specification
COMP.4.1.20
Movement
and Control
GPS Unit
(MCGPS)
Specification
Type
Basis of
Description
Metric
Verified
By
Performance
Quantitative
Test
Table 24. Air Retrieval Vehicle (ARV) Movement and Control Subsystem Internal Interface Specification
Number
Name
Type
Description
Metric
R.5.1.6
LINK.4.1.18
ESC1 -> EM1 Internal
Interface Requirement
Performance
Quantitative
Verified
By
Inspection
620
Name
Type
Description
Metric
Verified By
R.5.2
Mobile Unit
Navigation
Functional
Binary
Demonstration
R.5.2.1
Performance
Quantitative
Demonstration
R.5.2.2
Mobile Unit
Movement
Clearance
Performance
Quantitative
Demonstration
R.5.2.2.1
Separation from
Obstacles
Performance
Quantitative
Test
R.5.2.2.2
Separation from
Aircraft
Performance
Quantitative
Test
R.5.2.2.3
Separation from
Personnel
Performance
Quantitative
Test
R.5.2.2.4
Separation from
Vehicles
Performance
Quantitative
Test
R.5.2.3
Emergency
Posture
Functional
Binary
Demonstration
621
Number
Name
Type
Description
Metric
Verified By
R.5.2.4
FOD Location
Functional
Binary
Demonstration
R.5.2.5
Navigation
Commands
Functional
Binary
Demonstration
R.5.2.6
Disposal Area
Functional
Binary
Test
User Interviews
Requirements
User Surveys
Table 26. Air Retrieval Vehicle (ARV) Navigation Subsystem Requirement Origin Map
622
User Interviews
User Surveys
Requirements
R.5.2.3 Emergency Posture
R.5.2.4 FOD Location
R.5.2.5 Navigation Commands
R.5.2.6 Disposal Area
Name
Type
Basis of
Description
Metric
R.5.2.8
COMP.4.2.1
NAV Computer
Specification
Performance
F.4.2.2 Process
Navigation
Commands
Quantitative
Verified
By
Test
R.5.2.9
COMP.4.2.4
NAV GPS
Specification
Performance
F.4.2.8 Determine
Location
Quantitative
Test
623
Number
Name
Type
Basis of
Description
Metric
R.5.2.10
COMP.4.2.3
NAV RADAR Unit
Specification
Performance
F.4.2.4 Determine
Obstacle
Location
Quantitative
Verified
By
Test
R.5.2.11
COMP.4.2.5
NAV Radio
Specification
Performance
F.4.2.1 Receive
Navigation
Command
F.4.2.5 Receive
Aircraft Trajectory
Data from ATC
Quantitative
Test
R.5.2.12
COMP.4.1.1
Attitude and
Heading
Reference
Systems (AHRS)
Performance
F.4.1.27 Determine
Position in Space
Quantitative
Test
R.5.2.13
COMP.4.1.2
Barometric
Altimeter Unit
Specification
Performance
F.4.1.28 Determine
Barometric
Pressure
Quantitative
Test
624
Table 28. Air Retrieval Vehicle (ARV) Navigation Subsystem Internal Interface Specification
Number
Name
Type
Description
Metric
R.5.2.14
LINK.4.2.6
NAV GPS -> NAV Computer
Internal Interface Requirement
Performance
Quantitative
Verified
By
Inspection
Test
625
Name
Type
Basis of
Description
Metric
R.5.3
Power Subsystem
Specification
Performance
F.4.4 Provide
ARV
Electrical
Power
Quantitative
Verifi
ed By
Test
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD) Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
SME Interviews
User Surveys
Requirements
Table 30. Air Retrieval Vehicle (ARV) Power Subsystem Requirement Origin Map
626
Name
Type
Basis of
Description
Metric
R.5.3.1
COMP.4.3.2
Battery
Specification
Performance
F.4.4.1 Provide
Stored Electricity
to ARV
Quantitative
Verified
By
Test
R.5.3.2
COMP.4.3.1
Power Distribution
Board (PDB)
Specification
Performance
F.4.4.5 Provide
Power to ESC_1
F.4.4.6 Provide
Power to ESC_2
F.4.4.7 Provide
Power to ESC_3
F.4.4.8 Provide
Power to ESC_4
F.4.4.9 Provide
Power to ESC_5
F.4.4.10 Provide
Power to ESC_6
F.4.4.11 Provide
Power to ESC_7
F.4.4.12 Provide
Power to ESC_8
Quantitative
Test
R.5.3.3
COMP.4.3.3
Voltage
Regulator
Specification
Performance
F.4.4.2 Regulate
NAV Subsystem
Voltage
Quantitative
Test
627
Table 32. Air Retrieval Vehicle (ARV) Power Subsystem Internal Interface Specifications
Number
Name
Type
Description
Metric
R.5.3.4
LINK.4.3.4
BATT -> VR
Internal Interface
Specification
Performance
Quantitative
Verified
By
Test
628
Table 33. Air Retrieval Vehicle (ARV) FOD Gripping Subsystem Requirements
Number
Name
Type
Basis of
Description
Metric
Verified By
R.5.4
FOD
Retrieval
Functional
Binary
Demonstration
R.5.4.2
FOD
Weighing
Functional
Quantitative
Test
R.5.4.3
FOD Max
Weight
Performance
Quantitative
Test
R.5.4.4
FOD
location
Performance
Quantitative
Test
R.5.4.5
FOD
Dimensions
Performance
Quantitative
Test
629
Number
Name
Type
Basis of
Description
Metric
Verified By
R.5.4.6
FOD
Grasping
Performance
Quantitative
Test
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD)
Detection Equipment
User Interviews
Requirements
User Surveys
Table 34. Air Retrieval Vehicle (ARV) FOD Gripping Subsystem Requirement Origin Map
630
Table 35. Air Retrieval Vehicle (ARV) FOD Retrieval Subsystem Specifications
Number
Name
Type
Basis of
Description
Metric
R.5.4.1.1
COMP.4.4.3
FOD
Camera Unit
Specification
Performance
F.4.3.1
Determine
FOD
Characteristics
Quantitative
Verified
By
Test
R.5.4.1.2
COMP.4.4.4
Weight
Sensor
Specification
COMP.4.4.2
VERSABALL
System
Specification
Performance
F.4.3.4
Determine
FOD weight
Quantitative
Test
Quantitative
Test
COMP.4.4.1
Retrieval
Telemetry
Performance
Quantitative
Test
R.5.4.6.1
R.5.4.7
Performance
F.4.3.2 Notify
Personnel of
Object too
631
Radio
Specification
Large for
Retrieval
Table 36. Air Retrieval Vehicle (ARV) FOD Retrieval Subsystem Internal Interface Specifications
Number
Name
Type
Description
Metric
R.5.4.8
LINK.4.4.3
Weight Sensor <-> Versaball System
Internal Interface Specification
Performance
Quantitative
Verified
By
Test
632
Name
Type
Description
Metric
Verified By
R.6
AV Housing
and Power
Specification
Performance
Quantitative
Test
R.6.1
Back-Up
Power
Performance
Quantitative
Test
R.6.2
Loss of
External
Power
Performance
Quantitative
Test
633
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD)
Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
Requirements
User Interviews
User Surveys
Table 38. ARV Housing and Power Segment Requirement Origin Map
Name
Type
Basis of
Description
Metric
R.6.3
COMP.5.4
ARV housing
Specification
Performance
F.5 Provide
AV Housing
F.5.6
Secure ARV
Quantitative
Verified
By
Test
R.6.4
COMP.5.5
Battery
Charger
Specification
Performance
F.5.8
Recharge
Air Vehicle
Quantitative
Test
R.6.5
COMP.5.3
Generator
Specification
Performance
F.5.3
Generate
Quantitative
Test
634
Number
Name
Type
Basis of
Description
Emergency
Power
Metric
Verified
By
R.6.6
COMP.5.1
Power
Transfer
Panel
Specification
Performance
F.5.1
Accept
External
Power
F.5.4
Transfer
Power
Quantitative
Test
R.6.7
COMP.5.2
Transfer
Switch
Specification
Performance
F.5.2
Detect
External
Power
Failure
Quantitative
Test
R.6.8
COMP.5.6
Charging
Receptacle
Specification
Performance
F.5.7
Make
Charging
Connection
Quantitative
Test
Verified
By
Test
Table 40. ARV Housing and Power Segment Internal Interface Specification
Number
Name
Type
Description
Metric
R.6.9
LINK.5.7
Gen -> PWR
Transfer PNL
Int. Interface
Spec
Performance
Quantitative
635
Name
Type
Basis of
Description
Metric
Verified By
R.7
FOD Analysis
Segment
Functional
F.6 Analyze
FOD Trends
F.6.2 Perform
Trend Analysis
F.6.4 Export
FOD Reports
Qualitative
R.7.1
Types of Data
Functional
Binary
Test
R.7.1.1
Storage of
Data
Performance
F.6.1 Accept
FOD alert time
and date,
location
coordinates
and FOD
image data
F.6.3 Retain
Data
Quantitative
Test
Demonstration
636
FAA AC 150/5210-24
Airport Foreign Object
Debris (FOD) Management
FAA AC 150/5220-24
Airport Foreign Object
Debris (FOD) Detection
Equipment
Requirements
User Interviews
User Surveys
Name
Type
R.7.2
COMP.6.1
Analysis
Computer
Specification
Performance
R.7.3
COMP.6.2
Analysis Radio
Specification
Performance
Basis
of
Description
Metric
Quantitative
Verified
By
Test
Quantitative
Test
637
Number
Name
Type
R.7.4
COMP.6.1.1
Analysis
Software
Specification
Performance
Basis
of
Description
Metric
Quantitative
Verified
By
Test
Name
Type
Description
Metric
R.7.5
LINK.6.1
Analysis Radio -> Analysis
Computer Internal
Interface Specification
Performance
Quantitative
Verified
By
Test
638
Appendix G
639
Table of Contents
Introduction
641
642
648
640
Introduction
At the beginning of the SM4 Project, 5 risks were identified and subsequently tracked
throughout AFDIRTS development. Initial risks have been listed below:
1. If stakeholder interviews do not uncover all potential problems; or gather
enough information about the operating environment then these issues will
become more expensive to solve in the latter stages of AFDIRTS development;
because the design will be more complex and difficult to change.
2. If care is not taken to ensure traceability throughout system development,
then system architectural questions may go unanswered during the SM4
presentation; because a traceability matrix was unavailable.
3. If the triumvirate of conceptual design; as described by Kossiakoff et al. (2011,
p.175) is not applied to requirements analysis, then system requirements may be
developed as ambiguous and difficult to decompose into subordinate
requirements,; or just not make sense; because requirements analysis was not
properly performed.
4. If lessons learned are not documented as the project progresses, then they
may become difficult to recall during development of the final report; because
a lessons learned document was not available.
5. If the ATC interface requires too much of the controllers attention, it may
hinder their ability to control air/ground traffic; because they will be overtasked.
Risk Worksheets were developed along with one risk waterfall chart to aid in tracking
and documenting these initial risks.
641
Level
Likelihood
Probability of
Occurrence
Not Likely
~10%
Low likelihood
~30%
likely
~50
Highly Likely
~70
Near Certainty
~90
Consequence of Failure (C f )
Likelihood of Failure(L f )
Level
Performance/Technical
Schedule
Cost
Minimal or no impact
Minimal or no impact
Minimal or no impact
Minor
technical/performance
shortfall
Moderate
technical/performance
shortfall
Major
technical/performance
shortfall
642
Type:
Risk Title:
Design Flaws
Cost
Schedule
Performance
Description of Risk:
The AFDIRTS system concept does not address all
operational objectives; or some operational objectives
required to meet users needs go undocumented.
Consequence if Realized:
The systems specification could be submitted to
developers without necessary system specifications. This
can become an expensive fix later in system
development.
Success Criteria
Risk Level if
Successful
Cf
Lf
643
Type:
Risk Title:
Need -> Objective ->
Requirement -> Function ->
Component Traceability
Cost
Schedule
Performance
Description of Risk:
Traceability is not maintained throughout concept
development.
Consequence if Realized:
The project schedule may be threatened because it will
require extra resources to incorporate tractability in the
end.
Success Criteria
All CORE videos developed by
Christopher Olson have been
watched.
At the end of each workday, the
project has been exported under
the filename date_Roig.
Risk Level if
Successful
Cf
Lf
644
Type:
Risk Title:
ATC interface
Cost
Schedule
Performance
Description of Risk:
The ATC interface is designed to be too complex and
requires too much of the controllers attention.
Consequence if Realized:
The complexity of the ATC interface may hinder Air Traffic
Controllers ability to control air/ground traffic because
they will be distracted. This could lead to ground or air
incursions.
Success Criteria
The ATC interface design shall
provide only two options for ATC
to select. Additionally, the
interface shall be evaluated
utilizing Usability Heuristics for
User Interface Design developed
by Jakob Nielsen and zero
usability problems shall be
discovered.
Risk Level if
Successful
Cf
Lf
645
Type:
Risk Title:
Cost
Schedule
Performance
Description of Risk:
Lessons learned are not documented as the project
progresses.
Consequence if Realized:
They may become difficult to recall during development
of the final report.
Date
Scheduled
Success Criteria
Actual
Risk Level if
Successful
Cf
Lf
646
Type:
Risk Title:
Cost
Schedule
Performance
Substandard Requirements
Description of Risk:
System requirements are ambiguous, difficult to
understand or difficult to decompose into subordinate
requirements.
Consequence if Realized:
The development of inadequate requirements may lead
to a system that does not meet users needs.
Action/Event
Success Criteria
A survey is developed on
SurveyMonkey and at least 25
Users, SMEs and Stakeholders
participate.
2.5
647
Mitigation Strategies
Likelihood of Failure (L f )
2
3
4
5
6
Concept
Validation
Functional
Analysis and
Formulation
Performance
Requirements
Analysis
Performance
Requirements
Validation
Implementation
Concept
Exploration
Performance
Requirements
Formulation
Operational
Requirements
Analysis
Needs Validation
Feasibility
Definition
Functional
Analysis
Operational
Analysis
Project Proposal
648