Vista Integration and Equipment De-duplication | CLUE Learning

When equipment data arrives from multiple sources at the same time, the same physical machine can end up as two or three separate records in your system. Vista calls it EQ-0042. Samsara calls it 42. Someone entered it manually in Clue as "the blue Komatsu" before the sync ran. Without a system to recognize these as the same asset, work orders land on one record, GPS data updates a second, and meter readings go to a third. Nothing connects.

Vista Integration and Equipment De-duplication in Clue solves this by linking records from different sources to a single original asset, so your team always sees one machine with its complete history in one place. Learn more about the broader Clue and Vista integration.

‍

Who Is This For?

• Equipment Managers rely on de-duplication to ensure that GPS data, work order history, and Vista records are all visible on the same asset record rather than scattered across multiple entries in the directory.
• IT and Integration Administrators configure and maintain the matching parameters that determine how records from different sources are linked during the Vista sync process.
• Shop Managers benefit from having complete asset records where fault codes, inspections, and repair history are all consolidated on one asset rather than split between duplicate entries.

‍

The Problem De-duplication Solves

A typical fleet receives equipment data from three or more sources simultaneously:

• Vista provides the equipment master with full details including make, model, VIN, and department
• GPS and Telematics providers such as Samsara, John Deere, and CAT send location and engine data, often using a different equipment ID format
• Manual entry adds assets in Clue before the Vista sync has run or before a telematics device is installed

Without de-duplication, the same machine gets two or three records. Work orders are assigned to one, GPS location updates another, and PM schedules track against a third. The data is correct in each place but useless because nothing connects to give you the full picture.

‍

How De-duplication Works?

1. Detection

During each Vista sync cycle, Clue attempts to match incoming equipment records against existing assets in the system. Matching is attempted using the standard Equipment field from Vista's EMEM table, the VIN, and the udCleanEquipNo UDF which stores a sanitized equipment alias when the standard ID has formatting differences between systems.

2. Linking

When a match is found, the records are linked in Clue's EquipmentDuplication table. One record is designated as the original, typically the Vista record. The others become linked duplicates. All history stays on the original record.

3. Selective Updates

For linked records, only specific fields are updated from Vista during subsequent syncs. This is controlled by the vista_equipment_metadata_fields_from_duplicated parameter. Fields controlled by another source, such as GPS engine hours or telematics location data, are excluded from Vista overwrites so each source retains authority over its own data.

‍

What Gets Merged?

When a Vista asset is successfully linked to a GPS-tracked asset, a single consolidated record holds data from all sources:

• From Vista: Make, model, year, VIN, department, category, ownership status, and custom UDF fields
• From GPS: Live location, engine hours, odometer, fault codes, and idle time
• From Clue: Work orders, PM schedules, inspection history, and timecards

Everything is visible on one asset record. One place for the complete picture.

‍

Key Behaviors and Limitations

• De-duplication runs per organization. Each company's equipment is matched independently. There is no cross-organization de-duplication.
• The original record retains all history. Work orders, inspections, fault codes, and PM history remain on the original asset record. Linking a duplicate does not move or delete any existing data.
• Selective field sync prevents source conflicts. The metadata fields parameter controls exactly which fields Vista updates on linked records. This prevents Vista from overwriting data that should be owned by a GPS or telematics source, such as live engine hours or location.
• De-duplication mapping loads once per sync cycle. The matching table is loaded at the start of each sync for performance. Changes to the mapping do not take effect until the next sync cycle runs.

‍

Tips

• Check the EquipmentDuplication table when an asset appears to have incomplete data. If GPS location shows on one record and work orders appear on another, those records may not yet be linked. Investigate whether the equipment IDs or VINs differ between sources and configure matching accordingly.
• Match by VIN whenever possible. Equipment numbers change between systems, get reformatted, or use different prefixes depending on the source. VINs are permanent and do not change. VIN-based matching is the most reliable method for catching duplicates across sources.
• Review the metadata fields parameter if Vista overwrites are causing data conflicts. If Vista is updating fields that your GPS or telematics provider should own, such as engine hours, adjust the vista_equipment_metadata_fields_from_duplicated parameter to exclude those fields from the Vista update on linked records.‍
• Run a duplicate audit after the initial sync. The first sync after connecting Vista is the most likely time for unlinked duplicates to appear. Review the asset directory for obvious duplicates immediately after the first sync completes and configure matching rules to prevent them from recurring.