We have an indicative budget of £60K for a single provider increasing up to £120K for consortia.

The National Security Technology and Innovation Exchange (NSTIx) is a government-led science, technology and innovation partnership that enables coherent and agile delivery of innovative national security outcomes through a co-ordinated and systematic approach to research and capability development.&nbsp;
NSTIx has established a government-led network of themed Co-Creation Spaces (CCS). The CCS&rsquo; combine the respective power of specialist public and private sector partners in research, capability development and end user requirements. This supports the development of effective, user-driven technology at pace in areas that are critical to national security. For more information, please see the &lsquo;NSTIx Leaflet&rsquo; in digital form (https://www.gov.uk/government/publications/nstix-information- leaflet).&nbsp;
Op Tech Co-Creation (OCCS) has engaged with a network of key Community Collaborators, to accelerate and leverage access to their existing networks of industry and academic Solution Providers.&nbsp;
By responding to this Challenge (details provided in &lsquo;Solution Provider Proposals &ndash; &lsquo;our ask&rsquo; section) and participating in Co-Creation there is an exciting opportunity for collaboration between National Security, Community Collaborators and Solution Providers.&nbsp;

Responding to NSTIx OpTech Co-Creation

Numerous secure government facilities across the UK require a form of approved identification permitting entrance. These security measures effect both foot traffic and vehicle access to secure car parks. Unauthorised cameras or other recording equipment are typically not permitted on-site, and with the proliferation of dashboard cameras (dashcams) in vehicles adds an additional element of security concern, as they may inadvertently record facilities, road layouts and personnel information. After the incident, the vehicle may leave the car park inadvertently carrying uncontrolled classified information.&nbsp;

This Challenge 

Policies exist to minimise the use of dashcams within secure government facilities, but it is unlikely that this will prevent all cases from inadvertent recordings by staff or visitors, and even more so would not prevent nefarious clandestine recordings. Further to this, some modern vehicles have integrated cameras built-in which can only be disabled through a software &ldquo;toggle&rdquo;, which the vehicle owner may not even be aware of. These are likely to become more prevalent in future, and possibly even &ldquo;standard fit&rdquo;. This is coupled with a high throughput of vehicles, potentially hundreds in some facilities, so it is unrealistic to expect security staff to check for the presence of these cameras in all their myriad forms, as this would likely incur a significant delay.&nbsp;
In this challenge, there is the requirement to develop a technical solution to rapidly disrupt or prevent recordings at pinch point entrances and exits of secure facilities. This must be done remotely (i.e., no physical access to the vehicle) while leaving no lasting impact that the dashcam recording has been interrupted, ensuring the owner has no adverse experiences from this effect.&nbsp;

What is the Gap

Working with the users in an agile approach, by the end of the project period there should be the aim to achieve at least a concept demonstrator achieving TRL 4 - technology basic validation in a laboratory environment. There is no prescribed route to achieve a concept demonstrator, approaches that could be considered are:&nbsp;
- Conduct a market trawl of prospective solutions that could either be used out of the box, or adapted to solve this challenge quickly and cost-effectively.&nbsp; - Basic research to prove the principle in a lab environment that a dashcam can be safely interrupted, while minimising the intrusion on the owner.&nbsp; - Using existing developments which can be pivoted to this use case to produce one or more demonstrable prototypes for prospective users to trial.&nbsp;
Proposals not within scope are those that require physical access to the inside of the vehicle, and solutions that have a lasting impact on the dashcam.&nbsp;
An online breifing event will be held on Wednesday 6th December at 10am <a title="Dashcam Briefing" href="https://teams.microsoft.com/l/meetup-join/19%3ameeting_ZTVhYTkyOGItNzE3Mi00MDdmLThlOGQtNjFmMzJmODliNTZi%40thread.v2/0?context=%7b%22Tid%22%3a%22648cc389-431a-4896-bd5d-429236beac31%22%2c%22Oid%22%3a%22fba63579-5a1e-4ae6-bf9a-96f6cc3e8b27%22%7d">Teams Briefing</a>
Failure to attend the Briefing Call or pre-competition events does not exclude solution providers from submitting a proposal by the deadline stated below.&nbsp;
Deadline: The deadline for proposals to be submitted is close of business on Thursday 11th January 2024.&nbsp; Submissions: Please complete your submission on this portal ensuring you also include additional information outlining your deliverables and associated costs over the 12-week period. Format: Final responses for this Challenge can be provided in any format but we recommend the use of attachments.&nbsp;
Frequently Asked Questions &ndash; responses (FAQ): All enquiries from the Briefing Call will be collated, and responses sent to all parties in an FAQ document by Tuesday 19th December 2023.&nbsp;
Project start date: The target start date of contracted solution providers is March/April 2024.&nbsp;

Solution Provider Proposals - 'our ask'

This challenge is open to sole innovators, industry, academic and research organisations of all types and sizes. There is no requirement for security clearances.&nbsp;
Solution providers or direct collaboration from countries listed by the UK government under trade sanctions and/or arms embargoes, are not eligible for OpTech Co-Creation challenges.&nbsp;
OpTech Co-Creation are working with a multiple and diverse set of community collaborators to broadcast and host our challenges. <a href="https://www.hmgcc.gov.uk/co-creation/">Please follow this link for the full list of community collaborators.&nbsp;</a>
If possible, please submit applications via a community collaborator.&nbsp;
If the community collaborator does not host an application route, please send applications directly to <a href="mailto:cocreation@hmgcc.gov.uk">cocreation@hmgcc.gov.uk</a>, including the challenge title with a note of the community collaborator where this challenge was first viewed.&nbsp;
All information you provide to us as part of your proposal, whether submitted directly or via a collaborator platform, will be handled in confidence.&nbsp;
&nbsp;
Applications must be no more than six pages or six slides in length. The page/slide limit excludes personnel CVs and organisational profiles.&nbsp;
There is no prescribed application format, however, please ensure your application includes the following:&nbsp; Applicant details - Contact name, organisation details and registration number.
Scope - &nbsp;Describe how the project aligns to the challenge scope.&nbsp;
Innovation - Describe the innovation and technology intended to be delivered in the project, along with new IP that will be generated or existing IP that can be used.&nbsp;
Deliverables - Describe the project outcomes and their impacts.&nbsp;
Timescale - Detail how a minimum viable product will be achieved within the project duration.&nbsp;
Budget - Provide project finances against deliverables within the project duration.&nbsp; Team - Key personnel CVs and expertise, organisational profile if applicable.&nbsp;

Eligibility and Routes to apply 

All proposals, regardless of the application route, will be assessed by the OpTech Co-Creation team. Proposals will be scored 1&ndash;5 on the following criteria:&nbsp; 
Scope: Does the proposal fit within the challenge scope, taking into consideration cost and benefit?&nbsp;
Timescale: Will the proposal deliver a full or partial solution, if a partial solution, are there collaborations identified?&nbsp;
Budget: Are the project finances within the competition scope?
Team: Are the organisation / delivery team credible in this technical area?&nbsp;
Innovation: Is the technical solution credible, will it create new knowledge and IP, or use existing IP?&nbsp;
Deliverables: Will the proposal deliver a full or partial solution, if a partial solution, are there collaborations identified?&nbsp;
&nbsp;
&nbsp;

Evaluation criteria 

Successful applicants will be invited to a pitch day, giving them a chance to meet the OpTech Co- Creation team and pitch the proposal during a 20 minute presentation, followed by questions.&nbsp;
After the pitch day, a final funding decision will be made. For unsuccessful applicants, feedback will be given in a timely manner.&nbsp;
&nbsp;
Selection and notification of finalists: The OCCS Challenge Team will select a shortlist of and invited to a pitch day to be held on Friday 26th January 2024.
Pitch day: The OCCS Challenge Team pitch day will be on Thursday 1st February 2024. An option to attend face to face or online will be made.&nbsp;
Feedback: All applicants will be provided with written feedback via the Community Collaborator once both technical and commercial assessments have been concluded. We will endeavour to provide feedback within 2 weeks of the competition deadline.&nbsp;

Invitation to Present

Co-Creation Terms and conditions&nbsp;
Proposals must be compliant with the OpTech Co-Creation terms and conditions; by submitting your proposal you are confirming your organisation&rsquo;s unqualified acceptance of Co-Creation terms and conditions.
Commercial contracts and funding of successful applications will be engaged via our commercial collaborator, Cranfield University.&nbsp;

Commercial conditions 

1. Who owns the intellectual property?&nbsp;
As per the OpTech Co-Creation terms and conditions, project IP shall belong exclusively to the solution provider, granting the Authority a non-exclusive, royalty free licence.&nbsp;
2. Who are the end customers?&nbsp;
National security users. This is a wide range of different UK government departments which will vary from challenge to challenge. This is a modest market and so we would encourage solution providers to consider dual use and commercial exploitation.&nbsp;
3. What funding is eligible?&nbsp;
This is not grant funding, so OpTech Co-Creation funds all time, materials, overheads and indirect costs.&nbsp;
4. How many projects are funded for each challenge?&nbsp;
On average we fund two solution providers per challenge, but it does come down to the merit and strength of the received proposals.&nbsp;
5. Do you expect to get a full product by the end of the funding?&nbsp;
It changes from challenge to challenge, but it&rsquo;s unlikely. We typically see this initial funding as a feasibility or prototyping activity.&nbsp;
6. Is there the possibility for follow-on funding beyond project timescale?&nbsp;
Yes, if the solution delivered by the end of the project is judged by the OpTech Co-Creation team as feasible, viable and desirable, then phase 2 funding will be made available.&nbsp;
7. Can we collaborate with other organisations to form a consortium?&nbsp;
Yes, in fact this is encouraged, and additional funding may be made available as per the outlined budget.&nbsp;
8. I can&rsquo;t attend the online briefing event; can I still access this?&nbsp;
Yes, it will be made available to stream and view at your leisure after it has been broadcasted. This will be made available via the OpTech Co-Creation community collaborators.&nbsp;
9. Do we need security clearances to work with HMGCCCo-Creation?&nbsp;
There is no requirement for security clearances, our preference is work to be conducted at OFFICIAL.&nbsp;
10. We think we have already solved this challenge; can we still apply?&nbsp;
That would be welcomed. If your product fits our needs, then we would like to hear.&nbsp;
11. Can you explain the Technology Readiness Level (TRL)?&nbsp;
Please see the UKRI definition for further detail. 12. Can I source components from the list of restricted countries, e.g. electronic&nbsp;components?&nbsp;
Yes, that is acceptable under phase 1 - feasibility, as long as it doesn&rsquo;t break UK government trade restrictions and/or arms embargoes.&nbsp;
Further considerations:
Advice and guidance on how to keep your organisation secure online can also be found through the National Cyber Security Centre.&nbsp; Solution providers should also consider the protective security measures they have in place. Please ensure ways of working are in-line with Trusted Research (for academia) and Secure Innovation (for businesses) guidance.&nbsp;

FAQs

Clarifying questions or general requests for assistance can be submitted directly to <a href="mailto:cocreation@hmgcc.gov.uk">cocreation@hmgcc.gov.uk </a>prior to the cut-off date. These clarifying questions may be technical, procedural, or commercial in subject, or anything else where assistance is required. Please note that answered questions will be published to facilitate a fair and open competition.&nbsp;

Clarifying questions

&nbsp; Question 1. If we're disrupting OEM webcams, this method could be used for nefarious means. What provisions are being made to make sure what we come up with will remain in the right hands rather than used for nefarious purposes, e.g. using a tool that can be used to disable cameras could be used on motorways to disable cameras etc. Answer: It will be used on MOD sites so it will be a protected capability and wouldn't be available on open market. We don't hold the IP so it is the owner&rsquo;s responsibility to ensure it isn&rsquo;t used for nefarious means. In terms of confidentiality, these are set out in the contract. 2. How many solutions would be funded? Answer: There is no limit. As many as deemed viable. 3. How generic does the solution need to be? For all cars and all dashcams? Answer: We would accept solutions that only work with after-market dashcams and may look at follow on work to expand this. 4. Is there scope to look at adding tape over the camera as a low tech option? Answer: This is fine but doesn't work for discretely hidden cameras and uses a lot of resource in terms of the guard&rsquo;s time to look for the camera and then hide this. 5. The solution for each Dashcam will need to be unique we assume, therefore does that mean that anything that exploits the dashcam will be out of scope, e.g. firmware? Answer: This could be in scope. You would assume there aren't that many OEMs working on this so we'd be interested in seeing these.&nbsp; 6. Will MOD get something in place to avoid breaching the Computer Misuse Act?&nbsp; Answer: For the chosen solution we will make sure the appropriate channels are followed to ensure alignment.&nbsp; 7. What entry points are we covering?&nbsp; Answer: Many points but one of the key areas would be the pinch points at main entrances with guards and barriers where cars have to stop and there is time to assess the individual. We're open to ideas 8. Is this project matched funded? Answer: No we don't fund grants. This is a research project.&nbsp; 9. Does the application need to include a specific timeline? Answer: Applications should include a specific 12 week coverage in their timeline. 10. Can we form a consortium? Answer: We are open to consortium forming, but the lead supplier carries the financial flow of commercials to their partners. 11. Is there any need to disrupt the GPS metadata? Answer: It would be a &lsquo;nice to have&rsquo; to have a GPS disruption built into it, but is not a key requirement. 12. Are we concerned with say, built-in front facing cameras, that have been modified to record? Answer: It would be good if the device could say that the device is recording and is on but mainly we want to focus on commercial dashcam devices. 13. Who owns the intellectual property? Answer: As per the HMGCC Co-Creation terms and conditions, project IP shall belong exclusively to the solution provider, granting the Authority a non-exclusive, royalty free licence. 14. Who are the end customers? Answer: National security users. This is a wide range of different UK government departments which will vary from challenge to challenge. This is a modest market and so we would encourage solution providers to consider dual use and commercial exploitation. 15. What funding is eligible? Answer: This is not grant funding, so HMGCC Co-Creation funds all time, materials, overheads and indirect costs. 16. How many projects are funded for each challenge? Answer: On average we fund two solution providers per challenge, but it does come down to the merit and strength of the received proposals. 17. Do you expect to get a full product by the end of the funding? Answer: It changes from challenge to challenge, but it&rsquo;s unlikely. We typically see this initial funding as a feasibility or prototyping activity. 18. Is there the possibility for follow-on funding beyond the project timescale? Answer: Yes, if the solution delivered by the end of the project is judged by the HMGCC Co-Creation team as feasible, viable and desirable, then phase 2 funding will be made available. 19. Can we collaborate with other organisations to form a consortium? Answer: Yes, in fact this is encouraged, and additional funding may be made available as per the outlined budget. 20. I can&rsquo;t attend the online briefing event; can I still access this? Answer: Yes, it will be made available to stream and view at your leisure after it has been broadcasted. This will be made available via the HMGCC Co-Creation community collaborators. 21. Do we need security clearances to work with HMGCC Co-Creation? Answer: There is no requirement for security clearances, our preference is work to be conducted at OFFICIAL. 22. We think we have already solved this challenge; can we still apply? Answer: That would be welcomed. If your product fits our needs, then we would like to hear. 23. Can you explain the Technology Readiness Level (TRL)? Answer: Please see the UKRI definition for further detail. 24. Can I source components from the list of restricted countries, e.g. electronic components? Answer: Yes, that is acceptable under phase 1 - feasibility, as long as it doesn&rsquo;t break UK government trade restrictions and/or arms embargoes. &nbsp; &nbsp; &nbsp;

Dashcam Interruption

Opportunity

Challenge opens

Challenge closes

Benefit

Responding to NSTIx OpTech Co-Creation

This challenge is brought to you by:

Dashcam InterruptionCopy Link

Opportunity

Challenge opens

Challenge closes

Benefit

Responding to NSTIx OpTech Co-Creation

This challenge is brought to you by:

Dashcam Interruption