EEL System Capstone ProjectEEL System Capstone Project To fulfill course 645.800 Systems Engineering Project requirements 09/20/15 . fulfill course 645.800 Systems Engineering Project

EEL System Capstone Project To fulfill course 645.800 Systems Engineering Project requirements

09/20/15

fulfill course 645.800 Systems Engineering Project requirements Prepared By: Robert P. Mascoe Jr.

For Mentor: Steven Biemer

Instructor: Christian “CJ” Ultra

Project Introduction

The Electromagnetic Effects Listening receiver system or EEL System applies system engineering principles to a unique customer problem identified by two government agencies. The problem identified was the availability of a cost effective and reliable system to detect and locate illegal/improper radio frequency (RF) transmissions. This presentation presents the application of the iterative and systematic system engineering process steps: Need, Requirements, Functions, System Model, and solution to address the customers issues.

Agenda 1. Biography 2. Intro & Need 3. Requirements

• Requirements Process • User/Stakeholder

4. CONOPS • OV-1 Diagram • Scenarios (or Use Cases)

5. Functional Concept • Context Diagram • Top-Level Functional Diagram (IDEF0, FBD, FFBD, Activity, N2 Diagram) • One Lower-Level Functional Diagram • Functions to Requirements Traceability

6. Physical Concept • Top-Level System Physical Diagram • One Subsystem Physical Diagram • N2 Diagram • Components to Functions Traceability

7. Trade Study • List all trade studies that were pertinent (i.e., subsystems) • One detailed trade study

8. Risk Management • Summarize all risks • Detail One Technical Risk

9. System Specification • Requirements Growth & Quantitative % • KPPs

10. Summary of Final Concept, and any Further Work 11. Your Lessons Learned 12. Recommendations

Biography I’ve been employed at The Johns Hopkins University Applied Physics Laboratory for 11 years as of June 2015; while at APL I’ve been involved with the development and fielding of new technologies. Generally all of these programs have been quick reaction capabilities (QRC) that bring science experiments to the field. I’m a seasoned electronics engineer with an extensive background in specialty electronics systems for both fixed and rotary wing platforms. Robert P. Mascoe Jr.

Intro & Need • The EEL project is required to fulfill course 645.800 Systems

Engineering Project requirements and is needed to satisfy the Masters of Science degree in Systems Engineering for Johns Hopkins University Whiting School of Engineering.

• The EEL system design has been requested by two government agencies through interviews of current personnel at these agencies. The EEL system is needed to detect and locate illegal/improper radio frequency (RF) transmissions intended to deny RF communication services to authorized licensed/unlicensed RF frequency bands. The EEL system is intended to provide geo-location information for RF transmitters operating illegally.

Requirements • Requirement Analysis: It was here where the

customer/users operational needs were translated into five major categories of requirements operational, functional, interfaces, constraints and performance. The customer/user “To provide” statements were translated into “ The EEL System shall”. This translation required research into similar types of systems and further communications with the customer/user to refine and derive requirements. It is of paramount importance that all system attributes are traceable from the requirements throughout the system engineering process.

Sequence

Stakeholder Need to thank Mr. Turonis for providing user/stakeholder needs and feedback on system concepts and operations. Mr. Turonis is a supervisory special agent and serves as the Branch Chief for National Security under the Threat Management Division of Federal Protective Service Headquarters. For the past several years, he has managed the FPS Joint Terrorism Task Force Program as part of his assignment to the FBI National Joint Terrorism Task Force (NJTTF.) As a task force officer, he is a member of the Intelligence Team and the Agency Coordination Team.

SHAWN ANTHONY TURONIS CHIEF, NATIONAL SECURITY BRANCH

THREAT MANAGEMENT DIVISION FEDERAL PROTECTIVE SERVICE

NATIONAL PROTECTION AND PROGRAMS DIRECTORATE

CONOPS - OV-1 Diagram

A

B

C

A

A

A

A

A

B

FPS Joint Incident Management Center

A

FPS Megacenters

1

1

AA

A

2

2

B

C

EEL Fixed Site Node

EEL Mobile Node

EEL Portable Node

A

RF Jammers

1

2A

1

1

2 Court Order Trackers

1

Cell Tower CommunicationsInternet

Internet GPS ConstellationGPS

3 ATM

1

4 Personnel Tracking Devices

4

1

3 4 5

3

3

3

3

3

3

A

1

3

PROCESS Users

CONOPS - Scenarios (or Use Cases)

• EEL System Scenario 1 A scenario that the EEL System is to support is to aid with protecting federal facilities by rapidly detecting someone attempting to jam cellular CDMA/GSM or portable radios around law enforcement/security forces facilities. • EEL System Scenario 2 A scenario that the EEL System is to support is to aid law enforcement with locating stolen property that has been tagged with locating equipment and the equipment is being disabled by a jammer. • EEL System Scenario 3 A scenario that the EEL System prevent is the failure of first responders to be able to communicate with victims and each other caused by the presence of a jammer.

“one foreign vendor marketed and sold nearly 300 models of signal jamming devices in the United States.4”

PROCESS Stakeholders

Functional Concept -

Context Diagram

People Stakeholders

Functional Concept – Top-Level Functional Diagram

F0.0 To detect, locate, and alert customers of illegal/improper radio frequency (RF) transmissions denying RF

communication services

F3.0 Detect illegal/improper signals

F9.0 Distribute Power

F2.0 Sense RF

F1.3 Implement operator inputs

F5.0 Locate illegal/improper signal

activities

F4.0 Collect illegal/improper signal activity from all

points

F8.0 Facilitate maintenance

F6.0 Distribute illegal/improper

signal activity reports

F7.0 Manage Enterprise

F10.0 Facilitate operation in

different environments

F1.4 Alert Operators

F3.1 Monitor operator signals

of interest

F3.2 Alarm on signals impacted

F2.1 Filter RF

F2.2 Amplify RF

F2.4 ComputePosition, Time and

Velocity of Host F2.4 Digitize RF

F2.5 Digitize RF

F2.3 Route RF

F10.1 Facilitate Fixed Site Sensors

Deployment

F10.2 Facilitate Mobile Sensors

Deployment

F10.3 Facilitate Portable Sensors

Deployment

F4.1 retrieve all signal reports and

signal data

F4.2 filter all reports and signal

data by type

F4.3 filter signal type reports by characteristics

F4.4 Compile reports and signal

data that correlate

F5.1 Compute range of

correlated s ignals

F5.2 Compute bearing for

correlated s ignals

F5.3 Compute pos ition (latitude & longitude) for

correlated s ignals

F5.4 Compute range, bearing,

and pos ition error reports

F6.1 Distribute signal activity report to FPS

centers

F6.2 Distribute signal activity report to FPS

centers Megacenters

F6.3 Distribute signal activity

report to sensors

F7.1 Collect all sensor

communications

F7.2 Monitor all communication

data

F7.3 analyze system results

against truth data

F7.4 database and store all reports

F7.5 database and store all signal

data

F7.6 backup all reports and signal data to online and

offline storage

F8.1 Monitor sensor status

F8.2 Facilitate remote built-in

test (BIT)

F8.3 Facilitate remote system

upgrades

F8.4 Provide system

maintenance instructions

F8.5 Facilitate system health

reports

F9.1 Convert & Filter Vehicle (12

VDC) Power

F9.2 Convert & filter commercial

AC power

F9.3 Store power for off-power grid

operations

F2.6 Extract signal Characteristics

F4.6 Distribute reports and signal data of correlated

signals

F10.4 Support Automatic

operations at fixed site

F10.5 Support automatic

operation while portable

F10.6 Support automatic

operations while mobile

F5.5 Distribute range, bearing,

pos ition and error (signal activity)

reports

F 2.7 Sort Signals by Characteristics

F9.4 Convert & Filter Vehicle (24/

28 VDC) Power

F4.5 Compile reports and signal data based upon customer signal

defin itions

F8.6 Facilitate local data

transfers to/from

F10.7 Distribute weight

F1.0 Interact with Operators

F1.2 Receive Operator Data

F1.1 Receive Operator

Commands

F3.3 Request additional sensor detection reports

and signal data

F3.4 Distribute detection report and signal data

Challenges

Functional Concept –

One Lower-Level Functional Diagram

F2.0 Sense RF

- RF

- RF (Time)CDMA

GSM

- RFR/C and UAV C&C

- RF (Position, Time Velocity)GPS Constellation

Court order tracking- RF

- RFLO/JACK

Portable Communications - RF

WWVH- RF (Time)

Alarm Systems- RF

Personal Tracking Devices- RF

First Responder Communications

- RF

Other Cellular Services- RF

Wireless Networks- RF (Time)

RF Jamming and Interference Signal Sources

- Illegal RF

- SOI/Collection Parameters

F2.2 Amplify RF

F2.4 ComputePosition, Time and

Velocity of Host F2.4 Digitize RF

F2.5 Digitize RF

F2.3 Route RF

F 2.7 Sort Signals by

Characteristics

RFRF

Filterd RFF2.1 Filter RF

Filtered & Amplified RF

Filtered, Amplified, and Routed RF

Filtered, Amplified, and Routed RF

F1.0 Interact with Operators

Time, Position, Velocity

Digitized RF Spectrum I/Q samples

- SOI/Collection Parameters

F3.0 Detect illegal/improper

signals

Environment

- Heat- RF Signals

- Weight- Electricity

F9.0 Distribute

Power

F2.6 Extract signal

Characteristics

Federal CommunicationsRegulations and Laws

TIA

Communication Standards Laws, and Regulations

ETSI

ITU

- Laws- Regulations

- Standards

- Standards

- Standards

- Laws, Regulations, Standards- Frequency Spectrum details- Waveform Descriptions- Collection Parameters- Licensed base station locations



Learning

Functional Concept – Functions to Requirements Trace

Functional Analysis Functional Title Requirement Identifier F1.1 Receive Operator Commands OPERA0019, Const0017, F1.2 Receive Operator Data Inter0021, F1.3 Implement operator inputs OPERA0019

F1.4 Alert Operators

OPERA0002, OPERA0004, OPERA0006, OPERA0008, OPERA0010, OPERA0012, OPERA0014, OPERA0016, OPERA0018

F2.1 Filter RF Const0011, Const0012, Const0013, Const0014, Const0015, Const0016, Const0017

F2.2 Amplify RF Const0011, Const0012, Const0013, Const0014, Const0015, Const0016, Const0017

F2.3 Route RF Const0011, Const0012, Const0013, Const0014, Const0015, Const0016, Const0017

F2.4 Compute

Inter0020, Position, Time and Velocity of Host F2.4 Digitize RF

Sample of 77 functions being traced

Physical Concept - Top-Level System Physical Diagram

Mobile Host

Portable Host

Fixed Host

Customer Portable Devices

FPS Megacenters FPS Joint Incident

Management Center

RF Antennas and Receiver

Server Workstation with Data Storage

Ruggedized Processor and Network Communications

Alarm Systems

CellularCommunications

Personal Tracking Devices

Portable Communications

GPS Constellation

MobileCommunication

Network

MobileCommunication

NetworkInternet

MobileCommunication

NetworkInternet

GOOD RF

R/C and UAV

Controllers

Court order tracking

RF Jammers & Interference Signals

BADRF

Gigabit

Wired & WirelessWired &

Wireless

Wired & Wireless

Wired & Wireless

Wired & Wireless

Wired & Wireless

Host Node

Receiver PackagingC1.4

Command ProcessorC1.5

RF Antennas and ReceiverC1.0


RF FrontendC1.1

RF

RF

RF

RF

RF

Cable

Cable

Cable

Cable

Cable

RF

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

RF DistributionC1.2

Cable

Cable

Cable

Cable

Cable

Cable

Wireless ModemGPRS/UMTS/LTE C1.2.2

wire

Cable

Cable

wire

Web Interface App

C1.5.1

LinuxOS

C1.5.2

Wire

GPS ReceiverC1.2.1

WireWireWire

RF Antennas1.1.1

RF LimitersC1.1.2

RF AmplifiersC1.1.4

RF FiltersC1.1.3

GPS AntennasC1.1.1.1

Communications AntennasC1.1.1.2

RF Signal AntennasC1.1.1.3




Ref. Osc.1.2.1.1 Cable

wire

Analog to Digital ProcessingC1.3

wire

Wire

Wire

Ethernet

RadioC1.2.3

Signal Distribution

C1.3.4

RadioMemory

C1.2.5

Wire

Wire

Wire

Wire

Cable

Signal ProcessingC1.3.2

Signal StorageC1.3.3

Wire

LinuxOS

C1.3.2.1

RadioProcessorC1.2.4

Linux OSC1.2.4.1

Wire

Wire

Wire

Wire

RFeyeApps

C1.3.2.2

Wire

Wire

Heat SinkC1.4.1

Power StorageC1.4.2

Power Distribution

C1.4.2

EnergyTransfer

Wire

RFeyeSite

C1.3.2.3

Wire

Cable

WireSystem TimingC1.3.1

Wi-Fi

Wi-Fi

Ruggedized Processor and Network CommunicationsC2.0

Communication ProcessorC2.2

Signal and Data StorageC2.4

Signal and Data ProcessorC2.5

Processor Packaging C2.7

EnterpriseData Manager C2.6

Wire

EnergyTransfer

Heat SinkC1.4.1

Power StorageC1.4.2

Power DistributionC1.4.2

LinuxOS

C2.2.2

RF

Sensor Detection reports, Signal recording, sensor

status C2.6.1

RFeyeApps

C1.3.2.2

Command Processor C2.8

WireWeb Interface App

C2.8.1

LinuxOS

C2.8.2

RFeyeSite

C1.3.2.3

Wire

Wire

LinuxOS

C1.3.2.1

Gigabit

Gigabit

Gigabit

Gigabit

Gigabit

Gigabit

WireWeb Interface

AppC2.2.1

Wire

Wire

Wire

Wire

Wire

Wire

Wire

Communication ModemsC2.1

2x High speed NetworkC2.3

Network BridgeC2.1.1

Wire

WireWire

Network HubC2.3.1

Gigabit

SATA III

Gigabit

Gigabit

SATA III

Wire


GigabitWire

Wire

Server Workstation with Data StorageC3.0

RF

Wire

Communication ModemsC3.1

Communication ProcessorC3.2

Networ

k Bridge

C2.1.1

WireWir

e

Wire

Gigabit

Workstation Packaging C3.7

Wire

EnergyTransfer

Power

StorageC2.7

.2

Heat

SinkC2.7

.1

Signal and Data ProcessorC3.5

EnterpriseData Manager C3.3

Sensor Detecti

on report

s, Signal

recording,

sensor status C2.6.1

RFeye

Apps

C3.5.1

Command Processor C3.4

Wire

Web

Interfac

e AppC3.2

.1

Linux

OSC3.2

.2

RFeye

SiteC3.5

.3

Wire

Wire

Linux

OSC3.5

.2

Gigabit

Gigabit

Gigabit

Gigabit

GigabitGigabit

Gigabit

Linux

OSC2.2

.2

Wire

Web

Interfac

e AppC2.2

.1

Gigabit

Gigabit

Networ

k HubC2.3

.1

Gigabit Gig

abit

Windows Server C3.8

SATA III

SATA III

Linux VMsC3.8.1

Windows VM’sC3.8.2

RFeye

C3.8.1.2

RFeye

SiteC3.8.1.1

Gigabit

Gigabit

Wire

Gigabit

Gigabit

Gigabit

Gigabit

Gigabit

SATA III

Apache Tomcat

Server

C3.8.2.2

Map Dat

a Viewer &

ManagerC3.8.2.4 ESRI

C3.8.2.1

RFeye

ManagerC3.8.2.3

SATA III SAT

A III

Gigabit

C3.8.3 RAID Storage

System Upgrades & ImagesC3.8.3.1

Maintenance

& Configuratio

nInstructions

C3.8.3.2

Data ArchiveManager C3.6

Sensor Detecti

on report

s, Signal

recording,

sensor status historyC3.6.1

GigabitGig

abit

Signal

Detection

and Sign

al Dat

aC3.8.3.4

Maps,

Terrain and Structur

e Dat

a C3.8.3.3

Wire

Wire

WireWireWireWire

Power DistributionC2.7.3

Physical Concept – One Subsystem Physical Diagram

Receiver PackagingC1.4

Command ProcessorC1.5

RF Antennas and ReceiverC1.0RF Antennas and ReceiverC1.0

RF FrontendC1.1

RF

RF

RF

RF

RF

Cable

Cable

Cable

Cable

Cable

RFCable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

Cable

RF DistributionC1.2

Cable

Cable

Cable

Cable

Cable

Cable

Wireless ModemGPRS/UMTS/LTE C1.2.2

wire

Cable

Cable

wire

Web Interface

AppC1.5.1

LinuxOS

C1.5.2

Wire

GPS ReceiverC1.2.1

WireWireWire

RF Antennas1.1.1 RF Limiters

C1.1.2RF AmplifiersC1.1.4

RF FiltersC1.1.3GPS Antennas

C1.1.1.1

Communications AntennasC1.1.1.2





Cable

wire

Analog to Digital ProcessingC1.3

wire

Wire Gigabit

RadioC1.2.3

Signal Distribution

C1.3.4

RadioMemory

C1.2.5

Wire

WireWire

Wire

Cable

Signal ProcessingC1.3.2

Signal StorageC1.3.3

Wire

LinuxOS

C1.3.2.1

RadioProcessorC1.2.4

Linux OSC1.2.4.1

Wire

WireWire

Wire

RFeyeApps

C1.3.2.2

WireHeat Sink

C1.4.1

Power StorageC1.4.2

Power Distribution

C1.4.2

EnergyTransfer

Wire

RFeyeSite

C1.3.2.3

Wire

WireSystem TimingC1.3.1

Wi-Fi

Wi-Fi

Ruggedized Processor and Network CommunicationsC2.0

Wire

Network BridgeC1.2.2.1

Ref. Osc.1.2.1.1

Wire

Wire

WireWire

Wire

Physical Concept – N2 Diagram

Sample of 25 by 25 matrix of Physical

Physical Concept – Components to Functions Traceability

Sample of 24 by 3 matrix

Trade Study - List all trade studies that were pertinent

• RF Antenna selection for the host platforms. The antenna selection was concerned with size, weight, RF gain, antenna coverage patterns, and the ability to operate in the required environment

• Geo-processing algorithms selection required reviewing multiple geo-location algorithms (Time Difference of Arrival (TDOA), Power of Arrival (POA), Frequency Difference of Arrival (FDOA), and Direction of Arrival (DOA)) then to review how the errors in accuracies can be measured and reported with error ellipses. The geo-processing selection was concerned with the types of signals being processed, the static and dynamic nature of the possible host platforms, the computational power and time required to obtain results

• Communication Network selection given that the EEL system is required to operate in the presence of RF jammers and interference as well as being mobile there was a need to identify a robust set of wireless communication protocols and mediums.

• EEL System size, weight, and power constraints required by the customer required considerable amounts of informal trades trying to identify a common packaging size to support the fixed, mobile, and portable host requirements.

• Additional processor and Wireless Communication - Reviewed options for additional processing with additional wireless communications plus multiple gigabit Ethernet support.

Trade Study - One detailed trade study

The selection criteria for the EEL System trade study are being derived from the system requirements with the focus on receiver module performance needs. This trade study has five selection criteria for the receiver module. All receiver modules selected in this study support an Ethernet interface which is required for data transfers from the RF receiver to Ruggedized Processor and Network Communications module. The high speed interface is needed to meet several of the operational and performance allocated requirements to pass time critical digitized data. An additional feature of the proposed receivers are their frequency ranges of operations which are greater than that required by the customer. All receivers’ noise figures are approximately 8 dB so that will not be used in the trade study. The five criteria items used in this receiver study are: power supported, environmental capabilities, receiver timing, I/Q data distribution, and signal demodulation capabilities. The customer’s feedback on component selection criteria is to weight system design selections based upon the criteria’s impact on achieving his systems objectives of: detection, location, reliability, and capability at a minimal cost.

Risk Management Summarize all risks

Risk ID Risk

Title

Risk Description Risk

Area

Likelihood

Level

Consequence

Level R001 Loss of Network

Communications If the EEL System remote receivers wireless communication network is jammed then the receiver will be unable to report its findings of jammer needed to allow cooperative geo-location.

Operational, Technical 3 4

R002 Disruption of GPS satellite coverage

If the mobile EEL system encounters GPS problems due to loss of satellite coverage there will be a lack of position updates, possible degradation in system timing, and incorrect Doppler frequency values being applied to collected signals causing a larger error ellipse for any given geo-location solution.


R003 Exponential growth in type and quantity of jammers

If the volume and number of manufactures of RF jamming and interference sources is not prevented from being shipped into the US the EEL system will require a periodic update program to address the different techniques being used by new devices causing an increased cost for EEL system after development.

Programmatic 5 3

R004 Limited geo-location accuracy If the customer is not willing to accept the need to use a portable EEL system to aid in locating a jammer signal in the last 100 to 300 meters than there is a possibility that the location provided may be a building or doors in error. Resulting in the customer going to the wrong residence or business.


R005 Limited sensor deployment If the customer cannot provide multiple observation points to operate the EEL system receivers the ability to detect and geo-locate will be negatively impacted.

Programmatic 3 4

Risk Management Detail One Technical Risk

Risk Title LOSS OF NETWORK COMMUNICATIONS

Description:

If the EEL System remote receivers wireless communication network is jammed then the receiver will be unable to report its findings of jammer needed to allow cooperative geo-location.

Initial Assessment:

Likelihood: 3

Consequences: 4

Description of Consequences if realized

Missing jammer reports will result in no or poorer then possible geo-location data.

LIK

EL

IHO

O

CONSEQUENCE

1 2 3 4 5 1

2

3

4

5 Mitigation Plan L C Impact Description

& Rationale ID Associated Report Mitigation Action

1 (Initial) -- --

2 RAR No mitigations action at this time 5 4 --

3 FAR No mitigations action at this time 5 4 --

4 CDR

As a result of the conceptual design: adding multiple wireless communication modems which operate over multiple frequencies. Allows risk R001 likelihood to be reduce from 5 to 3. This design change does not impact the consequence of the R0001.

3 4

The application of wireless communication diversity, and enhanced signal modulations should reduce the likelihood of all wireless communications being jammed. However, if they do get jammed the consequence is the same on the system.

5 TS No additional mitigations action at this time 3 4

6 A-SPEC No additional mitigations action at this time 3 4

System Specification Requirements Growth & Quantitative %

Total Quantitative % Qualitative

Binary Subjective

Requirement Analysis Report

User Needs 7 14 Operational Requirements 20 20 100.0 Functional Requirements 15 15 100.0 Interfaces Requirements 23 23 100.0 Constraints Requirements 17 17 100.0 Performance Requirements 9 9 100.0

RAR Totals: 84 84 100.0

Functional Analysis Report

User Needs 7 14

Operational Requirements 22 22 100.0

Functional Requirements 17 17 100.0

Interfaces Requirements 26 26 100.0

Constraints Requirements 17 17 100.0

Performance Requirements 10 10 100.0

FAR Totals: 92 92

Conceptual Design

User Needs 7 16






CD Totals: 103 103

Trade Study

User Needs 7 16






TS Totals: 94 94

System Specifications Report

User Needs 7 16 Operational Requirements 24 24 100.0 Functional Requirements 17 17 100.0 Interfaces Requirements 35 35 100.0 Constraints Requirements 17 17 100.0 Performance Requirements 10 10 100.0

SSR Totals: 103 103 100.0

Overall Requirement Growth from

RAR 23 Percent

System Specification KPP’s

The key performance parameter (KPP) for the EEL system focus on quantitative attributes of the system that captures the user needs but are limited in scope to support the required quantitative testing needed at acceptance.

ID Need/Requirement Statement Reference SKPP001 The EEL System shall detect L Band (1 to 2 GHz)

jammer/interference sources around federal facilities within a 7 mile radius (threshold), 14 mile radius (objective) within 3 minutes (threshold), 1 minute (objective).

USER014

KPP002 The EEL System shall be deployable from a fixed or mobile configuration to operate in a man portable configuration under local control by the customer in 1 hour (threshold), 30 minutes (objective).

USER012, Derived

KPP003 The EEL System shall be deployable to operate under remote control in a customer service vehicle in 1 hour (threshold), 30 minutes (objective).

USER011

KPP004 The EEL System shall be deployable to operate under local control in a customer service vehicle in 1 hour (threshold), 30 minutes (objective).

USER011

KPP005 The EEL system shall provide geo-location range and bearing with confidence/accuracy values to all detected jammer and interference sources using a earth model based upon the WGS 84 ellipsoid (threshold), geo-location latitude and longitude with confidence/accuracy values to all detected jammer and interference sources using a earth model based upon the WGS 84 ellipsoid (objective)

USER015

KPP006 The EEL System shall provide indications of jammer and interference signals by frequency using audible/visual indications following European Telecommunication Standards Institute (ETSI) Technical Report ETR 160 January 1995 on human factors aspects of multimedia telecommunications (threshold).

USER018

Summary of Final Concept, and any Further Work

• The EEL system presented is not a completed system design

• In reality the system developed so far requires a significant amount of effort to fully develop.

• In talks with customer and current employer to explorer funding source to continue work on the EEL system design

Summary of Final Concept, and any Further Work

• Explore methods to refine the scope of work to address risk R003 “Exponential growth in type and quantity of jammers”

• Explore methods to refine the processing and signal distribution data pipe requirements

• Further refine the frequencies to be monitored and scan rates required for the desired frequency range of interest 20 MHz to 6 GHz

Your Lessons Learned

• The Johns Hopkins University Whiting School of Engineering, System Engineering program provided great insight into the tasks of technically developing a complex system.

• Complex system designs fail without a skilled team of engineering leadership (the Systems Engineers) to apply a proven set of systematic 12 steps.


• It is critical that the design process review, refine, and translate systems needs to verifiable quantitative requirements

• Forward and reverse traceability of requirements, functions, connections, and components is required

• System attributes can be found through the examination of the systems concept of operation (CONOPS) and scenarios of use


• Design must account for all system actors good/bad actors, Mother Nature (the environment), or external laws, regulations, and standards

• Functions are developed in hierarchical structure which leads to the visualization of e these functions at different layers (levels).

• As these levels are developed and explored, these levels must be traceable to the original requirements and user needs.


• After multiple passes through these functions these functions and their connections are grouped into physical attributes or components which assemble into subsystems

Recommendations

• As a student it would be helpful to have the program (instructor) to assist the students with backfilling the customer’s voice during a portion of the capstone project especially when customer interaction may be limited.

Recommendations

• The need to have a complex system designed over several semesters to develop group capstone style project which goes through the A and B specification development and testing master plan.

Documents

EEL System Capstone ProjectEEL System Capstone Project To fulfill course 645.800 Systems Engineering Project requirements 09/20/15 . fulfill course 645.800 Systems Engineering Project