Technical research and feasibility studies before you commit to build.
Before spending on hardware, it helps to know whether an idea can work and which technologies suit it, and a company with no R&D team has nobody to find out. We do that through feasibility studies, technical reports and technology scouting, and our badminton line-calling simulation shows the method at work.
The problem
Some questions are cheaper to answer in simulation than in hardware. Our badminton line-calling simulation, described on our computer vision page, is a worked example: it shows which camera and tracking choices matter before any camera is bought. It is a v0 demo with no real cameras behind it, but it shows how a study can point effort at the choice that matters. A feasibility study would typically begin with the question you need answered and the decision it feeds, then move to a model or a small experiment that can answer it.
We would write the result up as a technical report, name what was modelled and what was assumed, and say what a physical test would need to show before a decision rests on the result. Technology scouting is similar in kind. It compares candidate technologies against your case, such as the radio options for a particular site, and records why one was chosen over the others. For a company with no specialist in the field, a study is mostly about narrowing the options so that the next step is smaller. Both our simulations are simulation work with no deployment behind them, and we would label any study the same way.
A technical report is useful when a reader who was not in the room can follow it. We would state the question, the options considered, the criteria used to compare them and the recommendation, and keep the working visible so that it can be checked or repeated. Where evidence is thin we would say so and suggest the smallest experiment that would settle the matter. Technology scouting covers components and platforms as well as connectivity, such as comparing candidate modules, sensors or radios against your constraints on size, supply and availability.
What we'd build
What we would research for you
We would scope a study around a question you need answered before you build. Our simulation work is the closest example, and it is simulation, not a deployment.
| Layer | What we'd do | Detail |
|---|---|---|
| Feasibility studies | A study of whether an idea can work, and what it would take. | Our line-calling twin tests camera choices before any camera is bought |
| Technical reports | Findings and recommendations written down, so a decision can be made and kept. | |
| Technology scouting | Candidate technologies compared for your case, such as connectivity. | Our simulation of a city-scale camera mesh covers pixel to ray to voxel, with LoRa, LTE-M, NB-IoT and Wi-Fi mesh uplink options, and found that tracklets make LoRa viable |
| Method | A simulation or model built to answer the question before hardware is bought. | Python |
How working with us goes
- 01 Scope We agree what has to be built, where it lives and where the data goes.
- 02 Prototype Working hardware and firmware on your bench, tested against real conditions.
- 03 Pilot A small batch on real sites, with fixes folded back into the design.
- 04 Production Design for manufacture, a production run, and support once it is in the field.
Related
Product development ·Computer vision and sports tech ·Drones and aerial robotics ·LoRaWAN sensor design · All sectors →