Conclusion - Group 4 - 2018/2019, Semester B, Quartile 3: Difference between revisions

From Control Systems Technology Group
Jump to navigation Jump to search
No edit summary
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<link rel="shortcut icon" href="https://www.tue.nl/favicon-64.ico" type="image/x-icon">
<div style="font-family: 'Georgia'; font-size: 15px; line-height: 1.5; max-width: 800px; word-wrap: break-word; color: #333; font-weight: 400; box-shadow: 0px 25px 35px -5px rgba(0,0,0,0.75); margin-left: auto; margin-right: auto; padding: 70px; background-color: white; padding-top: 30px;">
<link rel=http://cstwiki.wtb.tue.nl/index.php?title=PRE2018_3_Group4&action=edit"stylesheet" type="text/css" href="theme.css">
<div style="width:calc(100vw - 175px);background-color:#EFEFEF;padding-bottom:35px;position:absolute;top:0;left:0;">
<div style="font-family: 'q_serif', Georgia, Times, 'Times New Roman', serif; font-size: 14px; line-height: 1.5; max-width: 750px; word-wrap: break-word; color: #333; font-weight: 400; box-shadow: 0px 25px 35px -5px rgba(0,0,0,0.75); margin-left: auto; margin-right: auto; padding: 70px; background-color: white; padding-top: 25px;">


<div style="display: block; position: absolute; right: 0%;">
<div style="display: block; position: absolute; right: 6%;">
; Page navigation
; Page navigation
# [[PRE2018_3_Group4 | Root]]
# [[PRE2018_3_Group4 | Root]]
# [[Notes - Group 4 - 2018/2019, Semester B, Quartile 3|Notes]]
# [[Notes - Group 4 - 2018/2019, Semester B, Quartile 3|Notes from meeting]]
# [[Initial ideas - Group 4 - 2018/2019, Semester B, Quartile 3|Initial ideas]]
# [[Initial ideas - Group 4 - 2018/2019, Semester B, Quartile 3|Initial ideas]]
# [[Project setup - Group 4 - 2018/2019, Semester B, Quartile 3|Project setup]]
# [[Project setup - Group 4 - 2018/2019, Semester B, Quartile 3|Project setup]]
# [[General problem - Group 4 - 2018/2019, Semester B, Quartile 3|General problem]]  
# [[General problem - Group 4 - 2018/2019, Semester B, Quartile 3|General problem description]]  
# [[State of the Art - Group 4 - 2018/2019, Semester B, Quartile 3|State of the Art]]
# [[State of the Art - Group 4 - 2018/2019, Semester B, Quartile 3|State of the Art]]
# [[Specific problem - Group 4 - 2018/2019, Semester B, Quartile 3|Specific problem]]
# [[Specific problem - Group 4 - 2018/2019, Semester B, Quartile 3|Specific problem description]]
# [[Present situation - Group 4 - 2018/2019, Semester B, Quartile 3|Present situation]]
# [[Present situation - Group 4 - 2018/2019, Semester B, Quartile 3|Present situation]]
# [[Drones - Group 4 - 2018/2019, Semester B, Quartile 3|Drones]]
# [[Drones - Group 4 - 2018/2019, Semester B, Quartile 3|Drone analysis]]
# [[Solutions - Group 4 - 2018/2019, Semester B, Quartile 3|Solutions]]
# [[Solutions - Group 4 - 2018/2019, Semester B, Quartile 3|Solution analysis]]
# [[Airports under a microscope - Group 4 - 2018/2019, Semester B, Quartile 3|Airports under a microscope]]
# [[Airports under a microscope - Group 4 - 2018/2019, Semester B, Quartile 3|Airport analysis]]
# [[Recommendation report - Group 4 - 2018/2019, Semester B, Quartile 3|Recommendation report]]
# [[Types of Decision Models - Group 4 - 2018/2019, Semester B, Quartile 3 | Decision Model investigation]]
# [[Decision Model - Group 4 - 2018/2019, Semester B, Quartile 3 | Decision Model implementation]]
# [[Decision Model validation - Group 4 - 2018/2019, Semester B, Quartile 3|Decision Model validation]]
# [[Categorizing solutions - Group 4 - 2018/2019, Semester B, Quartile 3|Categorising solutions]]
# [[Web_Application_-_Group_4_-_2018/2019,_Semester_B,_Quartile_3 | Web Application]]
# [[Future - Group 4 - 2018/2019, Semester B, Quartile 3|Future]]
# [[Future - Group 4 - 2018/2019, Semester B, Quartile 3|Future]]
# [[Types of Decision Models - Group 4 - 2018/2019, Semester B, Quartile 3 | Decision Model Investigation]]
# [[Decision Model - Group 4 - 2018/2019, Semester B, Quartile 3 | Implemented Decision Model]]
# [[Decision Model validation - Group 4 - 2018/2019, Semester B, Quartile 3|Decision Model validation]]
# [[Categorizing solutions - Group 4 - 2018/2019, Semester B, Quartile 3|Categorizing solutions]]
# [[Conclusion - Group 4 - 2018/2019, Semester B, Quartile 3|Conclusion]]
# [[Conclusion - Group 4 - 2018/2019, Semester B, Quartile 3|Conclusion]]
# [[Discussion - Group 4 - 2018/2019, Semester B, Quartile 3|Discussion]]
# [[Discussion - Group 4 - 2018/2019, Semester B, Quartile 3|Discussion]]
Line 31: Line 28:
== Introduction ==
== Introduction ==


In the conclusion, we want to look back at important aspects of the project and discuss our most interesting findings and results. Where we look at both the literature research we did on unwanted UAV presence at and around airports, as well as the decision model we have created. We try to give a short summary and report on all the things learned whilst working on this project.  
In the conclusion, we want to look back at important aspects of the project and discuss our most exciting findings and results. Where we look at both the literature research we did on unwanted UAV presence at and around airports, as well as the decision model we have created. We try to give a short summary and report on all the things learned while working on this project.
 
== Literature Research ==
 
Looking back at the problem where last few years multiple airports were forced to cancel hundreds or thousands of flights affecting many travellers due to sightings of UAVs at airports. Not only does this negatively affect the passengers but this also costs the airports itself enormous amounts of money. However, from our literature research and interviews with multiple (Dutch) airports, we have learned that many airports have nothing in place to quickly deal with these UAV sightings, let alone have something in place against potential attacks with (weaponised) UAVs. Since we see the increase in the number of consumer UAVs growing each year, this problem seems to become more and more critical. Furthermore, from the interviews, we know that many of these airports without any defences would like to invest in a solution against unwanted UAV presence.
 
There are many different potential types of solutions against UAVs at airports that can detect, identify/classify, track or neutralise unwanted UAVs. There already even exist multiple concrete systems created by many different companies using a variety of technologies that could be invested in and deployed at these airports. However, the problem is that there are multiple differences between each of the solutions, and finding the best solutions for your airport is extremely difficult. This is where our research and decision model comes into play. We have thoroughly researched many of these solutions and systems as well as many different airports and types of airports in the Netherlands. After researching the differences between all of these systems, the differences between all of the airports and the wants of the stakeholders of the airports, we have come up with a list of attributes of the solutions which are to be to create a decision model.
 
== Decision Model ==
 
We have brainstormed and researched many different types of decision models, and found a voting advice application (VAA) such as the Dutch Stemwijzer, to most closely represent the model we would like to create. Where, instead of advising on political parties by using statements based on issues, we give advice on the best anti-UAV system for your airport based on propositions based on attributes of anti-UAV systems and the airport itself. For setting up these propositions, we used the attributes found in the literature research, to create an enormous table of solutions against the attributes. Then, we formed the propositions for the decision model based on the differences between the attributes of the solutions. In the decision model, we wanted to give the users of the model (airports) some freedom to indicate on attributes that they might find more interesting, or indicate attributes that the solution must necessarily have. Hence we also give the users both of these options. Furthermore, we give the users the option to decide on whether to be advice on detection only solutions, neutralisation only solutions or both. We feel like, with all of these features combined with the exhaustive research and validation of the model, the decision model is a useful anti-UAV decision tool for airports.


== Literature research ==
To make the decision model more tangible, more accessible to test, we decided to create a web-based application to implement the decision model. This decision model web-app asks the user all of the propositions, where more important attributes and must-haves can be indicated and calculates a score for each of the solutions based on the answers of the user. These scores then indicate which solution fits best with the airport and for the convenience of the user also the percentage of how well a solution matches with the airport is indicated. Lastly, the user can also find descriptions of the advanced solutions on the web-app. For the next couple of weeks, this web-app will be hosted online on the website: https://drones.jortdebokx.nl/.


== Presentation ==


The project has been wrapped in a presentation, which can be viewed [http://cstwiki.wtb.tue.nl/index.php?title=File:Presentatie_anti_uav.pdf here].


== Decision model ==
----
sd
Back to the [[PRE2018_3_Group4 | root page]].

Latest revision as of 11:48, 6 April 2019

Conclusion

Introduction

In the conclusion, we want to look back at important aspects of the project and discuss our most exciting findings and results. Where we look at both the literature research we did on unwanted UAV presence at and around airports, as well as the decision model we have created. We try to give a short summary and report on all the things learned while working on this project.

Literature Research

Looking back at the problem where last few years multiple airports were forced to cancel hundreds or thousands of flights affecting many travellers due to sightings of UAVs at airports. Not only does this negatively affect the passengers but this also costs the airports itself enormous amounts of money. However, from our literature research and interviews with multiple (Dutch) airports, we have learned that many airports have nothing in place to quickly deal with these UAV sightings, let alone have something in place against potential attacks with (weaponised) UAVs. Since we see the increase in the number of consumer UAVs growing each year, this problem seems to become more and more critical. Furthermore, from the interviews, we know that many of these airports without any defences would like to invest in a solution against unwanted UAV presence.

There are many different potential types of solutions against UAVs at airports that can detect, identify/classify, track or neutralise unwanted UAVs. There already even exist multiple concrete systems created by many different companies using a variety of technologies that could be invested in and deployed at these airports. However, the problem is that there are multiple differences between each of the solutions, and finding the best solutions for your airport is extremely difficult. This is where our research and decision model comes into play. We have thoroughly researched many of these solutions and systems as well as many different airports and types of airports in the Netherlands. After researching the differences between all of these systems, the differences between all of the airports and the wants of the stakeholders of the airports, we have come up with a list of attributes of the solutions which are to be to create a decision model.

Decision Model

We have brainstormed and researched many different types of decision models, and found a voting advice application (VAA) such as the Dutch Stemwijzer, to most closely represent the model we would like to create. Where, instead of advising on political parties by using statements based on issues, we give advice on the best anti-UAV system for your airport based on propositions based on attributes of anti-UAV systems and the airport itself. For setting up these propositions, we used the attributes found in the literature research, to create an enormous table of solutions against the attributes. Then, we formed the propositions for the decision model based on the differences between the attributes of the solutions. In the decision model, we wanted to give the users of the model (airports) some freedom to indicate on attributes that they might find more interesting, or indicate attributes that the solution must necessarily have. Hence we also give the users both of these options. Furthermore, we give the users the option to decide on whether to be advice on detection only solutions, neutralisation only solutions or both. We feel like, with all of these features combined with the exhaustive research and validation of the model, the decision model is a useful anti-UAV decision tool for airports.

To make the decision model more tangible, more accessible to test, we decided to create a web-based application to implement the decision model. This decision model web-app asks the user all of the propositions, where more important attributes and must-haves can be indicated and calculates a score for each of the solutions based on the answers of the user. These scores then indicate which solution fits best with the airport and for the convenience of the user also the percentage of how well a solution matches with the airport is indicated. Lastly, the user can also find descriptions of the advanced solutions on the web-app. For the next couple of weeks, this web-app will be hosted online on the website: https://drones.jortdebokx.nl/.

Presentation

The project has been wrapped in a presentation, which can be viewed here.


Back to the root page.