Last updated:

Automatically create Caterpillar (VisionLink) assets as assets in SafetyCulture

Learn how to automatically create Caterpillar (VisionLink) assets as assets in SafetyCulture.

Caterpillar is recognized as one of the world's leading manufacturers of construction and mining equipment. As part of their technology solutions, VisionLink is a cloud-based software application that receives telematics data seamlessly to desktop or mobile devices to help customers monitor and optimize the performance of their equipment.

An example use of the Caterpillar (VisionLink) app.

With SafetyCulture, you can set up an integration that automatically creates your Caterpillar assets as assets in SafetyCulture, empowering you to keep your assets well-maintained using inspection schedulesactions, and more. Over time, changes you make to your assets in Caterpillar will also automatically sync to their corresponding assets in SafetyCulture, ensuring details are always up-to-date.

You may need to enable third-party cookies for your browser to support this integration.

  1. Log in to the web app.

  2. Click your organization name on the lower-left corner of the page and select Integrations.

  3. Scroll to "Caterpillar (VisionLink)" and click Set up.

  4. In the pop-up window, click Install.

  5. Click Pencil iconEdit, then click Pencil iconEdit once more.

  6. Enter your CAT client ID and client secret. Both should be provided to you as part of your ISO 15143-3 (AEMP 2.0) API subscription with Caterpillar.

  7. Click Connect.

  8. The integration will now perform the following tasks:

    • Create a "CAT asset" asset type with all the Caterpillar asset details as custom fields. If an asset type named "CAT asset" already exists, that type will be updated with the required custom fields.

    • Check if each Caterpillar asset already exists in SafetyCulture by checking its "Equipment ID" against each asset's "Unique ID":

      • If a match is found, update the asset's type with the fields required for the integration and update the asset itself with the vehicle details.

      • If a match is not found, create the vehicle as a new asset.

When installing for the first time, the integration may take some time to sync data into SafetyCulture as assets.

Frequently asked questions

You can connect your existing assets to the integration by updating the "Unique ID" to match your asset management system's "Vehicle Name" (Samsara, Geotab, or AT&T) or "Equipment ID" (Caterpillar).

Please ensure you update your existing assets before installing the integration to prevent duplicates from being created.

Integrations with asset management systems sync changes to SafetyCulture every 10 minutes, so changes you make might not immediately reflect in SafetyCulture.

If an asset created from an asset management system integration has been archived, the asset will remain archived and no longer receive updates from the integration.

If an asset has been deleted, a new asset will be created the next time the integration syncs.

The integration may have been turned off due to an authentication error. Either because the external account used for the integration no longer has access to the system or its permissions to make changes have been removed.

When this happens, an email would be sent to users with the "Platform management: Organization" permission to inform them about the error. To fix the problem, we recommend that you uninstall the integration and follow the instructions to install it again.

You can view your telematic readings within the asset profile. You can click on a relevant reading to view historical readings, including those pre-dating the installation of your integration, and export them to CSV.

View telematic readings for your asset via the web app.

If you get a connection error while installing the integration, it's likely because your browser is blocking third-party cookies on SafetyCulture websites. To fix this, we recommend that you enable third-party cookies in your browser settings and try installing the integration again.

Example of a connection error when installing an integration via the web app.

Need more help?
In this article