Recommended sensors
—
Sensorry.
Design the network, not just the sensor.
Drop nodes onto the canvas — actuators, observable states, faults — and draw the arcs between them. The tool runs a simplified NDCI heuristic and rings the state nodes a sensor would actually earn its place on. Edit, share the URL, or reset.
Fault coverage
—
Status
Default flow loaded. Edit, or hit reset to start over.
● Simplified heuristic for the live demo: each state's score = (faults reachable) + 0.5 × (actuators upstream); greedy pick until every fault is covered. The published NDCI uses a richer information-theoretic formulation — the toy gives the right intuition, not the optimal answer. Keyboard users: every button in the toolbar is reachable via Tab; node positioning on the canvas is reserved for pointer or touch input.
Status
◐ Prototype — method packaging, early UI
Target user
Systems engineers and IVHM programme leads designing sensor networks for complex assets
Problem solved
Sensor-network design and diagnostic-coverage tooling — direct commercialisation of MOSOF and NDCI
What is real now
Working prototype; method packaging underway; early UI under development — not yet publicly available
§ 01 / What it solves
Three positions on the same problem.
A six-fault subsystem under three different design moves. Coverage and count change; the NDCI-optimal column is the one Sensorry argues for.
i.
"Where do I put sensors?"
No sensors yet. Six faults exist; the asset is operating blind.
ii.
"Naive: one per fault."
Six sensors, one per fault. Coverage is high but you've paid for sensors whose information overlaps.
iii.
"NDCI-optimal."
Three sensors picked for the unique diagnostic information they carry. Same coverage to within a point, half the hardware.
§ 02 / Status & partners
Prototype, not GA.
Sensorry is a working prototype. The methods it implements (MOSOF, NDCI) are peer-reviewed and validated across four aircraft subsystems through Cranfield's SESAC platform. The product around them — UI, data ingest, customer onboarding — is the work in progress, and that work is best done in the open with engineers who have a real network to scope.
If you'd be a useful early partner — you have a sensor-network decision in front of you and you'd value an external lens on it — book a slot directly. The first cohort is capped at five; we treat each design partner as a co-author on the resulting case study.
Design-partner cohort 01
30-minute scoping call to see whether your problem is in scope, followed by a one-week paid pilot if both sides want it. Direct line to Burak; no sales motion.
3 / 5 slots filled · 2 remaining
§ / Talk
Designing a network right now?
If you're scoping a sensor network on a complex asset and you'd value an external view — or you'd consider being an early Sensorry partner — get in touch. The product isn't general-availability yet, but the methods are ready to apply to your problem now.
[email protected] →Design partnerBook a slot
Lead ventureAcoustR
Case study/proof — paper to product
Other venturesVentures overview