ARMY QUANTUM TECHNOLOGY CHALLENGE 2021 & ARMY QUANTUM TECHNOLOGY EXPLORATION DAY 2021 (AQTED21)

The Department of Defence via the Australian Army and the Land Capability Division (Defence) is seeking submissions that will demonstrate solutions to The Challenge (details in the Challenge Statement) at the first Army Quantum Technology Exploration Day (AQTED21), to be held on 20 April 2021 at the Brisbane Exhibition Centre.

Army is seeking to leverage Australia’s national strategic strength in quantum technology research, its emerging quantum industry and cooperation with aligned nations, to gain and retain an early quantum advantage.

The AQTEDs are designed to enable Army to:

• issue challenges that test specific hypotheses of quantum technology applications in land operations

• provide forums for the generation of new ideas and critical discussion of quantum technology applications in land operations

• establish networks and mutual understanding with Australia’s quantum technology research and industry community

• assess the abilities of participating teams and their suitability for future Army quantum technology projects.

This Call for Submissions (CFS) comprises the Challenge Statement, the CFS Terms, and a sample Deed of Participation. Submissions are open to Australian Permanent Residents or Citizens only, and must hold an ABN. Proposals must directly address one of three sub-themes as outlined in the Challenge Statement. These examples have been chosen because they are both sufficiently specific and tangible for respondents to make appropriate assumptions and produce meaningful results, whilst also being applicable to other situations and tasks in land operations.

Potential Applicants are only encouraged to respond to the CFS if their solution can reasonably be expected to be ready for demonstration at AQTED21. An alternative for such Potential Applications is to consider an innovation submission through the Defence Innovation Hub (DIH) portal as an unsolicited innovation proposal - Priority Innovation Notice instead.