I have recently attended an excellent 2-day workshop on proposal writing for the european commission’s new research funding programme, Horizon 2020, given by Dr. Sean McCarthy from Hyperion. I won’t write about the nitty-gritty details of proposal writing here, but one thing I got to know more as a sidenote in this seminar are Technology Readiness Levels (TRLs).
Essentially, any technological development can be associated with a TRL between 1 (“we have observed that this happens, but we do not even know why and how it happens”) and 9 (“this is used in working real-life applications on the market”). The concrete details of the stages in between vary a bit depending on who you ask, but the figure below represents the 9 TRL levels as seen by the european commission:
(figure is copy and paste from here)
Now this notion of TRLs allows us to formulate an interesting observation why the practical impact of academic research is, frankly, often quite crappy.
University research in computer science largely falls into TRL 2, 3 and 4. In relatively rare cases it might mature up to 5, but that’s about it. Why do we not see our research through all the way until TRL 9? Well, there’s no publications to do. You can hardly publish that you tweaked your tool (which you have already proven conceptually sound) to also work in a relevant demo environment. It’s a lot of hard work, with very little immediate benefit for the academic. Hence, people do not do it.
Companies, on the other hand, usually do not want to touch anything below TRL 7 or 8. They may have research departments that operate on TRL 6, but those are few and far between. Why? Simply because the risk-reward ratio is not right for them. Many of the academic ideas in lower TRLs might be sound in principle, but practical problems will still hinder their practical usefulness. Companies typically do not appreciate that kind of risk.
It’s obvious that there is a gap that prevents even good academic ideas from being picked up by practitioners. This gap is often referred to as the Valley of Death. It’s the place where ideas go to die.
(this figure is another copy and paste, this time from here)
This figure nicely illustrates why academics and people from industry often have such a hard time collaborating. Essentially, all parties silently assume that the other person will interface with them on the level where they typically start/stop. The academic assumes that the company will be willing to pick up their stuff at TRL 4 (they won’t). The company assumes they will receive technology on TRL 7 level (this won’t happen either). Everybody is unhappy and feels like the other person is not doing their job. However, practically speaking, everybody kinda is.
The problem is that there is a job missing in the middle. Essentially, what is required is a person (let’s call her the Technology Transfer Agent) in the middle, who has the right incentives to take up TRL 3 or 4 technology and bring it all the way up to TRL 8. Clearly, this will not work every time. Sometimes, the agent will recognise on TRL 6 that 7 will already not be feasible, and the technology will remain an academic idea until somebody improves upon it. However, in many cases, it will work, and the world will (in theory) be a little bit of a better place.
The european commission is also explicitly addressing this Valley of Death in their Horizon 2020 programme. For instance, they have established PPP (Private-Public Partnership) and the EIT (European Institute of Innovation and technology) to explicitly bring technology (some part) through the Valley and make them relevant to society faster.