How Texture is organized
The building blocks you'll see across Texture, and how they fit together
Your organization holds workspaces. Each workspace holds your sites and programs. Sites have devices and meters, whose readings roll up to the grid elements above them.
| Building block | What it is | Learn more |
|---|---|---|
| Organization | Your company in Texture. Members, roles, and sign-in settings such as SSO belong to the organization. | Organizations and workspaces |
| Workspace | A separate environment inside your organization. Every organization starts with production for real data and sandbox for testing. Data and API keys in one workspace aren't visible from another. | Organizations and workspaces |
| Site | A service location, usually a street address. A site links to its contact, the person who lives or works there, and to the meters and devices installed there. | Sites and contacts |
| Contact | The person or business at a site. | Sites and contacts |
| Devices and meters | Batteries, EV chargers, thermostats, inverters, and AMI meters. They carry the readings. | Devices and connections, Meters |
| Grid elements | Transformers, feeders, and substations. Their usage is rolled up from the meters beneath them, and SCADA adds measurements at the substation. | The grid hierarchy |
| Program | A demand response, VPP, or other offering. Members enroll, and you run events against their enrolled devices. | Programs and enrollments |
Because these are connected, you can move between them: from a site to its devices, from a meter up to its transformer, or from a program to the sites and devices enrolled in it.