1 00:00:00,000 --> 00:00:00,000 2 00:00:06,740 --> 00:00:08,573 Good afternoon everyone and good 3 00:00:08,573 --> 00:00:10,796 morning to our colleagues in the west , 4 00:00:10,796 --> 00:00:13,129 very glad you're with us for the 2022 D . 5 00:00:13,129 --> 00:00:15,351 O . D . Cloud exchange , we've got what 6 00:00:15,351 --> 00:00:17,573 we think is going to be a great week of 7 00:00:17,573 --> 00:00:19,629 content lined up for you this week . 8 00:00:19,629 --> 00:00:19,070 And if you've joined us on any of our 9 00:00:19,070 --> 00:00:21,126 previous cloud exchanges , hopefully 10 00:00:21,126 --> 00:00:23,237 you've gotten the gist of what we try 11 00:00:23,237 --> 00:00:25,348 to do with these events , which is to 12 00:00:25,348 --> 00:00:27,459 zoom out a little bit from the day to 13 00:00:27,459 --> 00:00:29,626 day cloud computing , news that me and 14 00:00:29,626 --> 00:00:31,681 my colleagues across the media space 15 00:00:31,681 --> 00:00:33,737 report on day in and day out and and 16 00:00:33,737 --> 00:00:35,903 really let our government and industry 17 00:00:35,903 --> 00:00:37,848 speakers give you something like a 18 00:00:37,848 --> 00:00:40,126 state of the Union for where D . O . D . 19 00:00:40,126 --> 00:00:42,237 Is in its adoption of cloud computing 20 00:00:42,237 --> 00:00:44,348 as of this moment in in the big grand 21 00:00:44,348 --> 00:00:46,514 scheme of things . The common theme of 22 00:00:46,514 --> 00:00:45,840 the events that we've tried to do so 23 00:00:45,840 --> 00:00:48,020 far is really to highlight real 24 00:00:48,020 --> 00:00:51,440 concrete progress as well this year . 25 00:00:51,440 --> 00:00:53,662 The thing that we're trying to organize 26 00:00:53,662 --> 00:00:55,496 around is the role that cloud is 27 00:00:55,496 --> 00:00:57,718 playing in the bigger I . T . Strategic 28 00:00:57,718 --> 00:00:59,662 frameworks that D . U . D . In the 29 00:00:59,662 --> 00:01:01,829 military services have been working on 30 00:01:01,829 --> 00:01:03,940 and have indeed published now . And I 31 00:01:03,940 --> 00:01:03,880 think that's happened in a way where 32 00:01:03,880 --> 00:01:05,950 the question is less about how do we 33 00:01:05,950 --> 00:01:08,770 get to the cloud ? Less about assuming 34 00:01:08,770 --> 00:01:11,300 that cloud is inherently going to be 35 00:01:11,300 --> 00:01:13,500 better in all cases than on premise 36 00:01:13,500 --> 00:01:15,790 environments and more about why D . O . 37 00:01:15,790 --> 00:01:17,957 D . Is going to the cloud in the first 38 00:01:17,957 --> 00:01:20,179 place and what it can get from being in 39 00:01:20,179 --> 00:01:22,290 the cloud leadership has done quite a 40 00:01:22,290 --> 00:01:24,346 bit over the past year to sharpen up 41 00:01:24,346 --> 00:01:26,512 thinking on things like where we think 42 00:01:26,512 --> 00:01:28,290 think cloud fits in our digital 43 00:01:28,290 --> 00:01:30,401 transformation strategy and there are 44 00:01:30,401 --> 00:01:30,370 different words for that . But 45 00:01:30,370 --> 00:01:32,481 directionally I think you're seeing a 46 00:01:32,481 --> 00:01:34,648 lot of commonality across the services 47 00:01:34,648 --> 00:01:36,870 and agencies and at the OSD level and , 48 00:01:36,870 --> 00:01:38,814 and it's hard to point to a better 49 00:01:38,814 --> 00:01:40,814 example of everything I just talked 50 00:01:40,814 --> 00:01:42,648 about than the brand new D O D . 51 00:01:42,648 --> 00:01:44,259 Software monitors , software 52 00:01:44,259 --> 00:01:46,370 modernization strategy that just came 53 00:01:46,370 --> 00:01:48,203 out from OSD last month . It's a 54 00:01:48,203 --> 00:01:47,830 perfect place to start this 55 00:01:47,830 --> 00:01:50,052 conversation on this year's D O D cloud 56 00:01:50,052 --> 00:01:52,219 exchange and for our kickoff keynote , 57 00:01:52,219 --> 00:01:53,997 we're very glad to have with us 58 00:01:53,997 --> 00:01:56,163 Danielle Metz , the deputy D O D C I O 59 00:01:56,163 --> 00:01:58,386 for Information Enterprise to talk more 60 00:01:58,386 --> 00:02:00,552 about that strategy at the D O D level 61 00:02:00,552 --> 00:02:02,663 and all other things . Cloud from the 62 00:02:02,663 --> 00:02:04,830 OSD perspective MS . Metz , Thanks for 63 00:02:04,830 --> 00:02:06,608 being with us , appreciate it . 64 00:02:06,608 --> 00:02:08,608 Absolutely . Thank you And MS let's 65 00:02:08,608 --> 00:02:10,219 let's dig into that software 66 00:02:10,219 --> 00:02:12,386 modernization strategy . Um one of the 67 00:02:12,386 --> 00:02:14,441 things that it's very clear about is 68 00:02:14,441 --> 00:02:16,441 that it is also the new D O D cloud 69 00:02:16,441 --> 00:02:18,441 strategy . Talk a bit about why you 70 00:02:18,441 --> 00:02:20,497 decided to fold all of that together 71 00:02:20,497 --> 00:02:22,608 into a broader software modernization 72 00:02:22,608 --> 00:02:24,719 strategy rather than just doing a new 73 00:02:24,719 --> 00:02:27,052 standalone update to the cloud strategy . 74 00:02:27,052 --> 00:02:29,219 Yeah . After , after our initial cloud 75 00:02:29,219 --> 00:02:31,441 strategy that we published in 2018 , we 76 00:02:31,441 --> 00:02:33,330 began to realize that the mission 77 00:02:33,330 --> 00:02:35,497 impact was not immediately jumping out 78 00:02:35,497 --> 00:02:37,330 at folks and that the purpose in 79 00:02:37,330 --> 00:02:39,552 guiding the department to the cloud was 80 00:02:39,552 --> 00:02:42,360 never to migrate to this really cool 81 00:02:42,360 --> 00:02:45,010 technology called the cloud . And so 82 00:02:45,010 --> 00:02:47,830 what we wanted to be able to do was to 83 00:02:47,840 --> 00:02:50,920 rethink that . So starting in late 2019 , 84 00:02:50,930 --> 00:02:53,750 we began a very measured uh 85 00:02:53,760 --> 00:02:56,430 strategic shift to software 86 00:02:56,430 --> 00:02:58,319 modernization , being the primary 87 00:02:58,319 --> 00:03:00,440 driver for why we wanted people to go 88 00:03:00,440 --> 00:03:02,496 to the cloud , why we wanted to move 89 00:03:02,496 --> 00:03:04,718 the department to go to the cloud . And 90 00:03:04,718 --> 00:03:06,940 it was really the rationale for why the 91 00:03:06,940 --> 00:03:09,162 systems needed to go to the cloud . And 92 00:03:09,162 --> 00:03:11,329 so all of this is now reflected in our 93 00:03:11,329 --> 00:03:13,329 new software modernization strategy 94 00:03:13,329 --> 00:03:15,384 that was published last month . Um I 95 00:03:15,384 --> 00:03:17,440 don't think it really makes a lot of 96 00:03:17,440 --> 00:03:17,260 sense to separate software 97 00:03:17,260 --> 00:03:20,080 modernization um from cloud adoption 98 00:03:20,090 --> 00:03:22,980 because it would imply that software uh 99 00:03:22,990 --> 00:03:25,960 could be modernized without cloud . Um 100 00:03:25,960 --> 00:03:28,320 and by placing the cloud at the center 101 00:03:28,320 --> 00:03:30,540 of the technology enablers of the 102 00:03:30,540 --> 00:03:33,270 strategy that we just did . It 103 00:03:33,280 --> 00:03:36,420 absolutely affirms the importance of 104 00:03:36,420 --> 00:03:39,040 cloud and why we want the department to 105 00:03:39,040 --> 00:03:41,550 move uh and migrate to cloud both the 106 00:03:41,550 --> 00:03:43,550 military departments as well as the 107 00:03:43,550 --> 00:03:45,383 Fourth Estate . And it's further 108 00:03:45,383 --> 00:03:47,383 reinforced in the D . O . D . C IOS 109 00:03:47,383 --> 00:03:49,606 capability planning guidance that we've 110 00:03:49,606 --> 00:03:49,580 been issuing and sharing with the 111 00:03:49,580 --> 00:03:51,850 military departments As well as the 4th 112 00:03:51,850 --> 00:03:54,490 estate for the past few years guiding 113 00:03:54,490 --> 00:03:56,560 them towards an industry standard 114 00:03:56,560 --> 00:03:59,330 target of cloud spin while achieving 115 00:03:59,330 --> 00:04:01,780 the benefits of Decommissioning their 116 00:04:01,780 --> 00:04:04,830 legacy systems . So in some ways these 117 00:04:04,830 --> 00:04:06,941 things are mutually reinforcing you , 118 00:04:06,941 --> 00:04:09,940 you do get some cost savings or don't 119 00:04:09,940 --> 00:04:12,610 you ? Because the sort of the thought 120 00:04:12,610 --> 00:04:14,832 leadership in the D . O . D . Space has 121 00:04:14,832 --> 00:04:16,999 gone a bit back and forth on that over 122 00:04:16,999 --> 00:04:19,166 the years as to whether this saves you 123 00:04:19,166 --> 00:04:21,166 money in the end or doesn't whether 124 00:04:21,166 --> 00:04:23,332 cost savings is really an objective in 125 00:04:23,332 --> 00:04:22,680 the first place or not , Have we 126 00:04:22,680 --> 00:04:24,920 shifted back to the idea that not only 127 00:04:24,920 --> 00:04:26,976 is it a better mission enabler , you 128 00:04:26,976 --> 00:04:29,253 can also save money if you do it right ? 129 00:04:29,253 --> 00:04:31,476 Yeah , I think , you know , the idea of 130 00:04:31,476 --> 00:04:33,642 saving money by going to the cloud was 131 00:04:33,642 --> 00:04:35,309 a misnomer , not only for the 132 00:04:35,309 --> 00:04:37,031 department but for the federal 133 00:04:37,031 --> 00:04:38,976 government . And I think it's just 134 00:04:38,976 --> 00:04:41,198 because we didn't really understand our 135 00:04:41,198 --> 00:04:43,031 inventory , the applications and 136 00:04:43,031 --> 00:04:45,198 workloads where they were and how hard 137 00:04:45,198 --> 00:04:46,920 it would be to transform those 138 00:04:46,920 --> 00:04:49,142 workloads to be cloud enabled and cloud 139 00:04:49,142 --> 00:04:51,640 ready . Um and so that was a false 140 00:04:51,640 --> 00:04:53,696 premise , but I think now and that's 141 00:04:53,696 --> 00:04:55,862 the reason why we've kind of broadened 142 00:04:55,862 --> 00:04:57,751 the aperture of what we think the 143 00:04:57,751 --> 00:04:59,807 problem statement is and it's how do 144 00:04:59,807 --> 00:05:02,830 you quickly and actually uh develop and 145 00:05:02,830 --> 00:05:05,780 then get capability to for us , the war 146 00:05:05,780 --> 00:05:08,300 fighter at the speed of relevance . And 147 00:05:08,300 --> 00:05:10,450 so it really comes down to having 148 00:05:10,450 --> 00:05:12,339 harnessing the power of the cloud 149 00:05:12,339 --> 00:05:14,228 compute uh and then being able to 150 00:05:14,228 --> 00:05:17,890 natively build applications um 151 00:05:17,900 --> 00:05:20,630 continuously and often in that space . 152 00:05:20,640 --> 00:05:23,200 And so it also affords better 153 00:05:23,200 --> 00:05:26,050 cybersecurity , uh the ability to have 154 00:05:26,060 --> 00:05:28,150 um technology at the , at the 155 00:05:28,150 --> 00:05:30,670 fingertips of our war fighter as 156 00:05:30,670 --> 00:05:33,380 opposed to trying to have this hardware 157 00:05:33,380 --> 00:05:36,290 intensive platform that you then bolt 158 00:05:36,290 --> 00:05:39,420 on software . Uh So I think that there 159 00:05:39,420 --> 00:05:41,260 could be an opportunity for cost 160 00:05:41,260 --> 00:05:43,260 savings , but that's really not the 161 00:05:43,260 --> 00:05:45,670 primary driver , it's all about agility , 162 00:05:45,680 --> 00:05:48,690 the cybersecurity , um making sure that 163 00:05:48,690 --> 00:05:50,900 our warfighter has exactly what he and 164 00:05:50,900 --> 00:05:53,233 she needs at the time that she needs it . 165 00:05:53,340 --> 00:05:55,396 Another just high level thing on the 166 00:05:55,396 --> 00:05:57,618 strategy before we dig into some of the 167 00:05:57,618 --> 00:05:59,770 details inside of it um noteworthy on 168 00:05:59,770 --> 00:06:01,881 this one is that it has the signature 169 00:06:01,881 --> 00:06:03,826 of the Deputy Secretary of Defense 170 00:06:03,826 --> 00:06:06,190 talked about how important that is . Um 171 00:06:06,200 --> 00:06:08,367 because I think that is also knew when 172 00:06:08,367 --> 00:06:10,533 it comes to a D O . D . I . T strategy 173 00:06:10,533 --> 00:06:12,367 document . Yeah , it's extremely 174 00:06:12,367 --> 00:06:14,644 important and you know , quite frankly , 175 00:06:14,644 --> 00:06:16,700 the D O . D . Cloud strategy uh that 176 00:06:16,700 --> 00:06:18,756 was sent out in 2018 was also signed 177 00:06:18,756 --> 00:06:20,811 out by Deputy Secretary of Defense . 178 00:06:20,811 --> 00:06:22,811 And so it's a compliment and it's a 179 00:06:22,811 --> 00:06:24,978 recognition in terms of the importance 180 00:06:24,978 --> 00:06:27,790 of this being a joint endeavor for the 181 00:06:27,790 --> 00:06:29,901 entire department . And it's not just 182 00:06:29,901 --> 00:06:32,400 coming from one organization saying 183 00:06:32,410 --> 00:06:34,720 that we need to do this . It is 184 00:06:34,730 --> 00:06:37,910 combining superpowers of three offices . 185 00:06:37,910 --> 00:06:40,760 Secretary of Defense components are 186 00:06:40,770 --> 00:06:43,110 research and engineering . Brothers and 187 00:06:43,110 --> 00:06:44,832 sisters are acquisitions , the 188 00:06:44,832 --> 00:06:46,888 statement Brother and Sisters and of 189 00:06:46,888 --> 00:06:49,180 course D . O . D C I O uh and so uh we 190 00:06:49,180 --> 00:06:51,410 recognize that we need to have software 191 00:06:51,410 --> 00:06:54,210 modernization principles and practices 192 00:06:54,210 --> 00:06:56,470 within the department and how we go 193 00:06:56,470 --> 00:06:58,850 about doing that through the combined 194 00:06:58,850 --> 00:07:00,350 superpowers of those three 195 00:07:00,350 --> 00:07:02,572 organizations is that we want to remove 196 00:07:02,572 --> 00:07:04,683 impediments in our business processes 197 00:07:04,683 --> 00:07:07,380 that allow us to think and obtain 198 00:07:07,390 --> 00:07:11,170 actual technology um and 199 00:07:11,170 --> 00:07:13,392 really inculcate that into our business 200 00:07:13,392 --> 00:07:15,448 processes . So it's not just done by 201 00:07:15,448 --> 00:07:17,392 exception , Which is what has been 202 00:07:17,392 --> 00:07:19,503 happening for the past . You know , I 203 00:07:19,503 --> 00:07:21,503 would say 3-4 years we know that we 204 00:07:21,503 --> 00:07:23,559 have a problem but instead of fixing 205 00:07:23,559 --> 00:07:25,781 the actual problem kind of wave on give 206 00:07:25,781 --> 00:07:28,003 an exception and test it out and see if 207 00:07:28,003 --> 00:07:30,059 it works , but we never really fully 208 00:07:30,059 --> 00:07:32,170 inculcated those lessons learned into 209 00:07:32,170 --> 00:07:33,892 our day to day normal business 210 00:07:33,892 --> 00:07:36,059 practices to make it just normal . And 211 00:07:36,059 --> 00:07:37,948 I think it's a recognition of the 212 00:07:37,948 --> 00:07:40,370 secretary hicks signature , recognizing 213 00:07:40,370 --> 00:07:42,450 not only that we have the strategy , 214 00:07:42,840 --> 00:07:44,451 but she also tasked us on an 215 00:07:44,451 --> 00:07:46,618 implementation plan . How are we going 216 00:07:46,618 --> 00:07:49,620 to execute , what are our goals or 217 00:07:49,620 --> 00:07:52,690 objectives and metrics to ensure that 218 00:07:52,690 --> 00:07:54,801 we're trending in the right direction 219 00:07:54,801 --> 00:07:57,540 and actually making progress . Um and 220 00:07:57,540 --> 00:07:59,818 so that was a task that she gave to us . 221 00:07:59,818 --> 00:08:02,570 Um and then I think by the summertime 222 00:08:02,580 --> 00:08:05,740 we will have that to her . I was 223 00:08:05,740 --> 00:08:07,796 wondering if you dig in a little bit 224 00:08:07,796 --> 00:08:10,050 more into those exceptions that you 225 00:08:10,050 --> 00:08:12,272 talked about having to make in the past 226 00:08:12,272 --> 00:08:14,390 in order to make cloud projects go 227 00:08:14,390 --> 00:08:16,501 across the department . It it gets to 228 00:08:16,501 --> 00:08:18,612 some of that implementation work that 229 00:08:18,612 --> 00:08:20,779 you talked about and I'm not gonna ask 230 00:08:20,779 --> 00:08:22,612 you to forecast what that policy 231 00:08:22,612 --> 00:08:22,540 development process is going to look 232 00:08:22,540 --> 00:08:24,810 like but what sort of hacks and 233 00:08:24,810 --> 00:08:26,977 workarounds says the department had to 234 00:08:26,977 --> 00:08:29,143 do to make cloud work in the past . So 235 00:08:29,143 --> 00:08:31,366 I think it comes down to if you look at 236 00:08:31,366 --> 00:08:35,100 our business enablers , it's really um 237 00:08:35,200 --> 00:08:39,160 acquisition , contracting the color 238 00:08:39,160 --> 00:08:41,860 of money and so that's within the N . S . 239 00:08:41,860 --> 00:08:44,770 Lane . Uh Then you can see within the C . 240 00:08:44,770 --> 00:08:47,250 I . O . Lane , it's really about cyber 241 00:08:47,250 --> 00:08:49,420 security . Uh This thing called 242 00:08:49,420 --> 00:08:52,660 continuous 80 oh , which um the D . O . 243 00:08:52,660 --> 00:08:55,000 D . C . So signed out last month as 244 00:08:55,000 --> 00:08:57,530 well that really articulated what The 245 00:08:57,530 --> 00:08:59,697 definition of continuous 80 oh , so we 246 00:08:59,697 --> 00:09:03,090 can use the same normal nature . Um the 247 00:09:03,090 --> 00:09:05,090 process in terms of how we would go 248 00:09:05,090 --> 00:09:07,090 about doing it for deficit cops and 249 00:09:07,090 --> 00:09:09,312 that , you know , as we go through this 250 00:09:09,312 --> 00:09:11,423 process , the D . O . D . System will 251 00:09:11,423 --> 00:09:13,423 be the one that will um provide the 252 00:09:13,423 --> 00:09:15,460 authorizations um for this and and 253 00:09:15,460 --> 00:09:17,680 really is to allow to ensure that all 254 00:09:17,680 --> 00:09:19,800 authorizing officials can become 255 00:09:19,800 --> 00:09:22,080 educated and standardized and how they 256 00:09:22,080 --> 00:09:24,080 would do this in the depths of cops 257 00:09:24,080 --> 00:09:26,350 manner and then move forward in that 258 00:09:26,350 --> 00:09:28,406 way . So it's kind of a transitional 259 00:09:28,406 --> 00:09:31,440 type thing . Um So I think that that 260 00:09:31,440 --> 00:09:34,990 was with within see IOS lanes um and 261 00:09:34,990 --> 00:09:37,500 then for research and engineering for 262 00:09:37,500 --> 00:09:41,470 the uh maturing research that they are 263 00:09:41,470 --> 00:09:44,750 taking place . Um these brilliant ideas 264 00:09:44,750 --> 00:09:47,250 that are incubated . How do we move 265 00:09:47,250 --> 00:09:50,540 that forward to an ecosystem , a 266 00:09:50,540 --> 00:09:52,780 software ecosystem that is going to be 267 00:09:52,780 --> 00:09:56,070 ready to accept uh and then sustain uh 268 00:09:56,080 --> 00:09:57,969 that ecosystem . And then again , 269 00:09:57,969 --> 00:10:00,080 partnering back with A and S in terms 270 00:10:00,080 --> 00:10:02,020 of how we go about procuring that 271 00:10:02,020 --> 00:10:05,330 ecosystem um to be able to create uh to 272 00:10:05,330 --> 00:10:07,441 prevent that valley of death activity 273 00:10:07,441 --> 00:10:09,497 that we know happens not only within 274 00:10:09,497 --> 00:10:11,552 the department , but quite frankly , 275 00:10:11,552 --> 00:10:13,497 even in Silicon Valley , since you 276 00:10:13,497 --> 00:10:15,663 brought up the continuous 80 oh memo , 277 00:10:15,663 --> 00:10:17,830 let me let me pull on that thread just 278 00:10:17,830 --> 00:10:17,150 a little bit . I don't want to drag you 279 00:10:17,150 --> 00:10:20,300 too much into Cisco land since you're 280 00:10:20,300 --> 00:10:23,090 not the Cisco , but as I recall that 281 00:10:23,090 --> 00:10:25,034 continuous 80 oh memo came out the 282 00:10:25,034 --> 00:10:26,812 exact same week as the software 283 00:10:26,812 --> 00:10:28,923 modernization strategy . I'm guessing 284 00:10:28,923 --> 00:10:31,146 that wasn't a coincidence , but I don't 285 00:10:31,146 --> 00:10:33,312 think they made explicit references to 286 00:10:33,312 --> 00:10:35,423 one to each other in the real world . 287 00:10:35,423 --> 00:10:37,479 How do those two things play on each 288 00:10:37,479 --> 00:10:39,590 other and how interdependent are they 289 00:10:39,590 --> 00:10:41,757 on ? It was significant and I wished I 290 00:10:41,757 --> 00:10:43,812 could claim credit for the timing of 291 00:10:43,812 --> 00:10:45,701 that . We had been working on the 292 00:10:45,701 --> 00:10:47,701 software modernization strategy for 293 00:10:47,701 --> 00:10:49,812 almost a year . Um And the reason why 294 00:10:49,812 --> 00:10:51,646 we took the time for that year's 295 00:10:51,646 --> 00:10:53,868 because we really wanted to ensure that 296 00:10:53,868 --> 00:10:55,868 each of the stakeholders across the 297 00:10:55,868 --> 00:10:58,090 department military um services as well 298 00:10:58,090 --> 00:11:00,146 as the Daffy's and Quebec commands , 299 00:11:00,146 --> 00:11:02,146 you could see themselves in in that 300 00:11:02,146 --> 00:11:04,380 strategy and then take ownership for 301 00:11:04,380 --> 00:11:07,040 its execution separate from that . We 302 00:11:07,040 --> 00:11:09,140 spent about eight months doing the 303 00:11:09,140 --> 00:11:11,590 continuous 80 oh memo of working 304 00:11:11,590 --> 00:11:13,770 through the Cisco community , um 305 00:11:13,770 --> 00:11:15,937 creating outreach , ensuring that they 306 00:11:15,937 --> 00:11:18,370 understood that they also had buy in 307 00:11:18,370 --> 00:11:20,703 from how we wanted to proceed with that . 308 00:11:20,703 --> 00:11:23,590 And so for the continuous 80 Oh , it's 309 00:11:23,590 --> 00:11:26,890 really focused on deaths , cops and uh , 310 00:11:26,900 --> 00:11:29,360 software modernization isn't limited to 311 00:11:29,360 --> 00:11:31,416 death said cops , it's one of many . 312 00:11:31,416 --> 00:11:33,360 And so when there's other software 313 00:11:33,360 --> 00:11:35,027 modernization practices , the 314 00:11:35,027 --> 00:11:36,971 principles that can come forward , 315 00:11:36,971 --> 00:11:39,193 there's a pathway within the continuous 316 00:11:39,193 --> 00:11:41,416 80 oh memo to bring that forward to the 317 00:11:41,416 --> 00:11:43,638 D . O . D . C . So to be able to review 318 00:11:43,638 --> 00:11:45,804 and then we can create another process 319 00:11:45,804 --> 00:11:47,971 similar to what we're doing with death 320 00:11:47,971 --> 00:11:50,193 set cops to always have this continuous 321 00:11:50,193 --> 00:11:52,360 authorization to operate . So it's not 322 00:11:52,360 --> 00:11:54,582 limited to devastate cops , but cops is 323 00:11:54,582 --> 00:11:56,749 our pathfinder for the continuous 80 . 324 00:11:56,749 --> 00:11:59,082 Oh , so what other paths would there be ? 325 00:11:59,082 --> 00:12:01,193 Is it , is it sort of along the lines 326 00:12:01,193 --> 00:12:03,249 that deficit cops make sense for new 327 00:12:03,249 --> 00:12:05,360 system development and you might need 328 00:12:05,360 --> 00:12:07,582 other pathways for for the legacy . How 329 00:12:07,582 --> 00:12:09,471 do you think about the separation 330 00:12:09,471 --> 00:12:11,527 between those lanes ? Well , I think 331 00:12:11,527 --> 00:12:13,471 it's just an evolution where there 332 00:12:13,471 --> 00:12:15,638 could be the next thing beyond def sec 333 00:12:15,638 --> 00:12:18,180 ops that could be considered under the 334 00:12:18,180 --> 00:12:20,124 umbrella of software modernization 335 00:12:20,124 --> 00:12:21,958 practices . Just everyone's very 336 00:12:21,958 --> 00:12:24,180 familiar with death set off . It's been 337 00:12:24,180 --> 00:12:26,347 happening for a while , but that's not 338 00:12:26,347 --> 00:12:25,370 to say that it's going to be the end 339 00:12:25,370 --> 00:12:27,537 all be all . And so we want to be able 340 00:12:27,537 --> 00:12:29,537 to not necessarily future proof but 341 00:12:29,537 --> 00:12:31,960 allow opportunity for that innovation . 342 00:12:31,960 --> 00:12:34,870 So there's another modern practice that 343 00:12:34,870 --> 00:12:37,200 goes about doing and having an 344 00:12:37,200 --> 00:12:39,367 operational effect . We wanted to make 345 00:12:39,367 --> 00:12:41,589 sure that we can also include that . So 346 00:12:41,589 --> 00:12:43,930 I wish I had that uh crystal ball to be 347 00:12:43,930 --> 00:12:45,986 able to predict that . I don't but I 348 00:12:45,986 --> 00:12:47,930 also know based on working in the 349 00:12:47,930 --> 00:12:50,320 department for 15 years that the new 350 00:12:50,320 --> 00:12:52,487 thing that you're working on right now 351 00:12:52,487 --> 00:12:54,764 isn't always going to be the new thing . 352 00:12:54,764 --> 00:12:56,987 All right , well that that deficit cops 353 00:12:56,987 --> 00:12:59,209 cops piece takes us a little bit into . 354 00:12:59,209 --> 00:12:59,070 I think one of the key pillars of the 355 00:12:59,070 --> 00:13:01,292 software modernization strategy , which 356 00:13:01,292 --> 00:13:03,070 is the big emphasis on software 357 00:13:03,070 --> 00:13:04,903 factories and their role in this 358 00:13:04,903 --> 00:13:06,670 ecosystem . Talk about why the 359 00:13:06,670 --> 00:13:08,392 department chose to make those 360 00:13:08,392 --> 00:13:10,530 factories such a key piece of this 361 00:13:10,530 --> 00:13:12,752 strategy and where you see them playing 362 00:13:12,752 --> 00:13:14,641 a role , I think for the software 363 00:13:14,641 --> 00:13:16,863 modernization strategy , we really have 364 00:13:16,863 --> 00:13:18,863 like three pillars . So the digital 365 00:13:18,863 --> 00:13:20,808 infrastructure piece where we have 366 00:13:20,808 --> 00:13:22,863 cloud is the fulcrum and then that's 367 00:13:22,863 --> 00:13:24,974 where you can have the ecosystems for 368 00:13:24,974 --> 00:13:27,086 the software factories and going back 369 00:13:27,086 --> 00:13:28,974 to what our previous conversation 370 00:13:28,974 --> 00:13:31,400 regarding exceptions . So we had 371 00:13:31,400 --> 00:13:33,800 platform one we have with the air Force 372 00:13:33,800 --> 00:13:36,420 black Pearl with the Navy in order to 373 00:13:36,420 --> 00:13:39,950 get their software factory stood up . 374 00:13:39,960 --> 00:13:41,960 There was some exceptions to policy 375 00:13:41,960 --> 00:13:44,071 that needed to take place . Um and so 376 00:13:44,071 --> 00:13:46,293 that's what I mean by having exceptions 377 00:13:46,293 --> 00:13:48,127 for exceptionalism and they were 378 00:13:48,127 --> 00:13:50,238 amazing to be able to do that because 379 00:13:50,238 --> 00:13:52,404 we were able to glean so much of their 380 00:13:52,404 --> 00:13:54,460 lessons learnt and partner with them 381 00:13:54,460 --> 00:13:56,627 and part of the work that they've done 382 00:13:56,627 --> 00:13:58,404 is translated into the software 383 00:13:58,404 --> 00:14:00,460 modernization strategy that was just 384 00:14:00,460 --> 00:14:02,516 recently published . Right . So that 385 00:14:02,516 --> 00:14:04,682 enterprise cloud environment being the 386 00:14:04,682 --> 00:14:06,516 first pillar maybe maybe take us 387 00:14:06,516 --> 00:14:06,420 through the other too quickly and then 388 00:14:06,420 --> 00:14:08,476 we'll dig into some details . Yeah , 389 00:14:08,476 --> 00:14:10,698 absolutely . So we wanted to also focus 390 00:14:10,698 --> 00:14:12,698 not only the technical labelers but 391 00:14:12,698 --> 00:14:14,642 also the fact that we need to have 392 00:14:14,642 --> 00:14:16,531 transformation and our technology 393 00:14:16,531 --> 00:14:18,531 system um process transformation as 394 00:14:18,531 --> 00:14:20,253 well as our people in business 395 00:14:20,253 --> 00:14:22,309 transformations and that totality is 396 00:14:22,309 --> 00:14:23,976 what leads us to the software 397 00:14:23,976 --> 00:14:26,031 modernization . I think the software 398 00:14:26,031 --> 00:14:28,730 factory is uh is a key aspect because 399 00:14:28,730 --> 00:14:31,130 this is where we can really focus on 400 00:14:31,130 --> 00:14:34,120 having some commonality and ecosystem 401 00:14:34,120 --> 00:14:36,420 jointness which will allow for the 402 00:14:36,420 --> 00:14:38,309 military services , the combatant 403 00:14:38,309 --> 00:14:41,410 commands to act and behave Like a joint 404 00:14:41,410 --> 00:14:43,521 force and this is really going to get 405 00:14:43,521 --> 00:14:45,688 us to that next stage of the joint all 406 00:14:45,688 --> 00:14:48,170 domain C . two um a lot of software 407 00:14:48,170 --> 00:14:50,226 factories in D . O . D . Right now , 408 00:14:50,226 --> 00:14:52,400 it's 29 . The right number . 29 is the 409 00:14:52,400 --> 00:14:54,960 right number and counting but we're at 410 00:14:54,960 --> 00:14:57,182 29 right now the current number . Maybe 411 00:14:57,182 --> 00:14:59,349 not the right number . We will go with 412 00:14:59,349 --> 00:15:01,830 current , but they're also not evenly 413 00:15:01,830 --> 00:15:03,997 spread across the services . Right ? I 414 00:15:03,997 --> 00:15:06,163 think there's a lot in the Air Force , 415 00:15:06,163 --> 00:15:07,870 only one in the army does the 416 00:15:07,870 --> 00:15:10,092 implementation plan that you're working 417 00:15:10,092 --> 00:15:12,259 on over the next few months . Start to 418 00:15:12,259 --> 00:15:14,940 try to answer the question of what the 419 00:15:14,940 --> 00:15:16,996 right number is and that's just what 420 00:15:16,996 --> 00:15:18,940 the current number is . I think we 421 00:15:18,940 --> 00:15:21,051 don't want to limit how many software 422 00:15:21,051 --> 00:15:24,020 factories we will have . Um But I do 423 00:15:24,020 --> 00:15:25,909 think what we want to go after is 424 00:15:25,909 --> 00:15:28,260 optimize the software factories um and 425 00:15:28,260 --> 00:15:30,660 ensure that we have common tools 426 00:15:30,660 --> 00:15:32,604 because if you look at each of the 427 00:15:32,604 --> 00:15:34,771 software factories , you can see a lot 428 00:15:34,771 --> 00:15:37,560 of the same tools that are being used . 429 00:15:37,570 --> 00:15:39,792 So there's an opportunity to be able to 430 00:15:39,792 --> 00:15:41,681 optimize to do enterprise service 431 00:15:41,681 --> 00:15:43,910 contracting for that . Um So there's a 432 00:15:43,910 --> 00:15:46,210 way that you can glean some um some 433 00:15:46,220 --> 00:15:48,387 cost efficiencies and some operational 434 00:15:48,387 --> 00:15:51,040 effectiveness I think for um software 435 00:15:51,040 --> 00:15:52,890 repositories . Software code 436 00:15:52,890 --> 00:15:55,001 repositories , there's an opportunity 437 00:15:55,001 --> 00:15:57,070 there that we can standardize , make 438 00:15:57,070 --> 00:15:59,600 that an enterprise service um which 439 00:15:59,600 --> 00:16:02,860 will allow not only for um better 440 00:16:02,870 --> 00:16:06,130 collaboration across different mission 441 00:16:06,130 --> 00:16:09,140 partners , um but better 442 00:16:09,150 --> 00:16:12,120 innovation and reuse so that you're not 443 00:16:12,120 --> 00:16:14,231 having to do everything in your stove 444 00:16:14,231 --> 00:16:16,398 pipe and try to figure things out . We 445 00:16:16,398 --> 00:16:18,509 really want to be able to democratize 446 00:16:18,509 --> 00:16:20,920 that activity where we can and allow 447 00:16:20,920 --> 00:16:24,000 for a core foundation um so that each 448 00:16:24,000 --> 00:16:26,111 of the services or even the combatant 449 00:16:26,111 --> 00:16:27,889 commands where they have a very 450 00:16:27,889 --> 00:16:30,056 specific unique mission they can build 451 00:16:30,056 --> 00:16:31,778 upon instead of having to redo 452 00:16:31,778 --> 00:16:34,000 everything from scratch that code reuse 453 00:16:34,000 --> 00:16:36,167 piece seems really huge to me . And as 454 00:16:36,167 --> 00:16:38,278 I recall the Defense Innovation Board 455 00:16:38,278 --> 00:16:40,444 made a big point of that in there swap 456 00:16:40,444 --> 00:16:42,444 study a couple of years ago um talk 457 00:16:42,444 --> 00:16:44,444 about some of the discrete benefits 458 00:16:44,444 --> 00:16:46,611 that you see coming from that . I mean 459 00:16:46,611 --> 00:16:48,611 Speed feels like the obvious one if 460 00:16:48,611 --> 00:16:48,480 you're not recoding stuff that's 461 00:16:48,480 --> 00:16:50,647 already been coded for other times and 462 00:16:50,647 --> 00:16:53,120 some other part of Dodd . It absolutely 463 00:16:53,120 --> 00:16:56,560 is speed . It's the reuse of peace . 464 00:16:56,570 --> 00:16:58,750 It's the fact that you don't have to 465 00:16:58,750 --> 00:17:02,170 invest do and then there's just so much 466 00:17:02,170 --> 00:17:04,450 duplication in terms of not sharing . 467 00:17:04,460 --> 00:17:06,071 And I think that this is the 468 00:17:06,071 --> 00:17:08,293 opportunity like software , the ability 469 00:17:08,293 --> 00:17:10,460 that your virtual in the cloud affords 470 00:17:10,460 --> 00:17:12,571 you the ability to share and you want 471 00:17:12,571 --> 00:17:14,682 to share because that's where you get 472 00:17:14,682 --> 00:17:16,904 that innovation and collaboration . And 473 00:17:16,904 --> 00:17:16,570 so I think it really is a cultural 474 00:17:16,570 --> 00:17:18,459 shift from having like a physical 475 00:17:18,459 --> 00:17:20,626 substantiation of something and saying 476 00:17:20,626 --> 00:17:22,681 it's yours to being in a space where 477 00:17:22,681 --> 00:17:25,920 you can actually um play use and um 478 00:17:25,930 --> 00:17:27,874 inspire for others . And so that's 479 00:17:27,874 --> 00:17:29,930 really what we're focused on and for 480 00:17:29,930 --> 00:17:32,180 the um the dip swap study that took 481 00:17:32,180 --> 00:17:34,347 place . We really took that to heart . 482 00:17:34,347 --> 00:17:36,402 So that's why over the past now it's 483 00:17:36,402 --> 00:17:38,624 been three years . Everything that they 484 00:17:38,624 --> 00:17:40,513 pointed out is now you can see um 485 00:17:40,513 --> 00:17:42,124 embodied within the software 486 00:17:42,124 --> 00:17:44,236 modernization strategy . Alright then 487 00:17:44,236 --> 00:17:46,458 let's transition a bit to the third big 488 00:17:46,458 --> 00:17:48,236 pillar in the strategy which is 489 00:17:48,236 --> 00:17:50,458 transforming your processes to make all 490 00:17:50,458 --> 00:17:52,680 of this work . You already talked a bit 491 00:17:52,680 --> 00:17:54,680 about how exceptions to policy were 492 00:17:54,680 --> 00:17:56,458 required to make previous cloud 493 00:17:56,458 --> 00:17:58,624 projects go in the past but but talk a 494 00:17:58,624 --> 00:18:00,847 bit more about where this goal is going 495 00:18:00,847 --> 00:18:02,958 to take you . Yeah so I think for the 496 00:18:02,958 --> 00:18:04,736 first step it's really from the 497 00:18:04,736 --> 00:18:06,958 acquisition standpoint . So A . And S . 498 00:18:06,958 --> 00:18:09,124 Has done over the past couple of years 499 00:18:09,124 --> 00:18:11,740 reformation in terms of of their 5000 500 00:18:11,740 --> 00:18:14,770 series for acquisition and really um 501 00:18:15,440 --> 00:18:17,760 separating how we've always done 502 00:18:17,760 --> 00:18:19,830 acquisition . Thinking of it as a 503 00:18:19,840 --> 00:18:21,951 hardware intensive with software kind 504 00:18:21,951 --> 00:18:24,610 of on the back end or I . T . On the 505 00:18:24,610 --> 00:18:26,777 back end . I remember going to the D . 506 00:18:26,777 --> 00:18:28,790 A . You a number of years ago as a 507 00:18:28,790 --> 00:18:31,370 program manager . I was doing I . T . 508 00:18:31,370 --> 00:18:33,259 But yet I was learning um to be a 509 00:18:33,259 --> 00:18:35,314 program manager as if I was going to 510 00:18:35,314 --> 00:18:37,426 deliver an aircraft carrier so it was 511 00:18:37,426 --> 00:18:39,600 15 plus years a waterfall approach . 512 00:18:39,600 --> 00:18:42,630 And that just does not translate for um 513 00:18:42,640 --> 00:18:44,751 delivering technology the way that we 514 00:18:44,751 --> 00:18:46,807 want to deliver . So A . And S . Has 515 00:18:46,807 --> 00:18:49,320 done an exceptional job in terms of um 516 00:18:49,330 --> 00:18:52,120 transforming their acquisition really 517 00:18:52,120 --> 00:18:55,100 focus on agility . Uh Software 518 00:18:55,110 --> 00:18:58,310 Pathfinder . Um And then uh doing 519 00:18:58,320 --> 00:19:00,690 outreach within the D . A . You and 520 00:19:00,690 --> 00:19:03,610 others and having um partnership with 521 00:19:03,610 --> 00:19:05,721 the program executive offices where a 522 00:19:05,721 --> 00:19:07,721 lot of this work is taking place in 523 00:19:07,721 --> 00:19:10,270 terms of um the acquisition of 524 00:19:10,270 --> 00:19:12,300 technology uh the acquisition of 525 00:19:12,300 --> 00:19:14,420 software factories and things of that 526 00:19:14,420 --> 00:19:16,900 nature . I think even within the C . I . 527 00:19:16,900 --> 00:19:19,250 O . We've done some good work . The 528 00:19:19,250 --> 00:19:21,472 biggest is what we've talked about with 529 00:19:21,472 --> 00:19:23,639 the continuous 80 . Oh that was a huge 530 00:19:23,639 --> 00:19:25,806 mind shift in terms of um what we were 531 00:19:25,806 --> 00:19:27,861 doing with risk management framework 532 00:19:27,861 --> 00:19:29,920 and then expanding it to focus on 533 00:19:29,920 --> 00:19:32,031 continuous monitoring . And so that's 534 00:19:32,031 --> 00:19:34,090 part of what continuous 80 . Oh is I 535 00:19:34,090 --> 00:19:36,201 think there was a misnomer and people 536 00:19:36,201 --> 00:19:38,368 thinking about continuous 80 . Oh it's 537 00:19:38,368 --> 00:19:40,368 like oh we're throwing out our risk 538 00:19:40,368 --> 00:19:42,534 management framework . No because risk 539 00:19:42,534 --> 00:19:44,312 management framework always had 540 00:19:44,312 --> 00:19:46,534 continuous monitoring . We just weren't 541 00:19:46,534 --> 00:19:48,757 doing it . And so with the cops and the 542 00:19:48,757 --> 00:19:50,646 way that we have it set up we can 543 00:19:50,646 --> 00:19:52,868 actually do it . And so that's that was 544 00:19:52,868 --> 00:19:54,979 a big shift from from C . I . O . And 545 00:19:54,979 --> 00:19:57,510 then of course um we're also the 546 00:19:57,510 --> 00:19:59,720 department's piloting um the budget 547 00:19:59,720 --> 00:20:02,270 activity eight for software and digital 548 00:20:02,270 --> 00:20:04,400 pathfinders . This idea of colorless 549 00:20:04,400 --> 00:20:07,600 money right now we have a significant 550 00:20:07,600 --> 00:20:09,822 problem and and I know that it was also 551 00:20:09,822 --> 00:20:11,989 um you know it's been well studied and 552 00:20:11,989 --> 00:20:14,630 reported in terms of like how our money 553 00:20:14,630 --> 00:20:16,880 is tagged . So for sustainment dollars 554 00:20:16,880 --> 00:20:19,590 you can't um do anything new 555 00:20:19,590 --> 00:20:22,280 development um for technology and so 556 00:20:22,280 --> 00:20:24,940 that's really been hamstringing us in 557 00:20:24,940 --> 00:20:26,940 on how we're going to do death said 558 00:20:26,940 --> 00:20:28,551 cops , there's a blending of 559 00:20:28,551 --> 00:20:32,250 development operations and security but 560 00:20:32,250 --> 00:20:34,880 our money and how we use our money 561 00:20:34,890 --> 00:20:36,834 isn't affording us to do that . So 562 00:20:36,834 --> 00:20:38,834 these pilot efforts that are taking 563 00:20:38,834 --> 00:20:40,612 place will inform our financial 564 00:20:40,612 --> 00:20:42,612 policies moving forward and it will 565 00:20:42,612 --> 00:20:44,710 open up the gates for us to even be 566 00:20:44,720 --> 00:20:47,610 able to be more agile . Um , in terms 567 00:20:47,610 --> 00:20:49,610 of doing depth spec ops , I want to 568 00:20:49,610 --> 00:20:51,554 stick with a colorless money piece 569 00:20:51,554 --> 00:20:53,721 because it seems like there's a ton of 570 00:20:53,721 --> 00:20:53,490 potential there and Congress has 571 00:20:53,490 --> 00:20:55,657 created a pilot authority that I think 572 00:20:55,657 --> 00:20:57,960 we're in the second year of now 573 00:20:57,990 --> 00:21:00,960 relatively limited number of programs 574 00:21:00,970 --> 00:21:03,830 in there so far . But but have you seen 575 00:21:03,830 --> 00:21:05,970 any meaningful results that that lead 576 00:21:05,970 --> 00:21:08,192 you to believe this is the way we gotta 577 00:21:08,192 --> 00:21:09,859 fund software from now on . I 578 00:21:09,859 --> 00:21:12,026 absolutely do . And I think that , you 579 00:21:12,026 --> 00:21:14,026 know , it's Air force has a piece , 580 00:21:14,026 --> 00:21:16,081 Navy has a piece , there's a Defense 581 00:21:16,081 --> 00:21:18,137 wide piece . OsD is participating as 582 00:21:18,137 --> 00:21:20,192 well . Arnie has been for leaning in 583 00:21:20,192 --> 00:21:22,790 this and so I think that um what we 584 00:21:22,790 --> 00:21:25,130 have to figure out is from the results 585 00:21:25,130 --> 00:21:27,019 of the pilot , how we're going to 586 00:21:27,019 --> 00:21:29,730 transform those policies in order for 587 00:21:29,730 --> 00:21:32,860 us to be able not to um 588 00:21:32,870 --> 00:21:36,230 to have exceptions and not have 589 00:21:36,230 --> 00:21:38,452 oversight . And I think it's that sweet 590 00:21:38,452 --> 00:21:40,910 spot balancing the ability to go fast 591 00:21:40,910 --> 00:21:44,050 without sacrificing um accountability . 592 00:21:44,440 --> 00:21:46,607 Well , yeah , and it seems like a huge 593 00:21:46,607 --> 00:21:48,718 part of this is just showing Congress 594 00:21:48,718 --> 00:21:50,829 that you can get really great results 595 00:21:50,829 --> 00:21:52,940 out of this , assuming you get really 596 00:21:52,940 --> 00:21:55,162 great results out of it and you and you 597 00:21:55,162 --> 00:21:57,329 don't lose the ability for the kill to 598 00:21:57,329 --> 00:21:59,440 track your spend . Um So are you at a 599 00:21:59,440 --> 00:22:01,551 point more of an acquisition question 600 00:22:01,551 --> 00:22:03,662 maybe , But are you a point yet where 601 00:22:03,662 --> 00:22:05,662 you can go up to the hill and say , 602 00:22:05,662 --> 00:22:07,662 look how well it's worked ? I don't 603 00:22:07,662 --> 00:22:09,884 think we're there yet , so I think that 604 00:22:09,884 --> 00:22:11,773 that's , you know , year two , it 605 00:22:11,773 --> 00:22:11,740 always takes a while to be able to 606 00:22:11,740 --> 00:22:15,420 actually do an execution , analyze the 607 00:22:15,420 --> 00:22:17,531 results and come up with a thoughtful 608 00:22:17,531 --> 00:22:19,420 policy change and then be able to 609 00:22:19,420 --> 00:22:21,476 socialize that with Congress . And I 610 00:22:21,476 --> 00:22:23,476 think that , you know , by the next 611 00:22:23,476 --> 00:22:25,531 year we should be able to to be in a 612 00:22:25,531 --> 00:22:25,040 better position to have to have that 613 00:22:25,040 --> 00:22:26,984 come to fruition and along similar 614 00:22:26,984 --> 00:22:28,984 lines . You brought up the software 615 00:22:28,984 --> 00:22:31,151 acquisition pathway , which which d au 616 00:22:31,151 --> 00:22:33,318 has done a lot of work on , I'm trying 617 00:22:33,318 --> 00:22:35,540 to get the workforce ready to adopt , I 618 00:22:35,540 --> 00:22:37,651 think that has also been a little bit 619 00:22:37,651 --> 00:22:39,651 slow in terms of making its way out 620 00:22:39,651 --> 00:22:42,300 into implementation . Is that or do we 621 00:22:42,300 --> 00:22:44,480 know yet whether that is the obvious 622 00:22:44,480 --> 00:22:46,702 way to do software from now on ? Well , 623 00:22:46,702 --> 00:22:48,869 I think we have about 35 programs that 624 00:22:48,869 --> 00:22:50,924 are following that . Um and over the 625 00:22:50,924 --> 00:22:52,980 past year and a half , that's that's 626 00:22:52,980 --> 00:22:55,690 fairly remarkable in terms of shifting 627 00:22:55,690 --> 00:22:57,746 and not just saying it by name , but 628 00:22:57,746 --> 00:22:59,857 actually following that pathway and I 629 00:22:59,857 --> 00:23:02,079 think that this allows us opportunities 630 00:23:02,079 --> 00:23:04,190 to learn if we need to tweak , we can 631 00:23:04,190 --> 00:23:06,190 be able to do that . And that was a 632 00:23:06,190 --> 00:23:08,357 really nice thing about what how and S 633 00:23:08,357 --> 00:23:10,357 did the 5000 series where they were 634 00:23:10,357 --> 00:23:12,579 able to piece parted out so that if you 635 00:23:12,579 --> 00:23:14,579 have to make a change , you weren't 636 00:23:14,579 --> 00:23:16,690 changing the whole volume of the 5000 637 00:23:16,690 --> 00:23:16,680 series . It was one of those specific 638 00:23:16,680 --> 00:23:18,736 types of elements . And so I think , 639 00:23:18,736 --> 00:23:20,791 you know , um there's a lot we don't 640 00:23:20,791 --> 00:23:23,740 know , we have to actually do . And the 641 00:23:23,740 --> 00:23:25,796 nice thing is , is that we're out of 642 00:23:25,800 --> 00:23:29,380 the theoretical philosophical mode and 643 00:23:29,380 --> 00:23:31,547 we're actually doing , which will then 644 00:23:31,547 --> 00:23:33,713 inform and we can keep building upon . 645 00:23:33,713 --> 00:23:35,990 I'm gonna ask a dangerous sis oh 646 00:23:35,990 --> 00:23:37,990 related question again here and and 647 00:23:37,990 --> 00:23:40,157 we'll we'll see if you can tackle it , 648 00:23:40,157 --> 00:23:42,212 but but I think it's relevant to the 649 00:23:42,212 --> 00:23:44,020 whole accelerating technology 650 00:23:44,020 --> 00:23:46,370 development in the cloud piece . One of 651 00:23:46,370 --> 00:23:48,426 the things that I've heard more than 652 00:23:48,426 --> 00:23:51,130 once recently regarding RMF and the 653 00:23:51,130 --> 00:23:53,620 need for RMF reform is that even if you 654 00:23:53,620 --> 00:23:56,780 get an A T O for a cloud service 655 00:23:56,780 --> 00:23:59,300 offering , people feel like they've got 656 00:23:59,300 --> 00:24:01,600 to reauthorize it every single time 657 00:24:01,600 --> 00:24:03,822 they want to put a new service offering 658 00:24:03,822 --> 00:24:06,040 in that cloud environment , so why are 659 00:24:06,040 --> 00:24:08,151 we bothering in the first place ? And 660 00:24:08,151 --> 00:24:10,262 it and it that's another thing that I 661 00:24:10,262 --> 00:24:12,262 have heard really slows things just 662 00:24:12,262 --> 00:24:14,318 down , I can't tell if that's just a 663 00:24:14,318 --> 00:24:16,540 misapprehension of what the RMF process 664 00:24:16,540 --> 00:24:18,540 is supposed to be or if it's a real 665 00:24:18,540 --> 00:24:20,651 thing . Is that something that you're 666 00:24:20,651 --> 00:24:22,873 examining as part of this process and I 667 00:24:22,873 --> 00:24:24,984 think the continuous 80 oh piece also 668 00:24:24,984 --> 00:24:27,207 goes after that because as you're , you 669 00:24:27,207 --> 00:24:29,096 have an environment that has been 670 00:24:29,096 --> 00:24:31,207 certified or authority to operate and 671 00:24:31,207 --> 00:24:33,660 then as you add new services in , how 672 00:24:33,660 --> 00:24:35,827 do you go about ensuring that that new 673 00:24:35,827 --> 00:24:37,938 service doesn't impact or cause undue 674 00:24:37,938 --> 00:24:40,049 harm ? And that's what we were trying 675 00:24:40,049 --> 00:24:42,240 to do with the model of continuous 80 676 00:24:42,240 --> 00:24:44,670 oh , how can you continuously monitor , 677 00:24:45,140 --> 00:24:47,307 understand where their vulnerabilities 678 00:24:47,307 --> 00:24:49,362 and then quickly go about mitigating 679 00:24:49,362 --> 00:24:51,529 said vulnerabilities as opposed to how 680 00:24:51,529 --> 00:24:53,473 we have been doing RMF in the past 681 00:24:53,473 --> 00:24:55,584 where it was a static three year type 682 00:24:55,584 --> 00:24:57,910 thing . More compliance check the box . 683 00:24:57,920 --> 00:25:00,680 So we were really being placed in a 684 00:25:00,690 --> 00:25:03,860 less um secure cyber security posture 685 00:25:04,050 --> 00:25:06,680 in that manner . And so there's gonna 686 00:25:06,680 --> 00:25:08,902 be fits and starts with this too . This 687 00:25:08,902 --> 00:25:10,958 is something that's fairly brand new 688 00:25:10,958 --> 00:25:12,847 for the department and that's the 689 00:25:12,847 --> 00:25:15,124 reason why within the continuous A two , 690 00:25:15,124 --> 00:25:14,480 we wanted to make sure that there was 691 00:25:14,480 --> 00:25:16,536 an opportunity to be able to educate 692 00:25:16,536 --> 00:25:18,313 and ensure that the authorizing 693 00:25:18,313 --> 00:25:20,536 officials rise the tide for all because 694 00:25:20,536 --> 00:25:22,730 we recognize that this is new and we 695 00:25:22,730 --> 00:25:24,674 need to make sure that everyone is 696 00:25:24,674 --> 00:25:26,619 winning of how to do this and that 697 00:25:26,619 --> 00:25:28,841 we're going to have to constantly build 698 00:25:28,841 --> 00:25:30,952 upon it as you've already mentioned , 699 00:25:30,952 --> 00:25:33,008 really key to this whole strategy is 700 00:25:33,008 --> 00:25:32,620 bringing the R . N . D . The A . And S . 701 00:25:32,620 --> 00:25:35,030 And the Ceo communities together . Does 702 00:25:35,030 --> 00:25:38,320 that continue beyond this initial 180 703 00:25:38,320 --> 00:25:40,210 day implementation framework 704 00:25:40,220 --> 00:25:42,442 development process ? I mean , do there 705 00:25:42,442 --> 00:25:44,553 need to be ongoing permanent linkages 706 00:25:44,553 --> 00:25:46,553 between those three teams ? We have 707 00:25:46,553 --> 00:25:48,720 been working together for the past two 708 00:25:48,720 --> 00:25:50,442 years and really this software 709 00:25:50,442 --> 00:25:52,442 modernization strategy codifies the 710 00:25:52,442 --> 00:25:54,870 fact that these three organizations um 711 00:25:54,880 --> 00:25:56,880 are the facilitators or the leaders 712 00:25:56,880 --> 00:25:59,440 with uh for software modernization and 713 00:25:59,440 --> 00:26:01,607 that we're partnered with the Military 714 00:26:01,607 --> 00:26:03,718 Services , the Combatant commands and 715 00:26:03,718 --> 00:26:05,829 Fourth Estates to move the department 716 00:26:05,829 --> 00:26:08,170 um in this direction . Um so we will 717 00:26:08,180 --> 00:26:10,069 continue to do this . And I think 718 00:26:10,140 --> 00:26:13,220 what's really amazing to witness in the 719 00:26:13,220 --> 00:26:15,331 past years that we've been doing this 720 00:26:15,331 --> 00:26:17,387 is that there has been an incredible 721 00:26:17,387 --> 00:26:19,553 coalition of the willing from not only 722 00:26:19,553 --> 00:26:21,720 across those three organizations , but 723 00:26:21,720 --> 00:26:23,609 the military services and data is 724 00:26:23,609 --> 00:26:25,831 people who really want to have positive 725 00:26:25,831 --> 00:26:27,609 change . And so we were able to 726 00:26:27,609 --> 00:26:29,570 capitalize on that and do a lot of 727 00:26:29,580 --> 00:26:32,150 informal engagements with our deficit 728 00:26:32,150 --> 00:26:34,150 cops community of practice where we 729 00:26:34,150 --> 00:26:37,920 marry uh industry academia , the entire 730 00:26:37,920 --> 00:26:40,450 department together so we can have an 731 00:26:40,460 --> 00:26:42,627 open and safe space where we can share 732 00:26:42,627 --> 00:26:46,580 lessons learned uh um discuss 733 00:26:46,580 --> 00:26:48,650 about openly failures because 734 00:26:48,650 --> 00:26:51,240 inevitably we fail and how do we go 735 00:26:51,240 --> 00:26:53,540 about ensuring that we can learn from 736 00:26:53,540 --> 00:26:55,762 that and move forward . And so a lot of 737 00:26:55,762 --> 00:26:57,762 these activities we've been able to 738 00:26:57,762 --> 00:27:00,300 kind of bring together and now we're at 739 00:27:00,300 --> 00:27:02,522 the point where we formalized it within 740 00:27:02,522 --> 00:27:04,522 a strategy . So we've connected the 741 00:27:04,522 --> 00:27:06,633 department's leaders strategic vision 742 00:27:06,633 --> 00:27:08,689 to people who really want to make it 743 00:27:08,689 --> 00:27:10,744 happen . And I you rarely get to see 744 00:27:10,744 --> 00:27:12,856 that and be a part of that and that's 745 00:27:12,856 --> 00:27:14,856 where we are right now . So it's an 746 00:27:14,856 --> 00:27:16,633 incredible time to be um in the 747 00:27:16,633 --> 00:27:18,522 department working on the on this 748 00:27:18,522 --> 00:27:20,744 activity . Yeah . And you said this was 749 00:27:20,744 --> 00:27:22,522 socialized amongst the military 750 00:27:22,522 --> 00:27:24,078 departments and all the key 751 00:27:24,078 --> 00:27:25,911 stakeholders . Before the actual 752 00:27:25,911 --> 00:27:27,689 strategy comes out , those same 753 00:27:27,689 --> 00:27:29,578 stakeholders have a voice in this 754 00:27:29,578 --> 00:27:31,522 implementation roadmap that that's 755 00:27:31,522 --> 00:27:33,856 still needs to get written . Absolutely , 756 00:27:33,856 --> 00:27:35,980 certainly . And so we're using the 757 00:27:35,990 --> 00:27:37,768 software modernization , senior 758 00:27:37,768 --> 00:27:39,712 steering group . So I'm one of the 759 00:27:39,712 --> 00:27:42,660 chairs along with Phil Rogers from A 760 00:27:42,660 --> 00:27:45,050 and S . Stephanie Polson from our any 761 00:27:45,240 --> 00:27:48,770 and uh last month uh the team presented 762 00:27:48,770 --> 00:27:51,000 the outline the methodology of how we 763 00:27:51,000 --> 00:27:53,250 would go about um building the 764 00:27:53,250 --> 00:27:55,310 implementation plan and received 765 00:27:55,310 --> 00:27:57,610 approval from everyone . And we have uh 766 00:27:57,620 --> 00:28:00,370 an action officer working group that is 767 00:28:00,380 --> 00:28:03,640 under the uh the software modernization 768 00:28:03,640 --> 00:28:06,770 steering steering group that 50 members 769 00:28:06,770 --> 00:28:08,659 strong . They're the ones who are 770 00:28:08,659 --> 00:28:10,881 actually going to put pen to paper work 771 00:28:10,881 --> 00:28:10,750 this through . And there's 772 00:28:10,750 --> 00:28:12,917 representatives , the cross functional 773 00:28:12,917 --> 00:28:16,220 team depart from uh military 774 00:28:16,220 --> 00:28:19,190 departments , the Fourth Estate , um 775 00:28:19,200 --> 00:28:21,110 program , executive officers , 776 00:28:21,120 --> 00:28:24,350 operators , acquisition experts 777 00:28:24,350 --> 00:28:26,406 etcetera . So we really want to have 778 00:28:26,406 --> 00:28:28,572 that full complement because we really 779 00:28:28,572 --> 00:28:30,790 believe that this challenge is um is 780 00:28:30,790 --> 00:28:32,790 for all of us to solve not just one 781 00:28:32,790 --> 00:28:35,570 organization or or one skill set in our 782 00:28:35,570 --> 00:28:37,570 last 15 minutes here . I do want to 783 00:28:37,570 --> 00:28:39,792 loop back around to the first goal that 784 00:28:39,792 --> 00:28:41,903 we haven't talked about a ton , which 785 00:28:41,903 --> 00:28:44,014 is , as you put it accelerate the dut 786 00:28:44,014 --> 00:28:46,181 enterprise cloud environment . Part of 787 00:28:46,181 --> 00:28:48,237 that , I think in the strategy makes 788 00:28:48,237 --> 00:28:50,403 clear is going to be rationalizing the 789 00:28:50,403 --> 00:28:52,459 total number of cloud contracts that 790 00:28:52,459 --> 00:28:54,681 are out there , you know SD and diSA in 791 00:28:54,681 --> 00:28:56,681 the military services and coming up 792 00:28:56,681 --> 00:28:58,903 with a set of contracts that complement 793 00:28:58,903 --> 00:29:00,903 each other . And that makes sense . 794 00:29:00,903 --> 00:29:02,737 Certainly not asking you to pick 795 00:29:02,737 --> 00:29:04,681 winners and losers in front of the 796 00:29:04,681 --> 00:29:06,903 cameras right now . But can you walk us 797 00:29:06,903 --> 00:29:08,848 through sort of what the objective 798 00:29:08,848 --> 00:29:10,903 there is and what that process might 799 00:29:10,903 --> 00:29:12,903 look like and what questions you're 800 00:29:12,903 --> 00:29:12,430 going to be asking as you try to come 801 00:29:12,430 --> 00:29:14,790 up with a sensible portfolio in the 802 00:29:14,790 --> 00:29:17,050 coming years . Yeah , I think that um a 803 00:29:17,050 --> 00:29:19,050 lot of what we're trying to do with 804 00:29:19,050 --> 00:29:21,161 software modernization , particularly 805 00:29:21,161 --> 00:29:23,383 that digital infrastructure piece is to 806 00:29:23,383 --> 00:29:25,494 to go about enterprise services and a 807 00:29:25,494 --> 00:29:27,717 big one that we are trying to tackle is 808 00:29:27,717 --> 00:29:30,010 with our forthcoming joint warfighting 809 00:29:30,020 --> 00:29:32,350 cloud capability . And so this truly is 810 00:29:32,350 --> 00:29:34,572 going to be an enterprise cloud service 811 00:29:34,572 --> 00:29:36,950 for the entire department um that will 812 00:29:36,960 --> 00:29:39,700 provide the full complement of what is 813 00:29:39,700 --> 00:29:42,150 currently missing um in terms of 814 00:29:42,150 --> 00:29:44,261 requirements from unclassified to top 815 00:29:44,261 --> 00:29:46,920 secret to tactical edge um cloud 816 00:29:46,920 --> 00:29:49,198 infrastructure and associated services . 817 00:29:49,198 --> 00:29:52,090 Um right now the military departments 818 00:29:52,090 --> 00:29:53,970 have peace parts of what I just 819 00:29:53,970 --> 00:29:56,930 described for for themselves really . 820 00:29:56,930 --> 00:29:58,874 The combatant commands and Daffy's 821 00:29:58,874 --> 00:30:00,819 don't have access to that . And so 822 00:30:00,819 --> 00:30:02,930 there's this has been a struggle . So 823 00:30:02,930 --> 00:30:05,041 this isn't the urgent unmet need that 824 00:30:05,041 --> 00:30:07,208 we're working through with J W C . C . 825 00:30:07,208 --> 00:30:10,410 Um and so I think that it is not unlike 826 00:30:10,420 --> 00:30:12,620 um its predecessor , we're not 827 00:30:12,620 --> 00:30:15,220 mandating this . Um this really is 828 00:30:15,220 --> 00:30:18,240 access for all the focus is going to be 829 00:30:18,240 --> 00:30:20,129 the fourth estate . So when I say 830 00:30:20,129 --> 00:30:22,462 fourth Estates , the combatant commands , 831 00:30:22,462 --> 00:30:24,518 uh it's our defense agencies , field 832 00:30:24,518 --> 00:30:26,590 activities and um the osd components 833 00:30:26,590 --> 00:30:29,380 that are in the in the pentagon . Um as 834 00:30:29,390 --> 00:30:32,190 military services need uh um 835 00:30:32,200 --> 00:30:34,422 capabilities and and services that they 836 00:30:34,422 --> 00:30:36,644 don't have on their current contracts . 837 00:30:36,644 --> 00:30:38,811 They're absolutely able to use the J W 838 00:30:38,811 --> 00:30:41,150 C C as those individual uh , cloud 839 00:30:41,150 --> 00:30:44,860 contracts term expire , uh 840 00:30:45,540 --> 00:30:47,940 J W C C is available for use . They 841 00:30:47,940 --> 00:30:50,162 don't have to go out and do their own . 842 00:30:50,162 --> 00:30:52,384 So there is trade space and flexibility 843 00:30:52,384 --> 00:30:55,890 um to allow for an optimization of 844 00:30:55,890 --> 00:30:58,310 enterprise services . The J W C C will 845 00:30:58,310 --> 00:31:00,430 be for five years once it's awarded . 846 00:31:00,430 --> 00:31:02,880 So through your base , um to one year 847 00:31:02,880 --> 00:31:05,040 option years . And then the next big 848 00:31:05,040 --> 00:31:07,860 push at the department wants to do is a 849 00:31:07,870 --> 00:31:10,250 cloud market space . Um And so we will 850 00:31:10,250 --> 00:31:13,040 go after that as well . Way too early 851 00:31:13,040 --> 00:31:15,096 to get into a ton of detail and what 852 00:31:15,096 --> 00:31:17,429 that market marketplace might look like . 853 00:31:17,429 --> 00:31:19,373 But can you just give some initial 854 00:31:19,373 --> 00:31:21,096 ideas on how that would differ 855 00:31:21,096 --> 00:31:23,040 fundamentally from what J W C C is 856 00:31:23,040 --> 00:31:25,151 going to be ? Yeah , absolutely . The 857 00:31:25,151 --> 00:31:27,318 biggest differentiator is that for J W 858 00:31:27,318 --> 00:31:29,373 C C , we did direct solicitations to 859 00:31:29,373 --> 00:31:31,540 the cloud service providers . Um so we 860 00:31:31,540 --> 00:31:33,651 were very narrow in our scope because 861 00:31:33,651 --> 00:31:35,873 we wanted to be able to have capability 862 00:31:35,873 --> 00:31:37,984 quickly because we've had that urgent 863 00:31:37,984 --> 00:31:40,151 unmet need for the cloud marketplace . 864 00:31:40,151 --> 00:31:42,140 It would not be exclusive to cloud 865 00:31:42,140 --> 00:31:44,100 service providers , so integrators 866 00:31:44,110 --> 00:31:46,332 etcetera would be able to participate . 867 00:31:46,840 --> 00:31:49,007 Got it . Um , let's talk more about JW 868 00:31:49,007 --> 00:31:51,180 CC specifically , um , you've , you've 869 00:31:51,180 --> 00:31:53,402 given us some of the high level details 870 00:31:53,402 --> 00:31:55,458 about it so far . I think one of the 871 00:31:55,458 --> 00:31:57,680 most interesting bits that you guys are 872 00:31:57,680 --> 00:31:57,600 doing is how the task order selection 873 00:31:57,600 --> 00:31:59,767 process is gonna work . So just to set 874 00:31:59,767 --> 00:32:01,989 this up a little bit for folks , one of 875 00:32:01,989 --> 00:32:04,211 the ways this is different is that each 876 00:32:04,211 --> 00:32:06,156 of the hyper scale cloud computing 877 00:32:06,156 --> 00:32:08,378 vendors is going to get their own I D I 878 00:32:08,378 --> 00:32:10,544 Q . Contract I believe is the way it's 879 00:32:10,544 --> 00:32:12,600 going to work . And then task orders 880 00:32:12,600 --> 00:32:14,870 will be made on those individual 234 881 00:32:14,870 --> 00:32:16,759 contracts . I don't think we know 882 00:32:16,759 --> 00:32:18,870 exactly yet how many there's going to 883 00:32:18,870 --> 00:32:20,814 be at this point , but but talk us 884 00:32:20,814 --> 00:32:20,730 through how that sort of innovative 885 00:32:20,730 --> 00:32:23,810 task order award process is notionally 886 00:32:23,810 --> 00:32:25,900 gonna work . Yeah , I think the the 887 00:32:25,910 --> 00:32:28,450 struggle has always been is the fact 888 00:32:28,450 --> 00:32:30,710 that normally we do as you just 889 00:32:30,710 --> 00:32:33,210 described task order competition . It 890 00:32:33,210 --> 00:32:35,266 could take up to 45 days and that is 891 00:32:35,266 --> 00:32:38,330 unsatisfactory . And so the the team 892 00:32:38,330 --> 00:32:40,108 has been working really hard to 893 00:32:40,108 --> 00:32:43,030 absolutely streamline that and make it 894 00:32:43,040 --> 00:32:45,880 down to 5 to 10 days . And the way that 895 00:32:45,880 --> 00:32:47,602 they've gone about this is pre 896 00:32:47,602 --> 00:32:49,610 populating templates that the 897 00:32:49,610 --> 00:32:51,777 contracting officer will work with the 898 00:32:51,777 --> 00:32:53,888 mission partner to be able to fill in 899 00:32:53,888 --> 00:32:56,950 uh the host hosting and cloud computing 900 00:32:56,960 --> 00:33:00,720 offices , the program manager for 901 00:33:00,730 --> 00:33:03,130 uh for the J . W . C . C . So they will 902 00:33:03,130 --> 00:33:04,908 be the ones screens white glove 903 00:33:04,908 --> 00:33:06,852 treatment working with the mission 904 00:33:06,852 --> 00:33:08,797 partners to refine requirements to 905 00:33:08,797 --> 00:33:11,310 populate into um those pre populated 906 00:33:11,320 --> 00:33:14,860 templates . Uh that will kick off the 907 00:33:14,940 --> 00:33:18,500 the the task order initiation . 908 00:33:18,510 --> 00:33:20,732 Uh then we'll have to ask whether award 909 00:33:20,732 --> 00:33:22,899 and once we have to ask for a reward , 910 00:33:22,899 --> 00:33:25,121 the mission partner will be able to buy 911 00:33:25,121 --> 00:33:27,288 services through our tool called at at 912 00:33:27,288 --> 00:33:29,454 it's our provisioning tool . They will 913 00:33:29,454 --> 00:33:31,740 be able to monitor and and see uh 914 00:33:31,750 --> 00:33:33,820 services , their consumption rate 915 00:33:33,820 --> 00:33:36,170 etcetera . So that will be there portal 916 00:33:36,170 --> 00:33:38,530 into once it's been awarded , how 917 00:33:38,530 --> 00:33:41,170 they'll be able to manage um their 918 00:33:41,170 --> 00:33:43,059 their capabilities that they just 919 00:33:43,059 --> 00:33:45,700 purchased . Our vendor is going to have 920 00:33:45,710 --> 00:33:48,790 any sort of insight into maybe why a 921 00:33:48,790 --> 00:33:50,860 competitors project was chosen for a 922 00:33:50,860 --> 00:33:52,804 particular requirement and there's 923 00:33:52,804 --> 00:33:54,971 weren't because because it seems to me 924 00:33:54,971 --> 00:33:57,193 there's got to be some sort of feedback 925 00:33:57,193 --> 00:33:59,304 process of some kind so that they can 926 00:33:59,304 --> 00:34:01,416 continue improving their services and 927 00:34:01,416 --> 00:34:03,638 make them make sure they're as relevant 928 00:34:03,638 --> 00:34:05,527 as they possibly can be to duties 929 00:34:05,527 --> 00:34:07,304 requirements since they are not 930 00:34:07,304 --> 00:34:09,360 proactively responding to individual 931 00:34:09,360 --> 00:34:11,527 solicitations each time . This is kind 932 00:34:11,527 --> 00:34:13,582 of an automated process . Yes . So I 933 00:34:13,582 --> 00:34:15,693 think what it's going to come down to 934 00:34:15,693 --> 00:34:18,080 is are the services available um at the 935 00:34:18,080 --> 00:34:20,247 time where the mission partner needs a 936 00:34:20,247 --> 00:34:23,030 cost . And so those are going to be the 937 00:34:23,040 --> 00:34:25,207 two things that are going to drive the 938 00:34:25,207 --> 00:34:27,151 competition and there will be um a 939 00:34:27,151 --> 00:34:29,373 feedback loop in order for because it's 940 00:34:29,373 --> 00:34:31,610 a competition . So each of the CS PS 941 00:34:31,610 --> 00:34:34,200 that have those I . D . Iike us will be 942 00:34:34,200 --> 00:34:36,330 able to refine get better and if they 943 00:34:36,330 --> 00:34:38,330 have capabilities that aren't their 944 00:34:38,330 --> 00:34:40,552 work really hard to ensure that that is 945 00:34:40,552 --> 00:34:43,040 on in the catalog the next time . Um 946 00:34:43,050 --> 00:34:45,950 this comes up but the feedback process , 947 00:34:45,950 --> 00:34:48,050 is it going to be more than okay . I 948 00:34:48,050 --> 00:34:50,550 didn't I know I didn't win this one and 949 00:34:50,550 --> 00:34:53,110 company X did . Are there gonna be some 950 00:34:53,110 --> 00:34:55,250 kind of ongoing discussions or 951 00:34:55,250 --> 00:34:57,361 documentation passed back and forth ? 952 00:34:57,361 --> 00:34:59,361 Has any of that figured out yet ? I 953 00:34:59,361 --> 00:34:59,290 think we're still working through that 954 00:34:59,300 --> 00:35:02,390 piece . I mean right now we are in the 955 00:35:02,390 --> 00:35:04,168 process , we're actively in the 956 00:35:04,168 --> 00:35:06,410 acquisition process for J W . C . C . 957 00:35:06,410 --> 00:35:08,690 Reviewing the vendors proposals , we're 958 00:35:08,690 --> 00:35:11,070 gonna have to normalize um all those 959 00:35:11,070 --> 00:35:14,110 proposals um for the the to create the 960 00:35:14,110 --> 00:35:16,620 catalog and the price point . So I I do 961 00:35:16,620 --> 00:35:18,780 know we're thinking about that and I 962 00:35:18,780 --> 00:35:20,780 just don't have a very satisfactory 963 00:35:20,780 --> 00:35:22,836 answer . But those are things by the 964 00:35:22,836 --> 00:35:24,836 time the contracts are awarded , we 965 00:35:24,836 --> 00:35:27,002 will be able to have that and again um 966 00:35:27,002 --> 00:35:29,450 will continually refine and get better 967 00:35:29,450 --> 00:35:31,730 at this another area we haven't talked 968 00:35:31,730 --> 00:35:35,640 about a ton is workforce Talk about 969 00:35:35,640 --> 00:35:37,780 how a modernized software approach 970 00:35:37,780 --> 00:35:39,910 might impact the kind of skills you 971 00:35:39,910 --> 00:35:41,966 need , the number of people you need 972 00:35:41,966 --> 00:35:44,021 where those people are in five or 10 973 00:35:44,021 --> 00:35:46,930 years . So to me , workforce is 974 00:35:46,930 --> 00:35:49,650 absolutely critical if we had all the 975 00:35:49,650 --> 00:35:51,594 money in the world to buy the best 976 00:35:51,594 --> 00:35:53,372 technology and we had the right 977 00:35:53,372 --> 00:35:55,428 processes in place to be able to get 978 00:35:55,440 --> 00:35:58,060 the needed technology at the time of 979 00:35:58,060 --> 00:36:00,171 consumption for our workforce and our 980 00:36:00,171 --> 00:36:02,800 war fighter , but that workforce , our 981 00:36:02,800 --> 00:36:05,320 workforce , our work our warfighter do 982 00:36:05,320 --> 00:36:07,487 not know how to use that technology to 983 00:36:07,487 --> 00:36:09,598 be able to execute their mission . We 984 00:36:09,598 --> 00:36:12,100 failed . And so we really need to focus 985 00:36:12,100 --> 00:36:14,790 not only on the technology enablers , 986 00:36:14,800 --> 00:36:17,140 the business transformation needs to 987 00:36:17,140 --> 00:36:19,730 take place , but our workforce . And so 988 00:36:19,740 --> 00:36:22,180 the workforce piece is a key enabler in 989 00:36:22,180 --> 00:36:24,236 that business transformation that we 990 00:36:24,236 --> 00:36:26,513 have as part of software modernization . 991 00:36:26,513 --> 00:36:28,680 I think that you know , we are working 992 00:36:28,680 --> 00:36:31,160 on our strategy to be able to not only 993 00:36:31,160 --> 00:36:33,750 retain , cultivate and train our our 994 00:36:33,750 --> 00:36:36,520 current workforce and it goes beyond 995 00:36:36,520 --> 00:36:38,576 just those who are actually hands on 996 00:36:38,576 --> 00:36:41,900 keyboard . So to say those scientists , 997 00:36:41,900 --> 00:36:44,011 those engineers that are working with 998 00:36:44,011 --> 00:36:45,844 software factories , the program 999 00:36:45,844 --> 00:36:48,122 managers that are responsible for this , 1000 00:36:48,122 --> 00:36:50,289 that's the entire workforce that needs 1001 00:36:50,289 --> 00:36:52,344 to be digitally literate . Um and so 1002 00:36:52,344 --> 00:36:54,456 that that's part of the strategy that 1003 00:36:54,456 --> 00:36:56,678 we're working on and towards to be able 1004 00:36:56,678 --> 00:36:58,789 to do that . And the other thing I'll 1005 00:36:58,789 --> 00:37:00,900 offer is there's always going to be a 1006 00:37:00,900 --> 00:37:02,900 focus on stem , but we also need to 1007 00:37:02,900 --> 00:37:04,733 broaden that aperture as well to 1008 00:37:04,733 --> 00:37:06,733 recognize that we need to recruit a 1009 00:37:06,733 --> 00:37:08,567 different skill set to allow for 1010 00:37:08,567 --> 00:37:12,220 diversity of thought . Um and uh the 1011 00:37:12,220 --> 00:37:14,550 ability to be innovative and to see see 1012 00:37:14,550 --> 00:37:16,439 things differently and talk about 1013 00:37:16,439 --> 00:37:18,606 things differently in order to push us 1014 00:37:18,606 --> 00:37:20,550 Even further and harder . I have a 1015 00:37:20,550 --> 00:37:22,717 bachelor's of arts , political science 1016 00:37:22,717 --> 00:37:24,661 and I've been in this field for 15 1017 00:37:24,661 --> 00:37:26,717 years and I think my contribution is 1018 00:37:26,717 --> 00:37:28,772 the fact that I can be strategic , I 1019 00:37:28,772 --> 00:37:30,717 think a little bit differently and 1020 00:37:30,717 --> 00:37:33,050 always want to learn . And so uh that's , 1021 00:37:33,050 --> 00:37:35,106 we shouldn't limit ourselves to just 1022 00:37:35,106 --> 00:37:37,161 having just stem . So I think that's 1023 00:37:37,161 --> 00:37:36,960 also part of the conversation that 1024 00:37:36,960 --> 00:37:38,682 we're doing to get our digital 1025 00:37:38,682 --> 00:37:41,390 warfighters and workforce up to to 1026 00:37:41,400 --> 00:37:43,567 where we need them to be . And there's 1027 00:37:43,567 --> 00:37:45,680 so many moving parts in that bucket 1028 00:37:45,680 --> 00:37:47,736 that we call workforce , there's the 1029 00:37:47,736 --> 00:37:49,736 military workforce , the contractor 1030 00:37:49,736 --> 00:37:51,902 workforce , the civilian workforce and 1031 00:37:51,902 --> 00:37:54,013 it almost seems like you need to pull 1032 00:37:54,013 --> 00:37:56,124 PNR into this triad that you have now 1033 00:37:56,124 --> 00:37:58,124 to start talking about how software 1034 00:37:58,124 --> 00:38:00,180 modernization actually works right ? 1035 00:38:00,180 --> 00:38:01,902 And and PNR has been an active 1036 00:38:01,902 --> 00:38:03,680 participant within our software 1037 00:38:03,680 --> 00:38:05,902 modernization , senior steering group . 1038 00:38:05,902 --> 00:38:08,124 Um and so we've been leaning on them to 1039 00:38:08,124 --> 00:38:10,291 um their partnership with A and S . Um 1040 00:38:10,291 --> 00:38:12,860 and so like I said , it is a whole of 1041 00:38:12,860 --> 00:38:14,870 government to make this work to 1042 00:38:14,870 --> 00:38:17,610 transform how we go about doing things 1043 00:38:17,610 --> 00:38:19,666 better and quite frankly differently 1044 00:38:19,666 --> 00:38:22,230 than how we have been in the past . And 1045 00:38:22,230 --> 00:38:24,230 and one other area I wanted to make 1046 00:38:24,230 --> 00:38:26,230 sure we got to before we run out of 1047 00:38:26,230 --> 00:38:28,286 time here is what what's the current 1048 00:38:28,286 --> 00:38:30,452 thinking on how I . T . Infrastructure 1049 00:38:30,452 --> 00:38:32,620 and cloud , including cloud works in 1050 00:38:32,620 --> 00:38:34,564 the outside the continental United 1051 00:38:34,564 --> 00:38:36,676 States . O'Connor's environment . You 1052 00:38:36,676 --> 00:38:38,676 guys published a formal strategy on 1053 00:38:38,676 --> 00:38:40,898 O'Connor's cloud , I want to say a year 1054 00:38:40,898 --> 00:38:42,953 and a half , two years ago now . How 1055 00:38:42,953 --> 00:38:45,009 much has that thinking changed if at 1056 00:38:45,009 --> 00:38:44,450 all , that was still kind of in the 1057 00:38:44,450 --> 00:38:47,010 Jedi um time period when that that all 1058 00:38:47,010 --> 00:38:49,010 came together . And we've also been 1059 00:38:49,010 --> 00:38:50,788 hearing more , I think from the 1060 00:38:50,788 --> 00:38:53,500 services that they are , their thinking 1061 00:38:53,500 --> 00:38:55,556 has changed in a way that makes them 1062 00:38:55,556 --> 00:38:57,556 think they're going to need more on 1063 00:38:57,556 --> 00:38:59,500 prem of their own in the O'Connors 1064 00:38:59,500 --> 00:39:01,222 environment , what's the d O D 1065 00:39:01,222 --> 00:39:03,167 perspective on all of that at this 1066 00:39:03,167 --> 00:39:05,056 point ? Yeah . So I think that we 1067 00:39:05,056 --> 00:39:07,056 recently published Roku bonus cloud 1068 00:39:07,056 --> 00:39:09,167 strategy , which is a companion piece 1069 00:39:09,167 --> 00:39:11,278 to what was the duty cloud strategy . 1070 00:39:11,278 --> 00:39:13,444 So that was just published in april of 1071 00:39:13,444 --> 00:39:15,167 last year . And so that was in 1072 00:39:15,167 --> 00:39:17,333 partnership and recognition the Quebec 1073 00:39:17,333 --> 00:39:19,389 commands came through joint staff to 1074 00:39:19,389 --> 00:39:21,780 osd saying we don't have cloud , we 1075 00:39:21,780 --> 00:39:23,920 don't have access to cloud , um , the 1076 00:39:23,920 --> 00:39:26,650 critical infrastructure to allow for um 1077 00:39:26,650 --> 00:39:28,640 cloud to work just isn't there 1078 00:39:28,650 --> 00:39:30,817 everything's being back hold to to the 1079 00:39:30,817 --> 00:39:32,928 United States and we can't , we can't 1080 00:39:32,928 --> 00:39:35,230 execute our mission . And so we uh 1081 00:39:35,240 --> 00:39:38,280 articulate a very bold vision with the 1082 00:39:38,280 --> 00:39:41,860 Oakland A's cloud strategy and what the 1083 00:39:41,860 --> 00:39:43,860 J W C C is going to afford us to be 1084 00:39:43,860 --> 00:39:45,916 able to have that infrastructure and 1085 00:39:45,916 --> 00:39:47,804 cloud services to do that . We're 1086 00:39:47,804 --> 00:39:49,638 partnered with the cloud service 1087 00:39:49,638 --> 00:39:51,638 providers . They were uh as well as 1088 00:39:51,638 --> 00:39:53,693 industry , they were instrumental in 1089 00:39:53,693 --> 00:39:55,916 terms of devising this old plan that we 1090 00:39:55,916 --> 00:39:58,190 came out with with the strategy as you 1091 00:39:58,190 --> 00:40:00,357 mentioned in the military services are 1092 00:40:00,357 --> 00:40:02,579 moving forward . But what we don't want 1093 00:40:02,579 --> 00:40:04,690 to have happen is for each of them to 1094 00:40:04,690 --> 00:40:06,690 kind of strike out on their own and 1095 00:40:06,690 --> 00:40:08,523 figure things out for themselves 1096 00:40:08,523 --> 00:40:10,246 without taking a step back and 1097 00:40:10,246 --> 00:40:12,023 recognizing there are some core 1098 00:40:12,023 --> 00:40:14,190 enterprise services that we can have , 1099 00:40:14,190 --> 00:40:16,246 that would be foundational . Um even 1100 00:40:16,246 --> 00:40:18,412 when we're talking about pushing cloud 1101 00:40:18,412 --> 00:40:20,920 compute to the edge and then allow for 1102 00:40:20,920 --> 00:40:23,087 them for that last mile to springboard 1103 00:40:23,087 --> 00:40:25,087 off for their very specific service 1104 00:40:25,087 --> 00:40:27,330 specific mission . And so if you think 1105 00:40:27,330 --> 00:40:29,930 about some of the duplication that 1106 00:40:29,930 --> 00:40:32,110 could occur if we didn't follow that 1107 00:40:32,110 --> 00:40:35,880 model , I can , solutions , networking , 1108 00:40:35,890 --> 00:40:39,830 um , encryption , mechanisms , all 1109 00:40:39,830 --> 00:40:41,680 of that would be vying with for 1110 00:40:41,680 --> 00:40:43,402 precious resources and already 1111 00:40:43,402 --> 00:40:45,402 constrained environment . And so we 1112 00:40:45,402 --> 00:40:47,624 really want to come up with a way to be 1113 00:40:47,624 --> 00:40:49,690 able to standardize that or provide 1114 00:40:49,690 --> 00:40:52,830 some commonality so that each service 1115 00:40:52,840 --> 00:40:55,740 isn't going about that for themselves . 1116 00:40:56,110 --> 00:40:59,420 Um , and so that's what we're trying . 1117 00:40:59,420 --> 00:41:02,690 The D O D C I O is advocating for these 1118 00:41:02,690 --> 00:41:05,380 common enterprise services . We have 1119 00:41:05,380 --> 00:41:07,491 this concept called Joint Operational 1120 00:41:07,491 --> 00:41:09,491 Edge . It's just that the concept , 1121 00:41:09,491 --> 00:41:12,030 we're working through our um , the 1122 00:41:12,030 --> 00:41:13,808 working groups that I've , I've 1123 00:41:13,808 --> 00:41:15,419 mentioned under the software 1124 00:41:15,419 --> 00:41:17,363 modernization steering group , the 1125 00:41:17,363 --> 00:41:19,419 Action Officer , we have an Oak Onus 1126 00:41:19,419 --> 00:41:21,770 working group that has participation 1127 00:41:21,770 --> 00:41:23,714 from the military services and the 1128 00:41:23,714 --> 00:41:25,937 combatant commands to really flesh that 1129 00:41:25,937 --> 00:41:27,850 out and try to figure out what is 1130 00:41:27,850 --> 00:41:30,070 common and then have a delineation of 1131 00:41:30,070 --> 00:41:32,126 what would be the responsibility for 1132 00:41:32,126 --> 00:41:34,292 the services . So , but to some degree 1133 00:41:34,292 --> 00:41:36,390 there will be D O D , joint provided 1134 00:41:36,390 --> 00:41:38,557 services , no kidding . All the way to 1135 00:41:38,557 --> 00:41:40,390 the Edge , not just back at some 1136 00:41:40,390 --> 00:41:42,390 regional hub node , that is what we 1137 00:41:42,390 --> 00:41:44,168 want . And so that's what we're 1138 00:41:44,168 --> 00:41:46,112 advocating for . And so that's the 1139 00:41:46,112 --> 00:41:48,223 initial concept , um , you know , the 1140 00:41:48,223 --> 00:41:47,730 department is very much consistent 1141 00:41:47,740 --> 00:41:50,100 driven and so it is ensuring that we're 1142 00:41:50,100 --> 00:41:52,460 working with our stakeholders um , to 1143 00:41:52,460 --> 00:41:54,990 get a plan , not only a strategy , but 1144 00:41:54,990 --> 00:41:57,157 an executed plan in order to do that , 1145 00:41:57,157 --> 00:41:59,379 we need to have their buy in and we can 1146 00:41:59,379 --> 00:42:01,712 work with him on that . So we're in the , 1147 00:42:01,712 --> 00:42:03,934 in the early stages for that , but from 1148 00:42:03,934 --> 00:42:06,101 my personal perspective , that's where 1149 00:42:06,101 --> 00:42:08,510 I want to lead us towards maybe maybe 1150 00:42:08,510 --> 00:42:10,621 too early to answer any of this . But 1151 00:42:10,621 --> 00:42:12,720 what what sort of things are in play 1152 00:42:12,720 --> 00:42:15,160 that could or could not be provided at 1153 00:42:15,170 --> 00:42:17,480 the edge as an enterprise service . And 1154 00:42:17,480 --> 00:42:19,980 and I frankly still have my hard time 1155 00:42:19,980 --> 00:42:22,036 wrapping my mind around what a cloud 1156 00:42:22,036 --> 00:42:24,258 looks like on an actual battlefield . I 1157 00:42:24,258 --> 00:42:26,730 know , and so I think that because um 1158 00:42:26,800 --> 00:42:28,356 when you think about like a 1159 00:42:28,356 --> 00:42:30,630 disconnected or limited network uh 1160 00:42:30,640 --> 00:42:33,430 connectivity , um a lot of it comes 1161 00:42:33,430 --> 00:42:35,652 down to that critical infrastructure of 1162 00:42:35,652 --> 00:42:37,763 of your network . So that's thing one 1163 00:42:37,763 --> 00:42:39,930 thing two is where are we putting what 1164 00:42:39,930 --> 00:42:41,874 I'll call the next generation , um 1165 00:42:41,874 --> 00:42:44,390 regional data centers , um and 1166 00:42:44,390 --> 00:42:46,501 O'connells and partnering potentially 1167 00:42:46,501 --> 00:42:48,668 with a cloud service provider that has 1168 00:42:48,668 --> 00:42:50,890 a data center , they're working through 1169 00:42:50,890 --> 00:42:53,057 that . So there's a lot that has to be 1170 00:42:53,057 --> 00:42:55,112 unpacked , there's a lot of legal um 1171 00:42:55,112 --> 00:42:57,780 policy regulations that are driving us 1172 00:42:57,780 --> 00:43:01,190 to be uh a certain posture , but we are 1173 00:43:01,190 --> 00:43:03,412 working through those now to see what's 1174 00:43:03,412 --> 00:43:05,634 in the realm of possible . And then you 1175 00:43:05,634 --> 00:43:08,480 also have um these portable uh type 1176 00:43:08,490 --> 00:43:12,220 devices like AWS , a snowball that um 1177 00:43:12,600 --> 00:43:15,960 can be used um uh more 1178 00:43:15,960 --> 00:43:17,682 downrange . And so it's really 1179 00:43:17,682 --> 00:43:19,738 threading the needle for all of that 1180 00:43:19,738 --> 00:43:21,571 and making sure that we have the 1181 00:43:21,571 --> 00:43:23,793 infrastructure in place to to push that 1182 00:43:23,793 --> 00:43:25,849 to the edge and then the around that 1183 00:43:25,849 --> 00:43:28,040 piece out once we've done all that we 1184 00:43:28,040 --> 00:43:30,262 need to make sure that the war fighters 1185 00:43:30,262 --> 00:43:32,318 that are at the edge are able to use 1186 00:43:32,318 --> 00:43:34,262 the capabilities and so we need to 1187 00:43:34,262 --> 00:43:36,207 constantly have that plan in place 1188 00:43:36,207 --> 00:43:38,373 where we're educating in ensuring that 1189 00:43:38,373 --> 00:43:40,540 we have the right skilling for them to 1190 00:43:40,540 --> 00:43:42,651 be able to take full advantage of the 1191 00:43:42,651 --> 00:43:44,762 technology to execute their mission . 1192 00:43:44,762 --> 00:43:46,984 You just brought up identity and I want 1193 00:43:46,984 --> 00:43:46,670 to make sure we get to that in our last 1194 00:43:46,670 --> 00:43:48,837 couple of minutes . Can you just say a 1195 00:43:48,837 --> 00:43:50,892 bit about how central that is to the 1196 00:43:50,892 --> 00:43:53,003 whole software modernization strategy 1197 00:43:53,003 --> 00:43:55,226 working and does it need to be a common 1198 00:43:55,226 --> 00:43:57,448 enterprise service ? I believe it needs 1199 00:43:57,448 --> 00:44:00,110 to be a common enterprise service . I 1200 00:44:00,110 --> 00:44:02,332 think it's just because how else are we 1201 00:44:02,332 --> 00:44:04,388 going to be joined ? How else are we 1202 00:44:04,388 --> 00:44:06,721 going to be able to achieve some of the , 1203 00:44:06,721 --> 00:44:08,777 the , the goal , the stated goals of 1204 00:44:08,777 --> 00:44:10,832 joint all Domain C two . Um and so I 1205 00:44:10,832 --> 00:44:14,780 think for having I cam um be a central 1206 00:44:14,780 --> 00:44:17,002 enterprise place and then being able to 1207 00:44:17,002 --> 00:44:20,690 work from that is to me a linchpin , 1208 00:44:20,690 --> 00:44:22,190 not only just for software 1209 00:44:22,190 --> 00:44:24,301 modernization , but for the work that 1210 00:44:24,301 --> 00:44:26,468 we're trying to do with our zero Trust 1211 00:44:26,468 --> 00:44:28,579 principles too . We're good . Um that 1212 00:44:28,579 --> 00:44:30,746 is a great place to leave it . I think 1213 00:44:30,746 --> 00:44:32,968 we are going to have to say goodbye and 1214 00:44:32,968 --> 00:44:32,680 I appreciate you taking the time this 1215 00:44:32,680 --> 00:44:34,680 mets . This has been a great way to 1216 00:44:34,680 --> 00:44:36,791 kick off our D O D cloud exchange for 1217 00:44:36,791 --> 00:44:39,013 2022 . Thanks for doing it . Absolutely 1218 00:44:39,013 --> 00:44:41,069 my pleasure . Thank you . And we are 1219 00:44:41,069 --> 00:44:43,291 just getting started for the 2022 D O . 1220 00:44:43,291 --> 00:44:43,280 D . Cloud Exchange later in the week , 1221 00:44:43,280 --> 00:44:45,447 you're going to hear perspectives from 1222 00:44:45,447 --> 00:44:47,391 other D . O . D . Leaders on their 1223 00:44:47,391 --> 00:44:49,558 consumption of cloud computing . Later 1224 00:44:49,558 --> 00:44:51,780 today , you'll hear from paul Puckett , 1225 00:44:51,780 --> 00:44:51,320 the director of the Army Enterprise 1226 00:44:51,320 --> 00:44:53,660 Cloud Management Agency . First of all , 1227 00:44:53,660 --> 00:44:55,438 we're going to transition to an 1228 00:44:55,438 --> 00:44:57,493 industry perspective . Derek pledger 1229 00:44:57,493 --> 00:44:59,660 from Lighthouse is going to join us to 1230 00:44:59,660 --> 00:45:01,827 talk about some of the unique benefits 1231 00:45:01,827 --> 00:45:04,049 of multi cloud strategy can provide D . 1232 00:45:04,049 --> 00:45:06,104 O . D and the military services . My 1233 00:45:06,104 --> 00:45:05,960 colleague , Jason Miller , has the lead 1234 00:45:05,960 --> 00:45:07,960 for that conversation and now we'll 1235 00:45:07,960 --> 00:45:08,780 toss it over to Jason .