WEBVTT 00:02.060 --> 00:03.180 Lectures are recorded. 00:03.520 --> 00:07.940 So, welcome again also to those who are not really following this 00:07.940 --> 00:08.340 course. 00:08.840 --> 00:11.960 Just the first slide again. 00:12.980 --> 00:14.520 That's the course on organic computing. 00:15.260 --> 00:19.340 I forgot to record, so I have to repeat this briefly. 00:19.880 --> 00:23.420 Welcome to the summer semester 2013. 00:23.840 --> 00:27.440 And the lecture will be given by myself and by Wanda Postegi, who is 00:27.440 --> 00:29.720 not here today, but will be there next week. 00:29.720 --> 00:34.280 She will teach next week and then the week after that and several 00:34.280 --> 00:35.040 times more. 00:35.520 --> 00:39.100 So, I think she has the majority of the lectures. 00:40.460 --> 00:47.300 Ok, so, this will be a course presented live, definitely, but also the 00:47.300 --> 00:48.220 lecture is recorded. 00:51.200 --> 00:55.000 And recorded, as you know, means, if you do a little contagion, it's 00:55.000 --> 00:58.700 brain grabbing, so everything which is on the screen is recorded. 00:59.600 --> 01:04.980 And I did not check whether it was full screen, but I think it was 01:04.980 --> 01:09.160 full screen when I started to record. 01:09.260 --> 01:09.840 It should be ok. 01:11.520 --> 01:14.080 So, otherwise I would see something different. 01:15.240 --> 01:21.260 Ok, so, the recorded lectures are available as ABI documents, so you 01:21.260 --> 01:24.560 can download them and then look at them whenever you like. 01:25.080 --> 01:29.240 Whenever you like may be sometime when you are preparing for the final 01:29.240 --> 01:34.540 exam or maybe for just when you are working on assignments. 01:34.880 --> 01:36.520 Or whatever you like to do. 01:36.720 --> 01:41.860 Maybe you miss a lecture and then you would like to use that. 01:41.860 --> 01:47.860 And so you can download those documents from the web pages. 01:48.200 --> 01:55.280 There is a link at the website of this course and there is also in the 01:55.280 --> 02:00.420 digital video and audio archive there is a listing of all the recorded 02:00.420 --> 02:03.040 lectures and you can easily find my lectures there. 02:03.720 --> 02:07.340 There are many courses and lectures that I have recorded so far. 02:07.480 --> 02:14.300 So you have a broad selection of lectures that I have given before and 02:14.300 --> 02:15.760 will be giving this term. 02:16.360 --> 02:19.320 You can use the recorded lectures with any media player. 02:19.820 --> 02:22.080 Those who have looked at that before know that. 02:22.420 --> 02:23.740 You can use any video player. 02:24.240 --> 02:29.460 But the important point is that if you are really working with such a 02:29.460 --> 02:32.040 recorded lecture you should be able to do visible scrolling. 02:32.040 --> 02:36.420 That means when you are going back and forth you should see where you 02:36.420 --> 02:36.880 are scrolling. 02:37.380 --> 02:43.280 And this is available for the Camtasia player which is free of charge. 02:43.760 --> 02:44.960 It can be downloaded. 02:45.640 --> 02:49.020 And you can also certainly use any other media player if you like. 02:49.720 --> 02:57.140 Maybe you prefer to have a changed speed in order to speed up the 02:57.140 --> 02:58.180 lecture a little bit. 02:59.400 --> 03:05.560 Standard effect that usually in class lecturer speed is ok, but if you 03:05.560 --> 03:10.280 look at that later on in a recorded lecture the impression is that 03:10.280 --> 03:11.000 it's too slow. 03:11.260 --> 03:15.200 So you can easily speed it up and then you can use that. 03:15.260 --> 03:16.780 But that's up to you. 03:16.960 --> 03:21.400 And just this is one of the features that we provide to you. 03:21.740 --> 03:23.620 Lecture material that's recorded. 03:24.020 --> 03:24.920 These recorded lectures. 03:25.720 --> 03:28.620 Ok, that's all I have on this slide. 03:28.820 --> 03:33.920 And then what should have been the reference to the website comes a 03:33.920 --> 03:34.280 bit later. 03:35.160 --> 03:36.280 You see another thing here. 03:36.380 --> 03:40.680 You see down here the Nukid tools. 03:43.880 --> 03:46.060 You see these tools. 03:46.700 --> 03:48.340 So, this feedback tool. 03:48.340 --> 03:55.540 So, this is something which I just want to tell you that you can use 03:55.540 --> 03:55.960 that. 03:56.560 --> 04:00.300 Certainly in a class like this, where there are very few students, the 04:00.300 --> 04:02.320 best thing is to communicate directly. 04:02.600 --> 04:05.780 Raise up your hands and ask questions and things like that. 04:06.120 --> 04:09.560 But we have designed these cooperation tools. 04:09.840 --> 04:13.760 And so, like a long time ago, now we have updated it. 04:13.760 --> 04:19.400 We have an app for your smartphone, where you can use that tool. 04:19.840 --> 04:22.040 Who of you has never seen those Nukid tools? 04:26.190 --> 04:29.070 You don't have a smartphone, but you have a laptop, maybe. 04:29.550 --> 04:31.810 You can also use it on a laptop. 04:32.890 --> 04:35.890 And so, here are these tools. 04:36.190 --> 04:39.970 So, this is the link to the web application, which just looks like 04:39.970 --> 04:40.230 this. 04:40.230 --> 04:45.350 That you can choose the lecture that you would like to give feedback. 04:45.650 --> 04:46.650 But you're sitting in the front row. 04:46.770 --> 04:47.550 You can leave the address. 04:48.150 --> 04:52.970 I just want to give information on that application. 04:53.250 --> 04:54.730 You can use it on your Android phone. 04:55.010 --> 04:57.990 Not on an iPhone, but you can use it on the Android phone. 04:58.370 --> 05:02.070 By the way, where I see the word iPhone here. 05:02.790 --> 05:04.810 I said that the lecture is recorded. 05:04.810 --> 05:12.690 And available, actually worldwide available, at our digital media and 05:12.690 --> 05:13.370 audio archive. 05:13.850 --> 05:18.030 But nowadays, people always like to be fancy. 05:18.410 --> 05:22.250 And the Mac world, or the Apple world, sometimes is considered to be 05:22.250 --> 05:22.570 fancy. 05:23.290 --> 05:27.210 So, there is some repository for courses. 05:29.450 --> 05:32.250 Presented or made available by iTunes. 05:32.250 --> 05:38.010 The iTunes U site, where all kinds of universities are presenting the 05:38.010 --> 05:38.310 lecture. 05:39.050 --> 05:40.890 So far, I have not done that. 05:41.050 --> 05:45.330 I was asked, would you like to also present this lecture at iTunes U? 05:45.710 --> 05:48.910 It was not asked by iTunes, but it was asked by our library. 05:50.190 --> 05:54.390 And I said, well, that's a proprietary platform, why should I support 05:54.390 --> 06:00.570 a company in its business ideas, business models, and provide my 06:00.570 --> 06:02.930 valuable lectures to their platform? 06:03.790 --> 06:06.290 The Faculty of Informatics is doing that. 06:06.850 --> 06:11.250 They are presenting everything on the iTunes U part, because then you 06:11.250 --> 06:11.890 are fancy again. 06:11.990 --> 06:12.670 Everything is available. 06:13.010 --> 06:15.170 My lectures have always been available to everybody. 06:16.190 --> 06:17.870 But it's on iTunes U. 06:17.990 --> 06:19.270 Only iTunes U is famous. 06:20.310 --> 06:22.550 Do you think I should present it on iTunes? 06:23.610 --> 06:25.810 Anybody who said okay, that would be fine? 06:27.150 --> 06:27.490 Nobody? 06:27.910 --> 06:29.010 I don't know what I said before. 06:29.690 --> 06:31.990 I might be a bit scared to raise my hand. 06:32.490 --> 06:33.850 But I could. 06:34.490 --> 06:37.810 So far, I don't like to do that. 06:38.390 --> 06:41.990 I think at KIT we have a good policy of presenting our lectures. 06:43.110 --> 06:43.730 And I'm doing that. 06:44.590 --> 06:44.790 Okay. 06:45.290 --> 06:47.630 So, these are the tools. 06:48.590 --> 06:52.710 I can use them, but it's not really necessary. 06:52.870 --> 06:57.710 If you'd like to use it, just download the app. 06:58.470 --> 07:02.250 And if you would like to download the app, you have to click on this 07:02.250 --> 07:06.730 link at the Play Store. 07:07.450 --> 07:09.670 And then look for LookIT. 07:10.430 --> 07:12.370 And then you can use it. 07:12.370 --> 07:16.630 And you can pick the password for this course is 07:23.850 --> 07:27.410 organiccomputing.com And that's for you on the app. 07:27.890 --> 07:32.450 That's the password you need for getting access to that course. 07:33.470 --> 07:33.690 Okay. 07:33.990 --> 07:34.850 So, you're welcome to do that. 07:35.890 --> 07:36.450 Okay. 07:36.810 --> 07:41.550 So, this is showing you briefly the tool, providing you with 07:41.550 --> 07:44.650 possibility to get feedback on the speed of the course, most of you 07:44.650 --> 07:46.610 would say now, be faster, please. 07:47.090 --> 07:49.010 You can say faster, or right, or slower. 07:50.530 --> 07:54.850 And, by the way, on the feedback here, because Phyllis Piper is here, 07:54.970 --> 08:01.210 and she is one of the persons mainly responsible for those tools, I'm 08:01.210 --> 08:05.710 always asking, oh, the top line, was it faster, or was it slower, or 08:05.710 --> 08:06.110 was it... 08:06.770 --> 08:13.650 I think it would be nice to have there some indication of let's say F, 08:13.790 --> 08:19.550 or rather F, A, and F, for faster, slower, or right, or slower. 08:20.230 --> 08:20.350 Yeah. 08:21.390 --> 08:24.310 So, if somebody would click on that, it would be something there. 08:24.450 --> 08:26.190 Okay, and then you can ask questions. 08:26.930 --> 08:30.590 And I will see those questions, I will see that the exclamation mark 08:30.590 --> 08:35.170 here will turn yellow, and then I can take that question and answer 08:35.170 --> 08:35.470 it. 08:36.010 --> 08:41.090 But, as I said, you can also ask questions by just asking it here in 08:41.090 --> 08:41.350 class. 08:41.350 --> 08:46.770 And you can also, or I can also ask you questions, and then we can get 08:46.770 --> 08:48.930 a brief survey on a certain question. 08:49.590 --> 08:51.290 But nobody is using that. 08:55.030 --> 08:57.630 So, let's continue. 08:58.450 --> 09:01.310 So, I will move this back. 09:04.280 --> 09:10.410 Why doesn't this...that's the appropriate position for... 09:11.010 --> 09:12.510 while I'm presenting something. 09:12.510 --> 09:16.150 So, all the relevant information of this course is available on the 09:16.150 --> 09:17.750 KIT study portal, as you know. 09:17.870 --> 09:18.630 So, this is the link. 09:19.530 --> 09:23.710 And we can briefly go on that link. 09:23.990 --> 09:29.700 If I switch back to this mode here. 09:30.360 --> 09:33.040 Now, I click on it. 09:35.380 --> 09:35.840 Ah, yeah. 09:36.220 --> 09:36.680 It's busy. 09:38.860 --> 09:40.280 There's something in the background. 09:42.140 --> 09:43.500 Maybe it doesn't like me. 09:43.620 --> 09:46.980 Maybe there are too many courses where people are doing things like 09:46.980 --> 09:47.320 that. 09:48.000 --> 09:48.780 It's still busy. 09:50.640 --> 09:51.760 Seems to take some time. 09:52.360 --> 09:55.340 Okay, don't know why this takes so long. 09:56.660 --> 10:00.380 So, the times, all those who are here know that the scheduled times 10:00.380 --> 10:02.420 are Mondays, 11.30 to 1. 10:02.700 --> 10:07.960 And the location is this room, room 231, this building. 10:08.760 --> 10:11.140 And I don't know why it is so busy. 10:11.460 --> 10:17.600 Let's just briefly go back and look what's happening here. 10:30.910 --> 10:32.310 Something is wrong. 10:32.530 --> 10:33.850 I don't know what happened. 10:34.410 --> 10:36.270 Sometimes things like that happen. 10:36.570 --> 10:40.010 In particular, when you are testing things before the course, 10:40.070 --> 10:40.970 everything is fine. 10:41.790 --> 10:46.650 And then, you are doing something in course, in the course, and all of 10:46.650 --> 10:51.540 a sudden, this link is correct. 10:51.740 --> 10:52.460 I tested it. 10:53.140 --> 10:54.120 But it doesn't work. 10:55.060 --> 10:56.740 So, now I should... 10:56.740 --> 10:58.800 Just to show you, I said I wanted to show you that. 10:59.480 --> 11:00.120 What's this? 11:00.700 --> 11:01.380 That's wrong. 11:01.740 --> 11:02.920 It didn't want to go there. 11:03.960 --> 11:04.720 What's this? 11:06.640 --> 11:07.120 What? 11:08.440 --> 11:09.140 Come on. 11:09.660 --> 11:10.840 Didn't want to show you that. 11:11.340 --> 11:13.020 So, I wanted to go to Mozilla. 11:13.360 --> 11:13.620 Right. 11:14.580 --> 11:16.440 So, here it's doing something. 11:16.440 --> 11:17.100 OK. 11:17.360 --> 11:25.200 Obviously, you notice that I could not enter the WKIT website. 11:26.240 --> 11:29.040 So, maybe it's not liking that. 11:29.220 --> 11:30.400 Maybe the server is down. 11:31.220 --> 11:32.220 The study portal server. 11:32.380 --> 11:32.980 I guess that. 11:34.600 --> 11:35.240 OK. 11:35.720 --> 11:38.120 So, that's really on time. 11:38.640 --> 11:42.920 On time, on the first day of the summer term, the study portal is not 11:42.920 --> 11:43.240 available. 11:43.860 --> 11:44.200 Perfect. 11:44.200 --> 11:44.860 OK. 11:47.480 --> 11:50.520 So, let's go back to the course. 11:50.740 --> 11:52.640 Everything is here on my slides. 11:52.960 --> 11:53.600 Let's continue. 11:54.080 --> 11:57.420 The tutorials will be managed by Friederike Pfeiffer-Bohnen. 11:57.480 --> 11:58.840 She's sitting over there. 11:59.060 --> 12:00.580 To the south, quickly. 12:01.260 --> 12:02.780 And, Sabrina Merkel. 12:04.120 --> 12:13.440 Yeah, so, they are sitting in the AIB in the Kronplatz and they are 12:13.440 --> 12:18.540 happy to assist you in everything that concerns this course and 12:18.540 --> 12:19.220 tutorials. 12:19.400 --> 12:24.000 So, they will organize the tutorials and give you feedback on the 12:24.000 --> 12:25.260 forum and things like that. 12:26.060 --> 12:28.500 And here you see the specific time. 12:28.880 --> 12:35.960 So, just before this course starts, every Monday, you can go to 12:35.960 --> 12:42.660 Friederike Pfeiffer-Bohnen and Sabrina Merkel is just available all 12:42.660 --> 12:44.680 the time, according to agreement. 12:45.400 --> 12:45.520 Yeah. 12:46.120 --> 12:46.560 Or never. 12:47.580 --> 12:48.760 According to agreement. 12:51.280 --> 12:51.660 Did you? 12:52.020 --> 12:52.540 Which one? 13:01.080 --> 13:05.730 Tuesday 2 p.m. 13:07.090 --> 13:09.630 14 to 15. 13:11.530 --> 13:12.470 Okay. 13:13.430 --> 13:13.770 Fine. 13:14.910 --> 13:16.430 So, what else do we have? 13:16.830 --> 13:19.010 Every other week will be what? 13:19.210 --> 13:20.970 Every other week there will be tutorials. 13:22.110 --> 13:26.270 Every other week you have to go to the tutorials or you are offered 13:26.270 --> 13:26.930 the tutorials. 13:27.310 --> 13:31.510 We offer you this service and we would like to give you a chance to 13:31.510 --> 13:35.190 work more intensively with the content of this course. 13:36.170 --> 13:39.390 So, Wednesday afternoon 2 p.m. 13:39.910 --> 13:44.950 to 3.30 in this room or in the Zippool. 13:46.330 --> 13:48.930 Sometimes in the Zippool, the first time it will be in the Zippool. 13:49.610 --> 13:57.150 This Wednesday, next week Wednesday will be in the Zippool downstairs 13:57.150 --> 14:02.250 because there are quite a few things that you should get to see on the 14:02.250 --> 14:08.070 Zippool, on the computers because there will be not just tutorials or 14:08.070 --> 14:12.490 assignments where you do something with pencil and paper, but also 14:12.490 --> 14:13.170 with a computer. 14:14.970 --> 14:17.270 Registration by signing up in the first tutorial. 14:18.830 --> 14:20.850 Don't use the subscribe tool. 14:21.870 --> 14:22.990 Don't want to use that. 14:23.270 --> 14:28.730 Could have used that, but we just do it in the first tutorial so just 14:28.730 --> 14:33.390 come to the Zippool and then you have to sign up wherever you have the 14:33.390 --> 14:34.410 possibility to sign up. 14:35.290 --> 14:35.510 Okay. 14:36.230 --> 14:40.090 And this course is on self-organization and adaptive systems, so the 14:40.090 --> 14:42.770 course itself will also be like that. 14:43.090 --> 14:46.070 This was particularly true for the first editions of this course. 14:46.290 --> 14:49.070 It has been taught two times. 14:49.290 --> 14:53.830 So, it will still be adaptive for your requirements. 14:55.410 --> 14:57.590 What do we do in the tutorials? 14:57.830 --> 15:04.390 You will be given typical assignments, some typical things you can do 15:05.650 --> 15:07.830 on paper. 15:09.210 --> 15:11.550 And we will have... 15:11.550 --> 15:19.390 we think that it is very good for a course like this which is on 15:20.530 --> 15:24.450 systems which can self-organize, can be adaptive, having to do with 15:24.450 --> 15:27.230 many agents and so on, as you will see a little bit later. 15:27.850 --> 15:32.210 It's good to see a realistic example and to get some experience how 15:32.210 --> 15:34.130 you can actually program systems like that. 15:34.130 --> 15:36.170 At least simulate systems like that. 15:37.010 --> 15:41.490 And so we said, well, it's good to do something practical. 15:42.230 --> 15:46.890 And so you will get quite a few assignments where you have to do 15:46.890 --> 15:48.130 something with NetLogo. 15:48.310 --> 15:51.550 NetLogo is a nice tool that you can download from the link that is 15:51.550 --> 15:55.250 given here or from the website of the course when it is available. 15:56.970 --> 16:02.530 And then you will be given several assignments, up to six assignments, 16:03.150 --> 16:07.330 and you will have some exercises that you do directly in the tutorial, 16:07.670 --> 16:09.270 some things you will be doing at home. 16:09.770 --> 16:13.590 And you will get some feedback on how well you did that. 16:14.070 --> 16:17.930 You should work in groups of two students in order to learn how to 16:17.930 --> 16:18.290 cooperate. 16:19.310 --> 16:25.490 And so we will also offer a bonus for active and successful 16:25.490 --> 16:26.690 participation in tutorials. 16:27.450 --> 16:29.110 Actually, there are several bonuses. 16:29.590 --> 16:33.610 The first bonus you get is if you are actively participating in 16:33.610 --> 16:37.250 tutorials, then you get a bonus because you learn more. 16:38.250 --> 16:44.610 The next thing is that if you are active and successful, you do have 16:44.610 --> 16:47.850 some specific, more concrete rules for that. 16:48.770 --> 16:49.830 My tool is the assistant. 16:51.890 --> 16:57.470 What is the explicit regulation for getting the bonus? 16:57.470 --> 17:00.590 Usually I say something here on the number of points or whatever. 17:01.030 --> 17:01.830 There are some rules. 17:04.210 --> 17:05.310 Seventy-five percent. 17:06.410 --> 17:11.530 Yes, but maybe a minimum number of assignments that you have to do. 17:11.710 --> 17:13.130 Maybe four or something. 17:15.650 --> 17:17.230 But that's up to you. 17:17.310 --> 17:18.750 You can explain all that on Wednesday. 17:19.550 --> 17:24.850 But we are giving a bonus and this bonus will lead to an improvement 17:24.850 --> 17:31.230 of your final mark if you have passed the final exam, you get the next 17:31.230 --> 17:34.570 step in the grades, in the marks. 17:34.850 --> 17:40.550 So, it is an improvement of 0.3 or 0.4, depending whether you go from 17:40.550 --> 17:45.150 1.7 to 1.3 or from 1.3 to 1.0. 17:46.610 --> 17:49.690 Because usually you will be just doing fine. 17:50.150 --> 17:52.730 These are the typical marks you would get. 17:52.930 --> 17:57.810 I guess some may also get marks that are not as good, but if you are 17:57.810 --> 18:02.130 actively working in the assignment, you will get good marks. 18:03.330 --> 18:03.590 Okay. 18:03.870 --> 18:04.750 What type of exam? 18:05.210 --> 18:09.650 The exam will be as always, a one-hour exam at the end of the course. 18:10.190 --> 18:14.050 First week after the end of lectures or standard time at the AISD for 18:14.050 --> 18:15.650 exams. 18:16.090 --> 18:22.870 So, the first three days after the end of lectures is 22nd to the 24th 18:22.870 --> 18:23.470 of July. 18:24.830 --> 18:30.850 It will be a written exam, unless there are less than, let's say, 12 18:30.850 --> 18:31.750 students or so. 18:32.110 --> 18:32.490 Then, 18:36.110 --> 18:37.330 quite a few more. 18:38.130 --> 18:40.270 The exam questions will be in English. 18:41.390 --> 18:47.970 And you may answer in English what you are The exam is not testing 18:47.970 --> 18:52.570 your ability to express yourself in English, but it is testing your 18:52.570 --> 18:57.410 ability to know something, do something to the topics that we have 18:57.410 --> 18:57.650 here. 18:58.050 --> 19:01.670 And I don't mind or don't bother whether you do that in English or in 19:01.670 --> 19:01.890 German. 19:02.670 --> 19:04.830 But, we present this course in English. 19:07.310 --> 19:11.590 And, so, there are many reasons why one should do that. 19:12.050 --> 19:13.910 One is internationalization. 19:14.330 --> 19:16.690 So, it's good to have something which is available everywhere, 19:17.390 --> 19:18.670 understandable everywhere. 19:19.230 --> 19:22.230 Then, it's good for improving English language skills. 19:22.590 --> 19:24.350 I'm keeping up my English language skills. 19:24.710 --> 19:28.810 You are learning how to listen to somebody who is talking English. 19:29.590 --> 19:33.690 And maybe when you are doing everything in English, also in the 19:33.690 --> 19:37.930 tutorials and get the right things, we ask questions here, you just 19:37.930 --> 19:39.870 improve your English language skills. 19:39.950 --> 19:45.750 This can be beneficial for your future professional life, job life, 19:46.290 --> 19:47.670 definitely for foreign studies. 19:47.670 --> 19:52.530 Who of you has been somewhere in some foreign country for studying 19:52.530 --> 19:53.030 already? 19:55.580 --> 19:56.720 Not quite, ok. 19:57.340 --> 20:01.980 But, maybe, and who of you intends to spend some time at a foreign 20:01.980 --> 20:02.560 university? 20:04.080 --> 20:04.900 A few more. 20:05.580 --> 20:06.740 Ok, good. 20:07.640 --> 20:11.780 And, then certainly the global marketplace, everything nowadays is 20:11.780 --> 20:13.260 international, globalized. 20:13.540 --> 20:18.580 And, so, it's just necessary to have no problem conversing in English. 20:19.240 --> 20:21.840 And, then, certainly we also would like to attract foreign students. 20:23.720 --> 20:30.220 And, for that, we arranged or we agreed that in this faculty we should 20:30.220 --> 20:36.040 have English courses in every subject, so that somebody who is 20:36.040 --> 20:41.860 studying or coming here for just one term or for a year has a chance 20:41.860 --> 20:49.920 to study in English, even so, can come here to the KIT and study here 20:49.920 --> 20:52.220 even without knowing German sufficiently. 20:53.160 --> 20:54.800 So, that's why we present English courses. 20:57.380 --> 20:59.740 Anybody here who doesn't speak German? 21:03.400 --> 21:09.600 Maybe, later on in the feedback from the from those who listened to 21:09.600 --> 21:13.600 this lecture remotely might give that feedback. 21:13.600 --> 21:15.180 Would you prefer to have... 21:15.180 --> 21:17.340 Who would prefer to have this course on German? 21:20.160 --> 21:20.640 Okay. 21:21.780 --> 21:26.340 Otherwise, I would have had to change the slides, maybe. 21:26.700 --> 21:28.020 So, this is the graduate course. 21:28.620 --> 21:29.560 Graduate course? 21:29.800 --> 21:31.100 We don't have graduate and undergraduate. 21:31.560 --> 21:36.400 We talk here about bachelor and master, but we talk about basic stuff 21:36.400 --> 21:37.420 and real stuff. 21:37.740 --> 21:42.500 This is real stuff, so it's starting in the third year of your 21:42.500 --> 21:42.980 studies. 21:42.980 --> 21:51.060 So, it is available in the module for the master courses, or for the 21:51.060 --> 21:55.420 master program, but I've always had some students who already took 21:55.420 --> 21:57.320 that as bachelor students. 21:58.830 --> 22:02.120 I think in the moment it's five credits, sometimes. 22:02.580 --> 22:06.800 Some study program, some module can focus on 4.5. 22:07.440 --> 22:08.920 You will get what you need. 22:09.760 --> 22:12.980 And who is the target group? 22:13.200 --> 22:15.040 Certainly the students of this faculty. 22:16.160 --> 22:19.300 Business engineering, economics engineering. 22:20.500 --> 22:25.560 And you can combine that with other courses in applied informatics. 22:26.920 --> 22:30.500 Then there is the course on the program on information engineering and 22:30.500 --> 22:30.900 management. 22:32.340 --> 22:36.940 And there are other courses or other programs like business math, 22:37.060 --> 22:39.160 technomath, informatics, energy technology. 22:39.440 --> 22:42.640 Who is here from, let's go from top down. 22:43.180 --> 22:44.800 Who is the business engineer? 22:47.680 --> 22:51.640 Who is studying economics engineering, technical law behavior? 22:52.580 --> 22:55.740 Who is in information engineering and management? 22:56.960 --> 22:57.780 Both of you. 22:58.400 --> 23:01.980 You are in master or bachelor? 23:03.320 --> 23:04.980 Who is in bachelor program? 23:05.940 --> 23:06.980 You are studying what? 23:06.980 --> 23:07.580 Which one? 23:09.180 --> 23:09.820 Okay. 23:10.040 --> 23:10.300 And you? 23:11.280 --> 23:11.920 Okay. 23:13.360 --> 23:16.320 And who is here from some of the others? 23:17.840 --> 23:21.700 Business math, technomath, informatics, energy technology, and tech. 23:22.820 --> 23:23.700 Nobody here. 23:24.340 --> 23:24.980 Okay. 23:27.160 --> 23:31.500 And you have to check for the module where you would like to have this 23:31.500 --> 23:32.280 accounted for. 23:33.200 --> 23:34.840 There is some flexibility. 23:34.840 --> 23:39.000 Some people responsible for the module handbook and the program of 23:39.000 --> 23:44.980 study would like to have a very strict setting for that. 23:45.360 --> 23:47.000 I like to have flexibility. 23:47.860 --> 23:51.640 And the most important point is that you can study what you think is 23:51.640 --> 23:56.820 really important for your future career, maybe in industry, or 23:56.820 --> 23:59.200 wherever you like to be active in the future. 23:59.820 --> 24:02.340 And for that we need adaptive study program. 24:03.480 --> 24:04.040 Okay. 24:05.420 --> 24:08.520 Do you have any questions with respect to these organizational stuff? 24:10.200 --> 24:10.480 Nothing? 24:10.760 --> 24:10.940 Okay. 24:11.360 --> 24:14.700 Then let's go to a brief overview of what I will tell you. 24:14.800 --> 24:20.260 Something about introductory things, then there will be a chapter on 24:20.260 --> 24:21.060 architectures. 24:21.680 --> 24:25.640 We definitely will talk about self-organization emergence, more about 24:25.640 --> 24:30.160 so -called self-x features, like self-configuring, self-healing, self 24:30.160 --> 24:30.700 -protecting. 24:30.700 --> 24:35.160 We will hear a bit more about that in a moment. 24:35.720 --> 24:37.640 But there will be a chapter on machine learning. 24:38.880 --> 24:40.620 Oops, why do we have six there? 24:41.920 --> 24:42.540 That's funny. 24:44.500 --> 24:45.500 Where is chapter five? 24:46.400 --> 24:51.140 I guess that I have just chuckled around a little bit the chapters up 24:51.140 --> 24:51.420 here. 24:52.420 --> 25:00.520 So, chapter five is like just will be machine learning, then six, I 25:00.520 --> 25:01.900 guess, robustness, flexibility, and trust. 25:02.080 --> 25:03.940 Or I mixed up something here. 25:04.520 --> 25:04.960 I don't know. 25:05.300 --> 25:08.660 But this is this will be the contents of this course. 25:08.780 --> 25:12.380 You see, it's quite a broad range of topics. 25:13.040 --> 25:16.420 Organic computing is a transdisciplinary topic. 25:16.860 --> 25:23.740 And so we have to select certain topics here that highlight the facets 25:23.740 --> 25:24.880 of organic computing. 25:25.140 --> 25:28.640 And in the end, you will know what it is and will be able to do more 25:28.640 --> 25:29.200 in that area. 25:29.780 --> 25:34.880 We will also look at applications, traffic control, energy systems. 25:35.580 --> 25:38.120 And these applications will also be visible before. 25:38.700 --> 25:41.820 So, we will always talk about applications there. 25:42.060 --> 25:44.340 But there will be a specific chapter on that in the end. 25:45.620 --> 25:46.180 Okay. 25:46.920 --> 25:49.440 References are quite a few, meanwhile. 25:50.640 --> 25:53.340 So, there are two books. 25:53.860 --> 26:01.460 One early book on organic computing came out in 2008 or so. 26:02.060 --> 26:04.900 Then we have this book on organic computing. 26:05.500 --> 26:06.760 Why is it this book? 26:06.940 --> 26:13.280 Because this is the compendium containing papers by the contributions 26:13.280 --> 26:19.920 by the participants of the six-year running priority program, like 26:19.920 --> 26:24.080 research program, of the German Research Foundation on Organic 26:24.080 --> 26:24.580 Computing. 26:25.320 --> 26:29.200 And in the end we came up with this final compendium. 26:29.960 --> 26:35.020 And you can look at it using those links here. 26:35.500 --> 26:39.860 And you can download the content, the book, also the library. 26:40.540 --> 26:46.960 So, that's a very comprehensive book on all the different topics that 26:46.960 --> 26:49.520 we touch here in organic computing. 26:49.520 --> 26:56.020 So, this is, like, we sometimes talk about the topic that teaching at 26:56.020 --> 26:58.540 KIT should be research oriented teaching. 26:59.240 --> 27:02.860 And organic computing is something that is a rather new area of 27:02.860 --> 27:03.260 research. 27:04.000 --> 27:05.820 And we designed most of it. 27:06.280 --> 27:10.840 I was coordinating the program, so you get your first-hand information 27:10.840 --> 27:12.900 on topics of current research. 27:13.620 --> 27:18.920 Then, there is a multitude of papers that can look at many different 27:18.920 --> 27:19.580 conferences. 27:20.320 --> 27:23.960 This topic, as you will see, is quite diverse. 27:24.340 --> 27:26.800 And so, there are many different conferences where you can look up 27:26.800 --> 27:28.400 something on organic computing. 27:28.540 --> 27:32.660 Sometimes it's not called organic computing, but appearing under a 27:32.660 --> 27:33.460 different name. 27:34.160 --> 27:37.200 You see there are conferences like Autonomic Computing, Ubiquitous 27:37.200 --> 27:40.580 Computing, Pervasive Computing, Self-Organization, Computex Systems, 27:40.740 --> 27:42.940 Bioquiet Systems, Machine Learning, and so on. 27:43.900 --> 27:48.980 And, there is also a list of links to relevant literature. 27:49.120 --> 27:55.440 There is one link to a repository of papers that was available on the 27:55.440 --> 28:00.360 website of our SPP Schwerpunktprogramm, or priority program. 28:01.420 --> 28:05.940 And this comprehensive guide, Literature on Organic Computing, was not 28:05.940 --> 28:06.820 available yesterday. 28:07.420 --> 28:12.320 I approached the person who was responsible for that yesterday, and he 28:12.320 --> 28:14.800 said, we will look at it and make it available again. 28:15.500 --> 28:20.620 So, there is a large repository on literature from that priority 28:20.620 --> 28:22.440 program, but also beyond that. 28:23.260 --> 28:25.740 And if you would like to see more about the topic of organic 28:25.740 --> 28:33.000 computing, if you just go to this URL without SPP, then you get a more 28:33.000 --> 28:35.060 general website on organic computing. 28:35.540 --> 28:39.580 And this here with SPP is mainly the information on the priority 28:39.580 --> 28:40.160 program. 28:40.160 --> 28:44.480 We also have information on most of the colloquia and most of the 28:44.480 --> 28:47.140 presentations that have been given to that research program. 28:47.260 --> 28:50.180 So, there is a lot of information available, if you are interested. 28:51.060 --> 28:51.240 Okay. 28:52.300 --> 28:58.200 I would certainly like to get feedback on what we are telling you, 28:58.220 --> 28:59.100 what we are teaching you. 28:59.760 --> 29:01.560 It is a dynamic subject. 29:02.140 --> 29:04.540 Things are developing there quite fast. 29:05.300 --> 29:09.040 And this is also an active research area at Karlsruhe. 29:09.340 --> 29:13.360 The project or the priority program is no longer active, but we are 29:13.360 --> 29:15.840 still working on topics having to do with organic computing. 29:16.480 --> 29:21.060 So, if you are interested in getting direct access to our research, 29:21.200 --> 29:24.720 just approach us and there are projects where you can do something in 29:24.720 --> 29:25.160 this area. 29:25.860 --> 29:30.520 This is just the organizational stuff that I wanted to present to you. 29:30.620 --> 29:34.200 And now we come to the first real chapter. 29:35.380 --> 29:42.920 Chapter introduction, where I will tell you a little bit more about 29:42.920 --> 29:43.760 organic computing. 29:43.980 --> 29:45.260 Just some introductory stuff. 29:45.720 --> 29:52.920 You see these different items here on this initial page. 29:54.120 --> 29:56.320 It looks a little bit funny. 29:56.580 --> 29:57.820 There are not many devices there. 29:58.360 --> 30:03.500 So, I will give you some motivation why this is characteristic of the 30:03.500 --> 30:04.940 core of organic computing. 30:05.200 --> 30:09.120 I will give you some motivation, show you some scenarios, give you the 30:09.120 --> 30:13.080 vision of organic computing, and what kind of things we have to work 30:13.080 --> 30:15.160 on in order to actually satisfy this. 30:16.520 --> 30:21.940 And one thing which is quite reasonable to start with is to tell you 30:21.940 --> 30:22.700 what it's not about. 30:22.760 --> 30:27.240 Because the topic, organic computing, immediately leads to some 30:27.240 --> 30:27.960 misconceptions. 30:28.520 --> 30:31.480 So, for example, if you compare it to organic chemistry, oh, this is 30:31.480 --> 30:34.380 something which is having to do with organic stuff. 30:35.100 --> 30:39.500 And if you go to the English-speaking world, North America or so, it's 30:39.500 --> 30:40.400 the organic food. 30:40.520 --> 30:41.560 Oh, that's the bad stuff. 30:42.520 --> 30:44.360 It's a different type of thing. 30:44.940 --> 30:46.500 So, what is organic computing? 30:46.920 --> 30:48.040 What it's not about? 30:48.340 --> 30:51.380 It's not about letting the computer grow green. 30:52.080 --> 30:52.300 Yeah? 30:53.380 --> 30:56.460 Like putting some green material into the computer. 30:59.000 --> 31:03.240 It's also not about building computers from organic materials. 31:04.440 --> 31:07.940 This would be a very nice idea, so there are quite a few interesting 31:09.520 --> 31:16.760 things, interesting research projects on actually building things from 31:16.760 --> 31:17.540 organic materials. 31:17.660 --> 31:22.300 For example, there's a very interesting thing on organic LEDs. 31:23.540 --> 31:27.380 Organic monitors, organic screens from organic materials. 31:27.380 --> 31:29.980 Really organic, natural things. 31:31.120 --> 31:37.240 And there is a cluster on organic electronics quite close to 31:37.240 --> 31:37.940 Karlsruhe. 31:38.060 --> 31:39.080 That's north of Karlsruhe. 31:40.000 --> 31:43.780 And this is a leading edge cluster on organic electronics. 31:44.260 --> 31:48.620 You can look at those websites and see what's available there. 31:48.920 --> 31:53.160 The first one here is a presentation on some biologically oriented 31:53.160 --> 31:58.660 research or some topics having to do with doing something in biology, 31:59.340 --> 32:05.460 with computing, and the organic electronics cluster is also doing 32:05.460 --> 32:09.580 interesting stuff, but it's not the kind of topic that I would like to 32:09.580 --> 32:10.260 present you. 32:10.880 --> 32:17.820 It's also not about connecting nervous material to digital 32:17.820 --> 32:18.520 electronics. 32:19.300 --> 32:21.260 So, this is something which some people do. 32:21.700 --> 32:25.200 So, this is showing actually a brain cell of a rat on a microchip. 32:25.720 --> 32:28.200 Then you can just do fancy things with a rat. 32:29.540 --> 32:33.200 There's also some, like there's a researcher who connected some of his 32:33.200 --> 32:38.380 nerves to a microchip and he planned it, or looked for a person who 32:38.380 --> 32:41.940 would implant the corresponding microchip to the nervous cells of 32:41.940 --> 32:42.560 somebody else. 32:42.840 --> 32:47.160 And then they could communicate using wireless communication and 32:48.400 --> 32:50.780 communicate with their nervous signals. 32:51.920 --> 32:52.640 Interesting idea. 32:53.460 --> 32:53.600 Yeah? 32:53.980 --> 32:57.180 But, whether you like that, well, it's some kind of research. 32:57.820 --> 32:59.580 But we're not doing that here. 32:59.920 --> 33:01.760 It's an interesting area of research. 33:01.920 --> 33:04.060 You can look at that, but not in this course. 33:04.940 --> 33:07.120 Also, it's not about wet computing. 33:07.300 --> 33:10.900 So, it's not about DNA computing, or whatever you would like to do 33:10.900 --> 33:11.120 there. 33:11.580 --> 33:15.160 It's also an interesting area of research, but it's far, far beyond of 33:15.160 --> 33:16.440 what we can do at the moment. 33:17.400 --> 33:21.900 And, although there is some real research going on with that, but we 33:21.900 --> 33:27.600 are more down-to-earth doing things, real computing platforms. 33:28.480 --> 33:32.060 So, if you're interested in that, look it up in Wikipedia, or 33:32.060 --> 33:32.740 somewhere else. 33:33.660 --> 33:43.040 And, oops, I wanted to, I seem to have forgotten to repeat all those, 33:44.380 --> 33:46.460 come on, this is not real. 33:46.460 --> 33:56.460 I had to, yes, I had to briefly delete where is that? 34:01.430 --> 34:03.010 Where is that? 34:03.850 --> 34:06.750 I wanted to delete all the 34:12.020 --> 34:14.120 that would be the entry left. 34:15.120 --> 34:17.100 Why don't I see here? 34:20.220 --> 34:21.500 This is ridiculous. 34:24.530 --> 34:25.750 Where did that go? 34:30.710 --> 34:32.630 I have no idea where that... 34:34.740 --> 34:35.380 Come on. 34:37.440 --> 34:40.080 I don't want to prepare something. 34:46.820 --> 34:49.180 Can we take it out there? 34:50.380 --> 34:51.720 Why don't I see that? 34:51.980 --> 34:54.600 Do you have any idea why I don't see Lushen here? 34:57.600 --> 34:58.500 There, there it is. 34:59.400 --> 34:59.960 There it is. 35:03.280 --> 35:04.020 There it is. 35:04.020 --> 35:06.920 So, now we can continue. 35:08.260 --> 35:12.820 And, now we don't have the annotations from last year. 35:13.780 --> 35:16.220 So, what is it about? 35:16.380 --> 35:17.120 Organic computing. 35:17.320 --> 35:18.800 It's about certain developments. 35:18.900 --> 35:21.900 Well, it's inspired, motivated by certain developments in computing. 35:22.740 --> 35:30.720 So, initially we had small computers, or actually large in space, but 35:30.720 --> 35:31.560 small in power. 35:31.560 --> 35:33.380 One computer for many persons. 35:34.600 --> 35:36.720 Then we had a personal computer. 35:37.500 --> 35:39.740 One computer per person. 35:40.280 --> 35:41.220 A personal computer. 35:41.900 --> 35:44.200 Now we have many computers per person. 35:45.560 --> 35:51.280 And, actually, in the moment we have just lots of computers per 35:51.280 --> 35:51.500 person. 35:52.080 --> 35:57.460 We have many devices that are carrying around, which might be, which 35:57.460 --> 36:03.580 might use several computers, several cores, and things like that. 36:04.620 --> 36:07.600 And, suddenly, the performance increased. 36:07.840 --> 36:10.460 The size went down. 36:10.640 --> 36:11.580 The size decreased. 36:11.740 --> 36:14.720 So, we can have all these components in our vicinity. 36:15.480 --> 36:22.220 We can embed all kinds of intelligent devices into our devices of our 36:22.220 --> 36:22.780 daily life. 36:23.420 --> 36:26.900 And this certainly changes the way we can live, and how we can 36:26.900 --> 36:28.980 interact with each other, and with our environment. 36:30.440 --> 36:35.820 You know that this development, that the size is decreasing, the 36:35.820 --> 36:40.160 performance is increasing, something which had been predicted by 36:40.160 --> 36:41.360 Gordon Moore. 36:41.760 --> 36:46.360 He said every 18 months the power would double and the size would be 36:46.360 --> 36:47.000 cut in half. 36:47.760 --> 36:48.880 And this was almost true. 36:48.980 --> 36:50.180 He did... 36:50.180 --> 36:57.400 he published his law sometime there, the beginning of the development 36:57.400 --> 36:58.240 of microchips. 36:59.020 --> 37:01.460 And it's actually still true. 37:01.580 --> 37:03.480 So, it's still increasing. 37:03.620 --> 37:08.100 Not at that pace, but it's incredible how much we can actually 37:08.100 --> 37:12.600 integrate on a very small area of the chip. 37:13.700 --> 37:20.600 One problem is that the reliability certainly is increasing, but it's 37:20.600 --> 37:23.400 just the reliability for transistors that is increasing. 37:24.800 --> 37:29.280 It means if we have many, many transistors, the reliability for chips 37:29.280 --> 37:30.880 will go down. 37:31.660 --> 37:37.580 And so, the more we integrate transistors on a chip, the more we will 37:37.580 --> 37:41.160 have to deal also with unreliability, with faults. 37:42.060 --> 37:47.260 So, sometimes the hardware that we are using will not function exactly 37:47.260 --> 37:48.760 as we would like it to do. 37:49.760 --> 37:51.940 So, we have to be aware that there may be faults. 37:52.520 --> 37:55.120 We have to be aware of that and do something about that. 37:55.560 --> 37:59.560 This is one motivation also for organic computing that we have to deal 37:59.560 --> 38:02.420 with unwanted behavior. 38:03.460 --> 38:09.600 This is just showing you a slide on estimates of parameters of the 38:09.600 --> 38:13.480 system on chips up to the year 2025. 38:14.820 --> 38:18.060 And, like, an important point certainly is that the number of 38:18.060 --> 38:22.880 transistors per millimeter will really be increased, like something 38:22.880 --> 38:25.040 larger than 50 transistors per millimeter. 38:26.420 --> 38:31.860 The number, or the chip size will be the same, so we will have a 38:31.860 --> 38:36.320 tremendous amount of logic of transistors on our chips. 38:37.140 --> 38:39.120 The frequency will go up. 38:39.200 --> 38:45.000 So, in 2004, 2007, it said the frequency that we can have can be 8 38:45.000 --> 38:45.380 GHz. 38:45.520 --> 38:50.300 Actually, what we are currently having, so here in 2013, usually we 38:50.300 --> 38:55.160 have something like 3 to 4 GHz in our processor. 38:56.140 --> 39:01.000 It means that technology is not really utilizing the very high 39:01.000 --> 39:06.260 frequency that would be possible in principle, but it's rather staying 39:06.260 --> 39:10.160 in the more conservative frequency of 3 to 4 GHz. 39:11.420 --> 39:16.760 And, but we have many more cores on a chip, so the power that we have 39:16.760 --> 39:17.860 available is increased. 39:18.760 --> 39:22.180 An important point here that I mentioned is the reliability. 39:23.060 --> 39:27.360 Although the reliability with respect to permanent failures of a chip 39:27.980 --> 39:34.280 will still be quite good, so the mean time to failure of a chip is a 39:34.280 --> 39:43.240 very large number, but the mean time to failure for transient faults 39:43.940 --> 39:45.220 will go down. 39:46.080 --> 39:51.060 And that means that we might have transient faults in our circuitry. 39:51.360 --> 39:57.280 That means faults that just occur now, then the chip is okay again. 39:57.460 --> 40:02.860 Maybe by radiation or things like that we have certain changes in our 40:02.860 --> 40:03.700 computations. 40:04.260 --> 40:05.700 We have to be aware of those things. 40:06.360 --> 40:10.280 There's a large body of work on fault-tolerant computing. 40:11.240 --> 40:15.080 It's not exactly what we are talking about in organic computing, but 40:15.080 --> 40:18.260 the main point is that I wouldn't want to address here is that we have 40:18.260 --> 40:20.200 to be aware that there might be faults. 40:21.200 --> 40:23.320 So what is organic computing about? 40:23.600 --> 40:27.560 It is about all kinds of collections of intelligent systems. 40:28.220 --> 40:34.580 So, systems in different scenarios, like the notion of a smart house 40:34.580 --> 40:38.080 or smart home is quite old, 10-15 years old. 40:38.740 --> 40:42.780 We actually have one smart home on our campus here that we have built 40:42.780 --> 40:47.320 for energy management studies and research. 40:47.960 --> 40:52.580 There are smart cars, offices, factories, shops, smart healthcare, 40:52.760 --> 40:56.060 like embedded systems in our healthcare devices. 40:56.960 --> 41:02.220 And there are corresponding disciplines, areas of research on 41:02.220 --> 41:06.280 ubiquitous computing, pervasive computing, or on cyber physical 41:06.280 --> 41:06.980 systems. 41:07.960 --> 41:13.600 All having to do with this presence of computing in all kinds of 41:13.600 --> 41:14.920 devices in our vicinity. 41:16.300 --> 41:23.120 The important thing is that our devices will be working in large 41:23.120 --> 41:23.980 networks. 41:24.480 --> 41:25.280 They may be mobile. 41:26.000 --> 41:29.960 That means that the environment might change over time, or during the 41:29.960 --> 41:33.320 operation time of some device. 41:33.600 --> 41:36.320 It might be confronted with many different environments, and it would 41:36.320 --> 41:37.780 always work correctly. 41:38.240 --> 41:42.560 So, we have something like an unlimited network for operating our 41:42.560 --> 41:43.020 systems. 41:43.980 --> 41:46.020 And those systems can interact. 41:47.300 --> 41:52.880 They can talk to each other, and agree on doing something, which might 41:52.880 --> 41:54.540 not always be what we like them to do. 41:54.620 --> 41:56.480 Usually we would like them certainly to cooperate. 41:57.520 --> 42:01.180 So, sometimes spontaneous local interaction can lead to emergent 42:01.180 --> 42:01.800 phenomena. 42:01.800 --> 42:06.800 One typical example that you all know is a traffic jam in traffic 42:06.800 --> 42:08.720 where there is no accident or anything. 42:09.140 --> 42:10.840 But all of a sudden you have a traffic jam. 42:11.520 --> 42:15.880 And it's just because of the interactions of the different cars. 42:16.200 --> 42:17.920 Some speed up, some have to brake. 42:18.540 --> 42:22.840 And so, you may get a traffic jam. 42:23.460 --> 42:28.560 Sometimes there are other so-called emergent phenomena which are just 42:28.560 --> 42:29.440 there. 42:29.440 --> 42:34.380 If we talk about effects, or self-organization, self-organizing 42:34.380 --> 42:38.020 systems, then we have to be aware of those potential effects. 42:38.580 --> 42:40.740 So, this will be one topic of our talk. 42:41.780 --> 42:44.400 Then we would like to have systems which are very robust. 42:44.920 --> 42:51.220 That means they should provide their service even if there are certain 42:51.220 --> 42:52.340 disturbances. 42:53.140 --> 42:58.740 So, our mobile phones will work everywhere, in the car, in the bus, 42:59.040 --> 43:00.740 certainly not in a car. 43:01.100 --> 43:06.440 We use functionality in class, in lecture rooms, because we wouldn't 43:06.440 --> 43:09.060 be distracted unless we use our nice app. 43:10.260 --> 43:13.820 And, so, robust service is one thing. 43:14.600 --> 43:18.960 Do something in spite of, or in presence of certain disturbances 43:18.960 --> 43:20.820 provide functionality. 43:21.360 --> 43:24.940 Sometimes we would like to have a change in functionality. 43:24.940 --> 43:31.180 The system should be able to change its way of responses, depending on 43:31.180 --> 43:35.140 certain things in the vicinity. 43:35.520 --> 43:40.540 So, a traffic light control should be able to be flexible, and maybe 43:40.540 --> 43:44.480 sometimes just skip a certain green phase because no car is waiting, 43:45.060 --> 43:45.820 or things like that. 43:45.920 --> 43:46.560 It should be adaptive. 43:47.120 --> 43:51.000 Maybe also it should be flexible to say, okay, I would like to control 43:51.000 --> 43:55.640 the traffic such that the number of stops of the cars is reduced, the 43:55.640 --> 44:00.740 waiting time, or the driving time is reduced, would be one objective 44:00.740 --> 44:02.480 for traffic control. 44:02.980 --> 44:05.920 Another objective might be to reduce the energy consumption. 44:06.620 --> 44:09.320 This might be different settings of the system. 44:09.960 --> 44:13.580 The system should be able to just adapt to those different objectives. 44:16.140 --> 44:20.180 And, the point that certainly is of interest is that if we design 44:20.180 --> 44:25.600 those systems, if we try to manage those systems, we have to solve 44:25.600 --> 44:30.680 real challenges, and there's also one problem of the acceptance of 44:30.680 --> 44:31.420 those systems. 44:32.000 --> 44:36.200 Because, if you know that you are observed all the time, maybe you 44:36.200 --> 44:36.820 don't like that. 44:37.840 --> 44:44.400 A typical example is that you have some RFID tag devices that you buy, 44:44.840 --> 44:46.400 then it can be traced. 44:47.060 --> 44:53.100 So, people say, no, I don't want those goods having RFID tags. 44:53.440 --> 44:56.840 They have to be disabled when I leave the store. 44:57.800 --> 44:59.540 So, we have all these systems. 44:59.660 --> 45:00.560 They are just there. 45:01.420 --> 45:02.300 They will be there. 45:03.160 --> 45:08.060 The problem is, what can we do to really make them controllable and to 45:08.060 --> 45:09.040 make them trustworthy? 45:10.060 --> 45:10.920 What is trustworthiness? 45:11.440 --> 45:15.040 Trustworthiness would be a topic of a chapter at the end of the 45:15.040 --> 45:23.420 course, but it means that if I use a certain service, it should do 45:23.420 --> 45:24.660 what I expect it to do. 45:25.180 --> 45:27.240 And if it does something different, it should tell me. 45:28.580 --> 45:33.360 Because if the system, which is self-organized and adaptive and able 45:33.360 --> 45:38.320 to change its behavior, how do I know that it will do what I would 45:38.320 --> 45:38.980 like it to do? 45:39.640 --> 45:42.740 So, I have to get some experience of using a certain service or 45:42.740 --> 45:43.120 device. 45:43.560 --> 45:48.280 And if it's conforming to my expectations, if it is credible in what 45:48.280 --> 45:51.660 it does, then I put some trust into that system. 45:52.040 --> 45:53.660 Then we can talk about the trustworthiness. 45:53.880 --> 45:56.540 And certainly we would like to have trustworthy systems. 45:56.920 --> 45:58.460 So, when I like a... 45:58.460 --> 46:02.340 when I use certain information systems for getting, for example, train 46:02.340 --> 46:06.260 connections, it's telling me something about departure time. 46:07.220 --> 46:11.320 Then I should be able to trust that these are the real departure 46:11.320 --> 46:11.680 times. 46:11.680 --> 46:17.380 So, nowadays, in a good service, you get also information on delays of 46:17.380 --> 46:17.860 trains. 46:18.880 --> 46:22.260 Then you get really trustworthy systems, because those delays 46:22.260 --> 46:23.520 hopefully are correct. 46:23.980 --> 46:27.840 Then you can use that information in that service in a much better 46:27.840 --> 46:28.080 way. 46:29.300 --> 46:33.640 The important challenge is that we as computer scientists, or business 46:33.640 --> 46:38.360 engineers, or information engineers, we should be those persons who 46:38.360 --> 46:40.120 actually utilize this technology. 46:41.180 --> 46:45.960 So, we should be able to design, manage, and control those unlimited 46:45.960 --> 46:47.620 dynamical networks of devices. 46:48.560 --> 46:55.120 And we should utilize this technology for the utmost benefit to 46:55.120 --> 46:55.480 humans. 46:57.060 --> 47:01.540 Because if it's not beneficial to us, we don't need it. 47:02.320 --> 47:06.640 And if all this technology in our environment is just doing harm to 47:06.640 --> 47:08.220 us, we wouldn't like it. 47:08.240 --> 47:09.540 We wouldn't get rid of it. 47:10.360 --> 47:15.100 But certainly there's quite some potential for designing the systems 47:15.100 --> 47:17.400 such that they extend our capabilities. 47:18.220 --> 47:22.060 And that we get the impression, well, this is really something which 47:22.060 --> 47:24.200 helps me, which is beneficial for me. 47:25.000 --> 47:29.540 If we can manage to design systems in this way, that would be 47:29.540 --> 47:30.340 something which is good. 47:30.660 --> 47:35.000 And since the chance is there, the potential is there, we should 47:35.000 --> 47:39.980 actually do something there and design the appropriate system, the 47:39.980 --> 47:43.980 appropriate concept for coming up with systems that actually are 47:43.980 --> 47:44.820 beneficial to us. 47:45.260 --> 47:48.540 And if they are not, we should be able to just switch them off. 47:49.700 --> 47:56.200 Now, I have sometimes talked to people who design nice fancy systems, 47:56.820 --> 48:01.360 and they said, well, humans should never try to interfere with what 48:01.360 --> 48:02.320 that system does. 48:02.360 --> 48:03.620 It's always doing the right thing. 48:04.020 --> 48:06.560 They should never dare to switch them off. 48:07.380 --> 48:10.260 That shouldn't be allowed, because the system is always doing the 48:10.260 --> 48:10.620 right thing. 48:11.220 --> 48:17.380 If you design a system with that attitude, then you can be sure that 48:17.380 --> 48:18.440 people will like it. 48:19.700 --> 48:23.280 So, you should... 48:23.280 --> 48:29.260 what you see here is there are challenges, and it's a topic that has 48:29.260 --> 48:33.400 not just to do with writing a program, but how a system actually 48:33.400 --> 48:37.940 behaves and how it shows itself to the environment. 48:38.520 --> 48:42.520 Now, let's look at a few scenarios that we have to look at if we talk 48:42.520 --> 48:43.560 about organic computing. 48:44.240 --> 48:48.240 I mentioned those few things like a smart house, for example. 48:48.300 --> 48:49.280 What is a smart house? 48:49.720 --> 48:52.160 A smart house is something which is not that new. 48:52.680 --> 48:56.640 A smart house is a house that has all kinds of home automation 48:56.640 --> 48:57.600 systems. 48:57.960 --> 49:04.280 Sensoring equipment, access, which lets you get the shades down, put 49:04.280 --> 49:07.580 the blinds down, or the... 49:09.720 --> 49:11.120 the blinds, whatever. 49:13.260 --> 49:18.600 Or you have your stove, which is doing what you like, and you just 49:18.600 --> 49:23.680 control it remotely, or when you come into your house, the door opens, 49:23.800 --> 49:25.340 just for you, not for other persons. 49:25.760 --> 49:26.860 So, all kinds of things. 49:26.860 --> 49:29.840 The house knows what you need when you get home. 49:30.960 --> 49:38.080 I was at a conference some time ago, there was somebody talking about 49:38.080 --> 49:41.800 his experiences like he lived for, I think, for two years in a smart 49:41.800 --> 49:46.180 house with his family, and he said it was a very nice experience, but 49:46.180 --> 49:51.940 the bad thing about it was that most of the time, he was looking for 49:51.940 --> 49:56.660 some broken unfunctioning components, some batteries that had to be 49:56.660 --> 50:00.040 replaced, or some things that just didn't work. 50:01.120 --> 50:06.200 So, the more components you have in your house which assist you in 50:06.200 --> 50:10.800 your daily life, the more you get annoyed if one of those services 50:10.800 --> 50:11.440 doesn't work. 50:12.680 --> 50:18.500 Then you are dealing with those devices, and it's taking up your time. 50:19.060 --> 50:19.820 You don't like that. 50:19.960 --> 50:22.800 So, those systems should be self-healing, and things like that. 50:23.420 --> 50:28.480 It's a nice idea, but it should work, operate in a way such that it 50:28.480 --> 50:29.440 only helps you. 50:29.780 --> 50:32.040 It doesn't take your time for maintaining. 50:33.040 --> 50:38.180 So, very small letters here, you have the leaks of what you can look 50:38.180 --> 50:44.360 at more at more detail in typical smart houses. 50:44.860 --> 50:46.740 I said we have a smart home on campus. 50:47.160 --> 50:50.940 We also have a smart home in the House of Living Labs, the Research 50:50.940 --> 50:53.380 Center for Information Technology here at Karlsruhe. 50:54.400 --> 50:59.520 There we concentrate on not on home automation, but on energy 50:59.520 --> 51:01.300 management, energy issues. 51:02.280 --> 51:07.180 If you are interested, as I said, in getting connected to that, just 51:07.180 --> 51:07.820 come to us. 51:07.940 --> 51:12.140 We have jobs available for student assistants, and so on. 51:13.560 --> 51:14.500 What is a smart car? 51:14.780 --> 51:17.820 A smart car fits with electronic equipment. 51:17.820 --> 51:21.640 It adapts to different drivers, the road conditions, to know all that. 51:21.800 --> 51:24.040 It's not that fancy, new, futuristic. 51:25.140 --> 51:26.120 It's daily life. 51:26.800 --> 51:30.920 It gives advice on currently best routes, typical communication with 51:30.920 --> 51:32.260 other cars on special events. 51:32.700 --> 51:37.220 Well, that's not really happening too often that cars are talking to 51:37.220 --> 51:41.880 each other because one car sees an accident and tells the car behind, 51:42.520 --> 51:43.340 hey, there's an accident. 51:44.500 --> 51:45.980 Things like that are conceivable. 51:45.980 --> 51:50.260 And it integrates your personal devices into its network. 51:50.620 --> 51:55.260 Integration of the personal area network and the car area network. 51:56.500 --> 52:03.460 So, as soon as you enter with your smartphone or some device, speaking 52:03.460 --> 52:08.060 Bluetooth, if you enter your car, it connects to the system, then you 52:08.060 --> 52:15.460 can use the system and so actually, that's the future idea of how we 52:15.460 --> 52:18.300 can make a car really smart and provide all kinds of services. 52:18.740 --> 52:19.480 We have a smartphone. 52:20.360 --> 52:24.680 All kinds of services, assistant services for driving and all kinds of 52:24.680 --> 52:27.340 extra fancy services are on your smartphone. 52:28.000 --> 52:32.820 You enter in the car, just an arbitrary car having the interface, and 52:33.580 --> 52:37.300 then it uses the services that you have on your smartphone. 52:38.640 --> 52:43.560 So you have always the same service environment into the car that 52:43.560 --> 52:44.740 supports such an interface. 52:45.480 --> 52:50.780 And then you are not depending on the services that are built into the 52:50.780 --> 52:51.840 car and what to do. 52:53.480 --> 52:53.740 Okay. 52:54.300 --> 52:54.940 Smart factory. 52:55.420 --> 52:57.240 Intelligent control of production. 52:57.480 --> 52:59.860 Also something which is around for some time. 53:01.340 --> 53:02.860 Not always, certainly. 53:03.040 --> 53:05.880 There can always be things that can be done smarter. 53:06.920 --> 53:10.800 And there's quite a bit of research going on in that area. 53:12.500 --> 53:13.580 Smart office. 53:14.680 --> 53:19.060 We are all having our services on our desktop, in our smartphone, all 53:19.060 --> 53:23.200 kinds of things that are assisting us with respect to our timetable, 53:23.580 --> 53:25.480 projects, events, and so on. 53:26.160 --> 53:27.940 Takes care of travel arrangements. 53:28.140 --> 53:30.720 You can use all those services nowadays already. 53:31.480 --> 53:32.500 There's the smart shop. 53:32.580 --> 53:36.980 I mentioned that already that you can have all kinds of things that 53:36.980 --> 53:41.780 you buy in a shop attached with RFID tags. 53:42.160 --> 53:46.800 Then you get all kinds of extra information on what is available on 53:46.800 --> 53:48.040 that specific product. 53:49.000 --> 53:53.540 And you can get more and much more information. 53:53.680 --> 53:59.200 For example, if a bottle of milk has such a tag, it can record the 53:59.200 --> 54:04.500 temperature that was exposed to it on the way from the production site 54:04.500 --> 54:05.940 to the store. 54:06.840 --> 54:07.580 Things like that. 54:08.140 --> 54:13.520 But it certainly can also know and record your shopping preferences. 54:14.940 --> 54:16.860 It can observe your shopping habits. 54:17.680 --> 54:22.200 And we like that if we are living somewhere and we go to the shop next 54:22.200 --> 54:27.880 corner and we are welcomed, oh, hi Bob, nice that you come in and I 54:27.880 --> 54:29.780 know what you need, I have put it there already. 54:30.620 --> 54:31.460 Oh, it's nice. 54:32.540 --> 54:37.320 But if you do that on the internet and it says, oh, hello, I have 54:37.320 --> 54:41.580 there everything that you need, you say, oh, this system is knowing 54:41.580 --> 54:42.500 too much about itself. 54:43.840 --> 54:47.740 And so, the way we perceive those things is different. 54:48.640 --> 54:52.680 So, if a shop is knowing our shopping habits, it might be nice. 54:53.480 --> 54:56.200 It can also be something which we don't like. 54:56.800 --> 54:59.860 But see all kinds of recommendations when you enter, when you go to 54:59.860 --> 55:01.060 Amazon or things like that. 55:01.460 --> 55:04.060 These things are there and are useful. 55:04.880 --> 55:06.040 Then there are smart clothes. 55:06.260 --> 55:10.360 Clothes which behave differently, like now it's getting warm, so the 55:10.360 --> 55:16.900 shirt should show different properties than in the cold days, when it 55:16.900 --> 55:22.380 should keep the temperature so the body should be transparent and so 55:22.380 --> 55:25.400 you should have a warming or a cooling deck. 55:25.980 --> 55:29.520 There are actually material available which is doing that, which is 55:29.520 --> 55:33.060 adapting to the current requirements. 55:34.200 --> 55:38.100 There's also there are clothes which have censoring equipment, which 55:38.100 --> 55:40.480 can record your body function. 55:40.680 --> 55:44.800 This is important for medical purposes. 55:46.160 --> 55:54.640 So, for e-health, record or control, like a patient who is having 55:54.640 --> 55:58.220 heart problems, it can be very important to actually notice 55:58.220 --> 56:01.620 immediately if something has gone wrong, so that the doctor is alerted 56:01.620 --> 56:02.600 if something can be done. 56:03.260 --> 56:05.520 Okay, e-care, also important thing. 56:06.140 --> 56:12.340 So, there are there is clothing available which is having this feature 56:12.340 --> 56:17.180 of checking personal parameters, centering or measuring the current 56:17.180 --> 56:18.900 situation of your body. 56:20.560 --> 56:24.540 I just wanted to show you one kind of wearable system, like wearable 56:24.540 --> 56:25.520 computer system. 56:26.100 --> 56:31.080 An example which had been designed at Zurich in the wearable computing 56:31.080 --> 56:31.440 lab. 56:32.060 --> 56:40.920 Imagine in winter, just one or two weeks ago, you would have been in 56:40.920 --> 56:47.980 the Alps skiing, and you are having censoring equipment. 56:49.340 --> 56:55.360 And these sensors notice, for example, that you are tired. 56:55.700 --> 56:58.060 They tell you, you are tired, be careful. 56:58.660 --> 57:03.300 Because if you are skiing and you are tired, your responses might not 57:03.300 --> 57:05.160 be adequate all the time. 57:05.940 --> 57:12.100 Now, imagine a situation where you had an agreement with some friends 57:12.100 --> 57:13.020 to meet somewhere. 57:13.280 --> 57:16.540 Now you see, oh, I'm in a hurry, I don't want to slow down. 57:17.620 --> 57:22.760 And this communication equipment that you wear in your pocket is 57:22.760 --> 57:23.860 communicating with your friends. 57:23.980 --> 57:26.260 You see, oh, there's a disappointment with the friends. 57:26.900 --> 57:34.860 And it's talking to that other device that is here in the clothing of 57:35.880 --> 57:36.820 those friends. 57:37.100 --> 57:40.280 And the system tells you, your friends will also be late to the 57:40.280 --> 57:40.720 meeting point. 57:41.320 --> 57:42.020 So, don't worry. 57:43.220 --> 57:48.080 And then the system knows where you want to go, and it checks with the 57:48.760 --> 57:54.360 station, with the some controller station here, about the routes that 57:54.360 --> 57:58.380 it can take to the point where you want to go, and it says, well, you 57:58.380 --> 58:01.280 are tired, so take the right route. 58:01.460 --> 58:02.320 There's an alternative. 58:02.580 --> 58:07.120 Take the route that is easier to take, it's in better condition, and 58:07.120 --> 58:09.300 so it's better because you are tired at the moment. 58:09.720 --> 58:11.340 It's more advisable to take that route. 58:12.080 --> 58:15.800 And this is just done by the devices that you are wearing on your 58:15.800 --> 58:16.040 body. 58:17.120 --> 58:17.740 Nice idea. 58:19.120 --> 58:25.620 Maybe not always nice, but it can be some assistant service that could 58:25.620 --> 58:26.760 help us in doing things. 58:27.320 --> 58:30.460 Not just in professional life, but also in private life. 58:31.220 --> 58:34.140 Okay, so this is just-in-time information, anytime, anyplace. 58:34.880 --> 58:41.080 And so, this is the kind of scenario that could be looked at in this 58:41.080 --> 58:41.440 area. 58:41.440 --> 58:49.400 Let me just look a bit closer at a car that is intelligent, a smart 58:49.400 --> 58:49.880 car. 58:50.920 --> 58:55.760 So, this is a rather old car, already something like eight years old, 58:55.780 --> 58:56.620 or something like that. 58:56.920 --> 59:00.400 So, nowadays they even look more fancy, but what they have, like here 59:00.400 --> 59:07.180 in that car, they had about 80 control units, and what do we need all 59:07.180 --> 59:09.220 these processors and embedded systems for? 59:09.220 --> 59:12.700 So, they are needed nowadays to keep the vehicle on the road. 59:13.660 --> 59:18.900 Easy driving, a complex car, is possible because of those controllers. 59:20.120 --> 59:25.180 You have ESP and all kinds of these driving assistant systems, driving 59:25.180 --> 59:26.680 assistant controllers. 59:27.580 --> 59:31.280 There is a controller available for controlling the engine. 59:32.060 --> 59:35.100 Combustion, pollution control, the behavior. 59:35.240 --> 59:37.380 Is it more sporty, or more comfortable? 59:38.060 --> 59:42.080 There are about 2,000 threads controlling the engine. 59:42.340 --> 59:45.980 Or 200,000 lines of code that control an engine. 59:46.500 --> 59:47.240 An engine. 59:47.760 --> 59:51.260 That's just a physical device, but there's no logic in there. 59:51.800 --> 59:53.200 There's lots of logic in there. 59:53.800 --> 01:00:02.340 Like the engine can be just adjusted for the kind of characteristic 01:00:02.340 --> 01:00:04.940 that it should have for a specific car. 01:00:04.940 --> 01:00:07.240 And for a specific type of car. 01:00:08.040 --> 01:00:13.860 So, there's a lot of intelligence in there, the way the engine 01:00:13.860 --> 01:00:14.740 actually is controlled. 01:00:15.260 --> 01:00:19.260 Persists the driver for steering, braking, accelerating. 01:00:21.420 --> 01:00:28.640 Just turn the wheel, but this is transformed into something which is 01:00:28.640 --> 01:00:29.980 carried out by electronics. 01:00:30.700 --> 01:00:33.780 There are words like steer by wire, brake by wire. 01:00:34.240 --> 01:00:41.040 When you push the brake, you just start some information processing 01:00:41.040 --> 01:00:44.960 process, and this resides in braking. 01:00:45.920 --> 01:00:50.260 But it's not necessarily a direct mechanical connection between your 01:00:50.260 --> 01:00:52.760 brake pedal and the brake. 01:00:54.580 --> 01:00:57.780 So, this is quite a requirement on software. 01:00:58.780 --> 01:01:01.360 Accelerating, things like that, also very important. 01:01:02.620 --> 01:01:07.720 Or in, for example, in electronic cars, when you push the brake, it's 01:01:07.720 --> 01:01:08.380 recuperating. 01:01:09.260 --> 01:01:11.760 And if you push it a bit more, it's recuperating more. 01:01:12.600 --> 01:01:14.160 Like, retrieving energy. 01:01:15.100 --> 01:01:18.320 And then, if you push it more, it's physically braking. 01:01:19.060 --> 01:01:21.820 This is only done, only possible by electronics. 01:01:23.240 --> 01:01:25.600 Then, to keep track of external conditions. 01:01:26.140 --> 01:01:28.000 What kind of things happen outside? 01:01:28.660 --> 01:01:30.240 To provide security. 01:01:30.980 --> 01:01:35.160 If you're noticing, oh, the car is approaching another car very fast 01:01:35.160 --> 01:01:39.380 with some obstacle, it would be good to switch off all the electronic 01:01:39.380 --> 01:01:41.900 components just before the car is crashing. 01:01:42.400 --> 01:01:46.260 Because otherwise it will ignite or it will get fired. 01:01:47.200 --> 01:01:49.320 The systems do that currently. 01:01:49.480 --> 01:01:53.180 Like, if you are having an accident, the smart cars are doing that. 01:01:53.280 --> 01:01:55.040 Most of the cars employ know how to do that. 01:01:55.040 --> 01:01:59.180 They just switch off just before the crash. 01:02:00.220 --> 01:02:00.980 That's security. 01:02:01.300 --> 01:02:05.700 Or the airbags have to be put in action. 01:02:05.820 --> 01:02:06.340 Things like that. 01:02:06.400 --> 01:02:08.300 Seatbelts should be tightened. 01:02:08.660 --> 01:02:12.720 All these things are happening when you have a special situation. 01:02:13.540 --> 01:02:15.760 And then there are all kinds of comfort functions. 01:02:16.060 --> 01:02:17.020 Air, seat conditioning. 01:02:17.660 --> 01:02:19.320 Just in a... 01:02:19.320 --> 01:02:25.860 The seat of a higher class car is having something like 30-40 01:02:25.860 --> 01:02:26.960 different controls. 01:02:28.300 --> 01:02:30.360 Many different things can do there in the seat. 01:02:31.480 --> 01:02:37.320 Navigation, parking assistant can just tell the car to park in the 01:02:37.320 --> 01:02:37.980 parking lot. 01:02:38.820 --> 01:02:40.180 I had a piece like that in my car. 01:02:40.240 --> 01:02:42.800 I never tried it so far because I don't dare to do that. 01:02:42.960 --> 01:02:44.100 But I should do it. 01:02:44.340 --> 01:02:47.400 But I don't trust it that it will actually do it in real life. 01:02:47.460 --> 01:02:50.720 So I should go somewhere where I can do that without harming anyone. 01:02:50.720 --> 01:02:51.580 OK. 01:02:52.080 --> 01:02:52.860 Information service. 01:02:53.080 --> 01:02:53.800 All kinds of things. 01:02:55.240 --> 01:02:56.340 To entertain the driver. 01:02:57.160 --> 01:02:59.420 If it's safe to do that. 01:02:59.640 --> 01:03:00.180 Infotainment. 01:03:00.420 --> 01:03:03.460 It would be better to entertain the passenger sitting in the backseat. 01:03:03.820 --> 01:03:04.420 Not the driver. 01:03:04.660 --> 01:03:06.800 The driver should pay attention to the traffic. 01:03:07.960 --> 01:03:08.980 And whatever you like. 01:03:09.520 --> 01:03:14.240 Many different functions that we need or that we provide in the car. 01:03:14.460 --> 01:03:15.780 Not everything is needed really. 01:03:16.280 --> 01:03:17.600 But it's in there. 01:03:18.080 --> 01:03:21.360 And so all these controllers have to communicate. 01:03:22.180 --> 01:03:23.400 And it's a very complex network. 01:03:24.300 --> 01:03:26.240 Now something is going wrong there. 01:03:27.480 --> 01:03:28.620 Certain functions are not available. 01:03:29.660 --> 01:03:30.760 Things shouldn't go wrong. 01:03:30.940 --> 01:03:34.220 In particular security features safety features shouldn't go wrong. 01:03:35.080 --> 01:03:39.700 And so this is still called an electric-electronic architecture from 01:03:39.700 --> 01:03:44.480 the old days where it was only to do with electricity and electronics. 01:03:45.120 --> 01:03:47.720 Now it should be called a service-oriented architecture. 01:03:49.200 --> 01:03:53.080 But that would mean that computer scientists have to design that. 01:03:53.740 --> 01:03:59.420 Car designers say, oh, please, don't let the computer scientists do 01:03:59.420 --> 01:04:00.320 something in the car. 01:04:00.680 --> 01:04:01.660 But they know things. 01:04:02.140 --> 01:04:03.660 And they have to do certain things. 01:04:04.300 --> 01:04:07.900 Obviously, this is a very complex network. 01:04:08.120 --> 01:04:12.400 And if you design that, how can you make sure that everything here is 01:04:12.400 --> 01:04:13.080 functionally correct? 01:04:13.240 --> 01:04:16.860 If you put in a component here, how do you know that it will not 01:04:16.860 --> 01:04:19.760 interact with some other component and things go wrong? 01:04:20.380 --> 01:04:25.320 So there has been an example a simple example where people design a 01:04:25.320 --> 01:04:26.860 nice system. 01:04:27.480 --> 01:04:30.260 So there was this ramp here. 01:04:30.500 --> 01:04:31.420 There was a door. 01:04:32.320 --> 01:04:33.740 Let me just draw it like this. 01:04:34.620 --> 01:04:38.880 And there was a car that was trying to get in there. 01:04:39.860 --> 01:04:45.460 And now when you are going down a ramp into a garage, usually there is 01:04:45.460 --> 01:04:47.680 some device where you have to identify yourself. 01:04:48.120 --> 01:04:50.660 So somebody had a car which was a very smart car. 01:04:51.200 --> 01:04:57.200 There was a parking brake which at the moment where the engine was 01:04:57.200 --> 01:05:01.400 accelerating, at the moment you push the gas pedal, you say, okay, the 01:05:01.400 --> 01:05:04.780 driver would like to go, so the parking brake is released. 01:05:06.140 --> 01:05:10.720 So another nice device in there, an air conditioning system, which 01:05:10.720 --> 01:05:13.100 would measure the temperature inside the car. 01:05:13.860 --> 01:05:20.160 And if it gets too warm inside, it would provide more surface. 01:05:20.880 --> 01:05:25.940 So, since to really cool the car down, if it's getting hot inside, you 01:05:25.940 --> 01:05:27.020 have to accelerate the engine. 01:05:27.760 --> 01:05:33.640 So a person pushed the parking brake here, the car stopped, what is 01:05:33.640 --> 01:05:37.740 certainly very steep, not that steep usually, but and he had to leave 01:05:37.740 --> 01:05:42.340 the car, left the door open, because it was a hot day, he didn't reach 01:05:42.340 --> 01:05:47.460 the place where he had to identify himself, he left the car, he pushed 01:05:47.460 --> 01:05:52.220 the brake, and the sensory equipment inside noticed, oh, it's getting 01:05:52.220 --> 01:05:56.360 warmer, and the engine was accelerated in order to provide more air 01:05:56.360 --> 01:05:59.480 conditioning service, the parking brake said, oh, the car wants to 01:05:59.480 --> 01:06:01.920 drive, and so it crashed. 01:06:03.840 --> 01:06:04.960 Things like that happen. 01:06:05.440 --> 01:06:09.540 Interaction of components, which has been designed in a very nice way, 01:06:10.280 --> 01:06:15.680 but the interaction, it's a silly interaction here, but that was a 01:06:15.680 --> 01:06:19.260 real example that things like that can happen. 01:06:19.560 --> 01:06:25.500 Or there's the example of a car sitting at the curve of a street, and 01:06:25.500 --> 01:06:33.460 there's this lamp, which is electronically controlled, and somebody 01:06:33.460 --> 01:06:37.840 parked his car close to that lamp, and in the morning the battery was 01:06:37.840 --> 01:06:38.080 empty. 01:06:38.920 --> 01:06:45.320 The reason was that the electronics in the lamp and the electronics in 01:06:45.320 --> 01:06:53.340 the car were communicating somehow, and the mechanism for locking and 01:06:53.340 --> 01:07:02.120 unlocking the door somehow was initiated, was triggered, so this 01:07:02.120 --> 01:07:07.780 function was going on all the time, and the car battery was empty. 01:07:09.240 --> 01:07:12.620 Things like that happen, just because of interaction of components. 01:07:13.320 --> 01:07:18.040 And even if you have tested certain components together with some 01:07:18.040 --> 01:07:21.240 other components, if there are many of them available, you might run 01:07:21.240 --> 01:07:21.720 into problems. 01:07:22.480 --> 01:07:25.920 So this is the reason why people have to talk about these topics. 01:07:28.680 --> 01:07:29.200 Okay. 01:07:29.460 --> 01:07:32.820 Then the question is, so who can manage the complexity of such a 01:07:32.820 --> 01:07:32.980 network? 01:07:33.460 --> 01:07:38.700 Car designers are the limits of what they can really design. 01:07:39.180 --> 01:07:42.040 Who can guarantee that there's no unintended interference between 01:07:42.040 --> 01:07:46.680 components of this or other, of this car, or of other cars or 01:07:46.680 --> 01:07:47.140 networks? 01:07:47.460 --> 01:07:49.560 That's the emergent behavior, just to give an example. 01:07:50.200 --> 01:07:51.660 Who's actually controlling the car? 01:07:51.980 --> 01:07:55.680 If you have a smart car, you have all this systems, systems. 01:07:56.620 --> 01:07:59.700 Are you, as a driver, really controlling what it's doing? 01:08:01.600 --> 01:08:06.960 If there is some service which is taking over control of the car, is 01:08:06.960 --> 01:08:09.080 the system responsible if something happens? 01:08:10.160 --> 01:08:10.940 I didn't do it. 01:08:11.000 --> 01:08:11.720 The system did it. 01:08:12.540 --> 01:08:17.460 Like, if I use the parking, like the parking systems, driving into a 01:08:17.460 --> 01:08:23.360 parking lot, if an accident is happening there, I did drive the car 01:08:23.360 --> 01:08:25.320 door, so the car is responsible. 01:08:26.220 --> 01:08:27.300 That's a difficult question. 01:08:27.920 --> 01:08:31.220 Or some external entity, somebody is remotely controlling my car. 01:08:32.600 --> 01:08:35.180 How can you make sure that things like that don't happen? 01:08:35.440 --> 01:08:39.020 So there are lots of questions around that, and that's a reason why 01:08:39.020 --> 01:08:43.760 quite a few of those services which could, in principle, be in the 01:08:43.760 --> 01:08:49.040 car, be available there for a long time already, are not there because 01:08:49.040 --> 01:08:54.240 the car manufacturers say, well, liability is a problem, and we just 01:08:54.240 --> 01:08:59.480 provide things which have to be explicitly initiated by the driver. 01:09:00.100 --> 01:09:01.640 Then the driver is responsible. 01:09:02.680 --> 01:09:07.380 Things that are done autonomously always carry the question of who is 01:09:07.380 --> 01:09:10.460 actually liable in case of some problem. 01:09:11.880 --> 01:09:16.380 So who is responsible for malfunctioning of the car, producer, driver, 01:09:16.680 --> 01:09:17.380 or the system. 01:09:19.260 --> 01:09:23.340 Then, in the smart shop, I told you that already there are these RFID 01:09:23.340 --> 01:09:28.780 tags which lead to acceptance problems, and so customers are afraid of 01:09:28.780 --> 01:09:29.580 being controlled. 01:09:30.320 --> 01:09:36.500 We have to look at privacy protection and, you know, who of you have 01:09:36.500 --> 01:09:38.760 read the book by Orville, 1984? 01:09:40.400 --> 01:09:41.140 You know that book? 01:09:42.500 --> 01:09:43.400 Nobody else? 01:09:44.120 --> 01:09:50.840 Very interesting book on the system, on the state, on the government, 01:09:51.320 --> 01:09:53.160 which is completely controlling everything. 01:09:54.440 --> 01:10:00.780 And so if I say Orville, well, Orville is the author of that book, and 01:10:00.780 --> 01:10:06.880 it's the book 1984, and we don't like to be controlled. 01:10:07.000 --> 01:10:10.080 We are actually controlled to some extent, meanwhile. 01:10:10.780 --> 01:10:18.980 Like, if you apply for a job, for example at Google, and you send your 01:10:18.980 --> 01:10:26.420 CV, or your material to Google, they get thousands of applications. 01:10:27.360 --> 01:10:29.900 And they just check what they know about the person. 01:10:30.680 --> 01:10:35.500 And if what they know is different from what they see in the CV they 01:10:35.500 --> 01:10:37.100 got, that's a problem. 01:10:38.540 --> 01:10:41.740 So the application is a problem, not what they know is a problem. 01:10:43.060 --> 01:10:49.540 And so, there are quite a few institutions which know quite a bit 01:10:49.540 --> 01:10:50.280 about themselves. 01:10:51.120 --> 01:10:54.140 And so Orville is not that far away, really. 01:10:54.560 --> 01:10:58.200 But we have to make sure that we still have or can make sure that we 01:10:58.200 --> 01:11:04.160 follow the right of like the information that is accessible, the right 01:11:04.160 --> 01:11:10.760 to control your information life. 01:11:12.700 --> 01:11:18.860 Now, we look at all these problems, like actually in the what is the 01:11:18.860 --> 01:11:23.700 GEE, the Gesellschaft der Informatik, the Association for Informatics 01:11:23.700 --> 01:11:29.820 in Germany, and the Information Technical Society, we looked at, like, 01:11:30.220 --> 01:11:34.820 more than ten years ago, we looked at the challenges for research. 01:11:35.440 --> 01:11:39.720 At a time that is about ten years or something in the future. 01:11:40.780 --> 01:11:44.860 And we discussed what are actually the challenges that we have to 01:11:44.860 --> 01:11:49.740 address, and it was obvious that we will get all these conflicted 01:11:49.740 --> 01:11:56.260 systems around us, and that we should try to make sure that we don't 01:11:56.260 --> 01:11:58.800 get caught in this new world. 01:12:00.700 --> 01:12:04.720 So, the computer systems have to be designed with respect to human 01:12:04.720 --> 01:12:05.940 needs, definitely. 01:12:06.760 --> 01:12:08.960 They should be trustworthy. 01:12:09.800 --> 01:12:12.120 They have to be robust, adaptive, and flexible. 01:12:13.360 --> 01:12:17.260 And if you have a system like that, you would say, well, this is 01:12:17.260 --> 01:12:23.240 something that could be adaptable, flexible, robust, and trustworthy. 01:12:23.660 --> 01:12:28.060 Something which is similar to things that are really living. 01:12:28.800 --> 01:12:30.500 So, some life-like property. 01:12:31.260 --> 01:12:34.520 Because of that, we call them organic computer systems. 01:12:35.100 --> 01:12:39.200 So, it's the behavior of the system, which is of interest to us. 01:12:40.020 --> 01:12:42.700 Those are the organic computer systems. 01:12:43.960 --> 01:12:47.960 And the history of that, long history of all kinds of research 01:12:47.960 --> 01:12:52.720 programs, which are mentioned to some extent already, like ubiquitous 01:12:52.720 --> 01:12:59.140 computing, is one topic having to do with the presence of computers, 01:12:59.220 --> 01:13:02.280 or the availability of computing in many different places. 01:13:02.960 --> 01:13:08.660 So, Mark Weiser came up with that vision of ubiquitous computing quite 01:13:08.660 --> 01:13:10.320 some time ago, more than 30 years ago. 01:13:11.020 --> 01:13:15.440 Intelligent Autonomous Systems is actually a division of Siemens, 01:13:15.540 --> 01:13:17.520 which was founded in 1994. 01:13:18.340 --> 01:13:20.000 They did quite a bit of research on that. 01:13:20.560 --> 01:13:24.280 Pervasive computing is a term that was coined by IBM. 01:13:25.360 --> 01:13:27.900 They didn't like ubiquitous computing, but meant the same. 01:13:27.900 --> 01:13:31.920 They needed their own name for that. 01:13:32.380 --> 01:13:35.560 So, they said it's pervasive computing, which certainly also addresses 01:13:35.560 --> 01:13:36.580 a different aspect. 01:13:36.800 --> 01:13:41.860 Pervasive means that information processing is really penetrating all 01:13:41.860 --> 01:13:46.700 kinds of objects in our environment. 01:13:47.200 --> 01:13:50.420 Every aspect of our life is there. 01:13:50.540 --> 01:13:51.940 There's pervasive computing. 01:13:52.300 --> 01:13:54.900 It's getting in everything. 01:13:54.900 --> 01:14:00.200 And then there was this Autonomic Computing Initiative by IBM at the 01:14:00.200 --> 01:14:01.840 start of this century. 01:14:03.860 --> 01:14:05.880 Self-ex property for server architecture. 01:14:06.120 --> 01:14:11.200 IBM is now providing technology for enterprise server systems. 01:14:12.020 --> 01:14:15.260 And they noticed that they're getting so complex that it's important 01:14:15.260 --> 01:14:19.900 to, for example, do the standard maintenance jobs. 01:14:20.460 --> 01:14:23.400 In some way, standardized, automated way. 01:14:24.280 --> 01:14:30.380 So, they came up with a vision of server architecture like of a data 01:14:30.380 --> 01:14:34.880 center management system, which would do certain things on its own. 01:14:35.420 --> 01:14:38.020 Self-protect against viruses and so on. 01:14:38.120 --> 01:14:41.400 Self-configure, self-optimize, and so on. 01:14:42.320 --> 01:14:44.000 I will come back to that a bit later. 01:14:44.800 --> 01:14:50.300 Then I mentioned the problems people had with cars like Daimler 01:14:50.300 --> 01:14:54.860 Chrysler started something called the Evolutionary Architecture for 01:14:54.860 --> 01:14:55.300 Cars. 01:14:55.800 --> 01:15:00.740 They didn't really follow it for a long time, but they were quite 01:15:00.740 --> 01:15:03.740 aware of the complexity of the system and how they could actually 01:15:03.740 --> 01:15:07.180 evolve the properties of future cars. 01:15:08.080 --> 01:15:14.300 Then there was an initiative for organic computing, not by that 01:15:14.820 --> 01:15:18.640 sequence of workshops that I mentioned, but by Christoph von der Maas' 01:15:18.680 --> 01:15:25.440 book, who actually came up with that notion based on his vision of or 01:15:25.440 --> 01:15:28.880 his knowledge of neural systems, like neurological systems, 01:15:29.800 --> 01:15:36.160 neurosciences, molecular biology, and they actually were motivated by 01:15:36.160 --> 01:15:39.740 the things that happen in our living body. 01:15:41.020 --> 01:15:47.460 By the way, this term autonomic computing is well chosen, the term 01:15:47.460 --> 01:15:52.460 autonomic, because autonomic refers to the autonomic system, which is 01:15:52.460 --> 01:15:54.680 the nervous system of the body. 01:15:55.320 --> 01:15:58.580 The human body has a so-called nervous system, it's called the 01:15:58.580 --> 01:15:59.560 autonomic system. 01:16:00.600 --> 01:16:05.700 And the specific features are that most of the life-dependent things, 01:16:05.980 --> 01:16:10.340 essential things, are done unconsciously. 01:16:10.720 --> 01:16:15.380 Like breathing, heartbeat and so on, we don't control it, we don't go, 01:16:15.420 --> 01:16:17.020 oh, now, beep, beep, beep. 01:16:17.920 --> 01:16:18.880 It's doing that. 01:16:19.800 --> 01:16:22.460 But if we like to, we can stop breathing. 01:16:24.280 --> 01:16:24.460 Yeah? 01:16:24.760 --> 01:16:25.940 If we like to, we can do that. 01:16:26.040 --> 01:16:26.980 Not for a long time. 01:16:27.320 --> 01:16:29.240 If we do it too long, we run into problems. 01:16:29.800 --> 01:16:34.360 But we can control, to some extent, we can do things consciously. 01:16:35.100 --> 01:16:36.620 But normally, we're not doing that. 01:16:37.420 --> 01:16:38.760 It's just so nightly. 01:16:39.340 --> 01:16:42.100 But if we like to, we can control certain things. 01:16:42.160 --> 01:16:46.300 And this is what actually was the structure of the term autonomic 01:16:46.300 --> 01:16:47.040 computing. 01:16:47.220 --> 01:16:51.720 Although, it also has the meaning that it is an autonomous system, 01:16:51.980 --> 01:16:55.300 which can do everything on its own, and it doesn't need interference. 01:16:56.560 --> 01:16:58.640 I'll come back to those issues a bit later. 01:16:59.880 --> 01:17:01.600 Then we had organic IT. 01:17:02.640 --> 01:17:07.360 Forrester Research, a consulting company, they came up with a research 01:17:07.360 --> 01:17:11.860 company providing reports on trends in the industry. 01:17:12.140 --> 01:17:14.860 They came up with the notion of organic IT. 01:17:15.000 --> 01:17:18.980 They said, server architecture, server systems, should evolve and 01:17:18.980 --> 01:17:20.100 should become organic. 01:17:20.900 --> 01:17:26.420 They meant exactly what I just mentioned before, this organic behavior 01:17:26.420 --> 01:17:30.420 should be adaptive, should have these self-ex features. 01:17:30.880 --> 01:17:34.940 They were also mentioned by IBM, the Autonomic Computing Program. 01:17:35.480 --> 01:17:39.780 Then we came up with organic computing, and we're lucky to get the 01:17:39.780 --> 01:17:43.520 priority program of the German Research Foundation, which ran for six 01:17:43.520 --> 01:17:46.640 years, and was an interesting program. 01:17:47.320 --> 01:17:51.180 And nowadays people talk quite a bit about cyber physical systems. 01:17:52.100 --> 01:17:57.300 Cyber physical systems refer to that you have all kinds of physical 01:17:57.300 --> 01:18:01.060 systems, which have embedded devices, cyber systems. 01:18:01.760 --> 01:18:05.700 Now the problem is, what the cyber system says, and one would like to 01:18:05.700 --> 01:18:12.100 control, is not really put into action in the real world, because 01:18:12.100 --> 01:18:13.400 there are physical constraints. 01:18:14.220 --> 01:18:20.280 Like there is a typical example, if you have a robot, maybe it's a 01:18:20.280 --> 01:18:25.600 robot having two wheels, you can easily let it go straight. 01:18:26.280 --> 01:18:27.040 Go straight. 01:18:28.020 --> 01:18:31.240 In simulation, it's going straight. 01:18:31.760 --> 01:18:34.260 In reality, it's going like that. 01:18:34.260 --> 01:18:35.060 Why? 01:18:36.160 --> 01:18:38.560 Because there are small obstacles on the ground. 01:18:39.580 --> 01:18:44.020 There are slight deviations in the turning speed of the wheels, so 01:18:44.020 --> 01:18:49.040 it's very hard to actually let a robot drive straight. 01:18:50.560 --> 01:18:53.360 You can do experiments with that in our group. 01:18:53.460 --> 01:19:00.160 We have a robot arena in our institute where you can run experiments 01:19:00.160 --> 01:19:00.900 with those robots. 01:19:00.900 --> 01:19:04.060 And it's an interesting experience to see what you can do in 01:19:04.060 --> 01:19:08.800 simulation and what they do when they are on their arena and moving 01:19:08.800 --> 01:19:09.140 there. 01:19:09.860 --> 01:19:16.060 And cyber-physical systems actually is now a funding program of the 01:19:16.060 --> 01:19:16.720 federal government. 01:19:17.540 --> 01:19:23.360 It's also a funding program in North America and in Germany it's 01:19:23.360 --> 01:19:25.860 currently called the funding program Industry TNO. 01:19:27.220 --> 01:19:34.520 So, having to do with all this economic control embedded systems in 01:19:35.060 --> 01:19:39.700 industrial processes where we have exactly that problem of cyber 01:19:39.700 --> 01:19:44.120 -systems and their interactions with physical systems. 01:19:45.220 --> 01:19:50.920 So, when we talk about organic computing we are talking about a nice 01:19:50.920 --> 01:19:56.440 vision of systems, but it's not the question whether adaptive and self 01:19:56.440 --> 01:19:57.960 -organizing systems will emerge. 01:19:58.400 --> 01:19:59.480 They will be there anyway. 01:20:00.380 --> 01:20:04.500 The major challenge is how they actually will be designed and 01:20:04.500 --> 01:20:04.940 controlled. 01:20:05.920 --> 01:20:12.980 And so, it's our challenge to provide the concept, the architecture, 01:20:13.160 --> 01:20:18.300 the methods, such that those adaptive and self-organizing systems 01:20:18.860 --> 01:20:19.680 behave nicely. 01:20:20.620 --> 01:20:23.060 That we feel, oh, they are really beneficial. 01:20:23.060 --> 01:20:30.600 If we don't do that job well, we might be confronted with systems 01:20:30.600 --> 01:20:34.400 which are self-adaptive and self-organizing and we don't like what 01:20:34.400 --> 01:20:34.820 they are doing. 01:20:35.900 --> 01:20:38.380 So, we need the right concept for that. 01:20:38.660 --> 01:20:39.620 It's a real challenge. 01:20:39.660 --> 01:20:40.460 We have to do that. 01:20:41.560 --> 01:20:44.640 And so, we worked on that for several years, came up with certain 01:20:44.640 --> 01:20:45.000 ideas. 01:20:45.520 --> 01:20:50.560 We are not really in the position to say, now we have the organic 01:20:50.560 --> 01:20:51.040 system. 01:20:51.040 --> 01:20:55.420 There are certain systems which behave quite nicely, but there are all 01:20:55.420 --> 01:20:58.900 kinds of questions that have to be looked at, all kinds of questions 01:20:58.900 --> 01:21:04.540 with respect to the type of control that might be necessary, the kind 01:21:04.540 --> 01:21:08.700 of architectures observer controller may or whatever operator 01:21:08.700 --> 01:21:14.340 controller or what kind of policies would be like, or many questions 01:21:14.960 --> 01:21:16.120 that have to be looked at. 01:21:17.060 --> 01:21:21.220 So, to say what we would like to get in an organic computer system 01:21:21.220 --> 01:21:25.960 which will possess all those life-like properties, should consist of 01:21:25.960 --> 01:21:29.120 autonomous systems which do things on their own. 01:21:30.960 --> 01:21:36.360 So, we work as much as possible in a self-organized way, but will also 01:21:36.360 --> 01:21:38.040 adapt to human needs. 01:21:38.660 --> 01:21:43.520 Should be robust, adaptive and flexible, should be controlled by 01:21:43.520 --> 01:21:44.200 objectives. 01:21:44.800 --> 01:21:45.540 That's a nice idea. 01:21:46.160 --> 01:21:48.700 I just tell my computer what it should do, and it will do it. 01:21:49.140 --> 01:21:50.180 I don't tell it how. 01:21:51.160 --> 01:21:51.980 Is that real? 01:21:52.760 --> 01:21:53.580 Can that happen? 01:21:54.540 --> 01:21:57.060 Well, we are working, for example, on evolutionary algorithms. 01:21:58.300 --> 01:22:02.300 And there we tell what kind of system we'd like to get. 01:22:02.820 --> 01:22:06.660 And the system is experimenting until it finally gets the system which 01:22:06.660 --> 01:22:08.300 is doing what we'd like it to do. 01:22:09.180 --> 01:22:15.200 So, in our systems where we project a traffic control, a traffic light 01:22:15.200 --> 01:22:22.180 patrol, we tell the system, you should minimize the number of stops 01:22:22.820 --> 01:22:24.680 and the driving time. 01:22:25.980 --> 01:22:26.980 And the system does it. 01:22:27.040 --> 01:22:31.300 Even if it's starting without any rules, there's certainly methodology 01:22:31.300 --> 01:22:37.240 in there, and it will generate a set of rules such that it has 01:22:37.240 --> 01:22:41.820 actually optimized green phases and will actually even provide a 01:22:41.820 --> 01:22:47.800 system where we have green phases, or progressive signal systems, as 01:22:47.800 --> 01:22:51.660 the official name is, which come up wherever it's necessary. 01:22:52.040 --> 01:22:56.600 If it's reasonable, in order to reduce the number of stops in the 01:22:56.600 --> 01:23:02.620 whole street system, then you get a certain sequence of traffic lights 01:23:02.620 --> 01:23:03.580 which are synchronized. 01:23:04.700 --> 01:23:08.800 And this is something which can be done by the system on its own. 01:23:08.900 --> 01:23:09.960 Actually, we just tell it. 01:23:09.960 --> 01:23:13.840 Certainly, we have put all kinds of intelligence in there, such that 01:23:13.840 --> 01:23:14.780 it's able to do that. 01:23:15.720 --> 01:23:17.940 But, normally, it's a very difficult problem. 01:23:18.220 --> 01:23:21.420 We are far away from actually being able to do that. 01:23:21.800 --> 01:23:27.040 We know that there are certain nice features somewhere in some devices 01:23:27.040 --> 01:23:31.400 where you can tell something and they will respond reasonably, but 01:23:31.400 --> 01:23:33.780 it's still quite a challenge. 01:23:34.360 --> 01:23:36.720 So, self-organization is an important issue. 01:23:37.340 --> 01:23:42.320 We will have all kinds of X-features, self-configuring, self 01:23:42.320 --> 01:23:47.080 -optimizing, self-healing, in case there are some diseases or faults, 01:23:47.180 --> 01:23:49.060 self -protecting, self-explaining. 01:23:49.520 --> 01:23:53.440 Also important that the system explains what it's doing and not just 01:23:53.440 --> 01:23:56.240 doing things on its own, and then we have to live with that. 01:23:58.100 --> 01:24:02.660 In Germany, I told you, we had that research framework, just two more 01:24:02.660 --> 01:24:08.560 slides, where we worked on all kinds of aspects on fundamental 01:24:08.560 --> 01:24:12.960 research on self-organization and organic computing. 01:24:13.440 --> 01:24:18.160 We designed the toolbox of systems of architecture for organic 01:24:18.160 --> 01:24:22.180 computing, and we always had in mind technical applications. 01:24:22.540 --> 01:24:23.520 I mentioned traffic. 01:24:24.340 --> 01:24:28.760 Now we are working very much on energy problems, energy systems, and 01:24:28.760 --> 01:24:31.640 apply our organic computing systems there. 01:24:31.900 --> 01:24:35.980 We looked at many different application areas, and also looked at 01:24:35.980 --> 01:24:36.440 nature. 01:24:37.320 --> 01:24:41.120 So, organic computing also has to do something with nature, because 01:24:41.120 --> 01:24:43.300 there we see self-organizing systems. 01:24:43.920 --> 01:24:47.880 And if we notice something which is nice, working nicely in nature, 01:24:48.560 --> 01:24:52.840 maybe we can use the way it's functioning there in order to design our 01:24:52.840 --> 01:24:53.620 technical systems. 01:24:54.460 --> 01:24:59.740 And so, it's reasonable to look at what nature does, but we should 01:24:59.740 --> 01:25:05.220 certainly design things such that they are best, or working in the 01:25:05.220 --> 01:25:07.580 best way, in the technical life. 01:25:08.060 --> 01:25:08.240 Okay. 01:25:08.580 --> 01:25:13.220 We had many projects in that research program. 01:25:13.800 --> 01:25:18.060 You can just look at them, and you can go to the website of that 01:25:18.060 --> 01:25:23.380 program, and you can look at what kind of material was in there. 01:25:23.480 --> 01:25:24.840 The presentations are all available. 01:25:25.400 --> 01:25:26.020 You can look it up. 01:25:27.020 --> 01:25:30.920 And next time, Vanas Moskvagi will have the task to finish up this 01:25:30.920 --> 01:25:35.540 chapter on a few more interpretations of organic computing, which 01:25:35.540 --> 01:25:41.320 sometimes I'm not really grasping what organic computing is about. 01:25:41.520 --> 01:25:45.340 I don't have the time to continue today, so thank you for your 01:25:45.340 --> 01:25:45.720 attention. 01:25:46.080 --> 01:25:50.020 Hope to see you again in the next lectures next week. 01:25:50.140 --> 01:25:52.060 As I said, Vanas Moskvagi will do this. 01:25:52.760 --> 01:25:55.280 Thanks for today, and have a good week.