Get the first site device into a known state

Solstice Utilities commissions a new building controller. Until it has a live heartbeat, a device class, and site tags, nobody can answer “is that unit even ours?” when the first alarm fires.

Without Dataplicity

The installer leaves a serial on a handover sheet. Ops discovers the unit weeks later - or never. Contractor access and monitors have nothing durable to attach to.

With Dataplicity

1. Install and claim so the device appears in inventory with a recent check-in.
2. Attach the product class that carries Solstice’s defaults for that controller line.
3. Tag the site and environment (and customer record where enabled) before treating commissioning as done.
4. Confirm the record - class, site, and online state together - then hand the same path to the next building.

Outcome

The first site device is a known operational record, not an orphan waiting for the first outage to invent its identity.

Next

• Connect your first device
• Device classes
• Networks and tags
• Provision and claim

Related: Illustrative customers, Internal IoT operations, Ship the first customer unit you can still support