Highlights
What this service covers
- Node registration, certificate bootstrapping, and registry lifecycle state
- Groups, tags, metadata, sharing, and batch operator actions
- OTA job visibility, firmware image tracking, and fleet health widgets
Operate connected products after launch.
Fleet Management
Fleet Management expands the public operations story beyond the website's sales-lead admin page. It describes how product teams register nodes, issue device identity material, organize the registry, coordinate firmware operations, and review fleet-wide operator widgets in a future IoT platform console.
Capabilities
Platform building blocks
- Register nodes, bind manufacturing records, and rotate or revoke device certificates as products move through activation and support workflows
- Search the device registry by model, region, firmware, customer, ownership, or rollout cohort while applying bulk tags and service actions
- Review activation counts, firmware distribution, alert queues, and queued OTA or support work without implying this marketing site is the production operator console
Outcomes
Why product teams use it
- Give product and operations teams a credible public admin-platform narrative
- Keep the website lead admin boundary separate from future IoT console scope
- Connect provisioning, release, and support workflows under one fleet-operations story
Operations Surface
Map each admin workflow to the right platform boundary
Realtek Connect+ now describes the public operations story in concrete operator terms while keeping the website's own admin runtime clearly scoped to lead review.
| Workflow | What operators manage | Why it matters | Website boundary |
|---|---|---|---|
| Node registration | Serials, models, bootstrap certificates, claim state, and factory readiness for newly manufactured devices. | Gives support and onboarding teams a traceable source of truth before devices reach customers. | Described as future platform-console scope; this repo does not expose a live node-registration UI. |
| Device registry | Searchable inventory, groups, tags, timezone or ownership metadata, and node-sharing visibility. | Keeps fleets searchable and lets teams target the right cohort for support or release actions. | Public feature content only; the current Go app ships marketing pages plus protected lead review. |
| Release operations | Firmware images, OTA jobs, rollout cohorts, and batch actions tied to registry segments. | Lets release managers coordinate campaigns without breaking the device inventory context. | OTA and fleet operations are described credibly, but the website runtime is not a production release console. |
| Statistics widgets | Activation totals, firmware distribution, alert backlog, and operator task queues. | Surfaces the metrics product, support, and operations teams watch first after launch. | These widgets describe expected operator dashboards; the shipped admin endpoint remains /admin/leads for website sales workflow only. |
Registration
Register nodes with durable device identity boundaries
The fleet story now starts at the point where hardware leaves the factory and enters a managed registry.
- Record serial number, model, MAC, factory lot, and claim state when a node is first registered into the platform catalog.
- Issue bootstrap certificates or device credentials, then support rotation or revocation workflows when products are repaired, replaced, or reworked.
- Keep claim tokens, activation checkpoints, and ownership-transfer state tied to the device record so support teams can trace onboarding history.
Operations
Use one registry to drive firmware and support workflows
Registry views are positioned as the operator surface that connects provisioning, OTA, and customer support work.
- Search the device registry by region, firmware, product family, installer, or customer account and save groups for repeat operations.
- Coordinate firmware images and OTA jobs from the same operations surface so release managers can move from device search to rollout action without spreadsheet handoffs.
- Apply batch tags, metadata edits, ownership updates, reboot requests, or service-state changes when support teams need to act on a cohort instead of one device at a time.
Operator Widgets
Show the metrics an IoT admin console would surface first
Dashboard widgets keep the page concrete while staying honest about what this repository actually ships today.
- Summarize activation counts, firmware mix, online-versus-offline ratios, alert backlogs, and support escalations in operator-facing statistics widgets.
- Use these widgets to highlight where OTA jobs, registration failures, or field alerts need attention before they become customer-visible incidents.
- The existing /admin/leads page only covers website sales leads; the future IoT platform admin console described here remains a public product narrative rather than a shipped control plane in this repo.
Next step
Evaluate Fleet Management for your product roadmap.
Share your product category, target deployment, and cloud requirements with the Realtek Connect+ team.