CarteNav is a Canadian mission-software company and PAL Aerospace subsidiary whose AIMS-ISR and AIMS-C4 products integrate sensors, mission data and common operating pictures across airborne, maritime and command environments.
Operating context
AIMS-ISR runs local sensor plugins, moving maps, cross-cueing and mission recording; AIMS-C4 provides browser access to a shared picture, messaging and archives. MissionLink is a Rust service in the C4 Kubernetes cluster, with inherited authentication including LDAP integration, REST GET/POST interfaces and XML/Lua-defined controls. Its illustrated route transfer still requires operator acceptance. The AIMS-ISR 10/PrecISR integration establishes named radar control and imagery/moving-target data, not universal sensor compatibility. The published licence excludes navigation and terrain avoidance. Customer versions, interface packages, hosting jurisdiction, security accreditation, data-release rules and performance over constrained links require configuration-specific agreement and acceptance.
Canadian footprint
CarteNav’s current official headquarters is 1701 Hollis Street, Suite 1000, Halifax, Nova Scotia, with Canadian mission-software development, integration and support. The DND maintenance record lists 55 employees and an older Halifax address; that supplier entry is not an independently audited current headcount or evidence of another operating site. PAL’s wider aircraft, facilities, workforce and flight hours are not CarteNav’s standalone capacity.
Halifax, Nova Scotia is the published city-level context for CarteNav. It does not imply a street address or exact facility location.
CarteNav offers a Canadian software layer for combining sensor control, mission evidence and shared operating pictures across crewed, uncrewed and maritime platforms. Named Greek delivery, Peregrine integration and DND maintenance evidence make the commercial role concrete. A buyer still needs an accepted version/sensor package, hosting and data controls, and long-term licensing/support terms. The evidence supports monitoring operator tools; it does not establish undersea sensing, autonomous navigation or parent aircraft capacity as a CarteNav capability.
Interpretation of the public record. Not qualification, endorsement or evidence of buyer interest.
Multi-sensor ISR mission management and common operating picture software
Read technical summary
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.
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.
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
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
On February 10, 2026, CanadaBuys recorded amendment 001 to CarteNav’s AIMS-ISR maintenance contract CW2387618 for DND. It adds CAD 33,342.75 to the original CAD 31,618.13, bringing the total to CAD 64,960.88 and extending the contract period to February 28, 2027. The procurement concerns software maintenance and renewal, with PSPC as contracting authority.
Commercially licensed mission software with sensor/platform integration and maintenance. The public standard licence provides executable-use rights tied to the quote and device; DND’s AIMS-ISR maintenance renewal and named delivered aircraft integrations establish a continuing product business.
Financing and disclosed activity
EIC’s August 2016 acquisition of all CarteNav shares had a price of up to CAD 17 million, subject to earnings and closing adjustments, financed in cash through EIC’s credit facility. This is a historical acquisition price. The OSC Tech Companion collaboration has a CAD 1.4 million project total and CAD 639,750 OSC contribution; no CarteNav allocation is disclosed. ACOA’s CAD 7.5 million conditionally repayable 2026 contribution names PAL Aerospace, not CarteNav. Standalone current revenue, financing raised and the software company’s share of parent/project funding are not established.
Ownership and entity scope
CarteNav Solutions is a PAL Aerospace subsidiary within publicly listed Exchange Income Corporation (TSX: EIF). EIC completed the all-share acquisition on August 8, 2016, when its filing identified CarteNav as wholly owned by Provincial Aerospace. The current CarteNav profile continues to identify the PAL/EIC subsidiary chain.
Programs and deployments
DND AIMS-ISR Maintenance – CW2387618
Contracted software supplier
Sponsor or operator: Department of National Defence
Contracted
Organization role. CarteNav Solutions Inc. received the February 14, 2025 original CAD 31,618.13 contract. Amendment 001 dated February 10, 2026 adds CAD 33,342.75, for a cumulative CAD 64,960.88 and a March 1, 2025 to February 28, 2027 period. The directed/non-competitive record cites exclusive rights.
Program. DND AIMS-ISR software support and maintenance renewal, contracted through PSPC under CW2387618 / solicitation WS4924697234. This is software maintenance procurement rather than an aircraft or sensor-system purchase.
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.
Which AIMS/MissionLink versions, sensor plugins, hosting controls and data-release rules are accepted for the intended platform and links?
Local AIMS-ISR, distributed C4 and MissionLink have distinct roles. Public REST/XML/Lua descriptions and named PrecISR integration do not provide a versioned conformance test, customer accreditation or link-performance guarantee.
02
What executable, integration, transfer and export rights apply to the customer’s configuration and planned downstream users?
The public EULA retains source code, limits device use and constrains transfers, with an intermediary exception. The general terms provide for export permission when needed. Navigation and terrain avoidance are explicitly outside the licensed software use.
03
What CarteNav staffing and funded workshare are committed to the proposed integration and long-term maintenance?
The supplier record lists 55 employees without an independent current audit. OSC project funding and the 2026 PAL contribution are not allocated to CarteNav in the inspected originals, and parent airframe capacity cannot establish software-team capacity.
Original sources 26 linked records
These records support the organization, its owned capabilities and their reviewed connections. A source count is not a count of independent confirmations.
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: Profile · operating context
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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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.
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.
The cited complementary source supports the carefully attributed current product, integration, program or operating activity summarized for the reviewer.
CarteNav's public evidence establishes its current role and offering, but it does not answer every access, configuration, eligibility, maturity or buyer question needed for a first business-development conversation.
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.
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.
The Ocean Supercluster identifies a $1.4 million Tech Companion operational and in-service support project with Modest Tree Media, CarteNav Solutions and Mitacs. CarteNav contributes sensor/IoT data integration for remotely accessible maintenance information and augmented-reality visualization. The project total is not a CarteNav grant allocation, company revenue or proof that CarteNav owns the Tech Companion product.
Supports: Tech Companion – Operational and In-Service Support · canonical program
Public sources cited · Facts and assessments kept separate · Human review
Tech Companion – Operational and In-Service Support
Technical collaborator
Sponsor or operator: Canada’s Ocean Supercluster
Delivering
Organization role. CarteNav participates with Modest Tree Media and other collaborators through sensor/IoT datasets and integration. The OSC 2023–2024 report records CAD 639,750 OSC funding and labels the project as closing while pipeline-application code integration with CarteNav datasets continues. No company-specific grant share or completed customer deployment is disclosed.
Program. A collaborative project extending a remotely accessible digital service hub for ocean-equipment maintenance and in-service support, including sensor/data integration and augmented-reality visualization. The announced total project value is CAD 1.4 million.
SNC identifies AIMS mission management in its RAPCON-X configuration for Finnish MVX. Its October 2025 update places the first aircraft at the integration stage and forecasts first customer delivery in early 2027, with the second a year later. The Finnish buyer separately distinguishes design approval, delivery, training and eventual operational capability.
Platform Integration Partner
Diamond Aircraft
Diamond’s November 2025 delivery report identifies AIMS-ISR with Trakka TC375 and Smith Myers ARTEMIS on three DA62 MPP aircraft delivered to Greece’s civil-protection ministry in October 2025. ATESE was the prime contractor; no separate CarteNav order value is disclosed.
Platform Integration Partner
Schiebel
Schiebel’s February 10, 2023 Peregrine release names CarteNav AIMS as the software fusing I-Master radar, EO/IR and AIS for the S-100 system operator and host-ship picture. The Royal Navy announced program service entry in September 2025; its release does not verify a particular AIMS version.
Sensor Integration Partner
HENSOLDT
The July 18, 2025 joint release names AIMS-ISR 10 integration with HENSOLDT PrecISR for unified radar control, imagery, moving-target data and C4 sharing. It does not identify a newly accepted platform delivery. The source names HENSOLDT, without assigning the role to the distinct HENSOLDT Canada identity.
CarteNav is a PAL Aerospace subsidiary in the Exchange Income Corporation group. EIC’s August 2016 all-share acquisition and financial filing identify it as wholly owned by Provincial Aerospace at closing; CarteNav’s current profile continues to name the PAL/EIC subsidiary chain. Parent aircraft operations and financing are not separately allocated to CarteNav.
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.
Reviewed connections indicate possible relevance based on public evidence. They do not indicate procurement direction, eligibility, endorsement or customer interest.
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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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.
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.
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: Profile · operating context
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.
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.
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: Profile · operating context
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.
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.
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: AIMS mission management and common operating picture software · capability type
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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software → 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: AIMS mission management and common operating picture software → 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: AIMS mission management and common operating picture software → 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: AIMS mission management and common operating picture software → 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: Profile · profileData.currentActivity
The cited complementary source supports the carefully attributed current product, integration, program or operating activity summarized for the reviewer.
Supports: Profile · operating context
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: AIMS mission management and common operating picture software · summary
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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software → Persistent uncrewed underwater surveillance
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: Profile · operating context
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.
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: AIMS mission management and common operating picture software · summary
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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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.
Supports: sensor_integration_partner relationship
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: sensor_integration_partner relationship
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: sensor_integration_partner relationship
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: sensor_integration_partner relationship
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.
The Ocean Supercluster identifies a $1.4 million Tech Companion operational and in-service support project with Modest Tree Media, CarteNav Solutions and Mitacs. CarteNav contributes sensor/IoT data integration for remotely accessible maintenance information and augmented-reality visualization. The project total is not a CarteNav grant allocation, company revenue or proof that CarteNav owns the Tech Companion product.
Supports: Tech Companion – Operational and In-Service Support · canonical program
The Ocean Supercluster identifies a $1.4 million Tech Companion operational and in-service support project with Modest Tree Media, CarteNav Solutions and Mitacs. CarteNav contributes sensor/IoT data integration for remotely accessible maintenance information and augmented-reality visualization. The project total is not a CarteNav grant allocation, company revenue or proof that CarteNav owns the Tech Companion product.
Supports: Tech Companion – Operational and In-Service Support · canonical program
The Ocean Supercluster identifies a $1.4 million Tech Companion operational and in-service support project with Modest Tree Media, CarteNav Solutions and Mitacs. CarteNav contributes sensor/IoT data integration for remotely accessible maintenance information and augmented-reality visualization. The project total is not a CarteNav grant allocation, company revenue or proof that CarteNav owns the Tech Companion product.
Supports: Tech Companion – Operational and In-Service Support · canonical program
The Ocean Supercluster identifies a $1.4 million Tech Companion operational and in-service support project with Modest Tree Media, CarteNav Solutions and Mitacs. CarteNav contributes sensor/IoT data integration for remotely accessible maintenance information and augmented-reality visualization. The project total is not a CarteNav grant allocation, company revenue or proof that CarteNav owns the Tech Companion product.
Supports: Tech Companion – Operational and In-Service Support · canonical program
The Ocean Supercluster identifies a $1.4 million Tech Companion operational and in-service support project with Modest Tree Media, CarteNav Solutions and Mitacs. CarteNav contributes sensor/IoT data integration for remotely accessible maintenance information and augmented-reality visualization. The project total is not a CarteNav grant allocation, company revenue or proof that CarteNav owns the Tech Companion product.
Supports: Tech Companion – Operational and In-Service Support · canonical program
The Ocean Supercluster identifies a $1.4 million Tech Companion operational and in-service support project with Modest Tree Media, CarteNav Solutions and Mitacs. CarteNav contributes sensor/IoT data integration for remotely accessible maintenance information and augmented-reality visualization. The project total is not a CarteNav grant allocation, company revenue or proof that CarteNav owns the Tech Companion product.
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.
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.
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.
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.
Supports: Profile · current activity
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.
Supports: Profile · defence posture
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.
Supports: Profile · executive relevance summary
Source location: executiveRelevanceSummary
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.
Supports: Profile · current activity as of
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.
Supports: Profile · canadian footprint
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.
Supports: Profile · commercial status
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.
Supports: AIMS mission management and common operating picture software · commercial availability
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Supports: DND AIMS-ISR Maintenance – CW2387618 · canonical program
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.
Supports: DND AIMS-ISR Maintenance – CW2387618 · canonical program
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.
Supports: DND AIMS-ISR Maintenance – CW2387618 · canonical program
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.
Supports: DND AIMS-ISR Maintenance – CW2387618 · canonical program
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.
Supports: DND AIMS-ISR Maintenance – CW2387618 · canonical program
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.
Supports: DND AIMS-ISR Maintenance – CW2387618 · canonical program
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.
EIC’s second-quarter 2016 report (MD&A p7 and financial note15 p44) identifies CarteNav as a wholly owned subsidiary of Provincial after the August 8, 2016 close. The Canadian-dollar financial note gives a price up to CAD 17 million, contingent on earnings and post-closing adjustments; results consolidate into EIC from Q3 2016. These are historical ownership and acquisition terms, not CarteNav’s current revenue or new capital raised.
Supports: Profile · disclosed financing summary
EIC’s second-quarter 2016 report (MD&A p7 and financial note15 p44) identifies CarteNav as a wholly owned subsidiary of Provincial after the August 8, 2016 close. The Canadian-dollar financial note gives a price up to CAD 17 million, contingent on earnings and post-closing adjustments; results consolidate into EIC from Q3 2016. These are historical ownership and acquisition terms, not CarteNav’s current revenue or new capital raised.
Supports: subsidiary_of relationship
EIC’s second-quarter 2016 report (MD&A p7 and financial note15 p44) identifies CarteNav as a wholly owned subsidiary of Provincial after the August 8, 2016 close. The Canadian-dollar financial note gives a price up to CAD 17 million, contingent on earnings and post-closing adjustments; results consolidate into EIC from Q3 2016. These are historical ownership and acquisition terms, not CarteNav’s current revenue or new capital raised.
Supports: subsidiary_of relationship
EIC’s second-quarter 2016 report (MD&A p7 and financial note15 p44) identifies CarteNav as a wholly owned subsidiary of Provincial after the August 8, 2016 close. The Canadian-dollar financial note gives a price up to CAD 17 million, contingent on earnings and post-closing adjustments; results consolidate into EIC from Q3 2016. These are historical ownership and acquisition terms, not CarteNav’s current revenue or new capital raised.
Supports: subsidiary_of relationship
EIC’s second-quarter 2016 report (MD&A p7 and financial note15 p44) identifies CarteNav as a wholly owned subsidiary of Provincial after the August 8, 2016 close. The Canadian-dollar financial note gives a price up to CAD 17 million, contingent on earnings and post-closing adjustments; results consolidate into EIC from Q3 2016. These are historical ownership and acquisition terms, not CarteNav’s current revenue or new capital raised.
Supports: subsidiary_of relationship
EIC’s second-quarter 2016 report (MD&A p7 and financial note15 p44) identifies CarteNav as a wholly owned subsidiary of Provincial after the August 8, 2016 close. The Canadian-dollar financial note gives a price up to CAD 17 million, contingent on earnings and post-closing adjustments; results consolidate into EIC from Q3 2016. These are historical ownership and acquisition terms, not CarteNav’s current revenue or new capital raised.
The official public contact pathway for CarteNav is https://cartenav.com/.
Supports: Profile · description
The cited official source supports CarteNav's Canadian identity and the bounded organization description prepared for review.
Supports: Profile · profileData.publicContact
The official organization material supports the Canadian location and public contact route summarized in this candidate.
Supports: Profile · ownership
Founded in 2002, CarteNav Solutions describes itself as a PAL Aerospace subsidiary within Exchange Income Corporation. It develops ISR mission software for defence/security and civil safety, economic and environmental operations. Its 600-installation/over-40-country statement differs from over-60-country wording in other current company articles; no normalized deployment count is established.
Supports: Profile · current activity
True North Map classifies the legacy undated product description as operating context rather than a material current development, so the optional Recent Activity field is cleared.
Supports: Profile · canadian footprint
Founded in 2002, CarteNav Solutions describes itself as a PAL Aerospace subsidiary within Exchange Income Corporation. It develops ISR mission software for defence/security and civil safety, economic and environmental operations. Its 600-installation/over-40-country statement differs from over-60-country wording in other current company articles; no normalized deployment count is established.
Supports: Profile · founded year
Founded in 2002, CarteNav Solutions describes itself as a PAL Aerospace subsidiary within Exchange Income Corporation. It develops ISR mission software for defence/security and civil safety, economic and environmental operations. Its 600-installation/over-40-country statement differs from over-60-country wording in other current company articles; no normalized deployment count is established.
Supports: Profile · editorial profile version
CarteNav has sufficient mapped public evidence for private reviewer consideration of the shared editorial profile template.
Supports: subsidiary_of relationship
Founded in 2002, CarteNav Solutions describes itself as a PAL Aerospace subsidiary within Exchange Income Corporation. It develops ISR mission software for defence/security and civil safety, economic and environmental operations. Its 600-installation/over-40-country statement differs from over-60-country wording in other current company articles; no normalized deployment count is established.
Supports: subsidiary_of relationship
Founded in 2002, CarteNav Solutions describes itself as a PAL Aerospace subsidiary within Exchange Income Corporation. It develops ISR mission software for defence/security and civil safety, economic and environmental operations. Its 600-installation/over-40-country statement differs from over-60-country wording in other current company articles; no normalized deployment count is established.
Supports: subsidiary_of relationship
Founded in 2002, CarteNav Solutions describes itself as a PAL Aerospace subsidiary within Exchange Income Corporation. It develops ISR mission software for defence/security and civil safety, economic and environmental operations. Its 600-installation/over-40-country statement differs from over-60-country wording in other current company articles; no normalized deployment count is established.
Supports: subsidiary_of relationship
Founded in 2002, CarteNav Solutions describes itself as a PAL Aerospace subsidiary within Exchange Income Corporation. It develops ISR mission software for defence/security and civil safety, economic and environmental operations. Its 600-installation/over-40-country statement differs from over-60-country wording in other current company articles; no normalized deployment count is established.
EIC announced on August 8, 2016 that it closed the acquisition of all issued and outstanding CarteNav shares for up to $17 million, subject to earn-out and post-closing adjustments. Consideration was cash financed through EIC’s existing credit facility. This is historical acquisition consideration, not a current financing round or software revenue.
Supports: Profile · ownership
EIC announced on August 8, 2016 that it closed the acquisition of all issued and outstanding CarteNav shares for up to $17 million, subject to earn-out and post-closing adjustments. Consideration was cash financed through EIC’s existing credit facility. This is historical acquisition consideration, not a current financing round or software revenue.
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.
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.
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: Profile · executive relevance summary
Source location: executiveRelevanceSummary
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.
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: Profile · operating context
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.
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.
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: AIMS mission management and common operating picture software · commercial availability
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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software → 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: AIMS mission management and common operating picture software → 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: AIMS mission management and common operating picture software → 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: AIMS mission management and common operating picture software → 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.
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: Profile · defence posture
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: AIMS mission management and common operating picture software · summary
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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software → 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: AIMS mission management and common operating picture software → 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: AIMS mission management and common operating picture software → 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: AIMS mission management and common operating picture software → 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.
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.
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.
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.
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.
Current official headquarters: 1701 Hollis Street, Suite 1000, Halifax, Nova Scotia. Public phone +1 902 446 4988 and sales email team@cartenav.com; support@cartenav.com is the product-support route. Current customer portal requires an active account. The older procurement record has a different Halifax street address; it does not establish another active office.
Current official headquarters: 1701 Hollis Street, Suite 1000, Halifax, Nova Scotia. Public phone +1 902 446 4988 and sales email team@cartenav.com; support@cartenav.com is the product-support route. Current customer portal requires an active account. The older procurement record has a different Halifax street address; it does not establish another active office.
Current official headquarters: 1701 Hollis Street, Suite 1000, Halifax, Nova Scotia. Public phone +1 902 446 4988 and sales email team@cartenav.com; support@cartenav.com is the product-support route. Current customer portal requires an active account. The older procurement record has a different Halifax street address; it does not establish another active office.
Current official headquarters: 1701 Hollis Street, Suite 1000, Halifax, Nova Scotia. Public phone +1 902 446 4988 and sales email team@cartenav.com; support@cartenav.com is the product-support route. Current customer portal requires an active account. The older procurement record has a different Halifax street address; it does not establish another active office.
Current official headquarters: 1701 Hollis Street, Suite 1000, Halifax, Nova Scotia. Public phone +1 902 446 4988 and sales email team@cartenav.com; support@cartenav.com is the product-support route. Current customer portal requires an active account. The older procurement record has a different Halifax street address; it does not establish another active office.
The Ocean Supercluster 2023–2024 annual report, printed page 61, records CAD 639,750 of OSC funding for Tech Companion Operational and In-Service Support and names Modest Tree Media, CarteNav, Mitacs, Saint Mary’s University and Microsoft. Its Project Closing row says pipeline-application development is continuing with CarteNav datasets. This supports a development collaboration, not an individually allocated CarteNav grant or proof of completed commercial deployment. The distinct Tech Companion entry on page 69 is not added to this project.
The Ocean Supercluster 2023–2024 annual report, printed page 61, records CAD 639,750 of OSC funding for Tech Companion Operational and In-Service Support and names Modest Tree Media, CarteNav, Mitacs, Saint Mary’s University and Microsoft. Its Project Closing row says pipeline-application development is continuing with CarteNav datasets. This supports a development collaboration, not an individually allocated CarteNav grant or proof of completed commercial deployment. The distinct Tech Companion entry on page 69 is not added to this project.
Supports: Tech Companion – Operational and In-Service Support · organization participation
The Ocean Supercluster 2023–2024 annual report, printed page 61, records CAD 639,750 of OSC funding for Tech Companion Operational and In-Service Support and names Modest Tree Media, CarteNav, Mitacs, Saint Mary’s University and Microsoft. Its Project Closing row says pipeline-application development is continuing with CarteNav datasets. This supports a development collaboration, not an individually allocated CarteNav grant or proof of completed commercial deployment. The distinct Tech Companion entry on page 69 is not added to this project.
Supports: Tech Companion – Operational and In-Service Support · organization participation
The Ocean Supercluster 2023–2024 annual report, printed page 61, records CAD 639,750 of OSC funding for Tech Companion Operational and In-Service Support and names Modest Tree Media, CarteNav, Mitacs, Saint Mary’s University and Microsoft. Its Project Closing row says pipeline-application development is continuing with CarteNav datasets. This supports a development collaboration, not an individually allocated CarteNav grant or proof of completed commercial deployment. The distinct Tech Companion entry on page 69 is not added to this project.
Supports: Tech Companion – Operational and In-Service Support · organization participation
The Ocean Supercluster 2023–2024 annual report, printed page 61, records CAD 639,750 of OSC funding for Tech Companion Operational and In-Service Support and names Modest Tree Media, CarteNav, Mitacs, Saint Mary’s University and Microsoft. Its Project Closing row says pipeline-application development is continuing with CarteNav datasets. This supports a development collaboration, not an individually allocated CarteNav grant or proof of completed commercial deployment. The distinct Tech Companion entry on page 69 is not added to this project.
Supports: Tech Companion – Operational and In-Service Support · organization participation
The Ocean Supercluster 2023–2024 annual report, printed page 61, records CAD 639,750 of OSC funding for Tech Companion Operational and In-Service Support and names Modest Tree Media, CarteNav, Mitacs, Saint Mary’s University and Microsoft. Its Project Closing row says pipeline-application development is continuing with CarteNav datasets. This supports a development collaboration, not an individually allocated CarteNav grant or proof of completed commercial deployment. The distinct Tech Companion entry on page 69 is not added to this project.
Supports: Tech Companion – Operational and In-Service Support · organization participation
The Ocean Supercluster 2023–2024 annual report, printed page 61, records CAD 639,750 of OSC funding for Tech Companion Operational and In-Service Support and names Modest Tree Media, CarteNav, Mitacs, Saint Mary’s University and Microsoft. Its Project Closing row says pipeline-application development is continuing with CarteNav datasets. This supports a development collaboration, not an individually allocated CarteNav grant or proof of completed commercial deployment. The distinct Tech Companion entry on page 69 is not added to this project.
Supports: Tech Companion – Operational and In-Service Support · organization participation
The Ocean Supercluster 2023–2024 annual report, printed page 61, records CAD 639,750 of OSC funding for Tech Companion Operational and In-Service Support and names Modest Tree Media, CarteNav, Mitacs, Saint Mary’s University and Microsoft. Its Project Closing row says pipeline-application development is continuing with CarteNav datasets. This supports a development collaboration, not an individually allocated CarteNav grant or proof of completed commercial deployment. The distinct Tech Companion entry on page 69 is not added to this project.
Supports: Tech Companion – Operational and In-Service Support · organization participation
The Ocean Supercluster 2023–2024 annual report, printed page 61, records CAD 639,750 of OSC funding for Tech Companion Operational and In-Service Support and names Modest Tree Media, CarteNav, Mitacs, Saint Mary’s University and Microsoft. Its Project Closing row says pipeline-application development is continuing with CarteNav datasets. This supports a development collaboration, not an individually allocated CarteNav grant or proof of completed commercial deployment. The distinct Tech Companion entry on page 69 is not added to this project.
The government grants record names PAL Aerospace and CAD 7,500,000 under agreement 228454, March 3, 2026 through September 30, 2027, as a conditionally repayable contribution. It does not establish a separate CarteNav funding award or its share of this parent-level contribution.
The government grants record names PAL Aerospace and CAD 7,500,000 under agreement 228454, March 3, 2026 through September 30, 2027, as a conditionally repayable contribution. It does not establish a separate CarteNav funding award or its share of this parent-level contribution.
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: Profile · executive relevance summary
Source location: executiveRelevanceSummary
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: AIMS mission management and common operating picture software · technicaldomainslugs
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: AIMS mission management and common operating picture software · 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.
Supports: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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.
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: Profile · executive relevance summary
Source location: executiveRelevanceSummary
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: Profile · commercial status
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: AIMS mission management and common operating picture software · defence applications
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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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: AIMS mission management and common operating picture software · 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 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 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 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 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 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.
Supports: AIMS mission management and common operating picture software · maturity
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.
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.
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.
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.
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 separates AIMS-ISR sensor and mission software from AIMS-C4 common-operating-picture and historical mission-data functions. It reports 600 installations in more than 40 countries and uses modular plugins; this vendor count does not certify every sensor, platform or deployment configuration.
PAL’s August 21, 2026 guide describes aircraft mission-system integration dependencies including electrical power, cooling, electromagnetic compatibility, connectivity and certification. AIMS software is one part of that configuration. Parent flight hours, airframe approvals and communications performance cannot be assigned to CarteNav as software-company capacity or assurance.
CanadaBuys contract CW2387618, solicitation WS4924697234, awarded February 14, 2025 to CarteNav for AIMS-ISR maintenance and support, originally records $31,618.13 for March 1, 2025–February 28, 2026. DND is buyer and PSPC contracting authority. This is software sustainment, not an aircraft or sensor procurement.
CanadaBuys contract CW2387618, solicitation WS4924697234, awarded February 14, 2025 to CarteNav for AIMS-ISR maintenance and support, originally records $31,618.13 for March 1, 2025–February 28, 2026. DND is buyer and PSPC contracting authority. This is software sustainment, not an aircraft or sensor procurement.
The public general terms make the quote/proposal and schedules the contract basis. They do not confer blanket authority to export or transmit software, and provide for a Canadian export permit and end-use statement when required. Marketing language that the software is ITAR free does not establish that a configured system has no export or release restrictions.
Sensor OEM Smith Myers describes ARTEMIS on a Nova Systems EC-135 fully integrated with CarteNav AIMS-ISR and Safran EUROFLIR 410. Phone-location tracks overlay the mission map and augmented-reality display for turret cueing. This supports one named sensor/aircraft integration, not an unbounded all-platform certification.
Supports: AIMS mission management and common operating picture software · maturity
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.
Supports: mission_system_integrator relationship
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.
Supports: mission_system_integrator relationship
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.
Supports: mission_system_integrator relationship
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.
Supports: mission_system_integrator relationship
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.
Supports: AIMS mission management and common operating picture software → 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: AIMS mission management and common operating picture software → 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.
SNC names CarteNav AIMS mission management in the RAPCON-X Challenger 650 configuration proposed for the Finnish Border Guard MVX program. This is an integrator configuration statement at an intermediate procurement stage, not an accepted Finnish operational delivery.
Supports: mission_system_integrator relationship
SNC names CarteNav AIMS mission management in the RAPCON-X Challenger 650 configuration proposed for the Finnish Border Guard MVX program. This is an integrator configuration statement at an intermediate procurement stage, not an accepted Finnish operational delivery.
Supports: mission_system_integrator relationship
SNC names CarteNav AIMS mission management in the RAPCON-X Challenger 650 configuration proposed for the Finnish Border Guard MVX program. This is an integrator configuration statement at an intermediate procurement stage, not an accepted Finnish operational delivery.
Supports: mission_system_integrator relationship
SNC names CarteNav AIMS mission management in the RAPCON-X Challenger 650 configuration proposed for the Finnish Border Guard MVX program. This is an integrator configuration statement at an intermediate procurement stage, not an accepted Finnish operational delivery.
The Finnish Border Guard reports April 11, 2025 approval of MVX critical design review and system specifications, enabling production and integration. Its May 12 update estimates first Finnish delivery in March 2027 and separates delivery, training and eventual full operational capability. Its sensor table names mission-management integration but not a CarteNav software release.
Supports: mission_system_integrator relationship
The Finnish Border Guard reports April 11, 2025 approval of MVX critical design review and system specifications, enabling production and integration. Its May 12 update estimates first Finnish delivery in March 2027 and separates delivery, training and eventual full operational capability. Its sensor table names mission-management integration but not a CarteNav software release.
Supports: mission_system_integrator relationship
The Finnish Border Guard reports April 11, 2025 approval of MVX critical design review and system specifications, enabling production and integration. Its May 12 update estimates first Finnish delivery in March 2027 and separates delivery, training and eventual full operational capability. Its sensor table names mission-management integration but not a CarteNav software release.
Supports: mission_system_integrator relationship
The Finnish Border Guard reports April 11, 2025 approval of MVX critical design review and system specifications, enabling production and integration. Its May 12 update estimates first Finnish delivery in March 2027 and separates delivery, training and eventual full operational capability. Its sensor table names mission-management integration but not a CarteNav software release.
Continue exploring
Follow the strongest connections
Continue through related organizations, reviewed mission and Defence need connections, programme pathways, and explicitly linked intelligence. Similarity results describe shared areas of work, not partnerships or endorsements.
Organizations
Profiles that provide the strongest reviewed or discovery-led continuation.