CMS 330 is Lockheed Martin Canada's configurable naval command-and-combat-management architecture for integrating sensors, tactical information and operator workflows. Its common core supports different customer fits. River-class descriptions require particular care: Aegis and the Canadian Tactical Interface configuration should be distinguished from a generic claim that the destroyers use an unchanged CMS 330 installation.
Technical detail
Core features
Scalable common-core command architecture
Sensor, tactical-data and operator-interface integration
Programme-specific configurations and through-life updates
Combat Management
C4isr
Naval Systems
Use & integration
Recorded applications
Surface combatant command and control
Multi-domain maritime operations
Combat-system modernization
These describe the reviewed application scope, not confirmed deployments, released requirements or procurement eligibility.
Evidence of maturity
Fielded and exported architecture across named naval programmes; River-class integration is part of a future ship programme.
Commercial availability
Procured as a customer-specific combat or command-system integration package with associated support.
Integration and verification
Readiness
A technology readiness level is not established by the reviewed public sources.
A combat-management layer can integrate and present shipboard underwater-sensor and track data, but platform-specific anti-submarine performance requires reviewer confirmation.
This is a reviewed public-source assessment. It is not procurement eligibility, endorsement, customer interest, or classified demand.
Original sources 3 linked records
These records support this capability and its published Mission area and Defence need connections. A source count is not a count of independent confirmations.
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · commercial availability
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · name
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · core features
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · technical tags
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · capability type
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · defence applications
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · technical tags
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · core features
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · technicaldomainslugs
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · technology readiness level
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · technicaldomainslugs
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · defence applications
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · maturity
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · defence applications
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · summary
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · technical tags
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Capability · technicaldomainslugs
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Mission area · Underwater ISR
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Mission area · Underwater ISR
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Mission area · Underwater ISR
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
Supports: Mission area · Underwater ISR
CMS 330 is described as an open-architecture, scalable integration layer connecting ship sensors, information systems and effectors with training and through-life software services. The page explicitly distinguishes Canadian Tactical Interface integrated with Aegis on the new surface combatants, despite broader CMS 330 family wording elsewhere on that page.
DND identifies Lockheed Martin Canada as Irving's River-class design-team subcontractor using the BAE Type 26 design. It identifies the Aegis combat system as government-supplied equipment through US Foreign Military Sales, distinguishing the overall programme from a generic CMS 330 installation.
Supports: Capability · maturity
DND identifies Lockheed Martin Canada as Irving's River-class design-team subcontractor using the BAE Type 26 design. It identifies the Aegis combat system as government-supplied equipment through US Foreign Military Sales, distinguishing the overall programme from a generic CMS 330 installation.
The cited official portfolio material supports the CMS 330 naval combat management capability family and its described delivery scope; product and platform availability remains configuration-dependent.
Supports: Mission area · Underwater ISR
Analyst mapping only: A combat-management layer can integrate and present shipboard underwater-sensor and track data, but platform-specific anti-submarine performance requires reviewer confirmation.
Public sources cited · Facts and assessments kept separate · Human review
DND identifies Lockheed Martin Canada as Irving's River-class design-team subcontractor using the BAE Type 26 design. It identifies the Aegis combat system as government-supplied equipment through US Foreign Military Sales, distinguishing the overall programme from a generic CMS 330 installation.
