Skip to content
Manuals and Docs

EcoPhi Portal Structure

Watch this video to get an overview of how the EcoPhi portal is structured:

Play

1.1 Entity structure

The following picture shows how Entities and Sub-Entities as well as Sites are structured on the EcoPhi Portal.

Entity structure

1.2 Site structure

The following picture shows how a Site on the EcoPhi Portal is structured.

Site structure

1.3 Main Entity

  • Definition: The Entity represents the top level of the hierarchy. Typically, there is one Entity linked to one EcoPhi customer. Only an Entity can create new Sites.
  • Example: A solar company using the EcoPhi platform to monitor and control multiple solar systems and facilities.
  • Platform terms: A (Main) Entity using the EcoPhi platform to monitor and control multiple Sites.

1.4 Sub-Entity

  • Definition: Sub-Entities are hierarchically below the Entities and are used to organize different Sites within the organizational structure. They can’t create new Sites but may edit existing Sites if they are permitted to do so.
  • Example: Different departments, subsidiaries, or end-customers of a company, each operating one or various solar systems.
  • Platform terms: Different Sub-Entities of a (Main) Entity, each operating one or various Sites.

1.5 Site

  • Definition: Sites represent physical or virtual facilities and systems that aggregate one or various Data Sources. They are the actual locations or systems where data is collected and monitored.
  • Example: A production plant, a data center, or a solar farm.

1.6 Data Source

  • Definition: Data Sources are specific sources of data within a Site. These can either be physical devices like EcoPhi Boxes or APIs that retrieve data from external systems.
  • Example: An EcoPhi Box for monitoring energy consumption or an API providing weather data for the Site.

1.7 Component

  • Definition: Components are physical devices within the Data Source “EcoPhi Device” that provide measurement data.
  • Example: An inverter in a solar installation, serial, analog, and digital sensors.

1.8 Roles, permissions and rules

Permissions are handled both on Entity and User level.

1.8.1 Entity Permissions

The permission to create further Sub-Entities and edit Sites can be assigned at Sub-Entity level. Thus, actions and settings can be permitted on Sub-Entity level.

1.8.2 User Roles and Permissions

  • Owner: Owns the Entity with all permissions. The Owner automatically has access and can manage all Sub-Entities. Each (Sub-)Entity must have at least one Owner.
  • Manager: Have editing permissions for the (Sub-)Entities where they are a member of. Can create and edit Sites and handle members.
  • Viewer: Have only viewing permissions and can’t edit.
  • Member: Have limited viewing permissions and only see the Site Overview.

1.8.3 Rules

  • (Main-)Entity members see all Sites of the (Main-)Entity.
  • Sub-Entity members see all Sites that have been shared with this Sub-Entity.
  • A User can be a member of several Entities and Sub-Entities at the same time. Users of (Main-)Entities don’t get automatically access to Sub-Entities but need to be added as a Sub-Entity member.