Whichever path you take, the same discipline stands behind it.
The CRA’s essential requirements, implemented rather than approximated, in your codebase rather than a slide deck.
Every deliverable maps to what a notified body or test lab expects to see: the technical file, the traceability, the test reports.
The discipline of the industry with the least tolerance for firmware that fails, brought to your connected product.
Aceman was founded by an embedded engineer who spent years in automotive software, where a firmware fault can mean a recall.
The discipline that keeps a vehicle safe is what connected products now need, and it is what we bring to teams that don’t have it in-house.
Eleven years of embedded engineering, most of it in automotive safety-critical software: bootloaders, secure boot, diagnostics and the evidence that satisfies the world’s strictest assessors. M.Eng, University of Leeds.
LinkedIn →No. Notified bodies verify and certify, and they’re barred from also building the solution. We do the engineering that makes a product pass, so you’re ready when the assessor arrives.
Seven questions, two minutes, and a straight answer on what your product still needs.