How does the location hierarchy work in FireFlight?

How does Location Mapping handle temporary, shared, and rotating asset locations?

What apps does Location Mapping integrate with?

Work Orders Ownership & Custody Warranty Management Site Management Asset Master Records

What does the Location Mapping app actually track?

• Site, building, floor, and sub-zone hierarchies: A fully configurable location hierarchy that matches your actual facility structure. Every level of the hierarchy is searchable and filterable. Assets assigned to any level are visible from every level above it without requiring separate queries for each location tier.
• Location assignment at acquisition or at any point during asset life: Locations assign when an asset is first registered or at any subsequent point. Assignment at acquisition ensures the record is current from day one. Reassignment at any point logs as a movement event rather than overwriting the history.
• Historical movement logs and relocation event records: Every location change timestamps with the user who made the change. The full movement sequence is available from the asset record. Audit requests that require knowing where an asset was at a specific date are answered from the log rather than from recollection or paper records.
• Temporary, shared, and rotating location support: Temporary deployments, shared tool rotations, and in-transit status all log as distinct location event types with their own context and timeline. The primary location record remains intact while temporary assignments track in parallel.
• Location ties to ownership, maintenance teams, and cost centers: Each location links to the responsible team, ownership record, and cost center associated with assets at that location. When an asset moves, the connected records update with the location rather than requiring manual updates in each linked system.
• Facility-level views for asset counts, usage, and activity metrics: Dashboards show how many assets are at each location, which are active, and where movement volume has been highest over any time period. A facilities manager gets that visibility from the dashboard without requesting a custom report for each site.
• Geographic, functional, and departmental tagging: Locations tag by geography, function, and department simultaneously. An asset in a clean room on the second floor of the east building in the chemistry department carries all three tags and is findable by any of them from the same search interface.

What changes after deploying Location Mapping?

• Technicians stop searching for assets that were moved without a record update. The current location is in the system before they leave for the job, not discovered after they arrive and have to ask around.
• Audit responses are answered from the movement log rather than reconstructed from memory and paper. Where an asset was at any specific date is in the system record rather than in someone's recollection.
• Multi-site asset visibility consolidates into one view. Operations managing assets across multiple buildings or campuses see the full distribution from a single dashboard without switching between location-specific records.
• Temporary deployments track from checkout through return. Shared equipment rotating across crews or departments is accountable at every point in its rotation rather than only when it is at its primary location.
• Maintenance scheduling improves because location is part of the work order. Routing considers where the asset is, not where it was last officially registered, so dispatching decisions are based on current information.