Requirements checklist
What to ask for when choosing software for ioT device manufacturers.
A checklist built from how ioT device manufacturers work, to print or save as a PDF and bring to any supplier meeting.
What the software should cover
Tick each one that matters to your business.
- Device register
- Firmware release control
- Build batches and component lots
- Programming and calibration records
- Provisioning and activation
- Test, burn-in and shipment
- Returns and field issues
Roles that need their own access
Who logs in, and what each person may see or change.
- For firmware and hardware engineers
- For production and test
- For purchasing and stores
- For support
- For the owner
Reports to ask for
Ask to see each one with your own sample data.
- Devices by hardware revision and firmware build
- Batch yield at programming, test and burn-in
- Units carrying a flagged component lot
- Provisioning failures by step
- Returns by batch, firmware and fault
- Shipped devices by customer with identifiers
- Calibration offsets outside the usual spread
Systems it may need to connect to
Note which ones you already run.
- Programmer and fixture log files
- Label printers
- Cloud device registry
- Accounting export
Questions for any vendor
Put these to every supplier you are comparing.
- Does it update devices over the air?
- Can it stop a wrong firmware from being programmed?
- What if a component supplier recalls a lot?
- How do keys and certificates stay safe?
- Can a customer receive a list of their device IDs?
- Can it deal with devices built by a contract assembler?
- How are existing devices moved in?
- What decides the cost?
Where the work usually breaks today
Circle the ones you recognise. They set the order of the project.
- Firmware versions drift in the field
- Device identifiers are tracked in sheets
- Calibration values are not tied to a unit
- Radio modules and batteries run in lots
- Returns arrive without context
Prefer to talk it through? See the ioT device manufacturers page.