Whitepapers, engineering demos, and case studies from work we've shipped to production — not marketing collateral. Where we can't share the full system, we tell you what's real and invite you to ask for the rest.
Practitioner-level technical publications, written by the engineers who did the work — not marketing. Each is a short form away, delivered straight to your inbox.
The full practitioner walkthrough of the DO-178C certification lifecycle — planning through to Final Certification Data — written by engineers who have delivered certification evidence on live airborne programmes.
Need the plans themselves, not just the guide?
We supply a paid DO-178C template & checklist pack —
PSAC, SDP, SCMP, SVP and SQAP skeletons with the DAL tailoring already done,
plus the review checklists we use on live programmes. Weeks of planning effort, ready to adapt to your project.
A 23-page practitioner’s guide to writing well-formed software requirements, grounded in the INCOSE Guide for Writing Requirements and aligned to ISO 26262, ASPICE and DO-178C — with twenty worked examples drawn from a Battery Management System context.
A cross-domain practitioner’s guide to naming software baselines and configuration items under DO-178C, DEF STAN 00-55, ASPICE SUP.8 and ISO 26262 — including a ready-to-adopt naming convention and a clause-by-clause compliance mapping.
Filter by format, or scroll to see everything we've published.
A recorded walkthrough of our High Voltage Interlock Loop (HVIL) design — deployed to production vehicles and aligned with ISO 26262 and IEC 61851. Full system/software requirements and Simulink models available on request.
Watch the VideoHow our BTMS software controls active cooling, passive cooling, heating, diagnostics, and preconditioning autonomously — managing the full thermal envelope in real time across cell temperature, ambient conditions, and driver demand.
Read the Case StudyOur flagship aircraft: a 2.43 m fixed-wing VTOL for intelligence, surveillance and reconnaissance, with four lift motors, a front cruise motor, a 30 km radius and GNSS-denied navigation.
See Where We AreA short walkthrough of how we approach requirements engineering — the practices behind the Writing Good Software Requirements guide above, shown in context.
Watch the VideoA narrated walkthrough of the naming convention behind the Software Requirements Baseline Naming & CM Identification whitepaper — how CI identifiers, safety levels, versions and baseline sequences fit together across DOORS and Git.
Watch the VideoA walkthrough of how we write, structure, and trace requirements on safety-critical programmes — the practical companion to our Writing Good Software Requirements guide.
A narrated walkthrough of how software baselines and configuration items are identified on safety-critical programmes — the practical companion to our Software Requirements Baseline Naming & CM Identification whitepaper.
Most of our work is under NDA. If you have a specific requirement, tell us — we'll point you to the closest published example or arrange a call.
Email the TeamWe typically respond within one business day.