01.12.2016 Views

EVALUATION

evaluation_of_the_lcnf_0

evaluation_of_the_lcnf_0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

AN INDEPENDENT <strong>EVALUATION</strong> OF THE LCNF<br />

C.1.7<br />

Barriers That May Have Discouraged Project Partner Involvement (Q1.7)<br />

Questions:<br />

Are you aware of any barriers that may have discouraged project partner<br />

involvement?<br />

C.1.7.1 Summary of Responses<br />

Four respondents that answered the question felt there were no direct barriers. The<br />

barrier most respondents mentioned was the intellectual property rights with this being<br />

mentioned in six responses.<br />

One respondent had no clear view, and one did not respond.<br />

C.1.7.2 Intellectual Property<br />

As mentioned, intellectual property was mentioned as a barrier by several respondents<br />

with the issue being the partners having to give up too much ownership of IP. One of<br />

these respondents stated that although background IP is protected and foreground IP is to<br />

be shared; sometimes it is not possible to reveal the latter without revealing some of the<br />

former. They believe allowing partners to retain foreground IP would encourage more<br />

partners especially SME’s and start-ups that cannot afford to lose IP, and it will attract<br />

innovators which, in their opinion, surely is the point.<br />

Another of these respondents made a point that when a supplier talked on a project with a<br />

DNO to test their product on the network this will inevitably improve the product, but then<br />

the DNO will claim ownership of the IP of the improvement as they funded it. They, once<br />

again, say this is a big barrier for SMEs as they will not have the experience or resource<br />

to be able to negotiate a licence with the DNO. They suggested a way to avoid this is<br />

scoping projects so suppliers develop no foreground IP, claiming all of it back as<br />

background IP.<br />

The IP points made in the previous question responses are also relevant here.<br />

C.1.7.3 Other Barriers<br />

One response stated that initially the barrier was that companies were not prepared to<br />

take the risk on the new initiative, but this is no longer a problem as the LCNF has<br />

become established.<br />

One respondent was aware of organisations which could be potential partners if they were<br />

more familiar with the program; they feel more needs to be done to disseminate the<br />

knowledge outside of the more established channels.<br />

Another respondent is aware that some companies are hesitant to prepare bids with<br />

project partners in case the partners feel they will have an open cheque come delivery.<br />

These companies would prefer an informal arrangement, with the work tendered out once<br />

the project has been awarded, but the problem with this is the contribution of the project<br />

partners to the scope and development will be less.<br />

A barrier mentioned in the previous question responses was once again brought up by a<br />

different respondent – the lack of resources DNOs have for innovation projects, and<br />

having to prioritise day-to-day running of the business over that. They think this could<br />

possibly by remedied by an allowance for “key” disciplines such as those responsible for<br />

PÖYRY MANAGEMENT CONSULTING<br />

October 2016<br />

713_Poyry_Report_Evaluation_of_the_LCNF_FINAL_Oct_2016_v700.docx<br />

173

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!