Submitting joint venture assets to GRESB

Edit online

Joint venture assets are often set up in IBM® Envizi ESG Suite as locations belonging to different reporting groups. However, if the same asset location is being reported under a different GRESB reporting entity, which also has a different entity ID, GRESB requires each submitted asset to have a different asset ID.

About this task

Before you send asset location data to GRESB by API, you must configure both the asset ID and the entity ID to be interpreted correctly by Envizi ESG Suite.

When sending data to GRESB, at any time there can be only one active reporting entity. If multiple parent groups of the same location all have the GRESB flag set to Active, the platform considers the group that was set to Active most recently as the group whose entity ID will be used for submission.

The platform bases the check on the Updated_On time stamp when the flag was set to Active. The Active Parent GRESB Group column in the GRESB Group Review page and the Current - Envizi column in the GRESB Asset Summary page both show the active group that the platform has determined to be used for API submission.

Procedure

  1. In the Group Summary page, click GRESB > All Groups Settings.
    The GRESB Group Settings page is displayed.
  2. Review all the groups that have entity Ids and, for any joint venture location, update the GRESB reporting flags as necessary to ensure that only one of the location's parent groups has the GRESB reporting flag set to Active.
    All the other groups in the joint venture location must be set to Inactive.
  3. Review and confirm that the active group’s Entity Id has been recorded correctly in Envizi ESG Suite, and update the Entity ID if necessary.
  4. Review the other settings such as the Reporting Period Starting Month and Floor Area unit.
  5. In either the location's GRESB Location Settings page or the group's Asset Characteristics grid, ensure that the location’s asset Id has been recorded correctly in Envizi ESG Suite and that it matches the parent entity ID for the planned API data submission.
  6. Submit the data to GRESB through either the GRESB Asset Summary (with API) page for the individual asset, or the GRESB Group Review (with API) page for all assets under the same reporting entity group. Before API submission, in whichever page that you use, check that both the entity ID and the asset ID have been correctly populated.
  7. Optional: Repeat the previous steps by adjusting the parent groups active flags and location asset ID for data submission to another GRESB reporting entity, if you are using the same data from the same location.
    For groups that do not need to be submitted, set the GRESB reporting flag to Inactive.