You've just received an email informing you of completing your thermal inspection. A quick dive into the platform reveals some hotspots, a string that's down, some open panels, and several potential PID issues.

This article will explain how to start using the remedial actions on the platform and some helpful tips on how it can be used to focus your interventions and make them more efficient.

When you first open the operation there might be a lot of anomalies that have been identified in this inspection.

Let's look at what information we can use to determine which anomalies are worth investigating further and what we should do about them.

You can start by clicking on one of the anomalies on the map to open the anomaly information modal specific to that anomaly.

You can see that this specific anomaly might be a PID issue, which is a physical problem inside the module. However we can see that it's still relatively early in it's degradation process as it's only lost 20% of it's capacity.

While there's a lot more data to explore in the other sections, this article will focus on the Remedial action section. If we open it up, we'll find Sitemark's recommendations for this anomaly.

The Remedial Action field highlights what action to take for this anomaly. Since the problem isn't too bad, the platform suggests monitoring it. You can do that through your monitoring system, field checks, or yearly drone scans. The platform will also track this anomaly through your future inspections of this site to monitor it's progress.

The Estimated Remedial Cost highlights what that remedial action will cost you. It's handy to prioritise remedial actions. To learn more about the remedial costs and how they are calculated, you can check out this support article on thermal anomaly properties.

The Status field tells you whether you should still look at the anomaly, whether a fix is in progress, whether the issue has been resolved, or whether you won't do anything about it. In this case, we'll leave it on To Do until we've gathered more information to decide.

You've seen an example of remedial action in the previous section. Here's a table that highlights the different remedial actions supported by the platform.

If any of the recommended remedial actions are incorrect, or if you want to include some modules in a warranty claim, you can edit the anomaly to change it.

You can edit them one-by-one or in bulk using our bulk edit feature, to learn more about how to use this feature you can find the support article here.

In order to better prepare for any interventions you might make based on these results, it will be helpful to look at different views of your results. To do this, you can filter on the Remedial Action data point. Some examples of how this can be useful are shown below.

Learn more about filtering.

Modules that must be replaced, repaired, or moved must be sent to your technical team. You can filter out these issues and either export them as Excel or PDF or send them to the Field Link to automatically get the updates back into the Fuse platform.

Learn more about the Field Link

If the modules have to be cleaned or vegetation has to be removed, you should either wait for the next routine maintenance or order the next service.

We recommend routine maintenance before a thermal inspection to avoid this thermal anomaly.

If additional information has to be collected, the Field Link is a great way to do that. Once all the information is available, a PDF report is usually enough to complete your claim.

Learn more about the Field Link

If you're using the Field Link, completing a remedial action is as easy as changing the status of that ticket to resolved and importing the changes back into the platform.

If you're using the platform itself, you can edit the anomaly to change the status to resolved to indicate that this intervention has taken place and the problem should not persist.