WEBVTT 00:01.040 --> 00:04.820 Good morning A USa Welcome to 00:04.820 --> 00:07.710 Warriors Corner Day one . Our first 00:07.710 --> 00:11.060 presenters topic is by soldiers for 00:11.060 --> 00:13.510 soldiers building an organic soldier 00:13.510 --> 00:15.732 lead software development capability in 00:15.732 --> 00:18.040 the army presenters include Lieutenant 00:18.040 --> 00:20.262 Colonel veto . Eriko , Director of Army 00:20.262 --> 00:22.596 Software factory . Army Futures Command , 00:23.140 --> 00:24.980 First Lieutenant Michael David , 00:25.330 --> 00:29.250 Military Project Product Manager , 00:29.640 --> 00:32.740 First Lieutenant Ammand Shaw . Military 00:32.750 --> 00:34.980 application Engineer and staff Sergeant 00:34.980 --> 00:37.190 chris paulie , military platform 00:37.200 --> 00:38.200 engineer . 00:42.540 --> 00:44.262 Hey , good morning everybody . 00:44.262 --> 00:46.207 Everybody hear me okay . Alright , 00:46.440 --> 00:50.030 first of all , thank you for joining us 00:50.040 --> 00:52.670 for the inaugural Warriors Corner 00:52.850 --> 00:55.210 presentation . It's an absolute honor . 00:55.210 --> 00:57.377 It appeared to be representing General 00:57.377 --> 00:59.432 Murray and Sergeant Major Crosby and 00:59.432 --> 01:01.599 all of the army futures command team . 01:01.599 --> 01:03.821 Some of you might be wondering what the 01:03.821 --> 01:06.043 army software factory is and we're here 01:06.043 --> 01:07.988 to talk about that as we do that I 01:07.988 --> 01:07.780 would ask you to think about and 01:07.780 --> 01:10.680 consider two questions as we talk about 01:10.690 --> 01:13.090 everything that the software factory um 01:13.100 --> 01:15.100 potentially provides the army . The 01:15.100 --> 01:18.060 first one How to industrial age 01:18.440 --> 01:21.110 organizations up skill and re skill 01:21.110 --> 01:22.850 their talent to dominate in an 01:22.850 --> 01:25.260 information age . The second question , 01:25.640 --> 01:28.360 how does the army prepare its soldiers 01:28.740 --> 01:30.796 for a future operating environment ? 01:31.020 --> 01:33.187 That's going to ask commanders to make 01:33.187 --> 01:35.450 better and faster decisions among an 01:35.450 --> 01:37.561 increasing amount of data streams and 01:37.561 --> 01:39.510 information flows . That's what we 01:39.510 --> 01:41.566 think the software factory . Does it 01:41.566 --> 01:43.677 answer those two questions . Let's go 01:43.677 --> 01:45.899 to the first time . Some of you , maybe 01:45.899 --> 01:48.010 you wonder where did this come from ? 01:48.010 --> 01:50.121 Uh it comes from ? Like the secretary 01:50.121 --> 01:52.177 talked about during her keynote , an 01:52.177 --> 01:54.343 incredible amount of analysis . Uh not 01:54.343 --> 01:54.300 by the army or not Buy futures . 01:54.300 --> 01:57.450 Command . um but by multiple bipartisan 01:57.450 --> 01:59.672 non part of partisan groups from across 01:59.672 --> 02:01.728 the federal government , Integrating 02:01.728 --> 02:03.894 software engineers and data scientists 02:03.894 --> 02:05.894 to the leading edge should not be a 02:05.894 --> 02:08.950 controversial issue in 2021 . How about 02:08.950 --> 02:11.960 the next slide ? What does it mean for 02:11.960 --> 02:14.140 the army ? Well , like we kind of 02:14.140 --> 02:16.230 talked about as commanders face an 02:16.230 --> 02:18.410 increasing amount of data streams to 02:18.410 --> 02:20.600 make decisions at the nipper sipper J 02:20.600 --> 02:22.822 Wickes and commercial internet levels . 02:23.140 --> 02:25.029 Somebody's got to be at that last 02:25.029 --> 02:27.251 tactical mile to make sense of all that 02:27.251 --> 02:29.362 information . We're not so sure we're 02:29.362 --> 02:31.251 gonna be able to move contractors 02:31.251 --> 02:33.473 around the battlefields in the same way 02:33.473 --> 02:33.220 that we were able to do so in Iraq and 02:33.220 --> 02:35.720 Afghanistan and we certainly think in 02:35.720 --> 02:37.831 the age , in the information age it's 02:37.831 --> 02:40.180 time to start investing in soldiers who 02:40.180 --> 02:43.240 have the skill sets already . Let's go 02:43.240 --> 02:44.296 to the next line . 02:47.040 --> 02:49.350 Ultimately , the army software factory 02:49.640 --> 02:51.529 nested with the chief information 02:51.529 --> 02:53.696 officer of the army and the enterprise 02:53.696 --> 02:55.450 cloud management agency of the 02:55.460 --> 02:58.420 underneath the C . I . O . Is about how 02:58.420 --> 03:00.150 do you produce an autonomous 03:00.160 --> 03:02.670 application or product team that's 03:02.670 --> 03:04.960 capable of prototyping , developing and 03:04.960 --> 03:07.016 getting a solution on an operational 03:07.016 --> 03:09.182 network at the edge of the battlefield 03:09.340 --> 03:11.507 that we can't prepare them to do . Now 03:11.507 --> 03:13.507 we don't know what commanders might 03:13.507 --> 03:15.562 need them to do . So we've got we've 03:15.562 --> 03:17.729 got essentially plan for ambiguity and 03:17.729 --> 03:19.562 plan for unpredictability and by 03:19.562 --> 03:21.396 investing in this competence for 03:21.396 --> 03:23.507 soldiers . Now we can begin to invest 03:23.507 --> 03:26.190 in the future . At the end of the day , 03:26.200 --> 03:29.980 we all kind of see one off solutions 03:29.980 --> 03:32.091 that get built across the army . Both 03:32.091 --> 03:34.258 the software factory is about doing is 03:34.258 --> 03:36.147 building an enduring and scalable 03:36.147 --> 03:38.380 capability for soldiers across the army 03:38.380 --> 03:41.030 again . Well , necid with H . P . D . A . 03:41.110 --> 03:43.221 With the chief information officer of 03:43.221 --> 03:45.388 the army and with the enterprise cloud 03:45.388 --> 03:47.388 management agency . Let's go to the 03:47.388 --> 03:51.230 next one . So what's so special 03:51.240 --> 03:54.820 about upscaling and re scaling a 03:54.820 --> 03:56.931 workforce for the information agent ? 03:56.931 --> 03:59.100 How do we do it ? Well , we had this 03:59.100 --> 04:01.280 idea that there's probably a lot of 04:01.280 --> 04:03.690 software development talent in the army 04:03.690 --> 04:05.690 that the army didn't realize it has 04:05.840 --> 04:07.951 this morning , the secretary talked a 04:07.951 --> 04:10.118 little bit about the race for talent . 04:10.118 --> 04:12.340 We're a big part of that . We thought , 04:12.340 --> 04:14.062 let's start doing some soldier 04:14.062 --> 04:16.284 interviews and seeing how many soldiers 04:16.284 --> 04:18.562 across the army would be interested in . 04:18.562 --> 04:20.729 Agile dep , sec , ops , agile software 04:20.729 --> 04:22.896 development platform engineering , all 04:22.896 --> 04:24.562 these sort of not so emerging 04:24.562 --> 04:26.618 technologies that Silicon Valley and 04:26.618 --> 04:28.729 private industry have sort of figured 04:28.729 --> 04:28.230 out that the army needs to begin 04:28.230 --> 04:30.660 investing in a big way . And you might 04:30.660 --> 04:33.990 not be surprised to realize That we 04:34.000 --> 04:36.167 after about 3000 soldier touchpoints , 04:36.167 --> 04:38.167 we discovered a completely untapped 04:38.167 --> 04:41.810 market of soldier talent . And it was 04:41.810 --> 04:43.977 abundantly clear to army leadership at 04:43.977 --> 04:45.810 that point that the army had an 04:45.810 --> 04:47.977 opportunity here to put that talent to 04:47.977 --> 04:50.143 work and um , we've got some of them , 04:50.143 --> 04:52.199 they're going to be talking a little 04:52.199 --> 04:54.366 bit later after I'm done . But you can 04:54.366 --> 04:56.199 imagine where should the army be 04:56.199 --> 04:58.199 investing some talent when it comes 04:58.199 --> 05:00.510 time to the choice of truck driver or 05:00.510 --> 05:02.566 software developer , combat medic or 05:02.566 --> 05:04.510 platform engineer . We've got such 05:04.510 --> 05:06.780 amazing talent in the army that can be 05:06.780 --> 05:08.947 re scaled , that's mislabeled , that's 05:08.947 --> 05:11.080 underutilized that we can put towards 05:11.080 --> 05:13.590 emerging technology skill sets . So 05:13.590 --> 05:15.812 what we do is , uh , we've been getting 05:15.812 --> 05:18.520 about 250-350 fully qualified 05:18.520 --> 05:21.120 applications every six months . We 05:21.120 --> 05:23.650 assemble a cohort of soldiers , uh , 05:23.650 --> 05:25.706 and put them towards lines of effort 05:25.706 --> 05:27.928 like product management , user design , 05:27.928 --> 05:30.100 application engineering , platform 05:30.100 --> 05:32.300 engineering . And we , and we baseline 05:32.300 --> 05:35.270 their skill sets . We choose about 25 05:35.270 --> 05:36.881 of them to be a part of five 05:36.881 --> 05:39.770 application teams , uh , in a sort of a 05:39.780 --> 05:43.360 paste bi annual process . Once they get 05:43.360 --> 05:45.471 that technical accelerator , we bring 05:45.471 --> 05:47.582 them in and we pair them with Silicon 05:47.582 --> 05:49.693 Valley experts . Not so that they can 05:49.693 --> 05:51.916 hold their own expertise , but they can 05:51.916 --> 05:53.860 begin to learn to how to work as a 05:53.860 --> 05:56.082 Silicon Valley product team , just like 05:56.082 --> 05:55.900 we might see in some of our favorite 05:55.900 --> 05:58.850 Silicon Valley companies , but really 05:59.240 --> 06:01.351 it's the teamwork , it's learning how 06:01.351 --> 06:03.240 to prototype a solution that they 06:03.240 --> 06:06.600 weren't handed and prescribed the exact 06:06.610 --> 06:08.840 answers ahead of time . It's again , 06:08.840 --> 06:11.062 it's that planning for ambiguity factor 06:11.440 --> 06:13.780 at the same time , We're teaching them 06:13.780 --> 06:15.447 how to build for a production 06:15.447 --> 06:17.669 environment . And that gets back to our 06:17.669 --> 06:19.836 relationship with the as we co develop 06:19.836 --> 06:22.058 our platform with the Chief information 06:22.058 --> 06:23.891 officer and the enterprise cloud 06:23.891 --> 06:26.058 management agency by teaching them how 06:26.058 --> 06:28.350 to build for production . We sort of 06:28.360 --> 06:30.416 underwrite a lot of the risk that we 06:30.416 --> 06:32.638 see going on across industry and across 06:32.638 --> 06:35.240 the army and how to build a deficit 06:35.240 --> 06:37.580 cops capability that that has yet to 06:37.580 --> 06:40.650 really be um championed . We're going 06:40.650 --> 06:42.706 to hear a little bit more about that 06:42.706 --> 06:44.928 afterwards . So the whole idea then now 06:44.928 --> 06:46.872 you've got about a year's worth of 06:46.872 --> 06:48.928 experience in a variety of different 06:48.928 --> 06:50.872 ways is now you have these , these 06:50.872 --> 06:53.094 soldiers that can then in turn and turn 06:53.094 --> 06:52.820 around and train the soldiers that come 06:52.820 --> 06:54.760 after them . So again , every six 06:54.760 --> 06:56.927 months , it gives us this cohort model 06:56.927 --> 06:58.927 that allows us to sort of like like 06:58.927 --> 07:00.927 agile software development to build 07:00.927 --> 07:02.649 measure and learn . That's the 07:02.649 --> 07:04.871 fundamental idea here is how do we grow 07:04.871 --> 07:06.927 this in a self sustaining way ? Um , 07:06.940 --> 07:09.162 that's that's sort of the special sauce 07:09.162 --> 07:11.496 there and you get an idea for , for how , 07:11.496 --> 07:13.496 how much across the whole army that 07:13.496 --> 07:15.718 were really pulling . Um , a variety of 07:15.718 --> 07:17.829 mos is a variety of ranks . We didn't 07:17.829 --> 07:20.051 really care and this is key , We didn't 07:20.051 --> 07:22.273 really care what rank you were or where 07:22.273 --> 07:24.440 you went to grad school . In fact , we 07:24.440 --> 07:26.551 probably thought most of our soldiers 07:26.551 --> 07:28.718 didn't need to go to grad school to be 07:28.718 --> 07:30.773 able to code and they , most of them 07:30.773 --> 07:32.496 have not . So we have soldiers 07:32.496 --> 07:34.496 everywhere from the rank of private 07:34.496 --> 07:36.607 first class all the way up to major . 07:36.607 --> 07:38.750 And the idea is to put rank aside and 07:38.750 --> 07:40.806 promote ideas . Uh , because you can 07:40.806 --> 07:42.972 imagine just as much as what a private 07:42.972 --> 07:45.139 first class can learn from a captain , 07:45.139 --> 07:47.250 you can imagine what that captain can 07:47.250 --> 07:47.160 learn from that private first class . 07:47.640 --> 07:49.807 And that's the fundamental ideas as we 07:49.807 --> 07:52.029 consider how the army should invest and 07:52.029 --> 07:54.550 institutionalize expertise in emerging 07:54.550 --> 07:57.350 technologies . Let's go to the next one , 08:00.640 --> 08:02.918 the third part of the software factory , 08:02.918 --> 08:04.751 right . We have the human talent 08:04.751 --> 08:06.807 management component , We've got the 08:06.807 --> 08:08.918 technology component , but we've also 08:08.918 --> 08:10.973 got the component of it that sort of 08:10.973 --> 08:13.029 forges relationships with , uh , non 08:13.029 --> 08:14.973 traditional industry with the tech 08:14.973 --> 08:17.029 industry , uh , with the traditional 08:17.029 --> 08:19.196 defense industry and that's a big part 08:19.196 --> 08:21.418 of what we're doing down in Austin . So 08:21.418 --> 08:21.310 every week we're hosting lunch and 08:21.310 --> 08:23.860 learns , we're hosting talks from 08:23.860 --> 08:26.450 Microsoft from facebook from google . 08:26.840 --> 08:28.729 Uh , and the soldiers are getting 08:28.729 --> 08:30.951 exposed to that sort of problem solving 08:30.951 --> 08:33.173 process that Silicon Valley has , has , 08:33.173 --> 08:35.770 has sort of championed . Um , and we're 08:35.770 --> 08:38.890 sort of leveraging the fact that the 08:38.900 --> 08:41.122 software factories in such a phenomenal 08:41.122 --> 08:43.233 location like Austin where right down 08:43.233 --> 08:45.400 the road or the headquarters of google 08:45.400 --> 08:47.567 facebook and Tesla , right up the road 08:47.567 --> 08:49.622 is the UT McCombs School of Business 08:49.622 --> 08:51.567 and then that leads us to national 08:51.567 --> 08:53.289 partnerships with a lot of the 08:53.289 --> 08:55.400 companies that are here today . Let's 08:55.400 --> 08:57.067 go to the next slide please . 08:59.240 --> 09:01.351 But I would also kind of point out to 09:01.351 --> 09:03.462 everybody here today that's listening 09:03.462 --> 09:05.573 is that we have a tendency to sort of 09:05.573 --> 09:07.920 plan things in a vacuum and we build in 09:07.920 --> 09:10.142 a way that hey , everything is gonna be 09:10.142 --> 09:12.364 great in the next two years . We didn't 09:12.364 --> 09:14.531 do that in this case , just like agile 09:14.531 --> 09:16.698 software development . We sort of , we 09:16.698 --> 09:18.753 sort of learned as we went and so we 09:18.753 --> 09:20.587 were building a proof of concept 09:20.587 --> 09:23.550 project as we developed the concept for 09:23.550 --> 09:25.606 the wider software factory project . 09:25.940 --> 09:28.020 And so this proof of concept project 09:28.030 --> 09:30.252 was built in conjunction with the Chief 09:30.252 --> 09:32.308 Information Officer of the Army . It 09:32.308 --> 09:34.197 was built in conjunction with the 09:34.197 --> 09:36.419 enterprise cloud management agency . It 09:36.419 --> 09:38.474 was built with soldiers at Fort Hood 09:38.474 --> 09:40.697 and Army material command . And what we 09:40.697 --> 09:40.200 quickly realizes everything about . The 09:40.200 --> 09:42.367 software factory should be well nested 09:42.367 --> 09:44.589 with operational and army wide partners 09:44.589 --> 09:47.260 and that's really a key to success . So 09:47.740 --> 09:50.180 ah , we just sent soldiers up to Fort 09:50.180 --> 09:53.540 Hood to observe what could happen in 09:53.550 --> 09:55.760 logistics warehouses across the army . 09:56.140 --> 09:58.307 And the beautiful thing about the army 09:58.307 --> 10:00.473 is those logistics warehouses are sort 10:00.473 --> 10:00.300 of all standardized . So if we can 10:00.300 --> 10:02.189 solve a problem for one logistics 10:02.189 --> 10:03.800 warehouse , we could solve a 10:03.800 --> 10:05.800 potentially solve a problem for all 10:05.800 --> 10:07.967 logistics warehouses and by monitoring 10:07.967 --> 10:09.967 soldier behavior . And this gets us 10:09.967 --> 10:09.790 into a lot of the top line talking 10:09.790 --> 10:11.957 points of user centered design , which 10:11.957 --> 10:14.123 is really soldiers center design . And 10:14.123 --> 10:16.234 then the idea of the software factory 10:16.234 --> 10:18.290 is taking soldiers center design one 10:18.290 --> 10:20.290 step further and co developing with 10:20.290 --> 10:20.050 soldiers to make sure you're getting 10:20.050 --> 10:23.920 the projects right . Um we found out 10:23.930 --> 10:26.041 that we could automate something that 10:26.041 --> 10:28.041 was inherently manual at the at the 10:28.041 --> 10:30.610 warehouses using accredited def sec ops , 10:30.610 --> 10:32.832 pipelines and platforms . Again through 10:32.832 --> 10:35.360 co development with the army C . I . O . 10:35.740 --> 10:38.060 Um we were able to fast track a 10:38.060 --> 10:40.340 solution to the field that hadn't been 10:40.340 --> 10:42.507 able to get out there despite the fact 10:42.507 --> 10:44.618 that people have been requesting it . 10:44.618 --> 10:46.784 And as you can see there , the big the 10:46.784 --> 10:48.840 big number about 3500 soldiers hours 10:48.840 --> 10:50.840 safe per per S . S . A . Across the 10:50.840 --> 10:53.007 army uh is something that we're really 10:53.007 --> 10:54.896 proud of . And so we took all the 10:54.896 --> 10:54.310 lessons learned , the good things and 10:54.310 --> 10:56.421 the bad and that informed the concept 10:56.421 --> 10:58.700 development of what became the army 10:58.700 --> 11:01.010 software factory . Let's go ahead and 11:01.010 --> 11:04.250 go to the next slide . So , uh 11:04.840 --> 11:06.910 current status is , we've got cohort 11:06.910 --> 11:09.021 one . I talked a little bit about the 11:09.021 --> 11:11.021 cohort of soldiers that we bring on 11:11.021 --> 11:13.021 every six months . So cohort one is 11:13.021 --> 11:15.021 through their technical accelerator 11:15.021 --> 11:17.132 phase there , through their discovery 11:17.132 --> 11:17.010 and framing phase and they're already 11:17.010 --> 11:19.690 coding solutions to army problems with 11:19.690 --> 11:21.857 partners across the army and these are 11:21.857 --> 11:23.968 some of the partners that we're doing 11:23.968 --> 11:27.500 um cohort two . Uh They're finishing up 11:27.500 --> 11:29.722 their technical accelerator and they'll 11:29.722 --> 11:32.056 be starting their , their pairing phase , 11:32.056 --> 11:34.222 uh , right after thanksgiving , cohort 11:34.222 --> 11:36.444 three will be here in december and then 11:36.444 --> 11:38.500 cohort four pending HRC S approval . 11:38.500 --> 11:40.556 They'll be in , they'll be in Austin 11:40.556 --> 11:42.722 next summer . So without further ado , 11:42.840 --> 11:45.062 I want to let you hear from some of the 11:45.062 --> 11:47.062 soldiers and as as they come up and 11:47.062 --> 11:49.284 they talk to you about their projects , 11:49.284 --> 11:48.990 I want you to think about the fact that 11:48.990 --> 11:51.770 the army did not sign them up to be 11:51.770 --> 11:53.950 software developers , they self 11:53.950 --> 11:55.920 selected in because they had the 11:55.920 --> 11:58.170 aptitude and the attitude . And I think 11:58.170 --> 12:00.770 what we've proven out here is that , uh , 12:00.780 --> 12:03.170 a little bit of organic capability will 12:03.170 --> 12:05.880 go a long way towards informing a lot 12:05.890 --> 12:08.130 of policy that the army creates over 12:08.140 --> 12:10.473 the next couple of years as we consider , 12:10.473 --> 12:12.640 like the Secretary said this morning , 12:12.640 --> 12:14.862 uh , dominating in an information age . 12:14.862 --> 12:16.973 So , uh , Lieutenant Richelle David , 12:16.973 --> 12:18.751 don't you come up and introduce 12:18.751 --> 12:22.720 yourself to the crowd . Hello everyone . 12:22.730 --> 12:24.452 I'm Lieutenant Michael David , 12:24.452 --> 12:26.720 originally an engineer officer , I 12:26.720 --> 12:28.700 guess I still am . And uh , I'm 12:28.700 --> 12:30.890 originally from new york and I'm a 12:30.890 --> 12:33.260 product manager on team mocha . Can you 12:33.260 --> 12:36.050 go to next slide please ? Thank you . 12:37.140 --> 12:39.520 And so on . The problem in Argentina 12:39.520 --> 12:42.180 mow cop As it stands today . National 12:42.180 --> 12:44.300 Guard reservists . Uh , they , so 12:44.300 --> 12:47.270 600,000 people who want to apply for 12:47.270 --> 12:49.492 and volunteer for active duty jobs , it 12:49.492 --> 12:51.659 is incredibly difficult for them to do 12:51.659 --> 12:53.548 that . And so me and my team , we 12:53.548 --> 12:55.770 partnered with the G 357 , the Chief of 12:55.770 --> 12:57.714 the Army Reserves and the National 12:57.714 --> 12:59.770 Guard Bureau as well as other hiring 12:59.770 --> 13:01.830 managers across the army to find out 13:01.840 --> 13:03.951 what our soldiers experiencing . That 13:03.951 --> 13:06.062 makes this process so difficult . And 13:06.062 --> 13:08.380 we found is that the existing tool tour 13:08.380 --> 13:10.770 of duty , it's only accessible on 13:10.770 --> 13:12.992 Nipper , which means that most National 13:12.992 --> 13:15.214 Guard reservists can't access it . They 13:15.214 --> 13:17.270 need to go physically to the nearest 13:17.270 --> 13:20.230 either post or armory or something that 13:20.240 --> 13:22.462 is able to , you can go on a government 13:22.462 --> 13:24.462 computer and go on nipper to access 13:24.462 --> 13:26.407 Tour of duty , which is incredibly 13:26.407 --> 13:28.351 difficult even to see what is even 13:28.351 --> 13:30.510 available . But we also found is that 13:30.510 --> 13:32.343 once they do find something that 13:32.343 --> 13:34.121 interests them , the process to 13:34.121 --> 13:36.121 actually get that job is incredibly 13:36.121 --> 13:38.232 manual . They need to physically pick 13:38.232 --> 13:40.454 up a phone or email someone in order to 13:40.454 --> 13:42.399 move their packet along . And this 13:42.399 --> 13:44.454 process takes a long time and people 13:44.454 --> 13:46.788 often give up because it's so difficult . 13:47.040 --> 13:49.230 And what's what we found most baffling 13:49.230 --> 13:51.397 is that the army owns this data , they 13:51.397 --> 13:53.563 own the existing code . And so what me 13:53.563 --> 13:55.397 and my team are here to do is to 13:55.397 --> 13:57.230 overhaul your duty and produce a 13:57.230 --> 13:59.341 solution that soldiers can use in the 13:59.341 --> 14:01.619 palm of their hand . Next slide please . 14:01.619 --> 14:03.508 So our solution , Correra enables 14:03.508 --> 14:05.563 soldiers to view open positions from 14:05.563 --> 14:07.341 anywhere on their other , their 14:07.341 --> 14:09.508 personal phone or their computer uh in 14:09.508 --> 14:12.360 a secure way . they can uh find jobs 14:12.360 --> 14:14.360 that they're eligible for since not 14:14.360 --> 14:16.471 they're not eligible for every single 14:16.471 --> 14:16.110 job . So find jobs that they're 14:16.110 --> 14:18.166 eligible for jobs that they actually 14:18.166 --> 14:21.040 want to apply for and by doing so uh 14:21.050 --> 14:23.161 what we hope to accomplish is getting 14:23.161 --> 14:25.930 uh matching tops older talent with top 14:25.930 --> 14:27.708 jobs in a way that's prompt and 14:27.708 --> 14:29.652 personalized so that we can better 14:29.652 --> 14:31.763 manage the talent that already exists 14:31.763 --> 14:33.986 in our force . And so the army is ready 14:33.986 --> 14:36.152 to mobilize and I will hand it back to 14:36.152 --> 14:38.208 Colonel Eriko to talk about the next 14:38.208 --> 14:41.050 project . Thanks . Yeah , 14:42.540 --> 14:44.651 So unfortunately , uh let's go to the 14:44.651 --> 14:48.040 next time . Uh Thanks to the Southwest 14:48.040 --> 14:50.262 Airlines , the person that was going to 14:50.262 --> 14:52.596 brief this like can't be here right now . 14:52.596 --> 14:55.220 But what we're doing is we're 14:55.220 --> 14:57.331 continuing the work from the proof of 14:57.331 --> 15:00.060 concept with Army Material Command and 15:00.060 --> 15:02.760 uh potentially looking at how soldiers 15:02.770 --> 15:04.937 engage in the preventative maintenance 15:04.937 --> 15:07.103 checks and services process , which as 15:07.103 --> 15:09.214 many of us I think that are listening 15:09.214 --> 15:11.381 here no , is the lifeblood for how the 15:11.381 --> 15:10.910 army maintains its equipment at the end 15:10.910 --> 15:12.790 user level . There's a lot that 15:12.790 --> 15:15.530 technology can provide um in sort of a 15:15.530 --> 15:18.200 simple scalable way that the soldier 15:18.200 --> 15:21.680 perspective will uniquely inform And so 15:21.690 --> 15:23.523 we have a team dedicated towards 15:23.523 --> 15:25.579 working with Army Material Command , 15:25.579 --> 15:27.634 working with units up at Fort Hood , 15:27.634 --> 15:29.579 Fort Riley um in understanding how 15:29.579 --> 15:31.634 soldiers are using the equipment and 15:31.634 --> 15:33.634 then what we could potentially meet 15:33.634 --> 15:35.690 them with halfway as the army fields 15:35.690 --> 15:37.857 larger systems um let's go to the next 15:37.857 --> 15:40.780 slide and let's bring up lieutenant on 15:40.780 --> 15:41.450 on shaw . 15:46.840 --> 15:49.450 So the model of the software factory is 15:49.450 --> 15:52.560 by soldiers for soldiers . Last year , 15:52.560 --> 15:54.616 Sergeant Major Grinstein asked us to 15:54.616 --> 15:56.560 build a digital tool that empowers 15:56.560 --> 15:58.400 squad leaders . The bluff of our 15:58.400 --> 16:00.350 project is that we've built an 16:00.350 --> 16:02.760 accredited army tool for soldiers , 16:02.760 --> 16:06.340 personal devices . Sergeant Major 16:06.340 --> 16:08.500 Grinstein kept our charter vague like 16:08.510 --> 16:10.566 Lieutenant Colonel Errico said we're 16:10.566 --> 16:12.840 planning for ambiguity . He simply 16:12.840 --> 16:14.890 requested that we ask what soldiers 16:14.890 --> 16:17.430 want and we build that so that's what 16:17.430 --> 16:20.300 we did every week since the inception 16:20.300 --> 16:22.510 of our team , we've had touchpoints 16:22.520 --> 16:24.576 from soldiers and squad leaders from 16:24.576 --> 16:26.860 Fort Hood and Fort Lewis about what 16:26.860 --> 16:30.310 they need . We learned that a company 16:30.310 --> 16:33.120 of 150 soldiers oftentimes is assigned 16:33.120 --> 16:36.230 only 15 laptops . We learned that staff 16:36.230 --> 16:38.580 duty rosters will oftentimes get lost 16:38.580 --> 16:41.630 in a WhatsApp group chat . We also 16:41.630 --> 16:43.463 learned that a squads day to day 16:43.463 --> 16:45.780 schedule isn't just affected by what's 16:45.790 --> 16:48.012 on a chalkboard at the platoon office , 16:48.012 --> 16:50.068 but also by last minute appointments 16:50.068 --> 16:53.770 and Taskings . So some takeaways , 16:54.140 --> 16:56.700 soldiers don't have consistent access 16:56.700 --> 16:59.810 to the existing army provided tools so 16:59.820 --> 17:01.931 they use third party systems on their 17:01.931 --> 17:03.876 personal devices like WhatsApp and 17:03.876 --> 17:07.280 google drive . We hope to decrease this 17:07.280 --> 17:09.600 task and schedule volatility so squads 17:09.600 --> 17:12.350 can focus on readiness and cohesion . 17:14.440 --> 17:16.680 So based on their feedback , we set out 17:16.690 --> 17:18.820 to build a solution with them . next 17:18.820 --> 17:22.620 slide please . Soldiers guided us as we 17:22.620 --> 17:25.140 built a web app that allows soldiers to 17:25.140 --> 17:27.790 pool and assigned tasks , manage unit 17:27.790 --> 17:30.190 events and personal appointments and 17:30.190 --> 17:32.357 share their digital counseling packets 17:34.240 --> 17:36.890 right now . The lack of access to legit 17:36.900 --> 17:39.400 army tools , forces soldiers to conduct 17:39.410 --> 17:41.950 and coordinate army businesses on 17:41.960 --> 17:44.270 unaccredited third party applications 17:44.280 --> 17:46.502 which we can't control and which can go 17:46.502 --> 17:48.502 down to any time . Like we saw last 17:48.502 --> 17:52.250 week our app meets 17:52.250 --> 17:54.260 soldiers where they are on their 17:54.260 --> 17:56.371 personal cell phones and it's still a 17:56.371 --> 17:58.430 work in progress . We still gather 17:58.430 --> 18:00.860 feedback every week and we need more 18:02.140 --> 18:04.140 so for members of the army family . 18:04.140 --> 18:06.140 Come find us at the futures command 18:06.140 --> 18:08.307 Booth will on board you to the app and 18:08.307 --> 18:10.418 you can join the team that's building 18:10.418 --> 18:12.251 the my squad app by soldiers for 18:12.251 --> 18:15.090 soldiers . Our app is built on an 18:15.090 --> 18:17.034 accredited army platform which has 18:17.034 --> 18:19.090 worked on by engineers such as staff 18:19.090 --> 18:21.312 sergeant Polly who's gonna come up next 18:27.840 --> 18:30.062 Good afternoon . I'm Steph Sarah Polley 18:30.062 --> 18:32.062 and I'm the platform engineer for a 18:32.062 --> 18:35.030 software factory . Formerly I was a 18:35.040 --> 18:37.300 cyber security analyst at Fort Hood and 18:37.300 --> 18:38.800 prior to that or satellite 18:38.800 --> 18:41.410 communications And after 12 years of 18:41.410 --> 18:43.577 service , I would have never thought I 18:43.577 --> 18:45.670 would be here working def sec ops 18:45.680 --> 18:47.847 ecosystem for software factory for the 18:47.847 --> 18:51.630 army and our product that we built next 18:51.630 --> 18:55.280 slide please is a sorcerer 18:55.560 --> 18:57.490 and with this product is a credit 18:57.490 --> 19:01.100 secure kubernetes based platform that 19:01.100 --> 19:03.320 hosts our army applications and we 19:03.320 --> 19:05.487 provide a path to production for these 19:05.487 --> 19:08.550 applications . The process to go from 19:08.550 --> 19:11.360 inception to authority to operate was 19:11.360 --> 19:13.840 typically around two years and we 19:13.840 --> 19:17.040 reduce that time 3-6 months with our 19:17.040 --> 19:18.360 product Sorcerer 19:20.740 --> 19:22.851 traditionally an app team without the 19:22.851 --> 19:24.907 source , our product , they will own 19:24.907 --> 19:27.018 everything in the grain on the left , 19:27.018 --> 19:28.851 which is the build process , the 19:28.851 --> 19:30.907 security controls the infrastructure 19:30.907 --> 19:32.962 networking , but with the source our 19:32.962 --> 19:35.184 product , we handle all that for them . 19:36.540 --> 19:38.960 We enable our application developers to 19:38.960 --> 19:41.420 focus on coding . This is possible 19:41.420 --> 19:43.840 through a variety of innovative tools 19:43.840 --> 19:45.870 such as kubernetes and the use of 19:45.870 --> 19:48.690 automation . I've used this word two 19:48.690 --> 19:51.290 times now kubernetes , not many people 19:51.290 --> 19:53.780 know what it is , it's a very new tool 19:53.790 --> 19:56.260 less than four or five years old if you 19:56.260 --> 19:58.260 have any , if you want to know more 19:58.260 --> 20:00.427 information about it , you come to our 20:00.427 --> 20:02.482 booth at the Army software factory . 20:03.540 --> 20:05.484 Once the app team is in production 20:06.040 --> 20:08.310 teams continuously integrate and deploy 20:08.310 --> 20:11.440 their code as such a rapid pace if they 20:11.440 --> 20:14.130 want to fix uh boat bug fixes and 20:14.130 --> 20:17.700 features , quickly integrating 20:17.700 --> 20:20.680 changes into the production provides an 20:20.820 --> 20:23.780 incredible value enabling our 20:23.780 --> 20:26.050 developers to get software into the 20:26.050 --> 20:29.660 hands of soldiers hands faster 20:31.140 --> 20:33.560 and thank you 20:38.240 --> 20:41.300 thanks to absorb early . So at we're 20:41.300 --> 20:43.750 going to open it up to questions and so 20:43.760 --> 20:45.830 we started getting warmed up um but 20:45.830 --> 20:48.330 before we do that , I want to just sort 20:48.330 --> 20:50.274 of clothes on . Remember those two 20:50.274 --> 20:52.274 questions I I opened with about how 20:52.274 --> 20:54.497 does the army think about going from an 20:54.497 --> 20:56.219 industrial age workforce to an 20:56.219 --> 20:58.274 information age workforce . And then 20:58.274 --> 21:00.163 how does the army help commanders 21:00.163 --> 21:02.160 operate in a future environment of 21:02.160 --> 21:05.130 increasingly complicated communication , 21:05.130 --> 21:06.741 sweets , weapons platforms , 21:06.741 --> 21:08.908 information streams and data streams . 21:09.040 --> 21:12.710 So again the software factory up skills 21:12.710 --> 21:14.750 re skills , soldiers who have the 21:14.750 --> 21:17.600 talent who have the desire in modern 21:17.610 --> 21:19.666 application engineering and software 21:19.666 --> 21:21.666 development were institutionalizing 21:21.666 --> 21:23.832 those practices so that we're not just 21:23.832 --> 21:25.999 building this one time , we're opening 21:25.999 --> 21:27.999 it up for the army to build , build 21:27.999 --> 21:27.720 more widely and that's under 21:27.720 --> 21:29.942 consideration at HQ . Today . Right now 21:30.140 --> 21:32.330 we're leveraging modern technology 21:32.330 --> 21:34.552 through close partnership with the army 21:34.552 --> 21:36.610 C . I . O . And the def . Sec ops 21:36.620 --> 21:38.787 ecosystem that the army C . I . O . Is 21:38.787 --> 21:40.509 championing so that we can put 21:40.509 --> 21:42.287 technology to work for everyday 21:42.287 --> 21:44.453 soldiers so that we can actually build 21:44.453 --> 21:46.564 applications faster . And then lastly 21:46.940 --> 21:48.829 leveraging the unique location of 21:48.829 --> 21:50.996 features , command with respect to all 21:50.996 --> 21:53.107 the tech companies in Austin with the 21:53.107 --> 21:55.329 modernization efforts down there at the 21:55.329 --> 21:57.329 headquarters as well as Fort Hood . 21:57.329 --> 21:59.496 Just being right up the road , uh sort 21:59.496 --> 22:01.718 of sort of a perfect storm for the army 22:01.718 --> 22:03.940 software factory . So really appreciate 22:03.940 --> 22:05.940 everybody's attention . It was very 22:05.940 --> 22:07.996 much an honor to be able to go first 22:07.996 --> 22:10.162 for the warriors corner at this year's 22:10.162 --> 22:12.273 A U . S . A . And welcome any and all 22:12.273 --> 22:14.496 questions anybody has . I think we have 22:14.496 --> 22:13.740 a mic in the back for anybody that 22:13.740 --> 22:14.740 wants to ask . 22:17.640 --> 22:19.473 Thank you very much . That was a 22:19.473 --> 22:21.807 fantastic presentation . Should be very , 22:21.807 --> 22:23.696 really proud of the progress that 22:23.696 --> 22:25.640 you've made with the United States 22:25.640 --> 22:27.529 Armies . Global force Information 22:27.529 --> 22:29.362 management system and enterprise 22:29.362 --> 22:31.362 business systems convergence . Both 22:31.362 --> 22:33.084 adopting and piloting low code 22:33.084 --> 22:35.084 platforms . How do you see low code 22:35.084 --> 22:37.084 platforms being integrated into the 22:37.084 --> 22:39.970 software factory ? Thank you . You guys 22:39.970 --> 22:43.690 okay if I take this one . Okay . Uh So 22:43.690 --> 22:45.910 I think you know low code is obviously 22:45.920 --> 22:48.260 pretty , pretty popular right now . Um 22:48.740 --> 22:50.962 some things to think about for low code 22:50.962 --> 22:52.962 is that there are a lot of discrete 22:52.962 --> 22:55.296 solutions out there . So for , you know , 22:55.296 --> 22:55.280 the army is a customer's perspective . 22:55.280 --> 22:57.447 It's hard to pick just one and I'm not 22:57.447 --> 22:59.391 a contracting officer , I'm not an 22:59.391 --> 23:01.391 acquisition officer . Um I do think 23:01.391 --> 23:03.613 that the work being done by the deficit 23:03.613 --> 23:05.780 cops uh ecosystem underneath the chief 23:05.780 --> 23:07.891 information , the army , the platform 23:07.891 --> 23:07.770 work that sergeant , staff sergeant 23:07.770 --> 23:10.480 paulie is doing is providing the policy 23:10.480 --> 23:12.702 guidance and the security accreditation 23:12.702 --> 23:14.860 precedent . So that as the army feels 23:14.860 --> 23:16.804 those kinds of things , you know , 23:16.804 --> 23:18.971 cyber security is sort of a reciprocal 23:18.971 --> 23:20.971 or there's a reciprocity associated 23:20.971 --> 23:23.138 with cyber security across the D . O . 23:23.138 --> 23:25.360 D . Which you're obviously aware buy us 23:25.360 --> 23:27.693 trail blazing a path with the C . I . O . 23:27.693 --> 23:30.400 Of the army bringing on low code 23:30.400 --> 23:32.456 solutions or proprietary solutions . 23:32.456 --> 23:34.622 We'll get through the fed ramp process 23:34.622 --> 23:36.789 faster . It'll get through the D . O . 23:36.789 --> 23:38.956 D . Accreditation process faster . And 23:38.956 --> 23:41.011 so that's another great part that we 23:41.011 --> 23:43.178 didn't really mention is the faster we 23:43.178 --> 23:45.289 can bring on third party applications 23:45.289 --> 23:44.630 that more to the army will benefit from 23:44.630 --> 23:47.160 that as well . Great question . 23:50.940 --> 23:54.150 Thank you . Um you noted that the size 23:54.150 --> 23:56.570 of the cohorts right now are about 25 23:56.570 --> 23:58.737 personnel . Is any thought being given 23:58.737 --> 24:00.848 to increase the size of those just to 24:00.848 --> 24:02.959 kind of increase the pipeline and the 24:02.959 --> 24:05.181 throughput of the folks you're training 24:05.181 --> 24:07.403 a great question . What I can say right 24:07.403 --> 24:09.403 now is this is very much a software 24:09.403 --> 24:11.626 factory itself is very much a pilot and 24:11.626 --> 24:13.570 it's built to learn from , if that 24:13.570 --> 24:16.290 makes sense . Um There's a lot of 24:16.290 --> 24:18.234 lessons to be gleaned about talent 24:18.234 --> 24:20.234 management , a lot of lessons to be 24:20.234 --> 24:22.401 gleaned about technology . And so it's 24:22.401 --> 24:24.568 not until this experiment's done , are 24:24.568 --> 24:26.679 we going to be able to to maybe think 24:26.679 --> 24:29.012 think about how to scale it more widely ? 24:29.012 --> 24:27.930 I'd be interested to see what the 24:27.930 --> 24:30.097 cohort members think about the size of 24:30.097 --> 24:32.152 the cohort . Do you guys feel it's a 24:32.152 --> 24:34.152 pretty intimate experience ? You're 24:34.152 --> 24:36.319 getting enough attention . Head nuts . 24:36.319 --> 24:39.170 Okay . Mhm . Thanks for the question . 24:40.140 --> 24:42.362 I think we have a couple more minutes . 24:42.362 --> 24:42.360 If anybody wants to ask anything , 24:44.640 --> 24:46.918 there's a question somewhere over here . 24:47.140 --> 24:51.120 Yeah , I veto 24:51.130 --> 24:54.370 over uh the talent aspect of this is 24:54.370 --> 24:57.110 critical . And so for probably for the 24:57.110 --> 24:59.460 cohort here and and the future cohorts , 25:00.240 --> 25:02.490 they're assuming some individual risk 25:02.490 --> 25:04.546 with their career progression in all 25:04.546 --> 25:06.323 these different mos is to build 25:06.323 --> 25:08.580 software . What's the on ramp or off 25:08.580 --> 25:11.480 ramp for them into a new mos and or 25:11.480 --> 25:13.647 what's the army ? What's the check the 25:13.647 --> 25:15.591 army is going to write to them for 25:15.591 --> 25:17.702 their ability to have a career in the 25:17.702 --> 25:19.647 army after three years of building 25:19.647 --> 25:21.869 software away from their M . O . S . So 25:21.869 --> 25:24.091 it is kind of a problem for my team and 25:24.091 --> 25:24.030 I know it's gonna , thanks for the 25:24.030 --> 25:27.310 question cory . Uh So um what I can say 25:27.310 --> 25:29.421 it's sort of like the last question . 25:29.421 --> 25:31.254 Um we're sort of well aware that 25:31.254 --> 25:33.143 everything that we do is going to 25:33.143 --> 25:35.310 inform the creation or the creation of 25:35.310 --> 25:37.532 new army policy and practices about how 25:37.532 --> 25:39.699 we handle talent . Again the secretary 25:39.699 --> 25:41.810 said this morning we're in a race for 25:41.810 --> 25:43.866 talent . This is very much a part of 25:43.866 --> 25:45.977 the question that you just asked . Um 25:45.977 --> 25:48.088 So the H . P . D . A . Is considering 25:48.088 --> 25:50.254 all options here . Um I think that you 25:50.254 --> 25:52.477 know a lot of people recognize the army 25:52.477 --> 25:51.980 doesn't want to make this type of 25:51.980 --> 25:53.980 investment and doesn't want to lose 25:53.980 --> 25:56.036 these kinds of soldiers . And so the 25:56.036 --> 25:58.202 thought is how do we how do we best do 25:58.202 --> 25:57.950 that long term to your point and 25:57.950 --> 25:59.839 hopefully we can help inform that 25:59.839 --> 26:00.839 process . 26:04.840 --> 26:07.007 I saw the companies listed on your one 26:07.007 --> 26:09.960 slide how can other companies help ? Is 26:09.960 --> 26:11.904 there still room ? I thought you'd 26:11.904 --> 26:15.170 never ask . Um So that is not an 26:15.170 --> 26:17.480 exhaustive exclusive list . That's just 26:17.480 --> 26:19.591 an idea of some of the companies . Uh 26:19.591 --> 26:22.240 so we try to have industry interaction 26:22.240 --> 26:24.407 in a couple different ways . We talked 26:24.407 --> 26:26.407 a little bit about coming in person 26:26.407 --> 26:28.351 down to Austin and doing lunch and 26:28.351 --> 26:30.240 learns or demonstrations with the 26:30.240 --> 26:32.351 soldiers . Uh , what we didn't really 26:32.351 --> 26:34.684 talk about is built into the experience . 26:34.684 --> 26:36.740 Covid hasn't helped much , but we're 26:36.740 --> 26:38.796 gonna get there about 30 to 60 day , 26:38.796 --> 26:40.684 many internship we call them mini 26:40.684 --> 26:42.629 versions uh , to to vendors or the 26:42.629 --> 26:44.851 industry that's interested in hosting a 26:44.851 --> 26:47.018 soldier for that amount of time . Um , 26:47.018 --> 26:46.850 and then of course there's there's 26:46.850 --> 26:49.120 plenty of opportunities across uh the 26:49.120 --> 26:51.342 army to connect to you um for for other 26:51.342 --> 26:53.380 things . So there's a spot on our 26:53.380 --> 26:55.600 website . If you're an industry that 26:55.610 --> 26:57.110 wants to contribute to the 26:57.110 --> 26:59.277 collaboration going on at the software 26:59.277 --> 27:01.499 factories , you can do that or you come 27:01.499 --> 27:03.554 by the booth and we'll trade contact 27:03.554 --> 27:03.340 information there and you can always 27:03.340 --> 27:05.562 visit the Army Software factory website 27:05.562 --> 27:07.618 at the army features command dot com 27:07.618 --> 27:09.760 slash software dash factory . Yeah . 27:12.640 --> 27:13.640 Yes , ma'am . 27:16.640 --> 27:20.460 I'll repeat it . Thank you so much . 27:21.740 --> 27:23.684 I just wondered if you look to the 27:23.684 --> 27:26.018 other services um , for lessons learned , 27:26.018 --> 27:28.184 especially the Air Force and maybe the 27:28.184 --> 27:30.351 level of code works , which I think is 27:30.351 --> 27:32.629 in Austin near you . Yeah . Oh , santa . 27:32.629 --> 27:34.796 Um , just kind of for their experience 27:34.796 --> 27:36.851 and kind of how you're building your 27:36.851 --> 27:39.950 fantastic question . Um I'm sort of uh , 27:40.740 --> 27:44.280 happy to report um the process that 27:44.290 --> 27:46.512 informed everything that we just talked 27:46.512 --> 27:49.150 about Uh included about 12 to 15 months 27:49.150 --> 27:51.620 what I kind of call a market analysis 27:51.620 --> 27:53.564 or industry analysis and that that 27:53.564 --> 27:55.731 included to your point about the other 27:55.731 --> 27:57.731 services , what they're doing . The 27:57.731 --> 27:59.842 idea of incorporating service members 27:59.842 --> 27:59.620 into the application development 27:59.620 --> 28:02.780 process is not new , right ? What's new 28:02.780 --> 28:04.947 about it is putting building them into 28:04.947 --> 28:06.920 it long term and to invest in the 28:06.920 --> 28:08.698 people component , not just the 28:08.698 --> 28:10.809 technology component . What we saw as 28:10.809 --> 28:13.031 we looked at some of the other services 28:13.031 --> 28:15.087 was that they were doing really well 28:15.087 --> 28:14.260 for the initial service member 28:14.260 --> 28:16.316 involvement , but how to build it in 28:16.316 --> 28:18.427 longer term . That was something that 28:18.427 --> 28:20.593 had yet to be decided by any service . 28:20.593 --> 28:22.760 And so as we were conceptualizing it , 28:22.760 --> 28:24.816 we were thinking how long could we , 28:24.816 --> 28:26.927 could we realistically keep a soldier 28:26.927 --> 28:29.038 and build it soldier first or service 28:29.038 --> 28:31.260 member first . And so the soldiers that 28:31.260 --> 28:33.482 come to the software factory as part of 28:33.482 --> 28:32.910 the experiment , the pilot that we've 28:32.910 --> 28:35.077 been talking about , they're there for 28:35.077 --> 28:37.299 three years . So whereas other services 28:37.299 --> 28:39.521 do the 179 day T . D . Y . Uh we've got 28:39.521 --> 28:41.410 a whole whole unit full of people 28:41.410 --> 28:43.521 staying for three years and that will 28:43.521 --> 28:45.299 help lose a lot of , you know , 28:45.299 --> 28:47.410 ameliorate a lot of the institutional 28:47.410 --> 28:49.688 turnover that goes on a great question , 28:49.688 --> 28:49.230 ma'am actually . And let me also add , 28:49.230 --> 28:51.063 that's the human component , the 28:51.063 --> 28:53.174 technology component , you know , the 28:53.174 --> 28:55.397 Air Force did a great job codifying the 28:55.397 --> 28:57.286 continuous RMF process , the risk 28:57.286 --> 28:59.397 mitigation framework process . Uh and 28:59.397 --> 29:01.619 that's directly inform a lot of the def 29:01.619 --> 29:03.786 sec ops um environment of the Army C . 29:03.786 --> 29:06.008 I . O . The enterprise cloud management 29:06.008 --> 29:08.119 agency and then us have have all sort 29:08.119 --> 29:09.730 of co developed . So again , 29:09.730 --> 29:11.786 cybersecurity comes out to precedent 29:11.786 --> 29:11.660 and reciprocity and that that was a big 29:11.660 --> 29:13.771 part of it . So we couldn't have done 29:13.771 --> 29:17.710 that without them beat . 29:17.710 --> 29:19.988 I'll be your last question if you want . 29:19.988 --> 29:23.010 So obviously the software factories up 29:23.010 --> 29:25.066 and running right . You've got great 29:25.066 --> 29:28.080 initial success . Are you efforting 29:28.080 --> 29:31.390 with project convergence ? Uh 29:31.400 --> 29:34.680 Ridgeway A I two cc five s are to kind 29:34.680 --> 29:36.569 of provide some connective tissue 29:36.569 --> 29:39.350 across the space . Yeah . So uh there's 29:39.350 --> 29:41.239 a lot to say about the connective 29:41.239 --> 29:43.800 tissue and what I would go back to is a 29:43.800 --> 29:45.911 lot of the policy that we're building 29:45.911 --> 29:48.790 um with H . P . D . A regarding 29:48.800 --> 29:51.300 cybersecurity processes . So the shared 29:51.300 --> 29:53.360 services . Uh We're in a we have a 29:53.360 --> 29:55.527 multi cloud offering in both Azure and 29:55.527 --> 29:58.720 AWS the shared services that create um 29:58.730 --> 30:00.730 which is which is championed by the 30:00.730 --> 30:02.674 enterprise cloud management agency 30:02.674 --> 30:04.730 underneath the Army C . I owe all of 30:04.730 --> 30:06.897 that tech stack accreditation stuff is 30:06.897 --> 30:09.119 going to serve as the fabric across all 30:09.119 --> 30:11.230 of the efforts that we're starting to 30:11.230 --> 30:13.286 see because they're all built on the 30:13.286 --> 30:15.341 idea of the more rapidly you can get 30:15.341 --> 30:17.563 feedback on to an operational network . 30:17.563 --> 30:19.786 The more important it is for the army . 30:19.786 --> 30:19.510 So I think we're pretty happy that 30:19.510 --> 30:21.732 we're anchoring that entire process and 30:21.732 --> 30:23.621 serving as a basis for the shared 30:23.621 --> 30:25.621 services there . We can also report 30:25.621 --> 30:27.843 kind of like we talked about everything 30:27.843 --> 30:30.177 that we do is has more than one partner . 30:30.177 --> 30:32.343 We got multi partners for every single 30:32.343 --> 30:34.121 aspect , whether it be platform 30:34.121 --> 30:33.790 application or in the human talent 30:33.790 --> 30:36.700 management fields . Um So I would say 30:36.700 --> 30:38.922 ah there's sort of no limit to the , to 30:38.922 --> 30:42.260 the collaboration that's going on . 30:46.740 --> 30:48.796 Thanks so much for doing this . Um I 30:48.796 --> 30:51.180 guess I'm wondering what's the duration 30:51.180 --> 30:53.110 of the experiment ? What are the 30:53.120 --> 30:56.340 decision points along the way ? Um And 30:56.340 --> 30:59.320 when do you expect HQ d a to to make 30:59.330 --> 31:01.540 decisions about whether to expand this 31:01.540 --> 31:04.380 or make it permanent ? Thanks . So the 31:04.380 --> 31:06.047 experience from the soldier's 31:06.047 --> 31:08.240 perspective is three years . The first 31:08.240 --> 31:10.680 phase is about 5-6 months . The second 31:10.680 --> 31:12.736 phase is another six months and then 31:12.736 --> 31:14.902 two years on top of that helping to on 31:14.902 --> 31:16.847 board and train follow on soldiers 31:16.847 --> 31:19.069 coming in in this emerging technology . 31:19.069 --> 31:20.791 So those are each one of those 31:20.791 --> 31:22.902 represents a decision point for me is 31:22.902 --> 31:24.680 the director is a soldier worth 31:24.680 --> 31:26.624 continuing to invest in . Are they 31:26.624 --> 31:28.736 right fit ? Because this is obviously 31:28.736 --> 31:28.370 not for everybody , not just from an 31:28.370 --> 31:30.481 emerging technology technical sense , 31:30.481 --> 31:32.703 but it's can you work as a team ? Uh do 31:32.703 --> 31:34.870 you understand what we're trying to do 31:34.870 --> 31:36.759 here ? Um You know software is no 31:36.759 --> 31:38.870 longer sort of like a guy or a girl , 31:38.870 --> 31:40.981 the hooded sweatshirt and uh you know 31:40.981 --> 31:43.092 your you know your phones in the back 31:43.092 --> 31:45.203 like we see in the movies it's a team 31:45.203 --> 31:45.120 sport and the army's gonna train it as 31:45.120 --> 31:47.120 a team sport and build it as a team 31:47.120 --> 31:49.176 sport which is why we do those small 31:49.176 --> 31:51.120 product teams . Um So people can't 31:51.120 --> 31:53.009 participate in that then you know 31:53.009 --> 31:55.231 that's not the right spot for them . Um 31:55.231 --> 31:57.398 And then with respect to H . P . D . A 31:57.398 --> 31:59.453 far be it from from me to be able to 31:59.453 --> 32:01.564 put a timeline on H . P . D . A . But 32:01.564 --> 32:01.560 I'm I'm hopeful we'll hear something 32:01.560 --> 32:03.560 here in the next couple of months . 32:07.540 --> 32:09.800 Oh God I think one more here , if we 32:09.800 --> 32:13.150 have time for one more , I can't stop 32:13.150 --> 32:16.670 with . Hello , are you hear me ? 32:17.240 --> 32:20.060 Lot of clear ma'am . Yes I have a 32:20.060 --> 32:23.780 question . I saw that you 32:23.780 --> 32:27.630 also mentioned there about design 32:27.640 --> 32:30.050 of programs to losing the field 32:31.240 --> 32:34.170 during soldiers operations , correct ? 32:35.240 --> 32:37.800 Say that one more time for me man . Mhm . 32:37.810 --> 32:40.260 I'm talking about tough world that is 32:40.260 --> 32:43.260 not for administrative task 32:43.270 --> 32:46.470 but for operations in the field . 32:46.480 --> 32:49.770 Okay . My question is 32:51.440 --> 32:54.740 I know that the expert ties of a 32:54.740 --> 32:57.670 person to perform . If you give 32:58.340 --> 33:01.140 it was really gives value to the use of 33:01.140 --> 33:05.110 a prop work but for example if 33:05.110 --> 33:08.790 I asked you , I need to know , I 33:08.790 --> 33:11.060 need to know if 33:12.740 --> 33:16.470 we improve the efficiency , the 33:16.470 --> 33:19.740 reliability of the tank for example , 33:19.900 --> 33:23.460 which has stopped well about 33:24.740 --> 33:27.860 15% or 25% . 33:28.540 --> 33:31.300 How you can help me to perform an 33:31.300 --> 33:35.230 evaluation so that we can know the 33:35.240 --> 33:38.960 financial um dead 33:39.940 --> 33:43.360 reliability results if we 33:43.360 --> 33:47.000 implement that change . Okay . That's 33:47.000 --> 33:49.890 all a study . You're performing a study 33:49.890 --> 33:53.360 with the help of your , of your people 33:53.840 --> 33:57.840 that do uh develop programs but I 33:57.840 --> 34:00.350 am a manager and I want to know , 34:01.040 --> 34:04.280 okay , I try to do a test and I want to 34:04.280 --> 34:07.730 know how much For example the 34:07.740 --> 34:11.170 10 , I can improve the reliability 34:11.740 --> 34:14.990 of an equipment that is using a soldier 34:14.990 --> 34:17.157 that have expert tights who use this , 34:17.157 --> 34:19.770 that equipment . I want to know that 34:19.770 --> 34:21.890 because I want to know the financial 34:21.900 --> 34:24.230 impact , how much money I need to do 34:24.230 --> 34:28.090 that in all the army and I want to 34:28.100 --> 34:32.070 have a document to add the needed 34:32.240 --> 34:34.050 budget . Can you ? 34:36.840 --> 34:38.896 I think I think I understood some of 34:38.896 --> 34:40.729 the question ma'am . I think the 34:40.729 --> 34:42.729 headline is uh that we're certainly 34:42.729 --> 34:44.951 operating not just in an administrative 34:44.951 --> 34:47.173 sense but also in a tactical sense . Um 34:47.173 --> 34:49.062 and that there's plenty of people 34:49.062 --> 34:51.007 around the army like the army test 34:51.007 --> 34:53.173 evaluation command that are working on 34:53.173 --> 34:55.340 problems that you just described . And 34:55.340 --> 34:57.507 if I didn't get it right , please come 34:57.507 --> 34:56.920 to the software factory booth right on 34:56.920 --> 34:59.250 the other side of this wall and we'll 34:59.250 --> 35:01.417 sit down and talk about . I'm so sorry 35:01.417 --> 35:03.570 man , I'm also getting the hook uh , 35:03.580 --> 35:05.858 pending general Murray's guidance . No , 35:05.858 --> 35:07.580 and I usually don't make guest 35:07.580 --> 35:09.636 appearances at these , but for these 35:09.636 --> 35:12.110 guys , I will . So um , everything you 35:12.110 --> 35:14.360 just heard was an idea two years ago 35:14.940 --> 35:16.996 and two young majors and we promoted 35:16.996 --> 35:20.170 one of them , uh , put this together in 35:20.180 --> 35:22.890 in two years and that the talent we 35:22.890 --> 35:25.560 have in the army , it's just absolutely 35:25.560 --> 35:27.782 incredible . I was told when we started 35:27.782 --> 35:30.004 this , you don't have that talent , You 35:30.004 --> 35:32.116 gotta go buy it , you gotta go higher 35:32.116 --> 35:32.000 it , you gotta go find it , you gotta 35:32.000 --> 35:34.200 go recruit it . We have the talent . 35:34.210 --> 35:37.160 These kids are just incredibly talented . 35:37.540 --> 35:39.762 And the question you ask is what people 35:39.762 --> 35:41.762 ask me all the time . What keeps me 35:41.762 --> 35:43.873 awake at night that keeps me awake at 35:43.873 --> 35:45.929 night is we have the talent , we can 35:45.929 --> 35:48.151 develop the talent and now we've got to 35:48.151 --> 35:47.980 figure out how to retain the talent 35:47.990 --> 35:49.712 because these kids will make a 35:49.712 --> 35:51.712 significant difference from both an 35:51.712 --> 35:53.770 administrative and on the future , 35:53.780 --> 35:56.002 future battlefield someplace . And then 35:56.002 --> 35:58.336 this has nothing to do with industry ip , 35:58.340 --> 36:00.562 This is all about solving problems that 36:00.562 --> 36:02.610 I have walked past for the last 40 36:02.610 --> 36:04.820 years that our soldiers have each and 36:04.820 --> 36:06.431 every day that we can make a 36:06.431 --> 36:08.900 significant impact on our soldiers now 36:08.900 --> 36:10.956 into the future . Just by harnessing 36:10.956 --> 36:13.640 the town we've got . So just a hats off 36:13.640 --> 36:15.980 to . This is one half of the wonder 36:15.980 --> 36:19.080 twins . So veto and Jason zuniga is the 36:19.080 --> 36:21.136 other half of the Wonder Twins and , 36:21.136 --> 36:23.358 and really it's on their shoulders that 36:23.358 --> 36:25.080 stood this up and it's just an 36:25.080 --> 36:26.413 incredible experience . 36:33.240 --> 36:35.351 Come visit us at the software factory 36:35.351 --> 36:37.462 booth , we're out of time . Thank you 36:37.462 --> 36:39.573 again for paying attention . I really 36:39.573 --> 36:38.700 appreciate it and sort of , thank you 36:38.700 --> 36:40.478 for that guest appearance . See 36:40.478 --> 36:40.550 everybody .