Spectral Autonomy

Open Mission Systems: Mission-system integration

Part of the Open Architecture Field Guide.

Open Mission Systems (OMS) defines interfaces for integrating mission-system components. Its Critical Abstraction Layer separates the exchanges a component exposes from the details of the platform that hosts it.

In this guide

Moving a capability between platforms

A mission-system component has two kinds of engineering detail. One concerns the capability it provides, such as processing sensor observations. The other concerns the aircraft or vehicle on which it runs: how it receives a task, obtains support services, and reports its state. When those platform details are embedded throughout the component, moving the capability to another host requires changes in many places.

Open Mission Systems (OMS) organizes mission functions and their supporting platform through defined architecture elements. A Service supplies software functionality; a Subsystem can combine hardware and software. These are among the elements OMS calls Units of Replaceability, giving the capability and its host explicit responsibilities and integration requirements. [1]

The Critical Abstraction Layer (CAL) addresses the application's messaging dependency on its host. It gives application software a common messaging interface while the platform supplies the implementation that transports and routes those messages. The application can work with defined message objects without containing the details of each platform's communication infrastructure. This is the abstraction that supports moving a service between hosts. [1]

Following an exchange across the boundary

Consider a processing component that accepts a task, consumes sensor data, and returns a report. The host needs a way to express the task. The component needs to receive the required data and communicate progress or failure. When processing is complete, the result needs a defined form that the recipient can interpret.

OMS organizes the exchanges through which those interactions occur. The Universal Command and Control Interface (UCI) supplies a common model for mission-level messages, including the information used in tasking, status, and reporting. In this example, UCI concerns the meaning and structure of the messages, while the CAL supplies the application's interface for sending and receiving them. [2]

The OMS messaging boundarySubsystem or Service application software uses the CAL messaging interface. The platform provides its transport and routing implementation.messaging interfaceplatform implementationSubsystem or Service softwareCritical Abstraction LayerPlatform transport and routing

Scroll horizontally to inspect the diagram.

Figure 1. Application software uses the common CAL messaging interface while the platform supplies its transport and routing implementation. This separates application messaging from platform-specific communication details.

The separation gives the host and component suppliers a shared point at which to work. The component team can test whether its implementation receives and responds to the defined exchanges. The platform team can provide those exchanges through its own integration software. Changes inside either implementation can then be assessed against the interface they expose.

Why the standard distinguishes different exchanges

Mission equipment exchanges more than compact commands and reports. A stream of sensor data can be much larger than a status message. The OMS documentation distinguishes OMS Messaging, Data Transfer, Special Signals, and Security Information Exchanges. Messaging uses the CAL; Data Transfer defines protocols and formats for moving data among subsystems, services, and storage. The separate exchange types address these different integration needs. [1]

The distinction becomes useful when tracing the processing example. A request tells the component what work to perform. A bulk transfer supplies the data on which that work operates. A status message describes progress, and a report communicates the result. Treating all of them simply as “data” would hide their different roles and delivery requirements.

An interface description connects these roles to the participating components. It identifies the exchanges the component produces and consumes and the behavior expected when they occur. This allows integration testing to follow a complete interaction, from an accepted request to the resulting state or report.

Describing the implemented interface

OMS compliance is organized in tiers, which describe the extent of an implementation's adoption. The selected tier and applicable exchanges give the platform and component teams a concrete basis for allocating work. They identify which parts of the common interface belong in the delivered component and which supporting behavior belongs elsewhere in the system. [1]

For the processing component, the resulting specification connects its function to its integration obligations: the requests it accepts, the data it consumes, and the information it returns. The UCI article follows the message side of that relationship in more detail, including how a common message model helps separate task meaning from the software that transports it.

References

  1. OACWG / AFLCMC, Open Mission Systems Standard v2.5: Definition and documentation set.
  2. OACWG / AFLCMC, UCI Standard OAC-STD-001 v2.5: Definition and documentation set.