# Alert-to-repair: before and after context | SourceX

Canonical: https://refer.sourcex.si/guides/alert-to-repair-verification-missing-context
Last updated: 2026-11-04

What gets lost is whether the fix held. A Field Service export shows a job, a part and a status that says verified. It leaves out the number that triggered the job, the transducer swapped during it, the stock the ERP issued and what the replacement transducer reads on a healthy machine. Put back together, those pieces can show the numbers fell partly because the measuring device changed, something no lone export reveals.

This before-and-after reading is part of [alert-to-repair-verification records](/guides/chain-alert-to-repair-verification). The [record linkage page](/guides/alert-to-repair-verification-record-linkage) shows which keys join the systems; this page shows what a reader misses when nobody joins them, using one pump and one autumn.

## Before: the work order export on its own

**Illustrative and fictional.** A 350-person cold-storage operator runs refrigerated warehouses and maintains its own ammonia circulation pumps, with an in-house maintenance crew dispatched through Salesforce Field Service. Here is everything one export says about one job.

| Field | Value in the export |
|---|---|
| Work order | WO-7731 |
| Asset | Pump P-7, warehouse 3 |
| Opened | September 9, 05:50 |
| Subject | "High vibration alarm" |
| Visit | September 10, seal kit replaced |
| Status | Completed, verified |
| Closed | September 12 |

Read on its own, this is a clean record: an alarm, a prompt call-out, a part replaced and a verified close inside three days. Anyone counting first-time fixes would count this one, and a maintenance KPI report would too.

## After: the same job with its surrounding context

Now add what three other places hold. The values remain Illustrative.

The monitoring platform shows the trigger: pump P-7 read 8.4 mm/s at 05:42 on September 9, against an alarm limit of 7.0 and a healthy level for that transducer of about 2.4 mm/s. The ERP shows the job drew two stock items, not one: the seal kit and a replacement transducer, both issued to WO-7731. The technician's notes mention it only as "transducer swapped, cable chafed".

Afterward, the replacement transducer read 2.9 mm/s, below the company's rule of "under 3.5 mm/s within 48 hours", so the work order closed as verified. Over the following weeks, transducers of that newer model settled at about 1.6 mm/s on healthy pumps of the same type. Against that normal, 2.9 mm/s was high. On November 2, P-7 tripped again and a new work order, WO-8120, opened with no reference to WO-7731.

## What went missing, and where it lives

| Lost context | Why it matters | Where it lives | In the Field Service export? |
|---|---|---|---|
| The trigger reading and the alarm limit | Shows how far from normal the pump was | IoT platform measurements and alarm history | No; only the alarm's subject line |
| The sensor swap | Changes what "normal" means after the visit | ERP parts issue; asset records if sensors are tracked | Only as a phrase in notes |
| The new sensor's own baseline | Decides whether the post-repair reading is truly healthy | IoT platform, across comparable units | No |
| The verification rule and when it was set | Shows what "verified" required | Service procedures, sometimes a rule in the IoT platform | No; only the status |
| The repeat failure | Shows the repair did not hold | A later work order on the same asset | Only if both orders are exported and someone links them |

Salesforce's data model links a work order to an asset and a visit to its work order, so the export is internally consistent. What it cannot do is reach into the IoT platform, where AWS IoT SiteWise, for instance, holds each raw measurement as a data stream with its own alias, or into the ERP.

## Why the baseline shift only shows in the after view

The new sensor reported into the same data stream as the old one, so the readings look like one continuous line that drops after the repair. A drop is exactly what verification expects to see. Only two extra facts expose the problem: that the instrument changed on September 10, and what the new instrument reads on a healthy pump. Salesforce documents an AssetRelationship object that records a replacement between assets and the date the old one was uninstalled; a company that tracks sensors that way holds the first fact in a system field. Most hold it only in parts records or notes.

The point for an introducer is not to diagnose pumps. It is to recognize that "verified" in a single export may mean less than it says, and that a company whose records hold the other pieces has a more valuable history than its work orders suggest.

## Asking for the after view without seeing a record

Four questions establish whether the after view could be rebuilt, all answerable at metadata level:

1. Which system holds raw readings and alarms, at what interval, and for how many years?
2. Are parts issues tied to work order numbers, including sensors?
3. When a sensor is replaced, is the swap recorded anywhere other than notes?
4. Are repeat failures linked to the earlier work order?

The CEO can authorize a licensing discussion, usually with the COO or head of maintenance as sponsor; the controls engineer and the service manager can answer the questions but do not authorize it. The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. What stays unknown until SourceX reviews it: how complete each join is, what must be de-identified and whether a buyer wants the equipment type. Score the answers with the [completeness checklist](/resources/alert-to-repair-verification-completeness-checklist). For finding similar companies, see the [field service work order field guide](/guides/a-partner-field-guide-to-finding-companies-with-field-service-work-orders), [field service histories](/data-types/field-service-histories), [maintenance data for AI training](/data-types/maintenance-data-ai-training) and the [systems hub](/systems).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a maintenance team you know can answer the four questions and name who owns its readings, work orders and parts history, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce its decision-maker.

## Sources

- https://developer.salesforce.com/docs/atlas.en-us.field_service_dev.meta/field_service_dev/fsl_dev_soap_core.htm
- https://developer.salesforce.com/docs/platform/object-reference/references/standard-objects/object-assetrelationship.html
- https://docs.aws.amazon.com/iot-sitewise/latest/userguide/asset-properties.html
- https://refer.sourcex.si/terms
