 Good afternoon, everyone. I'm in the unenviable position of speaking to you after your lunch break So I will try and make this as entertaining as possible. My name is Jeff Hallington I'm one of the leaders of the face consortium, and I'm Glad to be giving you a face overview for the next 25 minutes This overview you've heard a lot of conversation already this afternoon With respect to several of the technical aspects of the face technical standard I'm here to talk a little bit lighter with respect to the technical details And I'm going to focus a lot more on the business aspects the why of face The motivations behind it and a little bit about the structure of the organization That is working to develop that face technical standard So with that I'm going to go ahead and go forward for the why of the face technical standard and It kind of comes back to the trends within avionics software development And I want to emphasize the software piece to that Trends are that as capabilities are increasing as the need for increased airspace capability Work pilot workload reduction The ability to increase safety of flight Software has taken the front seat with respect to avionics capabilities The figure I show here on the screen 70 to 90 percent Of aircraft capability avionics capability is now implemented as software on board that And You can measure it with that shift from the hardware focus towards software You're starting to see complexity increase as those capabilities increase cost time to field are elements that They're starting to see a lot of growth in those that's not really a good thing And that that's a an issue for both commercial As well as military avionics developments so As we we took a look around a number of us in the industry took a look around as far as What we could do about that we noticed several trends within the commercial airspace industry and primarily with respect to Open standards open architecture and so forth And so we started Jim germinating the idea of what could we do in leveraging that now another motivation That we have with respect to the phase consortium and the phase technical standard has to do with What our adversaries are doing And our adversaries are utilizing asymmetrical techniques Utilizing commercial off-the-shelf items Taking a very A fast approach with respect to developing Their weapon systems and the the quote I show on the bottom here six to one that ratio When I heard that That ratio as it applied to Development of anti aircraft systems by an adversary as compared to A single development cycle for the aircraft the fighter aircraft that was designed to go against that threat I was floored I heard that at the april speeds conference Keynote presentation there and I started thinking about the commercial world When you're looking at competition that's outrunning you to that degree That's a recipe for going out of business right and You know when you think about it from a defense standpoint That's a recipe for defeat in an unacceptable defeat as far as we're concerned So a number of individuals who were visionary with respect to that software development the ability for us to Break those issues that we were seeing with cost and and time to field Started getting together under the leadership of us navy navier pma 209 And we began to discuss What are the issues that we're facing getting to a greater level of detail? and discovered that You know certain things stood out right The development of avionics the development of aircraft systems in general Uh essentially resulted in a siloed development cycle where the end result was capabilities that really they they Kind of stuck with the aircraft itself that specific aircraft type model series And we had a difficult time Very expensive very lengthy process of trying to Uh port that kind of capability to other aircraft So you essentially ended up with a repeating cycle as you went from aircraft to aircraft Drove cost and and schedule Long integration cycles We take a look at What standards that avionics development Utilized not everyone was on the same sheet of music And for us we we saw the end result Uh multiple integration efforts multiple development efforts again a lack of the ability to to Really concentrate on what you really needed to concentrate on which was driving innovation Into your capabilities driving advanced capabilities into your aircraft You're spending a lot of time trying to to just move things around Um And so as again as we looked at the commercial world looked at integrated marzler architecture avionics Um started looking at how we could leverage perhaps the same ideas Maybe not the same ideas, but certainly similar ideas We started seeing a model by which Utilizing standard architecture utilizing open interfaces We could drive leverage ability of components from platform to platform if we developed them correctly And uh that allows us to optimize investments for capability innovation Focusing on what really mattered the most and then being able to Enable that faster integration to cut the time to the field so again, um Taking that cue from the open architecture The group of us who started the phase consortium idea We began to think about The openness of the interfaces the architecture and the standards that we wanted to utilize Think about the the phone that's in your pocket right It's very straightforward for you as a user of your of your phone To be able to go to an app store and to download an app of your liking For the purposes that you need it for and operate that on your phone You don't need to know very much about the phone itself But you do have assurance that the manufacturer of that phone the operating system that that is on it There's enough openness to that where third party developers can develop an ecosystem of applications And you benefit by that wide variety and for that matter The cost effectiveness Of those applications So we wanted to move from the legacy world of a closed system controlled by a single vendor Vendor locked if you will and go more toward that open open standard for For the operating system for the middleware pieces And then of course for the applications themselves then implement the business logic for the capability And do so in a way that If there's an application developer that's out there And they really don't know very much about the system itself and how their application is going to be hosted Yet they are really smart at developing the business logic behind the capability that's innovative for you They still can participate in that market team up with others And develop the application do the testing and do the integration in cooperation with others And now you've got the ingredients for true cost and schedule reduction So those of you who are familiar with software development You are Probably familiar with some of the standards that I show listed up here POSIX A-Ring 6x1 A-Ring 6x53 OpenGL Some of those have existed for a long long time POSIX an outgrowth of The unix wars back in the 1980s of which the open group Hand-to-hand at helping to resolve one of the reasons why we picked them to help manage the face consortium These are standards that are well known They're usable they're open and we felt that that was a great foundation for us To place into the face technical standard But the real value add that the face consortium felt would be um extremely important for Utilization in that technical standard is this is the structure the architecture if you will whereby modular components are capable of being placed into that structure In a way that allows for the portability of reuse and And and others are able to understand what you placed into that system Standard data models to understand the data flows from your module to somewhere else and now the integration process becomes easier these In the end permit life cycle competition By many players in the marketplace and again when you do that now in your differentiation in that marketplace is How innovative is your capability going on board that that that software piece? We also looked at well, how are we going to pick which open standard? Interfaces to use for the software. How are we going to develop that standard architectural structure? And we felt it was hugely important for us to implement a voluntary consensus standards body Formulated underneath with a good legal foundation and on be circular a1 19 Was really important for us allowed for government participation to take place And as well the national cooperative research and production act Which allowed industry together together With protection from things like antitrust issues And if we were following the rules with respect to Uh the the consensus body the fair and equal representation do do process the appeals process Driving toward consensus Then we had that foundation for an Adoptable standard by as many people in the industry as we could reach The overall goal for the face consortium, which was started in 2010 again with the leadership of The navy nav air organization the open group and uh, I would say about 15 or so Organizations that served as charter members Was to create the ability for independent third party vendors to to provide portable and reusable software components that would be hosted on top of essentially a face environment And this this is kind of the most Popular chart that we use to identify the face architecture Each of the booths that you will see in our exhibit hall Are required to have a representation of this face architecture and The components that they are demonstrating or they're showing as part of their booth They need to represent that In the different layers that exist in the face architecture The business In the most important piece for us are two of the segments in this architecture The portable component segment as well as the platform specific services segment Which allow for that portable reusable component to reside And the interfaces that we have chosen For those components to interface to the rest of the system We have carefully identified What calls are allowed that would allow for Those components to not have to know what's underneath the hood so to speak their hardware agnostic their sensor agnostic And then if you've done doing it right operating system agnostic And uh, you do not have to understand the device drivers that you're working with Or other things that would necessarily tie your component To the underlying system therefore we're making that reusability and portability much more easier The rest of the segments the transport services segment The ios services segment and of course the operating system segment Those are probably what we would consider the pieces of the environment that those portable reusable components are going to operate on top of And those are huge with respect to being able to transform the calls from those portable reusable Components to interface with the hardware and sensors As as needed Also important is independent verification that you have followed the face technical standard In all of the requirements necessary for portable and reusable components. We have a multi step process Again independent VA's Verification authorities they run the tests. They do the inspections Necessary for them to say yes, you have followed the standard You now have the ability of obtaining a face certificate which the certification authority will grant and The certification authority also maintains the integrity of the process by allowing for Autotability of the testing that the VA's do there are multiple VA's that we have And there's one single certification authority that kind of oversees their work At the last step of the process we have a library administrator once you have Successfully obtained a face Obtaining face certificate You are now able to list your software On a face library page that the face consortium maintains hugely important for the marketing of your face components And allows for independent verification by a customer Potential customer that Allows them to say yes, I see that you are listed. I know that you have a face certificate And gives them assurance that we have a marketplace with integrity And the ability for for them to say yes, I want to I'm going to select a face Certified product and I think a measure of success with respect to Having application of the face technical standard is right here The number of face certified components that have entered into the face library since 2017 When we started that program We're now 19 components from 12 different suppliers More are in the pipeline They're covering all of the face segments that are in our architecture And there's quite a number of Capabilities that are represented by those components Again, we have in the hall a number of the vendors these vendors here are represented They are given a special signage If they are part of the face library Please go visit them check them out and talk to them about their face conformant products So I've given you kind of a really brief overview Kind of lacking in details. There are many documents of various Um levels of detail that are available for you to Get started with the face technical standard with understanding the face concepts They range in uh with respect to guides for business Contracting and that's both uh industry as well as government contracting officers And uh for programmers themselves Uh kind of the getting started Aspects of what face is all about And allows you to ease into the concept Again, if you have software expertise with some of the standards that I talked about earlier You have a great foundation to begin with the face technical standard If you're uh, if you're the the nerd type That wants to get into the major details There is the face technical standard itself and a companion document called the face reference implementation guide These are very lengthy documents. They will get you into the details As necessary for successfully Implementing face conformant products They are available on the open group website. We have the web page information on the lower left It's probably hard to see At your distance there But w w w dot open group Dot org Backslash face And from there, uh, you'll find information about the consortium about the open group And the documents that we have available. There is a link called Documents and tools Check that page out Those are available for free consortium members we're at I think we normally say 80 Plus members we didn't typically have a little bit of churn from year to year But overall we're maintaining around the 80 mark and The who's who of the defense industry is represented here government Industry as well as academia All have been involved They all are Essentially paying for their own time their own way To provide their experts For each of the face meetings If you're interested in joining Please see the open group booth in the exhibit hall and they will provide you with the information you need Again, I identified myself as one of the face leaders in the consortium We have a whole host of them working on both business as well as technical as well as datum architecture These are hardworking individuals who are spending again a lot of time with this and We we joke as we meet from time to time that you know, we're doing our night job We have our day jobs with respect to our employers And so this is a lot of work And I want to thank those who are in the audience who are Listed on this list for Helping out I can't identify a finer group of individuals to be working with on this initiative and finally you know we we end A lot of presentations with this quote this quote graces the front page of many of our documents And it kind of harkens back to that problem statement that I talked about in the beginning the time and cost that we've seen with the increasing capabilities that are going on board our warfighter aircraft and The complexity of that's driving And the fact that our adversaries are doing all that they can to outrun us with respect to innovation It's time to recapture that Back for the u.s. Warfighter and our allies It's a necessary thing. It's important for us Otherwise this will happen And we don't want that to happen So thank you for your time and your attention. I'm happy to answer any questions that you have