Set up a new project
The end-to-end path from nothing to a live, monitored project — the order to do things and the guide for each step.
Setting up a building for the first time is a handful of steps, done roughly in order. This page is the map: what to do, why, and the guide for each step. Do them top to bottom and you’ll go from an empty account to a project that’s collecting data, showing it on pages, and alarming on it.
1. Register a server
The on-site server is what collects a building’s data and sends it to the Cloud. Register it first so you can point the project at it.
2. Create the project
A project is one building or site. Creating it — and choosing the server from step 1 — is what gives everything else a home.
3. Connect devices and add tags
Tags are the individual values you read — a temperature, a pump’s run state. Add the devices that provide them, then the tags themselves. This is the data everything downstream is built on.
4. Build a page
A page turns tags into a picture an operator can read at a glance. Start with one and the rest follow the same pattern.
5. Set up alarms
An alarm watches a tag and raises a flag when something’s wrong — a temperature too high, a device gone quiet. Add the ones that matter for the site.
6. Give your team access
Finally, let the people who’ll use the project in — operators on site, managers in the Cloud — each with the right role.
Who does what
Steps 1, 2, and the account side of 6 are system-administrator work (servers, projects, and user accounts live across the whole organization). Everything inside the project — tags, pages, alarms, and granting access on that project — is done by a Manager or Admin on it. See the roles matrix for the full picture.