Device Engineering
Connected devices and the software that runs on them, from sensor to stored record.
Scope of the practice.
Device and hardware selection
Choosing a platform against the real constraints of power, cost, environment and production volume, and saying plainly where the limits are.
Firmware
Device software written to be flashed, updated and diagnosed in the field rather than only on a bench.
Sensors and interfaces
Bringing in the physical signals a device exists to measure, and handling the cases where they are absent, noisy or disagree.
Connectivity and telemetry
Getting readings off the device reliably over an unreliable link, with buffering for the periods when it is not connected.
Fleet operations
Provisioning, over-the-air updates and monitoring across more than one unit, which is where most device projects actually become difficult.
What an engagement usually includes.
- Platform selection and feasibility review
- Firmware development and field update path
- Sensor integration and calibration
- Connectivity, buffering and telemetry
- Fleet provisioning and monitoring
What this is not.
Device work is quoted in stages, because the right platform is often only settled once the constraints have been tested.
Every engagement starts with a written scope that states what is included, what is not, and the criteria the work will be accepted against.
Start with a conversation.
A consultation is a scoped conversation about what you need, not a sales call. You will leave it knowing whether this is the right practice for the work.