WEBVTT 00:01.640 --> 00:03.610 you for a good portion of your 00:03.610 --> 00:07.600 workforce initially , Yeah , 00:07.790 --> 00:10.750 that's a great question for a large 00:11.610 --> 00:13.890 portion of our prospective employees . 00:13.900 --> 00:16.340 That transition was relatively seamless . 00:17.090 --> 00:19.890 Although many of our employees had some 00:19.890 --> 00:21.900 unique situations , such as dealing 00:21.900 --> 00:24.770 with various child care or school 00:24.770 --> 00:28.470 closures , college shutdown and things 00:28.480 --> 00:30.760 like that . The majority of our 00:30.800 --> 00:32.800 programs and contracts were able to 00:32.800 --> 00:34.467 transition . To tell it works 00:34.467 --> 00:36.970 relatively smoothly . That was not 00:36.980 --> 00:39.620 really the case with a number of our 00:39.620 --> 00:41.980 defense and Intel programs where our 00:41.980 --> 00:45.280 customers could not shift that work 00:45.470 --> 00:48.880 outside or as into tele work situation . 00:48.890 --> 00:52.200 So for us , that meant making sure that 00:52.200 --> 00:54.200 our employees were able to do shift 00:54.200 --> 00:56.750 work , were able to do this weekend 00:56.750 --> 00:58.806 work , and we're able to support the 00:58.806 --> 01:01.250 mission in whatever way I could . 01:04.140 --> 01:07.370 I think if you ask me today , I would 01:07.380 --> 01:10.400 say that Kobe really became a forcing 01:10.410 --> 01:13.750 function on how to change the way we 01:13.750 --> 01:16.350 execute mission and executed in a 01:16.360 --> 01:20.270 different way . For a lot of our 01:20.720 --> 01:24.390 customers , the big decision was what 01:24.390 --> 01:26.820 level of risk to take on and what could 01:26.830 --> 01:30.710 be done in an unclassified fashion on a 01:30.710 --> 01:32.654 number of our major contracts . We 01:32.654 --> 01:35.190 actually build , tell the work plans 01:35.190 --> 01:37.301 and submitted them to our customers , 01:37.301 --> 01:40.250 and they use quite a bit of that in 01:40.260 --> 01:43.910 there . Tell a work and outward 01:43.920 --> 01:47.870 facing movements . So ah , lot of that 01:48.290 --> 01:51.210 came in part on making sure that we 01:51.210 --> 01:53.360 were focusing and prioritizing on the 01:53.370 --> 01:55.820 big ticket items that became a priority , 01:56.220 --> 01:58.360 making sure that cyber encounter 01:58.360 --> 02:01.650 intelligence component was out in front , 02:01.840 --> 02:03.970 determining what could be done in an 02:03.970 --> 02:07.220 unclassified level . So there was a lot 02:07.220 --> 02:09.570 of back and forth with our customers to 02:09.570 --> 02:11.848 make sure we were able to support them . 02:13.240 --> 02:15.210 So here we are , you know , coming 02:15.210 --> 02:17.410 towards the end of July , a lot of a 02:18.090 --> 02:20.090 didn't initially incision that this 02:20.090 --> 02:22.257 would be going on this long or that we 02:22.257 --> 02:24.312 would be projecting out as far as we 02:24.312 --> 02:26.680 are . But in in present day terms , how 02:26.680 --> 02:30.020 is perspective workforce 02:31.030 --> 02:33.850 for a physical workspace versus working 02:33.850 --> 02:35.739 from home ? How have you all been 02:35.739 --> 02:37.050 ableto by that up ? 02:40.020 --> 02:41.870 So from that perspective , the 02:41.880 --> 02:44.850 situation continues to evolve pretty 02:44.850 --> 02:48.240 much on a daily basis . Perspective has 02:48.560 --> 02:51.240 employees in the majority of our 02:51.240 --> 02:54.420 employees in around 23 states , so 02:54.420 --> 02:56.490 we're pretty diverse from that 02:56.500 --> 02:59.360 perspective . One of the avenues that 02:59.360 --> 03:01.527 is working well is our site ambassador 03:01.527 --> 03:04.830 program . Each large large site has a 03:04.830 --> 03:07.100 leader that's responsible for not only 03:07.100 --> 03:09.400 staying abreast of the different state , 03:09.410 --> 03:12.310 local and municipal requirements , but 03:12.310 --> 03:14.477 also making sure that that information 03:14.477 --> 03:17.610 flows upward to the Cova task team and 03:17.620 --> 03:19.790 downwards all of the employees within 03:19.790 --> 03:22.690 their sights . So that allows us to 03:22.690 --> 03:24.990 develop comprehensive plans for each 03:24.990 --> 03:27.110 work location , regardless of what 03:27.120 --> 03:30.040 fazer and and really to make sure that 03:30.050 --> 03:32.820 as a company , we understand what each 03:32.830 --> 03:36.260 state or each county is doing on make 03:36.260 --> 03:38.260 sure that our employees are aware . 03:40.040 --> 03:41.984 Well , it sounds like you all have 03:42.020 --> 03:44.110 really had your workforce as well as 03:44.110 --> 03:46.221 your government customers . It's your 03:46.221 --> 03:48.240 top priority . There any closing 03:48.240 --> 03:50.351 thoughts you'd like to share with our 03:50.351 --> 03:52.573 virtual attendees before we turn things 03:52.573 --> 03:56.150 over to Aaron and the panel ? You know , 03:56.150 --> 04:00.020 if you had asked me , um , in February 04:00.020 --> 04:02.830 and March when this all started that we 04:02.840 --> 04:05.460 would be , but this in July , I 04:05.470 --> 04:07.414 wouldn't have believed you , but I 04:07.414 --> 04:09.303 think one of the things that this 04:09.303 --> 04:13.020 teaches us is that we really need to be 04:13.020 --> 04:15.580 prepared and have continuity plans , 04:15.970 --> 04:19.610 both internally as industry and from a 04:19.610 --> 04:22.490 government perspective because as we've 04:22.490 --> 04:24.434 all found out these things , we're 04:24.434 --> 04:26.840 bound to happen . And they include such 04:26.840 --> 04:30.190 things as from the intelligence 04:30.190 --> 04:32.480 community perspective , really figuring 04:32.480 --> 04:35.910 out how much risk we can take in 04:35.910 --> 04:39.050 moving pieces of the mission into an 04:39.050 --> 04:42.770 unclassified fashion . I think many of 04:42.770 --> 04:44.826 our customers are now doing a really 04:44.826 --> 04:47.048 good job of determining that and really 04:47.048 --> 04:49.390 working through the security aspects of 04:49.390 --> 04:52.300 it . Weah's industry need to be there 04:52.300 --> 04:54.800 not only to support , but to be able to 04:54.850 --> 04:57.750 manage that work through any one of 04:57.760 --> 04:59.704 these pandemics or conflict . So I 04:59.704 --> 05:01.760 think that really the bottom line is 05:01.760 --> 05:03.927 for all of us . We've now learned that 05:04.390 --> 05:06.223 work is really a product , not a 05:06.223 --> 05:09.190 location . Uh , we've seen a lot of 05:09.200 --> 05:12.600 productivity from Martello Workforce 05:12.820 --> 05:15.042 specifically around the support side of 05:15.042 --> 05:17.120 the house . So facilities age , our 05:17.120 --> 05:20.030 security and other areas really haven't 05:20.030 --> 05:22.380 missed a beat . And I think for the 05:22.380 --> 05:25.200 next generation of workforce , both for 05:25.210 --> 05:27.488 industry in the intelligence community , 05:28.030 --> 05:31.060 that flexibility and the fact that of 05:31.360 --> 05:33.527 folks that are able to work in various 05:33.527 --> 05:36.850 aspects should be top of mind . Well , 05:36.850 --> 05:39.780 what well said And thanks again for 05:39.790 --> 05:41.901 taking time out of your afternoon for 05:41.901 --> 05:43.740 this conversation . It's now my 05:43.740 --> 05:47.150 pleasure to turn things over to Aaron 05:47.160 --> 05:49.800 and our esteemed Panelists . Erin , 05:50.440 --> 05:53.010 thank you . Then let's meet our 05:53.010 --> 05:55.370 speakers for today . We have Jeff 05:55.380 --> 05:57.491 Fowler , chief information officer of 05:57.491 --> 05:59.713 the Bureau of Intelligence and Research 05:59.713 --> 06:01.824 of the department State Mania Jones , 06:01.824 --> 06:04.047 acting chief information officer of the 06:04.047 --> 06:05.936 intelligence community within the 06:05.936 --> 06:07.880 office of the Director of National 06:07.880 --> 06:09.880 Intelligence , Peter Ranks , deputy 06:09.880 --> 06:11.547 chief information officer for 06:11.547 --> 06:11.180 information enterprise at the 06:11.180 --> 06:13.069 Department of Defense , and carry 06:13.069 --> 06:15.180 Buckley , vice president of Air Force 06:15.180 --> 06:18.390 programs with Miter , as we get started 06:18.390 --> 06:20.557 here like you needed just very briefly 06:21.250 --> 06:23.417 introduce yourselves . Let us know who 06:23.417 --> 06:25.583 you are with those those titles that I 06:25.583 --> 06:27.583 just read off . What do they really 06:27.583 --> 06:29.806 mean ? And how does your work relate to 06:29.806 --> 06:32.730 managing the workforce remotely in 06:32.730 --> 06:35.300 during this pandemic ? Just let's start 06:35.300 --> 06:38.990 with you . Sure , thanks , Erin , and 06:39.080 --> 06:41.080 expose on behalf of the Panelists , 06:41.080 --> 06:43.302 they should say thank you also to inset 06:43.302 --> 06:46.230 Suzanne and prospective Orlando who are 06:46.230 --> 06:47.952 hosting us . That an important 06:47.952 --> 06:49.952 conversation to be having . Now , I 06:49.952 --> 06:52.119 think , um , you know , we might think 06:52.119 --> 06:55.560 that Kobe , 19 is what has having us do 06:55.560 --> 06:57.671 the tele work right now and then when 06:57.671 --> 06:59.782 it goes away , this goes away . But I 06:59.782 --> 07:02.004 don't think so . I think we're going to 07:02.004 --> 07:04.171 be living in this world for quite some 07:04.171 --> 07:06.338 time to come . But my background I'm a 07:06.338 --> 07:08.770 32 year that turned up the ICSC , sir . 07:09.130 --> 07:11.352 I'm on detail over to the Department of 07:11.352 --> 07:13.352 State , where I'm serving his chief 07:13.352 --> 07:15.519 information officer like my colleagues 07:15.519 --> 07:17.408 with the same title it means were 07:17.408 --> 07:17.380 responsible for the technology 07:17.380 --> 07:19.750 enablement of mission . In my 07:19.750 --> 07:21.950 particular case , I didn't grow up in 07:21.950 --> 07:24.172 the technology world has spent the last 07:24.172 --> 07:26.172 half of my career there . The first 07:26.172 --> 07:27.839 half was as an analyst . Uh , 07:27.839 --> 07:29.728 unfortunately , that means that I 07:29.760 --> 07:31.593 understand the business that I'm 07:31.593 --> 07:34.500 enabling with technology . So that's 07:34.510 --> 07:37.880 primary focus for me . You asked about 07:37.880 --> 07:40.047 sort of our jobs , the other jobs that 07:40.047 --> 07:42.340 I would say that I'm a parent and I 07:42.350 --> 07:45.590 think I've got school age Children like 07:45.590 --> 07:48.440 many of our workforce and colleagues . 07:48.980 --> 07:51.147 And when you start thinking about that 07:51.147 --> 07:53.258 and understanding of the complexities 07:53.258 --> 07:55.480 of enabling work , uh , in that type of 07:55.480 --> 07:57.940 environment , I think the truth is , is 07:57.940 --> 08:00.051 that what we think about our business 08:00.051 --> 08:02.107 and what we're doing here ? It's not 08:02.107 --> 08:04.218 just about technology and even look , 08:04.218 --> 08:06.440 it's also about enabling human beings . 08:06.440 --> 08:08.607 My motto , really , for all of this is 08:08.607 --> 08:10.496 remember your humanity drama . Go 08:10.496 --> 08:12.718 distract . That's the thing that drives 08:12.718 --> 08:15.460 me fantastic . Big more go into all 08:15.460 --> 08:17.750 that could get on a high level topics I 08:17.750 --> 08:19.972 know we're gonna be talking about Thank 08:19.972 --> 08:22.920 you mania . But I hear from you good 08:22.920 --> 08:25.700 afternoon in echoing Jeff messages 08:25.710 --> 08:27.932 sending the same regard . Thank you for 08:27.932 --> 08:29.988 having us my name . Linda Jones . So 08:29.988 --> 08:31.543 asked the acting CEO of the 08:31.543 --> 08:33.930 intelligence community . What we 08:33.930 --> 08:35.986 provide in that role is we work with 08:35.986 --> 08:38.680 all of the 17 . I see agency , 08:38.680 --> 08:41.300 specifically the CEOs , and we worked 08:41.310 --> 08:43.700 to further , uh , technical or 08:43.700 --> 08:46.240 technology related issues and concerns . 08:46.320 --> 08:48.910 We work on interoperability . We work 08:48.920 --> 08:51.560 across the community to ensure that 08:51.740 --> 08:54.160 mission needs are being met on shared 08:54.160 --> 08:56.250 resource is it could be talked with 08:56.270 --> 08:59.280 such a cybersecurity or cloud or 08:59.280 --> 09:01.400 working with up industry partners as 09:01.400 --> 09:03.650 well as our colleagues regarding data . 09:03.940 --> 09:07.560 Uh , I myself a swell as others are as 09:07.560 --> 09:09.671 well . Been at the office director of 09:09.671 --> 09:11.782 national intelligence for a few years 09:11.782 --> 09:15.320 now as a d telly . And so in that 09:15.320 --> 09:18.830 role , it's been great to work with 09:18.840 --> 09:21.740 defense , uh , work with colleagues 09:21.740 --> 09:24.160 across the icy , all 17 of elements , 09:24.380 --> 09:26.269 as well as work with our industry 09:26.269 --> 09:28.320 partners in order to further the 09:28.320 --> 09:31.450 mission . Fantastic . 09:32.440 --> 09:34.607 Peter , who are you ? What do you do ? 09:35.790 --> 09:37.790 I think they're unloaded One , uh , 09:37.830 --> 09:41.090 direct . Uh uh , deputy chief 09:41.090 --> 09:43.350 information officer of duty . There's a 09:43.350 --> 09:45.730 number of us than my portfolio really 09:45.730 --> 09:48.170 involves software modernization , the 09:48.170 --> 09:50.226 way we build deploy software for the 09:50.226 --> 09:52.448 duty on all the supporting technologies 09:52.448 --> 09:54.114 from cloud infrastructure and 09:54.114 --> 09:56.400 everything else . I think it was my pre 09:56.400 --> 09:58.622 existing relationships with some of the 09:58.622 --> 10:01.490 cloud vendors as well as the role and 10:01.490 --> 10:03.712 delivering collaboration capabilities . 10:03.712 --> 10:05.823 That kind of trust me into the how do 10:05.823 --> 10:07.770 we respond ? Teoh Tele Work 10:07.770 --> 10:09.780 conversation . When this spun up , 10:11.370 --> 10:14.370 I'm actually a CIA employee on detail 10:14.370 --> 10:16.537 over to the FBI . Have been here about 10:16.537 --> 10:18.703 15 months . I spent the majority of my 10:18.703 --> 10:22.660 career in I T and technical 10:22.660 --> 10:25.090 support to intelligence on a little bit 10:25.090 --> 10:27.201 time in the counter proliferation and 10:27.201 --> 10:29.312 collection communities as well . Uh , 10:29.312 --> 10:31.312 so happy to be here looking for the 10:31.312 --> 10:33.368 conversation . And , you know , it's 10:33.368 --> 10:35.590 funny . I didn't even realize that when 10:35.590 --> 10:37.701 we were first setting up this panel . 10:37.701 --> 10:39.979 We've got civilian defense , and I see . 10:39.979 --> 10:42.090 But really , you're all just I see in 10:42.090 --> 10:41.350 disguise here 10:46.440 --> 10:48.970 and just want out our intros . Uh , 10:48.980 --> 10:51.330 Carrie , let's hear from you . Thanks . 10:51.340 --> 10:53.507 I guess you could say I might be I see 10:53.507 --> 10:57.350 in my career . But currently I 10:57.350 --> 10:59.230 am a vice president at the vital 10:59.230 --> 11:01.980 corporation running our support to the 11:01.990 --> 11:04.650 Air Force . Some folks may not be 11:04.660 --> 11:06.716 familiar with Miter . We are not for 11:06.716 --> 11:09.120 profit . We operate seven EPA party 11:09.160 --> 11:12.480 sees for the government . Uh , my , my 11:12.480 --> 11:14.480 job falls within one of our largest 11:14.480 --> 11:16.720 epic party . Sees our national security 11:16.720 --> 11:20.710 engineering center . We have 8500 11:20.710 --> 11:22.821 employees , maybe a little bit more , 11:23.040 --> 11:26.650 and the work that we dio out of the the 11:26.650 --> 11:29.230 end of our D . C . It is very much in 11:29.240 --> 11:31.462 support of the D . O d . And I see . So 11:31.462 --> 11:33.840 what that means is that during these 11:33.850 --> 11:36.650 times my responsibility has been making 11:36.650 --> 11:38.850 sure that we can maintain our mission 11:38.850 --> 11:41.580 impact . For for those sponsors , that 11:41.580 --> 11:43.691 means making sure that our folks have 11:43.691 --> 11:45.191 access to the data and the 11:45.191 --> 11:47.413 collaboration tools that they need like 11:47.413 --> 11:50.270 perspective , with also kept open 11:50.280 --> 11:53.010 throughout the pandemic . So we've been 11:53.010 --> 11:55.780 really focused on the well being and 11:55.790 --> 11:57.846 safety of our folks that you have to 11:57.846 --> 11:59.950 come in to do that work . But , like 11:59.950 --> 12:02.650 perspective also found incredible 12:02.650 --> 12:05.590 innovation and willingness and new ways 12:05.670 --> 12:07.840 to tackle some of the traditionally 12:07.840 --> 12:11.750 classified problems in , um , class 12:11.760 --> 12:13.840 settings . Looking at looking at 12:13.850 --> 12:15.830 different mechanisms on data and 12:15.840 --> 12:19.770 sources to do that . And I'll 12:19.780 --> 12:22.800 just say it was also from similar to 12:22.800 --> 12:24.900 Jeff would really taken up . People 12:24.900 --> 12:26.956 first approached through all of this 12:26.956 --> 12:29.210 understanding of the work life and 12:29.210 --> 12:31.043 family challenges that folks are 12:31.043 --> 12:34.670 dressing . Thank you . Fantastic . Okay , 12:34.670 --> 12:36.892 I'm gonna start with you . But before I 12:36.892 --> 12:39.114 do a reminder to the audience listening 12:39.114 --> 12:41.337 out there , if you have questions along 12:41.337 --> 12:43.392 the way , please drop those in the Q 12:43.392 --> 12:45.980 and A the attendee questions box as you 12:45.980 --> 12:48.710 have them . If we get toward about 1 50 12:48.810 --> 12:51.032 I'm not seeing questions populate , I'm 12:51.032 --> 12:52.977 just gonna keep talking and nobody 12:52.977 --> 12:55.199 wants that . So if you have questions , 12:55.199 --> 12:57.421 get him in to make sure that we can get 12:57.421 --> 12:59.532 there at the yet . Okay . I wanted to 12:59.532 --> 13:01.421 start with you and hear about two 13:01.421 --> 13:03.254 things from you . Uh , first you 13:03.254 --> 13:05.310 started talking in your introduction 13:05.310 --> 13:07.310 about how miter has adjusted to the 13:07.310 --> 13:09.590 current situation . The interesting . A 13:09.590 --> 13:12.100 little bit more about that . And what 13:12.100 --> 13:15.510 kind of innovations are unexpected 13:15.510 --> 13:17.621 changes you all went through in order 13:17.621 --> 13:20.160 to adapt to this crisis . And then I'd 13:20.160 --> 13:22.470 love for you to provide us the 10,000 13:22.470 --> 13:24.690 foot view . You have some some 13:24.900 --> 13:26.970 visibility across the U . S . 13:26.980 --> 13:29.170 Government as an FFR D . C . So the 13:29.170 --> 13:31.226 interested to hear some of the thing 13:31.226 --> 13:33.337 interesting things you've seen across 13:33.337 --> 13:35.226 government , and then we'll go to 13:35.226 --> 13:37.226 everyone else and dive into some of 13:37.226 --> 13:39.226 those unique use cases . So again , 13:39.226 --> 13:41.337 first Carrie , how it might have been 13:41.337 --> 13:43.337 handling all this . Uh oh , great . 13:43.337 --> 13:45.670 Thanks . Very questionnaire . One thing , 13:45.670 --> 13:47.837 as you mentioned , that the miter does 13:47.837 --> 13:49.820 have the advantage point and we do 13:49.820 --> 13:52.098 operate across the whole of government . 13:52.098 --> 13:54.110 We also bridge between the private 13:54.120 --> 13:56.064 sector and government . One of the 13:56.064 --> 13:58.300 first things that might er did is we 13:58.380 --> 14:00.660 stood up a cove in 19 health care 14:00.660 --> 14:03.870 coalition , and we have to about 900 14:03.870 --> 14:06.470 partners right now where we have an 14:06.470 --> 14:09.460 online presence where we are helping 14:09.760 --> 14:12.690 state , local , federal and industry 14:12.690 --> 14:14.801 understand how they can best response 14:14.970 --> 14:17.500 to take over it and some of the various 14:17.510 --> 14:19.940 aspects of that to include things like 14:20.150 --> 14:22.140 the political care outcomes we're 14:22.140 --> 14:24.362 tracking that her helping tracking that 14:24.362 --> 14:26.418 with with the nation and partnership 14:26.418 --> 14:27.973 with D . C and universities 14:28.010 --> 14:30.232 understanding , you know , the critical 14:30.232 --> 14:32.288 supply chain and where folks can get 14:32.288 --> 14:34.510 those supplies and also public guidance 14:34.510 --> 14:37.130 and policy . So that might have really 14:37.140 --> 14:41.110 stuffed into our mission of solving 14:41.110 --> 14:44.040 problems for a safer world by providing 14:44.040 --> 14:46.400 a resource to all of the decision 14:46.400 --> 14:49.740 makers across the country . Internally , 14:49.750 --> 14:52.700 we set up a similar dashboard . We have 14:52.710 --> 14:54.654 a dashboard that tracks trends and 14:54.654 --> 14:56.543 localities of our campuses in our 14:56.543 --> 14:58.330 sights , as well as being very 14:58.330 --> 15:00.560 transparent about the health and safety 15:00.560 --> 15:03.210 of our of our own folks . We actually 15:03.210 --> 15:05.432 post the number of folks that have been 15:05.432 --> 15:08.260 tested and tested positive so that we 15:08.260 --> 15:09.990 can use that data to be very 15:09.990 --> 15:13.380 informative in terms of . But what 15:14.430 --> 15:16.597 facilities might need to be closed for 15:16.597 --> 15:18.541 cleaning and who may or may not be 15:18.541 --> 15:21.350 available , though not naming people by 15:21.460 --> 15:25.300 person way to run afoul of happen . 15:25.300 --> 15:28.290 And you know that that's right , That's 15:28.290 --> 15:31.160 right way also purchase down of 15:31.160 --> 15:33.590 employees . So we are now focused on a 15:33.590 --> 15:36.250 mobile first platform and the way that 15:36.250 --> 15:39.280 we do all of our work . Um , we are 15:39.280 --> 15:41.169 looking at all kinds of different 15:41.170 --> 15:44.020 collaboration tools was also changed . 15:44.030 --> 15:46.300 Some of our policies and procedures 15:46.460 --> 15:49.210 relaxing some of the medical leave and 15:49.220 --> 15:51.220 the time that we have with expanded 15:51.220 --> 15:53.870 other types of time charging of folks 15:53.880 --> 15:56.260 can make up time that they don't 15:56.270 --> 15:58.990 typically charge because of other 15:58.990 --> 16:01.046 obligations are taking care of loved 16:01.046 --> 16:03.330 ones . So that was extended that and 16:03.330 --> 16:05.330 then we're also looking at new ways 16:05.330 --> 16:07.274 that that we're gonna be using our 16:07.274 --> 16:09.760 facilities as I mentioned with and 16:09.880 --> 16:12.102 putting shift work in . We're providing 16:12.280 --> 16:14.740 free food for everyone who who does 16:14.750 --> 16:17.440 have to come in into the office . What 16:17.440 --> 16:19.600 we're seeing across the d . O . D in 16:19.600 --> 16:23.550 the I C is just Our sponsors 16:23.560 --> 16:27.350 are embracing our innovative ideas 16:27.470 --> 16:30.540 and really working closely with us 16:31.240 --> 16:34.600 to accommodate and leverage some of the 16:34.600 --> 16:36.830 innovation that's coming as a result of 16:36.840 --> 16:38.970 this . Something that we talked about 16:38.980 --> 16:41.130 earlier was our ability to leverage 16:41.140 --> 16:42.918 people around the world . Now , 16:42.918 --> 16:45.690 wherever they may be to bring new ideas 16:45.700 --> 16:48.350 to the table because we don't have to 16:48.360 --> 16:50.471 be , I'll be sitting in the same room 16:50.471 --> 16:52.749 of the white border come up with ideas . 16:52.749 --> 16:54.693 So So we really are looking at the 16:54.693 --> 16:56.804 Spansion of bringing able to bring in 16:56.804 --> 16:58.582 new talent and partners through 16:58.582 --> 17:00.804 throughout this this time . And I think 17:00.804 --> 17:02.860 we're learning Ah , lot there on the 17:02.860 --> 17:04.971 last day , I'll say , You know , last 17:04.971 --> 17:07.027 year I know . And you know , D and I 17:07.740 --> 17:09.629 they stood up that the initiative 17:09.629 --> 17:11.573 around right , trusted in an agile 17:11.573 --> 17:13.810 workforce . So this was really looking 17:13.810 --> 17:17.400 at making sure that we can build on 17:17.400 --> 17:20.100 accommodate a workforce for the future . 17:20.110 --> 17:22.430 And I do think that the pandemic 17:22.440 --> 17:25.470 response that we're all responding to 17:25.470 --> 17:27.920 is really truly capitalizing 17:27.920 --> 17:30.490 opportunity to make make us think 17:30.490 --> 17:33.160 differently and how we really might be 17:33.160 --> 17:35.660 much more agile in the future . 17:36.520 --> 17:38.880 Excellent . Uh , Carrie keep you right 17:38.880 --> 17:40.950 up there perfectly . You wanna talk 17:40.950 --> 17:44.170 about Ah , some of those initiative 17:44.170 --> 17:46.281 that the icy had already incorporated 17:46.281 --> 17:49.380 and how they were well timed to meet 17:49.380 --> 17:52.530 this crisis absolutely ensure . And so , 17:52.810 --> 17:55.110 yes , Kerry mentioned about art or the 17:55.110 --> 17:57.277 right trust agile workforce . That was 17:57.277 --> 17:59.388 definitely one of the initiative that 17:59.388 --> 18:01.443 we had already prior to the pandemic 18:01.443 --> 18:05.040 began to look at improving how 18:05.050 --> 18:07.800 Ah , individuals are brought into the 18:07.800 --> 18:10.022 intelligence community from a clearance 18:10.022 --> 18:13.110 process from a skills process from just 18:13.110 --> 18:15.490 a timeliness of transferring , whether 18:15.490 --> 18:17.780 it be public and private , and how we 18:17.780 --> 18:19.502 work across the community with 18:19.502 --> 18:21.750 individuals may be going from one 18:21.750 --> 18:24.040 location , one office organization to 18:24.040 --> 18:27.320 another . And so , as Kerry mentioned 18:28.010 --> 18:30.580 with that , this gave us a great 18:30.590 --> 18:33.570 opportunity to innovate some of the 18:33.580 --> 18:35.747 early seedlings that were put in place 18:35.900 --> 18:38.067 to look at how to improve items we had 18:38.067 --> 18:41.340 always had . Ah , the option or the 18:41.340 --> 18:43.850 availability of teleworking for certain 18:43.850 --> 18:46.017 elements . It just wasn't maybe to the 18:46.017 --> 18:48.050 same size , scale or scope . Ah , 18:48.050 --> 18:50.161 perhaps it was for an accommodation , 18:50.161 --> 18:52.106 and perhaps it was for extenuating 18:52.106 --> 18:54.670 circumstances . But when the pandemic 18:54.670 --> 18:58.050 came about , one of the ICI's main , 18:58.060 --> 19:01.050 uh , strength is being agile and being 19:01.060 --> 19:03.580 able to flexibly meet the needs of the 19:03.580 --> 19:05.636 mission . And so this just gave us a 19:05.636 --> 19:07.747 chance to look at those ideas , those 19:07.747 --> 19:10.950 initiatives and to expand them for the 19:10.960 --> 19:14.910 situation over . So I think 19:14.910 --> 19:17.132 that dig in more , we stay with you for 19:17.132 --> 19:21.040 a second to talk about how fast you're 19:21.040 --> 19:24.020 able to pivot to getting allowing 19:24.020 --> 19:26.370 classified work to continue at the 19:26.370 --> 19:28.537 beginning of this pandemic , there was 19:28.537 --> 19:31.140 a slow move , telework , And then there 19:31.140 --> 19:34.190 was a rush to it . How would they be 19:34.190 --> 19:36.301 able to adjust to that ? And how long 19:36.301 --> 19:38.680 did it take you ? You all to figure out 19:38.690 --> 19:40.690 work flows and processes that would 19:40.690 --> 19:42.801 allow classified work to continue And 19:42.801 --> 19:45.023 And how have you been able to make that 19:45.023 --> 19:48.240 continue ? So yeah , so I guess you 19:48.240 --> 19:50.407 could say , as with everything else in 19:50.407 --> 19:52.573 the beginning , there's always kind of 19:52.573 --> 19:54.518 that learning curve . So sometimes 19:54.518 --> 19:56.684 people say you're kind of building the 19:56.684 --> 19:58.629 airplane as you're flying it , but 19:58.629 --> 20:00.740 because we did have some policies and 20:00.740 --> 20:02.962 procedures and work flows in place , it 20:02.962 --> 20:04.962 was Maura about . Okay , how can we 20:04.962 --> 20:07.073 make the most sense of this ? And how 20:07.073 --> 20:09.184 can we maybe lift or shift or partner 20:09.184 --> 20:11.351 with others to capitalize and and make 20:11.351 --> 20:13.462 the best use of this opportunity ? So 20:13.960 --> 20:16.127 in the beginning , you know , it was a 20:16.127 --> 20:18.404 lot of we had to see what was going on . 20:18.404 --> 20:20.293 I think that was not just for the 20:20.293 --> 20:22.404 intelligence community , but for many 20:22.404 --> 20:24.516 sectors of really assessing and doing 20:24.516 --> 20:27.380 that initial triage and then using that 20:27.390 --> 20:30.460 piece to kind of , uh , innovate and 20:30.460 --> 20:32.750 make our way through it . But when it 20:32.750 --> 20:34.917 came to the policies that procedures , 20:34.917 --> 20:36.972 this was a time also , that we could 20:36.972 --> 20:39.139 update things because we actually have 20:39.139 --> 20:41.306 that . The ongoing pandemic , in order 20:41.306 --> 20:43.028 to improve the process , is so 20:43.028 --> 20:45.700 something that may ah had been written 20:45.710 --> 20:48.360 before , tried out before now , we 20:48.360 --> 20:51.240 actually had actual situation , and we 20:51.240 --> 20:53.462 could We knew what worked , what didn't 20:53.462 --> 20:55.840 work . And we could further that those 20:55.840 --> 20:59.540 efforts Nice Peter 20:59.670 --> 21:01.840 for the d . O d . How does all that 21:01.840 --> 21:04.240 track for your experience ? Was it 21:04.240 --> 21:05.980 similar being ableto make that 21:05.980 --> 21:08.091 transition ? How long did it take you 21:08.091 --> 21:10.320 to get the necessary infrastructure 21:10.320 --> 21:13.170 policies culture in place over the 21:13.170 --> 21:16.510 language ? Yeah . No , of course , it's 21:16.510 --> 21:18.621 not a light switch , and I think some 21:18.621 --> 21:20.566 of some of our experience probably 21:20.566 --> 21:22.788 tracks with many others . We were lucky 21:22.788 --> 21:25.070 that seed had been planted for a lot of 21:25.070 --> 21:27.580 these solutions long before . They just 21:27.590 --> 21:30.390 weren't growing with with the all the 21:30.390 --> 21:33.010 urgency could give we had and existing 21:33.010 --> 21:35.232 remote work program . We had two people 21:35.232 --> 21:37.454 who are telling working every day , but 21:37.454 --> 21:39.621 it was it was never more than about 90 21:39.621 --> 21:41.788 to 100,000 users on a day , which is a 21:41.788 --> 21:44.010 lot in real terms , but as a percent of 21:44.010 --> 21:46.121 the duty workforce is only about 5% . 21:46.121 --> 21:48.232 So there's a big gap between about 5% 21:48.232 --> 21:50.343 telework and , you know , approaching 21:50.343 --> 21:52.690 70 or 80% of work . But we have 21:52.690 --> 21:54.468 programs in place . We had some 21:54.468 --> 21:58.220 programs for , uh , remote classified 21:58.220 --> 22:00.220 work . Most of them have been very 22:00.220 --> 22:04.060 targeted at specific niche problems on 22:04.060 --> 22:06.990 we had to work to scale them . I think 22:07.000 --> 22:10.510 we were able to respond very quickly 22:11.240 --> 22:14.610 in the own class space by moving users 22:14.610 --> 22:18.520 into an online collaboration tool . We 22:18.520 --> 22:22.220 now have about 960,000 users 22:23.340 --> 22:25.673 using an online environment we call CVR , 22:25.673 --> 22:27.340 which is just a collaborative 22:27.340 --> 22:29.396 environment that happened remarkably 22:29.396 --> 22:31.562 quickly . And I think we leveraged the 22:31.562 --> 22:34.700 urgency of the moment to to wait 22:34.700 --> 22:36.867 policies where he had to to accelerate 22:36.867 --> 22:39.340 processes , to take advantage of some 22:39.340 --> 22:41.610 existing contracts to do it . Uh , on 22:41.610 --> 22:43.721 the classified side , it was harder . 22:43.721 --> 22:45.888 Luckily again , we already had the flu 22:45.888 --> 22:47.999 press drawn up , but just scaling the 22:47.999 --> 22:50.054 production that was our high touch , 22:50.054 --> 22:52.850 producing the devices for classified 22:53.120 --> 22:54.898 remote work , all the commotion 22:54.898 --> 22:57.470 solutions for classified for what that 22:57.470 --> 23:00.190 is high touch in person labor on , but 23:00.190 --> 23:02.420 it was difficult to scale that in a 23:02.430 --> 23:04.597 safe way in order to meet the demand . 23:04.597 --> 23:06.763 We did eventually hit our stride . But 23:06.763 --> 23:08.819 whereas we moved in the unclassified 23:08.819 --> 23:11.340 space very broadly over the span of 60 23:11.340 --> 23:13.507 days , I think it's only recently that 23:13.507 --> 23:15.618 we feel like we have hit a lot of the 23:15.618 --> 23:17.950 demand for remote work at the secret 23:17.950 --> 23:21.750 level . So you mentioned that it took 23:21.750 --> 23:23.750 some time to spin up . How were you 23:23.750 --> 23:25.917 able to get there was just , ah , uh , 23:26.110 --> 23:27.943 lots of contracts with different 23:27.943 --> 23:30.830 suppliers toe production ? Or were you 23:30.830 --> 23:32.941 able to just be taxi routes out there 23:32.941 --> 23:35.163 and help boost production in some way ? 23:35.310 --> 23:37.477 Yeah , the first thing we had to do is 23:37.477 --> 23:39.643 find out where all those programs were 23:39.643 --> 23:41.532 buried within a part . So another 23:41.532 --> 23:43.810 department something place there's not . 23:43.810 --> 23:46.032 There is not a commercial solutions for 23:46.032 --> 23:48.340 classified or a secret work from home 23:48.340 --> 23:50.562 program . You know , there were a dozen 23:50.562 --> 23:53.570 or so we actually worked with esa us to 23:53.570 --> 23:55.626 approve all those things to First of 23:55.626 --> 23:57.848 all , just get our arms around those in 23:57.848 --> 24:01.720 a daily uh ah kind of I t before 24:01.720 --> 24:05.160 Ah , Kobe Telework task force that the 24:05.170 --> 24:08.010 beauty CEO chairs on get shared 24:08.010 --> 24:10.343 awareness of what all those things were . 24:10.343 --> 24:12.710 And once we knew where all of them were , 24:12.720 --> 24:15.040 what their state of maturity waas We 24:15.040 --> 24:16.984 could ensure that they had all the 24:16.984 --> 24:19.040 approvals they needed . And then the 24:19.040 --> 24:21.290 ability to ramp production , um , ended 24:21.290 --> 24:23.457 up being very local actions . I mean , 24:23.457 --> 24:25.568 I think , you know , in the injustice 24:25.568 --> 24:28.110 case , they had to identify the right 24:28.110 --> 24:30.221 amount of skip location . They had to 24:30.221 --> 24:32.110 replicate some infrastructure for 24:32.110 --> 24:34.277 provisioning on , and then they had to 24:34.277 --> 24:36.443 bring in a lot of people who did a lot 24:36.443 --> 24:38.610 of in the office hands on work to make 24:38.610 --> 24:38.410 that happen . I think in some of the 24:38.410 --> 24:41.470 other services it involved ramping up 24:41.470 --> 24:43.581 agreements with suppliers in order to 24:43.581 --> 24:46.270 do that . It was difficult for a lot of 24:46.270 --> 24:48.870 these solutions , you know , rely on a 24:48.880 --> 24:51.130 two generations old version of a tablet 24:51.130 --> 24:53.186 or something else that we have baked 24:53.186 --> 24:55.480 the conversating , the configuration 24:55.830 --> 24:59.660 around and getting rapid infusions of 24:59.660 --> 25:02.580 supply for those types of devices . It 25:02.580 --> 25:04.747 was difficult , and I think one of the 25:04.747 --> 25:06.969 lessons we draw from this is that those 25:06.969 --> 25:09.100 types of solutions have to be agile , 25:09.100 --> 25:13.030 adaptable to weigh , have toe not 25:13.030 --> 25:15.120 be too tightly tethered to specific 25:15.120 --> 25:17.342 hardware platforms because that was one 25:17.342 --> 25:20.160 of our friction Points for scale . Yeah , 25:20.810 --> 25:23.340 Yeah , makes sense . Jeff wanted to 25:23.340 --> 25:25.451 move over to you and talk a bit about 25:25.451 --> 25:27.673 the State Department , which I think of 25:27.673 --> 25:30.150 as , like , the other icy agency . 25:30.150 --> 25:32.372 Right ? State Department definitely has 25:32.372 --> 25:35.340 a lot of intelligence work that it does 25:35.990 --> 25:38.400 in support of the icy . And you also 25:38.400 --> 25:40.622 have an interesting perspective because 25:40.622 --> 25:42.733 I know State Department's resource is 25:42.733 --> 25:44.678 are very much Federated across the 25:44.678 --> 25:47.700 world . In many areas where 25:48.330 --> 25:50.274 infrastructure is not always their 25:50.274 --> 25:52.970 security isn't always , ah , easy to 25:52.970 --> 25:56.850 attain . So when this pandemic hit 25:56.940 --> 25:59.620 home here at the state how much of 25:59.620 --> 26:01.620 those lessons that you have learned 26:01.620 --> 26:03.787 overseas were you able to ramp up here 26:03.787 --> 26:06.040 at home ? Yes . So I was listening . My 26:06.040 --> 26:08.760 colleague , um you know , I think we 26:08.760 --> 26:10.790 actually took a slightly different 26:10.800 --> 26:14.090 approach than what other folks did 26:14.150 --> 26:16.261 first . Like , I guess I should start 26:16.261 --> 26:18.150 by saying , as a department , the 26:18.150 --> 26:20.317 department was fairly well situated to 26:20.317 --> 26:24.210 do remote operation . Um , most of its 26:24.210 --> 26:26.432 work was done in the unclassified world 26:26.820 --> 26:29.910 in we had fairly robust unclassified 26:29.910 --> 26:32.840 systems connecting , uh , you know , uh , 26:32.850 --> 26:35.580 posts all over the world with the 26:35.590 --> 26:38.960 German building . So there wasn't a 26:38.960 --> 26:41.100 whole lot of change there other than 26:41.110 --> 26:43.170 just moving to a more robust kind of 26:43.180 --> 26:46.510 status . It was different in the bureau , 26:46.520 --> 26:48.298 right ? Because there we've got 26:48.298 --> 26:50.290 intelligence analysts operating at 26:50.300 --> 26:52.356 essentially a top secret level . For 26:52.356 --> 26:55.530 the most part , I trying to enable top 26:55.530 --> 26:58.600 secret outside of sort of protected 26:58.610 --> 27:01.890 enclaves is extremely difficult . 27:02.190 --> 27:05.350 And it's made even more difficult when 27:05.350 --> 27:07.406 you're trying to do that in a rush . 27:07.406 --> 27:09.790 And so , frankly , we did . What we did 27:09.790 --> 27:11.810 is we recognize that the business 27:11.810 --> 27:15.010 environment had changed around us with 27:15.010 --> 27:17.640 coated with sort of distributed 27:17.720 --> 27:21.220 customer sets . Um , Teleworking 27:21.230 --> 27:23.380 Aziz Well , as the producers of 27:23.380 --> 27:25.547 intelligence , double working . And so 27:25.547 --> 27:27.769 we changed our business model largely , 27:28.550 --> 27:31.520 and we focused a lot on what we could 27:31.530 --> 27:34.590 do with unclassified 27:34.870 --> 27:37.820 information . So there was , ah , large 27:37.820 --> 27:40.690 emphasis enabling usable source , 27:41.540 --> 27:43.860 producing new product lines , thinking 27:43.860 --> 27:47.390 about how to , um provide value 27:47.400 --> 27:49.670 to customers , traditional customers of 27:49.670 --> 27:52.500 intelligence . But to do it with 27:52.510 --> 27:54.170 marginally open source past 27:54.170 --> 27:56.337 commentaries , the beginning of this I 27:56.337 --> 27:58.990 also mentioned that we think a lot 27:58.990 --> 28:00.934 about tools and technology and the 28:00.934 --> 28:03.157 implement just because of the nature of 28:03.157 --> 28:05.212 our business . But there really is a 28:05.212 --> 28:07.212 human element component to this . I 28:07.212 --> 28:09.630 think Orlando touched on it at the very 28:09.630 --> 28:12.650 beginning . So , you know , we did a 28:12.650 --> 28:15.090 lot of things like reducing or 28:15.090 --> 28:17.312 eliminating the requirement for quarter 28:17.312 --> 28:19.368 hours . Right ? So you can't come in 28:19.368 --> 28:21.368 during the day because you've got a 28:21.368 --> 28:23.590 spouse who needs to work and you've got 28:23.590 --> 28:26.380 Children at home , but your spouse can 28:26.380 --> 28:28.436 spell you in the evening hours . You 28:28.436 --> 28:30.547 can come in during the evening to get 28:30.547 --> 28:32.713 the classified piece of your work done 28:32.713 --> 28:34.547 while you've done run classified 28:34.547 --> 28:36.580 teleworking , uh , remotely eso 28:36.590 --> 28:39.360 removing core hours , giving people 28:39.360 --> 28:41.890 just maximum flexibility . The other 28:41.890 --> 28:43.890 thing . Oddly enough , you know , I 28:43.890 --> 28:45.946 said , flexibility there because you 28:45.946 --> 28:48.168 need to provide that to folks . What we 28:48.168 --> 28:49.946 discovered is the importance of 28:49.946 --> 28:52.001 providing structure . And again I go 28:52.001 --> 28:54.168 back to my quipped that I'm also a dad 28:54.168 --> 28:56.890 is a second job , and I've come to 28:56.890 --> 28:59.001 understand , with my own Children and 28:59.001 --> 29:01.168 distorted environment how important it 29:01.168 --> 29:03.650 is that provide a structure for them in 29:03.650 --> 29:06.180 a rather instruction period . But the 29:06.190 --> 29:08.610 same is true of business , even though 29:08.610 --> 29:10.970 we need to provide flexibility to the 29:10.970 --> 29:13.130 workforce and enable that their 29:13.130 --> 29:15.670 operations technologically into 29:15.680 --> 29:17.902 business process . We also need to give 29:17.902 --> 29:20.860 them a structure that creates sort of a 29:20.860 --> 29:23.027 new normal for them . So those are the 29:23.027 --> 29:25.420 sorts of things that we focused on sure 29:25.610 --> 29:28.740 distributed some secure coms , 29:28.740 --> 29:31.350 capabilities and what have you . But 29:31.350 --> 29:34.090 the heaviest reliance was on secure but 29:34.090 --> 29:36.940 unclassified systems . Yeah , 29:37.830 --> 29:40.350 you mentioned that you were able to Do 29:40.360 --> 29:42.360 you really focus as other that much 29:42.360 --> 29:44.471 right ? You start off focused that on 29:44.471 --> 29:46.620 class and then mixed in some of the 29:46.620 --> 29:48.620 classified work as you were able to 29:48.620 --> 29:50.842 normalize your operations for the Times 29:51.140 --> 29:53.307 at the State Department could give the 29:53.307 --> 29:55.840 percentage or are some kind of idea how 29:55.840 --> 29:58.050 much of the work that gets done is 29:58.060 --> 30:01.390 classified versus unq last well , and 30:01.630 --> 30:03.852 I would have to distinguish between the 30:03.852 --> 30:06.110 bureau and the department . So , 30:06.120 --> 30:09.700 partner , um is massive 30:10.240 --> 30:12.990 global , and the vast majority of it is 30:12.990 --> 30:16.510 unclassified or generally , if you 30:16.510 --> 30:19.350 say system high in the department , 30:19.780 --> 30:22.570 most people think secret . But within 30:22.570 --> 30:24.570 the bureau , which is one of the 17 30:24.570 --> 30:27.200 members of the the I C but which also 30:27.210 --> 30:29.043 sits in the department providing 30:29.043 --> 30:31.210 intelligence support to the department 30:31.370 --> 30:33.950 system highs , ts code word 30:34.910 --> 30:38.070 and pretty much everything that folks 30:38.070 --> 30:40.750 dio is done on that system . It's the 30:40.750 --> 30:43.120 same sort of challenge that I know . My 30:43.120 --> 30:46.000 colleagues , uh , from CIA with the 30:46.000 --> 30:48.730 familiar went back at our home agency 30:48.730 --> 30:52.030 is very difficult to do Top secret 30:52.090 --> 30:56.000 work , uh , in outside of outside of 30:56.000 --> 30:58.110 protected enclaves . That's 30:58.120 --> 31:01.560 understandable . So take it . With that 31:01.560 --> 31:04.570 in mind , I want to chip back over to 31:04.580 --> 31:08.260 Teoh . Some of our other Panelists get 31:08.260 --> 31:11.800 an idea of how that classified work is 31:11.800 --> 31:14.260 getting done . We mentioned some shift 31:14.260 --> 31:17.290 rotations . I know some work doing 31:17.290 --> 31:20.280 things like a proxy . Uh , so you can 31:20.280 --> 31:23.110 you can they take the classified nature 31:23.110 --> 31:25.620 out of the data or the workload and do 31:25.620 --> 31:27.731 it in an unclassified manner and then 31:27.731 --> 31:29.898 match it back ? Can we talk about some 31:29.898 --> 31:31.953 of how that works ? Uh , let's start 31:31.953 --> 31:34.170 with you . How have you been able to 31:34.170 --> 31:37.460 help people do the classified work in 31:37.460 --> 31:39.682 this time ? Can they do it at home ? Do 31:39.682 --> 31:41.738 they have to be in a skiff ? How did 31:41.738 --> 31:43.960 that work ? So that's a good question . 31:43.960 --> 31:46.050 And then let me answer from an icy 31:46.050 --> 31:47.994 perspective because it is a little 31:47.994 --> 31:50.050 different depending on where you are 31:50.050 --> 31:52.272 and what work being done . By and large 31:52.272 --> 31:54.217 for majority most the intelligence 31:54.217 --> 31:57.700 community , you could say 9% . All of 31:57.700 --> 32:00.800 the work should be performed in a 32:00.810 --> 32:03.200 secure facility . When I say classified 32:03.200 --> 32:06.700 work , I mean data information that we 32:06.700 --> 32:08.867 would like to have protected at higher 32:08.867 --> 32:11.940 levels . And so But within the I see , 32:11.940 --> 32:14.162 we do have multiple domains of multiple 32:14.162 --> 32:16.107 classifications so that some of my 32:16.107 --> 32:18.051 colleagues spoke about work in the 32:18.051 --> 32:20.051 unclassified realm or on classified 32:20.051 --> 32:21.890 world . Yes , we do have data 32:21.890 --> 32:24.400 information and environments that are 32:24.400 --> 32:27.190 available on the unclassified world and 32:27.240 --> 32:29.420 have been even prior to the pandemic , 32:29.590 --> 32:32.000 that people are able to do some work of 32:32.120 --> 32:34.760 remotely via that . But by and large , 32:34.760 --> 32:38.180 when it comes to what typically the the 32:38.180 --> 32:40.950 icy traditionally is known for , which 32:40.950 --> 32:43.990 is your higher classified related items ? 32:44.000 --> 32:46.770 Yes , that is , in a secure facility . 32:47.080 --> 32:51.020 We do a quart , uh , situations where 32:51.020 --> 32:53.790 you have maybe facilities working with 32:53.790 --> 32:56.068 vendors are working in other locations , 32:56.800 --> 32:58.633 but or working with , you know , 32:58.633 --> 33:01.380 defense . But by by far in large , it 33:01.380 --> 33:03.920 is in a secure facility . So the way 33:03.920 --> 33:06.087 that we looked at the challenge or the 33:06.087 --> 33:08.850 problem or the situation . Waas okay , 33:09.030 --> 33:11.510 at most of the work that a majority of 33:11.510 --> 33:13.566 the workforce needs to do is in this 33:14.260 --> 33:16.427 the care facility within that bubble . 33:16.427 --> 33:18.670 How can we maximize our efforts ? And 33:18.670 --> 33:20.892 that's where you have a lot of flexible 33:20.892 --> 33:23.050 work agreements . You have a lot of 33:23.270 --> 33:26.870 time sharing . As far as although , you 33:26.870 --> 33:29.860 know , we may have situated here in the 33:29.920 --> 33:31.864 metropolitan area . There could be 33:31.864 --> 33:33.976 members of the intelligence community 33:33.976 --> 33:36.198 and other places because our mission is 33:36.198 --> 33:39.150 not just here . And also so you think 33:39.150 --> 33:42.460 about the icy is very a very large off 33:42.540 --> 33:45.840 of of different types of intelligence 33:45.850 --> 33:47.820 because their mission sets are so 33:47.820 --> 33:49.931 variable . Right ? So , you know , we 33:49.931 --> 33:52.098 have some of the intelligence agencies 33:52.098 --> 33:53.987 that traditionally operate on the 33:53.987 --> 33:56.098 higher classified domains , which has 33:56.098 --> 33:58.480 some of the service , uh , services 33:58.480 --> 34:00.702 operate on the secret domain , and then 34:00.702 --> 34:02.813 you might have some elements that may 34:02.813 --> 34:05.036 be due more than mission unclassified . 34:05.036 --> 34:07.410 So because it varies in the type of 34:07.410 --> 34:09.720 intelligence that we're performing , it 34:09.720 --> 34:11.942 does specifically depend on the mission 34:11.942 --> 34:14.109 set and that mission . That is what we 34:14.109 --> 34:17.310 look at as what is the risk for what is 34:17.610 --> 34:20.030 the the way that we can achieve that . 34:20.040 --> 34:23.100 How it may not be just from your normal 34:23.100 --> 34:25.630 9 to 5 here in in the D C area . It 34:25.630 --> 34:28.770 could be somewhere else . And so , but 34:29.050 --> 34:31.220 unlike my colleagues , we we are a 34:31.220 --> 34:33.170 little more stringent , maybe with 34:33.430 --> 34:35.319 trying to do that . And it's just 34:35.319 --> 34:37.208 because that the work is a little 34:37.208 --> 34:39.208 different . We all work in the same 34:39.208 --> 34:41.060 field , doing a little bit of a 34:41.060 --> 34:44.460 different role . So over now that is 34:44.760 --> 34:47.270 the next one point . Yo dd diversity of 34:47.270 --> 34:49.440 the mission and how none of this is 34:49.880 --> 34:52.050 static haven't thinking about a year 34:52.060 --> 34:53.950 other than then The Intelligence 34:53.960 --> 34:55.793 Committee , which is such a wide 34:55.793 --> 34:57.960 community , probably the only one that 34:57.960 --> 35:00.016 might have more diverse mission test 35:00.016 --> 35:02.480 within a single group might be D . O . 35:02.480 --> 35:04.830 D . And the Commerce Department . Just 35:04.840 --> 35:07.080 commerce is a grab bag of all kinds of 35:07.080 --> 35:09.390 agencies in mission both hard , less 35:09.680 --> 35:11.800 classified work . Peter , I'd be 35:11.800 --> 35:13.800 interested to hear from you on this 35:13.800 --> 35:16.360 topic . Assessment . Did . Your role is 35:16.370 --> 35:18.703 to look at the entire enterprise across , 35:18.703 --> 35:20.830 you know , Dean , how are you ? What 35:20.830 --> 35:22.830 kind of high level guidance are you 35:22.830 --> 35:24.941 giving New components in the military 35:24.941 --> 35:27.370 branches about doing classified work 35:27.370 --> 35:29.870 right now , particularly remotely . Or 35:29.870 --> 35:32.230 are people come in on rotations in the 35:32.230 --> 35:34.452 light ? How much of that applies across 35:34.452 --> 35:36.452 the whole D o . D . And how much of 35:36.452 --> 35:38.674 that do you have to give general advice 35:38.674 --> 35:40.786 and then let the component make their 35:40.786 --> 35:43.030 own decisions ? Yeah , I think I think 35:43.830 --> 35:46.080 it's important within duty that there 35:46.080 --> 35:48.191 is always a lot of autonomy preserved 35:48.191 --> 35:50.380 at a local commander component level , 35:50.570 --> 35:52.681 and we're globally dispersed and have 35:52.681 --> 35:55.020 to respond to local conditions 35:56.760 --> 35:58.920 and diverse missions . And we really 35:58.920 --> 36:00.920 need commanders on the ground to be 36:00.920 --> 36:02.976 able to make those calls . So we try 36:02.976 --> 36:04.976 and give out guidance that is gonna 36:04.976 --> 36:07.142 allow people to make smart choices and 36:07.142 --> 36:09.142 keep things safe . Way tried really 36:09.142 --> 36:11.031 hard to stem the proliferation of 36:11.031 --> 36:12.864 Shadow I t . During this episode 36:12.864 --> 36:15.087 because we had every , you know , every 36:15.087 --> 36:17.310 command as their local to staff and 36:17.310 --> 36:19.532 their local C i o . Trying to solve the 36:19.532 --> 36:21.940 problems for themselves on but we 36:21.940 --> 36:23.884 didn't want was a proliferation of 36:23.884 --> 36:25.829 solutions that that we had limited 36:25.829 --> 36:27.600 visibility into going back to 36:27.610 --> 36:31.310 classified side points are spot on . I 36:31.310 --> 36:33.710 think for us as well , that , um 36:34.050 --> 36:36.272 although we talk about what it takes to 36:36.272 --> 36:39.870 enable some classified work remotely , 36:39.970 --> 36:42.081 I think is really important condition 36:42.081 --> 36:44.081 that to say , first of all , that's 36:44.081 --> 36:45.859 only gonna occur with a certain 36:45.859 --> 36:48.150 sensitivity of data . And second , 36:48.160 --> 36:51.220 although some home I can view a secret 36:51.220 --> 36:53.220 presentation or join a secret phone 36:53.220 --> 36:55.710 call if my job is in the war fighting 36:55.710 --> 36:57.543 domain to be looking at a common 36:57.543 --> 36:59.950 operating picture and directing the 36:59.950 --> 37:02.061 movement of aircraft , I'm only doing 37:02.061 --> 37:04.006 that in the office . And if I'm an 37:04.006 --> 37:06.006 Intel analyst and I'm working at TS 37:06.006 --> 37:07.950 level , I'm only doing that in the 37:07.950 --> 37:10.117 office . So at that point , it becomes 37:10.117 --> 37:12.600 down , comes down to , um , more of the 37:12.600 --> 37:14.767 human factors . Conversation is how do 37:14.767 --> 37:17.330 we stagger chefs ? How do we limit the 37:17.330 --> 37:19.608 number of people who are in the office ? 37:19.608 --> 37:21.608 It would be at work , and we really 37:21.608 --> 37:25.440 left most of those decisions to two 37:25.450 --> 37:28.440 local commanders and dressing . Yeah , 37:29.490 --> 37:32.120 so we are getting political into the 37:32.120 --> 37:34.250 time , and I asked for questions from 37:34.250 --> 37:36.028 the audience , and you all have 37:36.028 --> 37:38.028 delivered . We've got tons of those 37:38.028 --> 37:40.250 before we get , too , though . Carrie , 37:40.250 --> 37:42.361 I want to give the last question from 37:42.361 --> 37:44.583 me . I want to put to you . I mentioned 37:44.583 --> 37:46.970 before the idea of turning classified 37:47.090 --> 37:50.360 work flows into unclassified proxy 37:50.370 --> 37:52.537 projects . Can you talk about how some 37:52.537 --> 37:55.670 of that work at Miter and throughout 37:55.670 --> 37:57.948 the defense and intelligence community ? 37:58.430 --> 38:01.640 Uh , sure , I will again reiterate what 38:01.640 --> 38:03.918 you've just heard from our perspective . 38:03.918 --> 38:06.810 And so when we are doing the top secret 38:06.820 --> 38:10.210 has a secret problems and delivering on 38:10.210 --> 38:13.820 our on the road and I 38:13.850 --> 38:16.290 see Project , we are also within a 38:16.300 --> 38:19.220 secure facilities . But here here 38:19.220 --> 38:22.000 question being up on R and D 38:22.220 --> 38:25.760 organization . We do try and carve 38:25.770 --> 38:28.660 off our family , our Andy challenges 38:29.120 --> 38:31.860 that you could looking at new new 38:31.870 --> 38:33.900 solutions , new ways to solve those 38:33.910 --> 38:36.210 challenges . So you could put in the 38:36.210 --> 38:39.360 context maybe of a FEMA or crisis 38:39.370 --> 38:41.980 response activity . And I think about 38:41.990 --> 38:44.820 how you could pull a new modeling and 38:44.830 --> 38:46.941 simulation tools or things like vigil 38:46.941 --> 38:49.780 engineering , even looking at non 38:49.780 --> 38:52.010 traditional data . So those are the 38:52.020 --> 38:54.510 types of ways that we have expanded the 38:54.510 --> 38:56.399 app it Ercan which we address the 38:56.399 --> 38:59.500 problem . And so I think that's really 38:59.510 --> 39:03.060 something that , as I mentioned earlier , 39:03.070 --> 39:05.181 really lead to felt some innovation , 39:05.181 --> 39:07.520 and as we make those discoveries making 39:07.520 --> 39:09.631 car packet job , maybe the code , the 39:09.631 --> 39:11.742 tools of findings , and then put them 39:11.742 --> 39:13.909 back over to the classified so that we 39:13.909 --> 39:16.220 can deploy them on on the real real 39:16.220 --> 39:16.680 data . 39:19.770 --> 39:22.330 Fantastic . Good luck with that . I'm 39:22.330 --> 39:24.490 gonna move over to ah , some of the Q 39:24.490 --> 39:26.460 and A from the audience . As I 39:26.470 --> 39:28.359 mentioned , we've got quite a few 39:28.359 --> 39:30.581 questions here . We're gonna try to get 39:30.581 --> 39:32.803 through as many as we can . First off , 39:32.803 --> 39:34.970 a , uh , a consultant with the Defense 39:34.970 --> 39:37.137 Department asked our deal . The office 39:37.137 --> 39:39.137 has experienced a great increase in 39:39.137 --> 39:41.470 productivity , collaboration and morale . 39:41.470 --> 39:43.359 Been shifting to tell a work what 39:43.359 --> 39:45.526 policies need to be changed , telework 39:45.526 --> 39:47.748 in place . And what aspects of telework 39:47.748 --> 39:49.970 will d o d maintain when the cove in 19 39:49.970 --> 39:52.192 crisis is over ? You know , that sounds 39:52.192 --> 39:54.081 like it's for you . Okay , Yeah , 39:54.081 --> 39:56.192 that's it's a good point . And we and 39:56.192 --> 39:58.081 we've heard that from a number of 39:58.450 --> 40:00.506 corners and says , Hey , we actually 40:00.506 --> 40:02.617 had found , particularly from working 40:02.617 --> 40:04.561 in a knowledge work environment or 40:04.561 --> 40:06.672 something that's transactional , that 40:06.672 --> 40:08.728 productivity has benefited from this 40:08.990 --> 40:11.860 environment and one of the things we 40:11.860 --> 40:13.804 learned I think that speaks to the 40:13.804 --> 40:15.900 question is we built out some of the 40:15.900 --> 40:18.570 collaboration capabilities because we 40:18.570 --> 40:20.660 didn't . We wanted to be prepared in 40:20.660 --> 40:22.882 case our existing , like , remote VPN , 40:22.882 --> 40:24.993 everything . If that collapsed and we 40:24.993 --> 40:27.271 were underwater with capability wanted . 40:27.271 --> 40:29.493 This is kind of a catchall . One of the 40:29.493 --> 40:31.660 things we learned that there is a huge 40:31.660 --> 40:33.827 latent demand in the d . O . D . For a 40:33.827 --> 40:35.938 capability to easily collaborate with 40:35.938 --> 40:38.104 your team's easily jump up call . Flip 40:38.104 --> 40:40.271 between working on a document together 40:40.271 --> 40:41.938 back before these are not new 40:41.938 --> 40:44.104 discoveries for industry , but for D . 40:44.104 --> 40:46.104 O . D . Where we didn't have all of 40:46.104 --> 40:48.327 this capability , I think it was It was 40:48.327 --> 40:50.549 a revelation . We also because we built 40:50.549 --> 40:52.493 this out as an enterprise system , 40:52.493 --> 40:54.271 meaning a D o D wider system is 40:54.271 --> 40:56.438 supposed to something that was service 40:56.438 --> 40:58.549 unique . There's fewer barriers , the 40:58.549 --> 41:00.438 collaboration across the military 41:00.438 --> 41:02.438 services and the other agencies and 41:02.438 --> 41:04.327 field activities that make up the 41:04.327 --> 41:06.549 department . Um , I think we're looking 41:06.549 --> 41:09.620 very hard right now that at what we can 41:09.620 --> 41:11.787 preserve , there's a handful of things 41:11.787 --> 41:13.787 that we specifically want Preserved 41:13.787 --> 41:16.780 Number one is that capability to 41:16.780 --> 41:18.669 collaborate seamlessly across the 41:18.669 --> 41:20.558 entire department , so you're not 41:20.558 --> 41:22.780 locked into organizational boundaries . 41:22.780 --> 41:24.836 elsewhere in the department . Number 41:24.836 --> 41:26.724 two is to be able to do that from 41:26.724 --> 41:28.836 outside the network perimeter , which 41:28.836 --> 41:28.030 is really gonna accelerate the 41:28.030 --> 41:30.030 conversation about trust within the 41:30.030 --> 41:32.720 department and third a little bit . I 41:32.730 --> 41:34.952 think longer term goal is to be able to 41:34.952 --> 41:37.040 leverage more personal devices to be 41:37.040 --> 41:39.270 able to access that that have been 41:39.290 --> 41:41.012 found under this is all of the 41:41.012 --> 41:43.560 unclassified layer . So there's 41:43.560 --> 41:46.460 programs in work now to try and make 41:46.470 --> 41:49.820 eliminate some of what we authorize as 41:49.820 --> 41:52.670 a temporary solution going forward . My 41:52.670 --> 41:55.670 last comment on that is the tools can 41:55.670 --> 41:57.900 only do so much here . The other thing 41:57.900 --> 42:00.067 that we really have to focus on within 42:00.067 --> 42:01.670 department is the culture . 42:02.140 --> 42:04.140 Organizational culture is extremely 42:04.140 --> 42:06.362 resilient , and I do think that there's 42:06.362 --> 42:09.170 a chance that in a command and control 42:09.170 --> 42:11.670 environment like you d as soon as the 42:11.670 --> 42:13.726 leadership is back holding all their 42:13.726 --> 42:15.948 meetings in person , that flows quickly 42:15.948 --> 42:18.059 through the enterprise . So so we can 42:18.059 --> 42:19.948 help from a technology enablement 42:19.948 --> 42:22.170 standpoint . But we need that continued 42:22.170 --> 42:24.320 leadership commitment to a to a new 42:24.320 --> 42:26.431 normal . That's gonna be a little bit 42:26.431 --> 42:28.653 more flexible environment for workers . 42:28.653 --> 42:30.820 Man , I want to stay with you for this 42:30.820 --> 42:32.709 next question . I wasn't directed 42:32.709 --> 42:34.598 specifically at you , but some of 42:34.598 --> 42:36.820 things you just mentioned ductile right 42:36.820 --> 42:38.987 directly into this . So a team manager 42:38.987 --> 42:41.320 from one of our underwriters , actually , 42:41.320 --> 42:43.431 uh , agile is the direction that much 42:43.431 --> 42:45.264 of I t is moving to . One of the 42:45.264 --> 42:47.376 fundamentals of agile is face to face 42:47.376 --> 42:49.487 and working closely with team members 42:49.487 --> 42:51.264 at the same table . How are you 42:51.264 --> 42:53.264 adapting agile development toe work 42:53.264 --> 42:55.264 with a remote workforce ? So I feel 42:55.264 --> 42:57.542 like you got into some of that already , 42:57.542 --> 42:59.709 Peter , which mind ? Just very briefly 42:59.709 --> 43:01.850 addressing it directly , that this is 43:01.850 --> 43:03.900 actually a great question because I 43:03.910 --> 43:06.470 would say , if I could choose what to 43:06.470 --> 43:08.980 spend my time on , it would be on 43:08.980 --> 43:11.036 modernizing the way we were building 43:11.036 --> 43:13.258 deliver software for the department . A 43:13.258 --> 43:17.180 huge part of that is heavy user 43:17.180 --> 43:18.740 involvement , design rapid 43:18.750 --> 43:22.060 deterioration . I don't think it's 43:22.060 --> 43:25.550 fundamentally undermined by working 43:25.550 --> 43:28.030 remotely , provided that you have a 43:28.040 --> 43:30.207 really good set of schools . There are 43:30.207 --> 43:32.373 some things you can do when you've got 43:32.373 --> 43:34.373 a share screen in front of you that 43:34.373 --> 43:36.540 users can manipulate that are actually 43:36.540 --> 43:38.762 easier than watch . But I think that is 43:39.580 --> 43:41.524 particular teams that have already 43:41.524 --> 43:43.740 established trust in a battle rhythm . 43:44.580 --> 43:47.290 When I think about the places where in 43:47.290 --> 43:49.457 person interaction is still incredibly 43:49.457 --> 43:51.179 important , it's building that 43:51.179 --> 43:53.820 relationship between in this case , the 43:53.820 --> 43:56.150 development team and your user 43:56.150 --> 43:59.940 population . I I'm ready for the days 43:59.940 --> 44:01.773 when we can get those teams back 44:01.773 --> 44:03.829 together , tow launch things and get 44:03.829 --> 44:06.051 things moving . But then , as you begin 44:06.051 --> 44:08.162 to interest , I actually think , uh , 44:08.162 --> 44:10.218 way have an opportunity to go faster 44:10.218 --> 44:12.329 here because we have times today when 44:12.329 --> 44:15.250 you think about a commander control 44:15.250 --> 44:17.460 application that were delivering to 44:17.460 --> 44:19.440 users that combatant commands . In 44:19.450 --> 44:21.228 order to have that type of user 44:21.228 --> 44:23.283 feedback that we have today , we fly 44:23.283 --> 44:25.394 people back , which means we can only 44:25.394 --> 44:27.450 view that , uh , on a certain rhythm 44:27.450 --> 44:29.440 and really do that effectively , 44:29.900 --> 44:32.067 remotely . That means we could go from 44:32.067 --> 44:34.350 from three months Prince Teoh , three 44:34.350 --> 44:36.406 weeks prince and generate a lot more 44:36.406 --> 44:38.461 quickly . So it's a great question . 44:38.461 --> 44:40.517 Love toe Learn from the community on 44:40.517 --> 44:42.900 this because getting the department to 44:42.910 --> 44:45.132 be more agile on delivering software is 44:45.132 --> 44:47.466 is , I think , one of our biggest goals , 44:48.590 --> 44:51.000 and it also because we cover agile 44:51.000 --> 44:53.222 quite a bit here next . I think is also 44:53.222 --> 44:55.444 the flipside exactly what you were just 44:55.444 --> 44:57.500 talking about where , while agile in 44:57.500 --> 44:59.667 general , was intended to speed up the 44:59.667 --> 45:01.722 development process , especially for 45:01.722 --> 45:03.611 large agencies like Department of 45:03.611 --> 45:05.778 Defense . That doesn't mean that every 45:05.778 --> 45:07.944 single interaction has to be immediate 45:07.944 --> 45:10.500 right there . There is some value to a 45:10.500 --> 45:12.722 zoo I've been finding while teleworking 45:12.722 --> 45:14.778 during the pandemic . Having someone 45:14.778 --> 45:16.833 ask you a question and being able to 45:16.833 --> 45:18.722 stop and think about it for a few 45:18.722 --> 45:20.889 minutes 1/2 hour or responding through 45:20.889 --> 45:23.056 whatever communication channel so well 45:23.056 --> 45:25.278 agile . I think overall speed things up 45:25.278 --> 45:27.444 benefits . Taking a beat every now and 45:27.444 --> 45:30.470 again moving forward , uh , in the next 45:30.470 --> 45:32.581 one is for you , and it's coming from 45:32.581 --> 45:35.000 inside the house . Somebody at D and I 45:35.000 --> 45:37.090 asked , What are some of the most 45:37.090 --> 45:39.600 widely used collaboration tools being 45:39.600 --> 45:41.711 used by the intelligence community to 45:41.711 --> 45:43.878 carry out unclassified work during the 45:43.878 --> 45:45.933 pandemic ? Is that an Officer , Cody 45:45.933 --> 45:48.044 and I that has evaluated and approved 45:48.044 --> 45:49.878 certain tools for use by Odeon I 45:49.878 --> 45:51.822 components or other icy agencies ? 45:53.390 --> 45:55.870 Yes , there's a there's a few ways to 45:55.890 --> 45:59.080 answer So within OD and I the off the 45:59.080 --> 46:01.302 record national intelligence we do have 46:01.302 --> 46:04.430 localized I t organization . Uh , the 46:04.440 --> 46:06.580 Odeon I D . I . O . Does have 46:06.690 --> 46:09.310 recommendations for tools that can be 46:09.310 --> 46:12.470 used by that agency . That element . It 46:12.490 --> 46:15.340 does very across the community as to 46:15.350 --> 46:19.110 what tools applications foretold and 46:19.120 --> 46:21.231 the like , because there's many . And 46:21.231 --> 46:23.342 because we do have enterprise license 46:23.342 --> 46:25.509 agreements or E . L . A's with various 46:25.509 --> 46:27.676 companies , components organizations , 46:27.676 --> 46:29.842 in order to facilitate that management 46:29.980 --> 46:32.180 within the I C C i o . Office and not 46:32.180 --> 46:34.347 my office , we helped facilitate those 46:34.347 --> 46:36.520 L . A's across the department . So , 46:36.520 --> 46:39.840 yes , then OD and I There are some 46:39.840 --> 46:42.300 licenses that are used . The irony is , 46:42.310 --> 46:44.590 so we know the person can actually 46:44.590 --> 46:46.757 contact me directly at the I . C . C . 46:46.757 --> 46:49.780 I . A officer would like Teoh , but I 46:49.780 --> 46:52.030 would say that there are tools that 46:52.030 --> 46:54.500 they're using applications that OD and 46:54.500 --> 46:56.820 I have set up to facilitate meetings 46:56.820 --> 46:58.764 across the community . And in some 46:58.764 --> 47:00.709 cases that might be different than 47:00.709 --> 47:02.876 others . There are some other agencies 47:02.876 --> 47:05.410 and elements that have done studies . 47:05.720 --> 47:09.440 Recommendations have done a security . 47:09.450 --> 47:11.728 You could say mitigations if you would , 47:11.728 --> 47:13.950 in order for whether it be on your home 47:13.950 --> 47:16.061 and personal and private network when 47:16.061 --> 47:17.561 connecting , Or maybe some 47:17.561 --> 47:19.561 recommendations and hygiene , as we 47:19.561 --> 47:21.228 would say , cyber hygiene and 47:21.228 --> 47:23.339 cybersecurity for your devices . Some 47:23.339 --> 47:25.394 of the elements agencies are issuing 47:25.394 --> 47:27.561 out devices . For instance , I do have 47:27.561 --> 47:29.920 ODI , and I issued out devices to 47:29.920 --> 47:33.860 connect to my account , my OD and I 47:33.870 --> 47:36.037 accounts . And then that is the case . 47:36.037 --> 47:38.259 I would say that's also Avenue in a way 47:38.259 --> 47:40.259 to go toe Xs your official mail and 47:40.300 --> 47:42.820 your official data storage information 47:42.820 --> 47:45.360 on the unclassified side , because 47:45.370 --> 47:47.592 there is a myriad of solutions , and it 47:47.592 --> 47:49.800 really depends on the use case I don't 47:49.800 --> 47:53.410 like specify one is more secure or one 47:53.410 --> 47:55.521 is better than the other , because it 47:55.521 --> 47:57.743 does just depend on what you're doing , 47:57.743 --> 47:59.910 that there are at least many means and 47:59.910 --> 48:03.190 modes in ways that we can accomplish . 48:03.200 --> 48:06.000 That I would say a recommend going with 48:06.010 --> 48:09.030 the Odeon . I see Iot office or be 48:09.170 --> 48:11.740 going with issuing some devices , and 48:11.740 --> 48:13.573 they actually have the tools and 48:13.573 --> 48:15.629 applications set up within their and 48:15.629 --> 48:17.907 then by the public Internet We do have . 48:17.907 --> 48:20.060 Some of the icy elements have issued 48:20.060 --> 48:23.990 out , uh , cyber recommendations and 48:24.290 --> 48:27.570 cyber security steps that anyone can 48:27.570 --> 48:30.040 use just as an American to help protect 48:30.040 --> 48:32.250 your devices . on behalf of National 48:32.250 --> 48:36.120 Security . Over Nice one . I get a 48:36.130 --> 48:38.241 couple more here before we wrap up in 48:38.241 --> 48:40.130 the next one . I'm actually gonna 48:40.130 --> 48:42.241 combine two questions because they're 48:42.241 --> 48:44.352 very similar . Um , and this is gonna 48:44.352 --> 48:46.574 be for for you and a A and for Kerry as 48:46.574 --> 48:49.690 well . So first off , a person within D 48:49.690 --> 48:52.800 and I asked is od and I considering 48:52.800 --> 48:55.100 exploring systems similar to the ones 48:55.100 --> 48:57.500 Mr Ranks mentioned that would enable OD 48:57.500 --> 48:59.620 and I or I see employees toe work on 48:59.620 --> 49:02.010 classified work from home . And then 49:02.010 --> 49:04.121 also , I'm gonna combine it with this 49:04.121 --> 49:06.343 other question from Tish Lawn . Care of 49:06.343 --> 49:08.740 of in . So thanks dish for Len and 49:08.740 --> 49:11.560 Carrie about classified work from home . 49:11.780 --> 49:13.836 I understand . Both the army and the 49:13.836 --> 49:15.947 Air Force has some pilot programs for 49:15.947 --> 49:18.460 mobile secret . What is the icy doing 49:18.460 --> 49:20.890 in this arena ? So I think those kind 49:20.890 --> 49:22.946 of kind of go together . Then I will 49:22.946 --> 49:25.112 start with you . And that will get the 49:25.112 --> 49:27.390 last last word to carry during connect . 49:27.580 --> 49:29.913 Jump in on . That is the third , please . 49:29.913 --> 49:32.024 Oh , sure . You're looking at the end 49:32.024 --> 49:35.860 there , so I'll go to the first 49:35.860 --> 49:38.170 question . The verse one about is OD 49:38.170 --> 49:40.392 and I considering working on classified 49:40.392 --> 49:43.630 work I hold at home . Pete kind of hit 49:43.630 --> 49:46.260 on this . There's a lot that that's 49:46.260 --> 49:48.560 wrapped in that question . Culture is 49:48.570 --> 49:52.310 one , uh , safety and security huge . 49:52.310 --> 49:55.030 And these are all big areas . I 49:55.040 --> 49:57.190 wouldn't say yes or no to that . I 49:57.190 --> 49:59.246 think that we're constantly evolving 49:59.380 --> 50:01.560 constantly , constantly looking at our 50:01.560 --> 50:04.070 mission and how we can maybe improve it 50:04.280 --> 50:06.280 and do things better . But it's not 50:06.280 --> 50:08.690 really a cut and dry question . Yes , 50:08.700 --> 50:10.450 there are some elements as you 50:10.450 --> 50:12.672 mentioned the pilot , uh , with some of 50:12.672 --> 50:14.894 the services they're doing secret . But 50:14.894 --> 50:18.370 as I mentioned earlier , it is for very 50:18.380 --> 50:21.170 specific use cases in subsets in very 50:21.180 --> 50:23.310 specific instances . I don't want to 50:23.310 --> 50:25.990 paint the picture . Are the mirage that 50:25.990 --> 50:27.940 we have people in the intelligence 50:27.950 --> 50:30.350 community that are accessing classified 50:30.360 --> 50:32.527 data from home because that's just not 50:32.527 --> 50:34.693 the case we're looking at it at . What 50:34.693 --> 50:36.930 can we do ? And within that classified 50:36.940 --> 50:39.340 information , what makes the classified 50:39.390 --> 50:41.334 and are there elements in parts or 50:41.334 --> 50:43.590 pieces or processes that we can do on a 50:43.590 --> 50:45.620 lower classified domain that can 50:45.620 --> 50:48.040 mitigate that ? As you mentioned before ? 50:48.040 --> 50:50.950 Sometimes we look at it and we're in a 50:50.950 --> 50:53.820 paradigm shift , so it makes us look at 50:53.820 --> 50:56.870 how are operating . And in some cases 50:56.880 --> 50:59.047 there may be portions of the work that 50:59.047 --> 51:01.380 we're performing that can be done at 51:01.390 --> 51:03.630 the lower classified domains or at a 51:03.630 --> 51:06.250 tele work remote facility that don't 51:06.250 --> 51:09.270 need quite as much of the enforcement 51:09.410 --> 51:11.632 of the security rappers at the others . 51:11.960 --> 51:14.810 So I would say that that may not be the 51:14.820 --> 51:17.320 most straightforward answer , but it's 51:17.330 --> 51:20.160 really just just we're taking it . Uh , 51:20.170 --> 51:23.050 we need to really evaluate it and pill 51:23.050 --> 51:25.106 back that question . And just as the 51:25.106 --> 51:27.383 onion , there's a lot wrapped in there . 51:27.383 --> 51:28.383 Oh , yeah , 51:28.383 --> 51:36.130 Wait . 51:36.130 --> 51:38.297 And Peter said it well , and I want to 51:38.297 --> 51:41.920 say hi to and um yes , looking forward 51:41.930 --> 51:43.930 to , as we continue those pilots to 51:43.930 --> 51:46.152 learn more about how we can start great 51:46.152 --> 51:48.374 bringing that into some of the contract 51:48.374 --> 51:51.500 your basis Well , thank you . No way 51:51.500 --> 51:53.667 are running just over time . But I did 51:53.667 --> 51:55.722 want to let the last last two people 51:55.722 --> 51:57.722 just jump in on this topic . If you 51:57.722 --> 51:59.778 could keep it like 30 60 seconds and 51:59.778 --> 52:02.690 then we'll move right through . Erin , 52:02.690 --> 52:04.857 this is Japanese . Think we started to 52:04.857 --> 52:06.912 hit on what the real elephant in the 52:06.912 --> 52:08.980 room is here , which is that the 52:08.980 --> 52:11.060 intelligence community is vulnerable 52:11.390 --> 52:13.860 because we have to rely on high walls 52:13.860 --> 52:16.540 and fortifications around are 52:16.710 --> 52:18.960 classified operations . Frankly , I 52:18.960 --> 52:22.030 feel like it's May 1940 I'm sitting 52:22.700 --> 52:26.290 cozy and comfy in a fortification on 52:26.290 --> 52:28.720 the Maginot Line , and my adversary , 52:28.720 --> 52:32.580 who was coded right now is more agile 52:32.650 --> 52:34.790 than we are . Eso If you're talking 52:34.790 --> 52:37.450 about lessons learned from this , it's 52:37.450 --> 52:39.061 about understanding that the 52:39.061 --> 52:41.283 environment in which we're operating is 52:41.283 --> 52:43.690 changing , and we always been 52:43.690 --> 52:45.857 vulnerable to this . We've always been 52:45.857 --> 52:48.023 sort of isolated , but we've been able 52:48.023 --> 52:49.968 to live with it now . We can't any 52:49.968 --> 52:52.600 Walker , so we need to change , all 52:52.600 --> 52:54.822 right . And unfortunately , with that , 52:54.822 --> 52:56.878 I'm getting the hard hook . So we're 52:56.878 --> 52:59.100 gonna have to wrap up here . Why didn't 52:59.100 --> 53:01.322 think Jeff's when a P and carry you all 53:01.322 --> 53:03.544 were fantastic today on thank you . Our 53:03.544 --> 53:05.267 audience for listening and for 53:05.267 --> 53:07.489 submitting so many great questions as a 53:07.489 --> 53:09.711 reminder of the on demand event will be 53:09.711 --> 53:09.180 sent to you later this week , and we 53:09.180 --> 53:11.013 encourage you to share with your 53:11.013 --> 53:13.180 colleagues who may have missed today's 53:13.180 --> 53:13.020 discussion programme would not be 53:13.020 --> 53:15.020 possible without the support of our 53:15.020 --> 53:17.076 underwriter perspective , and I also 53:17.076 --> 53:19.187 want to thank integral part will with 53:19.187 --> 53:18.260 us on the power .