Detectors to spot hidden phones, smart watches or other electronic devices are sought in the latest challenge launched by HMGCC Co-Creation.
To prevent sensitive data being leaked, high classification government areas do not allow personal electronic devices (PEDs) such as phones.
In this challenge, we want to hear from organisations which have or could develop a PED detector to alert people to the presence of a banned device.
Organisations are being asked to apply if, over a 12-week period, they can develop and demonstrate alternative positioning, navigation and timing (PNT) technology to meet this challenge. HMGCC Co-Creation will provide funding for time, materials, overheads and other indirect expenses.
The challenge
Context of the challenge
UK government, international allies and strategic partners, have facilities with high classification areas, with an increased level of security in place. In these locations, it is vital to ensure no secret recording with prohibited devices like phones or smartwatches is allowed to happen.
The gap
Good security culture and vigilance goes a long way to solve this problem, but a technical solution is required to detect and alarm, with the presence of a PED. The solution will operate in a high classification area, so must not inadvertently record sensitive information itself. The solution should also be adaptable so when new RF bands are used in commercially available PEDs, it can still detect their presence.
Example use case
Jax works in a government building, typically in a low classification space where she is allowed PEDs. But sometimes she has to access a higher classification area where they are not allowed. On one occasion, when Jax is in a hurry, she rushes to a meeting in the higher classification space but forgets she is wearing her smartwatch. This is a genuine mistake, but it could have the unintended consequence of recording sensitive information.
However, the PED detector identifies the presence of an RF signature before the meeting even starts. Responding to this alert, all attendees check, and Jax realises she is wearing her smartwatch. Although embarrassing, this early detection is easier to deal with than the watch being found after the meeting.
Project scope
In this 12-week project, applicants should aim to deliver a demonstration to the sponsors alongside a report. This is open to Technology Readiness Levels (TRL) from 4 – 9. It is recommended that proposals label both the existing TRL and the TRL expected by the end of 12 weeks. Essential, desirable and stretch targets are listed below.
Essential requirements:
- Must be relatively small and unobtrusive.
- Alarm when a PED has been detected with a high degree of confidence.
- Should detect all type of PEDs.
- Consider capturing RF energy only to ensure the solution is not reliant on frequency or protocol detection that can change over time.
- Strictly passive monitoring.
- High degree of confidence when alarm happens. Consider Ability to baseline RF traffic or self-learn about the environment. A detector that alarms even when no prohibited PEDs are in the area could result in users ignoring it.
- Intended to be used globally. Allow privileged users the ability to program the unit.
- Device alarm should consist of both audible and visual keys.
Desirable:
- Battery backup.
- 500MHz – 8GHz frequency monitoring range.
- Easy to operate for a user.
- For wide adoption it must be relatively low cost. Consider what final costings per fully productionised unit may be.
- Include notifications for the occupants of the room
- Display the frequency or signal strength and band that triggered the alarm along with the network provider being used (if a cellular connection)
The environment and constraints:
- PED detector will be static in a meeting room, so can use mains.
- The PED detector will operate in an area without regular access to the internet.
- Wi-fi and other baseline RF signals may be present in some spaces, but necessarily available for the PED detector.
Not required:
- Horizon scanning only.
- Wireless intrusion detection system.
- RF protocol detector.
Key dates
Monday 12 May 2025
Competition opens
Tuesday 27 May 2025 at 10:00am
Deadline for clarifying questions
Tuesday 3 June 2025
Clarifying questions published
Thursday 12 June 2025 at 5:00pm
Competition closes
Tuesday 24 June 2025
Applicant notified
Tuesday 1 July 2025
Pitch day in Milton Keynes
Monday 7 July 2025
Pitch Day outcome
Friday 11 July 2025
Commercial onboarding begins*
*Please note, the successful solution provider will be expected to have availability for a 1-hour onboarding call via MS Teams on the date and time specified to begin the onboarding/contractual process.
Tuesday 5 August 2025
Target project kick-off
Eligibility
This challenge is open to sole innovators, industry, academic and research organisations of all types
and sizes. There is no requirement for security clearances.
Solution providers or direct collaboration from countries listed by the UK government under trade
sanctions and/or arms embargoes, are not eligible for HMGCC Co-Creation challenges.