Industrial Talk is onsite at the OMG Quarterly Standards Meeting and chatting with Matt Wilson, Group Vice President with SimVentions about "Simulating, ingrating and transitioning new technologies for defense". Tune in and hear more about the importance of simulation and Matt's unique insights on this Industrial Talk.

Finally, get your exclusive free access to the Industrial Academy and a series on “Why You Need To Podcast” for Greater Success in 2023. All links designed for keeping you current in this rapidly changing Industrial Market. Learn! Grow! Enjoy!

MATT WILSON'S CONTACT INFORMATION:

Personal LinkedIn: https://www.linkedin.com/in/mattwilsonsimv/

Company LinkedIn: https://www.linkedin.com/company/simventions/

Company Website: https://www.simventions.com/

PODCAST VIDEO:

https://youtu.be/VOSrEV663Z0

THE STRATEGIC REASON "WHY YOU NEED TO PODCAST":

OTHER GREAT INDUSTRIAL RESOURCES:

NEOM: https://www.neom.com/en-us

AI Dash: https://www.aidash.com/

Hitachi Vantara: https://www.hitachivantara.com/en-us/home.html

Industrial Marketing Solutions:  https://industrialtalk.com/industrial-marketing/

Industrial Academy: https://industrialtalk.com/industrial-academy/

Industrial Dojo: https://industrialtalk.com/industrial_dojo/

We the 15: https://www.wethe15.org/

YOUR INDUSTRIAL DIGITAL TOOLBOX:

LifterLMS: Get One Month Free for $1 – https://lifterlms.com/

Active Campaign: Active Campaign Link

Social Jukebox: https://www.socialjukebox.com/

Industrial Academy (One Month Free Access And One Free License For Future Industrial Leader):

Business Beatitude the Book

PODCAST TRANSCRIPT:

standards, conversation, pipeline, omg, vendors, devops, matt, platform, software development, industrial, dev, software, wilson, people, sim, joining, tools, target rich environment, absolutely, deploy

00:03

Welcome to the industrial talk podcast with Scott Mackenzie. Scott is a passionate industry professional dedicated to transferring cutting edge industry focused innovations and trends while highlighting the men and women who keep the world moving. So put on your hard hat, grab your work boots, and let's go.

00:21

All right, thank you very much for joining us next installment of industrial talk. And thank you so much for your support. We are broadcasting here in Austin, Texas, it is the OMG meeting. And it is a collection of people that are smarter than me. And they are solving problems and they are having great conversations to make the world a better place. They are the heroes of this story. And you're gonna come and learn with me because well, my ears bleeding after whatever four days of having great conversations with incredible people passionate about standards and everything else in there. In the hot seat. We have a gentleman by the name of Matt Wilson. I butchered his name. And you're saying to yourself, Scott, how can you put your man Wilson's name? Well, I did. And it was somebody else's name. So that's his name. Anyway,

01:08

I'll answer to Michael mark. Matt, whatever you want to call me. You? Yeah,

01:12

SimVentions is the company. So let's get cracking. Great. Yeah. Sim mentions. I like simulation conversations.

01:20

Yes. They're like artificial conversations. They they approximate conversations, simulated conversations. And that well, people do online all the time these days. Pretty much. Yeah.

01:30

Wow. Look at you, man. Just get right into it.

01:33

You're absolutely right. And just offending everybody in the audience. Right. So

01:36

first conversation of Thursday, and he's right off the bat. But it's true. I just think every time I have the conversation about simulation and running simulations, and what however you do it, and being able to, to play in that. Just think it's cool. It's pretty neat. Give us the listeners and me, Matt Wilson, a little background on who you are

02:00

great. Well, I've been doing software development for 30 years or so. Doing a lot of work for the United States Navy and as a contractor for different defense sorts of things started out building software for the Aegis combat system. So I don't know what that is. But they gratulations big Navy ships, big Navy ships, thank you. And started getting involved doing the standards work related to trying to make those systems more open. So you're not just stuck with the way a certain vendor made it if I wanted to bring in capabilities from other vendors. Yeah. So the Navy brought me into the standards conversation about 20 years ago. So I've been doing software development and standards work for 20 years. And but now I'm getting, you know, some wisdom in my face here. So they don't let me write software anymore. I just, I just pontificate and the people

02:57

out there, chirpy chirp about all of this fun stuff? That's pretty cool, quite frankly, and you've been in the business for so many years, you've seen a lot of changes? I'll tell you that much.

03:07

Yeah, the irony is the more changes, the more it stays the same. So

03:11

why don't you expand upon that, because I have no idea what you mean by that, because I always see just changes and everything's just changing. And everybody's talking about new use cases. And using this tech.

03:23

People, people had the same problems today than we've had all along. So and the domain that got me here in the first place. You know, the Navy has been trying to open up their combat system to make things reusable for my entire career. So we've certainly made progress in that direction, but there's a lot more progress that can and should be made.

03:43

See my ears bleeding? I'm here, these conversations. I don't know how you guys handle it. I don't know, I'm not I'm not the gold standard by any stretch. I did stay at a Holiday Inn. And I heard Oh, no, no, go. But anyway. Okay, so you're here. OMG? Great. I mean, I've been very fascinated by just the process of how everybody sits there and debates and it has these great conversations

04:07

more patients than I do.

04:10

Trust me, it's, it's just been a fascinating observation. And then when he so when you guys leave, and then you're, then you come back for the q1 event, then then all this whole, you know, couple of months, and you guys just think more about it, and then it just never stops you guys got now we're supposed to be talking about and you're gonna have to, this is the dev sim ops event. This is 2023. Right? I don't even know what that is. So tell us

04:43

in that effort to open up the systems and build and deploy software and systems more rapidly. The industry basically if you do software development these days if you do modern software development these days you're probably doing some form of DevOps,

05:02

which is development operation. Yeah.

05:06

DevOps. So it's a pretty well coined term throughout software development, the industry. Hopefully most of the people reading this have read the Phoenix Project if you've not read the Phoenix Project.

05:16

Now, all of a sudden, I'm feeling Yes, I did. Yes, yeah, absolutely, I was gripped by the tail,

05:23

it's actually really interesting. It's not all geeky either. So they actually take a real story, that's cool. Well, it's a made up story, but it makes you understand what DevOps is about. So DevOps is pretty well established, there's, there's lots of vendors out there have DevOps pipelines, there's lots of tools in the space. And there's like, three, four, or five different main ways to do DevOps. And that's, that's the process of designing, building, creating, testing, and deploying software, using automated processes. And then to automatically deploy those software's into the production environment, and keep those running and updating. So if I realized, oh, this system needs an update, then I can very quickly do an update, run it through the development process, get it tested, and deploy it in real time. Well, the DoD is realized we really need to do, we need to embrace that more and more. And the way we develop software, instead of sitting down and thinking about getting all the requirements perfect before I do anything, and then spend three years building something, another two years testing it, and then finally delivering it to the fleet. There's there's desires and objectives out there, to do compile the combat and 24 hours. So it's, it's, it's a lofty goal. But if we're gonna get doable, you gotta do it. If we're gonna get anywhere close to that, we need to more thoroughly embrace DevOps in the in the DoD sector. But being DOD, you can't do it without security. It's got to be fully secure. It's got to be fully tested. So that's where they crammed the word SEC in the middle of DevOps. So that's why you got dev SEC sec. Security dev development, secure operations. Hey, go? Yeah, I'll see. See,

07:17

let me just put that down. It says my, so. So you just slipped in security in the middle of DevOps? That's what you did?

07:26

Yeah, I didn't, I didn't coined the phrase. No. Time, all of you out there doing it. I didn't. I'm not saying I coined this phrase.

07:37

Doesn't matter. So. So is this an event?

07:41

Yeah. So what we're trying to do as at the OMG, we tried to develop and create standards, to improve the state of practice, or provide consistency to the state of practice, and hopefully, enable interoperability and interchange of kinds of things. So I was talking earlier, you know, there are multiple major vendors of DEV SEC ops, tools and pipelines. But it's pretty much if I choose to go with with this vendors pipeline, I do a lot of work to configure the pipeline and get it working and get all the tools talking to one another and all the handoffs. But then my leadership says we can't afford to use that pipeline anymore. I want you to go and use this pipeline, because I've heard it's better. So all the work you did to set up this pipeline is now not compatible when I move over to this pipeline. So if we can start to look at an established technology standards to make it more consistent, if I need to move off of this vendors pipeline onto this vendors pipeline.

08:47

Okay. I have to I have to step in? Yes. Because I'm going to I, you know, what I have in my mind when you say pipeline, yeah, a pipeline? Yeah. Is that what you're talking about? Or what are you talking? Because I want to make sure this is clear, because I'm like, I've been out of a pipeline. In the field. There's a right away. Yeah. And there it is. There's not talking about it. Well,

09:10

it's the it's the coined term for the the process and the tools in the automated handoffs between each step in the process to get me from a an idea that I want to build to writing the code to do it to testing the code to getting it out the door and actually deploying it on to production. See, I

09:30

got that No, no, I'm all in good questions.

09:34

You should host like Lucia host interviews

09:40

with an idea because I like to be the, the not the sharpest guy in the room because I'm gonna ask that because I, I have all these interviews in my head and I'm going I'm like, I know what that is. Right there. That's an asset. I'm on the right away and we shut down all the plants. Exactly. But that's the truth. Yes, but I get I I understand the word pay If you're associated with DevOps and all of the steps that are in there, and you write if you, if you're down this and you're heading down this road, and you're making sure everything is connected, and you've got it from idea to actual operations over here, and then all of a sudden shipped over here. Yeah, that's not an easy

10:16

one. And your boss, or your leadership says, Well, you can't do it on this platform anymore, we need to move you over to this other pipeline. And all of that detailed, complicated work that you did get all the little pieces aligned. So it actually works. You got to, it's not complete redo, because you figured it out in one, but you got to re implement that in a totally different way on the other pipeline.

10:41

So so this, this 2023, Dev sim ops, or

10:45

SEC SEC ops,

10:49

company name, and I'm going oh,

10:50

my gosh, man, see here to throw you off.

10:53

Easy peasy to throw me off known. So this this dev SEC ops, focus standards, whatever the practice state, making it more efficient, making it more open. Right, yeah. And having those conversations around that effort. So that from my idea, to actual operations is compressed, right? Because you've got those standards there. And I can just like, okay, here.

11:23

Yep. And the standards will help. You know, it's a target rich environment. So let's say I'm a tool vendor, that's part of what my company does. We make novel tools, we do really cool and analytic things and stuff like that, if I make a software tool that can make a step in the pipeline better. If we have the standard in place, my tool will now work with, you know, I'm not going to name actual vendors, but vendor A's pipeline, vendor B's pipeline, piece pipeline, because because there's us clear technical definition of how do I get data out of the pipeline? Yeah. And how do I add value back to it? So that's one of the use cases, you know, that that's part of my motivation. So I got the broader motivation for everybody in general, but you know, standards are about business. See,

12:15

uh, now, I'm getting a clearer picture, oh, my gosh, I'm dangerous. No, I'm not dangerous. But I am getting, if you have standards that everybody sort of embrace and say, Yes, and and what happens here at OMG, where you get in a room, you actually physically get in a room and you begin to debate and you get to discuss and you develop these standards. But in light of that, with that competence, with that assurance that these standards have been thoroughly vetted, then it creates a greater likelihood that they can be used in other platforms, and therefore making the shift easier. And so And correct me if I'm wrong, if I'm a platform, platform person, I would want these standards so that it make it easier for people to use my platform. But then it also makes it easier for me to they leave my platform.

13:08

Oh, the irony there is, is, you know, perhaps some vendors might say, well, if I if I standardize, you know, people aren't going to be stuck in my platform. And, you know, yeah, it is. I think that but it's often the opposite happens, you know, so if I know that, that you conform and in comply with the standards, I'm more comfortable using your product, and I probably more likely to buy your product, because I know I'm not stuck with you. Not that, you know, it's a bad thing. You're no i But it gives me the confidence that if I ever needed to. I could move.

13:45

Yeah, but but it also gives me the competent that there's the one I got the standards, but to there is a level of scalability, right? I can stick with that platform, because I know that right there. They embrace the standards, whatever it might be, right. And it's open. And so it doesn't sort of then it doesn't just sort of pigeonhole me into one way. And I don't want to think about that. It just gives me the greatest flexibility. And it seems that that there's a beauty and simplicity to a certain extent. I'm not saying that standards are simple by no means right. I'm just saying that it's a it's a good thing that they are applied. And I can feel confident in that. Exactly.

14:27

Exactly. So what we're trying to do with this, this event in March 2023,

14:34

also Q this is q one,

14:37

technology OMG technical meeting in March in q1. Yeah. So that'll be in Reston, Virginia, in Virginia. Yeah. We're trying to bring together kind of the thought leaders in the people do this for a living and the people who are really struggling with the problems of not having the standards. We're trying to bring everybody together into one room. I'm going to have a conversation because it is a target rich environment. If you think about just the handful of steps I've described to you, yeah, we could, we could come up with a standard that's, you know, 20,000 pages long and doesn't help anybody. Yeah. So we want to start that conversation and say, How can a standards body like the LMG come alongside and bring you into this conversation? Because it's a coalition of the willing who define the standards. We want to draw people into the conversation, to actually start working on the pieces of the puzzle that will add the most value to this marketplace, see,

15:37

and this, this goes across all the consortiums. Once you have that standard, whatever that conversation is, it impacts you know, digital twin, and then everybody absolutely responsible computing, you name it, and it does, right. So if somebody's listening to this, and they say, Yeah, that sounds like a pretty cool thing. Can Can I? How do they how do they

16:02...