 I'm the Senior Director of Airspace and Defense at Wind River. I also serve as the Chair of the FACE Business Working Group. I've been with the FACE Consortium since its inception in 2010, and I really enjoy working with this consortium. Probably one of the nicest things I've done in my career. And if you want to change the world one aircraft at a time, this is the consortium for you. So today I'm going to do a brief introduction to FACE, and hopefully you'll get a feel for the capabilities behind FACE and the way that FACE can impact and make more efficient and affordable next-generation systems. So why are we here? Next-generation military avionics systems are challenged to provide advanced capabilities while balancing the cost to procure and maintain the platform over the lifecycle of the deployed platform. This challenge is well-described in this slide that you see in front of you. It's a GE Aviation Costs and Complexity Chart that shows the exponential growth of software in commercial military platforms over time. The critical component is a trend from hardware-defined systems to modern software-defined systems where the cost to develop, integrate, and maintain software is growing at an unsustainable rate. Using open industry standards and advanced integration and maintenance technologies, GE was able to bend the curve for the Boeing 787 Dreamliner and other commercial aircraft. The goal of the open group, future airborne capability environment for FACE, the consortium is to duplicate and advance the success in military avionics systems in an open procurement environment with the goal of improving affordability, speed, agility, and excellence. So how do we start FACE? When the FACE consortium was first formed in June 2010, we needed to migrate from a closed single-vendor ecosystem system architecture to an open system architecture. This legacy federated system architecture is on the left-hand side of this graphic where everyone brings a single hardware-based component with some software to an aircraft. At the time, both Apple, iOS, and Google Android were soaring in popularity, so we immediately tried to use these architectures at a starting point. But we discovered that both of these architectures were not fully open, as depicted on the slide. And we needed to create an environment that had an open hardware, open operating system, open middleware, and open applications environment that could be served by any supplier, larger, small, in the defense industry. Therefore, we have FACE. With this open architecture, we were able to break the traditional barriers to innovation in military aircraft systems. Legacy platforms were traditionally purpose-built for specific aircraft in the avionics system. Within this aircraft were created to efficiently serve a given function within a legacy aircraft. This created barriers to deploying, integrating, and maintaining the software on other aircraft. The FACE approach changes the software architecture paradigm. The FACE technical standard created an open, layered architecture that allows any FACE software component to move from one aircraft platform to the next with minimal integration complexity on any desired hardware platform. This architecture is based upon proven commercial and military avionics standards. This allows the best-in-class technologies to be deployed on relevant platforms which removes duplicative investment and similar airborne capabilities. From the business standpoint, it enables widespread affordability and best fit for the cost solutions, accelerating both speed to fleet and capability agility. The FACE consortium is not driven by just a few vendors. It is supported by all of the U.S. Armed Forces and over 80 organizations in the industry, including all the major crimes and Tier 1 suppliers. We all work together on the FACE technical standard and FACE business approach as a diverse government and industry team that created a balanced open solution. So by FACE consortium, why can we not just get together and come up with a standard ourselves independent of the consortium? Well, the framework for open discussion was facilitated by the open group as a voluntary consensus standards body as defined by the National Technology Transfer Act to be circular 8-119. This consensus-based environment supports a balance of interest in an organizational foundation to support a due process with an appeals process which enables both government and industry to work together to create a common shared vision for innovation. As one can see from the slide, the many FACE business and technical committees consist of a wide range of business and government entities. We've been busy over the last seven years. The FACE consortium has been very productive. We have not only published multiple revisions of the FACE technical standard with incremental improvements, we have also published a shared data model with a government's plan, business and contract guides, and a fully operational FACE software verification, conformance and library process. We've also created a FACE problem request change request process for adjudicating any corrections to the published standards. The FACE conformance process, well underway, was completed in 2017. The FACE certified product library is now being populated with FACE conformance software from all segments. The initial products in the library were delivered by Harris, Honeywell, Buckle Columns and Win River, and we expect many more products to be certified here in 2017, or 2018, excuse me. The FACE approach is now ready for voting affordable, efficient, and competitive next-generation aircraft systems. The FACE standards are ready to use, the government is ready to procure, and industry is ready to provide the latest capabilities using this advanced interface software foundation. The goal of the FACE consortium is to enable agile innovation, innovative solutions that give the military a strategic advantage. Additionally, the military has focused its avionics resources on engineering efforts on a single platform, stovepipe architectures, and software designs. The FACE architecture is now free to focus on driving innovation across many platforms over the entire asset lifecycle. This increased application capability and utility speeds cutting edge technology to those who defend freedom globally. The FACE technical standards stand from the shoulder of over 60 proven commercial military standards provide value. The FACE has repeatedly leveraged the design and organizational efficiencies proven in commercial aircraft and drive these new capabilities into airborne systems. The FACE approach has four very powerful characteristics, affordability, speed, agility, and excellence. With affordability, we have created an open standard to be used by all future military avionics platforms, and this creates an open and stable marketplace for these next-generation systems. In both government and industry, it reduces the product development costs for industry because they can now create a product line for the capabilities for future platforms. It's good for government companies, and I'll select the best in class capability and use that capability across a wide range of programs in aircraft. The FACE technical standard directly enables greater speed and agility with a set of standards that have been proven and critically vetted by a consensus participation of members. We have not reinvented the wheel nor created another open architectural standard in our own image. The focus is on proven software foundation that drives down risk, accelerates schedule performance, and allows us to achieve objectives that are not possible using traditional methods, processes, and standards. Achieving innovation agility is critical to get to higher levels of interoperability and mission performance from aircraft. By using a common data model and characterizing data according to best-known practices, it achieves higher interoperability across domains, systems, and capabilities. This reduces the workload required to deploy new components and drives higher levels of mission situational awareness by leveraging standardized platforms and data architectures. The FACE technical standard establishes a software architecture that leads to a more robust structure while components are built and lately driving excellence into software design, acquisition, and deployment. The FACE approach provides these standards for both businesses and technical operations for both new and upgrade opportunities. The FACE technical standard is based upon proven rules of construction that lead to more resilient designs coupled with an enforceable conformance model that facilitates faster more robust integration and performance. FACE already has its first wave of certified conformed software products listed in the FACE registry and we expect to see more certified conformed programs in the future. Using the FACE capability is a smart, intelligent way to create innovative solutions for future generations of airborne systems. The FACE solutions will optimize scarce financial and engineering resources, enable a U.S. and its coalition partners to share advantages over the all global adversaries. All members of the FACE consortium are available to contact to help train and guide organizations to advance the airborne systems into a highly efficient standard space future. Feel free to contact any member for more information. You also may join the FACE consortium and help create the foundation for all next generation advanced avionics platforms. Thank you. Okay, Barbara, I've handed over to you, so please feel free to go ahead. Okay, I am Bubba Davis. I am an employee of senior software engineer at CRL Technology supporting the U.S. Army MRDEC. I've been involved with the FACE consortium since 2011 and I'm currently the data architecture working group vice chair. But today I'm going to give you a FACE technical overview and just a very high-level description of what the FACE reference architecture, the FACE technical standard provides to give you an idea of the technical advantages of using the FACE strategy. This technical overview I normally give in an hour and a half, so we're just going to scratch the surface today, so don't feel like you've got a thorough deep knowledge of the FACE technical standard in this 10-minute overview. The FACE technical strategy is to provide a software environment that enables moving applications from one platform to another. So the concept is we want to be able to move a capability from one DOD aircraft to another and minimize the software changes when doing so. The concept is the FACE computing that the technical standard defines exist on existing or new computing hardware and it provides a common set of interfaces to your portable applications so that they can move between existing hardware, new hardware, move across aircraft. So this is a strategy used in industry across many different industry domains and we are leveraging it for the avionics domain. The FACE architecture, you'll hear it referred to as the FACE software architecture, the FACE reference architecture, the real goal is it isolates a set of areas where variance and software can occur and we've defined a layered segmented architecture that you'll see in a second and the purpose of this is to provide a common set of interfaces and a small set of interfaces using a set of these interfaces we can really isolate where changes happen, where variability can happen and provide a common interface to applications and you'll see the bold green lines on the figure in the bottom are these vertical interfaces that are well-defined FACE interfaces. We also recognize that different applications may need to exchange data and when applications are exchanging data we define horizontal interfaces so that they are well described rigorously defined data-centric interfaces. This means you are rigorously defining any data you're exchanging so that the receiver of the data can understand and comprehend it. This allows both integrators, subsystem developers to understand the data needs of all their software components and build them to integrate them onto existing or new platforms. We are leveraging existing standards where possible especially operating system you'll see them I figure it mentions POSIX in area 653. FACE has not tried to redefine or come up with our own standard if there are existing standards that we can leverage and use we have done so where appropriate and so POSIX if you have a POSIX operating system that doesn't necessarily mean you're conformant to the FACE technical standard but there's a subset of the POSIX APIs that we've selected that we use in the FACE technical standard in the FACE architecture and this slide we could drop anchor here for quite a while but I just want to give you an overview of the different layers, the architectural segments in the FACE technical standard the primary one and where most software is anticipated to reside is in the portable component segment this is where your typical applications will live so if you have an application doing tracking or navigation it is most likely going to live in the portable component segment and early analysis looked across aircraft and determined that about two applications could live in this portable component segment if architected correctly so this is where you get your real portability between platforms is by developing these portable components you notice portable applications you see my bold green lines again on the figure they can use two of our well-defined interfaces in the FACE technical standard they can use the OS interfaces we've defined and we've defined an interface to transport services and that's the next segment the transport services segment exists to move data between components so we are separating out from your portable applications your need to be concerned with how the data is actually transported the separation of concerns removes the necessary knowledge from the portable component developer for the data transportation data conversion all the details that happen there are outside the purview of the portable component segment developer and really lets them focus on the need of their application transport services again uses the OS API left-hand side of the diagram and it's also used to talk to platform-specific services segment and these are software components typically to a particular platform they're less portable than what you would see in the portable component segment so we're going to have configuration, graphic services health monitoring some of these types of common services live in this area you also have platform-specific services that communicate to your I.O. services so we've built a layer just for our I.O. devices and this segment lives to communicate with the device drivers provide device driver normalization and provide a common mechanism for a platform-specific services segment to access I.O. information this enables us to separate from our our real business logic our algorithms the details of data presentation data transportation and data input output so we're no longer tied to specific graphics displays specific sensors or specific transport methodologies such as DDS, Corba UDP, TCP those are abstracted away from the real business logic of the application that's performing our capabilities on our aircraft and lastly there's an operating system segment where we have a one operating system that's listed in the FACE registry today the operating system segment provides your typical POSIX or airing 653 APIs as defined by the technical standard and by using a standard definition for these APIs we can allow portable components to move from one FACE conformant operating system to another FACE conformant operating system and we break that explicit tie to an existing operating system so if you get nothing else out of the FACE technical overview if you understand these five segments operating system I.O. services platform specific services transport services and portable components if you understand those five segments you have a good foundation FACE technical standard and the FACE reference architecture is trying to accomplish and the ability it gives you to develop portable software that can move from one aircraft to another just briefly Chip mentioned the consortium there's a technical working group in the consortium that's in charge of the FACE technical standard and there's several subcommittees that are responsible for different portions and just list those up I won't go through them but just wanted to be aware that the technical standard there's a large group of technical experts from both government and industry working and have been working on the design and the development of the technical standard since 2010 and lastly I want to bring up there's another organization I mentioned earlier that we use rigorously defined data descriptions across our transport services interface the data architecture working group is responsible for the FACE data architecture it's another working group several subcommittees the data architecture is included in the FACE technical standard up through and including 3.0 I will not try to give a data architecture working group but I will try to give a data architecture overview as that's an upcoming webinar later today and I believe that wraps my presentation Simon so I will pass the ball back to you that's great, thank you Baba Judy would you like to say a few words just to end today's session sure, thanks Simon my name is Judy Serendia I'm from the open group I'm the FACE consortium program director I'm joining us today and to thank our presenters Chip Downing FACE consortium business working group chair from Wind River and Dr. James Bubba Davis the vice chair of our data architecture working group within the FACE consortium from CRL Technologies representing U.S. Army Ammerdeck I appreciate both of you doing an excellent job giving folks good information about the FACE consortium technical overview and for more information you can contact us at ogface-admin at opengroup.us or look for us at www.opengroup.org for more information about the consortium, our work products and what we're doing to advance technical standard and meet business objectives for portable and reusable software on avionics platforms joining us today. Take care.