Alert-to-repair-verification records across IoT, Salesforce Field Service and ERP: what proves a fix worked

Short answer

A referral partner can describe a company's alert-to-repair-verification records from metadata: which IoT platform holds sensor readings and alerts, how work orders and visits are kept in Salesforce Field Service, which ERP records parts and invoices, the years and asset counts each covers, the identifier that ties a reading to a work order, and who owns each system. The case to test is a sensor replaced during a repair, because the new sensor resets what "normal" means.

Visual briefFull-size diagram
A vibration chart for one compressor shows an alert at 5.1 mm/s, a repair visit where the sensor is also replaced, post-repair readings of 2.3 mm/s that pass the old 3.0 check, and the new sensor's own healthy level of 1.4 mm/s, which the reading still exceeds.
Illustrative. The repair passed a check written for the old sensor; against the new sensor's baseline it had not.

The business task behind the records

A service company watches customer equipment, sends a technician when a machine signal crosses a limit, and decides afterwards whether the repair worked. That last decision is the valuable one. It joins a measured problem, a human diagnosis, the parts used and a measured outcome, and it is rarely written down in one place. Field service histories of this kind are covered more broadly on the field service histories and maintenance data for AI training pages.

Three systems usually hold the pieces. The IoT platform keeps raw measurements and alert events; in AWS IoT SiteWise, for example, measurements are an asset's raw sensor streams, each with a data stream alias, and transforms are values calculated from them. Salesforce Field Service keeps the work: work orders describe the job and can link to an asset, case, account or service contract, and service appointments are the scheduled visits under a work order. The ERP keeps parts issued, warranty claims and the invoice.

What metadata can a referral partner collect about alert-to-repair-verification without reading private content?

A short packet: one column per system, one row per fact you can learn by asking. You never need a reading, a work order or an invoice. The values below are Illustrative, for a fictional 300-person commercial refrigeration service company.

The metadata packet (Illustrative)

Packet fieldIoT platform (alert)Salesforce Field Service (visit)ERP (parts and billing)
Object typesMeasurements, alert events, thresholdsWork orders, service appointments, assetsParts issues, warranty claims, invoices
Years held2019 onward2016 onward2014 onward
Rough volumeAbout 4,800 monitored compressorsAround 22,000 work orders a yearAbout 61,000 part lines a year
Identifier the next step can useData stream alias per sensorAsset ID and work order numberWork order number on the part issue
Is the sensor itself an asset?Stream renamed on swap? UnknownCompressors yes, sensors noSensor part number only
Rule for "repair verified"Threshold per model, writtenStatus set by technicianNot held
System ownerControls engineering leadService operations managerFinance systems manager
Planned changePlatform renewal in 2027NoneERP replacement under review

Record answers as the client gives them, including "unknown". A packet with honest gaps is more useful than one that guesses. Counts can be ranges ("roughly 20,000 to 25,000 work orders a year"); you are describing the archive, not auditing it.

Three rows deserve the most attention in conversation:

  • Identifier. If a work order stores the asset and the alert time, the chain from signal to visit can be rebuilt later. If the dispatcher only types a description, it may not.
  • Sensor as an asset. Salesforce documents an AssetRelationship object that records a replacement between two assets, with the new asset and the date the old one was uninstalled. Whether the company uses anything like it for sensors decides whether a swap is visible at all.
  • Verification rule. Ask whether "verified" means a measured threshold, a technician's judgment or simply a closed work order.

For Salesforce retention defaults, see field history tracking retention.

The sensor swap: how it shows up in a packet

The open case for this chain is a repair in which the sensor is replaced along with the failing part. Here is the Illustrative case drawn in the graphic above.

On June 3, sensor A on one compressor reads 5.1 mm/s, above the alert limit of 4.5. On June 4 a technician replaces the bearing and, because the old sensor looks worn, the sensor too. From June 6, sensor B reads 2.3 mm/s. The work order rule says a repair is verified below 3.0, so the visit closes as verified. But sensor B's own healthy level, measured on identical units, is 1.4 mm/s. Against that baseline the compressor was still running rough, and it failed on July 19.

Nothing in that story is visible from the work order alone, and nothing in it requires reading a record to flag. In the packet it becomes two plain answers: "sensors are not tracked as assets" and "verification uses one fixed threshold per model". Write those down and move on. Whether the company's archive can still separate a real fix from a baseline shift is a question for SourceX's review, not for the introducer.

Who can authorize a discussion, and what stays unknown

Alert-to-repair records span operations, IT and finance, and the equipment may belong to the company's customers. The sponsor is usually the COO, the head of service or the owner. The controls engineer and the service operations manager can answer the packet but rarely have authority to license anything. Customer service agreements often decide who controls sensor data from customer equipment, which SourceX reviews.

Before you introduce, confirm:

  • The company has 50+ full-time employees at peak, contractors excluded, and a documented operating history.
  • The company has the right to license the records, including sensor data collected on customer sites.
  • A named decision-maker will take a first call.
  • 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: whether the records can be de-identified to a buyer's standard, which equipment types and years a buyer would want, how customer agreements limit use, and what the company would be paid. You never handle or forward raw records. Related reading: the field service work order field guide and assessing field service resolution notes. If the ERP is being replaced, the ERP replacement handoff checklist applies; the Salesforce page and the systems hub cover other record locations.

Go deeper on alert-to-repair-verification records

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 your client's service lead can fill in the packet, answer the sensor-replacement question and name who owns the IoT platform, Field Service and the ERP, register as a partner, check who qualifies and read the program terms before you introduce them.

  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

Does the company need sensors on its equipment for this to matter?

The alert half of the chain needs some machine signal, whether from an IoT platform, a building management system or a controller log. A company with work orders and parts history but no sensor data can still have valuable field service records; it just holds a shorter chain.

Is a fleet with many repeat repairs a bad introduction?

No. Repeat repairs with recorded outcomes are part of what makes a history informative. What matters is whether each visit can be tied to the alert before it and the readings after it.

Does SourceX connect to Salesforce Field Service or an IoT platform?

No connector is implied. Salesforce and AWS IoT SiteWise are named because their public documentation describes the objects involved. If the company proceeds, it decides what to share under a signed agreement.

Sources

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

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