I&I (Interoperability and Integration)

I&I stands for interoperability and integration. In NATO usage, interoperability is the ability of different systems, organizations and nations to work together coherently, effectively and efficiently. Integration refers to combining capabilities, systems or functions so that they operate together as part of a coherent capability.

The pairing is most common in defence, where national platforms, networks, sensors, data and forces must function alongside those of allies. NATO's Allied Command Transformation sets out the interoperability definition, and the Alliance Digital Strategy frames digital transformation around the rapid integration of secure, resilient and interoperable capabilities.

How NATO frames interoperability and integration

NATO's digital strategy calls for secure, resilient and interoperable digital capabilities to be rapidly integrated for multi-domain operations. The two ideas work as a pair: systems must be able to connect, and they must then be combined into a working whole.

Allied Command Transformation describes an interoperability continuum. Its purpose is to ensure that innovations integrate across NATO systems and multinational forces. The details are in the ACT innovation article. For suppliers, this means a new product is judged both on its own performance and on how well it fits into a wider allied architecture.

Where I&I shows up in Canadian defence programs

The Department of National Defence (DND) treats interoperability as a property of interconnected platforms, sensors and networks. Its force development evaluation identifies technical interoperability challenges that come from rapidly changing technology and from the need to integrate systems across architectures, systems and spectrum.

• C4ISR and network work: DND's C4ISR and Integration Program provides network-engineering support for allied interoperability, including among Canada, the United States and the Five Eyes network. See the 2023-24 Departmental Results Report.
• Major capital projects: DND names the Canadian Multi-Mission Aircraft, the Future Fighter Capability Project and the Strategic Tanker Transport Capability as projects with interoperability considerations. It also states that maximizing commonality supports affordability and coalition interoperability. See the procurement briefing.
• Munitions: Canada's participation in the Air Battle Decisive Munitions Framework is intended to maintain interoperability with NATO allies while reducing delivery timelines, according to the Minister's mandate priorities.
• Command and control software: A DND and CAF innovation challenge seeks software that converts, analyses and fuses real-time radio-frequency data into a secure, standardized pan-domain command-and-control format. The aim is better interoperability across domains and command levels. See the challenge description.

The link to United States procurement

CanadaBuys notes that Canadian procurements of military goods and services are often related to, and technically integrated with, U.S. military procurements for the same or similar goods and services. Its page on United States defense-related procurement covers this relationship. Canada also cooperates with Australia, the United Kingdom and the United States on capabilities, interoperability standards and joint experimentation.

What I&I means for a supplier bidding on Canadian public contracts

An interoperability or integration requirement asks a bidder to show that its product, system or service fits the buyer's environment. Depending on the solicitation, that can mean showing that the offering:

• works with specified Canadian, NATO, allied or U.S. systems;
• conforms to required standards, interfaces, data formats, networks or communications protocols;
• integrates with existing command-and-control, sensor, platform or information systems;
• supports coalition or multinational operations;
• can be tested, connected and operated in the buyer's technical environment.

The evidence required differs with each solicitation. It may include interface-control documentation, compliance matrices, test results, demonstrations, certifications, security approvals or integration support. Read the technical requirements and evaluation criteria closely, and build the proof into the bid from the start.