Canada commits $572 million to Digital Infrastructure
Supporting and growing the vibrant research and innovation sector across Canada.

In the Budget 2018, announced last February, the Canadian government made a bold promise to invest $572.5 million in digital infrastructure that would support and grow the vibrant research and innovation sector across Canada. The Government also promised to work with stakeholders to develop a “Digital Research Infrastructure Strategy” that would explain how to use this money to “deliver open and equitable access” to researchers across the country.
As CEO of Compute Canada through late 2017, I was heavily involved in advising the government in advance of the Budget. Obviously I can’t share specifics, but the advice was very detailed and reflected significant and broad stakeholder input. However it is clear that Canada’s DI community couldn’t come up with an organizational design that would satisfy everyone. This is why the Budget talks about how “the strategy [would] include how to incorporate the roles currently played by the Canada Foundation for Innovation , Compute Canada and CANARIE .”
Defining the services that go into Digital Infrastructure, and the organizations needed to deliver them, is a difficult topic around the world. Bloodstone just completed a study (future posts will share more details of our results) of exactly this question across eight countries (plus one region of countries), and there were almost as many organizational patterns as there were countries in that study. Of course this study wasn’t exhaustive -- two dozen countries have made large enough investments in DI (focusing on academia and research) to appear in the Top500 list – but it was broad enough to offer some useful lessons. Here are a few of the top ones:
-
Focus on, and collaborate with, the best researchers. Of course, this is a platitude, and every DI organization will “say” this is their priority. However, it is also very easy for DI service providers to fall into the “shared services” IT trap, prioritizing efficiency over effectiveness, and prioritizing the 80% over the 20%. This approach will alienate the most demanding researchers, who will then go their own way, while the rest of the community feels held back, rather than enabled, by their DI resources. Instead, DI providers need to collaborate with those most demanding researchers to ensure that the DI ecosystem stays at the leading edge and allows the best researchers to amplify their reach and achievement. (By the way, the leading edge does NOT necessarily mean having the biggest systems!)
-
Tame the leading edge so that the 80% can use it too. Leading edge technology is diverging instead of converging, the “middleware” continues to evolve, and – most importantly -- the problems your researchers are trying to solve are, by definition, “novel”. Bottom line, the landscape keeps changing and HAS to keep changing, so DI providers have to build and maintain intermediate solutions and interfaces so that the less demanding 80% can be effective and productive without having to keep up with all this change. Many important components in the DI ecosystem, such as scientific gateways and platforms, research asset management capabilities and research software devops, are critical to enabling researcher productivity in the face of this rapid change. These activities must be sustainably resourced if most researchers are going to experience the benefit of other DI investments (e.g. in compute or storage).
-
Invest in ALL the components of the DI ecosystem in a balanced, sustained way. Sustainability is more than predictable capital infusions. It also means making sure the power bill gets paid. It means creating stable career paths for research software experts and then making sure they are working to maintain and improve both the analysis codes and the middleware and gateways. It means investing in cybersecurity training and procedures. It means rewarding documentation and testing – from metadata annotation and code documentation, to reproducibility initiatives. It means creating standards that enable interoperability.
Of course, you will say that even these few lessons conflict with one another – for example, if we’re serving our most demanding researchers, they won’t want a penny spent on interoperability! (I didn’t say it was easy!)
I look forward to the government’s promised DI strategy – and I hope it will reflect some of these lessons!



