WEBVTT 00:00.380 --> 00:01.730 - I've been to the first two 00:01.730 --> 00:04.840 and the conversations have been incredibly interesting 00:04.840 --> 00:06.830 because there's a very, very wide range 00:06.830 --> 00:09.810 of views on this matter and, to the department's credit, 00:09.810 --> 00:12.793 it's listening to everybody, including its chief critics. 00:13.660 --> 00:16.540 What happens after Stanford, Michael? 00:16.540 --> 00:18.930 - I'm going to actually turn it mostly over to Josh, 00:18.930 --> 00:22.460 but I think the ultimate tasking for us 00:22.460 --> 00:25.570 is a set of recommendations that will go to the department. 00:25.570 --> 00:27.410 The department's made it very clear 00:27.410 --> 00:31.360 that if there will be AI-informed ethical principles 00:31.360 --> 00:34.860 or guidance in the department, the department owns that. 00:34.860 --> 00:36.750 We will develop a series of recommendations 00:36.750 --> 00:37.583 based on the listening sessions 00:37.583 --> 00:39.210 and the people we've talked to. 00:39.210 --> 00:40.706 Josh, can you talk about timing on that? 00:40.706 --> 00:41.539 - Absolutely. 00:41.539 --> 00:45.130 We'll do the sessions at Stanford at the end of April. 00:45.130 --> 00:47.530 We'll then have a red team session 00:47.530 --> 00:49.020 that'll be part of a subcommittee meeting 00:49.020 --> 00:51.550 that'll be closed and classified. 00:51.550 --> 00:53.840 After that, we should have a draft ready 00:53.840 --> 00:54.810 to share with the public 00:54.810 --> 00:56.930 in anticipation of our June meeting. 00:56.930 --> 00:58.623 So, the next public board meeting after this one 00:58.623 --> 01:01.360 will be in early June, at Defense Innovation Unit 01:01.360 --> 01:03.440 in Mountain View, California. 01:03.440 --> 01:05.560 Then we'll get feedback and deliberation 01:05.560 --> 01:07.340 from all of you at that session. 01:07.340 --> 01:09.270 We'll have, essentially, the summer 01:09.270 --> 01:12.370 to make revisions, iterations, follow-up conversations, 01:12.370 --> 01:15.040 further interviews, whatever the board needs to do, 01:15.040 --> 01:17.850 and then complete it in time for our fall meeting 01:17.850 --> 01:19.500 which is on October 25th. 01:19.500 --> 01:20.890 We're hoping that if it's ready, 01:20.890 --> 01:22.930 the board will vote as it did today on that 01:22.930 --> 01:24.900 and then convey it to the secretary, 01:24.900 --> 01:27.900 and then the secretary will begin a staffing process 01:27.900 --> 01:30.970 as it will do for software study or the others. 01:30.970 --> 01:32.810 We suspect that he'll make the decision 01:32.810 --> 01:35.840 to delegate it to appropriate group 01:35.840 --> 01:37.950 and there'll be an internal coordination process. 01:37.950 --> 01:40.210 He's committed that, at some point, when it's over, 01:40.210 --> 01:43.250 he'll inform the board what choice he's made 01:43.250 --> 01:45.700 about what to do with the principles you propose. 01:48.240 --> 01:49.260 - Okay, understood. 01:49.260 --> 01:53.653 Are there other reports, Josh, you wanted us to talk about? 01:54.740 --> 01:57.120 - [Joshua] No, I think that's a good overview. 01:57.120 --> 01:58.990 - Why don't you give everybody a report 01:58.990 --> 02:00.613 on what you all have been up to? 02:03.320 --> 02:04.153 - Come again? 02:05.140 --> 02:05.973 So sorry. 02:07.245 --> 02:08.610 - Talk through the implementation. 02:08.610 --> 02:09.443 - Oh, I'm sorry, sir. 02:09.443 --> 02:10.276 The implementation base. 02:10.276 --> 02:12.230 - This is your turn to talk. (audience laughing) 02:12.230 --> 02:13.530 - Yes, I'm sorry. 02:13.530 --> 02:15.770 Actually, Dr. Porter is here, 02:15.770 --> 02:16.603 so what I think we'll do, 02:16.603 --> 02:17.870 - Perhaps we should delay you - We'll switch the order. 02:17.870 --> 02:19.750 - [Eric Schmidt] so that we can hear from her. 02:19.750 --> 02:21.260 - Yes, I think that's much more important. 02:21.260 --> 02:23.580 Let me just get to her here. (Eric Schmidt laughing) 02:23.580 --> 02:24.670 There we go. 02:24.670 --> 02:25.503 All right. 02:25.503 --> 02:28.583 Let me quickly introduce Dr. Porter. 02:31.216 --> 02:32.770 She's the deputy under secretary 02:32.770 --> 02:34.440 for research and engineering. 02:34.440 --> 02:37.000 Dr. Porter is responsible for research, development, 02:37.000 --> 02:39.860 prototyping activities across the DOD enterprise 02:39.860 --> 02:42.070 and oversees the activities of DARPA, 02:42.070 --> 02:43.270 the Missile Defense Agency, 02:43.270 --> 02:45.250 the Strategic Capabilities Office, 02:45.250 --> 02:47.140 the Defense Innovation Unit, 02:47.140 --> 02:48.910 all of the department's laboratories 02:48.910 --> 02:50.250 and its engineering enterprise, 02:50.250 --> 02:52.400 as well as the under-secretariat staff 02:52.400 --> 02:54.990 that develops advanced technology and capabilities 02:54.990 --> 02:55.930 for the department. 02:55.930 --> 02:57.280 Dr. Porter previously served 02:57.280 --> 02:59.480 as the executive vice president of In-Q-Tel 02:59.480 --> 03:00.950 and the director of In-Q-Tel Labs, 03:00.950 --> 03:04.020 as well as the president of Teledyne Scientific & Imaging, 03:04.020 --> 03:05.680 was the first director of IARPA, 03:05.680 --> 03:06.900 and also previously served 03:06.900 --> 03:09.160 as an associate administrator at NASA 03:09.160 --> 03:11.380 and as a manager and scientist at DARPA. 03:11.380 --> 03:12.926 Please join me in welcoming Dr. Porter. 03:12.926 --> 03:15.676 (all applauding) 03:22.890 --> 03:25.210 - Hi, well, good morning, everyone. 03:25.210 --> 03:26.830 It's nice to be able to sneak in here 03:26.830 --> 03:30.250 and hear a little about the software study. 03:30.250 --> 03:32.710 I will confess I haven't read the whole thing yet 03:32.710 --> 03:34.914 'cause it's a hundred-and-something pages long. 03:34.914 --> 03:35.747 (man speaking faintly) 03:35.747 --> 03:38.903 Yeah, I lost it at about page 40. 03:39.940 --> 03:41.860 I'm kidding, I will read the whole thing. 03:41.860 --> 03:45.130 It is actually a very well-written report. 03:45.130 --> 03:47.370 I'll just pile on the accolades right up front 03:47.370 --> 03:50.780 regarding how high the quality of that report is. 03:50.780 --> 03:53.640 I wanted to thank the DIB members more broadly 03:53.640 --> 03:55.380 because I firmly believe 03:55.380 --> 03:57.800 that time is our most valuable asset 03:57.800 --> 04:00.050 and when the members of the board get together 04:00.050 --> 04:02.470 and put together that kind of quality report, 04:02.470 --> 04:04.950 and that's just one report, one study they're doing, 04:04.950 --> 04:07.420 I think it shows an incredible dedication and commitment 04:07.420 --> 04:09.250 to try to help the department 04:09.250 --> 04:11.180 execute our mission more effectively. 04:11.180 --> 04:13.010 So, I really do wanna genuinely thank you 04:13.010 --> 04:15.770 for the work that you guys do so tirelessly 04:15.770 --> 04:16.660 behind the scenes. 04:16.660 --> 04:18.780 And, again, I can't speak enough 04:18.780 --> 04:20.890 about how high the quality of that report is, 04:20.890 --> 04:22.520 so thank you. 04:22.520 --> 04:24.440 I thought I would spend the time that I have here 04:24.440 --> 04:26.840 just making a few high-level observations 04:26.840 --> 04:28.110 on behalf of USD(R&E). 04:31.470 --> 04:32.430 How many people in the audience 04:32.430 --> 04:34.423 are scientists and engineers? 04:35.540 --> 04:36.393 Okay, good. 04:37.360 --> 04:38.930 Probably a lot of what I'm gonna say 04:38.930 --> 04:40.670 is going to sound obvious. 04:40.670 --> 04:42.970 However, it's been my experience in my career, 04:42.970 --> 04:44.830 and nothing in my current position 04:44.830 --> 04:47.370 has deterred my opinion on this, 04:47.370 --> 04:50.230 that sometimes you have to say the obvious out loud, 04:50.230 --> 04:54.650 because we have biases, we have emotions, 04:54.650 --> 04:56.263 we have vested interests, 04:57.910 --> 04:59.810 we just have politics that we deal with, 04:59.810 --> 05:02.040 and all of these things can get in the way 05:02.040 --> 05:05.480 of really seeing what should be obvious to us. 05:05.480 --> 05:07.860 So, sometimes, it's worth it to take a step back 05:07.860 --> 05:10.560 and remind ourselves of some core principles. 05:10.560 --> 05:12.270 I'm gonna be at the hundred-thousand-foot level. 05:12.270 --> 05:14.150 I'm not gonna speak specifically about software 05:14.150 --> 05:16.780 because I know you've heard a lot about that already, 05:16.780 --> 05:19.180 but I think that, I'm hopeful that the points that I make 05:19.180 --> 05:20.390 will resonate with some of you 05:20.390 --> 05:22.100 and perhaps provide a framework 05:22.100 --> 05:25.810 for some of the thinking that we collaboratively engage in 05:25.810 --> 05:27.580 going forward with the DIB. 05:27.580 --> 05:29.440 The first observation I wanted to make 05:29.440 --> 05:32.130 is that the challenges that the department faces, 05:32.130 --> 05:34.700 and particularly the ones that we ask for help 05:34.700 --> 05:37.150 and advice from folks like the DIB, 05:37.150 --> 05:39.143 are extraordinarily complex. 05:40.150 --> 05:45.150 They actually require an appreciation for that complexity, 05:45.250 --> 05:48.410 they require an ability to bring nuance to how we view them, 05:48.410 --> 05:50.060 and, very importantly, they require 05:50.060 --> 05:51.573 a healthy dose of humility. 05:52.680 --> 05:53.970 There are no easy buttons 05:53.970 --> 05:58.040 to these complex problems that we face. 05:58.040 --> 05:59.950 I'm reminded of my favorite, 05:59.950 --> 06:01.240 well, it's not my favorite joke, 06:01.240 --> 06:03.550 but a favorite joke, as a geeky joke, 06:03.550 --> 06:05.070 of the spherical cow. 06:05.070 --> 06:06.780 How many of you know what I'm talking about 06:06.780 --> 06:08.450 when I say the spherical cow joke? 06:08.450 --> 06:10.983 Okay, so there are like two physicists in the room. 06:12.730 --> 06:14.610 I'll tell it even though I'm not a good joke teller 06:14.610 --> 06:16.170 and I'll tell you the condensed version 06:16.170 --> 06:19.700 'cause there's a million versions that go on and on and on. 06:19.700 --> 06:22.510 I think (chuckling) it's actually a helpful reminder. 06:22.510 --> 06:24.050 There's a farmer, a dairy farmer, 06:24.050 --> 06:27.260 and he wants to improve the output of the milk of his cows 06:27.260 --> 06:28.400 so he can make more money. 06:28.400 --> 06:32.530 So, he invites an engineer and a botanist and a physicist, 06:32.530 --> 06:34.500 and says, hey, can you guys help me figure out 06:34.500 --> 06:37.590 how to improve the output of my cows? 06:37.590 --> 06:39.830 The engineer says, yeah, I can tell you what you need to do. 06:39.830 --> 06:43.250 You need to completely redesign and rebuild 06:43.250 --> 06:44.410 your milking stalls. 06:44.410 --> 06:46.560 You gotta get many more cows in there. 06:46.560 --> 06:50.440 You've gotta overhaul all your pumps and all of your pipes 06:50.440 --> 06:52.700 and this is gonna be a huge infrastructure investment 06:52.700 --> 06:55.070 and you'll get a return several years down the road. 06:55.070 --> 06:57.390 The farmer's very depressed about this, 06:57.390 --> 06:59.390 so he turns to the botanist. 06:59.390 --> 07:01.830 If I can remember the real word for a grass specialist, 07:01.830 --> 07:04.030 there is one, but we'll call him a botanist. 07:04.940 --> 07:07.700 The botanist says, well, we can probably design 07:07.700 --> 07:09.940 some new grass through some seeds. 07:09.940 --> 07:11.440 We'll do a lot of genetic engineering, 07:11.440 --> 07:13.090 we'll find some grass that allows them 07:13.090 --> 07:14.720 to produce milk more quickly. 07:14.720 --> 07:15.600 But I gotta warn you, 07:15.600 --> 07:17.240 this is a very hit-or-miss kind of thing. 07:17.240 --> 07:19.470 It's gonna take a lot of experiments and a lot of years 07:19.470 --> 07:20.610 to do this just right, 07:20.610 --> 07:22.920 and I can't guarantee that it'll work. 07:22.920 --> 07:25.990 So, (sighs) the farmer at this point is really depressed, 07:25.990 --> 07:28.150 but then he notices the physicist over in the corner, 07:28.150 --> 07:29.730 looking very smug, 07:29.730 --> 07:32.120 as physicists do. (man chuckling) 07:32.120 --> 07:33.700 He says, well, do you have any ideas? 07:33.700 --> 07:35.490 He says, yeah, there's no problem, this is easy. 07:35.490 --> 07:37.310 He says, so, tell me what I need to do. 07:37.310 --> 07:40.855 He said, step one, assume a spherical cow. 07:40.855 --> 07:42.700 (audience members chuckling) 07:42.700 --> 07:44.900 And for the physicists in the room: 07:44.900 --> 07:47.136 of uniform density in a vacuum. 07:47.136 --> 07:50.024 (audience laughing) (Lisa chuckles) 07:50.024 --> 07:51.500 I love that joke because (chuckling) even though 07:51.500 --> 07:54.110 it's just so silly, and they tell it, 07:54.110 --> 07:55.780 by the way, I was an MIT undergrad, 07:55.780 --> 07:57.580 so they tell it to all the MIT freshmen 07:57.580 --> 08:00.200 when you take your first physics course. 08:00.200 --> 08:01.660 But it's a really important reminder 08:01.660 --> 08:03.430 that we have a tendency, as humans, 08:03.430 --> 08:05.360 to wanna wish away the hard parts of problems 08:05.360 --> 08:06.900 and really try to make them as simple 08:06.900 --> 08:08.590 as we know how to solve them, 08:08.590 --> 08:10.790 instead of solving the real problems. 08:10.790 --> 08:12.290 Part of the challenge of that, of course, 08:12.290 --> 08:14.240 is that we sometimes forget 08:14.240 --> 08:16.140 that when we're addressing a complex problem, 08:16.140 --> 08:17.920 like some of the problems we asked the DIB 08:17.920 --> 08:19.530 to look at for us, 08:19.530 --> 08:23.740 no matter what actions we take to address those problems, 08:23.740 --> 08:25.320 there are always gonna be consequences, 08:25.320 --> 08:27.063 some of which will be negative. 08:27.920 --> 08:30.330 You will take actions that you try to optimize 08:30.330 --> 08:33.350 the positive outcomes against the negative outcomes, 08:33.350 --> 08:36.150 but these complex problems always involve people, 08:36.150 --> 08:39.560 and so you're always gonna have social, financial issues, 08:39.560 --> 08:42.160 you're gonna have security-related issues, 08:42.160 --> 08:46.280 and you're trying to balance all of those different equities 08:46.280 --> 08:48.810 in a way that manifests on the outside that on, 08:48.810 --> 08:49.730 sorry, on the output, 08:49.730 --> 08:52.510 that you get more positive than negative. 08:52.510 --> 08:55.180 But there will be negative in the decisions that we make 08:55.180 --> 08:56.550 and we have to plan for that. 08:56.550 --> 08:57.660 We have to look ahead and say, 08:57.660 --> 09:00.000 what are the unintended consequences 09:00.000 --> 09:02.010 of the actions that I am going to take, 09:02.010 --> 09:04.830 to ensure that we're thinking ahead to those negatives. 09:04.830 --> 09:06.100 I think that's a part of the reason 09:06.100 --> 09:07.880 why we have to remember the world is complex 09:07.880 --> 09:11.010 and the problems that we're asking of our colleagues 09:11.010 --> 09:13.540 to help us solve are extraordinarily complex. 09:13.540 --> 09:16.543 And, again, humility is a really important part of this. 09:18.510 --> 09:20.960 I get nervous when I hear very simplistic thinking 09:20.960 --> 09:23.170 and I think part of the challenge with that 09:23.170 --> 09:26.100 is that people are very reliant on analogies. 09:26.100 --> 09:28.780 Analogies are really great for what they do 09:28.780 --> 09:31.820 but we have to be very careful not to over-rely on them 09:31.820 --> 09:34.820 or overextend their utility. 09:34.820 --> 09:36.710 They're essentially models and, like any model, 09:36.710 --> 09:39.333 they're not a perfect representation of reality. 09:40.333 --> 09:42.880 One of the analogies I'm hearing a lot 09:42.880 --> 09:46.130 that I'm not too fond of is the term race. 09:46.130 --> 09:49.333 We're in a race with country X over technology Y. 09:50.190 --> 09:51.590 You can fill in your favorite country 09:51.590 --> 09:52.620 and your favorite technology. 09:52.620 --> 09:55.163 We're in a race with China over AI, right? 09:56.970 --> 09:58.650 The problem with that is a race implies 09:58.650 --> 10:00.560 there's a finish line. 10:00.560 --> 10:02.790 And there is no finish line. 10:02.790 --> 10:04.890 So, we need to take a long view 10:04.890 --> 10:07.040 on all of the things that we're thinking about, 10:07.040 --> 10:09.060 whether it's biotechnology, whether it's 5G, 10:09.060 --> 10:11.690 whether it's AI, whether it's supply chain. 10:11.690 --> 10:13.630 Because when we think in terms of a finish line 10:13.630 --> 10:17.000 and we say, well, I wanna be ahead of country X by year Y, 10:17.000 --> 10:19.070 we actually can put policies in place 10:19.070 --> 10:20.580 and make decisions that will get us 10:20.580 --> 10:22.460 ahead of country X by year Y. 10:22.460 --> 10:24.270 And those same policies and decisions 10:24.270 --> 10:26.373 can then put us way behind later on. 10:27.370 --> 10:29.610 I will give you a concrete example of that. 10:29.610 --> 10:30.783 It's called ITAR. 10:31.760 --> 10:35.250 ITAR did a really good job of giving us an advantage 10:35.250 --> 10:37.363 for a while in the aerospace domain. 10:38.260 --> 10:42.150 It also did a lot of damage to us in terms of the long game. 10:42.150 --> 10:44.770 So, we have to be very thoughtful 10:44.770 --> 10:47.300 when it comes to complex problems and not oversimplify them, 10:47.300 --> 10:49.250 even in terms of the analogies we use 10:49.250 --> 10:51.110 to try to understand them. 10:51.110 --> 10:53.070 That's the first point I wanted to make. 10:53.070 --> 10:56.490 Second point I wanted to make is, again, 10:56.490 --> 10:58.010 especially for the scientist engineers, 10:58.010 --> 10:59.780 you'll understand this, 10:59.780 --> 11:02.800 it is about velocity and not speed. 11:02.800 --> 11:03.890 There's a big difference, right? 11:03.890 --> 11:05.560 Velocity is a vector. 11:05.560 --> 11:06.930 I don't care how fast you're running 11:06.930 --> 11:08.730 if you're running over the edge of a cliff. 11:08.730 --> 11:10.430 It's not gonna do you any good. 11:10.430 --> 11:12.830 We don't want to do stupid-fast. 11:12.830 --> 11:14.770 I'm a little bit concerned because I think, 11:14.770 --> 11:17.240 in the spirit of trying to move more quickly, 11:17.240 --> 11:20.340 and there's a lot of slow, sluggishness in the Pentagon, 11:20.340 --> 11:22.800 and oh my goodness, yes, that is true, 11:22.800 --> 11:24.470 nonetheless, you have to be careful 11:24.470 --> 11:26.620 when you respond to that sluggishness 11:26.620 --> 11:29.880 not to swing the pendulum so far to the other side 11:29.880 --> 11:32.060 that you're not doing the due diligence you need to do 11:32.060 --> 11:35.470 before you make a decision on how you wanna move forward. 11:35.470 --> 11:39.240 For example, I would assert, with the strongest fortitude, 11:39.240 --> 11:42.630 that peer review and the scientific method 11:42.630 --> 11:47.040 should never ever be compromised in the name of speed. 11:47.040 --> 11:51.220 These are not things that you just do out of convenience. 11:51.220 --> 11:52.700 These are actual things we do 11:52.700 --> 11:54.130 because, as scientists and engineers, 11:54.130 --> 11:57.260 we believe in the importance of peer review 11:57.260 --> 11:58.710 and scientific method. 11:58.710 --> 12:03.670 So, I'm a little concerned because I see a lot of spirit 12:03.670 --> 12:05.820 and momentum behind the concept of speed 12:05.820 --> 12:07.240 and I keep trying to remind people, 12:07.240 --> 12:09.610 it's velocity, it's not speed. 12:09.610 --> 12:11.890 Let's make sure that before we run really fast, 12:11.890 --> 12:14.600 we at least know we're going in the right direction. 12:14.600 --> 12:16.670 Part of doing that is making sure 12:16.670 --> 12:20.840 that we're assessing properly and with independent thought 12:20.840 --> 12:23.720 the ideas that are presented to us to pursue. 12:23.720 --> 12:26.540 Again, this is why having organizations like the DIB 12:26.540 --> 12:27.560 are so important, 12:27.560 --> 12:29.870 because they don't have a vested interest in the outcome. 12:29.870 --> 12:32.720 They're genuinely trying to bring an independent perspective 12:32.720 --> 12:34.950 and to say, all right, before you go in a direction 12:34.950 --> 12:37.290 and move quickly, let's at least design a framework 12:37.290 --> 12:39.020 that we all think makes sense. 12:39.020 --> 12:40.310 So, again, that kind of spirit 12:40.310 --> 12:41.930 of independent review and assessment 12:41.930 --> 12:43.800 is extremely important. 12:43.800 --> 12:45.730 It doesn't mean that we shouldn't be eliminating 12:45.730 --> 12:48.570 a lot of the bureaucracy that doesn't add value. 12:48.570 --> 12:49.550 That's not what I'm saying, 12:49.550 --> 12:52.020 but I'm saying, as we try to move forward, 12:52.020 --> 12:53.760 if we find ourselves in a position 12:53.760 --> 12:56.680 that we're making awards on contracts so quickly 12:56.680 --> 12:58.440 that we're not even reviewing the contracts 12:58.440 --> 13:00.920 to make sure the proposed ideas have technical merit, 13:00.920 --> 13:02.380 then we're moving too fast. 13:02.380 --> 13:05.543 We have to make sure we're at least doing our diligence. 13:06.670 --> 13:08.490 The ultimate success metric, remember, 13:08.490 --> 13:11.320 it's not speed, it's mission impact. 13:11.320 --> 13:13.583 Again, you're not going to transform the future 13:13.583 --> 13:17.470 and you're not gonna deliver transformative technologies 13:17.470 --> 13:18.780 to our warfighters 13:18.780 --> 13:20.240 if what we deliver doesn't work 13:20.240 --> 13:23.010 because we didn't do our due diligence. 13:23.010 --> 13:25.230 Related to this, fail fast. 13:25.230 --> 13:27.560 This is another bumper sticker I'm not too fond of 13:27.560 --> 13:30.720 and it's because I don't think it has any meaning. 13:30.720 --> 13:33.050 Because failures are not all created equal. 13:33.050 --> 13:35.950 I'm a little concerned that, again, in the mantra of fail. 13:41.613 --> 13:44.946 (audio static gurgling) 17:21.037 --> 17:21.950 - Let me just say, 17:21.950 --> 17:24.220 first of all, thank you so much, Dr. Porter, 17:24.220 --> 17:27.010 for those remarks and that perspective on the work of R&E 17:27.010 --> 17:29.970 and how the Defense Innovation Board fits into that. 17:29.970 --> 17:31.700 I wanted to remind everyone 17:31.700 --> 17:33.970 that after this very brief update, 17:33.970 --> 17:36.140 we will have the chance to hear from you. 17:36.140 --> 17:38.280 So, if you don't have one of these comment cards, 17:38.280 --> 17:40.300 my teammates are passing them around. 17:40.300 --> 17:41.520 All you have to do is put your name 17:41.520 --> 17:42.890 and contact information on here, 17:42.890 --> 17:44.950 maybe jot down a couple thoughts we'd like to say, 17:44.950 --> 17:46.020 and as those come up, 17:46.020 --> 17:49.010 then I'll call on people at the microphones 17:49.010 --> 17:51.330 that are all over the place, in every aisle. 17:51.330 --> 17:53.340 Really would be great to hear from you. 17:53.340 --> 17:57.550 In the meantime, let me say a couple words 17:57.550 --> 18:02.470 about how the board's recommendations have been received. 18:02.470 --> 18:07.230 It occurs to me, Dr. Lander, in response to your question, 18:07.230 --> 18:09.130 that what we might do, in going forward, 18:09.130 --> 18:10.960 is restructure this presentation 18:10.960 --> 18:12.550 that I've been giving these sessions, 18:12.550 --> 18:15.070 to really include more of a focus on the SWAP study 18:15.070 --> 18:17.370 and less of a focus on the previous recommendations. 18:17.370 --> 18:19.867 That way, we'll get that progress report. 18:21.850 --> 18:25.840 Let me just mention, it was said earlier, 18:25.840 --> 18:27.380 we are a federal advisory committee board, 18:27.380 --> 18:28.850 so we do not get to implement, 18:28.850 --> 18:30.910 but the law does state that the board members 18:30.910 --> 18:33.700 and other members of FACA boards are entitled to know 18:33.700 --> 18:36.500 how the government has received the recommendations 18:36.500 --> 18:38.353 and what actions they're taking. 18:40.290 --> 18:42.110 What we've done here 18:42.110 --> 18:45.750 is we've organized the board's 16 primary proposals 18:45.750 --> 18:49.170 and at these meetings, we always pick about half of them, 18:49.170 --> 18:51.170 and give an update on what the department's doing 18:51.170 --> 18:52.560 in these thematic areas. 18:52.560 --> 18:54.770 We chose eight to emphasize today. 18:54.770 --> 18:56.640 Let me start with recommendation number two, 18:56.640 --> 18:59.270 fittingly, very adjacent to software study, 18:59.270 --> 19:01.310 which was to make computer science 19:01.310 --> 19:03.780 a core competency of the department. 19:03.780 --> 19:05.750 I wanted to highlight two things 19:05.750 --> 19:06.930 that I think are really notable 19:06.930 --> 19:09.360 and in keeping with the spirit of the software study. 19:09.360 --> 19:11.670 First is, the Defense Digital Service, 19:11.670 --> 19:13.480 which the board knows well, 19:13.480 --> 19:15.050 has a program called Jyn Erso, 19:15.050 --> 19:18.200 which is designed to really foster that digital talent 19:18.200 --> 19:20.110 and software talent in the department. 19:20.110 --> 19:21.540 They've just expanded this program 19:21.540 --> 19:22.890 in partnership with Army Cyber, 19:22.890 --> 19:26.050 and just opened a facility, actually, in Georgia, 19:26.050 --> 19:27.200 where they'll be carrying out that work 19:27.200 --> 19:28.520 on a much wider scale, 19:28.520 --> 19:31.040 being able to reach a lot more Army personnel. 19:31.040 --> 19:32.770 They have new programs for accelerating 19:32.770 --> 19:35.290 the training pipeline for Army Cyber. 19:35.290 --> 19:38.630 I think they've managed to get it down by two-thirds, 19:38.630 --> 19:40.990 and they're expanding their work on bug bounties, 19:40.990 --> 19:42.280 Hack the Pentagon, and others, 19:42.280 --> 19:45.240 as well as their drone detection program, 19:45.240 --> 19:48.280 where they have young Army soldiers enlisted 19:48.280 --> 19:49.460 who's designing their own software 19:49.460 --> 19:51.840 for detecting and defeating drones. 19:51.840 --> 19:54.110 Kessel Run has come up a few times today 19:54.110 --> 19:56.310 and I wanted to mention one of the latest accomplishments 19:56.310 --> 19:57.890 out of the Kessel Run team in Boston, 19:57.890 --> 19:59.420 which is the Kronos app, 19:59.420 --> 20:01.600 which has managed to get an enormous reduction 20:01.600 --> 20:03.420 in planning time for F-35 maintenance, 20:03.420 --> 20:05.690 which, as you know, just earlier today, 20:05.690 --> 20:07.250 we heard from Ellen Lord 20:07.250 --> 20:08.840 how important that is to the department. 20:08.840 --> 20:10.820 Really significant progress there 20:10.820 --> 20:12.270 with Army and with Air Force. 20:13.840 --> 20:16.330 I also wanted to mention 20:16.330 --> 20:17.930 some really exciting things we've seen 20:17.930 --> 20:20.470 with the sort of maker movement in the Marine Corps, 20:20.470 --> 20:22.550 embracing culture of experimentation. 20:22.550 --> 20:24.960 This is a specifically interesting one. 20:24.960 --> 20:27.530 They've managed to figure out how to print and harden 20:27.530 --> 20:29.590 the door handles of Humvees. 20:29.590 --> 20:31.840 As you can imagine, there's a lot of wear and tear. 20:31.840 --> 20:32.970 It's not always feasible 20:32.970 --> 20:35.230 to be able to get those parts from the manufacturer 20:35.230 --> 20:37.490 and it's always extremely expensive when they do, 20:37.490 --> 20:40.740 so being able to print these and have the printed versions 20:40.740 --> 20:44.580 meet the rigorous MIL-SPEC standards was a big deal. 20:44.580 --> 20:46.560 But they went, I think, an important step further, 20:46.560 --> 20:48.830 which is they figured out a way to share those files 20:48.830 --> 20:50.670 with every unit in the Marine Corps, 20:50.670 --> 20:53.330 so now, whenever they come up with a CAD file 20:53.330 --> 20:55.470 for one of those parts, it can be shared and printed, 20:55.470 --> 20:58.310 which is a big part of the vision that we've talked about 20:58.310 --> 21:00.020 in the Marine Corps and the board has expressed 21:00.020 --> 21:01.670 about how we'd be able to try to do 21:01.670 --> 21:05.180 that sort of from-software-to-impact, just-in-time 21:05.180 --> 21:07.610 widely distributed anywhere in a resilient fashion. 21:07.610 --> 21:08.460 It's pretty cool. 21:11.320 --> 21:13.060 Of course, artificial intelligence 21:13.060 --> 21:15.660 has been one of the board's highest priorities 21:15.660 --> 21:18.220 and did recommend what became the JAIC 21:18.220 --> 21:20.520 in recommendation number five. 21:20.520 --> 21:22.010 But there is actually a couple other things 21:22.010 --> 21:22.947 that are happening in the department. 21:22.947 --> 21:24.770 You've heard a little bit from the Army 21:24.770 --> 21:27.440 about the task force that they've stood up 21:27.440 --> 21:28.890 at Carnegie Mellon. 21:28.890 --> 21:31.560 That's a big move for the Army, creating that task force, 21:31.560 --> 21:33.027 and we're gonna be working closely with them 21:33.027 --> 21:34.810 to try to help the Army 21:34.810 --> 21:38.410 drive adoption of artificial intelligence in the near term. 21:38.410 --> 21:40.360 An update on progress the JAIC is making. 21:40.360 --> 21:43.990 They are working with SOCOM and actually every service 21:43.990 --> 21:45.580 to do a predictive maintenance project 21:45.580 --> 21:47.120 with the H-60 fleet. 21:47.120 --> 21:49.540 The choice of the H-60 helicopter is interesting 21:49.540 --> 21:50.760 'cause it's one of the only platforms 21:50.760 --> 21:52.520 that every service uses. 21:52.520 --> 21:54.200 So, this is a way to try to scale 21:54.200 --> 21:55.990 rapid adoption of predictive maintenance 21:55.990 --> 21:58.100 using commercially mature machine-learning tools, 21:58.100 --> 22:00.200 so we're gonna follow that pretty closely. 22:01.300 --> 22:03.993 On recommendation number six, Acquisition Innovation, 22:04.920 --> 22:06.660 pretty interesting to see the Pitch Day 22:06.660 --> 22:09.470 that Will Roper and the Air Force put together 22:09.470 --> 22:11.060 in New York City. 22:11.060 --> 22:14.520 I think it may be the fastest from the pitch 22:14.520 --> 22:16.180 to decision to money transferred 22:16.180 --> 22:17.420 in the history of the department. 22:17.420 --> 22:19.150 They were using the purchasing power 22:19.150 --> 22:20.270 of our government credit cards 22:20.270 --> 22:22.610 to be able to get small amounts of money 22:22.610 --> 22:24.780 to firms in minutes. 22:24.780 --> 22:26.500 They had a series of pitches over 50, 22:26.500 --> 22:27.730 they made a series of awards 22:27.730 --> 22:30.030 based on the strength of those pitches from small companies, 22:30.030 --> 22:32.070 and they managed to transfer those funds 22:32.070 --> 22:33.510 essentially instantaneously. 22:33.510 --> 22:35.150 It's pretty remarkable, what they're trying to do, 22:35.150 --> 22:38.510 to bring years out of the acquisition cycle 22:38.510 --> 22:40.140 for the Air Force. 22:40.140 --> 22:41.360 The other thing I wanted to highlight is, you know, 22:41.360 --> 22:43.450 we've been working really closely 22:43.450 --> 22:45.190 with Ben Fitzgerald when he was on board, 22:45.190 --> 22:47.870 on revising the other transaction authorities, 22:47.870 --> 22:50.140 working very closely with Ms. Lord and her team, 22:50.140 --> 22:53.660 and they just did a revision of the OTA handbook. 22:53.660 --> 22:55.320 Apart from thinking it's really important 22:55.320 --> 22:56.410 that we're trying to figure out ways 22:56.410 --> 22:57.940 to smooth out the use of OTAs, 22:57.940 --> 22:59.290 which is, of course, sort of the backbone 22:59.290 --> 23:01.330 of how the Defense Innovation Unit operates, 23:01.330 --> 23:02.320 it's also interesting to note 23:02.320 --> 23:03.740 that they put out the policy change 23:03.740 --> 23:07.990 about a year and change after the last guidance. 23:07.990 --> 23:10.330 So, they're trying to apply the iterative approach 23:10.330 --> 23:11.690 you used for the software study, 23:11.690 --> 23:14.250 and that you recommended for software, to policy-making. 23:14.250 --> 23:16.650 That, I think, is a really important move forward 23:16.650 --> 23:18.080 in how the department tries to figure 23:18.080 --> 23:20.280 how to make acquisition happen a lot faster. 23:23.210 --> 23:24.300 Recommendation number seven 23:24.300 --> 23:27.430 was really new approaches to innovation 23:27.430 --> 23:30.227 and I thought I'd highlight what Hondo Geurts, 23:30.227 --> 23:32.030 the SAE for the Navy, has done 23:32.030 --> 23:34.420 with the creation of the NavalX Team, 23:34.420 --> 23:36.763 which is a joint Navy-Marine Corps effort. 23:37.630 --> 23:39.300 With NavalX, it's a very small team, 23:39.300 --> 23:40.550 but they're designed to try 23:40.550 --> 23:43.130 to change the culture and the practice 23:43.130 --> 23:45.050 by giving more user stories, 23:45.050 --> 23:47.290 more training, more platforms, opportunities, 23:47.290 --> 23:50.630 to highlight who is doing interesting and disruptive things, 23:50.630 --> 23:53.250 support them, and then scale those changes. 23:53.250 --> 23:56.110 So, we're excited to see the arrival of NavalX on the scene 23:56.110 --> 23:57.850 and we'll continue to get updates from them 23:57.850 --> 23:59.453 on what successes they've had. 24:02.480 --> 24:06.010 This is one that also is quite close to the software study 24:06.010 --> 24:07.860 which is an issue that, as Richard noted, 24:07.860 --> 24:08.970 has been more controversial 24:08.970 --> 24:10.300 than some of the other board recommendations, 24:10.300 --> 24:11.940 which is access to code. 24:11.940 --> 24:14.610 I wanted to mention, the Strategic Capabilities Office, 24:14.610 --> 24:16.550 which is doing a lot of work on autonomy, 24:16.550 --> 24:19.490 and particularly working with DARPA on surface ships, 24:19.490 --> 24:21.010 figuring out maritime autonomy, 24:21.010 --> 24:22.310 and one of the challenges they've seen 24:22.310 --> 24:25.010 is that there are multiple different autonomous systems 24:25.010 --> 24:27.400 that the Navy uses for navigation at sea, 24:27.400 --> 24:30.240 and they often have different code 24:30.240 --> 24:32.070 that they use to guide that autonomy. 24:32.070 --> 24:33.850 So, they're trying to figure out a common system 24:33.850 --> 24:37.525 which is maybe the best acronym that we've seen, CARACaS. 24:37.525 --> 24:38.720 (Josh chuckles) 24:38.720 --> 24:39.980 This is a way to try to have 24:39.980 --> 24:42.030 a better government purpose rights 24:42.030 --> 24:44.020 on the code written for autonomy 24:44.020 --> 24:46.170 so that, at some point, you could try to converge 24:46.170 --> 24:48.720 on a single set of code standards 24:48.720 --> 24:51.420 for all of the maritime autonomy for surface vessels, 24:51.420 --> 24:52.253 which, you can imagine, 24:52.253 --> 24:54.010 if you'd wanna one day scale to swarms, 24:54.010 --> 24:55.860 this is really necessary to figure out how to do that 24:55.860 --> 24:57.610 and SCO has had some success there. 25:03.640 --> 25:05.640 Recommendation number 10 for the board 25:05.640 --> 25:07.450 has really been about abundance 25:07.450 --> 25:09.200 in transport bandwidth and compute, 25:09.200 --> 25:12.230 something that this board's emphasized a great deal. 25:12.230 --> 25:14.900 The Army is moving out on its own cloud program office. 25:14.900 --> 25:16.290 We've had a series of meetings with them 25:16.290 --> 25:19.430 and they are figuring out a sort of rapid pathway 25:19.430 --> 25:22.640 to try to bring not all, but as many as possible, 25:22.640 --> 25:24.660 of the Army's systems into the cloud, 25:24.660 --> 25:26.720 so they've asked for some consultations with us 25:26.720 --> 25:28.820 on how to do that, how to move their appropriate 25:28.820 --> 25:29.850 and triage the workloads 25:29.850 --> 25:32.320 and try to get Army to cloud faster. 25:32.320 --> 25:34.430 And last, I wanted to talk about data. 25:34.430 --> 25:36.020 This was one of the last recommendations 25:36.020 --> 25:38.003 the board did at the end of last year. 25:39.080 --> 25:41.500 We have seen a growing convergence 25:41.500 --> 25:43.010 among the leaders of the services, 25:43.010 --> 25:44.600 understanding that they need to have 25:44.600 --> 25:46.880 greater interoperability of data standards 25:46.880 --> 25:49.250 if they wanna really use data as a strategic asset 25:49.250 --> 25:50.200 as the board had said. 25:50.200 --> 25:52.420 So, there's actually a new directive 25:52.420 --> 25:53.950 from all the leaders of the services 25:53.950 --> 25:57.070 directing a common set of standards 25:57.070 --> 25:58.830 that would allow a greater degree of sharing 25:58.830 --> 26:00.830 across all the sensors and platforms, 26:00.830 --> 26:02.650 which, again, very consistent with the worldview 26:02.650 --> 26:04.490 the board's been espousing. 26:04.490 --> 26:06.373 Any questions about any of those? 26:08.080 --> 26:09.290 That's good, okay, all right. 26:09.290 --> 26:11.150 - Nothing. - Great. 26:11.150 --> 26:12.850 Now, we get to do public comments. 26:17.360 --> 26:19.140 Please wave them in the air. 26:19.140 --> 26:21.622 A member of my team will pick them up. 26:21.622 --> 26:23.563 - [Man] We have to bring them down. 26:23.563 --> 26:24.934 - [Man] We'll just use your name. 26:24.934 --> 26:27.650 - Yeah, we need to know who's speaking. 26:27.650 --> 26:30.000 We have one, we'll start with Gwyneth Woolwine. 26:36.954 --> 26:39.030 - [Gwyneth] What am I supposed to say again? 26:39.030 --> 26:40.210 - Oh, I'm so sorry. 26:40.210 --> 26:42.641 Gwyneth, you are very welcome to approach the microphone. 26:42.641 --> 26:44.315 - [Man] Yeah, do you mind using the mic? 26:44.315 --> 26:45.148 - [Gwyneth] No, I'm sorry. 26:45.148 --> 26:45.981 (audience members chuckling) 26:45.981 --> 26:47.750 - I'm happy to hand this back to you. 26:47.750 --> 26:50.540 We have the same problem in Pittsburgh. 26:50.540 --> 26:51.700 We can give it to Brenda when you're done. 26:51.700 --> 26:53.023 But thank you, Gwyneth. 26:54.560 --> 26:55.860 I just wanna remind everyone 26:55.860 --> 26:56.810 that these are two-minute comments, 26:56.810 --> 26:58.690 so if you're 30 seconds off, I'll just give you, 26:58.690 --> 27:00.733 I'll tap on the mic. 27:02.380 --> 27:04.800 - [Eric Schmidt] Let's see, we have mics on over here, 27:04.800 --> 27:06.560 here, and here, so you have three choices. 27:06.560 --> 27:07.393 - [Joshua] Great. 27:07.393 --> 27:09.110 Next, we have Bobby Cunningham. 27:09.110 --> 27:10.660 If you're here, you're on deck. 27:12.290 --> 27:14.200 And if, that'd be great. 27:14.200 --> 27:15.823 Okay, we'll start with you. 27:16.980 --> 27:18.050 - Is it on? 27:18.050 --> 27:19.000 Great. - It is on. 27:20.370 --> 27:22.830 - I'm with the staff of the Senate Armed Services Committee, 27:22.830 --> 27:25.420 the Senate Armed Services Committee version 27:25.420 --> 27:27.740 of the National Defense Authorization 27:27.740 --> 27:31.500 was the version of the bill to originally carry the study 27:31.500 --> 27:35.123 that directed the DIB to look at software. 27:36.040 --> 27:38.930 I wanted to say that we are very excited 27:38.930 --> 27:41.590 to continue to tackle these complex issues 27:41.590 --> 27:43.630 with the board and with the department, 27:43.630 --> 27:46.690 and we applaud the candid nature of the discussion, 27:46.690 --> 27:50.940 the professionalism of the members and staff 27:50.940 --> 27:53.710 in engaging what have been often difficult 27:53.710 --> 27:55.980 and even emotional challenges and barriers 27:55.980 --> 27:58.930 that the department and industry face 27:58.930 --> 28:00.610 in trying to move forward together. 28:00.610 --> 28:02.483 So, I just wanted to say, bravo. 28:03.410 --> 28:04.332 Thanks. - Thank you very much. 28:04.332 --> 28:06.913 (audience applauding) 28:06.913 --> 28:08.557 - Go ahead. 28:08.557 --> 28:10.033 And who's on deck, Josh? 28:11.522 --> 28:12.410 - [Joshua] Oh. 28:12.410 --> 28:13.313 Wait, here we go. 28:14.800 --> 28:15.633 - Hi there. 28:16.860 --> 28:19.500 Bobby Cunningham, I'm a federal advisor with Omnity. 28:19.500 --> 28:22.590 Just wanna thank you all for the time 28:22.590 --> 28:26.070 and your hard work on these really important topics, 28:26.070 --> 28:28.880 ethical use of artificial intelligence 28:28.880 --> 28:31.743 as well as the software acquisition process. 28:33.180 --> 28:34.390 I was particularly pleased 28:34.390 --> 28:36.080 by Under Secretary Lord's comments 28:36.080 --> 28:39.090 about, you know, the government-furnished equipment 28:40.010 --> 28:41.320 in these hardened containers 28:41.320 --> 28:45.383 where industry can come in and work with the government. 28:46.350 --> 28:48.110 Really appreciate that 28:48.110 --> 28:51.093 and looking forward to reading your final report. 28:53.680 --> 28:55.650 Little bit more on Omnity. 28:55.650 --> 28:57.780 As we enter an increasingly digital world, 28:57.780 --> 28:59.780 explosion of knowledge, information, 28:59.780 --> 29:01.000 but also misinformation, 29:01.000 --> 29:03.220 I think there are a set of new challenges 29:03.220 --> 29:06.900 that will arise and have already started to arise. 29:06.900 --> 29:09.570 I think the work that you all are doing on this 29:09.570 --> 29:11.470 really kinda gets to the core of that. 29:12.880 --> 29:15.220 One of these challenge areas is data processing 29:15.220 --> 29:18.660 and ethical curation of that data. 29:18.660 --> 29:21.000 Omnity's a semantic search platform, 29:21.000 --> 29:23.123 sort of document as a query. 29:24.680 --> 29:28.490 Also, it's a decentralized knowledge curation platform, 29:28.490 --> 29:30.983 interconnecting document repositories at scale. 29:31.860 --> 29:34.610 We've also launched with a handful of other companies 29:34.610 --> 29:36.930 what we're calling the WisdomTech Society 29:36.930 --> 29:39.730 to raise consciousness, increase collective intelligence, 29:39.730 --> 29:43.460 develop industry standards, and expose misinformation, 29:43.460 --> 29:45.700 and, to kinda take a mantra 29:45.700 --> 29:48.613 familiar to probably a couple of you, do no evil. 29:49.960 --> 29:53.170 I encourage the board and also the Pentagon 29:53.170 --> 29:54.530 to consider what Omnity 29:54.530 --> 29:56.710 and the WisdomTech Society can offer. 29:56.710 --> 29:59.410 We're based in Menlo Park, so we're also planning to attend 29:59.410 --> 30:03.950 the April and June meetings 30:03.950 --> 30:06.370 and I'd be happy to follow up with anyone on the board 30:06.370 --> 30:08.460 or in this room after. 30:08.460 --> 30:09.520 Thank you again. 30:09.520 --> 30:11.317 - Okay, thank you very much. - Thank you. 30:11.317 --> 30:12.803 And next, we have Halimah. 30:14.240 --> 30:15.073 - Thank you. 30:15.073 --> 30:16.190 My name is Halimah Locke 30:16.190 --> 30:19.340 and I am a staffer on the House Armed Services Committee 30:19.340 --> 30:21.190 for Chairman Adam Smith 30:21.190 --> 30:25.050 and I just again want to really thank the DIB SWAP 30:25.050 --> 30:28.040 for this really, really thoughtful report. 30:28.040 --> 30:29.570 I think I can't iterate enough 30:29.570 --> 30:33.140 how just important this is and how timely this is. 30:33.140 --> 30:35.190 It's responsive to our needs 30:35.190 --> 30:38.060 and I want to specifically shout out the thoughtfulness 30:38.060 --> 30:41.360 around the crafting of the 805 recommendation 30:41.360 --> 30:44.170 and how that is actually responsive 30:44.170 --> 30:47.580 to congressional intent that was present previously 30:47.580 --> 30:48.780 and done by my colleagues, 30:48.780 --> 30:51.490 and how that's going to actually streamline 30:51.490 --> 30:55.220 and kind of meld what we're trying to do 30:55.220 --> 30:58.360 as far as bringing the industrial base to the fore 30:58.360 --> 31:00.210 and building the innovation base. 31:00.210 --> 31:02.210 I thank you for that thoughtfulness. 31:02.210 --> 31:06.230 I also want to really say I appreciate the awareness 31:06.230 --> 31:08.240 of broader acquisition efforts 31:08.240 --> 31:10.240 that are present across the government 31:10.240 --> 31:12.020 and specific to the DOD 31:12.020 --> 31:15.160 and your shouting out of the program management 31:15.160 --> 31:18.890 as evident in your PEO Digital recommendation downstream, 31:18.890 --> 31:21.950 as well as your comments around intellectual property 31:21.950 --> 31:23.720 and how that is dealt with. 31:23.720 --> 31:27.960 I look forward to seeing how this is integrated, 31:27.960 --> 31:32.300 both at the department level and in our efforts on Congress 31:32.300 --> 31:34.730 to really listen to the report 31:34.730 --> 31:37.080 and take from it what we can 31:37.080 --> 31:40.990 to actually give the tools to those that are using this. 31:40.990 --> 31:43.500 I again wanna thank you for the vignette 31:43.500 --> 31:47.110 because that adds texture when we're trying to explain 31:47.110 --> 31:49.860 how timely this is, how important this is, 31:49.860 --> 31:53.450 and how this actually creates a better warfighter. 31:53.450 --> 31:55.400 So, thank you so much. 31:55.400 --> 31:57.000 - Well, thank you very, very much. 31:57.000 --> 31:58.990 Can we get just a quick showing of hands 31:58.990 --> 32:02.010 of people who have interacted with us on the SWAP study, 32:02.010 --> 32:03.620 some people who helped us? 32:03.620 --> 32:04.453 Right. - That's great. 32:04.453 --> 32:06.275 - Can we get some thanks for all those people, too? 32:06.275 --> 32:09.442 (audience applauding) 32:12.850 --> 32:13.743 Yes, sir. 32:15.350 --> 32:16.250 - Here's a comment. 32:16.250 --> 32:19.440 Maybe I missed this, I have not read the report, 32:19.440 --> 32:22.280 but to what degree the report reflects 32:22.280 --> 32:25.860 the contemporary environment of apps 32:25.860 --> 32:29.040 as developed to actually to, 32:29.040 --> 32:32.550 for apps that reside in flexible platforms. 32:32.550 --> 32:35.550 The iPhone is really remarkable as an instrument 32:35.550 --> 32:38.720 to gather data, to actually, 32:38.720 --> 32:40.667 to gather accelerometer data. 32:40.667 --> 32:42.250 That's absolutely marvelous. 32:42.250 --> 32:46.100 To what degree your report actually reflects ability 32:46.100 --> 32:50.140 to embed, to develop apps in an apps ecosystem? 32:50.140 --> 32:52.520 That's the first question, the first issue. 32:52.520 --> 32:54.690 The second issue is regard to Mr., 32:54.690 --> 32:57.340 to the remarks surmised about bandwidth. 32:57.340 --> 32:58.910 Bandwidth is not only important 32:58.910 --> 33:02.720 in terms of the bandwidth that is available 33:02.720 --> 33:04.140 but also to actually, 33:04.140 --> 33:06.640 to deliver bandwidth to the battlefield. 33:06.640 --> 33:10.440 Developing microwave bandwidth to, it doesn't, 33:10.440 --> 33:13.570 bandwidth is not really universal at very low frequencies. 33:13.570 --> 33:15.060 Thank you. 33:15.060 --> 33:17.960 - We're not supposed to actually answer your questions. 33:17.960 --> 33:19.690 These are supposed to be more statements from you, 33:19.690 --> 33:21.320 so let's take that as a statement, 33:21.320 --> 33:24.170 that it's important that we anticipate and understand 33:24.170 --> 33:28.139 the Apple ecosystem and the Android ecosystem, I might add. 33:28.139 --> 33:31.020 (all laughing) (Eric Schmidt chuckles) 33:31.020 --> 33:33.830 In your final report, Richard and Michael, 33:33.830 --> 33:37.105 and second your comment about bandwidth. 33:37.105 --> 33:37.938 - [Audience Member] (speaks faintly) Yes, thank you. 33:37.938 --> 33:39.350 - Yes, thank you very much. 33:39.350 --> 33:40.183 Yes, sir. 33:41.070 --> 33:42.940 - Good morning, everyone. 33:42.940 --> 33:44.060 My name's Clay McGuire. 33:44.060 --> 33:46.900 I'm a retired Army officer, recently. 33:46.900 --> 33:49.320 My last tour was at JIDO, 33:49.320 --> 33:52.170 which I know you guys have interacted with. 33:52.170 --> 33:56.270 My statement's about personnel and career management, 33:56.270 --> 33:58.810 specifically, the DIB-identified 33:58.810 --> 34:02.060 innovation centers for excellence. 34:02.060 --> 34:03.950 They already exist in the DOD. 34:03.950 --> 34:05.390 We've been talking about them today. 34:05.390 --> 34:08.453 DDS, we mentioned JIDO Kessel Run. 34:09.970 --> 34:12.280 The board recommended improving communication 34:12.280 --> 34:14.450 between these organizations and DOD 34:14.450 --> 34:17.793 to help educate the rest of the DOD workforce. 34:18.890 --> 34:22.643 My comment is, DOD grooms its best and brightest personnel. 34:24.780 --> 34:26.770 I think that creating a pathway 34:26.770 --> 34:29.480 for DOD's best and brightest personnel, 34:29.480 --> 34:33.100 whether it be leaders or the software personnel 34:33.100 --> 34:35.520 that we know are so important, we talked about today, 34:35.520 --> 34:37.593 but also PMs, contractors, 34:38.880 --> 34:40.350 by pushing their career path 34:40.350 --> 34:43.110 through these organizations for a short time, 34:43.110 --> 34:46.110 that might help create a line of communication 34:46.110 --> 34:47.080 that we're talking about. 34:47.080 --> 34:49.127 As people move through the organizations 34:49.127 --> 34:50.993 and out into the rest of the DOD, 34:52.090 --> 34:53.630 they can carry with them those lessons 34:53.630 --> 34:56.200 and hopefully push innovation forward. 34:56.200 --> 34:58.403 Because I think communication can be best, 34:59.660 --> 35:03.123 is best experienced through personal interaction, 35:04.440 --> 35:08.543 and that that's a good way to share these experiences. 35:10.500 --> 35:12.600 - Okay, thank you very much. - Thank you. 35:12.600 --> 35:13.669 - Yes, sir. - He was in front. 35:13.669 --> 35:14.867 - [Eric Schmidt] Oh, I'm sorry, over here. 35:14.867 --> 35:16.210 - Okay, and then Robert, 35:16.210 --> 35:18.410 and then Mercedes. - Yes, thank you. 35:18.410 --> 35:21.840 Igor Alvarado from National Instruments in Austin, Texas. 35:21.840 --> 35:24.000 Just wanted to thank you for the report. 35:24.000 --> 35:25.670 I haven't seen it, but from the recommendations, 35:25.670 --> 35:28.870 I think is a excellent work. 35:28.870 --> 35:31.660 But I do see that there are a few things missing 35:31.660 --> 35:34.930 that might be something that could be added in the future. 35:34.930 --> 35:38.570 For example, there wasn't too much about operating systems, 35:38.570 --> 35:40.500 drivers, math kernels, 35:40.500 --> 35:43.040 all the hidden things that we forget about. 35:43.040 --> 35:45.450 You might have the best software you might think of, 35:45.450 --> 35:48.525 but you don't have the platform to run it, 35:48.525 --> 35:50.090 you don't have anything, right? 35:50.090 --> 35:51.630 That's one thing I didn't see. 35:51.630 --> 35:54.250 The other one was, or is, actually, 35:54.250 --> 35:57.110 that we're moving into symbiosis 35:57.110 --> 35:58.300 between hardware and software. 35:58.300 --> 36:01.930 I did see the comment that software is not hardware, 36:01.930 --> 36:05.070 which was obviously a message there, 36:05.070 --> 36:08.390 but I think what is happen is totally the opposite. 36:08.390 --> 36:09.710 Hardware is becoming software, 36:09.710 --> 36:11.600 software is becoming hardware. 36:11.600 --> 36:15.400 So, I will say, I would recommend also that in the future, 36:15.400 --> 36:18.890 you add a tracking which you also include new hardware 36:18.890 --> 36:21.510 that actually does computation directly, 36:21.510 --> 36:24.120 like neuromorphic, spiking neural networks, 36:24.120 --> 36:26.400 and things like that, analog computing 36:26.400 --> 36:28.413 that DARPA is actually working on. 36:29.720 --> 36:32.240 I think that that's something I didn't see there also. 36:32.240 --> 36:34.610 I would recommend also to add that. 36:34.610 --> 36:36.160 Finally, think more about 36:36.160 --> 36:37.620 not your software-defining hardware 36:37.620 --> 36:40.240 but also reconfigurable adaptive hardware 36:40.240 --> 36:44.900 that can actually adjust to the computation in real time 36:44.900 --> 36:46.680 that you are trying to perform. 36:46.680 --> 36:48.790 Those are some things that I see critical 36:48.790 --> 36:50.150 for DOD in the future 36:50.150 --> 36:52.750 and I didn't see those in the report, 36:52.750 --> 36:57.690 although, like I said, I really happy for, 36:57.690 --> 36:59.869 to see all the recommendations made. 36:59.869 --> 37:00.893 Thank you. - Okay, thank you. 37:01.980 --> 37:03.540 - [Joshua] Great, and be, well, here, 37:03.540 --> 37:06.203 Robert next, and then Simon, you're on deck, if you're here. 37:06.203 --> 37:08.410 - That's Robert. - And then Mercedes. 37:08.410 --> 37:09.350 Great. 37:09.350 --> 37:10.290 Robert. 37:10.290 --> 37:11.680 - I'm an analyst with the Bin Group. 37:11.680 --> 37:12.600 I just wanted to point out 37:12.600 --> 37:15.480 the apparent contradictive statements from Dr. Porter 37:15.480 --> 37:18.340 and the recent initiative with Air Force Pitch Day 37:18.340 --> 37:20.939 on the speed of contracting. 37:20.939 --> 37:23.010 I think that'll be an interesting point of discussion 37:23.010 --> 37:25.386 moving forward and something to keep an eye out for. 37:25.386 --> 37:27.920 (audience members murmuring) 37:27.920 --> 37:28.847 - Okay, thank you. 37:30.740 --> 37:32.590 - Sir? - Yes, sir. 37:32.590 --> 37:34.206 - Thank you very much for having me here. 37:34.206 --> 37:36.613 Lieutenant-Colonel Simon Poudrier from Canada. 37:37.650 --> 37:39.200 Just a small comment. 37:39.200 --> 37:42.890 With the changing in nature from the hardware focus 37:42.890 --> 37:44.350 to the software focus, 37:44.350 --> 37:46.350 changing in nature a bit of the workforce 37:46.350 --> 37:48.350 towards the hardware-working 37:48.350 --> 37:50.240 to a software-working workforce, 37:50.240 --> 37:52.200 but also with the changes in the population 37:52.200 --> 37:53.570 of the younger generation 37:53.570 --> 37:56.320 wanting to change jobs a few more times 37:56.320 --> 37:58.490 within their careers, too. 37:58.490 --> 38:01.160 There's discussion about moving within DOD, 38:01.160 --> 38:02.090 which is fantastic, 38:02.090 --> 38:03.980 but what about moving in and out of DOD? 38:03.980 --> 38:07.343 What about moving in and out of America? 38:08.540 --> 38:12.840 Including Canada. (audience chuckling) 38:12.840 --> 38:14.410 Just saying, if it's a challenge, 38:14.410 --> 38:17.080 if there's gonna be incentive, 38:17.080 --> 38:21.640 different kind of workforce-related management 38:21.640 --> 38:22.630 that's gonna be involved with this, 38:22.630 --> 38:25.410 'cause we're looking at the same thing in Canada. 38:25.410 --> 38:27.140 It's not about the number of push-ups you do, 38:27.140 --> 38:28.790 it's about your capacity. 38:28.790 --> 38:32.040 Anyway, just a comment-slash-question for you. 38:32.040 --> 38:33.367 - Okay, thank you very much. 38:33.367 --> 38:35.221 - And how many push-ups can you do? 38:35.221 --> 38:36.740 (Neil and audience chuckling) 38:36.740 --> 38:38.582 - [Man] Those are Canadian push-ups. 38:38.582 --> 38:39.415 - [Neil] Canadian push-ups? 38:39.415 --> 38:41.243 Is that what you... (audience laughing) 38:41.243 --> 38:42.199 (Neil laughing) 38:42.199 --> 38:43.199 - [Man] Ooh. 38:44.224 --> 38:46.269 (Eric Lander speaking faintly) 38:46.269 --> 38:47.728 - They're .8 of a U.S. push-up. 38:47.728 --> 38:48.561 - (chuckling) .8 of a U.S. push-up. 38:48.561 --> 38:49.394 - Okay. 38:50.800 --> 38:51.633 Yes, ma'am. 38:53.650 --> 38:56.710 It's hard to follow that one. (all chuckling) 38:56.710 --> 38:58.233 - Yet, I will try. 38:59.830 --> 39:01.410 Good morning. 39:01.410 --> 39:03.010 My name is Mercedes Fitchett. 39:03.010 --> 39:05.030 I'm a civilian with the Defense Department. 39:05.030 --> 39:06.820 I'm actually currently a student 39:06.820 --> 39:08.310 at the Eisenhower School here 39:08.310 --> 39:10.640 at National Defense University. 39:10.640 --> 39:14.150 I was absolutely thrilled that the DIB was going to be here 39:14.150 --> 39:18.060 because I consider this a once-in-a-lifetime opportunity, 39:18.060 --> 39:22.390 and I wanna congratulate and call out the professors 39:22.390 --> 39:25.283 who brought their classes and students here. 39:26.360 --> 39:28.150 For any future DIB meetings, 39:28.150 --> 39:32.170 I think it's fantastic to leverage the DOD infrastructure, 39:32.170 --> 39:35.840 but I think that also there was an opportunity missed 39:35.840 --> 39:38.460 with regards to not getting NDU leadership 39:38.460 --> 39:41.300 to commit the organizations here 39:41.300 --> 39:43.830 to facilitate the opportunity for the students 39:43.830 --> 39:46.910 to make it possible to be here. 39:46.910 --> 39:48.370 The courses that we had here 39:48.370 --> 39:50.470 this morning at Eisenhower School 39:50.470 --> 39:54.120 were acquisition and innovation and industry analytics, 39:54.120 --> 39:56.280 and I think both of those courses 39:56.280 --> 39:59.860 could certainly have been accommodated 39:59.860 --> 40:03.410 to allow for this whole auditorium to have been filled, 40:03.410 --> 40:05.630 because, again, it's the people adoption, 40:05.630 --> 40:08.370 it's the leadership buy-in, it's all levels. 40:08.370 --> 40:12.745 So, in the future, I would love to see a stronger commitment 40:12.745 --> 40:16.550 from DOD organizations to welcome and fully support the DIB. 40:17.950 --> 40:19.830 And thank you for your hard work. 40:19.830 --> 40:21.220 - Thank you, and Josh will give you, 40:21.220 --> 40:24.110 as a graduate of this place, (Josh chuckling) 40:24.110 --> 40:26.960 an action item to more fully integrate 40:26.960 --> 40:28.390 with the National Defense University, 40:28.390 --> 40:29.880 which I know we all admire. 40:29.880 --> 40:30.824 - Yes. 40:30.824 --> 40:32.619 We talked with the ambassador about that earlier. 40:32.619 --> 40:33.452 We're gonna do that. 40:33.452 --> 40:35.571 We have time for two more comments. 40:35.571 --> 40:39.154 We will hear from Victoria and then Rachel. 40:41.140 --> 40:42.110 - Good morning. 40:42.110 --> 40:43.480 My name is Tory Cuff. 40:43.480 --> 40:47.180 I was previously the chief of acquisitions 40:47.180 --> 40:50.973 for the entire Kessel Run effort for the Air Force. 40:52.200 --> 40:54.990 I fullheartedly believe and echo the statements 40:54.990 --> 40:57.360 and am very happy to see all the comments 40:57.360 --> 40:59.000 of internal talent. 40:59.000 --> 41:01.300 I think some of the most innovative people 41:01.300 --> 41:04.370 are the undersold heroes of acquisitions 41:04.370 --> 41:07.110 who are reading through the 5,000-plus pages 41:07.110 --> 41:09.330 of documents that guide them. 41:09.330 --> 41:10.650 And it's not just one. 41:10.650 --> 41:13.690 You have the financial management, the contracting, 41:13.690 --> 41:15.903 the 5000 series, the list goes on. 41:17.050 --> 41:20.440 I do wanna say that, as much as we have champions, 41:20.440 --> 41:22.920 we have to protect those people. 41:22.920 --> 41:26.470 My experience at Kessel Run, as in other offices, 41:26.470 --> 41:29.460 it's the hardest thing for the DOD to do today. 41:29.460 --> 41:32.630 We cannot accelerate careers of people 41:32.630 --> 41:34.820 that are the most promising, 41:34.820 --> 41:37.200 and we can do more for external hires 41:37.200 --> 41:38.513 than we can for internal. 41:40.090 --> 41:41.610 It's something we have to change 41:41.610 --> 41:44.720 because you have a whole slew of internal talent 41:44.720 --> 41:46.870 and definitely incoming talent 41:46.870 --> 41:49.030 that really want to serve 41:49.030 --> 41:51.890 and serve in a civilian capacity or in uniform 41:51.890 --> 41:54.520 that want to keep pushing this forward. 41:54.520 --> 41:57.180 My fundamental belief is that software 41:57.180 --> 41:59.720 is gonna be the differentiator for all of us. 41:59.720 --> 42:01.630 So, if we can't figure out software, 42:01.630 --> 42:05.280 we're nowhere in the next conflict or even in today's. 42:05.280 --> 42:09.770 Very happy to see how much culture and internal hiring, 42:09.770 --> 42:12.120 as well as, we still need to bring in externals, 42:12.120 --> 42:15.700 as this board demonstrates a fine talent 42:15.700 --> 42:19.100 for insights for our community. 42:19.100 --> 42:20.710 Thank you. 42:20.710 --> 42:24.247 - Thank you. (audience applauding) 42:25.090 --> 42:26.780 - It may not be appropriate to say this 42:26.780 --> 42:27.980 but I'm going to say it. 42:28.910 --> 42:30.420 We talk a lot about Kessel Run 42:30.420 --> 42:33.230 and Victoria's really one of the cofounders of Kessel Run. 42:33.230 --> 42:34.740 She did more for software 42:34.740 --> 42:36.820 as anyone I can imagine in the department 42:36.820 --> 42:39.052 and deserves a lot of credit and recognition for that. 42:39.052 --> 42:44.052 (audience members cheering) (all applauding) 42:44.240 --> 42:46.460 And Rachel. - Thanks. 42:46.460 --> 42:47.300 My name's Rachel Hoff. 42:47.300 --> 42:50.730 I'm the policy director at the Ronald Reagan Institute, 42:50.730 --> 42:52.670 which probably most famous in a crowd like this 42:52.670 --> 42:54.830 for our annual Reagan National Defense Forum 42:54.830 --> 42:56.930 out in Simi Valley, at the Reagan Library. 42:59.050 --> 43:01.730 Just wanted to thank the board for your work, 43:01.730 --> 43:05.670 particularly on the software acquisition piece. 43:05.670 --> 43:08.414 Looking forward to certainly the report 43:08.414 --> 43:10.930 on AI and ethical frameworks. 43:10.930 --> 43:12.700 We at the Ronald Reagan Institute 43:12.700 --> 43:15.140 are starting to build out some policy work 43:15.140 --> 43:18.160 in between our annual defense forums, 43:18.160 --> 43:20.710 and just sort of for general awareness, 43:20.710 --> 43:23.190 we'll be joining the proliferation 43:23.190 --> 43:26.060 of task forces and boards. 43:26.060 --> 43:28.470 We're launching this year a task force 43:28.470 --> 43:30.630 focusing on national security, technology, 43:30.630 --> 43:31.980 and workforce issues, 43:31.980 --> 43:34.090 so the work that you have done 43:34.090 --> 43:37.030 very much informs and provides a solid basis 43:37.030 --> 43:38.160 for what we're doing, 43:38.160 --> 43:40.600 which, broadly, is kind of scoping out 43:40.600 --> 43:42.260 beyond the traditional industrial base 43:42.260 --> 43:43.500 how we think about this concept 43:43.500 --> 43:45.533 of a national security innovation base. 43:47.850 --> 43:49.240 We've great bipartisan cochairs 43:49.240 --> 43:51.420 with former Under Secretary Bob Work 43:51.420 --> 43:53.410 and former Senator Jim Talent, 43:53.410 --> 43:55.750 and a dozen commissioners that are gonna help us 43:55.750 --> 43:57.100 think through those issues. 43:58.190 --> 44:00.210 From the ethical frameworks to the software side 44:00.210 --> 44:02.240 to acquisition innovation, 44:02.240 --> 44:03.310 just wanna say thanks for your work 44:03.310 --> 44:05.790 and we look forward to this fall, in November, 44:05.790 --> 44:07.960 putting out a report that hopefully 44:07.960 --> 44:09.680 piques some interest in this room as well. 44:09.680 --> 44:11.077 Thanks. - Thank you. 44:11.077 --> 44:13.570 - Thank you very much. - Great. 44:13.570 --> 44:15.723 Eric, you wanna make any closing remarks? 44:19.066 --> 44:20.620 - As I had mentioned at the beginning, 44:20.620 --> 44:23.220 I could not be prouder of the work of the team 44:23.220 --> 44:25.530 and the engagement we have done. 44:25.530 --> 44:29.487 This changes my view on the value of reports, 44:29.487 --> 44:30.890 (audience members chuckling) so, in that sense, 44:30.890 --> 44:31.820 it's pretty important. 44:31.820 --> 44:34.770 I can imagine a number of others that we might do 44:34.770 --> 44:36.700 if this one continues to be as successful 44:36.700 --> 44:37.650 as I hope it to be. 44:38.680 --> 44:40.680 Thank you very much and special credit 44:40.680 --> 44:42.199 to Josh and his whole staff. 44:42.199 --> 44:44.949 (all applauding) 44:47.488 --> 44:48.670 - Thank you very much. 44:48.670 --> 44:49.910 Thank you. 44:49.910 --> 44:51.670 Two quick admin details. 44:51.670 --> 44:54.613 First, is there any members of the media present? 44:56.530 --> 44:59.540 Great, if you would please meet us at that door? 44:59.540 --> 45:00.930 We'll do the media availability. 45:00.930 --> 45:02.060 You can make your way over there. 45:02.060 --> 45:04.150 For everyone else, thank you very much for coming, 45:04.150 --> 45:06.020 braving the weather and the security lines. 45:06.020 --> 45:08.200 Thank you, hope you'll join us in June. 45:08.200 --> 45:09.740 If you would please remain in your seats 45:09.740 --> 45:11.930 for about 45 more seconds while the board leaves, 45:11.930 --> 45:12.763 we'll be very grateful. 45:12.763 --> 45:16.563 Thank you very much. (audience applauding)