WEBVTT - Cognitive Buildings 0:00:00.160 --> 0:00:07.200 Brought to you by Toyota. Let's go places. Welcome to 0:00:07.360 --> 0:00:14.600 Forward Thinking. Hey there, and welcome to Forward Thinking, the 0:00:14.760 --> 0:00:17.360 podcast that looks at the future and says, I'm an 0:00:17.440 --> 0:00:21.520 ordinary guy burning down the house. I'm Jonathan Strickland, I'm Lauren, 0:00:22.160 --> 0:00:24.880 and I'm Joe McCormick. Hey Jonathan, Hey Joe. Do you 0:00:24.960 --> 0:00:28.760 remember the very first episode of Forward Thinking the videos 0:00:29.280 --> 0:00:36.120 I'll never forget. That was a long day of filming videos. No. No, 0:00:36.320 --> 0:00:39.120 we only did three that day. We wanted to do five. 0:00:40.000 --> 0:00:42.680 So before we get into this topic, just so in 0:00:42.680 --> 0:00:45.720 case you're curious about what this experience was like. I 0:00:45.920 --> 0:00:48.520 had shot plenty of videos in the past, but never 0:00:48.640 --> 0:00:51.320 one with a full crew. And we had a full 0:00:51.360 --> 0:00:55.280 crew that first day. So we had sound people, camera person, 0:00:55.400 --> 0:00:59.320 we had wardrobe and makeup, we had lighting, and we 0:00:59.400 --> 0:01:02.600 had um producers who were there for the first time 0:01:02.640 --> 0:01:05.880 to to like the executive producer types who were actually 0:01:05.880 --> 0:01:08.000 there to watch this happen. There was a lot of 0:01:08.040 --> 0:01:12.080 pressure on Uh. No teleprompter. I never used a teleprompter 0:01:12.120 --> 0:01:15.480 for any of the Forward Thinking videos. UH might explain 0:01:15.520 --> 0:01:17.280 a few of them to you, because I get a 0:01:17.319 --> 0:01:20.760 little wacky and a little off script, so, uh intern't 0:01:20.760 --> 0:01:23.440 knowet things was one of the three videos we shot 0:01:23.480 --> 0:01:25.679 that day. I remember three D printing was one of 0:01:25.720 --> 0:01:28.679 the other, but I don't remember what the third one was. 0:01:29.240 --> 0:01:31.399 Oh it was it was a car one I think, 0:01:32.000 --> 0:01:35.839 um self driving cars. Self driving cars. Yeah, yeah, because 0:01:35.840 --> 0:01:40.880 we actually had a a a car in the studio 0:01:41.040 --> 0:01:43.720 that we used. It was not an actual self driving car, 0:01:43.760 --> 0:01:47.400 but we treated it as such. Uh So, anyway, Internet 0:01:47.400 --> 0:01:50.840 of Things has a long, long, long history with The 0:01:50.960 --> 0:01:53.080 Forward Thinking Show, and of course we talked about on 0:01:53.120 --> 0:01:56.840 the podcast too. All the time, it comes up a 0:01:56.840 --> 0:01:59.920 lot smart devices all around you. We've talked about smart 0:02:00.000 --> 0:02:03.720 devices in your kitchen, smart devices in your in your 0:02:03.800 --> 0:02:08.480 body right, and the whole idea of just having sensors 0:02:08.520 --> 0:02:11.800 that are collecting data and devices that can use that 0:02:11.919 --> 0:02:15.320 data to change your environment in some way. This is 0:02:15.360 --> 0:02:18.320 not something that you know is a new topic, obviously, 0:02:18.400 --> 0:02:22.720 but we wanted to talk about a specific implementation of 0:02:22.760 --> 0:02:27.440 this where you incorporate directly into architecture. And this is 0:02:27.480 --> 0:02:30.200 an area of research that IBM is conducting. They call 0:02:30.240 --> 0:02:34.200 it cognitive buildings. Yeah, so I would say this relates 0:02:34.240 --> 0:02:36.359 to the Internet of Things in that it's sort of 0:02:36.400 --> 0:02:40.040 like the Internet of Things, but a top down, integrated 0:02:40.040 --> 0:02:42.840 approach to it, right, right, Yeah, this is an idea 0:02:42.880 --> 0:02:47.680 of we have the capability of incorporating all these different 0:02:47.720 --> 0:02:51.720 types of sensors and systems into a building piecemeal, but 0:02:51.800 --> 0:02:54.000 what if we were to do it from the design 0:02:54.240 --> 0:02:59.240 of a building and incorporated, uh directly integrate everything so 0:02:59.280 --> 0:03:02.480 it's into a parable And this is a big idea 0:03:02.600 --> 0:03:06.400 that could potentially have uh some some interesting benefits down 0:03:06.480 --> 0:03:10.080 the road. So it's something I wanted to explore a 0:03:10.080 --> 0:03:13.359 bit more. Um, It's a pretty pretty simple idea that 0:03:13.400 --> 0:03:15.720 I think a lot of people can grasp early on, right, 0:03:15.800 --> 0:03:18.680 Like the idea of a building that has all of 0:03:18.720 --> 0:03:21.160 these things integrated in it and then essentially has like 0:03:21.240 --> 0:03:25.880 a pretty hefty processor to take in all that data, 0:03:26.200 --> 0:03:29.520 crunch it, and then uh respond in whatever way is 0:03:29.560 --> 0:03:33.040 most appropriate, right right. And the process that IBM is 0:03:33.040 --> 0:03:37.080 is using for this kind of concept is cognitive computing, yes, 0:03:37.200 --> 0:03:40.720 which involves lots of different topics We've talked about before, 0:03:40.800 --> 0:03:45.920 artificial intelligence, pattern recognition, a natural language processing, data mining, 0:03:45.960 --> 0:03:49.280 machine learning, all of that is part of cognitive computing. 0:03:49.400 --> 0:03:54.200 Generally speaking, cognitive computing is trying to use computers to 0:03:54.400 --> 0:04:00.400 simulate the way we think, not necessarily in a like, uh, 0:04:00.640 --> 0:04:03.360 granular way where a processor is behaving the way a 0:04:03.440 --> 0:04:06.320 brain is, but so that the output is similar to 0:04:06.360 --> 0:04:08.440 what you would have if you asked a very smart 0:04:08.480 --> 0:04:10.800 person to do the same sort of stuff. So it's 0:04:10.800 --> 0:04:13.400 a problem solving kind of technique, and it's using some 0:04:13.480 --> 0:04:15.400 of the data processing that we've talked about in our 0:04:15.440 --> 0:04:19.600 episodes about deep learning. Yes, yes, so if you can 0:04:19.640 --> 0:04:23.880 imagine the same sort of stuff that produces incredibly trippy 0:04:23.960 --> 0:04:28.160 paintings could be running your home in the future, driving 0:04:28.200 --> 0:04:31.800 you mad over a series of entertaining days. I just 0:04:31.920 --> 0:04:35.040 realized that we we may be able to put together 0:04:35.080 --> 0:04:37.919 in the future tutor a tutorial on how to overclock 0:04:38.000 --> 0:04:41.680 your house. That's actually it's not too far off from 0:04:41.800 --> 0:04:46.920 from the possible reality, right, So uh, ideally, what this 0:04:47.120 --> 0:04:51.640 would result in is a system that would learn about 0:04:51.720 --> 0:04:54.680 you as you move through it. So whether it's your 0:04:54.720 --> 0:04:56.680 office that you work in or the home that you 0:04:56.760 --> 0:04:59.880 live in, if it's a cognitive building, it actually learns 0:05:00.120 --> 0:05:04.080 about you, your preferences, your needs, and is able to 0:05:04.120 --> 0:05:07.640 respond to that in a way that is seamless, so 0:05:07.680 --> 0:05:09.839 that you don't have to even think about it. You 0:05:09.839 --> 0:05:13.720 don't even necessarily have to voice a command UH if 0:05:13.720 --> 0:05:16.040 it's learned enough. This is not that far off from 0:05:16.080 --> 0:05:19.279 some systems we have now, Like the Nest thermostat is 0:05:19.320 --> 0:05:21.280 an example. It's easy to point to because it's been 0:05:21.279 --> 0:05:24.480 around for a few years. So Nest thermostat can detect 0:05:24.560 --> 0:05:28.200 when you are home using motion sensors UH. It can 0:05:28.320 --> 0:05:31.160 have some pre program temperatures that you could tell it like, well, 0:05:31.200 --> 0:05:33.320 at night, I like it to be around this cool. 0:05:33.600 --> 0:05:35.400 During the day, you can turn the temperature up a 0:05:35.400 --> 0:05:38.760 certain amount. It might even have have other parameters saying, well, 0:05:39.480 --> 0:05:42.080 while the person is gone, we can even crank that 0:05:42.160 --> 0:05:44.080 up a little bit more so that we're saving energy. 0:05:44.400 --> 0:05:45.960 You know, the a C is not blowing when no 0:05:46.000 --> 0:05:48.640 one's home, and we also know that typically the person 0:05:48.680 --> 0:05:50.480 gets home at around this time, so we can turn 0:05:50.480 --> 0:05:53.560 the a C back down UH an hour before they 0:05:53.560 --> 0:05:55.240 get home, so that way the house is nice and 0:05:55.279 --> 0:05:57.159 cool by the time you walk through the front door. 0:05:57.600 --> 0:06:00.920 That's a pretty easy example, and it's one tiny system, 0:06:00.960 --> 0:06:03.640 but in a cognitive building, it would be one part 0:06:03.800 --> 0:06:07.159 of an overall integrated system, and it would just be 0:06:07.279 --> 0:06:10.560 one element of that. Imagine a building able to measure 0:06:10.640 --> 0:06:13.680 pretty much everything you're able to do inside that building 0:06:13.960 --> 0:06:17.000 and respond in a way that helps you save energy 0:06:17.120 --> 0:06:20.760 so you're not wasting it and also makes the experience 0:06:20.839 --> 0:06:25.840 pleasant and comfortable for you. That's kind of the basic concept, 0:06:26.760 --> 0:06:31.120 but it's way harder than what it south. Yeah. Yeah, 0:06:31.160 --> 0:06:34.120 we're not really quite there yet to the point where 0:06:34.560 --> 0:06:37.320 in most buildings we are prepared to do that. Like, 0:06:37.320 --> 0:06:39.480 like right now, if you if you want to integrate 0:06:39.520 --> 0:06:42.960 all of these different Internet of Things type systems you're uh, 0:06:43.279 --> 0:06:45.800 your smart lights in your in your nest, and your 0:06:46.120 --> 0:06:49.120 eye toaster, you're gonna need to get a third party 0:06:49.360 --> 0:06:51.520 thing that's going to connect up with all of them, right, 0:06:51.520 --> 0:06:53.960 because otherwise what you're talking about is having a phone 0:06:54.080 --> 0:06:57.200 with eighty thousand apps on it. Like I need to 0:06:57.200 --> 0:06:59.480 turn off my lights. Okay, let me just scroll through 0:06:59.520 --> 0:07:01.359 all right, it's an this folder. Okay, let me scroll 0:07:01.400 --> 0:07:04.840 down through here, there's my light folder. Like it's ridiculous. Right. 0:07:04.880 --> 0:07:11.040 If you if you go through a single service provider 0:07:11.240 --> 0:07:15.280 or product manufacturer that makes lots of different stuff in 0:07:15.320 --> 0:07:18.520 that space, then maybe you could get away with two 0:07:18.600 --> 0:07:22.960 or three systems all using an integrated app. But I 0:07:23.000 --> 0:07:25.840 don't think anyone makes all the different types of home 0:07:25.880 --> 0:07:28.080 automation systems that you can run into. So if you 0:07:28.160 --> 0:07:31.240 really wanted like the automated home of the future, the 0:07:31.360 --> 0:07:34.560 downside is you're going to have all these different interfaces 0:07:34.600 --> 0:07:37.040 that you have to work with in order to make 0:07:37.120 --> 0:07:40.680 that happen. Uh. The alternative, as Laurence said, is to 0:07:40.680 --> 0:07:44.640 get a third party object that is able to be 0:07:44.800 --> 0:07:47.600 kind of like a liaison between you and each of 0:07:47.640 --> 0:07:51.080 your disparate systems, one app to rule them all. Yeah. 0:07:51.120 --> 0:07:55.240 So Amazon's Echo is a great example that has Alexa, 0:07:55.440 --> 0:08:01.320 the the voice activated digital personal assistant. And Alexa can 0:08:01.400 --> 0:08:04.240 work with lots of different systems, right, It can work 0:08:04.280 --> 0:08:06.720 with Nest, it can work with certain like I think 0:08:06.760 --> 0:08:10.920 Phillips Hugh light bulbs. So with Alexa, you could tell 0:08:10.960 --> 0:08:14.360 Alexa what you want and then Alexa would communicate with 0:08:14.440 --> 0:08:18.280 the appropriate system on whatever terms are necessary for it 0:08:18.320 --> 0:08:21.760 to get this done, and it would happen. This is 0:08:21.800 --> 0:08:25.480 an inelegant way of going about this because you still 0:08:25.520 --> 0:08:29.280 have to have that intermediary. This is essentially translating your 0:08:29.360 --> 0:08:33.040 commands so that whatever you want to have happen happens. 0:08:33.360 --> 0:08:35.400 It would be it would be nicer to have a 0:08:35.440 --> 0:08:39.600 fully integrated system that does this all automatically because it 0:08:39.720 --> 0:08:42.840 fully understands you not just what temperature you like, but 0:08:42.920 --> 0:08:46.400 what light level you like, and what music you like 0:08:46.520 --> 0:08:49.439 and uh, you know, even things like what you prefer 0:08:49.520 --> 0:08:52.560 to eat, because this could be incorporated all into the 0:08:52.600 --> 0:08:55.800 appliances of your house, not just the lighting and the 0:08:56.559 --> 0:09:01.360 climate system. And all of these integrat sans can ultimately 0:09:01.880 --> 0:09:04.600 result in energy conservation, which is I think, I would 0:09:04.679 --> 0:09:08.439 argue is the biggest point of concern for the IBM 0:09:08.480 --> 0:09:13.600 research team. Uh So, designing this building not the easiest 0:09:13.600 --> 0:09:14.760 thing in the world to do. You have to have 0:09:14.800 --> 0:09:18.160 all these different sensors to detect all sorts of stuff, 0:09:18.200 --> 0:09:23.000 you know, temperature, lighting, electricity, water flow. Perhaps. Uh it's 0:09:23.000 --> 0:09:25.720 a big job. And in fact, the IBM research center 0:09:25.760 --> 0:09:28.079 that they have, they've got a lab with more than 0:09:28.120 --> 0:09:34.320 three thousand sensors integrated into it. It's about a four 0:09:34.360 --> 0:09:37.680 ft by five ft cubicle. No, I don't I don't 0:09:37.720 --> 0:09:39.440 know how big the lab is, but it's not it's 0:09:39.440 --> 0:09:42.600 not as far as I know. It's in Dublin, Ireland. Um, 0:09:42.640 --> 0:09:45.319 it's not as large as like a full building as 0:09:45.360 --> 0:09:48.720 far as I'm aware, Um, but still, I mean, and 0:09:48.760 --> 0:09:50.240 if you think about that, if you think, well, if 0:09:50.280 --> 0:09:51.840 it's not as large as a full building, then a 0:09:51.840 --> 0:09:54.960 full building would need probably even more sensors to get 0:09:55.040 --> 0:09:57.400 comprehensive data. All right, But I mean think think about 0:09:57.480 --> 0:10:00.679 how many different factors you're you're trying to integrate here 0:10:00.840 --> 0:10:03.480 and and this is in every single room in the 0:10:03.640 --> 0:10:06.040 entire building. So you know, you're you're you're looking to 0:10:06.440 --> 0:10:11.400 detect motion, perhaps have facial recognition, uh, detect light levels 0:10:11.400 --> 0:10:17.079 like natural light levels to detect temperature, uma, detect water 0:10:17.280 --> 0:10:19.599 use to detect everything that's going on, and all of 0:10:19.640 --> 0:10:24.280 the pipes to detect what the sewage pipes are doing. Yeah, 0:10:24.280 --> 0:10:26.480 there's a lot of sensors for every single room, and 0:10:26.640 --> 0:10:29.520 and you think about that. You you ultimately have all 0:10:29.520 --> 0:10:33.240 of that data sent to a central processing unit a 0:10:32.840 --> 0:10:38.280 a computer of some sophistication to make sense of what 0:10:38.320 --> 0:10:42.400 that information means. It may mean that certain choices in 0:10:42.520 --> 0:10:47.520 order to conserve energy could at first appear counterintuitive because 0:10:47.520 --> 0:10:50.680 it may be that it's taking into consideration a lot 0:10:50.720 --> 0:10:53.680 of factors that you, as a human being inside that building, 0:10:53.720 --> 0:10:57.200 aren't necessarily aware of at the time. So it's like 0:10:57.240 --> 0:10:59.640 in a closed room, the amount of sunlight that the 0:10:59.720 --> 0:11:02.640 roof is getting somewhere near you could definitely affect the 0:11:02.640 --> 0:11:06.120 temperature that you're experiencing. Yeah, that's a that's a simple example, 0:11:06.200 --> 0:11:09.600 and there are so many out there. Everything like if 0:11:09.640 --> 0:11:11.920 if the room happens to have a whole bunch of 0:11:11.960 --> 0:11:15.640 pipes that water flows through, that might affect things as well. 0:11:15.760 --> 0:11:19.440 It's it's really complicated stuff, and so that's why you 0:11:19.480 --> 0:11:23.120 need like the really powerful processing ability on the other 0:11:23.240 --> 0:11:25.480 end to make sense of that and turn it into 0:11:25.600 --> 0:11:30.640 actionable items that the house can can then go through. So, 0:11:30.800 --> 0:11:34.560 like I said, saving energy, that's like the primary purpose 0:11:34.880 --> 0:11:38.680 for this project, and a cognitive building could keep track 0:11:38.840 --> 0:11:41.200 of all the rooms that are in use which ones aren't. 0:11:41.400 --> 0:11:45.680 Essentially it's like the very complicated way of telling people, Hey, 0:11:45.880 --> 0:11:48.240 turn off the light when you leave the room, except 0:11:48.280 --> 0:11:50.120 now the building is doing it for you, and also 0:11:50.160 --> 0:11:52.920 maybe adjusting the the air conditioning for that room. If 0:11:53.080 --> 0:11:56.000 if there's like different air conditioners for different floors or 0:11:56.000 --> 0:11:58.920 different even different sections of the building. It can manage 0:11:58.920 --> 0:12:03.280 it on a very grand, a little granular level. Ah, 0:12:03.360 --> 0:12:07.600 And it's h it's pretty intense to do all this. 0:12:07.640 --> 0:12:11.479 It's is an intense processing and intense data gathering system. 0:12:11.520 --> 0:12:15.520 It's really taking that big data approach on a building 0:12:15.559 --> 0:12:20.040 by building or collection of building kind of scale, which 0:12:20.080 --> 0:12:22.679 is also crazy because IBM research is looking not just 0:12:22.760 --> 0:12:25.880 at making one cognitive building, but making groups of them. 0:12:25.920 --> 0:12:28.160 Oh sure, yeah, not not just like personal homes, Like 0:12:28.200 --> 0:12:29.920 it's kind of easy to think about this on a 0:12:30.040 --> 0:12:33.080 single home kind of level. But but of course they're 0:12:33.080 --> 0:12:36.720 trying to expand that out. Yeah yeah, So, uh, let's 0:12:36.760 --> 0:12:39.960 say that what where can you where can you go 0:12:40.080 --> 0:12:44.520 besides energy conservation? I mean, that's obviously a very important element, 0:12:44.800 --> 0:12:47.480 but what else could you do with this? One thing 0:12:47.640 --> 0:12:51.120 that IBM is proposing is a system that could detect 0:12:51.160 --> 0:12:54.440 problems before they become so great that you have to 0:12:55.200 --> 0:12:58.920 have like an emergency response to it. So, let's say 0:12:59.000 --> 0:13:03.520 that your smart sensors detect that your air conditioner is 0:13:03.520 --> 0:13:06.200 working harder than it normally has to in order to 0:13:06.280 --> 0:13:09.240 maintain the temperature. It may mean that you need to 0:13:09.320 --> 0:13:11.840 change your air filter, right, it may be something as 0:13:11.880 --> 0:13:14.680 simple as that, or maybe that uh oh, we're detecting 0:13:14.720 --> 0:13:17.559 a decrease in pressure in the tubes and your your 0:13:17.679 --> 0:13:22.439 free on or other your coolant is leaking somewhere. It 0:13:22.559 --> 0:13:24.920 can then send you an alert. You get alert alert 0:13:24.960 --> 0:13:27.680 on your phone saying hey, by the way, I've detected 0:13:27.679 --> 0:13:32.000 this drop in efficiency. Um, the diagnosis I have is 0:13:32.040 --> 0:13:34.199 such and such. If it's something like switching out of filter, 0:13:34.320 --> 0:13:36.520 you could probably do it yourself. If it's something a 0:13:36.559 --> 0:13:39.079 little more complicated, might say that you might need to 0:13:39.320 --> 0:13:42.800 call someone, and may even bring you give you suggestions 0:13:42.840 --> 0:13:45.560 on who to call, depending upon the way you've designed 0:13:45.559 --> 0:13:47.920 this building. Same thing could be true with plumbing. It 0:13:47.920 --> 0:13:51.400 could say, well, I detected that they're the the waste 0:13:51.679 --> 0:13:56.000 pipes aren't flowing as properly as they should. It may 0:13:56.120 --> 0:13:59.160 very well be that the vent that allows air to 0:13:59.160 --> 0:14:02.079 pass through the the waste pipes has been clogged with something, 0:14:02.160 --> 0:14:05.000 so you need to just run some water down the 0:14:05.080 --> 0:14:07.280 vent to clear it out. And then you don't have 0:14:07.320 --> 0:14:09.400 to bring a plumber in to do an expensive job 0:14:09.400 --> 0:14:11.640 when you can just do it yourself. This is something 0:14:11.679 --> 0:14:14.120 that I actually had to go through myself recently. I 0:14:14.160 --> 0:14:17.000 had to I didn't have a computer tell me. It's 0:14:17.000 --> 0:14:19.080 just one of those things where I thought this drains 0:14:19.080 --> 0:14:22.320 backing up. I sure hope the venice claude because that's 0:14:22.320 --> 0:14:25.800 an easy solution. Turned out it was, But it would 0:14:25.800 --> 0:14:27.720 be great to have a system that tells me that 0:14:27.840 --> 0:14:31.040 oh sure, yeah, you know it's something that's that's telling 0:14:31.120 --> 0:14:34.040 you where you've got a a leak in a pipe 0:14:34.240 --> 0:14:39.240 or a leak in electricity flow. Sure a you know 0:14:39.280 --> 0:14:41.280 if if if you're if you're in an area where 0:14:41.320 --> 0:14:43.920 your pipes might freeze during the winter. Um, something that 0:14:43.920 --> 0:14:47.560 can automatically regulate the temperature in problematic sections at the 0:14:47.560 --> 0:14:51.600 house to not let your pipes freeze, yeah, or or 0:14:51.640 --> 0:14:54.040 an automated tap of some sort that can just let 0:14:54.160 --> 0:14:56.840 enough water flow to prevent it from freezing up right right, Yeah, 0:14:57.160 --> 0:14:59.720 it is Yeah, that that that would be great because 0:14:59.720 --> 0:15:01.920 again it saves you money in the long runs. It 0:15:02.960 --> 0:15:07.160 uh ends up also preventing further damage being done two 0:15:07.400 --> 0:15:10.000 elements of the home or the building. It would be 0:15:10.040 --> 0:15:13.760 a huge benefit sure And speaking of money, hey, in 0:15:13.840 --> 0:15:16.960 multi home buildings like condos or apartments or whatever, you 0:15:16.960 --> 0:15:23.720 could track who's using the most resources and adjust the rent. Wow, 0:15:23.760 --> 0:15:26.640 So you'd have to pay for the number of times 0:15:26.680 --> 0:15:30.640 you flush the toilet and your landlord knows Yep. I mean, 0:15:30.680 --> 0:15:32.680 I mean a lot of a lot of a lot 0:15:32.720 --> 0:15:35.160 of apartments and condos that I know of have there. 0:15:35.320 --> 0:15:38.480 You don't have a have a collected waste removal kind 0:15:38.520 --> 0:15:44.040 of fee. You know, I think it's only fair starting 0:15:44.040 --> 0:15:47.520 to get into brazil territory. And here's my receipt for 0:15:47.600 --> 0:15:51.360 your receipt. Uh. Yeah. And beyond this, like I said, 0:15:51.440 --> 0:15:55.720 this does actually remind me strangely of Brazilian Yeah that really? Yeah, 0:15:55.800 --> 0:15:59.000 will this cognitive building have ducks? Will There'll be lots 0:15:59.000 --> 0:16:04.680 of ducks? How man? Yes, require duct repair people, not 0:16:06.080 --> 0:16:09.280 side ducks. I've already been yelled at for talking about 0:16:09.280 --> 0:16:12.800 Pokemon Go too much. Uh. As I mentioned earlier, it 0:16:12.840 --> 0:16:14.240 doesn't have to just be a building and can be 0:16:14.240 --> 0:16:16.600 a collection of buildings. The example that they gave was 0:16:16.760 --> 0:16:20.480 imagine a college campus that could actually track the movement 0:16:20.600 --> 0:16:24.800 of students not just within individual buildings, but across different buildings. 0:16:25.280 --> 0:16:27.880 And then it starts getting into a really complicated kind 0:16:27.920 --> 0:16:31.280 of approach where if if you're designing it in such 0:16:31.480 --> 0:16:35.680 such a way so that uh it's as a seamless 0:16:35.680 --> 0:16:38.400 and experience for the people in there, but also one 0:16:38.480 --> 0:16:42.640 that conserves the most energy possible, and it's as busy 0:16:42.720 --> 0:16:45.800 as like a college campus that gets pretty tough to 0:16:45.840 --> 0:16:48.600 do too. Um. I was really impressed when I was 0:16:48.640 --> 0:16:50.800 reading about this, and I was curious, like, how could 0:16:50.840 --> 0:16:53.960 they even process this information? And then I found out 0:16:54.400 --> 0:16:58.200 that the back end, the brains behind this is essentially 0:16:58.280 --> 0:17:03.040 IBM Watson, Like, oh, that would do it. I don't 0:17:03.080 --> 0:17:05.760 happen to have access to one of those, but I 0:17:05.800 --> 0:17:09.320 can understand how that would help. Um. But it's not 0:17:09.440 --> 0:17:13.600 just not just convenience or energy conservation in these cases 0:17:13.640 --> 0:17:16.359 that could be helped out too. Oh yeah, stuff like 0:17:16.520 --> 0:17:20.760 response to a security or emergency situations could be streamlined 0:17:20.840 --> 0:17:23.720 because of the way that everything is connected and the 0:17:23.720 --> 0:17:26.120 way that it knows who's coming and going, which gets 0:17:26.119 --> 0:17:30.480 back into weird Brazil territory. There's some some privacy issues obviously, sure, 0:17:30.800 --> 0:17:34.080 but beyond that even you know, like they would never 0:17:34.160 --> 0:17:37.040 run out of your favorite soda in the vending machine 0:17:37.520 --> 0:17:39.560 or out of toilet paper in a bathroom. Now you're 0:17:39.600 --> 0:17:44.640 speaking my language. There's nothing like just taking that casual 0:17:44.720 --> 0:17:47.479 glance over and then thinking I have committed to an 0:17:47.480 --> 0:17:51.520 action that I regret now. Wow, yeah, thanks for taking 0:17:51.600 --> 0:17:54.199 us there with you, hey, you know, I was speaking 0:17:54.200 --> 0:17:56.800 in a circumspect kind of way. I was trying to 0:17:56.800 --> 0:17:59.760 be as gentlemanly about it as possible. Hey, how about 0:17:59.760 --> 0:18:03.040 another example of a cognitive building that they actually talked 0:18:03.320 --> 0:18:06.119 the IBM team is talked about hospitals. Yeah, and this 0:18:06.200 --> 0:18:08.760 is a this is a really kind of inspiring one. 0:18:09.119 --> 0:18:12.280 So not just energy conservation here either, but also trying 0:18:12.320 --> 0:18:15.040 to improve the health and safety of the staff and 0:18:15.119 --> 0:18:19.240 patients in the hospital. One of the biggest challenges facing 0:18:19.320 --> 0:18:23.800 hospitals is managing infection and contagion. I mean you hear 0:18:23.840 --> 0:18:25.440 people say this all the time, like I don't want 0:18:25.440 --> 0:18:28.000 to go to the hospital sick people are there. Yeah, 0:18:28.520 --> 0:18:30.080 and we talked a little bit about this in our 0:18:30.119 --> 0:18:35.240 episode about antibiotics. Yes, so yeah, hospital acquired infections are 0:18:35.359 --> 0:18:39.080 real things. Yeah, absolutely, And so it's it's you know, 0:18:39.200 --> 0:18:42.600 it's a it's a dangerous environment to be and even 0:18:42.640 --> 0:18:47.080 when people are very carefully following protocols. So a smart 0:18:47.119 --> 0:18:49.520 building version of a hospital might be able to help 0:18:49.560 --> 0:18:53.800 in that way by improving the airflow and even uh 0:18:54.080 --> 0:18:59.400 controlling air pressure in individual rooms to help maintain some 0:18:59.640 --> 0:19:03.760 safe between different patients, to contain areas that might have 0:19:04.400 --> 0:19:08.720 contagious uh pathogens in them or uh some other form 0:19:08.840 --> 0:19:12.600 of of infectious material, so that you minimize the risk 0:19:12.840 --> 0:19:16.920 of this spreading to either staff or other patients. Also, 0:19:17.000 --> 0:19:19.919 just knowing which rooms are occupied and which ones aren't, 0:19:19.960 --> 0:19:23.399 I mean you can save energy that way too. You know, 0:19:23.520 --> 0:19:25.200 one thing that occurred to me when I was thinking 0:19:25.200 --> 0:19:29.240 about the example of the hospital is what if your 0:19:29.280 --> 0:19:33.480 buildings in a sense could actually do science for you, 0:19:33.520 --> 0:19:36.960 like doing data analysis, And by that I mean taking 0:19:37.560 --> 0:19:40.640 the kind of data the buildings like this would naturally 0:19:40.680 --> 0:19:44.560 be collecting, and then pairing that with some other kind 0:19:44.600 --> 0:19:48.760 of data and cross referencing to see if any correlations emerge. 0:19:49.520 --> 0:19:52.520 So in a hospital environment, for example, that might mean 0:19:52.600 --> 0:19:56.359 you you're pairing this integrated environmental data like you know 0:19:56.440 --> 0:19:59.359 room temperature and where the lights are on, all that junk, 0:20:00.160 --> 0:20:03.480 you know, the hundreds of variables the buildings collecting just 0:20:03.560 --> 0:20:06.600 about the environment and what appliances are being used, and 0:20:06.720 --> 0:20:10.800 you pair that with linked data about health outcomes. You know, 0:20:10.840 --> 0:20:14.040 we might not find anything interesting. It probably wouldn't surprise 0:20:14.160 --> 0:20:16.560 us if environmental data about the building had no real 0:20:16.640 --> 0:20:19.840 correlation with health outcomes. But what if in some cases 0:20:19.880 --> 0:20:22.719 it did in ways that we wouldn't have even thought 0:20:22.800 --> 0:20:25.520 to look for if we had to do all these 0:20:25.560 --> 0:20:29.359 analyzes ourselves. Just like what if patients in rooms with 0:20:29.760 --> 0:20:34.040 lower air conditioning temperatures had fewer complications during surgery or 0:20:34.080 --> 0:20:36.280 something like that. Yeah, and and this could also help 0:20:36.400 --> 0:20:39.400 us us out what's going on with a sick building syndrome, 0:20:40.920 --> 0:20:43.919 which is which is the phenomenon in which there tend 0:20:44.000 --> 0:20:50.160 to be these these just kind of breakouts of long term, 0:20:50.320 --> 0:20:55.040 low grade illness among office workers who work in certain environments. 0:20:56.080 --> 0:20:58.879 I can imagine that I've worked with people who have 0:20:58.920 --> 0:21:03.560 made me feel sick before. It's it's suspected that it's 0:21:03.640 --> 0:21:06.320 usually due to like air quality of some kind or another, 0:21:06.440 --> 0:21:09.920 either like surrounding pollutants or mold and mildew or etcetera 0:21:10.560 --> 0:21:13.280 flickering fluorescent light that gives you a brain cloud, but 0:21:13.320 --> 0:21:18.880 it can also be march. Why march another thing that 0:21:19.240 --> 0:21:22.399 you have. When you talked about the building itself gathering data, 0:21:22.760 --> 0:21:26.640 it occurs to me that you could even incorporate the 0:21:26.720 --> 0:21:29.359 actual like you would probably want to scrub this of 0:21:29.400 --> 0:21:32.320 any personal information, but you could you could incorporate things 0:21:32.400 --> 0:21:35.840 like the actual nature of diseases of patients in actual rooms, 0:21:35.880 --> 0:21:38.600 and the building itself could become a data collection point 0:21:38.920 --> 0:21:41.960 and perhaps be an early indicator for something like, Hey, 0:21:41.960 --> 0:21:43.600 you need to be on the lookout for an epidemic, 0:21:43.640 --> 0:21:46.760 because based on the statistics that we're seeing here and 0:21:46.800 --> 0:21:48.479 the number of patients who have come in with this 0:21:48.920 --> 0:21:54.160 similar or identical condition, there could be a source nearby 0:21:54.280 --> 0:21:58.119 that's making people sick. It could give people the information 0:21:58.160 --> 0:22:02.199 they need to actually address the source of an issue 0:22:02.480 --> 0:22:05.720 before it gets even worse. Yeah, that's kind of I 0:22:05.800 --> 0:22:10.320 never even thought about that, but that is really cool. Yeah. Also, um, 0:22:10.520 --> 0:22:13.040 what about what about factories? Um? I mean these these 0:22:13.080 --> 0:22:16.439 are places where things are already fairly streamlined, but a 0:22:16.520 --> 0:22:20.200 cognitive factory could could monitor the waar too. Again to 0:22:20.280 --> 0:22:24.240 like every piece of equipment and alert staff if the 0:22:24.560 --> 0:22:26.560 if the heat levels or the sound of the moving 0:22:26.680 --> 0:22:30.600 parts or whatever it is, um indicates that something is 0:22:30.600 --> 0:22:33.080 about to wear out and and get in there and 0:22:33.840 --> 0:22:37.800 replace it to to prevent a costly and time time 0:22:37.840 --> 0:22:40.960 consuming or or even a hazardous breakage. Right. You know, 0:22:41.080 --> 0:22:45.560 factory environment seems susceptible to the same kind of automated 0:22:45.600 --> 0:22:48.440 scientific analysis that I was just talking about. With the hospital, 0:22:48.520 --> 0:22:52.880 where you could have the building just ambiently collecting all 0:22:52.920 --> 0:22:56.120 of these variables. And whereas in the hospital you'd compare 0:22:56.119 --> 0:22:59.679