Before we get started, do you have any questions for me? Anything? – As long as everything looks in place, I don’t have like a bug hanging, something I dunno (laughs) (upbeat music). Hi, I’m Andrew Kemendo, Chief Technology Officer here at Kessel Run, and I’ll be tackling some of the most common questions and misconceptions about Kessel Run. Here we go. (upbeat music). Is Kessel Run a private company? Actually, I get this one more frequently than I would like. – You serious? – No, Kessel Run is not a private company. We are a blended acquisitions and operations unit. – It’s the best of both worlds. – Organized under the Air ForceLife Cycle Management Center under Air Force Materiel Command. We have a mix of uniformed military, civilians like myself, and contract personnel, all dedicated to the mission of delivering fantastic technology transformation to our programs. Next question, let’s see what we got here. What is a software factory?
I don’t think you miss what you think to miss. – No, I don’t know what a software factory is. Somebody decided that they wanted to call Kessel Run a software factory, and that started growing toa lot of the other software pathways, pathfinders, experiments that are happening across the Air Force a bit prematurely, we think. And it’s hard to collapse everything that all of our different groups are doing into one software factory concept because if you look at each of them, they’re all very different. – Same, same, but different. – We run a global infrastructure. We also build software that does not necessarily translate when you’re trying to compare different groups. Kessel Run writes software. Well, nobody writes software. You’re ordained and transmitted this divine inspiration in code. – Ugh! – In fact, Kessel Run probably spends about 10% of our time as an organization writing code. – Whaaaaaaaat?! – The rest of it is building hardware deploying that hardware to many different worldwide operating locations.
Worldwide, wide, wide, wide- (chuckles) – Building contracts, making large-scale acquisitions, managing programs at the programmatic level, investigations into all of the different personal security, operational security, cybersecurity, and then we build software. – Investors. Possibly you.- Possibly you. We build, and we run, and we secure, and we maintain and reiterate on technology for the United States Air Force. That’s what we do. Does Kessel Run build software just for anyone? Unfortunately, the answer is no. – No, No, No. – We are restricted legally from what’s effectively working on programs that we’re not funded for by Congress – Bummer. – So what we’re officially the program for are the Air Operations CenterFalconer weapon system, the F-35 maintenance information system – Wait! (indistinct) – Air force modeling and simulation capabilities, not all of them but a big chunk of them utilized across the Air Operations Centers worldwide and for testing. And about a dozen other smaller programs that span from command and control all the way through intelligence mission sets.
We don’t just build whatever software anybody wants to build for the Air Force because they decided it was a good idea. That’s where other organizations and other software factories in groups come in. All right, is Kessel Run a part, is Kessel Run apart of AdvancedBattle Management Systems? We’ve been working with the ABMS folks since they stood up and have had a great relationship. Kessel Run is not part organizationally of ABMS, especially as it’s transitioning into its new program office. Is Kessel Run a part of Platform One? Well, we’re not a part of Platform One either. Again, we work alongside Platform One. We work with some of their technologies and utilize them where necessary, but we are not organizationally part of Platform One. Why is Kessel Run building a platform? That’s a good question, and one I get a lot actually. Well, the answer is cause we had to, frankly. – But why? – Back in 2017, KesselRun was just an experiment; it was a software pathfinder trying to figure out how the Air Force can make software acquisitions differently or if we can bring the building of software back in-house. Not long after, in 2018, our combatant commanders and our customers really were demanding that the software that we were delivering be more resilient and be worldwide available.
You have to understand if you want to iterate on the software, you have to have a great network. You have to have great hardware. You have to have people who are there more or less 24-7 to fix bugs and do whatever needs to be done to deliver great world winning software. And so we had to start building that, and we did, and we never looked back. – Excellent (electronic guitar music).
All right, plowing ahead is old, Billy burst says (laughs) Oh man, this is one of my favorites. I had a general officer ask me this, and I had to sit there. – Hmm. – I’ll answer it now. Isn’t DevOps just software developers working with military operators? So- – Google it! Google it! Google it! – DevOps really is about bringing software development and IT operations together, whereas previously there were somewhat separated.
It wasn’t always the case, but you’d have some people out there developing software; they’d do some testing. And then when it came to running it and actually getting into the user’s hands, they’d send them a disc. Basically, you get a manual may be or if not, you’re just kind of on your own how to do it. That’s when development and operations were separated. In the last about 15 years, developers work alongside the IT operators. – What? – Did we just become best friends? – Yeah. To make sure that there’s a continuous-delivery of software and continuous integration between what is actually being built and was actually being used in the field and troubleshooting that back and forth. DevSecOps adds security to the whole mix.