Set up customer asset hierarchies
An air-conditioning unit can contain a compressor, fan assembly, and other components. Your service organization might need to track the whole unit and also maintain a separate history for a component that receives its own inspections or repairs.
A customer asset hierarchy represents these equipment relationships. It helps technicians understand which component belongs to which system without confusing the equipment structure with the customer's buildings and rooms.
Model equipment, not places
Use parent and child asset relationships for equipment that forms part of other equipment. For example:
- Rooftop Unit 01: The main item of equipment.
- Compressor 01: A child asset of Rooftop Unit 01.
- Fan Assembly 01: Another child asset of Rooftop Unit 01.
The compressor and fan assembly have the rooftop unit as their direct parent. If you separately track a component within the fan assembly, that component's direct parent is the fan assembly, not the rooftop unit.
The building and roof describe where this equipment is located. Represent them with functional locations rather than customer assets. The next unit explains how to connect the equipment hierarchy to the location hierarchy.
Not every replaceable part needs its own asset record. Create child assets when the organization needs to identify and service those items separately. A filter consumed during maintenance can remain a work order product unless there is a business requirement to track that specific filter as equipment.
Agree on this level of detail before importing a large register. An equipment hierarchy that matches service responsibilities is easier to maintain than one that records every catalog part as a separate asset.
Create parent and child relationships
The Parent Asset field identifies an asset's immediate parent. To add the compressor under the rooftop unit:
- In Field Service, change to Service and select Assets under Assets.
- Create or open the asset record for Rooftop Unit 01 and verify its account.
- Create or open the asset record for Compressor 01.
- Set Parent Asset to Rooftop Unit 01.
- Check the account and functional location, then select Save.
- Open Rooftop Unit 01 and review its Sub Assets grid to confirm the relationship.
You can also use the Sub Assets grid on a parent asset to add child assets. Check the resulting child record rather than assuming that a similar name establishes the relationship.
The Top-Level Asset identifies the main asset at the top of a hierarchy. It isn't interchangeable with Parent Asset: a component several levels down has an immediate parent as well as a top-level ancestor.
For example, a separately tracked fan motor can have Fan Assembly 01 as its parent while Rooftop Unit 01 remains the top-level asset. Choose the immediate parent to preserve that intermediate relationship.
For more information, see Work with customer assets.
Review the hierarchy during service changes
On the service account, open Assets and Locations and select Show assets to view the equipment alongside the location structure. Expand the relevant branches to check that each item appears under its intended parent. The tree helps you examine the relationships; it doesn't replace checking the individual asset records.
Before using the hierarchy for service, verify:
- Equipment identity: Each separately maintained item has a distinguishable asset record.
- Immediate parent: A component is under the equipment that directly contains it, not just another item at the same site.
- Location consistency: A component and its parent equipment are located together. Field Service doesn't let you place a subcomponent at a different functional location from its parent.
- Service association: Each work order incident refers to the asset that receives the work. A parent relationship alone doesn't identify which item an incident services.
If a technician transfers a component to another unit, review its parent and location together. Moving a component under a parent at another functional location can replace the component's location with the new parent's location. Confirm the saved record after the change.
In the HVAC example, a repair to Compressor 01 belongs against that asset when you need a compressor-specific history. An inspection of the complete rooftop unit can refer to Rooftop Unit 01. Choose the association based on the scope of the work, not simply whichever record is highest in the tree.
Provide optional 3D reference models
A three-dimensional model can help a technician recognize equipment and understand its component layout. Field Service supports associating a model with customer assets; the same model can be associated with multiple assets. The model supplements the asset record and service instructions. It doesn't create the parent and child asset relationships.
Before adding models, confirm that the 3D Viewer solution is installed in the environment. Supported file types include GLB, GLTF, and OBJ. Ask an administrator to check attachment-size limits and blocked file extensions rather than changing organization-wide attachment restrictions without review.
To add a new model and associate it with an asset:
- Open the customer asset and select Related > Three-Dimensional Models.
- Select Add Existing Three-Dimensional Model, then select New Record > Three-Dimensional Model.
- Enter a Name, set Storage Type to Note Attachment, and select Save.
- In Timeline, select the paperclip icon, choose the supported model file, and select Open.
- Enter a title and select Add note.
- Select Save & Close, then select Add to associate the model with the customer asset.
For a model that already exists, use Add Existing Three-Dimensional Model to select and associate the existing record instead of uploading another copy. Verify that the model opens and represents the correct equipment before relying on it as a service reference.
For setup prerequisites and the full procedure, see Use 3D models with customer assets.