Appearance
Device mapping
Device context is how support finds the right unit in seconds instead of minutes.
Recommended tagging scheme
| Tag | Example | Purpose |
|---|---|---|
customer | customer:polar-freight | End customer |
site | site:bristol-dc | Deployment location |
asset | asset:GW-0042 | Internal asset ID |
firmware | firmware:2.1.0 | Software version |
deployment | deployment:production | Stage (dev, staging, production) |
Use consistent naming. Document the scheme for your team.
When to apply tags
- After enrolment - assign custom tags through the Dataplicity app or Web CLI.
- During operations - update tags when ownership, site, stage, or rollout cohort changes.
- During reassignment - remove context belonging to the previous customer or site before adding the new context.
Apply searchable customer, site, and fleet context with custom tags in the Dataplicity app or Web CLI.
Device names
Rename devices in the dashboard to something human-readable: bristol-gateway-042 is better than a factory-default hostname.