Sosa Military - Unlike most OpenVPX systems, the SOSA architecture requires the management of a hardware platform that uses the HOST 3.0 system management architecture, which itself is highly provided from VITA 46.11. The system management module accesses all SOSA architecture system components for census, health monitoring, troubleshooting, new firmware/software upgrades, and resets/restores the recovery operation.
At the software layer, work is being done to standardize the runtime environment, but some options are likely to be supported. The aim is to use the FACE, OMS, MORA and REDHAWK specifications, as well as the Common Open Architecture Radar Program Specification (COARPS), which is aimed at many large radar systems.
Sosa Military
Source: api.army.mil
Backplane I/O for RF signals and optical interfaces in OpenVPX has gained significant traction over the past six years in CMOSS, MORA and HOST systems, all of which are supported by the VITA 66 and VITA 67 specifications.
Standards Push
the front panel deserves high marks for maintenance and reliability. Some of the latest modular backplane standards provide ultra-high density and even hybrid optical/RF interfaces as shown in Figure 2. I continue to be amazed at the promotion and progress of The Open Group FACE™ and SOSA™ Technical Standards and Business
approach in the Armed Forces of the United States. Nowhere was this more evident than at the recent 2021 FACE and SOSA Technical Exchange Meeting (TIM), organized by the US Army, sponsored by TES-SAVi and supported by more than 45 exhibitors.
This event proves unequivocally that the Modular Open Systems Approach (MOSA) is here to stay. In 2014, Naval Aviation Systems Command (NAVAIR) initiated the Hardware Open Systems Technology (HOST) initiative; HOST has similar goals to CMOSS, but is focused on avionics system processing and focuses primarily on system management architecture.
The Air Force also has an Open Mission Systems (OMS) initiative, which began rolling out in 2015, promoting FACE and focusing on standardization of messages and middleware for platforms. The SOSA consortium uses government and industry collaboration to create an open technical standard applicable to military and commercial sensor systems with a business model that balances the interests of all stakeholders.
The specification will include a functional, open architecture with a modular design with widely supported, consensus-based, non-proprietary standards for major interfaces. . At the hardware module level, both CMOSS and SOSA use OpenVPX, but have a subset of plug-in card configurations defined to limit the number of unique configurations.
Source: www.usarmyjrotc.com
This is done by defining all user I/O pins, instead of leaving them "user-defined" as in standard VPX. Furthermore, configurations prioritize backplane coaxial and fiber capabilities over other I/O. Using a backplane instead of front-panel I/O for optics and RF is the key to easy card replacement, avoiding complicated cable management, and promoting higher levels
of reliability and density. Another important input is the use of Ethernet as the single fabric protocol for both 3U and 6U based systems. However, vendors currently offer products that are "developed in accordance with SOSA" such as the one shown in Figure 3. The main difference in SOSA architecture versus open standards preceded by well-defined IP protection, which more vendor examples
stimulates. innovation and investments. While each service has made significant progress in advancing OSA principles, they have done so through various initiatives that often share common open standards, including OpenVPX and FACE. However, each initiative also includes specific tasks tailored to service-specific platform requirements.
Navy's NAVAIR [Naval Air Defense Systems Command] in Patuxent River, Maryland, created HOST [Hardware Open System Technology], which initially focused on embedded processing for air and air missions and ground vehicles. The main goal is to abstract hardware and software components that fit well with OSA concepts.
The HOST hardware definition consists of three layers: Tier 1 defines the platform that is deployed (airframe, vehicle, UAV, etc.), Tier 2 defines the embedded system enclosure, and Tier 3 is the board, backplane Versatile, modular and visor
. Tiers 2 and 3 are subsets of OpenVPX configurations and modules. The Registry of Level 3 Products provides a list of approved ingredients for sharing between programs. • Load Profile – This is the main special configuration and contains modules that handle the sensor interfaces and most of the processing of the sensor.
This configuration can support FPGA modules with optical or RF interfaces, but can also support compute-intensive processor modules or GPGPU modules. The VITA Technical Committee, established in 1987 to develop dozens of new extensions to VMEbus, evolved in 1994 into the VITA Standards Organization (VSO).
Source: c8.alamy.com
A year earlier, VITA had become a standards development organization accredited by the American National Standards Institute (ANSI). • I/O intensive configuration – for single board computers that support external I/O. For sensor systems, these modules support the XMC mezzanine expansion card (VITA 42) and are designed for command and control functionality and are also the only module handling external I/O.
The Sensory Open Systems Architecture Association (SOSA) applies the most relevant subsets of existing open standards to form a general purpose backbone of building blocks for today's embedded systems. SIGINT), electronic warfare (EW), and communications. Its goals include supplier interoperability, lower procurement costs, easier technology upgrades, faster response to new requirements, and longer life cycles.
It is important that the module has well-defined boundaries, is separated, and has well-defined functionality. Modules are essential to make systems easier to upgrade to new technology or alternative functions. To suit many uses. In addition, the FACE Consortium and the SOSA Consortium, both managed by The Open Group, continue to grow - we currently have 98 company and service members in the FACE Consortium.
And the number of software products certified to be FACE compliant is also growing, with more than 25 software products from 13 vendors now in the FACE Software Registry. After BG Barrie's keynote, Stephen Simi, COO of TES-SAVi, started the technical presentations with a talk about TES-SAVi tools that accelerate FACE compliance.
Followed by 17 white papers distributed for the rest of the day. These white papers cover a wide variety of topics, from the FACE Transportation Services Segment (TSS) to security to DO-178C security certification to data modeling and more.
The Army's CCDC [Combat Capability Development Command] in Aberdeen, Maryland, developed the CMOSS [C4ISR/EW Modular Open Standard Kit]. These standards include OpenVPX for hardware, VICTORY [Media Integration for C4ISR/EW Interoperability] for sharing media services (such as time and location) for C4ISR/EW interoperability, and MORA [Modular Open RF Architecture] for antenna and amplifier sharing.
It also uses the REDHAWK framework and SCA [Software Communication Architecture]. Although the US defense segment is currently driving the creation of the standard, the standard is intended to be useful in a variety of complementary government and commercial market segments around the world.
The concepts of Modular Open Systems Approach (MOSA) are applied in all market segments. All published materials of the corporation are published for all to use. However, the TWG periodically publishes a "snapshot" of the evolving SOSA Technical Standard that is publicly available for review, the latest being Snapshot 2 released in January 2020. may not claim "compliance" with these snapshots, but they illustrate
the direction and underlying principles that guide the final standards. In May 2013, the US Undersecretary of Defense issued an important memorandum mandating that all acquisitions incorporate the principles and practices of the Department's Open Systems Architecture (OSA).
Defense (DoD). These principles include the use of existing or developing open standards for well-defined modular hardware and software components that can be sourced from multiple vendors. Once proven, hardware platforms will be reused for mission-critical needs that respond quickly, upgrade features and insert new technology.
The software architecture must be layered and extensible to allow for security and operating system upgrades and to accommodate new applications and user interfaces. These benefits reduce development risks and help ensure a significantly longer operational life cycle.
Rodger Hosking is the vice president and co-founder of Pentek. He has been in the electronics industry for over 30 years and has written hundreds of articles on radio and digital signal processing software. Previously he was technical director at Wavetek/Rockland;
He also holds patents on frequency synthesis and spectral analysis. He holds a BA in Physics from Allegheny University in Pennsylvania and a BSEE and MSEE from Columbia University in New York. The SOSA specification limits the main VPX power supplies to +12V only, prohibiting +5V and +3.3V.
This limitation greatly simplifies the previous OpenVPX problem of balance between three voltages to simplify chassis power supplies and standardization plug-in cards. At the same time will try to solve the dilemma between standardization and differentiation.
Source: www.gannett-cdn.com
It will do this by allowing easy replacement of competitor products, while still offering them an opportunity to differentiate themselves in the areas of robustness, longevity of supplies, improved security. and other capabilities that go beyond what is defined by the architecture.
In some cases, the SOSA association applies only to carefully selected subsets of the existing VITA specifications. For example, TWG accepts only a handful of the more than 100 OpenVPX 3U and 6U slot and module configurations, based on analysis that they can meet the majority of system requirements.
For 3U VPX systems, this is a bit of a change, as PCIe was the dominant fabric in the past. PCIe is still used on the expansion board to facilitate high-bandwidth connections between the processor and the FPGA [field-programmable gate array] or the GPGPU [general-purpose graphics processing unit] plug-in card.
While these capabilities drive changes in the COTS ecosystem, they will provide a clearer roadmap for future upgrades. Although the most visible part of a radar system is the large sensor array or antenna, behind each of these sensor arrays is a set of processing hardware that receives sensor data, filters the data to identify areas of interest.
That means, generate metadata to describe the received data. data, and then interpret that data to make useful decisions. This processing chain requires many interactions between different hardware entities as well as software functions. A: Radar processing is one of SOSA's targeted applications, but it also focuses on communications, electronic warfare (EW), electro-optics/infrared (EO/IR) and applications.
signal intelligence (SIGINT), as well as a multi-INT sensor system that combines two or more of these sensors. It is a complex arrangement (Figure 2). An embedded systems industry veteran and innovator in creating COTS security certifications for commercial RTOSs, he previously served as Senior Director of Aerospace & Defense at Wind River Systems, where he is responsible for the business development of the global A&D markets
of the company. During his 14-year tenure at Wind River, certified avionics design wins grew to more than 500 projects. Mr. Downing also leads the sales, marketing and consulting organizations at Esterel Technologies (now Ansys), Validated Software, OnCore Systems, and Mentor Graphics (now Siemens).
Source: data.militaryembedded.com
The Open Team is an international, vendor- and technology-neutral consortium that organizations rely on to lead the development of open technology standards and certifications and provide them with access to peers, key industry vendors, and best practices.
The Open Team provides guidance and an open environment to ensure interoperability and vendor neutrality. You can find more information about The Open Group at: www.opengroup.org One of the important challenges for the SOSA Association, as well as other similar initiatives, is balancing its goals, this constant competition.
For example, while fully defined backplane interfaces allow a high degree of mobility, overly restrictive connections can lead to a lack of flexibility and potentially add to costs. Striking the right balance will be key to the ultimate success of the SOSA Association.
The Sensor Open Systems Architecture Association (SOSA) is a voluntary, consensus-based membership association of The Open Group, a vendor-neutral technology standards organization. The SOSA™ Consortium is a government, industry and academic consortium developing an open technical standard for C5ISR sensors and systems.
The association provides a vendor-neutral forum for members to work together to harmonize, align and create open standards to facilitate the development of fast, interoperable and cost-effective sensors. Answer: SOSA defines itself as "an integrated and comprehensive standard to promote the development of modular, flexible and affordable sensor systems".
The goal is to leverage existing open standards under the MOSA initiative to accelerate development while using common interfaces and packaging to the extent possible. The primary goal of the SOSA Consortium is to help provide the Department of Defense (DoD) with common, cost-effective, commercially available sensing technologies (COTS) that can be easily integrated, repaired, or replaced, and rapidly.
versus vendor-controlled or vendor-locked system designs. A: The organizational structure of the consortium includes an advisory board, steering committee, architecture standing committee, compliance standing committee, as well as the Business Working Group and the Technical Working Group.
The SOSA Consortium is a partnership between government, industry and academia to provide a forum through which members of the SOSA Association can collaborate on an open sensor standard designed to benefit all stakeholders and balance stakeholder interests.
Members include major defense contractors, companies and research institutes; The air force, army, navy and other government agencies also participate in the consortium. In early 2017, the DoD launched the Small Business Innovation Research (SBIR) call for the Sensory Open System Architecture Study, outlining many of the OSA's initiatives and goals for an award.
This led to the creation of the SOSA Association, which is managed by The Open Group, a large organization with rigorous and well-defined practices, policies and procedures for standards development efforts. (Figure 1.)