Hello, everyone, and welcome to another episode of the Genesis podcast brought to you by Genesis Aero systems. I'm your host Daniel Littwin, the voice of b to b, and folks thanks so much for joining us on this video conversation. Before we get into the meet of the episode. I want to make sure that you've got access to all of our previous conversations and some relevant supplemental information. So make sure you're heading to our website, Genesis dash aero systems dot com. Again, that's Genesis with a y dash aero systems dot com. You'll find plenty of other video conversations, white papers, blogs, resources, and information about our solutions and services there on the site. Alright. Let's jump into the meat of the episode. So on today's episode, we're going to give you all a crash course On the fundamentals of integrated modular avionics or IMA, which are today's standards for real time centralized aircraft processing units, and will also be giving you a crash course on modular open systems approach or MoSA, which is the standard technical and business strategy deployed even by the DOD for the implementation of Open Systems. So we've got a panel here with us today that's going to help us discuss the basic principles and key components of IMA and Mosa. Where they're different in scope and where they're interconnected. We'll also be breaking down the use of, for example, airing six fifty three embedded, partitioned operating systems, and the FAA TSO one fifty three classes of IMA. Avionics devices. So let's get into it, the high level and the highly technical. Here to help us understand these ecosystems of modular systems, I'm pleased to welcome our three Genesis Aero System, guests. First up, mister Scott Evers, director of programs and customer support. Scott. Great to have you here. How you doing? Glad to be here. Thanks, doing great. Yeah, real pleasure. We're also joined by Gordon Pratt, cofounder of the company, Gordon. How you doing? Great. Great to be as well. Yeah, man. Thank you for joining us. And last but not least, mister John Fulanczyk. He is director of business development at Genesis. Great to have you, John. How are you doing? I'm doing well down there. Thank you. Good to be here. Fantastic. So thanks again to Scott Gordon and John for joining us here on the podcast. Got quite a lot to cover, so I want to jump right into it. Gordon, my first question is for you. Let's just draw the distinction a little clearly, what is the difference between MoSA and IMA? Break that down for us. Sure, Daniel. IMA Integrated Modular avionics is a technology or a product, whereas MoSA, the modular Open Systems approach is a design philosophy. Right. So Moza, like the DOD uses Moza to to specify how it's going to design systems. And then once they have that design, it may or may not include an IMA type device in it. Whereas an IMA device being integrated, modular avionics can have software functions, hardware functions. They can be all residing in one box. They can be in different parts of the aircraft. But the point is that they're all tightly connected. Now, Scott, for you, I know there are, you know, obviously, a lot of different kinds of avionics systems or not just one standard or, you know, even one way to define which buckets of, you know, aircraft solutions actually categorize themselves as avionics. So where does IMA differ from conventional avionics and sort of the current suite of what gets categorized as avionics equipment. Okay. Sure. As Gordon mentioned, the the traditional avionics are are more distributed, a bunch of different hardware, each having their own functionality dedicated to that piece of hardware. Sure. IMA allows you to put the processing into one common hardware module and and run the software at the lower level that runs that hardware. Autonomous of the software application that would do that would bring the capability separately. So what you can do is is layer in above that lower level. The the new features, the capabilities independently on top of that software, and and they can run wherever that hardware on the air vehicle is located. Right. So they could be in one time in one location if that fails, the software could actually adapt and run over in that same common hardware in a different part of the airplane or if it's located in the same location it could run there too. It it allows you to add those features more easily out at the air vehicle instead of having to send hardware back to the lab or upgrade the hardware or even the the base software. Yeah. And I mentioned this earlier, you know, calling it the standard of avionics today. Would you agree that IMA is already being treated as a standard in the industry? Or is it still sort of on its path to becoming the standard approach for an avionics ecosystem? I would say today is it's been adopted as a standard for the larger air vehicles -- Yeah. -- primarily on the civil and commercial side. At the the smaller lower cost fair vehicles. They're they're still more federated independent systems. Gotcha. But we're we're trying to head that way more so we can adapt to the the larger more expensive vehicles because there's there there's more concern there about the operating savings associated with an IMA type approach. Gotcha. Okay. Now, John, question for you. In terms of Mosa, Obviously, it's not an actually an equipment term. It is a solutions architecture framework. How does it compare to other approaches to integrating systems, whether that's open systems or otherwise, go and give us your perspective. Right in the name, Moce. Modular open systems approach -- Mhmm. -- emphasis on approach. It's a methodology that is allowing DOD primarily to multi source solutions that would hang on an aircraft from different vendors that'll all work together in concert with each other, operate on standard interfaces. There's a tremendous amount of latitude from the people making acquisitions within the Department of Defense as to how do they define what implement implementing the approach. But that's its overarching goal is to be an approach that allows multi vendor sourcing to run on standard interface or or within a standard set of interface. Right. So then what would you say is the key benefit of having that sort of vendor agnostic approach, that interoperable approach, that open systems approach. Right? Yeah. So think there's there's several. I think the most obvious one is you're now able to treat a fully integrated solution on an aircraft -- Right. -- as as you would have formally treated something federated. Meaning, you could take a function out of the equation and substitute a new function back into that equation and have it run on the same architecture without having to upgrade every piece of equipment on the aircraft, which had historically been more than norm within the the customers that that are impacted by Moosa. Gotcha. So What are the essential components of a Mosa system or a Mosa approach? Right? I guess, break down that ecosystem. Yeah. It's really about the it's about the interfaces. Okay. Those are the major components. Whether they be airing four twenty nine interfaces or RS two thirty two interfaces, some of the more standard that have been around in the industry for a long time or interfaces that get developed specifically for avionics. Within the RTCA. I cannot remember what the acronym stands for. Sure. But but it's it's all about the interfaces and then devices coming from multiple sources hanging on to those, connecting up to those interfaces. Makes sense. So building the foundation and then allowing, again, that sort of interoperable approach for different systems. There isn't no one piece of hardware required for something to be bay for a Moosa solution to be based upon. Right. It's encouraged that there be an operating system in the in an IMA for example that is Aering six fifty three compliant. Sure. But that's not an absolute requirement of the approach. Yeah. The approach really focuses on on rigorously tested industry standards for for communication between the different functions. Right. So they wanna really avoid proprietary proprietary solutions provided by a specific manufacturer, a specific avionics manufacturer. Well, that's not the end of the conversation folks, but we are gonna take a short break because we're actually gonna be splitting this podcast up into four parts. That's right. Four different parts for our conversation on IMA, Moza, with the Genesis Aero systems team. So make sure that you're heading to our website, genesis dash aero systems dot com. Again, that's Genesis dash aero systems dot com for more information on the podcast, but also to catch up a little bit on our solutions and services and how they integrate with this modern standard for modern avionics. So we'll catch you on the next episode. I'm your host, Daniel Littwin, the voice of b to b, make sure you tune in for the rest of this conversation with the Genesis team.
