Approach, benefits, and challenges of specifying a software operating environment (SOE) product line within the AMCE, with mission and safety critical variants to support the aviation enterprise.

CUI confirmation is required for attendance: - US Military Uniform - DoD CAC - Access to AFRL VDL - Contact Devin Wisdom, devin.wisdom@us.af.mil, 850-420-4283

MOSA allows the government to choose the best athlete for any specific capability. However, when all these capabilities are thrown into a single chassis, proprietary information needs to be shared with the Integrator. Often enough the Integrator is a competitor of the capability or has a complementary competitive division. This stifles the information flow and impacts teaming agreements at the expense of the customer. The problem is occurring more and more and dilutes the MOSA solution fundamentals. To compound this, being the integrator gives a contractual advantage which adds more competition to the proposed solution(s). This panel will work through these concerns and discuss potential business models that would allow competitors to work together, within a chassis, while protecting their own proprietary data, performance and roadmap, giving the customer and warfighter the best technology available. Putting the best of breed technology capabilities together is not a technology problem. It is a business problem fraught with pitfalls and perils.

The panel will explore different technologies to enhance the modularity and adaptability of Software Enabled Weapons (SEW) through an "App Store" concept. SEW will draw from industry best practices in areas like Modular Open System Approaches (MOSA), including Government Reference Architectures (GRAs), Cyber-Physical sub-system implementation designs, standardized interfaces, Component-based architectures, auto-code generation, and specialized modeling languages. Panelists will discuss how these components have been used in their organizations and showcase how they can be seamlessly integrated to create a prototype Weapons Application Store.

Describing the MOSA Conformance concept

To achieve the desired MOSA benefits, acquirers and suppliers must collaboratively apply mature systems engineering processes and MOSA principles to the alternative solutions that satisfy both the Mission and MOSA business requirements. This panel is a follow-on to the first MOSA summit MOSA in Acquisition: Policy to Practice Part 1 track and the Program MOSA Transformation Information Needs and Metrics presentation which defined a seven-step process for what was needed for MOSA success. Since the last conference there has been considerable progress at NDIA, OMG, and the DoD IP Cadre to address how the seven-step process is executed. The panel facilitates an interactive discussion of the seven-step process highlighting MOSA implementation considerations, information needs, metrics and collaboration needed for MOSA and mission success. Discussion of MOSA use cases provide the opportunity to explore how different MOSA approaches, at the practitioner level, can be applied to new and different situations. The concept of MOSA product value to support the business case and MOSA metrics recommendations will be discussed.

Some MOSA-enabling standards have been around since the beginning years of MOSA and have evolved significantly since then, not just in the technical standards but also the engineering processes and business practices that support them. This panel will explore topics such as the application of MOSA-enabling standards to increasingly complex systems, expanding the use of model-based system engineering to certification, further promoting reuse by integrating functional standards with MOSA-based modularity and interface standards, and the evolution of program acquisition and proposal processes for meeting MOSA requirements.

CUI confirmation is required for attendance: - US Military Uniform - DoD CAC - Access to AFRL VDL - Contact Devin Wisdom, devin.wisdom@us.af.mil, 850-420-4283

Title 10 - U.S. Code § 4401: A major defense acquisition program shall be designed and developed, to the maximum extent practicable, with a modular open system approach (MOSA) to enable incremental development and enhance competition, innovation, and interoperability. || Key MOSA/Open Architecture/Open Standards experts from NAVAIR PMA-209, Army DEVCOM C5ISR Center, PEO Aviation, and the Air Force ACC talk acceleration of open standards adoption, active advancements (i.e. fielded yet?) with the Hardware Open Systems Technologies (HOST) Standards Framework, Future Airborne Capability Environment® (FACE), Sensor Open Systems Architecture™ (SOSA), and the C4ISR/Electronic Warfare Modular Open Suite of Standards (CMOSS; think ‘Victory’) for Air, Sea, and Ground.

This panel will bring government and industry experts together to discuss the current state of the art with respect to digital twins across the Department of Defense. Topics include taxonomy, interfacing, data engineering, and architectures.

MOSA has been touted as a powerful concept to enable rapid program modification and upgrades throughout the DoD lifecycle. The key to taking full advantage of MOSA is the idea that everyone, from those involved in concept studies, through program development, and into sustainment can utilize/leverage the MOSAs to make rapid technical improvements and advancements with little wasted effort. However, the ideal is yet to be fully proven. This panel will showcase one case study in making that a reality with MOSA for Position, Navigation, and Timing (PNT), leveraging experiences from two programs of record: R-EGI (Air Force) and DAPS Gen II (Army). Both programs are utilizing two government-owned, open-source MOSA products, developed by IS4S for the government: ASPN and pntOS. ASPN is a PNT messaging standard, upon which WOSA is also based. PntOS is a pluggable, modular framework for sensor fusion and beyond, in use by IS4S, TRX, and several other companies. The esteemed panelists will provide experiences and observations from their unique perspectives, debating what is working, what deficiencies have been observed in the implementation, and what must be done to enable MOSA to achieve the ideal scenario.

TBD

This conference panel aims to provide a comprehensive retrospective on the achievements, challenges, and lessons learned from the implementation of MOSA principles for a perspective 50 years in the future. Focusing on the key goals and objectives outlined in the early days of MOSA, the panel will explore what worked and what didn't in the pursuit of modularity, openness, and interoperability. Through a lens of hindsight, the panelists will delve into modularity and highlight instances where standardization and open interfaces led to seamless integration and innovation across diverse technological landscapes. The panel will candidly address the obstacles encountered in achieving MOSA's goals. These may include challenges related to industry-wide adoption of open standards, unexpected complexities in maintaining interoperability, and issues surrounding the longevity of certain components in the face of rapidly evolving technologies. Attendees can expect an entertain conversation on how MOSA evolved over the past five decades, its impact on technological ecosystems, and the role it played in shaping the trajectory of modularity, openness, and interoperability in the ever-changing landscape of systems architecture. The insights shared in this panel will contribute to a deeper understanding what to do today to achieve MOSA goals tomorrow.

TBD

TBD

Please join us for a panel discussion exploring the dynamics and intricacies of Modular Open System Approaches (MOSA). This event features a diverse array of experts from across the supply chain, including notable figures from industry, government, and academia. Together, they will discuss the application, evolution, and impact of MOSA from their perspectives.

Emphasize importance of Digital Backbone as part of the Government MOSA and encourage discussion on concept, technology, and experience with

MOSA is an integrated business and technical strategy to achieve competitive and affordable acquisition and sustainment over the system life cycle. To achieve this, a balanced policy is required that will empower acquires to own and manage their systems independently, free from the constraints of acquisition decisions while also incentivizing the Defense industrial base to innovate without fear of losing control of discriminating IP. This panel will address the need for early and transparent communications to identify the decision information and metrics required to support MOSA success from the following perspectives: • Acquirer during the Request for Proposal (RFP) generation - content and evaluation factors (i.e., UCF section L and M); strategies for effective communications. (i.e. reference architectures, Domain overlays..)

This panel is a discussion on how the application of Open System Architecture (OSA) standards, and the resulting products, can deliver enhanced operational capability. There has previously been a lot of communication and understanding of how OSA can increase supplier competition and reduce cost/schedule. By having a holistic view of operational requirements, and translating that into engineering requirements, a MOSA-enabling enterprise can use OSA to deliver an increased competitive edge and therefore reduce operational risk. This panel will discuss some examples, and how the Defense community can deliver this valuable advantage to our Warfighters.

TBD

The traditional implementation of uncrewed aircraft system (UAS) and uncrewed ground vehicles (UGV) command and control (C2) are largely based on monolithic software architectures and Interoperability Overarching Profiles (IOPs) (RAS-A, RAS-G, STANAG4586). To answer the need for a systems of systems integration across all groups of UAS, UGV, and launched effects, large OEMs and emerging tech companies are attempting to solve the problem by proliferating proprietary software solutions and improving proprietary messaging standards that lock the government to a single vendor. This panel will talk through the MOSA which applies the PEO Aviation Enterprise Architecture (EA) FACE Technical Standard, Aviation Mission Computing Environment, Weapon Machine Interface (WMI), Scalable Control Interface (SCI) User Interface (UI), IOPs, and widely adopted open standards to create an architecture that solves the Human Machine Integrated Formation (HMIF), Uncrewed Vehicle Control (UVC) Component Specification Model (CSM), and Replicator.

The panel will focus on the application of Model-Based Systems Engineering (MBSE) to Modular Open System Approaches (MOSA). Of particular interest will be the relationship between a component specification model, a component design model, and a data model / data architecture and how those models can be applied in the context of acquisition of open systems. The panel will also be prepared to discuss refinement of component requirements and component architectures so they align to the Enterprise objectives for reusable, portable, modular, and certifiable systems, such that they can be composed into systems that meet the stakeholder's needs. All of these processes are aided by the use to models to capture, analyze, and document systems using multiple model languages such as System Modeling Language (SysML) and Open Universal Domain Description Language (Open UDDL), which is the model language adopted by the Future Airborne Capability Environment for its data model requirements.

This panel of experts will share experiences of those in the trenches of acquisition; lessons learned, useful approaches, and enablers as best practices. They will highlight innovative ideas, workarounds, enablers, and modified approaches created by government MOSA practitioners to help identify best practices, to help lead for a wider set of programs. Attendees will learn how to address some difficulties which include interpreting and addressing the impacts of complex and seemingly conflicting MOSA requirements, integrating systems using multiple standards or architecture frameworks, and work with providers in new ways.

A discussion amongst industry and DoD MOSA practitioners focused on the fielded solutions that embody MOSA principles and benefits. Point of the discussion is to show that it can be done and to share practical lessons learned.

TBD

Many platforms today are beholden to the OEM as the integrator despite them being slower, less innovative, and more expensive. For legacy and current systems this is largely due to proprietary architectures tied to the flight Operational Flight Profile (OFP). We no longer need to deal with this on existing or future systems, crewed or uncrewed. The separation of air vehicle and mission systems creates the opportunity to separate out a mission OFP that can enable independent and rapid capability insertion outside of the OEM. There are examples on the General Atomics Gray Eagle (MQ-1C) for the 160th, General Atomics MQ9, FTUAS, launched effects, and FARA and FLRAA. This panel will discuss how the peoblem is solved with architecture, the correct hardware and software infrastructure (AMCE CSM), open standards such as the Open Mission System (OMS), FACE Technical Standard, and IOPs across Army and Air Force systems. We can make MOSA successful, but it requires changing our architectures and moving away from OEMs as the integrator.

The panel will present and discuss findings related to the Army's Architecture Collaboration Working (ACWG) Digital Engineering Subgroup (DESG)'s sprints from January to May 2024. These sprints focused on discussions with experts from Industry and Government focused on the question "How do you ask for and receive digital artifacts?". The panel will discuss the themes, key findings, and experiences related to digital artifact acquisition.

TBD