Project WaveSmart, efficient, fluent driving

Project InformationEindhoven University of TechnologyBachelor College Major Industrial Design

DPB100 Project 1 DesignSmart and the City2017/2018, Semester B

Project Coaches:S.I. Lucas

T.J. Elfferich

Student InformationMathias Verheijden - 1234306Marnix van Wijland - 0904697

Dion Tjokroatmo - 1234410 Bas Heuvelmans -1265245

2

IndexIntroduction 3Project Goal 3Project Process 3Ideation 4Pressure Cooker 4Conceptualization 4Prototyping I 5Midterm Demo Day 5Redesign 6Presentation 9Prototyping II 9Business Plan 12Final Demo Day 14Overall Results 16Conclusion 16Appendix A - Reflections 17Appendix B - Extra Material 24Appendix C - Individual Contribution 30Appendix D - References 31

3

Introduction

Project Goal

Project Process

The cars we drive are getting smarter everyday. Our infrastructure, however, has been the same for quite some years now. Cars are meant to take us from A to B as fast as possible, but unnecessary traffic jams slow us down. How can we change that?

The data revolution is in full swing. The transition between manual and autonomous systems is visible in every aspect of our life and our society. Self-driving cars are on the brink of taking over. These cars can communicate with each other, optimizing their routes and speeds accordingly. The innovations seem to be endless, but our infrastructure seems to be years behind on this technological development. Proj-ect: Wave lets our cars communicate our cars with our infrastructure. This opens a whole new range of possibilities. Computers can analyze data about every car’s position, speed and destination and make sure users arrive at traffic lights when they are green.

This system provides a more efficient journey, not only focussing on saving fuel and reducing emissions, but especially focussing on ensuring a more pleasant and fluid driving experience.

The goal of project Wave is to decrease traffic congestion, make people’s journeys by car more efficient and pleasant, facilitate a seamless transition from non-auton-omous to self-driving cars, and create a better collaboration between traffic and infrastructure.

This project started off very fast with a pressure cooker. For this, we came up with the original Wave concept very fast. Through the ideation and conceptualization iterations a first prototype was formed within the first two weeks. Because of this there was too much focus on this first initial idea. This prevented the group from considering other applications.

During the midterm demo day, we received a lot of feedback on our first prototype and concept. This made us do a step back, and reflect back on our own work. This reflection allowed us to also consider other applications which turned out to be more feasible and realistic. The change of application also changed the vision of the project.

A new prototype was developed, which was meant to illustrate to function of the concept. Finally, a business plan was written to take some long term factors into account and improve the feasibility of the concept.

4

Ideation

Conceptualization

Pressure Cooker

The first widening brainstorms included a very broad range of ideas, ranging from sewage & waste management to smart lighting and use of empty buildings. We settled on traffic quite soon, because traffic flow is a crucial element of a well-func-tioning smart city. We had many ideas within the scope of logistics about public transport, solar cars, ingenious charging poles for electric cars, and so on. We soon realized however, traffic is mostly controlled by traffic lights in cities. Therefore, the rest of the ideation process was dedicated to generating ideas for integrating traffic and infrastructure with each other.

After the goals and the ideation were done it was time for us to come up with a more specific thing we wanted to make. Combining the transport and traffic subject, and integration of autonomous cars, resulted in a concept of removing the traffic jams from now to the time where autonomous vehicles are being used. Having a device which let todays cars and cars from the future communicate and solve the traffic problem would be a great thing to have in the future.

The pressure cooker gave us a great head start at ideation and conceptualization. Being forced to quickly come up with multiple ideas is a good way of generating concepts. Ideas developed during all stages of the process. We tried a few different ways of brainstorming but we kept coming back to the idea of transport and traffic. We realized that optimizing traffic flow and efficiency is crucial to a functioning smart city. It was also inspiring to see what the other groups came up with, and that there is a large difference in our takes on the concept of a smart city.

The initial idea was to communicate information about the traffic lights to the cars, so they can opti-mize their speed. Later, we realized that we should optimize the traffic lights instead, based on data from the cars. The prototype from the pressure cooker used an ultrasound sensor to measure the distance from the traffic light to an approaching car. When the car reached the light, it would turn green. This was a way to visualize how we think cars and traffic lights should interact, to create a steady flow and prevent congestion.

Image 1 - Building Pressure Cooker

Image 2 - Very Lo Fi sketch of the Green Wave Principle

5

Prototyping I

Midterm Demo Day

The prototype for the pressure cooker was a lot of fun to build, and it worked well at our presentation. With a simple distance sensor and an arduino, we could transfer our idea well. Building this contraption together with the four of us also created a good way to get to know each other, and get a feel for what everyone’s role within the team could be.

For the actual project, a new prototype was developed. The shape and specific function of this device evolved with our concept. Building the prototype for the Wave Go, we wanted to create a unique yet intuitive interaction experience. To proceed, we made a first sketch of our physical prototype. Although it was the first idea, it fitted the concept very well. Therefore, we decided it was that sketch we would use to make our prototype. Next to our physical prototype, we made some 3D renders to illustrate how a potential final product would look. Especially with the midterm Demo Day in mind, we wanted to build something to hold and feel, to be able to convey the concept.

The midterm demo day went very well. The presentation table looked clean and organized and we had a clear explanation of our concept. The audience reacted very well to the concept, but because of our very technical way of pitching, several people were confused and weren’t convinced that it would actually work. One major takeaway from the midterm demo day was that we should also consider different ways of implementing the concept in cars instead of the screen we already had. Several suggestions were made, varying from light effects to sounds effects and haptic feedback in the steering wheel. This made us realize that we had focussed too much on our initial prototype.

Secondly, for the midterm demo day, we did not focus on the business aspect of our concept. We decided that this was something that needed some attention for the final demo day. A good business plan does not only contribute to the project itself, but it also helps with explaining and convincing the concept to potential buyers, and of course demo day visitors. It gives the project a sense of feasibility that it would otherwise lack.

Image 3 - Development First Prototype

6

The most important thing that we learned from the midterm demo day was that it is good to take a step back from a design process and reflect upon the work done until that point. Looking at a project as an assessor, helps to find flaws and faults in a design. This reflective process massively changed the vision of our project. Initially the focus of project Wave was to travel from A to B as fast as possible. After some second thoughts however, we discovered that Wave would not actually enable us-ers to travel faster. Therefore, the vision of the concept changed to ensuring a more relaxed and fluent driving experience. This reflective process also made the group realize that the concept had some environmental aspects as well, which could be used as selling points for the project.

All in all, the midterm demo day shifted our project into a reflective transformative design process. This development was not only important for the project itself, but it also carried a huge learning curve for all team members. It taught us the importance of reflecting upon your own work and stepping outside the project for a moment, enabling you to see aspects that would otherwise be overlooked.

RedesignNow we are focussing on how to communicate the service and the tranquility to the user we have decided to look at the different senses, since that is the first thing how you perceive something. So the senses are seeing, hearing, sensing, smelling and tasting. Smelling and tasting are senses which are not that easily accessible since you need the user to smell or eat something, which is unhandy when it comes to driving. While we look at the other three senses: seeing, hearing and sensing, we see that these are more accessible since most companies are working with, for ex-ample, light, sound and vibration, such as your smartphone. Below you see a list of the different senses and their possible ways to communicate with the user.

Seeing, this could blind the driver but is the most subtle way to translate tranquil-ity. If we make the light not too bright it might work. Examples are light, screens or movement.

Hearing, this could cause irritation by the driver but the driver can focus on the road. Most of the time these sounds are associated with alarms and such, things which will increase the stress level instead of decrease it. Examples are buzzing, ringing, beeping and voice commands.

Sensing, this could be a distraction while driving but the driver can focus on the road. Your phone for example, when you get a message you immediately notice it and are distracted for a second, something you do not want while driving. Examples are vibration, temperature, shock, tickling, air flow.

Smelling and tasting. These two are quite irrelevant however.

These different way of communicating the tranquility with the user we have to look at differences in color, temperature and sound. This way we can send different mes-sages to the user. Below you see a list of different contrast regarding to the 3 senses we are focussing on.

7

Color, which could be color against color (e.g. red and blue), light against dark, warm against cold color, complementary colors, brightness and transparancy.

Temperature, warm and cold obviously.

Sound, which could be pitch, volume and frequency.

Using calm colors (blue or green) against chaotic (red) colors to emphasize the tran-quility and the turmoil, so people want to keep the tranquility and drive at the correct speed. On the other hand the lights must not be distracting, so the brightness has to be low and the transparency has to be high since you still have to focus on the road. As said before, sound will be distracting since it sounds as an alarm most of the time, or, if there are silences in between the signals, the communication will be unclear since you have to wait for the next signal and you do not have the info you want immediately. Temperature can be very unpleasant since you do not want your car to become hot or cold all of a sudden, and you only have two states, hot and cold, to communicate with the user.

We thought light is one of the most suitable for your design, both vibration and sound will cause large distraction or frustration. For example an alarm which rings is kind of annoying. Another thing, a sound is usually used when you received a mes-sage or, in a car, while driving backwards. People will use those sort of knowledge and associate the sounds with them, and not with the function we wanted it to have. If you would use a human voice which says how far you are from the wave it would be unclear since it not says where you are all the time. And when you have some music on, both sounds will sound through each other.

Vibration is associated with getting messages as well. There are massage chairs in some cars, but when we want to use vibration in your system we need some sort of periodic pattern where you can control the frequency. But it is annoying when your chair is constantly vibrating.

Image 4 - Lo-fi Redesign Sketching

8

The blue dot on the screen is the car respectively to the “green wave”. The more you approach the wave (the green part) the more the dot moves to the right or the left, depending if you are in front or behind the wave. This way you see if you are in the wave, and if you are in front or be-hind it. This concept can be integrated in your steering wheel as well, but this could be a bit distracting when you, for example, make a turn since you have to focus on the dot some more

This design is some more abstract. The light on your front window represents the position you are at. It is a gradient which goes from red-orange-green, when you are in the wave it is green and the more you approach the wave it changes red/orange in a smooth way. This way you have a clear view at where you are at, a downside is, you do not know immediately if you are in front of behind the wave. Another thing is, having your “whole” front window lit can be distracting while driving.

This concept can be integrated in your dashboard together with your meters to make is less distracting, but then again, you do not know if you are in front or behind the wave.

Our user evaluations show that people like to have a app so you do not have a whole new navigation device. But we want to make a device to have something to hold on to. So to combine this we decided to make the device as small as possible so people do not mind taking it with them, or having it in their car. The device combines both ideas shown above where you have the top interface, but the second way of display-ing it. The HUD would be above the dashboard so it does not take your whole front window. This way we can integrate the users demands in our two main ideas of displaying the concept. After doing some user interviews, introducing the different ways of implementation, the Heads Up Display turned out to be the preferred op-tion, because you would not have to take your eyes of the road and it was the least distracting option.

Image 6 - Window Screen

Image 7 - HUD and Phone Connection

Image 5 - Dash Board Idea

9

Presentation

Prototyping II: HUD

From the start of our project we wanted to explain our project in the greatest detail to make everybody understand our idea as good as possible. However, we have struggled with the way we wanted to explain it. We, as a group, wanted to explain every detail, software wise and system wise, how the product works and how wave functions. By doing this, we got a lot of questions from people about the functional-ity and whether everything works properly. Meaning that people were having ex-treme doubts about the project.

Our new way of presenting focussed more on the main goal of the project; “decreas-ing traffic congestion and making people’s journeys by car more efficient and pleas-ant”. The technological functionality of the concept was not mentioned to the user. Because this pitch purely focussed on the user experience instead of the technol-ogy, we were able to give the audience a feeling of recognition. This made it much easier to convince the audience that our concept would actually work.

As discussed before we used a HUD to display our interface. A HUD starts with a little projector which displays the interface. To have it projected at the right angle there is a mirror on the opposite site of the projector. Next there is a magnifying mirror which inverts and enhances the projection on your front window to make it visible.

For our prototype we recreated a HUD by using a perspex plate with tinted film to make it dark but transparent and an animation which displayed our interface , since it was not feasible to recreate a whole new HUD from scratch. This way people could see what we want to have on our dashboard, and it gives a good indication on how it works with the real HUD. If our device is fully working in the car, the HUD is installed on the inside of the windscreen and a little projector shows the interface.

Image 8 - Implementation Interview

10

Image 9 - HUD Prototyping

Prototyping II: RacetrackSince we decided to focus on the concept instead of a product, we needed to think of a way to demonstrate this. Our project is very technical in nature, so we wanted to incorporate this into the demo. The idea to use a race track to show this was born.

The first prototype consisted of an arduino with a distance sensor and a relay, and the race track. When the distance sensor noticed the faster car, it would turn of the power to that track using the relay. Then, when the wave-car passed in front of the sensor, the other track would be turned on again as well. However, this did not allow us to control the speed of the cars. First, we wanted to use potentiometers to con-trol the current to the cars. When this did not work, we thought of using transistors to control the current to the cars. Pulse-width modulation (PWM) allowed for the transistors to be turned on and off very quickly, to produce pulses of a controllable length. Because this happens many times a second, the result is an average of these pulses of current, and we can control the speed of the cars quite precisely.

The final step to the prototype is the green wave and the traffic light. To produce this, we added a railing with LED-strips to our figure-of-eight track. A green wave would propagate along this strip, next to the wave-car. The speed of this wave is determined by the time the whole array would stay at each LED. It was quite a chal-lenge to get this to correctly and precisely follow the wave-car. First, the system would calculate the round time and base the speed on this. However, due to com-ponent failure, this was not implemented in the final design. The speed was con-trolled using a potentiometer, so we could manually match the wave speed to the speed of the cars. To prevent the wave and the car getting out of phase, the wave resets to the starting point every time the car passed the sensor. Every time the car passed this sensor, the light would turn green and both cars could continue.

To bring this together into a presentable, neat demo, we built the race track, the HUD, the poster and the laptop with the video onto a big board.

11Image 10 - Racetrack Prototyping

12

Business PlanMarket and User SegmentFor Project: Wave to work, it needs 4 main sets of data; traffic light data, speed, location and destination. The final one, destination, means some sort of navigation should be part of Wave’s system. If Wave would release it’s standalone navigation system, users will most likely stay with the navigation systems of other, bigger com-panies like google and apple, because of their loyalty to those brands over the years (Roger Hallowell, 1996). Both Google’s and Apple’s navigation apps, are ranked in the top 20 most used apps at respectively number 5 and number 14. Google’s app in particular, has almost a hundred and two million monthly users. If we add Apple’s users on top, we reach an astonishing 154 million monthly users (Statista, 2018), a number that Wave would most likely never reach alone.

Next to navigation apps, car manufacturers also include navigation systems in their cars. Since the amount of cars with such a system is constantly increasing, it would make sense for Wave to also work together with the major car manufacturers. Be-sides, since wave is a startup with almost no resources, it is nearly impossible to compete with multi-billion companies that already have huge customer bases.

Finally, Uber is currently developing self driving software for its cars (Uber, n.d.). This is an opportunity for Project Wave to potentially introduce our concept to their development. We will elaborate more on this in the feasibility part of this document.Since there are a lot of com panies to work with, the best way of introducing Wave to the market is by turning the concept into a licence that can be sold to app developers, car manufacturers and even companies like TomTom.

To conclude; the market and user segment, or target group, of Wave, will be those who use already existing navigation services for cars.

Innovative aspects and selling pointsOur vehicles and road users are being improved every year and more and more technologies are being introduced. However, our infrastructure has been here for a very long time now. This is something that has to be improved. You can’t improve one thing and leave the other unchanged. That is why we want to combine modern day car technologies with the infrastructure that there already is. By collecting the data from traffic lights, we can see when they are green and red which helps us to create a route using the navigation system already present in a car. By doing this, we can combine modern day car technologies with the outdated infrastructure to create a personal green wave that will let you drive as relaxed as possible. The combining of infrastructure with modern day car technologies makes project wave very innovative and a major selling point.

For project wave to stay interesting and sellable on the modern day market it has to contain some innovative aspects. One current-day innovation is the Heads Up Display (HUD) in vehicles. A HUD is a transparent form of display that shows infor-mation/data enables the user to keep vision on their viewpoint. HUD was actually first used in military radar systems in 1960 (“Head-up display”, 2018) but is now recently being used in cars to display navigation routes, speed limits and other car specifications. Project Wave will use a heads up display to make the user aware of their personal green wave and where it is without distracting them from the road or without making it an extra application within the car.

13

Technical RoadmapAccording to (Jeong & Yoon, 2015) patent planning is an important step to make ‘because well-planned patents make larger profits and occupy dominant positions first’. What to consider however when deciding when to file your patent? (Jeong & amp; Yoon, 2015) suggest to look at a technology roadmap and patterns of patent development. Their approach is quite comprehensive in the sense that they first look at relevant technology roadmaps from products in the same market to gather relevant characteristics. Based on this they gather patents which are then analysed in distinctive groups to gather patterns. These patterns are then used to decide the best time to file the patent. Since we do not have the time to over this same process, we need to determine the optimal time ourselves.

If we were to actually release project Wave to the market, we would sell the concept as a license to other companies as said before. Because of this, we want to start marketing for this before the actual release date. To prevent the concept from being copied, it makes sense to file the necessary patents as early as possible in the de-sign process.

FeasibilityProject wave is an idea that is very innovative and new, it combines modern day car systems with the already existing traffic light system which means that hardly any modifications city wise have to be made. Next to that, people already are familiar with the green wave principle, modern day cars and traffic light system, which com-forts the users which makes them more tempted to use our product and makes them able to use it more quickly and effectively.

As described, when looking at feasibility, our product finds it strength due to the fact that it is easy to use because of the adaptation to already existing systems. Addi-tionally, project wave can be implemented in autonomous vehicles as well. Cars that are autonomous can follow their own personal wave without the control of a driver. Autonomous vehicles have been made in such a way that nowadays, they can read traffic lights and see whether a traffic light is green or red. For non-autonomous vehicles, cars are connected to the traffic lights via the cloud which then generates a display of the personal green wave of that car. For autonomous vehicles, this exist-ing cloud can be connected to the software of the car which then can adjust its own speed to make every green light and therefore have the same effect, without need-ing the extra user interface. Because of this our product will stay useful and helpful in the future as well, where more and more autonomous vehicles will be present.

Project wave is an improvement to the already existing green wave principle due to the personal wave that project wave has. Already existing green wave systems are mostly on roads that have multiple traffic lights in a relatively short pieces of road. When a car travels with a consistent speed in these green waves, because of the fixed time a traffic light turns red or green, a car will make every green light on that piece of road. Project wave is an improvement of this because project wave can already see beforehand if a traffic light is red or green and when it becomes red or green. Because of this ability of project wave, every road becomes a green wave that makes the experience of making every green light last longer.

Our product finds it weaknesses in the realisation of the big data that is being re-ceived. For project wave to be able to gather and save all the data that is being re-ceived from the traffic light and then being transmitted to all the cars, project wave is going to need a very big data storage facility.

14

One problem however, is that project wave simply does not, right now, have the financial capacity to host such a big data storage facility. All the data from each traffic light is already being gathered, just like the data of navigation systems that is needed to generate the required speed of the car to make all the green lights on that route. Because of the already present data, project wave has to find a way to cooperate with companies that host all of this data to make it able to work properly.

Most people who find out about our concept question whether project wave makes you arrive at your destination faster. However this is not our intention. We try to make travel by car more relaxed and comfortable instead of faster which is some-thing that most users we interviewed struggle with to see.

As mentioned before, project wave can be very easily adapted to autonomous cars and this opens up some opportunities. For example, some very big influencers in the autonomous car business could be interested in implementing project wave already during the production process of the cars instead of an app that can be implemented later on. A company that could be very much interested is Uber. Uber is busy using its own software on non-autonomous vehicles to make them drive autonomously (Uber, n.d.). This could come in very handy for us as well because the user of the uber can experience what it feels like to make every green traffic light and might therefore be interested in investing it for himself. Next to that, Uber still is a growing company that has a lot of competition within the taxi world and project wave could be something that separates them from the others.

As described as a weakness, we simply do not have all the resources needed to completely support our idea. The only thing lacking is the data storage. This could turn into a weakness when looking for stakeholders to invest in our product. We only have a concept and no resources to realize that concept. Another weakness could be that people misunderstand our idea and therefore buy it in order to get at the location faster which would lead to some major problems. To prevent this we need to emphasize that our project is meant to make your travel more relaxed in-stead of faster.

Final Demo DayFor demo day, we prepared a few different demos. We want to convey the idea in different ways. We already established that people don’t like to drive slower than they want to. To show that driving in your green wave is just as fast, we built a fully autonomous miniature track. One of the cars is driving around at a constant speed, following the green zone as indicated by the LEDs. The other car constantly has to stop at the traffic lights. The ‘green’ car arrives exactly when the traffic light turns green, and can constantly catch up with the faster car. This system used vintage race track toys to create something unique and eye-catching. Since we settled on a HUD to display the green zone, we made one for demo day as well. Displaying the animation on a phone, with a piece of plexiglass to reflect the animation, just like the way it would be built into the windscreen of a car.

Next to the two main demonstrations, the track and the HUD, we presented the idea on a poster and a video. This combined into a neat, attractive booth that drew plenty of attention and, together with our pitch, this made sure that everyone understood the concept well.

15

Image 11 - Final Demo Day

16

Overall Results

Conclusion

The final result of our project is not a product, but a concept. Project Wave is a sys-tem that tackles multiple problems related to driving. It aims to ease traffic conges-tion, and as a result it has many benefits for the environment and for driving times and comfort. All of the economy can benefit from shorter, more efficient transport of people and goods as well.

CongestionAt its roots, our system aims to decrease traffic congestion. By optimizing traffic lights, car speeds and routes, the traffic flow can be improved. Congestion is the main source of many transport-related problems, so decreasing it has many positive consequences.

Environmental benefitsProject Wave ensures less cars running idly at intersections, and shortens travel duration. This means less fuel burnt, and less pollution contaminating the air.

Fluent transition to self-driving carsSelf-driving cars can communicate with each other, using all this data to optimize their driving. Adding the data from non-autonomous vehicles to this network will greatly improve its efficiency. By knowing much more about its fellow road users, the self-driving cars can plan much better. This way, a future of fully autonomous vehicles can be eased in smoothly.

Driving experienceMost noticeable to the user, and the main focus of this particular project: the driving experience. The driver can see the green wave indicator in the heads-up display, without having to look away or being distracted by lights, sound or other sensorial input. As long as the driver follows their own green wave, they will have to stop and accelerate again very little, which massively improves the traveling experience.

The project goal was to tackle traffic congestion by making use of all the data that is already available. We developed a concept that can optimize traffic flow, which has many benefits.

Developing this concept following the reflective-transformative design process made us aware of some more consequences of the idea than we initially thought. These are all by-products of the original project goal. As mentioned in results, de-creasing congestion has positive influences on pollution and air quality, the driving experience, the economy and makes for a better transition to a world of self-driving cars.

Comparing our goals with out final outcome, we are convinced we can say that if we would release project Wave into the maket, it would not only reach our goals, but ex-ceed them. Wave not only saturates the goals we set like reducing stress in the car, help transitioning from normal to autonomous cars and reduce traffic congestions, but also helps with environmental problems. In short, we are convinced that project Wave was a succes.

17

Appendix AReflection Mathias Verheijden

Project 1 Design has been very valuable for me. Not only have I learned a lot in the perspective of a designer, but also have I learned about professional skills like meet-ing, organizing and planning.

The start of the project was quite rough. From the very beginning, we have had the problem that our meetings were not very effective. A lot of time was wasted and we didn’t have any clear goals. This resulted in a somewhat stressful environment. This was due to the fact that we came up with an initial concept very fast, which caused us to get stuck after a few weeks.After some time, I suggested we would do a meeting dedicated to discussing the group work. After this meeting, the productivity of the group hugely increased. We started making a planning, a clear task divisions and the overall communication improved For me, this is a valuable lesson for future projects. It taught me to take a step back and made me realize that the chemistry of the group is just as important as the project itself. Something that I will definitely pay attention to in future projects.

Project 1 Design has also contributed to my development within the Industrial De-sign competencies. For the initial prototype, I made sketches and 3D renders of our model. This was something I had never done before, but I find these skills to be very useful in a design process, because they allow you to communicate a design very easily. To further develop these skills, I’m planning to take the ‘Exploratory Sketch-ing’ course next year. Within the creativity and aesthetics competency I have also done all visual work for the project; the posters, logo, explanation video, explanation animation, HUD animation and report. This hugely contributed to my development within this competency.

The prototyping part of Project 1 Design was quite unfamiliar for me. It was one of the first times for me that I did some physical prototyping in the Vertigo workshop. At first I was not very confident in this area, but because of Project 1 Design, I now have much more confidence in translating my designs into actual physical forms. I have learned quite some new techniques, which allow me to prototype more com-plicated concepts for future projects. Next to the physical prototyping, I also assist-ed Marnix, who did most of the work in this area, with the coding for our prototype. This is something I had quite some experience in already, but working together with him taught me some important new concepts which I can use for future projects. This process did not only teach me the coding itself, but it also taught me that you can learn quite a lot from each other during a project. Therefore, during my future projects, I want to work together with experienced people in areas that are unfamil-iar for me to gain new experiences.

During my first year of Industrial Design, I have chosen two business electives. These came in really handy when making the business plan for project Wave. To-gether with Bas, I wrote the entire business plan for the concept. The major differ-ence between the two business electives and Project 1 Design was the purpose of the business plan. For the electives, I needed to make a business plan for an already existing company. For project wave, we had to start from scratch. This was a very useful experience for me since I could now combine all my prior knowledge for this project. Project Wave did not teach me a lot about the business skills themselves, but mostly about the importance of the business plan itself.

18

For this project, we made the business plan rather late. While writing however, I noticed that when the plan would have been written earlier, some important things could be taken into account during the design process. I now realize, that the way a concept will be sold or promoted, also influences how something is designed. Therefore, in the future, I will will probably write the (draft) business plan after the first concrete version of the concept, which will also contribute to having a reflective transformative design process.

To conclude, I have learned a lot from this project. I have learned new skills, gained experience in both the design process and professional skills. I think for me per-sonally there are two major takeaways from this project. First of all, in the end, the project came together in a very good way, and I think we the result was very nice and structured. However, the beginning and end of the project were very stressed, because, especially in the beginning, the was a lack of structure and planning. So the first takeaway is that the chemistry of the group is just as important as the proj-ect itself. Something that I will definitely pay attention to in future projects. Secondly, this project has especially taught me the importance of having a reflective transfor-mative design process. To take some distance and review the concept as an outsid-er. If this is not done, some very important factors or alternatives can be overlooked. Overall, I worked really hard on this project and put a lot of effort into it. I feel like that really payed off. This project definitely confirms that I have made the right study choice and it motivates me for the next two years!

19

Reflection Marnix van Wijland

Design & research processAfter Midterm demo day, we realized that it was time to get everything together. We had a concept, but it was not quite solid yet. We decided to focus on the business aspects, as well as the interface aspect. We decided to develop the concept and license this to companies that already have access to devices and data. Therefore, we had to come up with a way to demonstrate this, without the option to produce a physical product. I think we worked according to the RTDP quite well.

Group work – organization, communication and planningAs stated, the midterm demo day woke us up. Our meetings became more efficient, and we divided the work. Bas and Mathias would focus more on the business as-pect, and Dion and myself were going to work on the user interface. The big ques-tion here was: how do we motivate people to drive slower than the speed limit?When I had the idea to use my dad’s old toy race track for demo day, it became clear that this would be mostly my thing. I love to use this vintage technology (made in Western Germany even) and manipulate it with Arduino and electronics. My dad was very happy as well, he helped me out a lot with this. He is so happy that I finally found the study that suits me, and he would have loved to study ID as well. When I have a clear idea about how I want to make something, it can be hard to work with others, since I can get into a huge hyperfocus. The rest didn’t mind this though; they trusted in my idea, and they helped me whenever necessary.

Demo dayI think I experienced one of the more extreme demo day low-high’s. Every ID student has demo day stress of course, but I hope that this was somewhat of an exception. We had all the different bits for demo day, but it still had to come together. We start-ed working in vertigo at 8. I had written a lot of code which I couldn’t test at home, because our setup was in vertigo. I spent a few hours fixing the electronics and code. Around 2, I managed to fry my Arduino, my laptop and half of the electronic circuit in one jolt. Luckily, we had the (old) code on google drive, and Mathias had some spare transistors. In about an hour, Mathias and I re-wrote the code, and rede-signed the circuit. I have never had such a hyper focus and work flow as this day. My fried laptop motivated me even more to work hard for our demo.

In the end, I dare say we had quite an eye-catching demo. It worked well and demon-strated the concept clearly. I don’t regularly dare say these things about myself; but I think we really stood out. I have never been so relieved that it all came together. My dad came to see it as well, and he was very proud of our demo with his ancient race track.Because of the extremely hectic situation, we couldn’t finish our second demo. This would have been extra nice, but no one knew, and it was definitely not missed. We had plenty going on at our table, with the race track, the HUD, the video and the poster. After the demo, we decided to go out for dinner and see a movie. This was a great way to end the demo day.

Competency areas – my contribution and role in the teamBecause the project was quite ambitious with programming and electronics, I main-ly focused on the more technical aspects. These included: Doing the programming and electronics for the pressure cooker and demo day. Programming the Arduino with sensors, using transistors to control the speed of the cars, and controlling the LED strips and the traffic light. I love how I could use different concepts from math and physics, and combine them into this working, completely autonomous demo.

20

I also did quite a lot of the physical building and woodworking. I made the prototype for midterm demo day, and I built parts of our final demo. I developed a lot within the Technology & Realization and Math, Data & Computing competency areas.I tried to make the midterm demo look nice, with the product and the poster stand. I also made some concept visualisations of the HUD. The graphic design is mostly Mathias’ thing however. He loves to do it and he is good at it. By watching him and asking him questions when I was working myself, I could develop my Creativity & Aesthetics competency.

Summary – what did I learnThe biggest takeaway from this project is still about group dynamics and planning. In the end it came together, but we could have avoided a lot of stress by being more productive throughout the project. Still, this is something every student struggles with. For next time, I want to take more of an organizational role in the project. I could learn a great deal from this and it will also be beneficial to the project.I also gained a lot of self-confidence, and proved something important to myself. My teachers from elementary- and middle school always said: when Marnix really gets to work, he can achieve things. For one of the first times in my life, I actually worked really hard for my study, to accomplish what I wanted, and it really paid off. This proj-ect feels as a turning point in my view of studying and gaining motivation.

21

Reflection Bas Heuvelmans

My overall experience for project 1 has been really amazing and I can say with con-fidence that because of project 1, I definitely know that Industrial Design is the right bachelor program for me. This partly has to do with my team members which were really great and the vibe within the group was really amazing. But this also has to do with the fact that doing these projects, and working together in a group on such a project is really something that fits me.

After our midterm demo day we really sat down and reflected for ourselves what was lacking and what we could improve. What we figured during the midterm demo day, was that we already had a very fixed idea from pretty much the start and this meant that we should explore more visual options and areas to make our product better and to make it more innovative. We also figured that the base or research was lacking. However from the feedback we got, we realized that we should more fo-cus on the business aspect of our project instead of doing more research. Because of the feedback and reflections from the demo day, we divided our group in two. Mathias and I did the business part and Marnix and Dion covered the new user inter-face to make our product more innovative. I think that it was a really good choice to divide the group in 2 because this lead to some more individual responsibility. From the beginning of project 1 we did almost everything together and I think splitting up lead to better coordination and structure in the group which made us able to focus better and work more effectively.

My goals for past quartile were: trying to improve my adobe skills and trying to improve my programming skills. The first one, trying to improve my adobe skills, is something that I have tried to do this quartile, I made some design ideas for the mid-term poster and some visuals for on that poster. However, Mathias, in our group, is a web-designer whose job it is to make posters and visuals and things. Therefore, we, as a group decided that it would be better if Mathias did the visuals because he was way better in it. However, in the future, and for project 2, I want to try and improve my web-design skills and take them to a higher level. My other goal, improving my programming skills, kind of has the same story. Marnix in our group is an experi-enced arduino programmer and had way more skills in that than I did and therefore we decided to mostly let him do the programming.

I have improved my competencies a lot as well past semester with project 1. Of course I improved creativity and aesthetics. I have improved this by making a lot of prototypes and sketches. Most of the creativity and aesthetics was improved by making the final demo day materials and pressure cooker materials. These things made me more aware of the effort it takes to make demo day props but also how much fun I think it is. For the competency business and entrepreneurship I made some major improvements as well. Before project 1, I followed the course Introduc-tion to business design which taught me a lot about the importance of business within a design case and how to implement it. With this knowledge, I together with Mathias, made a business plan to support project wave and to show its plans and goals for the future which was really interesting to do and which was an addition to the report. I thought this was really helpful because a business plan shows you future goals and shows why your product should survive on the modern day market, which really is an important aspect. For the user and society competency, I made some improvements because we did some user interviews to improve our visuals of the project and gain some more feedback.

22

Even though we only didn’t do a lot of user based designing, we still gained some really useful and helpful feedback and information from these user tests which helped us to make our product more user friendly.

In conclusion, project 1 has been a really great experience for me. I really improved myself as a designer but also as a student. I improved my planning, my structured working and my group skills. As a designer I improved 3 out of the 5 competency areas which will really help me in future projects and courses. The only thing that I want to do more next projects, is working on my goals since that has been lacking. However, overall, I am really happy with the result that we achieved as a group and I am really happy with what we were able to present at the final demo day. Look-ing back, project 1 is something that will help me with all my future design work throughout my bachelor program of Industrial Design.

23

Reflection Dion Tjokroatmo

I can certainly say we have made a lot of improvement from the midterm. Before the midterm we struggled a bit with planning and meeting sessions, but after the mid-term demo day we realised we had to step up our game to have a solid prototype during the final demo day. The midterm demo day was a bit of an eye-opener since we discovered some flaws in our concept and the ideas everyone had regarding it. After this we sat together to discuss our idea and made sure everyone was on the same frequency.

We made a list of things we wanted to have during the demo day and divided the four of us in groups of two, since we noticed we distract each other when we are all together. Mathias sand Bas did the business plan because they had had two busi-ness courses in their curriculum, and Marnix and I did the user interface and inter-action of our device since I like to focus on the user during a design process. Both duo’s delivered a detailed description of the business plan and the user interface and interaction.

During this project I tried whatever I could and leave the people who did their thing. For example with the coding part, I think it is interesting to see how it works, but I have no clue how it works. This prevented me from helping and I just worked on things which were familiar to me since I thought I would hinder my teammates.

Regarding my goals this was a useful project as well, I worked on all of my three goals during this process. Since we had some more time and freedom to do what-ever we want we spend the last couple of weeks working on our final prototype, this consisted of sketching the interface and building the demo day stand. I first started sketching my ideas and interfaces on paper, but decided to work them out on Pho-toshop. It looked kind of crappy since this was the first time I touched the program, but with some help of tutorials and my group members I managed to digitally sketch out my ideas.

The prototype consists of coding, a case of the wiring and a frame for the LED-strips. I helped working on the frame and the case, so executing the sketches and ideas which were made beforehand. I thought everything was decent looking, but there are some minor details which could have been improved if there was some more time. Coding was something I was not really into, but I think it is handy to be able to code. Seeing a new possibility of what an Arduino can do motivates and inspires me to learn to code.

My last goal, presenting, is something I worked on as well. Pitching your project gave me a good insight of how I present and things I can improve. During the mid-term demo day I presented our idea to someone in dutch, this gave me some more confidence and went pretty well since it was in my native language. The thing is, I know what I want to tell the people, but I am too afraid I fail in front of “important” people. When I had to present during the final demo day I mostly explained your idea and prototype to friends and random students who came by, both in english and dutch. This again was a small accomplishment and I did not feel the nerves that bad while presenting.

24

Appendix BUser InterviewWhat do you think of our idea?How would you implement it in your daily life?How would you think something like this would look like? (shape, screen etc.)Would you use something like this?Would you like to see something like this in combination with your smartphone?Where would you use something like this? (car, bike, on foot etc.)Would it be nice/relevant to link it to other devices?Would you like to see it as a portable device? Or integrated in a vehicle?Have you got any additions to your existing idea to make it more versatile?

Answers (Examples)User 1At first sight it is not practical do have a device which says you have to slow down, I can get used to it but it is not something natural to do. But I understand the concept and it perhaps would work in a car or other driving vehicle, since you can adjust the speed easier than on foot for example. Another thing is, I mostly use the car and cannot really imagine using it on a bike or on foot because you have to make a big-ger effort to move at the right speed.

Designwise I would make it as small and mobile as possible so I do not have to carry an extra device with me. For example integrated in a smartwatch or as an app on your mobile phone, something what you carry (almost) all the time with you. As I said, it would probably only work in a car, so combine it with the existing dashboard meters would be something interesting. Nowadays everything has a touchscreen but if you add another screen in your car it would distract a lot and takes in a lot of space, you do not need a touchscreen if you only focus on the main function of the device, buttons or something would do the trick.

User 2I am a bit sceptic since it is hard to control every car, especially when there are a lot of cars and each of them has a different velocity. Applying it to other common means of transport, such as bikes or just walking, is a bit awkward since you influ-ence the speed yourself. Adjusting the speed is way harder and impractical than when you are driving a car, and another thing, I do not mind waiting for a little while before crossing the road. Another thing is, you have a change the whole existing infrastructure, which takes a bunch of money and time.

It is important to make it as small as possible, so for example a small box which you can attach on your dashboard or at your steering wheel, just like a clamp to attach your phone or Tomtom to the front window. I think it would be most useful to inte-grate it in the existing dashboard with some sort of chip or in your phone since you always carry it around. Probably involving your phone is something important, for example to store the data or to adjust settings.

25

A4 Midterm Demo Day Handout

“Wav

e G

o”

B1 /

DPB

100

Proj

ect 1

Des

ign

“Sm

art E

ffici

ent D

rivi

ng”

Proj

ect C

oach

es: S

ande

r Luc

as, T

ove

Elffe

rich

Gro

up: 1

3C

Stud

ents

:

M

athi

as V

erhe

ijden

Ba

s Heu

velm

ans

Dio

n Tj

okro

atm

o

Mar

nix

van

Wijl

and

Proj

ect:

WAV

E“P

roje

ct: W

ave”

is a

n in

tera

ctiv

e sy

stem

mea

nt to

opt

imiz

e tr

affic

flow

and

ens

ure

a co

mfo

rtab

le d

rivin

g ex

perie

nce.

Alm

ost

all

traffi

c lig

hts a

re cu

rren

tly ti

me b

ased

. This

mea

ns la

rge a

mou

nts o

f tr

affic a

re oft

en w

aitin

g for

just

a fe

w ca

rs. Th

is cr

eate

s unn

eces

sary

tr

affic j

ams.

Wav

e cr

eate

s a

netw

ork

of c

ars

and

traffi

c lig

hts

by e

ither

usin

g th

e ‘W

ave

Go’

or b

uilt-

in so

ftwar

e in

the

cars

. The

enab

les W

ave

to p

redi

ct w

here

clu

ster

s of t

raffi

c ar

e go

ing.

By

doin

g th

is, it

can

tu

rn tr

affic

light

s gr

een

at th

e op

timal

tim

e. Bu

t wha

t abo

ut th

e ca

rs th

at a

re n

ot in

that

clus

ter?

Wav

e ha

s the

m co

vere

d.Si

nce

wav

e kn

ows

whe

n tr

affic

light

s w

ill b

e gr

een,

it u

ses

the

“gre

en w

ave”

prin

cipl

e fo

r ca

rs o

utsid

e th

e pr

iorit

ized

clu

ster

s. Th

is m

eans

Wav

e sho

ws u

sers

whe

re to

driv

e in

orde

r to

arriv

e at

the

inte

rsec

tion

whe

n th

e lig

ht is

gre

en.

26

A3 Midterm Demo Day Poster

“Wav

e G

o”

“Pro

ject

: Wav

e” is

an

inte

ract

ive

syst

em m

ean

t to

op

tim

ize

traf

fic fl

ow

an

d

ensu

re a

co

mfo

rtab

le d

rivi

ng

exp

erie

nce

. Alm

ost

all

traf

fic li

gh

ts a

re c

ur-

ren

tly

tim

e b

ased

. Th

is m

ean

s la

rge

amo

un

ts o

f tr

affic

are

oft

en w

aiti

ng

fo

r ju

st a

few

car

s. T

his

cre

ates

un

nec

essa

ry t

raffi

c ja

ms.

Wav

e cr

eate

s a

net

wo

rk o

f ca

rs a

nd

tra

ffic

ligh

ts b

y ei

ther

usi

ng

th

e ‘W

ave

Go

’ or

bu

ilt-in

so

ftw

are

in t

he

cars

. Th

e en

able

s W

ave

to p

red

ict

wh

ere

clu

ster

s o

f tr

affic

are

go

ing

. By

do

ing

th

is, i

t ca

n t

urn

tra

ffic

ligh

ts

gre

en a

t th

e o

pti

mal

tim

e. B

ut

wh

at a

bo

ut

the

cars

th

at a

re n

ot

in t

hat

cl

ust

er?

Wav

e h

as t

hem

co

vere

d.

Sin

ce w

ave

kno

ws

wh

en t

raffi

c lig

hts

will

be

gre

en, i

t u

ses

the

“gre

en

wav

e” p

rin

cip

le fo

r ca

rs o

uts

ide

the

pri

ori

tize

d c

lust

ers.

Th

is m

ean

s W

ave

sho

ws

use

rs w

her

e to

dri

ve in

ord

er to

arr

ive

at t

he

inte

rsec

tio

n w

hen

th

e lig

ht

is g

reen

.

PR

OJE

CT

WA

VE

B1

/ D

PB

10

0 P

roje

ct 1

Des

ign

“Sm

art

Effi

cien

t D

rivi

ng

”

PR

OJE

CT

BY

:M

ath

ias

Ver

hei

jden

Bas

Heu

velm

ans

Dio

n T

jokr

oat

mo

Mar

nix

van

Wijl

and

27

A4 Final Demo Day Handout

B1 /

DPB

100

Proj

ect 1

Des

ign

“Sm

art E

ffici

ent D

rivi

ng”

Proj

ect C

oach

es: S

ande

r Luc

as, T

ove

Elffe

rich

Gro

up: 1

3C

Stud

ents

:

M

athi

as V

erhe

ijden

Ba

s Heu

velm

ans

Dio

n Tj

okro

atm

o

Mar

nix

van

Wijl

and

Proj

ect:

WAV

E“P

roje

ct: W

ave”

is a

n in

tera

ctiv

e sy

stem

mea

nt to

opt

imiz

e tr

affic

flow

and

ens

ure

a co

mfo

rtab

le d

rivin

g ex

perie

nce.

Alm

ost

all

traffi

c lig

hts a

re cu

rren

tly ti

me b

ased

. This

mea

ns la

rge a

mou

nts o

f tr

affic a

re oft

en w

aitin

g for

just

a fe

w ca

rs. Th

is cr

eate

s unn

eces

sary

tr

affic j

ams a

nd c

ause

s str

ess w

hile

driv

ing.

By c

ombi

ning

mul

tiple

sor

ts o

f da

ta l

ike

spee

d, l

ocat

ion

and

estim

ated

rout

e, W

ave

can

dete

rmin

e th

e op

timal

spee

d fo

r eac

h in

divi

dual

use

r to

arriv

e at a

n in

ters

ectio

n w

hen

the l

ight

is g

reen

.

This

signi

fican

tly r

educ

es t

he a

mou

nt ‘

stop

s’ w

hen

driv

ing,

re

duci

ng n

ot o

nly

stre

ss in

the c

ar, b

ut a

lso th

e em

issio

ns a

nd th

e fu

el co

nsum

ptio

ns o

f the

car.

Do

you

wan

t to

know

mor

e? A

sk u

s an

ythi

ng!

OUR

Busi

ness

Sinc

e W

ave

is a

conc

ept

with

alm

ost

no r

esou

rces

, it

is ne

arly

impo

ssib

le to

com

pete

with

mul

ti-bi

llion

com

pani

es

that

alre

ady

have

man

y m

ore

cust

omer

s. Th

eref

ore,

the

Wav

e co

ncep

t will

be

sold

to la

rger

com

pani

es a

s a li

cens

e. D

o yo

u w

ant t

o kn

ow th

e de

tails

? Let

us k

now

!

28

A3 Final Demo Day Poster

PROJ

ECT

WAV

E

B1

/ D

PB

10

0 P

roje

ct 1

Des

ign

“Sm

art

Effi

cien

t D

rivi

ng

”

The F

unct

ion

The B

usin

ess

The T

eam

Traf

fic L

igh

t D

ata

+ S

pee

d +

Lo

cati

on

+ R

ou

te =

Gre

en W

ave

We

sell

Pro

ject

: Wav

e to

larg

erco

mp

anie

s w

ith

an

alr

ead

y ex

isti

ng

cu

sto

mer

bas

e.M

ath

ias

Ver

hei

jden

Mar

nix

van

Wijl

and

Bas

Heu

velm

ans

Dio

n T

rjo

kro

atm

o

29

Project: Wave Logos

Project: Wave Video

https://drive.google.com/file/d/1NTMybaYAB5NuRXf-xYjX-rbRsK9cBwiU8/view?usp=sharing

30

Appendix CIndividual Contribution

MarnixProgramming and electronics for final demo day and the pressure cookerBuilding the prototype for midterm demo dayBuilding for the final demoBuilding the poster standCreating concept visuals for the interface in the carWriting part of the user interview and conducting the interviewsIdea generationWriting for midterm and final reports

BasBuilding and painting demo day props (wood)Creating the business modelStarring in the productvideoWriting part of the user interview and conducting the interviewsIdea generationWriting for final reportWriting business plan

MathiasPoster designs (midterm and final A3 and A4 posters)Logo designsVideo design/edit (midterm and final video)Animation design/edit (midterm and final animations)HUD Interface design/animationReport design (midterm and final report)Writing midterm reportWriting final reportIdea generationWriting business planBuilding the final demo day prototypeAssisting with programming and electronics for final demo day

DionBuilding and painting demo day props (wood)Writing part of the user interview and conducting the interviewsIdea generationWriting for final reportElaborate user interface Making a scheduleSupplying materialsBackground research

31

Appendix DReferences

Berman, B. (2014, 21 August). Get Ready To Say Goodbye To The Traffic Light. Retrieved 13 april 2018, from http://www.businessinsider.com/traffic-light-technol-ogy-2014-8?international=true&r=US&IR=T

Grey, C. G. P. (2016, 31 August). Get Ready To Say Goodbye To The Traffic Light [Video]. Retrieved 13 april 2018, from https://www.youtube.com/watch?v=iHzzS-ao6ypE

Jaffe, E. (2016, 19 February). Get Ready To Say Goodbye To The Traffic Light. Re-trieved 13 april 2018, from https://www.citylab.com/transportation/2016/02/of-course-copenhagen-is-giving-bicycles-traffic-light-priority/470067/

Smarter Cambridge Transport. (2016, 24 April). Smart Traffic Management. Re-trieved 13 april 2018, from http://www.smartertransport.uk/smart-traffic-manage-ment/

Solomon, A. (2017, 7 April). A New Smart Technology will Help Cities Drastically Re-duce their Traffic Congestion. Retrieved 13 april 2018, from https://www.pastemag-azine.com/articles/2017/04/a-new-smart-technology-will-help-cities-drasticall.html

De Beer, J. P. (2014, 1 September). Watch the first Flo in Utrecht, the Netherlands. Retrieved 13 april 2018, from http://springlab.nl/flo-en/

Roger Hallowell, (1996) “The relationships of customer satisfaction, cus-tomer loyalty, and profitability: an empirical study”, International Jour-nal of Service Industry Management, Vol. 7 Issue: 4, pp.27-42, https://doi.org/10.1108/09564239610129931

Unique U.S. visitors to mobile apps 2016 | Statistic. - Statista.com Retrieved from https://www.statista.com/statistics/250862/unique-visitors-to-the-most-popular-mobile-apps-in-the-us/

Head-up display. (2018, May 23). Retrieved June 10, 2018, from https://en.wikipe-dia.org/wiki/Head-up_display

Kleurcontrast. (2018, April 14). Retrieved May 13, 2018, fromhttps://nl.wikipedia.org/wiki/Kleurcontrast

De Ridder, M. (2017, 26 June). welke gevoelens/emoties roepen kleuren op? Re-trieved 13 May 2018, from https://www.moodles.nl/tips/design/kleurgebruik/wel-ke-gevoelens-emoties-roepen-kleuren-op

Hammond, L. A. (2013, 5 February). How does heads-up-display (HUD) work? Re-trieved 18 May 2018, from https://www.drivingthenation.com/how-does-heads-up-display-hud-work-on-driving-the-nation/

Wernisch, T. (2016, 3 May). Vehicle Cluster Dashboard Concept. Retrieved 16 May 2018, from https://dribbble.com/shots/2690845-Vehicle-Cluster-Dashboard-Con-cept

32

Varshney, A. (2017, 15 November). SIGNS YOU NEED TO REPLACE YOUR AUTO WINDOWS. Retrieved 16 mei 2018, from http://www.aaaautoglasshouston.com/signs-you-need-to-replace-your-auto-windows

Uber. (n.d.). Steel City’s New Wheels. Retrieved June 10, 2018, from https://www.uber.com/info/atg/car/

Jeong, Y., & Yoon, B. (2015). Development of patent roadmap based on technology roadmap by analyzing patterns of patent development. Technovation, 39, 37-52.

Traffic Light Exchange (TLEX) maakt real-time data-uitwisseling tussen verkeers-lichten en weggebruikers mogelijk. (2017, 29 maart). retrieved 2 juni 2018, from https://beterbenutten.nl/nieuws/1273/traffic-light-exchange-tlex-maakt-re-al-time-data-uitwisseling-tussen-verkeerslichten-en-weggebruikers-mogelijk

Sarkis, A. (2017, 19 september). Self-Driving Cars: Implementing Real-Time Traffic Light Detection and Classification in 2017. retrieved 7 juni 2018, by https://code-burst.io/self-driving-cars-implementing-real-time-traffic-light-detection-and-classifi-cation-in-2017-7d9ae8df1c58

Wikipedia, the free encyclopedia. (2018, January 11). Green wave. Retrieved May 26, 2018, from https://en.wikipedia.org/wiki/Green_wave