AIMS-ISR combines local sensor control, moving-map display, cross-cueing and mission recording on crewed, uncrewed and maritime platforms. AIMS-C4 shares and archives the operating picture through browser clients; MissionLink provides an integration service inside its server architecture. Named integrations include AIMS-ISR 10 with HENSOLDT PrecISR, the Greek DA62 MPP delivery configuration and AIMS sensor fusion for the Royal Navy’s Peregrine S-100. Licensing, interfaces and platform acceptance remain configuration-specific.
Technical detail
Core features
AIMS-ISR local plugins for EO/IR and radar control, georeferenced maps, AIS/ADS-B display, cross-cueing and KLV-recorded mission review
MissionLink Rust service in the C4 Kubernetes cluster; inherited authentication including LDAP integration, REST GET/POST, XML UI definitions and Lua scripting
AIMS-ISR 10/PrecISR integration for radar control, SAR/ISAR imagery, moving-target indication and range profiles, with C4 dissemination
Public EULA excludes navigation/terrain avoidance and retains source code; customer device, integration and transfer rights follow agreed terms
Mission software and data
Sensing and isr
Communications and cyber
Use & integration
Recorded applications
Maritime and airborne mission-operator situational awareness and evidence review
Uncrewed payload/sensor fusion and shared operating pictures for configured patrol systems
Civil-protection surveillance and search and rescue on named integrated aircraft
These describe the reviewed application scope, not confirmed deployments, released requirements or procurement eligibility.
Evidence of maturity
Commercial mission software with named delivered integrations. Diamond reports the Greek DA62 MPP fleet delivered in October 2025; the Royal Navy reports Peregrine service entry in September 2025. Finnish MVX remains an integration/future-delivery case, not an accepted operational deployment.
Commercial availability
Licensed software with integration and maintenance. Sensor plugins, device rights, host/server configuration and platform acceptance are agreed for each customer; public standard terms do not prove every negotiated entitlement.
Integration and verification
Readiness
A technology readiness level is not established by the reviewed public sources.
AIMS supplies the operator-tool layer for uncrewed monitoring: Schiebel’s Peregrine configuration fuses S-100 radar, EO/IR and AIS into an operating picture for the human operator and host ship. This aligns with the mission’s uncrewed systems and operator-tools definition. It does not establish autonomous flight control, navigation approval or undersea sensing; the public EULA excludes navigation and terrain avoidance.
AIMS Maritime Mission Software may help teams working on Persistent uncrewed underwater surveillance by contributing to maritime and undersea operations, detection and situational awareness, and autonomous and uncrewed systems.
This is a reviewed public-source assessment. It is not procurement eligibility, endorsement, customer interest, or classified demand.
Original sources 12 linked records
These records support this capability and its published Mission area and Defence need connections. A source count is not a count of independent confirmations.
The aircraft manufacturer reports delivery of all three DA62 MPP aircraft to the Greek Ministry of Climate Crisis and Civil Protection in October 2025. The specified configuration includes Trakka TC375 EO/IR, Smith Myers ARTEMIS, CarteNav AIMS-ISR, LOS/BLOS and 4G/5G communications. ATESE was the prime contractor. This establishes a delivered named integration for surveillance, firefighting and SAR; neither a separate CarteNav contract value nor measured software performance is disclosed.
Supports: Capability · maturity
The aircraft manufacturer reports delivery of all three DA62 MPP aircraft to the Greek Ministry of Climate Crisis and Civil Protection in October 2025. The specified configuration includes Trakka TC375 EO/IR, Smith Myers ARTEMIS, CarteNav AIMS-ISR, LOS/BLOS and 4G/5G communications. ATESE was the prime contractor. This establishes a delivered named integration for surveillance, firefighting and SAR; neither a separate CarteNav contract value nor measured software performance is disclosed.
Supports: Capability · technology readiness level
The aircraft manufacturer reports delivery of all three DA62 MPP aircraft to the Greek Ministry of Climate Crisis and Civil Protection in October 2025. The specified configuration includes Trakka TC375 EO/IR, Smith Myers ARTEMIS, CarteNav AIMS-ISR, LOS/BLOS and 4G/5G communications. ATESE was the prime contractor. This establishes a delivered named integration for surveillance, firefighting and SAR; neither a separate CarteNav contract value nor measured software performance is disclosed.
Supports: Capability · summary
The aircraft manufacturer reports delivery of all three DA62 MPP aircraft to the Greek Ministry of Climate Crisis and Civil Protection in October 2025. The specified configuration includes Trakka TC375 EO/IR, Smith Myers ARTEMIS, CarteNav AIMS-ISR, LOS/BLOS and 4G/5G communications. ATESE was the prime contractor. This establishes a delivered named integration for surveillance, firefighting and SAR; neither a separate CarteNav contract value nor measured software performance is disclosed.
The cited durable product or government material supports the named capability, its principal features and its existing applications; the containerized ASW fit remains a derived analyst assessment.
Supports: Capability · defence applications
CarteNav markets AIMS-ISR at shipboard consoles to integrate radar, EO/IR and AIS, and AIMS-C4 to distribute the picture to fleet/shore users. It identifies embarked S-100 unmanned aircraft as a shipborne application. The page describes surface and air surveillance; it does not identify an acoustic/sonobuoy processor, sonar interface or accepted containerized ASW system.
Supports: Defence need · Persistent uncrewed underwater surveillance
AIMS-C4 is commercial browser-based mission-data management software: shared operating picture, live asset display, messaging, third-party integrations, agency permissions and searchable imagery/video/radar/metadata archive. Deployment is demonstrated/configured with the customer. The public page names cloud browser access but does not specify a universal hosting jurisdiction, security accreditation or availability commitment.
Supports: Capability · technical tags
AIMS-C4 is commercial browser-based mission-data management software: shared operating picture, live asset display, messaging, third-party integrations, agency permissions and searchable imagery/video/radar/metadata archive. Deployment is demonstrated/configured with the customer. The public page names cloud browser access but does not specify a universal hosting jurisdiction, security accreditation or availability commitment.
CanadaBuys amendment 001 to CW2387618, dated February 10, 2026, adds CAD 33,342.75 to AIMS-ISR software maintenance for DND, bringing the contract total to CAD 64,960.88 and extending the period through February 28, 2027 (start March 1, 2025). PSPC is contracting authority. This is maintenance procurement, not an aircraft purchase; the record’s 55-employee supplier entry is not an independently audited current headcount.
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · technical tags
Public sources cited · Facts and assessments kept separate · Human review
The cited durable product or government material supports the named capability, its principal features and its existing applications; the containerized ASW fit remains a derived analyst assessment.
Supports: Capability · summary
AIMS-C4 is commercial browser-based mission-data management software: shared operating picture, live asset display, messaging, third-party integrations, agency permissions and searchable imagery/video/radar/metadata archive. Deployment is demonstrated/configured with the customer. The public page names cloud browser access but does not specify a universal hosting jurisdiction, security accreditation or availability commitment.
Supports: Capability · capability type
AIMS-C4 is commercial browser-based mission-data management software: shared operating picture, live asset display, messaging, third-party integrations, agency permissions and searchable imagery/video/radar/metadata archive. Deployment is demonstrated/configured with the customer. The public page names cloud browser access but does not specify a universal hosting jurisdiction, security accreditation or availability commitment.
Supports: Capability · core features
AIMS-C4 is commercial browser-based mission-data management software: shared operating picture, live asset display, messaging, third-party integrations, agency permissions and searchable imagery/video/radar/metadata archive. Deployment is demonstrated/configured with the customer. The public page names cloud browser access but does not specify a universal hosting jurisdiction, security accreditation or availability commitment.
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · technicaldomainslugs
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · technicaldomainslugs
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · technicaldomainslugs
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · core features
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · core features
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · defence applications
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · technology readiness level
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · maturity
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · technical tags
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · core features
The November 5, 2025 technical explanation describes MissionLink as a lightweight Rust service within the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration including customer LDAP. Its REST API uses HTTP GET/POST; AIMS Markup Language uses XML-defined UI with Lua scripting. Sequenced events and attachments support bidirectional data and GPX-route exchange; the illustrated route change requires operator acceptance. These are vendor-described interfaces and examples, not public API conformance tests or an autonomous flight authorization.
Supports: Capability · commercial availability
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · name
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · summary
The November 5, 2025 technical explanation describes MissionLink as a lightweight Rust service within the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration including customer LDAP. Its REST API uses HTTP GET/POST; AIMS Markup Language uses XML-defined UI with Lua scripting. Sequenced events and attachments support bidirectional data and GPX-route exchange; the illustrated route change requires operator acceptance. These are vendor-described interfaces and examples, not public API conformance tests or an autonomous flight authorization.
Supports: Capability · technical tags
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · core features
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Capability · summary
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Mission area · Autonomous Patrol and Monitoring
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Mission area · Autonomous Patrol and Monitoring
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Mission area · Autonomous Patrol and Monitoring
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
Supports: Mission area · Autonomous Patrol and Monitoring
CarteNav describes MissionLink as an integration service in the AIMS-C4 Kubernetes cluster, inheriting C4 access/authentication integration. AIMS-ISR serves local sensor control and moving-map display; browser-based C4 distributes and archives data. Integration still depends on supported interfaces and customer security configuration.
AIMS-ISR uses modular sensor plugins and georeferenced moving maps for local operator workstations. Documented functions include EO/IR and radar control, AIS/ADS-B display, multi-cue tracking, configurable alerts/filters, recording and post-mission review with KLV metadata. Kestrel MTI is an integrated video-analysis option; the host software does not itself establish detection performance or universal sensor compatibility.
Supports: Capability · name
AIMS-ISR uses modular sensor plugins and georeferenced moving maps for local operator workstations. Documented functions include EO/IR and radar control, AIS/ADS-B display, multi-cue tracking, configurable alerts/filters, recording and post-mission review with KLV metadata. Kestrel MTI is an integrated video-analysis option; the host software does not itself establish detection performance or universal sensor compatibility.
Supports: Capability · capability type
AIMS-ISR uses modular sensor plugins and georeferenced moving maps for local operator workstations. Documented functions include EO/IR and radar control, AIS/ADS-B display, multi-cue tracking, configurable alerts/filters, recording and post-mission review with KLV metadata. Kestrel MTI is an integrated video-analysis option; the host software does not itself establish detection performance or universal sensor compatibility.
Supports: Capability · technical tags
AIMS-ISR uses modular sensor plugins and georeferenced moving maps for local operator workstations. Documented functions include EO/IR and radar control, AIS/ADS-B display, multi-cue tracking, configurable alerts/filters, recording and post-mission review with KLV metadata. Kestrel MTI is an integrated video-analysis option; the host software does not itself establish detection performance or universal sensor compatibility.
Supports: Capability · technical tags
AIMS-ISR uses modular sensor plugins and georeferenced moving maps for local operator workstations. Documented functions include EO/IR and radar control, AIS/ADS-B display, multi-cue tracking, configurable alerts/filters, recording and post-mission review with KLV metadata. Kestrel MTI is an integrated video-analysis option; the host software does not itself establish detection performance or universal sensor compatibility.
Supports: Capability · summary
AIMS-ISR uses modular sensor plugins and georeferenced moving maps for local operator workstations. Documented functions include EO/IR and radar control, AIS/ADS-B display, multi-cue tracking, configurable alerts/filters, recording and post-mission review with KLV metadata. Kestrel MTI is an integrated video-analysis option; the host software does not itself establish detection performance or universal sensor compatibility.
Supports: Capability · technicaldomainslugs
AIMS-ISR uses modular sensor plugins and georeferenced moving maps for local operator workstations. Documented functions include EO/IR and radar control, AIS/ADS-B display, multi-cue tracking, configurable alerts/filters, recording and post-mission review with KLV metadata. Kestrel MTI is an integrated video-analysis option; the host software does not itself establish detection performance or universal sensor compatibility.
Supports: Capability · core features
AIMS-ISR uses modular sensor plugins and georeferenced moving maps for local operator workstations. Documented functions include EO/IR and radar control, AIS/ADS-B display, multi-cue tracking, configurable alerts/filters, recording and post-mission review with KLV metadata. Kestrel MTI is an integrated video-analysis option; the host software does not itself establish detection performance or universal sensor compatibility.
Schiebel’s February 10, 2023 original Peregrine contract release names CarteNav AIMS as the mission system fusing Thales I-Master radar, EO/IR and AIS on the S-100. Imagery and radar data go to a human system operator and the host ship combat-management system. The named supplier configuration establishes an uncrewed operator-tool integration; it is not an independent acceptance test, navigation system or undersea acoustic interface.
Supports: Capability · defence applications
Schiebel’s February 10, 2023 original Peregrine contract release names CarteNav AIMS as the mission system fusing Thales I-Master radar, EO/IR and AIS on the S-100. Imagery and radar data go to a human system operator and the host ship combat-management system. The named supplier configuration establishes an uncrewed operator-tool integration; it is not an independent acceptance test, navigation system or undersea acoustic interface.
Supports: Mission area · Autonomous Patrol and Monitoring
Schiebel’s February 10, 2023 original Peregrine contract release names CarteNav AIMS as the mission system fusing Thales I-Master radar, EO/IR and AIS on the S-100. Imagery and radar data go to a human system operator and the host ship combat-management system. The named supplier configuration establishes an uncrewed operator-tool integration; it is not an independent acceptance test, navigation system or undersea acoustic interface.
Supports: Mission area · Autonomous Patrol and Monitoring
Schiebel’s February 10, 2023 original Peregrine contract release names CarteNav AIMS as the mission system fusing Thales I-Master radar, EO/IR and AIS on the S-100. Imagery and radar data go to a human system operator and the host ship combat-management system. The named supplier configuration establishes an uncrewed operator-tool integration; it is not an independent acceptance test, navigation system or undersea acoustic interface.
Supports: Mission area · Autonomous Patrol and Monitoring
Schiebel’s February 10, 2023 original Peregrine contract release names CarteNav AIMS as the mission system fusing Thales I-Master radar, EO/IR and AIS on the S-100. Imagery and radar data go to a human system operator and the host ship combat-management system. The named supplier configuration establishes an uncrewed operator-tool integration; it is not an independent acceptance test, navigation system or undersea acoustic interface.
Supports: Mission area · Autonomous Patrol and Monitoring
Schiebel’s February 10, 2023 original Peregrine contract release names CarteNav AIMS as the mission system fusing Thales I-Master radar, EO/IR and AIS on the S-100. Imagery and radar data go to a human system operator and the host ship combat-management system. The named supplier configuration establishes an uncrewed operator-tool integration; it is not an independent acceptance test, navigation system or undersea acoustic interface.
The Royal Navy announced formal entry into service of Peregrine after trials and operations aboard HMS Lancaster in the Gulf. Thales and Schiebel supply the system, including I-Master radar. The operator release corroborates program maturity, but does not identify the AIMS version or independently evaluate CarteNav software performance.
CarteNav and HENSOLDT announced PrecISR radar integration with AIMS-ISR 10 in July 2025. The release establishes a named interface partnership, not a new 2026 aircraft award. Vendor pages conflict between 40-plus and 60-plus deployment countries, so no single unqualified geographic count is proposed.
Supports: Capability · core features
CarteNav and HENSOLDT announced PrecISR radar integration with AIMS-ISR 10 in July 2025. The release establishes a named interface partnership, not a new 2026 aircraft award. Vendor pages conflict between 40-plus and 60-plus deployment countries, so no single unqualified geographic count is proposed.
Supports: Capability · core features
The July 18, 2025 joint announcement integrates AIMS-ISR 10 with HENSOLDT PrecISR for unified radar control and SAR/ISAR imagery, moving-target indication and range-profile data in the local picture. AIMS-C4 can disseminate/archive the radar data. No named accepted platform delivery, aircraft purchase or unrestricted sensor-interface assurance is established by this announcement.
Supports: Capability · summary
The July 18, 2025 joint announcement integrates AIMS-ISR 10 with HENSOLDT PrecISR for unified radar control and SAR/ISAR imagery, moving-target indication and range-profile data in the local picture. AIMS-C4 can disseminate/archive the radar data. No named accepted platform delivery, aircraft purchase or unrestricted sensor-interface assurance is established by this announcement.
SNC received the first Challenger 650 for Finnish MVX systems integration at Hagerstown. Its October 2, 2025 statement anticipates first delivery in early 2027 and the second a year later. These later dates supersede earlier 2026/2027 delivery targets; receipt by the integrator is not delivery to the operational customer or proof of the accepted AIMS software version.
The published EULA licenses executables for internal operations, ordinarily one copy per paid licence/device, and retains source code and modification ownership with CarteNav. It explicitly excludes use as navigation or terrain-avoidance software. Transfers normally need consent, with an express intermediary exception. Compatibility and warranty attach to the applicable quote/specifications; this public standard form is not evidence of a specific customer’s negotiated terms.
Supports: Capability · core features
The published EULA licenses executables for internal operations, ordinarily one copy per paid licence/device, and retains source code and modification ownership with CarteNav. It explicitly excludes use as navigation or terrain-avoidance software. Transfers normally need consent, with an express intermediary exception. Compatibility and warranty attach to the applicable quote/specifications; this public standard form is not evidence of a specific customer’s negotiated terms.
Supports: Mission area · Autonomous Patrol and Monitoring
The published EULA licenses executables for internal operations, ordinarily one copy per paid licence/device, and retains source code and modification ownership with CarteNav. It explicitly excludes use as navigation or terrain-avoidance software. Transfers normally need consent, with an express intermediary exception. Compatibility and warranty attach to the applicable quote/specifications; this public standard form is not evidence of a specific customer’s negotiated terms.
Supports: Mission area · Autonomous Patrol and Monitoring
The published EULA licenses executables for internal operations, ordinarily one copy per paid licence/device, and retains source code and modification ownership with CarteNav. It explicitly excludes use as navigation or terrain-avoidance software. Transfers normally need consent, with an express intermediary exception. Compatibility and warranty attach to the applicable quote/specifications; this public standard form is not evidence of a specific customer’s negotiated terms.
Supports: Mission area · Autonomous Patrol and Monitoring
The published EULA licenses executables for internal operations, ordinarily one copy per paid licence/device, and retains source code and modification ownership with CarteNav. It explicitly excludes use as navigation or terrain-avoidance software. Transfers normally need consent, with an express intermediary exception. Compatibility and warranty attach to the applicable quote/specifications; this public standard form is not evidence of a specific customer’s negotiated terms.
Supports: Mission area · Autonomous Patrol and Monitoring
The published EULA licenses executables for internal operations, ordinarily one copy per paid licence/device, and retains source code and modification ownership with CarteNav. It explicitly excludes use as navigation or terrain-avoidance software. Transfers normally need consent, with an express intermediary exception. Compatibility and warranty attach to the applicable quote/specifications; this public standard form is not evidence of a specific customer’s negotiated terms.
Supports: Defence need · Persistent uncrewed underwater surveillance
The official requirement calls for long-duration uncrewed vehicles that deploy and employ sensors to provide persistent coverage, with initial delivery anticipated in 2035/2036.
Supports: Defence need · Persistent uncrewed underwater surveillance
The project requires persistent sensor coverage in strategic northern, coastal and expeditionary areas and identifies sonar and acoustic systems among the relevant investment capabilities.
