Saab launches Allied Mission System for space operations

Saab has introduced Allied Mission System (AMS), an Australian-developed software platform that combines space surveillance, analytical tools and mission management within a common operating environment. The architecture is designed to bring observations from different sensors and information providers together, then support decisions and the coordination of missions involving space assets. Saab intends to make the system available globally through a Software as a Service model, although it has not identified a first customer or a contracted operational deployment.

Developed by Saab Australia, AMS was unveiled on 20 October as an extension of the company’s experience in military command systems. Saab describes an open architecture in which users can monitor activity in space, interpret observations and manage the resources needed to investigate or respond. The launch concerns mission software rather than a new satellite, launch vehicle or sensor constellation; the quality of the resulting operational picture will depend in part on the external data and assets connected to it.

Space domain awareness requires information about objects in orbit to be assembled from observations made at different times and from different positions. Individual sensors may produce distinct records of an object or event, while external data providers can apply different formats and update intervals. Correlating these inputs is necessary before operators can distinguish a change in an object’s behaviour from a difference in observation or processing. AMS is designed to combine these feeds and place them within a shared mission context rather than leave operators to reconcile each source manually.

Historical information and current observations can then be assessed together. Saab says its analytical functions support the identification of behavioural patterns and potentially unusual activity, alongside tools for prioritising events that require attention. Automated assessment may reduce the volume of routine records requiring individual examination, but the company has not released independent figures for alert accuracy, false positives, analytical throughput or operator workload. These remain capabilities described by the developer rather than measured improvements established in customer service.

AMS also includes functions for assigning tasks and coordinating resources after an event has been assessed. A space surveillance network may need to redirect an available sensor, seek an additional observation or pass an assessment to another operational organisation. Keeping data and mission activity in one environment could reduce the number of separate applications involved in that sequence. The actual decision rights, approval processes and available actions will depend on the participating organisations and the systems integrated with their AMS installation.

Its modular design separates data services, mission services and applications, allowing different elements to be developed and changed without replacing the entire platform. A new source of surveillance data, for example, can be connected through an interface while analytical and mission applications continue to use the common services. This is an architectural proposition that still requires integration testing, information assurance and configuration control for each deployment. Saab says authorised customers and partners will be able to develop their own extensions and retain ownership of the intellectual property they create.

Software as a Service delivery is intended to let Saab maintain and develop the underlying platform while customers tailor its capabilities to particular tasks. The company has not specified subscription charges, hosting arrangements, performance guarantees, or how classified customers would implement the service. Those choices can affect resilience, security accreditation and the degree of control a defence organisation retains over its operating environment. A cloud delivery description alone does not establish that every installation will depend on continuous access to a public network.

Saab has also described analytical functions for monitoring the condition of the platform itself. Identifying abnormal software behaviour or failing services can support maintenance and fault investigation, particularly in systems intended for continuous use. No published reliability measures, recovery times or results from prolonged disconnected operation accompanied the launch. Similarly, the system’s capacity to ingest additional sensors will depend on the interfaces and information sharing permissions available to the customer rather than on its software architecture alone.

The company envisages future integration with wider operations across multiple domains, drawing on its existing surveillance and command system activities in the air, land and maritime environments. Exchanging information between space systems and other military networks requires common data definitions, operational permissions and appropriate security boundaries. The launch establishes the intended software framework for those exchanges, but it does not confirm that a particular combined operational network has been brought into service.

Andy Keough, managing director of Saab Australia, has linked the project to domestic command system expertise and the development of Australian defence capability. The work adds a locally developed software and systems engineering product to the country’s space security sector, while Saab plans to market it internationally. No disclosed contract value, customer list or delivery timetable allows the scale of that prospective business to be quantified.

The next measurable developments will be customer integrations, operational testing and evidence of how AMS performs with live surveillance and mission systems. Saab has delivered a new software offering with a defined architecture and intended service model; its effect on operational decisions cannot yet be judged from the platform description alone.