Lockheed Martin Canada

Supports: Profile · operating context

Lockheed Martin Canada leads combat-system design and integration within the Irving Shipbuilding-led River-class Destroyer delivery team, with CMS 330 and SPY-7 among the disclosed system elements.

Supports: prime shipyard integration partner relationship

Source location: relationships.0.publicSummary

Lockheed Martin Canada leads combat-system design and integration within the Irving Shipbuilding-led River-class Destroyer delivery team, with CMS 330 and SPY-7 among the disclosed system elements.

Supports: Profile · operating context

The cited official portfolio material supports the Naval electronic warfare systems capability family and its described delivery scope; product and platform availability remains configuration-dependent.

Supports: Naval electronic warfare systems · core features

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · technology readiness level

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · summary

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · core features

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · technical tags

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · summary

The cited official portfolio material supports the Naval electronic warfare systems capability family and its described delivery scope; product and platform availability remains configuration-dependent.

Supports: Naval electronic warfare systems · core features

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · defence applications

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · defence applications

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · technical tags

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · technicaldomainslugs

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · capability type

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · technicaldomainslugs

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · technical tags

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · technicaldomainslugs

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · defence applications

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · commercial availability

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · name

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems · maturity

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems → Arctic Domain Awareness

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems → Arctic Domain Awareness

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems → Arctic Domain Awareness

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Naval electronic warfare systems → Arctic Domain Awareness

Analyst mapping only: Electronic-support sensors may contribute to maritime awareness in northern operations, although no Arctic deployment is asserted by the cited portfolio pages.

Supports: Naval electronic warfare systems → Arctic Domain Awareness

Lockheed Martin Canada describes RAVEN as shipboard electronic countermeasures, Coronis as an electronic-warfare operational-support and mission-data product, and separate simulation/stimulation services. Product descriptions do not establish a new award or every advertised performance outcome.

Supports: Profile · profileData.publicContact.contactPageUrl

The official public contact pathway for Lockheed Martin Canada is https://www.lockheedmartin.com/en-ca/index.html.

Supports: Profile · canadian footprint

Lockheed Martin Canada identifies Ottawa headquarters, wholly-owned subsidiary status, more than 1,300 Canadian employees and seven major sites. Its Canadian work covers software engineering, systems integration, manufacturing, training and sustainment, with the official site providing company and IMPACT Centre routes.

Supports: Profile · editorial profile version

Lockheed Martin Canada has sufficient mapped public evidence for private reviewer consideration of the shared editorial profile template.

Supports: Profile · canadian footprint

Official organization material supports this profile: Canadian defence and technology prime with a seven-site national footprint spanning naval combat management, electronic warfare, all-domain systems integration, autonomous-system control software, advanced manufacturing, training, sustainment, and program delivery.

Supports: Profile · description

Official organization material supports this profile: Canadian defence and technology prime with a seven-site national footprint spanning naval combat management, electronic warfare, all-domain systems integration, autonomous-system control software, advanced manufacturing, training, sustainment, and program delivery.

Supports: Profile · operating context

Lockheed Martin Canada identifies Ottawa headquarters, wholly-owned subsidiary status, more than 1,300 Canadian employees and seven major sites. Its Canadian work covers software engineering, systems integration, manufacturing, training and sustainment, with the official site providing company and IMPACT Centre routes.

Supports: Profile · operating context

Official organization material supports this profile: Canadian defence and technology prime with a seven-site national footprint spanning naval combat management, electronic warfare, all-domain systems integration, autonomous-system control software, advanced manufacturing, training, sustainment, and program delivery.

Supports: All-domain systems integration and sustainment · technicaldomainslugs

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · technical tags

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · technicaldomainslugs

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · core features

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · technicaldomainslugs

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · defence applications

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · technical tags

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · technical tags

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · defence applications

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · technicaldomainslugs

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · summary

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · defence applications

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · name

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · technology readiness level

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · core features

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · commercial availability

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · maturity

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · capability type

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · core features

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment → Autonomous Patrol and Monitoring

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment → Autonomous Patrol and Monitoring

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment → Autonomous Patrol and Monitoring

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment → Autonomous Patrol and Monitoring

Lockheed Martin Canada identifies Halifax and New Zealand frigate integration, Victoria-class command-system support, AOPS, training and VISTA maintenance/operator instruction. These are programme-specific roles; global group product listings do not prove each technology is produced in Canada.

Supports: All-domain systems integration and sustainment · commercial availability

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: All-domain systems integration and sustainment · summary

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: All-domain systems integration and sustainment · 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.

Supports: CMS 330 naval combat management · commercial availability

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: CMS 330 naval combat management · 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.

Supports: CMS 330 naval combat management · summary

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: All-domain systems integration and sustainment · summary

The cited official portfolio material supports the All-domain systems integration and sustainment capability family and its described delivery scope; product and platform availability remains configuration-dependent.

Supports: All-domain systems integration and sustainment → Autonomous Patrol and Monitoring

Analyst mapping only: Canadian unmanned-system control software may support autonomous monitoring platforms, subject to verification of the specific operational configuration.

Supports: All-domain systems integration and sustainment → Sovereign defence capability areas

The cited official portfolio material supports the All-domain systems integration and sustainment capability family and its described delivery scope; product and platform availability remains configuration-dependent.

Supports: River-class Destroyer combat systems · organization participation

Source location: programs.river-class-destroyer-combat-systems.summary

The cited official program source publicly documents River-class Destroyer combat systems, its delivery scope, and Lockheed Martin Canada's disclosed role.

Supports: River-class Destroyer combat systems · canonical program

Source location: programs.river-class-destroyer-combat-systems.summary

The cited official program source publicly documents River-class Destroyer combat systems, its delivery scope, and Lockheed Martin Canada's disclosed role.

Supports: All-domain systems integration and sustainment → Sovereign defence capability areas

Canada needs secure strategic autonomy and reliable access to capabilities that are critical to defending its sovereignty and meeting allied commitments, while reducing exposure to foreign supply-chain and intellectual-property dependencies.

Supports: All-domain systems integration and sustainment → Sovereign defence capability areas

Reviewer synthesis of the public end state: Canada can build, sustain or control priority aerospace, ammunition, digital, in-service support, sensor, space, specialized manufacturing, training and uncrewed capabilities through domestic strength, trusted partnerships and sovereign access.

Supports: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management · 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: CMS 330 naval combat management → 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: CMS 330 naval combat management → 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: CMS 330 naval combat management → 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: CMS 330 naval combat management → 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: Coast Guard Information and Science Management Systems · core features

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · technology readiness level

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · commercial availability

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · core features

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · maturity

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · capability type

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · technical tags

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · add child

Lockheed Martin Canada states that its team integrates electronic science and situational-awareness systems and is designing Coast Guard Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8.

Supports: Coast Guard Information and Science Management Systems · defence applications

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · name

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · defence applications

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · defence applications

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · technicaldomainslugs

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · technical tags

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · summary

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · technical tags

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · technical tags

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · defence applications

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Coast Guard Information and Science Management Systems · core features

Lockheed Martin Canada's November 6, 2025 account describes Information and Science Management systems derived from CMS 330 for AOPS Coast Guard variants 7 and 8, with data display, capture and assessment. It reports systems ready for first-ship installation, not completed vessel delivery or operational acceptance.

Supports: Halifax-class Combat System Integration In-Service Support · organization participation

Public Services and Procurement Canada confirms a contract valued up to C$1.85 billion to Lockheed Martin Canada for renewed Halifax-class combat-system integration in-service support.

Supports: Halifax-class Combat System Integration In-Service Support · canonical program

Public Services and Procurement Canada confirms a contract valued up to C$1.85 billion to Lockheed Martin Canada for renewed Halifax-class combat-system integration in-service support.

Supports: Halifax-class Combat System Integration In-Service Support · organization participation

The official program feature states that CSI ISS runs through 2045 and covers CMS 330 releases, software, systems engineering, weapons and sensor integration, training, and embedded support by more than 160 Canadian personnel.

Supports: Halifax-class Combat System Integration In-Service Support · canonical program

The official program feature states that CSI ISS runs through 2045 and covers CMS 330 releases, software, systems engineering, weapons and sensor integration, training, and embedded support by more than 160 Canadian personnel.