Engineering whitepapers
Engineering knowledge for connected products
Practical whitepapers for leaders building hardware, embedded software, IoT and AI-native products.
Written from real engineering work and focused on architecture, technical decisions, risks and trade-offs.
- Architecture
- Technical decisions
- Risks and trade-offs
The library
Choose the engineering problem in front of you
Each whitepaper takes one class of connected product and asks where programs get stuck, which engineering decisions matter most and how to size the response.
Drone engineering
Gap or System? What's Really Stalling Your Drone Program
How to tell a narrow gap from a systemic problem in a stalled drone program, and the five boundary decisions that decide whether it reaches production.
What you'll learn
- A test for telling one specific gap from a systemic problem before you restart, re-staff or re-architect
- The five boundaries (interface, evidence, replaceability, reuse, knowledge) and the question each one asks
- How one decision about a payload, a compute module or a radio moves through power, heat, mass and range
How these are written
Evidence first, then the argument
- 01Written from project work
Each paper starts from real Indeema engineering projects and the engineers who did the work, not from a content calendar.
- 02Statements stay inside the evidence
Every project outcome is stated within what its project record shows. Where a paper cannot show a rate, a duration or a saving, it says so.
- 03Checked by the engineers involved
The engineers behind each project check their sections, and an edition is released only after that review.
Keep going
From reading to building
Talk through the decision in front of you
Bring an architecture question, a stalled program or a product that has to ship. Start with the decision your team needs to make next.
Talk to an IoT Architect