Associate customer assets

Completed

Rooftop Unit 01 needs another inspection after a compressor repair. Before dispatching a technician, the service manager needs to know which equipment received the repair, what the technician found, and whether the same problem appears again. A work order that mentions only the customer's building doesn't establish which of its air-conditioning units received service.

Associating the correct customer asset with service work builds a history that supports these decisions. It also provides context for Copilot work order summaries when that feature is available.

Associate assets with work order incidents

A work order incident groups the work for a particular issue or service requirement. Associating an asset with that incident identifies the equipment being serviced. For example, an annual HVAC inspection incident can refer to Rooftop Unit 01.

To associate the primary asset:

  1. Open a work order for the appropriate service account.
  2. Select the Incident type for the work, such as the annual HVAC inspection.
  3. In Primary asset, select Rooftop Unit 01.
  4. Select Save.

If the visit also includes Rooftop Unit 02, add another work order incident and select that asset for the additional incident. Don't associate the first unit with work intended for the second simply because both belong to the same customer.

When an asset is associated with a work order incident, Field Service also associates it with the work order products, services, and service tasks that result from that incident. For example, the inspection tasks generated for Rooftop Unit 01 refer to that unit.

Important

The association applies to records resulting from the incident. Selecting the primary asset doesn't automatically make every unrelated or manually added line on the work order part of that asset's history. Check the asset association on additional records when you add them.

After saving, review the incidents and their generated records. Confirm that the equipment, work description, and service account match. This check is especially important when one visit covers several similar assets.

For more information, see Build a service history for assets.

Review service history and Copilot summaries

Open the customer asset and review its related work orders. Follow the links to the underlying work order records rather than treating an asset name alone as evidence that a specific repair occurred.

Useful service records describe:

  • Reported problem: What the customer or technician observes.
  • Work performed: The inspection, repair, products, and services recorded for the correct asset.
  • Results and follow-up: Findings, completed tasks, and any additional action the equipment needs.

For Rooftop Unit 01, a note that identifies the replaced compressor and the remaining symptom is more useful than "maintenance completed." Record the findings on the appropriate service record so another technician can understand what happened.

Use a summary to prepare, not to replace the history

The default Copilot work order summary can include asset information and the asset's work order history. For scheduled and in-progress work orders, this information helps the technician understand the equipment and previous work. Administrators can configure which data contributes to a summary, so don't assume every environment uses the same content.

When the feature is enabled, open the work order or booking in the web app and select Generate in the Copilot control. Use Regenerate to refresh the summary after relevant records change. Open the source references to check details before deciding what work or parts the visit requires.

The summary respects your permissions and uses the available records. A repair linked to the wrong rooftop unit can therefore provide misleading context. Correct the underlying records rather than relying on a summary to infer the intended equipment.

Note

Work order summaries require connectivity and a paid Field Service environment; they aren't available in trial environments. An administrator must ensure the feature is enabled. The generated summary isn't saved as a permanent service record.

For more information, see Summarize work orders with Copilot and Enable work order summary with Copilot.

Handle assets associated with another account

By default, the assets available for a work order belong to its service account. This validation helps prevent accidental associations with another customer's equipment.

A rental or lease arrangement can require a different model: the provider owns the equipment, but the work order serves the customer using it. In this case, an administrator can allow assets from other accounts:

  1. In Field Service, change to Settings.
  2. Under General, select Field Service Settings.
  3. On the Work Order / Booking tab, set Disable Customer Asset Validation to Yes, and save.

Use this organization-wide option deliberately, not as a workaround for an incorrect asset account. Confirm the ownership and service-account model with the service manager before changing validation, then verify the asset chosen on each work order.

See Disable customer asset validation on work orders.

Connect assets with recurring maintenance

For recurring agreement work, select the Customer Asset on the agreement booking incident. When the agreement generates work orders, those work orders include the incidents and their associated assets. An annual inspection agreement can therefore contribute to the same asset history as a separate repair visit.

Field Service also provides asset maintenance plans as an optional preview capability. Choose the mechanism that matches the requirement:

  • Agreements: Generate recurring work orders and, when configured, recurring invoices using predefined frequencies and date ranges.
  • Asset maintenance plans (preview): Define maintenance for an individual asset using calendar-based, actual usage-based, or multistep schedules. The system forecasts service events and generates eligible work orders according to the schedule and work order creation lead time.

A customer asset can have one maintenance plan containing multiple schedules. Reusable templates help apply common maintenance requirements to similar assets. Applying a template creates a snapshot; later template changes don't update existing asset plans.

Usage-based maintenance uses recorded usage; it isn't a promise that AI predicts equipment failures. Generating a maintenance work order also isn't the same as booking a technician. Coordinate maintenance plans and agreements so both processes don't generate duplicate work for the same requirement.

Important

Asset maintenance is a preview feature, isn't intended for production use, and can have restricted functionality. It isn't required for the asset association and service-history workflows in this unit.

For more information, see Customer agreements overview and Asset maintenance overview (preview).