History of a device

In this guide, we’ll walk you through how to monitor and troubleshoot the history of a device using the OnGuard Controller Dashboard. Learn how to access site overviews, zoom into specific devices, and review 24-hour device reports to verify patrol performance and analyze feedback. We’ll also cover how to use tracking history to differentiate between completed and incomplete patrols, interpret system-injected messages, and understand key metrics like patrol efficiency. By leveraging this data, you can ensure compliance, identify issues, and improve overall operational effectiveness.

Accessing the Site Overview

  • Step 1: Log in to the OnGuard Controller Dashboard.
  • Step 2: Navigate to the Site you want to review.
  • Step 3: Click on the site to open its overview.
    • This provides a map view of the site.

3. Zooming into the Device

  • Step 1: Click on the specific device on the map.
    • The map will zoom in on the device’s location.
  • Step 2: Review the quick snapshot of the device for information like:
    • Battery Level
    • Volume
  • Note: The snapshot only shows current information, not historical data.

4. Viewing the Last 24-Hour Device Report

  • Step 1: Click on the Device Report button.
    • This will pull up the history for the past 24 hours (e.g., 13:24 today to 13:24 yesterday).
  • Step 2: Analyze the signals in the report:
    • Start walking patrol: Indicates patrol initiation.
    • Patrol ended: Marks patrol completion.
    • System-injected messages: These appear when:
      • The device is inactive for over 5 minutes.
      • The device goes offline or is turned off.

5. Interpreting Patrol Efficiency

  • Review the report for patrol statuses:
    • Patrol Complete: Indicates successful patrols.
    • Patrol Not Started: Red indicator; no checkpoints scanned.
    • Patrol Incomplete: Efficiency less than 100%.
  • Click on entries with an information icon for additional feedback from the controller.

6. Tracking Device History

  • Step 1: Access the tracking history to view GPS coordinates.
    • Remember:
      • This is not a vehicle tracking system.
      • The platform uses GPS data for patrol monitoring.
  • Step 2: Analyze the plotted points:
    • Stationary Guards: GPS drift may occur, causing slight deviations.
    • Moving Guards: Points will follow a general path of movement.

7. Comparing Patrols

  • Incomplete Patrol: May show erratic or insufficient GPS points.
  • Complete Patrol: Shows a consistent path covering checkpoints.
  • Step 3: Review feedback for discrepancies between the report and guard input.

8. Examples of Historical Insights

  • Device Turned Off: Reports when the device was shut down and restarted.
  • Offline Status: Tracks when the system injected an offline message (e.g., after 5 minutes of inactivity).

9. Using the Information

  • Use the history report to:
    • Verify the guard’s claims.
    • Troubleshoot patrol inefficiencies.
    • Ensure compliance with patrol protocols.
  • Share findings with management or supervisors for actionable steps.

10. Key Tips

  • Be aware of GPS drift when analyzing movement.
  • Compare feedback and tracking data to get a complete picture of patrol performance.
  • Leverage the tracking history and patrol efficiency data to optimize guard operations.

Share This Post