Skip to main content
Assets represent the physical equipment that generates or measures your production data. Each asset can belong to a location, to a project directly, or both, and carries its own typed metadata through custom fields. Manage a project’s assets in Settings → Assets. From there you can create assets, edit their details and custom field values, export the asset list, and edit many assets at once by importing a spreadsheet.

​
What an asset carries

  • Name: how the asset appears across the platform.
  • Location and project: an asset can be parented to a location (a site or facility), attached to a project, or both.
  • Coordinates: per-asset latitude and longitude, independent of the parent location.
  • Custom field values: typed attributes defined by your account’s asset custom fields, such as a serial number, registration status, or registry-assigned ID. See Custom Fields.

​
Editing assets in bulk

To change many assets at once, such as setting a registration status across a fleet of chargers, export the asset list, edit the file, and import it back. Bulk editing is enabled per account; ask your Mangrove account team if you do not see Import on the Assets page.
  1. Click Import, then Export assets to download the current list as CSV or Excel. Start from this file so the Asset IDs match.
  2. Edit the file and upload it. Only the columns in your file are edited. An empty cell empties the saved field, except on a required field, where the row cannot be imported. Rows that do not match an existing Asset ID are skipped.
  3. Review the preview before anything is saved. It shows each asset that will be edited, with its current value beside the value after import, plus the rows that cannot be imported, the rows with no matching asset, and the assets that already match the file.
  4. Click the button under the preview, such as Import 12 assets, and confirm. You can close the window while it runs.
A file can hold up to 5,000 rows, and one import edits up to 1,000 assets. Rows past that are left alone, so move them into a second file. An asset edited by someone else after you uploaded the file is skipped rather than overwritten. A preview you do not apply expires after seven days.

​
Import history and reverting an asset import

Import history on the Assets page lists every import on the project, with who uploaded it, when, and its result. Open one to see what it edited, download the file it used, or revert it. Revert import puts each edited asset back to the value it had before the import. A preview comes first and lists any asset that will not be reverted, with the reason: it has been edited since the import, it is no longer in the project, reverting would empty a required field, or one of its fields cannot be read. An import with some assets left in place reads Partly reverted, and Finish reverting tries those assets again. To apply the edits again after reverting, import the file again.

​
Attaching events to assets

Events can be linked directly to the asset that produced them. When an event type has Requires asset enabled, every event of that type must reference an asset, so per-equipment data can’t lose its linkage during ingestion. Data feeds attach each event to its asset by the asset’s friendly ID. Incoming rows must carry that ID for the event to be linked.

​
Per-asset batches

Models can partition batches by asset, producing one batch per piece of equipment in the generation window. This is the natural fit for programs that report per-unit (per-charger, per-meter, per-well), and each batch surfaces the asset it belongs to.

​
API access

Assets are available through the API. See List assets and related endpoints. Asset custom field values are readable and writable via the same endpoints, which lets external systems keep registration state in sync.