Functional Locations
Model sites, areas, systems and positions as a tree, and install assets into them.
Overview
A functional location is a place in the plant that keeps its own history even when the machine in it is replaced. Locations form an unlimited tree of types facility, area, system, line, unit and position. An asset is installed into a location; removing it ends the occupancy but keeps the history.
When to use functional locations
- You want maintenance history to follow the position rather than the serial number.
- You need a site, building and room structure.
Prerequisites
Step by step
Field reference
| Field | Description | Required | Data type | Business meaning |
|---|---|---|---|---|
| Code | Unique location code. | Yes | Text | Used in reports and search. |
| Type | Level of the location. | Yes | Facility, area, system, line, unit, position | Describes the role in the tree. |
| Parent | Location it sits under. | No | Location | Builds the tree; cycles are refused. |
| Criticality | Importance of the position. | No | Low to critical | Inherited into risk views. |
Permissions
These permission keys control access (granted to roles in Administration → Roles & Permissions):
- assets.location.manage
- assets.asset.read
Automation
- Changes on this screen are written to the asset audit trail and the asset timeline.