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.
| Step | Record | Key carried forward | System |
|---|---|---|---|
| 1. Signal | Vibration alert on air handler AH-12: 7.2 mm/s against a 6.0 limit | Asset tag on the data stream | IoT platform |
| 2. Dispatch | Work order WO-55102 opened on asset AH-12 | Asset ID on the work order; alert ID typed in the description | Salesforce Field Service |
| 3. Visit | Service appointment: bearing replaced, vibration sensor replaced | Work order number as the appointment's parent | Salesforce Field Service |
| 4. Parts | Bearing kit and sensor issued, invoice drafted | Work order number on the parts issue | ERP |
| 5. Verification | Readings of 3.1 mm/s pass the rule "below 4.0 within 48 hours"; status set to verified | Same stream alias; work order number on the status change | IoT platform and Field Service |
| 6. Recurrence | Seven weeks later, a new alert and work order on AH-12 | Asset ID, and a parent work order reference if used | IoT 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.
Link by link: how each key is carried and where it slips
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.
Repairing the weak link: an asset replacement record
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.
| Link | Joined by a system field | Joined by typed text | Not joined |
|---|---|---|---|
| Signal to dispatch | Auto-created work orders | Alert ID in the description | Dispatcher opened from a phone call |
| Dispatch to visit | Appointment parent record | Not usually needed | Visit booked on the site only |
| Visit to parts | Work order number on the issue | Technician note naming the part | Van stock replenished without reference |
| Parts to verification | Asset replacement record for the sensor | Swap mentioned in visit notes | Same stream alias, no record of the swap |
| Verification to recurrence | Parent work order reference | "Repeat of WO-55102" in notes | New 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.