Create a project

A project holds one body of twin work: the models you define, the entities you create from them, the data bound to those entities, and the screens built on top. It also keeps its own history, so the project is the unit you version and the unit you grant access to.

Everything you make from here on lives inside the one you create now.

Switch to Scenes Studio using the app switcher. It opens on a list of the projects you can reach, which is empty on a new installation.

Create it

Start a new project and fill in three fields.

Name — what this project covers.
Description — what the deployment is for and how far it reaches. One or two lines; you can change it later.
Model namespace — assigned automatically from the name. You can edit it before creating the project, but it is fixed once the project exists.

Confirm, and the project appears in the list.

Deciding what goes in one project

A project is a boundary in two ways that matter: it has one history, and access is granted to it as a whole. Put things together when you want them versioned together and seen by the same people.

That boundary is yours to draw, not something the physical world settles for you. A project might cover a single building, several buildings on one campus, or every site in a region — sites are entities you create inside a project, so one project can hold many of them.

Two questions usually decide it.

Do they change together? Work that is reviewed and published as one piece belongs in one project, because a revision covers the whole project.

Should the same people see all of it? If one group must reach part of it and not the rest, separate projects make that boundary plain rather than something you maintain by hand.

If you are unsure, start with one. Splitting later is work, but so is discovering that two parts needed separate access all along.

As for the name: name what the project covers, not why you started it. North Plant ages better than Energy Monitoring Pilot — the pilot ends, the plant does not.

Where you land

Open the project. You stay in Scenes Studio and arrive at Models, where you would normally begin describing what exists.

You are going somewhere else first. The next step sends a reading before anything is modelled, which means switching to Data Hub — so leave Models for now and come back to it in step four.

Next, send your first sample.