Dashcam Interruption Challenge
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.
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 “toggle”, which the vehicle owner may not even be aware of. These are likely to become more prevalent in future, and possibly even “standard fit”. 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.
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.
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:
• 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.
• Basic research to prove the principle in a lab environment that a dashcam can be safely interrupted, while minimising the intrusion on the owner.
• Using existing developments which can be pivoted to this use case to produce one or more demonstrable prototypes for prospective users to trial.
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.
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.
After the pitch day, a final funding decision will be made. For unsuccessful applicants, feedback will be given in a timely manner.
Key dates and timelines
Clarifying questions published.
Competition closes at 5pm.
Pitch day in Milton Keynes.
Target project kick-off.
Check this page for regular updates.
How to apply:
OpTech Co-Creation are working with a multiple and diverse set of community collaborators to broadcast and host our challenges. Please follow this link for the full list of community collaborators.
If possible, please submit applications via a community collaborator.
If the community collaborator does not host an application route, please send applications directly to email@example.com, including the challenge title with a note of the community collaborator where this challenge was first viewed.
All information you provide to us as part of your proposal, whether submitted directly or via a collaborator platform, will be handled in confidence.
To apply for the challenge, use this link and create a KTN account.