Spectral Autonomy

CMOSS: Shared infrastructure for Army mission systems

Part of the Open Architecture Field Guide.

CMOSS is the Army's suite of standards for placing communications, sensing, navigation, and electronic-warfare functions on shared platform infrastructure. It covers hardware, software, networking, and radio-frequency interfaces.

In this guide

From separate equipment installations to shared infrastructure

A vehicle can carry communications, navigation, sensing, and electronic-warfare equipment developed as separate systems. Each installation may bring its own enclosure, power conversion, processor, cables, and management software. As equipment is added, the vehicle must support the accumulated infrastructure as well as the mission functions themselves.

CMOSS, the Army's C4ISR/EW Modular Open Suite of Standards, approaches those functions through shared platform resources. C4ISR/EW refers to command, control, communications, computers, intelligence, surveillance, reconnaissance, and electronic warfare. The suite combines standards for modular hardware, software, networking, and radio-frequency interfaces so that the platform can host functions within a common integration approach. [1]

The design question changes from “where does the next complete box fit?” to “which resources does this function need, and where does it connect?” A processing function may use shared computing infrastructure. A navigation function may provide information to other applications through the vehicle network. The interfaces make those dependencies part of the platform design.

Why a suite needs several standards

Sharing hardware requires a description of physical connections. OpenVPX provides profiles for modules, slots, and backplanes. It lets the system specify how modular computing equipment connects within the chassis.

Sharing information across the vehicle requires another set of interfaces. VICTORY addresses vehicle networking and information exchange. A vehicle function can then provide data through an agreed network interface instead of requiring a dedicated connection designed separately for every consumer.

Radio-frequency resources introduce a further boundary. Antennas and the electronics connected to them can serve functions that need to request, configure, and receive information from those resources. MORA, the Modular Open RF Architecture, addresses that control-and-data relationship. Software frameworks provide interfaces through which applications use their supporting environment. The Army's CMOSS definition brings these areas together as a suite. [1]

Technical roles within the CMOSS suiteFour peer areas cover modular hardware, vehicle networking, RF resources, and software environments.Modular hardwareOpenVPXVehicle networkingVICTORYRF resourcesMORASoftware environmentFramework interfaces

Scroll horizontally to inspect the diagram.

Figure 1. CMOSS combines specifications for modular hardware, vehicle networking, RF resources, and software. Each area supplies interfaces for a different part of platform integration.

The figure groups these responsibilities because they solve different parts of the same integration problem. A backplane connection does the work of a hardware interface. A network exchange carries information between functions. An RF-resource interface describes access to a resource. The complete platform needs a coordinated design across all of them.

Following an added function through the platform

Consider adding a function that processes observations and reports a result to other vehicle equipment. The architecture first identifies its inputs, output consumers, and required computing resources. It then locates the hardware connection, software services, and network exchanges needed to support them.

If the function uses an RF resource, the design also identifies how it requests access and receives the resulting data. This request may interact with other users of the same hardware. The integration problem therefore includes resource allocation and timing, as well as the correctness of the processing algorithm.

The benefit of the shared design is that these responsibilities are visible before the function is installed. The platform team can examine available capacity and existing dependencies. The function supplier can implement the interfaces assigned to its contribution. Testing can follow the resulting chain from input resource to reported output.

What changes when infrastructure is shared

Shared infrastructure moves some engineering work to the platform level. Power, cooling, communication capacity, and management services may support several functions at once. A change that increases one function's demand can affect the resources available to another, so the complete configuration matters.

That system-level responsibility is the counterpart of modular replacement. A function can be added or upgraded through defined interfaces while the platform manages the resources those functions share. The architecture gives both activities a common description of what connects where and which services must be supplied.

The MORA article examines one of these boundaries in more detail: how an RF application uses resources without containing the implementation of the entire RF chain.

References

  1. U.S. Army PEO IEW&S, CMOSS Definition Document v5. Distribution A.