Asset Hierarchy

Ecosuite (following the Orange Button taxonomy guidelines) has a simple three level hierarchy for managing assets:

• Portfolio (e.g. grouping of projects based on a specific owner/investor)

  • Project (e.g. Company name)

    • Site (Asset)

      • System (e.g. Building)

This hierarchy will be stored and maintained in Ecosuite and most reporting will be based on it.

Naming Guideline

Project Name: The name of the project entity/LLC name (e.g. ACME MA I LLC, ACME RI X LLC, etc).

Project Code: Based on the LLC name. Up to 4 characters including the state abbreviation (e.g. ACME MA I LLC would become "MA1")

Site Name: The common name used to refer to a project site (e.g. Old Mill, Boondocks etc)

Site Code: Based on the name used for the site. Up to 4 characters (e.g. Old Mill might be "OMIL", but often to keep things simple "S1", "S2", "S3" etc are perfectly good Site Codes when one or more sites exist within a project).

System Name: The type and number of system(s) defines the system name (e.g. one roof mount would be Roof 1, if another roof System was added later it would be Roof 2, one canopy system would be Canopy 1, one ground mounted system would be Ground Mount 1, etc).

System Code: Based on type of system. Up to 2 characters. R: Roof-mount, C: Carport, G: Ground-mount. (e.g. A single roof system would be "R1")

Portfolio

The "portfolio" level is used to agregate many projects together. Portfolio's can be created for the pusposes of regional asset management or for the purposes of financial investment groupings etc. Portfolios have no constraints, hence you can create as many as you want and projects can be grouped many different ways accross multiple portfolios if that is desired.

Project

The project is a concept that groups sites into a single entity. Mostly its wise to use the LLC to define these site groups.

Property	Description	Example
code	The code that identifies the project	AE
name	The user friendly name of the project	ACME LLC
address	The address to use for this project	123 Somewhere St, Main Block, MiddleEarth 22222
sites	The sites that are attached to this project	\{...}

Site

A physical location where the installation is located.

Property	Description	Example
code	The code that identifies the site	SW
name	The user friendly name of the site	Somewhere
address	The address of the site	123 Somewhere St, Main Block, MiddleEarth 22222
systems	The systems that belong to this site	\{...}

System

Used to identify different systems such as buildings and fields at each site.

Property	Description	Example
code	The code that identifies the system	B1
name	The user friendly name of the system	Building "1"

SolarNetwork

Only nodes attached to the Portfolio's SolarNetwork account will be accessed.

The SolarNetwork node source ID naming convention will be based on this hierarchy:

Naming Convention

/<project>/<site>/<system>/<device-type>/<device-id>[/<sub-device-type>[/<sub-device-id>]]

Examples

Virgin Islands,Sugar site, Building “A”, SolarEdge Inverter 1

/VI/SU/B1/INV/1

Virgin Islands,Sugar site, Building “A”, SolarEdge Inverter 1, String Monitor 2

/VI/SU/B1/INV/1/SM/2

Virgin Islands,Sugar site, Building “A”, SolarEdge Inverter 1, Forecast

/VI/SU/B1/INV/1/FORECAST

Virgin Islands,Sugar site, Building “A”, SolarEdge Inverter 1, 12 Hour Forecast

/VI/SU/B1/INV/1/FORECAST/12

Virgin Islands,Sugar site, Building “A”, eGauge kWh generation meter 1

/VI/SU/B1/GEN/1

Naming Convention for Device Types:

Code	Device Type	Example
INV	Inverter	A SolarEdge inverter we are persisting datum from over Modbus RTU
GEN	Generation kWh meter (outputs are watts and wattHours)	A revenue grade meter installed after (aggregating the production of) 3 Solaron inverters
STO	This is effectively same as IMEX, but specifically for energy storage devices	An Import/Export meter that sits in front of a set of batteries or similar energy storage systems
SWI	Switch	A relay triggered by a coil on a PLC or similar
PYR	Pyranometer	A device that collects irradiance and insolation data. When multiple devices exist, our standard numbering is that PYR/1 indicates a physical POA device deployed on site and PYR/2 indicates virtual GHI data provided by satelite.
CON	Consumption kWh meter	A kWh meter that only measures a load, such as "all lighting on floor 3"
IMEX	Import/Export meter (watts +/- and wattHours and wattHoursReverse	A sevice measuring the inflow and outflow of energy from a building that often exports during the day but consumes power at night.
WEA	Weather Station	Provides environmental context values such as temperature, pressure, irradiance, wind speed, wind direction
CAM	Camera	Many camera types supported, connected via the motion plugin or similar (used for confirming snow on panels etc)
EVSE	EV Supply Equipment	An electric vehicle charging station
BESS	Battery with a charger/inverter and a BMS built in	A Battery Energy Storage System

Note, mathematically we have: IMEX = CON - GEN

or

CON = IMEX + GEN

or

GEN = CON - IMEX

Naming Convention for Sub Device Types:

Code	Sub Device Type	Example
SM	Sub Meter	One of many metering points that might exist under a single main energy meter.
STR	String Monitor	A String Monitor with multiple properties to record the strings
FORECAST	Forecast readings	Used to store ML driven forecasting