00;00;00;06 - 00;00;02;20 Alex Technically speaking. 00;00;02;22 - 00;00;05;18 Chelsie Welcome to our technically UN technical Technology talk 00;00;05;20 - 00;00;07;25 Alex A NIWC Atlantic production. 00;00;07;28 - 00;00;14;26 Joe And an award winning podcast with your hosts, Chelsie Holloway and Alex Jackson. 00;00;14;28 - 00;00;21;12 Chelsie So, Alex, I've discovered a brand new talent that my three year old has. He's going to be an amazing soccer player. I can tell. 00;00;21;12 - 00;00;22;15 Alex That's really exciting. 00;00;22;17 - 00;00;43;03 Chelsie It's very exciting. Now, granted, I'm biased. I'm his mom, but he's just signed up for the league. I know Joe, but he's so talented. So we did sign up for him for this, like, clinical three year old little soccer, like, league thing every weekend. I don't know, I'm new to this, this whole sport thing, but he's doing amazing. 00;00;43;03 - 00;00;59;12 Chelsie He's not afraid of the ball. He's. They call him a little killer on the team because he'll just go after it. And he scores so many goals. And. Yeah. So I'm a proud mama for my son's newfound skills with soccer. And he doesn't get tired. It drives me insane. 00;00;59;15 - 00;01;01;14 Alex You're the quintessential soccer mom. 00;01;01;16 - 00;01;04;00 Joe You'll be a good soccer mom, for sure. 00;01;04;03 - 00;01;12;06 Chelsie We'll see. So that's been my weekends lately. Is, going to soccer Saturday mornings. How have you been, Alex? What have you been up to? 00;01;12;07 - 00;01;34;06 Alex I'm doing pretty well. Just got back from, celebrating my grandmother's 80th birthday, so that was a lot of fun. And Georgia with the family and friends. So we had a great time and ate some really good food. So, I'm glad to, sort of be back at home and relaxing and sort of catching up from all the, the craziness over the weekend. 00;01;34;08 - 00;01;40;20 Chelsie 88 that's that's a milestone. That's great. So how did you celebrate? You cooked at home and what else did you do? 00;01;40;21 - 00;01;46;15 Alex We went out to eat at a restaurant and got to celebrate her. And so the love that everyone has for us, that was a really great time. 00;01;46;15 - 00;02;13;01 Chelsie Oh that's amazing. All right. So what do we have coming up for this episode? We've got chemistry models, creativity, but not the way you may be thinking. So we're going to be chatting with two charismatic guys. And the chemistry between them is undeniable. They're here to tell us about model based systems engineering. And I like Atlantic and the creative ways their teams have come up with information warfare solutions for the warfighter. 00;02;13;05 - 00;02;15;22 Chelsie Chemistry models, creativity. You get it, Alex? 00;02;15;22 - 00;02;41;27 Alex Yep, I like that. We had a great discussion with Po Digital Deputy Director of Architecture Caleb Scott, and now with Atlantic Lead Systems engineer Paul Walter about the recent milestones from MSI. Then we have a special military moment interview featuring now we get Linux, newly pinned Chief Petty officers hosted by our very own Public Affairs teammate Jerry sarcastic. 00;02;42;00 - 00;02;46;03 Alex So get comfy, turn up that volume and let's get started. 00;02;46;05 - 00;02;58;22 Chelsie So welcome to the podcast. We're going to be talking about some wonderful things happening in model based systems engineering here at Iowa Atlantic. But before we get into that, can you each please introduce yourselves by name and position? 00;02;58;28 - 00;03;12;17 Caleb Hi, everybody. This is Caleb Scott. I am the acting director of architecture for Poe Digital, but I am a network land employee working in the system of systems engineering competency. 00;03;12;22 - 00;03;21;17 Paul Everybody, I'm Paul Walter. I'm the lead systems engineer for our systems of systems engineering competency. I'm also the digital engineering champion for Narvik Atlantic. 00;03;21;18 - 00;03;38;20 Chelsie Wonderful. Thanks for coming on with us. And let's jump right into it. But first we just need to explain the work that MSC does at Niwa. Caitlin. So if you guys could just jump in and kind of give everyone a lay out who has no idea what MSC is and what we do, it navigate landing. 00;03;38;21 - 00;03;59;23 Paul Yeah. Sure thing. Got to provide a little bit of context. First, it's important to understand that doing MSC is just about doing systems engineering in a smarter way. And systems engineering is all about engineering. Complex systems across lots of different engineering disciplines, across an entire systems lifecycle in order to meet the user's needs and other stakeholders needs. 00;03;59;26 - 00;04;22;03 Paul MSC is just a more advanced way to do systems engineering by taking a model based approach using legacy systems engineering methods like writing up test plans in a word document or managing requirements in a Microsoft Excel file. Those sorts of things are insufficient to manage the complexity that we see in our information technology systems. So traditional systems engineering relies heavily on managing all these documents. 00;04;22;03 - 00;04;48;11 Paul And managing all those documents creates a lot of inefficiencies. A lot of change control issues. It's just super inefficient. And so now, like at Lanark, we really started taking this seriously about eight years ago. So 2017 was when we developed our first MSI technical focus area strategy. And so over the last eight years, we've actually implemented a number of different multi-year strategies aimed at really implementing MSI across the entire command and really adopting. 00;04;48;11 - 00;05;07;18 Chelsie So we're going to get more into that a little bit down the road when we talk. Yes, absolutely. So basically what and tell me if I'm simplifying this a little too much, but you guys are creating software or a set of applications that meet a need, and you're creating speed through a single tool based on what you need to make. 00;05;07;21 - 00;05;09;12 Chelsie Is that kind of it? 00;05;09;19 - 00;05;36;11 Paul The second part is true. The first part is only partially true. So okay, so software engineering is engineering software solutions. Systems engineering is a broader discipline which is really about integrating software engineering, electrical engineering, mechanical engineering, and all different forms of engineering in order to meet the needs. So it's a very cross-disciplinary function. So when we talk about MSI, you know, we're talking about capturing requirements from customers and translating that into the design. 00;05;36;13 - 00;05;40;13 Paul And then how we build it, how we test it and turn it over to the to the customer. 00;05;40;16 - 00;05;51;15 Alex Perfect. Explaining that process of the whole lifecycle of of the MSI. Can you give us some examples of what you all do, within Network Atlantic and helping your customers? 00;05;51;21 - 00;06;15;22 Paul Absolutely. We've collected several dozen success stories that we've recorded and videos, where we've captured objective return on investment metrics on to get a feedback loop. Hey, how are we doing with this? Is are we achieving some of the value that we we know is inherent to doing MSI? But give example, like with military construction projects like we call million projects, you know, we have to assess what systems the networks are going to need to go into. 00;06;15;22 - 00;06;37;10 Paul Like I say, a command center, environment or operations center, how the site's going to talk to other sites. And we, we need a way to pull this data together. So using MSI and working in a single model has allowed us to go a lot faster. So if you make a change in one place in your model and that changes reflected other places in the model, that system component or that requirement shows up. 00;06;37;13 - 00;06;54;23 Paul So if we try to connect two systems or components or command centers together that can't actually talk to each other like an MSI tool won't let you do that, it will flag it and say, hey, you know, the information flows between these two things. Do not connect these two devices. Do not talk. If you're using PowerPoint or Visio or tools like that, they're going to allow you to make those mistakes. 00;06;54;23 - 00;07;00;26 Paul They're not going to tell you you do anything wrong because there's no technical data underneath those two blocks that are there touching each other. 00;07;00;29 - 00;07;06;09 Alex So that saves time in terms of like knowing what could go wrong. If you had gone forward with that. Correct. 00;07;06;12 - 00;07;09;19 Paul It saves it saves time. But also reduces technical risk. 00;07;09;21 - 00;07;37;18 Caleb Yeah. And I like examples that aren't engineering examples per se to kind of make things make a little more sense to people that maybe are coming in from outside of that perspective. So, a virtual show of hands, Amazon Prime, members. Right. Everybody, like on the face of the earth. So if you have you ever gone in to Amazon and looked for like, like a light bulb for your car? 00;07;37;20 - 00;08;04;02 Caleb One of the things that it asks you to do is put in a whole bunch of information about your car to make sure that it finds compatible things for that car, and it shows your results that says, hey, these fit, and maybe specifically these fit in these places. So if you think about the transition from traditional systems engineering to model based, traditional systems engineering would have said, you need to know what the part number needs to be. 00;08;04;02 - 00;08;20;13 Caleb So you need to look that up somewhere. And then you need to go to Amazon and you need to take that part number, put it in the search and find it. And then you need to double check that it's the right one that returned the search. Now model based. It says, hey, we're going to put this all in one place. 00;08;20;15 - 00;08;47;16 Caleb You're going to give us the information you need. It's going to go through this back end that's really taking all of those different information sources and putting them together, and it's going to give you the result you need faster with fewer errors. And that's really what we're doing for our customers is we're we're working to take these manual processes where you have to keep things manually aligned and automate it. 00;08;47;19 - 00;08;55;05 Caleb And, kind of merge it so that you can get those answers with higher reliability. You can trust them. 00;08;55;05 - 00;09;19;24 Chelsie And one of your customers is the warfighter, right. And from what I understand, your skills and what you do affects everything from email to reconnaissance, from what the Navy could use, model based systems engineering for. And, it's a way for warfighters to have reliable networks. And it is not only more efficient, but it has saved the government money. 00;09;19;27 - 00;09;21;20 Chelsie Would you agree with all of those statements? 00;09;21;20 - 00;09;39;26 Paul Yeah, absolutely. So like I talked about, there's there's so much less manual administrative work being done that it really reduces the cost, the time, the risk on any project where we're engineering systems for any type of application, whether we're talking about the things you just mentioned and beyond. So our focus isn't on a particular type of program or a particular type of system. 00;09;39;26 - 00;10;02;20 Paul It's on all systems. And the more complex the systems are, the more beneficial it is to take this sort of approach. So we've experienced multi-million dollar savings by applying model based methods to projects where we're integrating IT systems and networks into, for example, the military construction efforts I was talking about. I mean, we have evidence of that. Another example actually is one that Caleb and I worked on together called the Target Enterprise Architecture. 00;10;02;22 - 00;10;19;25 Paul And that's where the Navy has a few hundred disparate networks. If you didn't know that, and they need to assess where they could consolidate their services and applications. So we always see lots of, hey, we got to consolidate all of our data centers or all of our networks or all of our applications or whatever, and this was one of those network convergence examples. 00;10;19;25 - 00;10;38;07 Paul And so what we did was we pulled all the data, regarding Navy networks, their applications, and put it into a single model and were able to do analyzes and auto generate reports for all those networks, for all those commands that that owned those networks, and that enabled the Navy to make smarter decisions regarding the consolidation of our network capabilities. 00;10;38;09 - 00;10;46;00 Paul So we even got an award this past year, the Don IT Excellence Award for our application of MSI in support of network modernization and convergence. 00;10;46;01 - 00;11;06;29 Chelsie Another milestone you reach. We're going to slide right into this. Let's talk about it. MSC has become a core proficiency at Nomic Atlantic, which is a very big deal here. And so let's kind of explain why that so important. And we went from a technical focus area to a core proficiency. What does that mean for you guys. What does that mean to the audience who has no idea what I'm talking about. 00;11;07;01 - 00;11;28;21 Caleb So transitions of initiatives and focus areas. Right. To core proficiency is, is always kind of a fun thing. It's kind of a little bit like graduating from high school, but not like graduating from middle school or elementary school, because that is not a real thing. I just want to I just want the listeners to understand that is that is not real. 00;11;28;24 - 00;11;59;02 Caleb Sorry, but we we just we invested a significant amount of time, energy funding, really just embracing what the Department of Defense and the Department of the Navy had mandated as this call to adopt model based practices, and more specifically, the shift, you know, this graduation, if you will, from a TFA to a core proficiency, it really marks the establishment of those skills and behaviors as something that we're doing that self-sustaining. 00;11;59;05 - 00;12;06;11 Caleb So it's no longer this thing that you have to keep feeding because otherwise it'll starve to death, right? 00;12;06;13 - 00;12;28;19 Chelsie It's showing, that you guys are reliable, like you're saying, and you can take on larger projects, you can solve harder problems. You've established yourself. And I can link to a degree that you have shown everyone that you've accomplished this success. Now, give us the work that we can do because we've got this. I love how you said about the high school graduation, though. 00;12;28;21 - 00;12;45;29 Chelsie Because once people have graduated high school, you don't have to feed them like you're saying. They've got the knowledge. They've at least got the basics anyway, right? And they can take on harder problems. And that's kind of like a core proficiency. Maybe you want to compare it to maybe getting a master's or a doctorate, because you guys are super smart. 00;12;46;03 - 00;12;50;27 Chelsie So that could be something that we can do. But yeah, I think that's a great way. 00;12;50;27 - 00;13;09;29 Paul It is a good analogy. And, you know, the reality is when you're going through school, you're you're learning all the time, you're getting smarter and you're able to do more and more throughout the years. And when you graduate from high school, it's a big milestone. So it's just that it's a milestone. So so the reality is, is that we've had the opportunity to work on harder and harder projects over the years, and we've done more and more work. 00;13;09;29 - 00;13;21;03 Paul And so it's been a progressive thing, of course. But it's been it's cool to, to kind of be able to take this on, to reflect back and say, well, we have actually grown quite a bit, you know, in eight years. 00;13;21;06 - 00;13;30;01 Alex You've spoken about the milestones over the last eight years. Can you tell me a little bit about the growth that you all have seen from the very beginning to, to now? 00;13;30;04 - 00;13;52;22 Paul Absolutely. Yeah. There's lots of ways to characterize the growth toward MSI as a core proficiency. You know, if you go back to 2017, we had less than ten people in the whole command, that were doing MSI to any degree. Fast forward to now, we've got several hundred people who are not only trained in MSI but are actively performing, you know, MSI type of practices. 00;13;52;24 - 00;14;12;25 Paul Another another statistic is we have about 100 integrated product teams in the command. And if you go back to 2017, we had one we had the mission engineering team that was doing anything that might resemble MSI. Now we are at 80% of our IP or integrated product teams that that do some form of engineering are actually applying model based practices to engineering in some way, shape or form. 00;14;13;01 - 00;14;13;19 Chelsie It's great. 00;14;13;19 - 00;14;29;22 Paul Yeah. And then since we set up our model based, system centric community of interest in 2017, we've had 50 to 60 community events. We've had ten different model based engineering challenges of different sorts, some internal with the government, some with industry. And our. 00;14;29;27 - 00;14;36;05 Chelsie About those challenges and what they're okay. Yeah. And why they're important. So can you kind of explain that a little bit more. 00;14;36;07 - 00;14;41;19 Paul Yeah, sure. So I think we could do a whole podcast just on digital engineering challenges. But it's funny. 00;14;41;22 - 00;14;44;01 Caleb And Paul's love of metrics. 00;14;44;04 - 00;14;44;16 Paul Yes. 00;14;44;16 - 00;14;48;14 Caleb I don't know if you've picked up on the numbers. He likes to drop numbers. 00;14;48;16 - 00;14;50;15 Paul That's good for the numbers. 00;14;50;15 - 00;14;55;02 Chelsie We need that data to kind of make that point to show how awesome we are. So that's great, right? 00;14;55;02 - 00;14;58;23 Caleb Chelsea? Well, have I got time for you. 00;14;58;25 - 00;15;00;16 Chelsie But challenges. Let's talk about those. 00;15;00;16 - 00;15;18;12 Paul Yes. So if we go back to right before the pandemic kind of had us teleworking a lot. January 20th, 20, Caleb and, another guy named Peyton Cab Rock in Iowa. We're working very closely together on all this digital engineering stuff. And Peyton walked in and said, hey, we should do some sort of challenge, some sort of MSK challenge. 00;15;18;14 - 00;15;43;24 Paul And so I said, oh, I've been thinking something similar. Caleb, Caleb's in the next office over. Come in here. Let's talk about this. And so, we had an hour long conversation where we brainstormed, doing an MSK challenge, and we said, what we want to do is we want to provide a way for people to innovate their MSK practices and give them hard problems to solve, and then just give them some space, some time, a little bit of funding to go and solve those problems. 00;15;44;01 - 00;16;05;24 Paul So we were able to acquire a little bit of overhead funding to do an MSK challenge back in early 2020. And what we did was we we just kind of went to our leadership in the command and said, hey, what are some hard problems that we're facing? And we publish those hard problems to the workforce. And we said, hey, form will be what I asked you to do is go form teams to go and try to solve these hard problems using MSI. 00;16;05;26 - 00;16;27;22 Paul And so what they came back with in that first challenge just blew us away. And so what that has resulted in is we've done ten challenges now, eight eight government to industry. And we do them twice a year. And we've expanded the concepts to applying model based practices to all forms of engineering. So we've seen lots of innovative use of, artificial intelligence, all forms of advanced modeling. 00;16;27;24 - 00;16;47;27 Paul We've seen stuff at higher classification levels to solve super hard problems that are really relevant to what's going on in the world. We have seen the integration of all sorts of tools and the beauty of it is, is that when one team comes together to solve an innovative problem for really small costs and not too much time, what happens is everybody gets to see the benefits of what they did. 00;16;47;27 - 00;17;02;21 Paul They get to learn the same some of the same lessons that team has learned and what I love to see, and I've seen it dozens and dozens of times, is one team does something and then other teams will pick up on it. And so they'll they'll go pick up that practice. They'll go pick up the use of a particular plug in or a tool. 00;17;02;24 - 00;17;11;17 Paul They'll start to leverage some integration between tools. And you get this exponential growth in terms of people learning how to do engineering better. You also get. 00;17;11;22 - 00;17;24;04 Chelsie These challenges like they not only provide solutions, but it sounds like they're creating motivation and collaboration. Just among the engineers. And the scientists within your guys is different teams 100%. 00;17;24;04 - 00;17;41;20 Paul We've had we've had almost 100 teams submit proposals to compete, and each of those teams is made up of, you know, a handful of people. So a lot of people have been in the mix. The people who compete in these challenges, they're coming from the financial community. They're coming from the software development community, from cybersecurity, from the data science and analytics, from you name a network. 00;17;41;20 - 00;17;59;02 Paul So it's a very these teams are very diverse in terms of the, their composition and the approaches that they're taking. So that what started off as an MSI challenge focus on how do you do systems engineering smarter has just grown and blossomed into this all kinds of innovation in the engineering space. 00;17;59;04 - 00;18;29;21 Caleb Well, you mentioned the the idea of motivation. I'm going to get fact checked on this, but I believe it's Google that actually has these opportunities. Are windows of time set aside for their staff to work on something that they want to work on, something that kind of speaks to them, that they're like, you know what? I'd really like to explore is this kind of, if you want to call them science projects, you can. 00;18;29;21 - 00;18;53;21 Caleb But the challenge, you know, the MSI challenge that became the digital Engineering challenge, really kind of borrowed from that idea that there were things that the workforce really wanted to be able to explore. And actually, a few of our challenges have been carte blanche. Challenges. Bring your own problem statement and just give them a blank card, right? 00;18;53;21 - 00;19;18;10 Caleb Just go for it. Bring your own problem statement in your own solution. You get to be the arson and the firefighter all at once, right? Like you, you break it and fix it. So it's been really interesting seeing what they bring because in some cases they bring problems that we're very aware of, very familiar with. But in other cases they come with things that honestly hadn't really risen to the level of visibility that we had. 00;19;18;12 - 00;19;38;12 Alex It brings along an opportunity to find these creative solutions to some problems that some people may not have thought about. And so it's very, innovative in that approach. Can you all explain how that makes you all feel the passion that you all have to be able to solve these problems? And how is that fulfilling to your day to day lives? 00;19;38;15 - 00;19;55;07 Caleb Oh, man. You know, I'm not always the most creative, when it comes to some of these problem solving things. So actually, one of the most fulfilling parts about this job is working with Paul because he's he's like my spirit animal or my spirit. 00;19;55;07 - 00;19;56;28 Chelsie What's going on, person. 00;19;57;01 - 00;19;57;20 Speaker 6 Well. 00;19;57;22 - 00;20;32;04 Caleb I you know that. Okay. But before you want to read title this podcast and the bromance, I want to explain that like I'm happiest personally when I'm helping people solve problems. For me, it's been incredibly rewarding just just to be able to have what I would really call a a front row seat to problem solving. Because I don't want to take anything away from the teams that are there with the problems, because really, truly, they're the ones that are solving the problems. 00;20;32;06 - 00;20;40;07 Caleb We're just helping them find the resources, see the things, you know, consider stuff from a different angle. 00;20;40;10 - 00;21;04;05 Paul Yeah, we have a brilliant workforce in this organization, and many of us are heads down trying to develop whatever solutions we are for the warfighter. And that is good. But what we're focusing on is how do we get more out of our workforce? By connecting people, connecting ideas, you know, taking these problems, these hard problems and getting them in the hands of people who can go solve them. 00;21;04;05 - 00;21;11;28 Paul What if the problem that I could be solving better would be the problem that Chelsea knows more about? And so connecting people, connecting ideas, connecting my. 00;21;11;28 - 00;21;31;11 Chelsie Way out it. You guys are such good champions for our workforce. I love hearing that, and I love hearing that you like to solve problems, because I doubt we'll run out of any proof of problems to solve, especially especially when we're talking about our warfighters. We've got to have their back. So it sounds like you guys have great stamina around your job. 00;21;31;11 - 00;21;34;08 Chelsie I love hearing it, and I love hearing your support about the workforce. 00;21;34;10 - 00;21;39;20 Alex We thank you guys for joining us on the podcast, and thanks for sharing your wealth of knowledge with our audience. 00;21;39;20 - 00;21;40;24 Paul Thank you, Alex and Chelsea. 00;21;40;29 - 00;21;42;24 Caleb Thanks so. 00;21;42;26 - 00;21;56;17 Speaker 2 So fun chatting with them. Alex and I definitely understand better now how influential MSI is in like streamlining the processes that we have to provide all of these solutions for our warfighters. 00;21;56;17 - 00;22;23;22 Alex Yes, it was great talking with them and learning a lot about what MSI is. Now let's jump into our military moment where our Public affairs teammate Jerry Sekerak sits down with three recently promoted active duty sailors who put on the revered rank of chief petty officer. He guides us through a powerful conversation with chief information systems technicians Tess Tharp and Matthew Gross, up and Chief logistics specialist Darian Adams. 00;22;23;25 - 00;22;24;27 Alex Hi. 00;22;25;00 - 00;22;54;07 Jerry How are you doing, Chiefs? Congratulations again. Let's start with the moment that you were pinned. What was going through your mind as you received the anchor? Who wants to take that one? I can take that one. Jerry. For sure. It was completely emotional process. I mean, at the time, you're tired mentally and emotionally, like, just exhausted. But then you look up, you look out in the crowd, everybody there in front of you, your family, your new brothers and sisters in the chief's mess. 00;22;54;07 - 00;23;20;10 Jerry And it's just in that moment. It's just everything washed away. It's pure pride. It's a great feeling. And it's great reaching that pinnacle and receiving the anchors. One of the greatest feelings in the world. Thanks, Matthew. Darian. Now, one for you. As you know, the Navy is the only service that designates E-7 as chief. How does that distinction feel now that you've crossed that threshold? 00;23;20;12 - 00;23;38;29 Jerry As I look back and think of my older chiefs and how the interactions were done, the phrase comes to mind as the chief because they you ask a chief, it gets done. There's no question about it. Now that I'm on this side of the fence, I see what the mess really is. And as a family, they are someone that you will always be able to depend on. 00;23;39;02 - 00;24;03;22 Jerry From this day forward and even looking back, you can always count on the chief. So now I know I can be that chief and make sure the job gets done. Absolutely. You're talking about networking, which is probably the biggest tool in the chief's tool bag. Great point Tess, over to you for this one. What part of the induction process challenged you the most and what did it teach you about leadership? 00;24;03;25 - 00;24;13;05 Speaker 6 The big challenge for me during the induction process was being vulnerable and not being afraid of asking for help. 00;24;13;05 - 00;24;14;23 Speaker 2 When I needed it. 00;24;14;25 - 00;24;20;05 Speaker 6 Leaning on the mess when I needed them, reaching out to my brothers and sisters in the mess, and that there was no. 00;24;20;05 - 00;24;21;27 Speaker 2 Judgment from them. 00;24;21;29 - 00;24;45;23 Speaker 6 It definitely taught me that it's important to ask for help, no matter what the situation is, because we're all humans and nobody, no matter who is perfect. Definitely not going to argue that one. Also, a great point to us. Thanks. Okay, well, we don't have a lot of time left and we're looking at the finish line. So I'm going to pass this one to all of you. 00;24;45;25 - 00;25;12;06 Speaker 6 So briefly. If you could say one thing to the junior sailors that are watching or in this case, listening to your journey, what would you want them to know about earning that anchor? We'll start with you, Matthew. Start being that leader now. Like, take care of those below you and those around you, okay, Tess, definitely staying true to yourself. 00;25;12;12 - 00;25;36;22 Speaker 6 Don't change who you are for anyone or any part of the process. If you're a good send class, first class, third class, you're going to be a good chief. And Darian, my my advice for junior sailors everything is a lesson. Whether there's someone in your leadership you cannot stand or someone you absolutely love, they will teach you something. 00;25;36;25 - 00;25;55;01 Speaker 6 Emulate the traits that you think are the best, and do whatever you can to be that good leader and not like the leadership. You couldn't stand all good stuff. Well, I wish we had more time, but we're pretty much at our limit right now. So thanks Chiefs and best to you as you move on with your new role. 00;25;55;03 - 00;26;04;22 Speaker 6 So with that, I'll turn it back to our host, Chelsie and Alex. Thank you both for letting me share this moment with these outstanding new leaders. 00;26;04;25 - 00;26;13;06 Alex That was a great chat with some accomplished new Chiefs. And we thank Jerry for taking the time to sit down with them at our Hampton Roads, Virginia location. 00;26;13;12 - 00;26;24;14 Speaker 2 Milestones all around for this episode. Alex, from your grandmother to MEAC to these brand new chiefs, I love it when we can chat about milestones on this podcast. 00;26;24;16 - 00;26;28;19 Alex Those are some great wins for the team and for our family. So this is really good news. 00;26;28;21 - 00;26;29;23 Joe For soccer player. 00;26;29;24 - 00;26;42;08 Chelsie That's right. Absolutely. That's awesome. All right. As always, to learn more about anything we've mentioned in this podcast, check out our social medias under Nap or our Narvik Atlantic website. Links are in the description. 00;26;42;08 - 00;26;54;26 Alex This wraps up another great episode. As always, we thank you for listening. If you have a story that you think should be included in this podcast, please contact us at our Public Affairs email address which is listed in the description. 00;26;55;03 - 00;27;12;08 Chelsie Naval Information Warfare Center Atlantic, also known as DeWitt, is the East Coast branch of the Naval Information Warfare Systems Command within the Department of the Navy, we develop a range of technologies that provide state of the art capabilities to the United States military.