This integration is still in beta. Don't hesitate to give us feedback!

To act on the insights that Sitemark detects, it's important to have an easy and streamlined way to get data out into the field. This guide explains how you can use our Fulcrum integration to provide your technicians a punchlist of anomalies to work on.

1️⃣ Set up Fulcrum

Since Fulcrum is a third party application, some setup is required to make the integration work:

  1. Make sure you have a Fulcrum account. Although you can start a 14-day trial, it won't allow you to use the Developer Pack, so you'll have to use a paid subscription. You can find out more about pricing here. At the time of writing it costs 22$ (account) + $149 (developer pack) = $171/month.
  2. Enable the Developer Pack as described here. The Developer Pack allows our integration to communicate with your Fulcrum account.

Once your account is ready, you can create a new Fulcrum app. An app is essentially a form with a database behind it. It allow you to define what properties you want your records to have. Technicians then use this form to alter the data in the field. Let's get started! 🚀

Go to the Apps section in your Fulcrum account and press the New App button on the top right to create a new app.

You'll arrive on the following screen:

You can see the page consists of three columns. On the left you have a list of fields you can add to the app. Those fields define what properties your records can have. You can drag them to the middle section of the page to create the layout of your form. The column on the right contains the settings of the app, where you can give it a name, a description and an image.

We'll start off by naming our new app. The name will be used to identify the app in our integration, so make sure it's descriptive enough so you easily know what it does. In our example we'll call it Solar Anomalies Punchlist. If you want you can also fill in a description.

Now we'll drag the fields we need to the form. We'll start with an Anomaly ID text field. The text field is the first field type in the Basic section. You can mark the field as required. To allow our integration to automatically match this field to our anomaly IDs, we have to make sure the Data Name is set to feature_id. You can find a list of available fields below.

Drag in any other fields you want. The following fields are available through the Sitemark integration:

General Fields

  • Feature ID (feature_id, text field): The ID of the feature. These are the numbers our platform uses to identify features. For example solar anomaly #753.
  • Site Name (site_name, text field): The name of the site on which the feature is tagged. If you're using a single Fulcrum app for anomalies from multiple sites, this can help you filter on a specific site.
  • Operation Date (operation_date, date field): The date of the operation that detected the feature.
  • Layer Name (layer_name, text field): The name of the layer that contains the feature. For example Solar Anomalies or Annotations.
  • Description (description, text field): The description of the feature, mostly used for annotations.
  • Longitude (centroid_lon, number field): The longitude of the center of the feature.
  • Latitude (centroid_lat, number field): The latitude of the center of the feature.

Solar Anomaly Fields

  • Anomaly Type (solar_anomaly_type, text field): The type of anomaly, like Hotspot or Single Bypassed.
  • Anomaly Cause (solar_anomaly_cause, text field): The expected cause of the anomaly, like Vegetation or Shadowing.
  • Severity (solar_anomaly_severity, text field): The severity of the anomaly, like Mild or Critical.
  • Mean Temperature (solar_anomaly_mean_temp, number field): The mean temperature of the panel on which the anomaly is found in degrees Celsius.
  • Max Temperature (solar_anomaly_max_temp, number field): The max temperature of the anomaly in degrees Celsius.
  • Delta Temperature (solar_anomaly_delta_temp, number field): The delta temperature of the anomaly in degrees Celsius. This is the difference between the background temperature of the panel and the temperature of the anomaly.
  • Estimated Loss (solar_anomaly_estimated_loss, number field): The estimated power percentage loss the anomaly is causing.
  • Remedial Action (solar_anomaly_remedial_action, text field): The action that should or has been taken to fix the issue.
  • Anomaly Reference (solar_anomaly_reference, text field): A unique locator for the panel consisting of 4 digits to mark the location of the table and the panel within that table. For example 4.5.1.2.
  • String Reference (solar_string_reference, text field): An old field before the anomaly reference field existed. A reference to the string to which the anomaly belongs.
  • Panel Reference (solar_panel_reference, text field): An old field before the anomaly reference field existed. A reference to the panel within the string.

An example setup for a solar anomalies app looks as follows:

2️⃣ Sitemark Integration

As soon as you've set up the app in Fulcrum you can move to the Sitemark platform. Take the following steps to push data to your Fulcrum app:

  • Filter out the anomalies you want to push to Fulcrum using the platform filters. You can access the filters on the top right.
  • On the top left of the screen, click on the Integrations button in the Export menu.
  • Log in to your Fulcrum account.
  • Select the form (or app) to which you want to push your data. The matching table will appear on the bottom.
  • Set up the correct matching of the fields. The list contains a row for every available Sitemark field. Note that only fields that occur somewhere in your filtered data will be visible.
    The checkbox on the left of a field indicates if you want to push this information to Fulcrum.
    The select box on the right allows you to select the Fulcrum field to which that Sitemark field should be pushed. If you've set up the data names correctly (as indicated in the list above), the correct fields should be chosen by default automatically. Otherwise you'll have to select them yourself. Note that you can always change the default selected fields if needed.
  • Make sure to indicate that you want to apply the filters, otherwise all data will be pushed to Fulcrum.
  • Once you're ready you can press the Push features button to start the synchronisation. The process can take a few minutes and you'll receive an email as soon as it's finished.

Tips, Tricks and Warnings

💡 If you want to apply more complex filters, you can push data to the same form multiple times.

💡 You can include fields in the Fulcrum form that aren't used by Sitemark. You can add a barcode field for example to keep track of panel replacements.

💡 You can assign records in the Fulcrum app to different technicians to divide the work.

⚠️ If you push a feature several times, it will create duplicates in Fulcrum.

Wrap-Up 🌯

That's it! You just learnt how to create a punchlist of anomalies in the Fulcrum app! 💪 Don't hesitate to send us feedback.

Did this answer your question?