Spectral Autonomy

SOSA: A reference architecture for sensor systems

Part of the Open Architecture Field Guide.

The Sensor Open Systems Architecture (SOSA) Technical Standard defines a modular reference architecture for sensor systems. It combines functional and interface requirements, including selected hardware profiles, under The Open Group SOSA Consortium.

In this guide

Designing the system around the sensor

A sensor produces observations, but a usable sensor system also needs to process them, move data, keep time, and manage the equipment performing those tasks. These supporting functions are closely connected. A processor needs the right input data, a communication path must carry it, and the receiving application may need a timestamp to relate it to other observations.

The Sensor Open Systems Architecture (SOSA) Technical Standard addresses this system of functions and interfaces. Developed through The Open Group SOSA Consortium, it covers sensor applications including radar, communications, electronic warfare, signals intelligence, and electro-optical and infrared systems. Its reference architecture organizes the components and connections through which a sensor capability is built. [1]

The value of this wider view becomes clear during an upgrade. Replacing a processing component affects more than the computation it performs. The new component must participate in the system's data, timing, and management arrangements. A reference architecture gives those dependencies a common place in the design.

The hardware connection to OpenVPX

For modular embedded hardware, SOSA draws on OpenVPX profiles. A profile specifies the arrangement of interfaces on a module, in a slot, or across a backplane. OpenVPX supplies a range of such arrangements; SOSA selects and constrains profiles for use within its sensor architecture. [1] [2]

Consider a sensor-processing chain with an input function, a processor, and a data-distribution function. The hardware design must connect the input to the processor and the processor to the consumers of its results. The selected profiles describe the relevant module connections, while the backplane topology describes the paths among them.

SOSA architecture and selected hardware profilesSOSA sensor-system requirements relate to selected OpenVPX profiles and to other sensor interfaces.SOSA sensor architectureSelected OpenVPX profilesOther sensor interfaces

Scroll horizontally to inspect the diagram.

Figure 1. OpenVPX supplies hardware profile definitions used within SOSA. The sensor architecture also addresses interfaces beyond the module-to-backplane connection.

The relationship in the figure is therefore one of specification reuse. OpenVPX provides hardware interface arrangements. SOSA applies selected arrangements within a larger set of sensor-system requirements. The surrounding architecture describes how the resulting hardware participates in the complete sensor function.

Giving timing and management their own roles

Data has to arrive with enough context to be used. If observations from two parts of a system are compared, their time information needs a defined interpretation. The equipment also needs a way to communicate operational state, configuration, and health. These concerns remain present even when the processing algorithm itself changes.

Treating them as architectural responsibilities keeps them visible during integration. The processing component can have a defined data interface, while the system separately establishes how time is distributed and how components are managed. A supplier can then identify the services its equipment consumes and the behavior it supplies at each boundary.

This separation also helps explain a fault. Missing input data leads the investigation along the data path. Inconsistent timestamps point toward timing and interpretation. A component that has not entered the expected state raises a management question. The architecture provides a map of these dependencies rather than leaving them hidden inside a supplier's complete solution.

Applying the reference to an actual configuration

An implementation selects components and interfaces to perform a particular sensor function. Processing modules perform calculations, switching functions distribute data, and the chassis supplies physical resources. The architecture relates those choices to the applicable profiles and interface requirements.

For an upgrade, the engineer can start with the function being changed and follow its dependencies. Replacing a processor may preserve its input and output interfaces while changing the internal computation. Adding a consumer may instead require a different distribution arrangement. Each change is assessed through the boundaries it affects.

The neighboring standards address different parts of this design work. OpenVPX explains the hardware profile relationships. CMOSS expands the platform view to shared Army mission infrastructure. Understanding those roles helps a reader see why the same hardware terminology appears in several architectures.

References

  1. The Open Group, Sensor Open Systems Architecture Consortium and Technical Standard.
  2. VITA, OpenVPX system profiles and standards catalogue.