Locations

Purpose

This page organizes where monitoring happens so readings, alerts, and actions are tied to the right physical context.

Prerequisites

• Your facility/location hierarchy should be defined.
• Devices should be ready for assignment.
• Users need permission to manage location records.

Main Actions

• Create and maintain location records.
• Assign devices/probes to specific locations.
• Update location details when operations change.
• Review location-linked monitoring coverage.

Field/Status Reference

• Location Name: Operational label used throughout the platform.
• Parent/Grouping: Higher-level area, site, or tenant mapping.
• Assigned Devices: Devices currently linked to the location.
• Coverage Context: What process/asset the location represents.
• Active State: Whether the location is currently in use.

Workflow

1. Create or confirm the location record.
2. Link devices to the location.
3. Validate incoming logs for that location.
4. Use location context when triaging alerts.
5. Update records as layouts or workflows change.

Connections

• Provides context for Probe Logs and Alerts.
• Determines where Devices are assigned.
• Helps incident and compliance reporting stay accurate by area.

Common Mistakes

• Creating duplicate locations with similar names.
• Moving devices physically without updating assignment.
• Leaving retired areas active, causing noisy or confusing data.

Troubleshooting

• If location filters return no data, verify assigned devices are reporting.
• If alerts show wrong area names, check device-location mapping.
• If records are hard to use, standardize naming conventions across sites.

Quick Tips

• Keep location names consistent and specific.
• Review assignment changes after facility moves.
• Archive or deactivate unused locations to keep views clean.