Reports

Reports use embedded analytics, so they load differently from normal list and form pages. The left sidebar is the report catalog, and the main workspace renders the selected dashboard or table after an extended load window.

Live validation date: March 12, 2026

1. Open the Reports Workspace

Purpose: Confirm the reporting module is reachable and the live report catalog loads.

Route / context: /reports/superset/1

Steps:

  1. Sign in to the portal.
  2. Open Reports from the top navigation.
  3. Allow the page extra time to load.
  4. Confirm the left report catalog appears.
  5. Confirm the default report body renders on the right.

Expected result: The Reports workspace opens with the catalog on the left and the selected report in the main panel.

Reports - Catalog and default report

2. Cargo and Driver Reports

Purpose: Review cargo volume and driver registry reporting.

Validated routes:

  • Cargo and Truck Summary -> /reports/superset/1
  • Driver List -> /reports/superset/18

Steps:

  1. Start from the Reports workspace.
  2. Select Cargo and Truck Summary when you need the default cargo dashboard.
  3. Select Driver List when you need the reporting view focused on drivers.
  4. Wait for the embedded analytics panel to finish rendering before changing report again.

Expected result: The cargo dashboard or driver report loads without leaving the portal shell.

Reports - Driver list

3. Journey Reports

Purpose: Review journey analytics, arrival outcomes, and arm/disarm audit activity.

Validated routes:

  • Journey Dashboard -> /reports/superset/2
  • Journey Arrival Report -> /reports/superset/8
  • Arm Disarm audit -> /reports/superset/19

Steps:

  1. Open Journey Dashboard for overall journey analytics.
  2. Use the same sidebar section to switch to Journey Arrival Report or Arm Disarm audit.
  3. Pause after each selection so the analytics frame can finish rendering.

Expected result: Journey reporting pages render inside the same analytics workspace, with the left catalog remaining available for switching.

Reports - Journey dashboard

4. Alert Reports

Purpose: Review alert trends and alert-position analysis.

Validated routes:

  • Alert Summary -> /reports/superset/3
  • Alert Position Report -> /reports/superset/9

Steps:

  1. Select Alert Summary for the main alert analytics dashboard.
  2. Switch to Alert Position Report when the investigation needs position-focused reporting.
  3. Treat a short blank state as normal while the iframe content loads.

Expected result: Alert dashboards render within the Reports workspace after the normal extended load window.

Reports - Alert summary

5. Inventory Reports

Purpose: Review stock visibility and inventory custody distribution.

Validated routes:

  • Inventory -> /reports/superset/4
  • Inventory distribution and custody -> /reports/superset/15

Steps:

  1. Select Inventory for the standard inventory report.
  2. Use Inventory distribution and custody when the focus is distribution or custody analysis.
  3. Wait for the report panel to refresh fully before capturing or presenting the result.

Expected result: Inventory reporting opens in the same embedded analytics frame without leaving the portal.

Reports - Inventory

6. Device and Custody Reports

Purpose: Review device-level analytics and custody history.

Validated routes:

  • Device Summary -> /reports/superset/11
  • Current Custody -> /reports/superset/12
  • Custody History -> /reports/superset/13

Steps:

  1. Select Device Summary for the main device dashboard.
  2. Use Current Custody when the immediate custody position matters.
  3. Use Custody History when the investigation needs prior handoff context.

Expected result: Device and custody reports render as report pages inside the same module shell.

Reports - Device summary

7. Maintenance Reports

Purpose: Review maintenance workload and repair reporting.

Validated routes:

  • Maintenance -> /reports/superset/5
  • Maintenance Repairs Report -> /reports/superset/14

Steps:

  1. Select Maintenance for the main maintenance dashboard.
  2. Switch to Maintenance Repairs Report when the focus is repair-specific reporting.
  3. Use the visible charts, summary tiles, and tables after the dashboard finishes loading.

Expected result: Maintenance reporting renders with charts and summary metrics inside the portal analytics panel.

Reports - Maintenance

8. System Report

Purpose: Review access-related analytics from the system reporting area.

Validated route:

  • Login Dashboard -> /reports/superset/10

Steps:

  1. Open the System section at the bottom of the report catalog.
  2. Select Login Dashboard.
  3. Wait for the dashboard to render before drawing conclusions from the page.

Expected result: The system login dashboard loads successfully inside the same reporting shell.

Reports - Login dashboard

9. Operational Notes for Reports

  • Reports can load more slowly than normal list, form, or dashboard pages.
  • The first load after sign-in is often slower than later report switches.
  • A short blank interval is not, by itself, evidence of failure.
  • If the catalog loads but a selected report does not, wait through the normal extended report window before escalating.
  • Escalate when multiple report pages repeatedly fail after their normal load window or when the report catalog itself does not appear.