Delivery: start with 1–5 sample sets, scale after it works.

Requirements → samples → validation → volume supply.

Delivery

01
Define requirements
List rooms or zones, device models, protocols, quantities and target ecosystems; confirm existing devices to keep.
02
Assess a show scene
Pick one room or zone, validate hardware, gateway, platform and branded App, then decide volume purchasing.
03
Validate the full experience
Check local control, state feedback, AI permissions and required Matter functions; record scope and limits.
04
Prepare delivery & O&M
Before scaling, confirm device versions, account roles, config backups and maintenance responsibilities.

No volume commitment up front.

Scenes, categories, protocols, quantities; manuals and register maps for existing devices.

1–5 sample sets with SaaS / App trial. AI parses the docs, the test gateway is taught on site, real results confirmed.

Confirmed devices enter the standard product library, reused across App, 3D, AI and Matter; volume supply per project.

AI parsing keeps page and line numbers; missing info flagged for confirmation.

Control and writes confirmed first; deployed devices never changed silently.

Project data isolated; never used for public model training or cross-project search.