Location level GRESB Asset Summary with API

Edit online

Use the GRESB Asset Summary (with API) page to review your asset configuration at the location level, and then submit it to GRESB through the embedded API.

The GRESB Asset Summary (with API) page contains the following main features:

You can use the GRESB Asset Summary (with API) page to interrogate location data down to the GRESB question level, and gain an understanding of how the data being reported to GRESB is summarized. The Current - Envizi column shows data that is automatically populated for each GRESB Real Estate Assessment question, based on various data points captured in the platform.

You can manage and update your responses data in the Location Settings page. You can also configure location level instructions to categorize your data, and apply explicit GRESB tags to accounts, and then review the final answers in the GRESB Asset Summary (with API) page. For more information, see the related link.

The following table describes the columns in the GRESB Asset Summary (with API) page.
Table 1. Location level GRESB Asset Summary (with API) grid columns and descriptions
Column Description
Section This fields aligns with the sections in the GRESB portal and the Asset Level Spreadsheet.
Field This refers to the field name in GRESB.
Previous - Envizi Values captured in Envizi for the previous reporting period as defined by logic in the GRESB Sections and Performance Indicator Data Sources.

Note that the GRESB API does consider some fields (for example, Asset Name, Property Type, Gross Asset Value, Asset Size) captured in Asset Characteristics to be annual data even though there is no option to populate these in the GRESB or the Asset Level Spreadsheet. For this reason they have been exposed in the Grid.

This column is blank if the field has been disabled for the previous period, for example to indicate that no value will be sent to GRESB.
Previous - GRESB After data has been sent to GRESB, this field will show the value stored in GRESB for the previous period.
Current - Envizi Values captured in Envizi for the current reporting period as defined by logic in the GRESB Sections and Performance Indicator Data Sources..

This column is blank if the field has been disabled for the current period, for example to indicate that no value will be sent to GRESB.
Current - GRESB After data has been sent to GRESB, this field will show the value stored in GRESB for the current period.
Previous - Percentage This field calculates the percentage of actual data according to requirements in Appendix 7 in the GRESB Reference Guide where at least 80% of your data must be actual data.

This field is calculated by dividing the number of months of actual data by the total number of months expected for the reporting period. This field and the following four fields will only populate for rows that track activity data (for example, kWh, GJ, and son on).

Note: If your asset was bought or sold during the previous or current reporting period as reflected in the GRESB Reporting Characteristics (RC) section under Owned Since or Owned Until, it will not be reflected in the percentage. This field assumes that 12 months of data is expected for every account so this value cannot be relied on in this instance.
Previous - Accounts/Meters Count of number of accounts and meters for the activity data listed.
Previous - Actual Months Count of the number of months of actual data.
Previous - Estimated Months Count of the number of months of accrued or estimated data.
Previous - Missing Months Count of the number of months of missing data. If your asset was bought or sold during this period, it’s likely that you will not have data stored in Envizi for the period where the asset was not owned.
Note: If your asset was bought or sold during the previous or current reporting period as reflected in the GRESB Reporting Characteristics (RC) section under Owned Since or Owned Until, it will not be reflected in the percentage. This field assumes that 12 months of data is expected for every account so if this field is showing missing months, investigate if the asset was owned for the entire period.
Current - … For the fields that relate to the current reporting period, similar logic as for the fields that relate to the previous reporting period.
Last API Action Date and time of the last API action in UTC.

Note that the first row of the grid shows the date and time of the last data received from GRESB. If the time shown in this row is before the time shown on other rows, then refresh your browser to retrieve the latest data.
Status The status field is a concatenation of 2 statuses: Envizi Request status - API Call status.
Envizi Request
  • Pending: request has been submitted but not yet picked up.
  • Active: request has been picked up.
  • Error: the request encountered an error. The details of the error can be reviewed in the Validation column.
  • Completed: the request has been returned and the Validation column will show any issues with the data.
API Call
  • Pending: API has not yet been reached.
  • Active: API is active. This status usually progresses quickly.
  • Initiated: this status means Envizi is compiling the data to be sent to GRESB
  • Requested: data has been sent to GRESB and Envizi is waiting for a response.
  • Responded: GRESB has responded with the data and validation. At this point it is possible that the grid is not showing the latest data that exists in GRESB if the last request was to submit data. Envizi always requests fresh data when loading the grid, so if the most currently submitted data is not showing, refresh your browser. This can be tested by comparing the timestamp of the field submitted or validated against the timestamp found in the first row of the grid which will always show the latest data received from GRESB.
  • Error: this will appear when there is an error specific to the API call that was made. For example, if a validation request was made but the asset ID was incorrect, this returns an error.
  • Completed: this status will show when the API call is complete.
Disabled This field will show fields that are disabled for the current period, previous period or both periods where applicable.

This feature is used when you want to stop Envizi from sending data for certain fields that are more easily handled outside Envizi in the Asset Level Spreadsheet or directly in the GRESB portal.
Validation This field shows GRESB validation returned with submit or validation requests.

Note that some validations are returned regardless of which fields were passed with the submit or validate requests.
Sync This field is useful for comparing Envizi data with GRESB data to see if data matches or has not yet been sent. Filter this column to focus on discrepancies.
GRESB Variable This field shows the GRESB variable name that appears in the API and on row 1 of the Asset Level Spreadsheet on every tab.

When validation is returned, the GRESB Variables are returned instead of the field names so this field can be useful when interrogating your data based on validations received.
Envizi Data Source This field lists the logic used to derive the values appearing in the Previous - Envizi and Current - Envizi columns. For more information, see the GRESB section and performance indicator data sources topics.