Updating an Anomaly Cause

This article explains what to do if the type or cause of a thermal anomaly was misidentified by the Fuse platform.

Updated over a week ago

Introduction

Being able to update an Anomaly cause is an important part of the process loop with inspection your solar site. It ensures that you have full control of your results and closes the feedback loop of the inspection.

This article will explain some of the benefits of being able to edit your anomalies as well as how to do it both on the platform and on the field app.


Benefits of editing the anomaly

There are a lot of benefits to editing an anomaly in the Fuse platform, rather than just performing the edit in your local Excel sheet for example.

  1. It allows you to keep using all other functionality in the Fuse platform: statistics, report exports, filters, etc.

  2. It keeps the digital twin up to date, enabling accurate historic comparisons of operations or comparisons with electroluminescence scans.

  3. When you identify a mistake, we will learn from it, so that mistake won't happen again.


Editing an anomaly in the platform

When working in the Fuse platform, you can easily change an anomaly's type or cause. Just click on the anomaly to open the anomaly popup. Then click the edit icon on the top right to edit it.

Some anomaly causes like Inverter or Wiring can never be determined by the platform. These causes can be used by you when a field assessment has determined these to be the cause of the anomaly.

Anomaly edit screen

Anomaly editing can be used for a lot of other use cases, including punchlist management and serial number tracking.

You can also edit multiple anomalies at once using our bulk edit feature.


Editing an anomaly in the field app

In some cases, the real cause of an anomaly can only be deduced in the field. In that case, you can edit the anomaly type and cause in the field app and import it back into the platform.

The short GIF below will show you how to update the anomaly cause in the field app.

Edit an anomaly's cause in the Fulcrum field app

Did this answer your question?