Resources
What to prepare before you brief a remote supplier.
Most delays start with a missing document, not a missing idea. These checklists and definitions are the ones we use at kickoff — published here so you can prepare before the first call.
Documents
Request a document. Get a version with a date.
We do not publish undated PDFs that go stale. Each document is issued against a program, a model or a specific question.
Capabilities overview
Process, disciplines and evidence package. Useful for an internal supplier review.
Reliability test report
An anonymized report showing how results, conditions and deviations are recorded.
Certification register
Document types, scopes and how verified copies are issued for a model and market.
Project brief template
A one-page structure for control target, protocol, markets, volume and timing.
Checklists
Two checklists that save a month of back-and-forth.
The first is for the brand team. The second is for the engineering team that owns the protocol.
Project brief checklist
- What the handset must control, by device family
- Which link each device uses — IR, BLE, RF, 2.4 GHz
- Target markets and required certification
- Annual volume and pilot quantity
- Launch window and a hard deadline, if any
- Brand assets: logo, CMF, packaging direction
- Existing product or a competitor sample
- Who signs off the key map and the design
Protocol document checklist
- Frame format and byte order
- Pairing, binding and unbinding rules
- Key codes and repeat behavior
- Security: keys, rolling code, encryption
- Update path and recovery behavior
- Timing and latency requirements
- Receiver model, firmware version and a sample
- What counts as a failure in the field
If a box cannot be filled, that is useful information. It becomes the first discovery item in the scope.:
Glossary
The words that change a quote, defined once.
A shared definition prevents a long conversation about a short word.
| Term | What it means here | Why it matters |
|---|---|---|
| IR | Infrared, a one-way line-of-sight light link | Needs a clear path and a matched code set |
| BLE | Bluetooth Low Energy | Pairing, GATT services and update behavior must be defined |
| GATT | The BLE data model of services and characteristics | Custom GATT is firmware work, not a checkbox |
| OTA | Over-the-air firmware update | Needs an update transport, validation and a rollback plan |
| EVT / DVT / PVT | Engineering, design and production validation builds | Each answers a different question; skipping one moves risk |
| DFM | Design for manufacturability | A design that cannot be assembled repeatably is not finished |
| CMF | Color, material and finish | Affects cleaning, UV, RF and perceived quality |
| IP rating | Ingress protection under IEC 60529 | A rating requires a test; “sealed” is not a rating |
| MOQ | Minimum order quantity | Driven by tooling and line setup, not by policy alone |
| BQB | Bluetooth qualification | Applies to the declared Bluetooth design |
Questions
Using these resources
Can I use the checklists with another supplier?
Do you publish prices?
Is there a newsletter or a downloadable catalogue?
Start a project
Use the checklist as your brief.
Fill what you can and send it. The empty fields are the first things we will ask about.