Functional location
Concept
In Dynamics 365 Asset Management, the place where an asset does its job, such as a site, building or production line, organised in a parent-child hierarchy that also carries cost details.
Description
A functional location in Dynamics 365 Asset Management is the place where an asset performs its job. It can describe a site, building, warehouse, workshop, production line or another operational location. Functional locations are elements of a technical structure, such as the functional units of a system, and they are created in a hierarchy of parent and child records. Assets are then installed on these locations, which separates the question of where work happens from the question of which physical item is doing it.
The hierarchy can follow the needs of the organization. According to Microsoft Learn, typical approaches include a functional layout, used to manage assets with similar behavior, a process-oriented layout based on workflows, and a spatial layout based on geographic locations or sites. A simple example from the M365.FM material is a plant that contains a packing area, which contains a conveyor line, which in turn contains individual motors, sensors and rollers. Each level is its own functional location, and the levels together describe how the operation is organized.
From a functional location, users can set up specifications and maintenance sequences for both preventive and reactive maintenance. They can also manage the assets installed there and follow the active requests, work orders and faults registered against those assets. Each functional location is managed independently within Asset Management, so it works as a working record in its own right and not only as a label in a tree.
Costs are a central reason for the concept. An asset can be installed on several functional locations during its life, for example when a pump is moved from one line to another. Costs are always assigned to the functional location where the asset was installed at that time. This keeps maintenance spending tied to the place where it occurred, even when the same asset appears in different locations over the years. The hierarchy therefore also serves as a structure for cost details.
One limitation is stated in the documentation: the structure is not flexible. Once a hierarchy has been built, locations cannot be moved within it. This makes the design of the hierarchy an early decision. Choosing between a functional, process-oriented or spatial layout, and deciding how many levels to model, determines how reporting, maintenance planning and cost tracking will behave later.
The episode "Dynamics 365 Asset Management - Simply Explained" places functional locations next to the asset record. Instead of relying on somebody remembering which machine is which, the asset record provides a consistent reference point, and functional locations describe where that equipment performs its job. The episode uses the plant, packing area, conveyor line and motor example to show how a hierarchy gives technicians context when a motor fails. They do not simply see a serial number, but also where in the operation the failing item sits.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Concept |
|---|
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What is a functional location in Dynamics 365 Asset Management? (AI)
It is the place where an asset does its job, such as a site, building, warehouse, workshop or production line. Functional locations are created in a parent-child hierarchy, and assets are installed on them.
How are costs handled for assets that move between functional locations? (AI)
An asset can be installed on several functional locations during its life. Costs are always assigned to the functional location where the asset was installed at that time.
Can a functional location be moved after the hierarchy is built? (AI)
According to Microsoft Learn, the structure is not flexible, and locations cannot be moved within a hierarchy once it has been built. The hierarchy should therefore be planned carefully before it is created.
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated: