You are managing your organization's assets. You need to give your organization's technicians better visibility on their locations in order to reduce travel time and time spent searching for the asset when the technicians arrive on site. How should you structure the system to manage this request?

Functional locations are designed to represent the physical location of assets in a hierarchical structure (e.g., Country > City > Building > Floor). This allows technicians to easily visualize where an asset is located, from a broad area down to a specific room. By attaching an asset to a functional location, you provide the precise location information needed to reduce travel and on-site search time, directly addressing the requirement.

A. Asset properties are used to record specific characteristics or readings of an asset (like temperature or pressure), not its physical location.
C. A service account tree shows customer relationships but does not provide the granular, hierarchical physical location details required for an asset.
D. Creating a custom entity is unnecessary as the standard 'Functional Location' entity is specifically designed for this purpose.

- Microsoft Learn. (2023). Create and manage customer assets in Dynamics 365 Field Service. Section: "Functional locations". "Functional locations allow you to specify where a customer asset is located... You can build a hierarchy to represent a location."

- Microsoft Learn. (2023). Asset properties in Dynamics 365 Field Service. Section: "Overview of asset properties". This document details how properties are for asset characteristics, distinguishing them from location data.