One pump repair, read twice: what a standalone Salesforce Field Service export leaves out of alert-to-repair verification

Short answer

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.

Visual briefFull-size diagram
A work order card for pump P-7 shows four blank fields; tiles labelled IoT readings, ERP parts and asset history slide in to fill them with the trigger reading of 8.4 mm/s, a seal kit plus sensor swap, a post-repair 2.9 mm/s, and the new sensor's normal of 1.6 mm/s.
Illustrative case for a fictional cold-storage operator. The export said verified; the joined record says the check used the wrong baseline.

This before-and-after reading is part of alert-to-repair-verification records. The record linkage page 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.

FieldValue in the export
Work orderWO-7731
AssetPump P-7, warehouse 3
OpenedSeptember 9, 05:50
Subject"High vibration alarm"
VisitSeptember 10, seal kit replaced
StatusCompleted, verified
ClosedSeptember 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 contextWhy it mattersWhere it livesIn the Field Service export?
The trigger reading and the alarm limitShows how far from normal the pump wasIoT platform measurements and alarm historyNo; only the alarm's subject line
The sensor swapChanges what "normal" means after the visitERP parts issue; asset records if sensors are trackedOnly as a phrase in notes
The new sensor's own baselineDecides whether the post-repair reading is truly healthyIoT platform, across comparable unitsNo
The verification rule and when it was setShows what "verified" requiredService procedures, sometimes a rule in the IoT platformNo; only the status
The repeat failureShows the repair did not holdA later work order on the same assetOnly 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. For finding similar companies, see the field service work order field guide, field service histories, maintenance data for AI training and the systems hub.

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, check who qualifies and read the program terms before you introduce its decision-maker.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is a single-system export ever enough?

For some questions, yes. A Field Service export alone shows visit volumes, response times and what technicians recorded doing. It cannot show whether the repair worked, because the evidence for that sits in the readings and the parts history.

Does the company need to join the systems before an introduction?

No. Nobody joins anything at the introduction stage. The introducer only learns whether the pieces exist, which keys connect them and who owns each system; any joining happens later, under the company's control.

Why does a replaced sensor matter so much?

Because two sensors on the same machine can read differently when both are healthy. If verification compares the new sensor's readings with a limit set for the old one, a machine that is still running rough can pass.

Sources

  1. developer.salesforce.com/docs/atlas.en-us.field_service_dev.meta/fiel…
  2. developer.salesforce.com/docs/platform/object-reference/references/st…
  3. docs.aws.amazon.com/iot-sitewise/latest/userguide/asset-properti…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment