Alert-to-repair-verification record linkage: the keys that join each step, and the link that usually breaks

Short answer

By carrying one key forward at every step: the asset ID from the sensor alert to the work order, the work order number to the visit, the parts issue and the status change, and the sensor's own identity into the readings that verify the repair. Most companies hold the first keys in system fields. The link that usually breaks is the last one, because a sensor swapped during the repair often keeps the old data stream, so nothing records which instrument produced the verification readings.

Visual briefFull-size diagram
Six record cards, from sensor alert to recurrence check, click together in a chain by their join keys; the link between parts issue and verification readings is highlighted as weak because a sensor swap kept the old stream alias, then bridged by an asset replacement record.
Illustrative chain for a fictional building-services contractor. The weak link is the sensor swap; an asset replacement record repairs it.

This page is part of alert-to-repair-verification records, which covers the metadata packet and who to introduce. Its job here is the record chain itself: step, record, key and system, link by link, with the weak link marked.

The chain at a glance: six steps, six keys

Illustrative and fictional. A 420-person building-services contractor monitors air handlers at client hospitals. One fan motor bearing starts to fail. Each row is one step and the key that ties it to the next.

StepRecordKey carried forwardSystem
1. SignalVibration alert on air handler AH-12: 7.2 mm/s against a 6.0 limitAsset tag on the data streamIoT platform
2. DispatchWork order WO-55102 opened on asset AH-12Asset ID on the work order; alert ID typed in the descriptionSalesforce Field Service
3. VisitService appointment: bearing replaced, vibration sensor replacedWork order number as the appointment's parentSalesforce Field Service
4. PartsBearing kit and sensor issued, invoice draftedWork order number on the parts issueERP
5. VerificationReadings of 3.1 mm/s pass the rule "below 4.0 within 48 hours"; status set to verifiedSame stream alias; work order number on the status changeIoT platform and Field Service
6. RecurrenceSeven weeks later, a new alert and work order on AH-12Asset ID, and a parent work order reference if usedIoT platform and Field Service

The keys come from ordinary product design. Salesforce documents that a work order can be linked to an asset and that a service appointment has a parent record, typically the work order. Its WorkOrder object carries an AssetId field and a ParentWorkOrderId field for linking one work order to another. In AWS IoT SiteWise, each raw measurement is a data stream identified by an alias, attached to an asset.

Signal to dispatch

The strongest version: the alert creates the work order automatically, with the asset ID filled in. The common version: a dispatcher reads the alert and opens a work order by hand, typing the alert ID or time into the description. That join works only as well as the habit behind it. Ask which version the company used, and since when.

Dispatch to visit

Usually solid. The visit's parent is the work order, so the appointment, the technician and the time on site travel with it. The slip is a visit booked against the site or account instead of the asset, which happens when a technician services several machines on one trip.

Visit to parts

The ERP issue usually carries the work order number, because parts need a cost destination. The slip is a van-stock part used on the visit and replenished later without a work order reference, so the parts record shows a sensor bought but not where it went.

Parts to verification

This is the weak link. The new sensor starts reporting into the same data stream alias as the old one, so the IoT platform shows one unbroken line of readings. The verification rule compares post-repair readings with a limit set for the old instrument. The work order says "verified", but nothing in the chain says which sensor produced the number. The missing context page shows what that does to a single case.

Verification to recurrence

A repeat failure is often opened as a fresh work order. If the team links it to the earlier one, using a parent reference or a typed note, the chain shows a repair that did not hold. If not, it looks like two unrelated jobs on the same asset.

The fix is to treat the sensor as an asset in its own right. Salesforce documents an AssetRelationship object that records a replacement between two assets, identifies the new asset and holds the date the old one was uninstalled. A company that logs sensor swaps this way, or in any equivalent table, can split the readings at the swap date and judge the verification against the new sensor's own normal.

LinkJoined by a system fieldJoined by typed textNot joined
Signal to dispatchAuto-created work ordersAlert ID in the descriptionDispatcher opened from a phone call
Dispatch to visitAppointment parent recordNot usually neededVisit booked on the site only
Visit to partsWork order number on the issueTechnician note naming the partVan stock replenished without reference
Parts to verificationAsset replacement record for the sensorSwap mentioned in visit notesSame stream alias, no record of the swap
Verification to recurrenceParent work order reference"Repeat of WO-55102" in notesNew work order with no reference

Every row is a question you can ask without seeing a record: which column describes your company, for which years?

Questions that test each key, and who answers them

  • "If you pick a work order from two years ago, can you find the alert that caused it?" The dispatch lead knows.
  • "When a sensor is replaced, does anything in your systems record the swap?" The field service manager knows.
  • "What does a verified status require: a reading, a technician's judgment or just a closed job?" The service operations lead knows.
  • "Can you see that a work order repeats an earlier one?" Again the field service manager.

For Salesforce history retention, see field history tracking retention; for reading technicians' notes as evidence, assessing field service records and resolution notes. Broader context is on field service histories, the Salesforce page and the systems hub.

Authority sits with the CEO, usually the owner in an owner-run company, with the COO or head of service as a likely sponsor, and client service agreements may decide who controls sensor data from client equipment. The company itself 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. Whether the joins are complete enough to matter is something SourceX reviews; the completeness checklist gives a pass, partial or fail guide in the meantime.

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 service company you advise can say which column each link falls in, and 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 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

Which key matters most in this chain?

The asset ID. If the alert, the work order, the parts issue and the follow-up readings can all be traced to the same asset, most of the chain can be rebuilt later even where people typed references by hand. The sensor's own identity is the next most important, because it decides whether the readings after a repair are comparable to those before.

Is a chain joined by typed references worthless?

No. A dispatcher who reliably typed the alert ID into the work order description left a usable join; it is just less certain than a system field. Describe it as typed, say since when, and let the review judge it.

Does SourceX connect to Salesforce or an IoT platform?

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

Sources

  1. developer.salesforce.com/docs/atlas.en-us.field_service_dev.meta/fiel…
  2. developer.salesforce.com/docs/atlas.en-us.228.0.object_reference.meta…
  3. developer.salesforce.com/docs/platform/object-reference/references/st…
  4. docs.aws.amazon.com/iot-sitewise/latest/userguide/asset-properti…
  5. 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