MatterODM by Shenan Yangguang MatterODM by Shenan YangguangEach layer has a different owner, a different failure mode, and a different cost of getting it wrong. We work them in order, but we review them together at every design gate.
Industrial design, mechanical engineering, PCB layout and RF optimisation. For sensor-class devices this is where battery life, antenna performance and enclosure fitment are won or lost — and where a wrong choice shows up as a certification problem two months later.
Board bring-up, drivers, power management, sensor handling and the SDK integration. On a shared platform this is where model differentiation happens: same board, different behaviour per SKU.
Device type selection, endpoint allocation, cluster and attribute mapping, reporting intervals. This is the layer that determines your certification test surface, so it is frozen before implementation.
The commissioning flow, factory provisioning of credentials, OTA update path and the functional test your line will run on every unit. Often left until last, and always more expensive when it is.
| Gate | Deliverable | Typical duration | Decision taken here |
|---|---|---|---|
| G0 | Spec & device-type memo | 1 week | Which device type, which transport, which certification route |
| G1 | Architecture & endpoint map | 1–2 weeks | Endpoint and cluster allocation — the certification surface |
| G2 | Schematic + mechanical layout | 3–5 weeks | BOM freeze for prototyping, tooling go/no-go |
| G3 | EVT samples (engineering validation) | 3–5 weeks | Functional confirmation; list of fixes |
| G4 | DVT samples (design validation) | 3–4 weeks | Design freeze for certification |
| G5 | Certification-ready build | 2–3 weeks | Submit to the lab |
| Approach | Best when | Trade-off |
|---|---|---|
| Shared core board | You want speed and a stable BOM more than a unique electronic architecture | Fastest and cheapest route to market. Differentiation comes from enclosure, firmware feature set and industrial design rather than from silicon. |
| Clean sheet | The product needs a form factor, power profile or sensor configuration the shared board cannot support | Adds 6–10 weeks and a larger NRE. Justified when the mechanical or power requirements are genuinely different. |
| Take over an existing design | You already have hardware and want a manufacturing and certification partner | Often the fastest route of all — unless the existing Matter implementation has structural problems, which we will tell you before you commit. |
What it does, what it must work with, and how it differs from what already exists.
Target cost, battery life expectation, size, and any industrial design already committed.
Which regions you sell into — that decides whether CE/RED and UKCA, FCC, or other compliance work belongs in the plan.
A product description, the ecosystem it must work with, a rough annual volume, and your target markets so we know which compliance set applies. If you already have industrial design or a board, we review it before proposing anything.
Yes, and it is usually the cheapest way to build a range. One certified core board plus different enclosures and firmware feature sets produces several SKUs from a single engineering investment — which is how our own 32-SKU Matter roadmap is structured.
We integrate a mainstream white-label app and cloud stack, or work with yours. The Matter-specific ownership is the data model, cluster implementation and provisioning flow — that is the part we will not hand off.
Yes, and we would rather you did. It is produced at G1 as a document you can review, because changing it later is a certification decision rather than a firmware edit.
Send what you have. We will come back with a device-type recommendation, a development path and an indicative schedule.