Navvion

Remote Diagnostics

Fix it before the truck rolls.

Guided troubleshooting, alarm correlation, and a FRACAS knowledge loop that turns every fault into a faster fix next time.

How It Works

From alarm to resolution.

A disciplined path from the first alert to a documented fix — remote when possible, dispatched with full context when not.

1

Detect

ISA-18.2 alarms arrive prioritized — floods suppressed, noise shelved.

2

Correlate

Related alarms, telemetry, and history are grouped into one incident.

3

Diagnose

Guided troubleshooting trees built from fleet-wide failure history.

4

Resolve or dispatch

Fix it remotely — or dispatch a technician with parts, access, and steps attached.

5

Learn

The outcome feeds FRACAS, so the next occurrence resolves faster.

What Changes

Service economics, rewritten.

Remote-first resolution

Many faults are diagnosed and cleared over the connection before a truck is ever scheduled.

One incident, not an alarm flood

Related alarms, telemetry, and history are correlated into a single incident, so teams triage the problem — not the noise.

Every fault makes the next fix faster

Outcomes feed FRACAS, turning each resolution into fleet-wide knowledge that shortens the next occurrence.

Capabilities

Engineering tools, service outcomes.

The same telemetry that runs the dashboards powers root-cause work.

Guided troubleshooting

Step-by-step diagnostic trees keyed to alarm signatures — first-line teams resolve what used to escalate.

  • Pack-level telemetry drill-down
  • Firmware and configuration context
  • Escalation with full case history

FRACAS knowledge loop

Failure Reporting, Analysis, and Corrective Action — every fault, root cause, and fix becomes searchable fleet knowledge.

  • Structured failure records
  • Root-cause taxonomy
  • Corrective actions tracked to closure

Smart dispatch

When remote resolution isn't possible, dispatch carries the full context — a qualified technician, the right parts, and site access.

  • Qualification-checked assignment
  • Parts list attached to the ticket
  • Safety requirements included

The Knowledge Loop

FRACAS: report, analyze, correct, prevent.

Failure Reporting, Analysis, and Corrective Action System — the discipline that turns field faults into a compounding knowledge base.

1

Report

Every fault becomes a structured failure record with telemetry, firmware, and configuration context attached.

2

Analyze

Records are classified against a root-cause taxonomy so patterns across the fleet become visible.

3

Correct

Corrective actions are tracked to closure, from a config change to a firmware fix or a service bulletin.

4

Prevent

Guided troubleshooting trees update from what was learned, so first-line teams resolve next time what used to escalate.

Questions

Remote diagnostics, answered.

What is FRACAS and why does it matter?

FRACAS is a Failure Reporting, Analysis, and Corrective Action System. It captures every fault, root cause, and fix as searchable fleet knowledge, so recurring problems resolve faster each time they appear.

Can faults really be fixed remotely?

Many can. Guided troubleshooting and pack-level telemetry let first-line teams clear issues over the connection, and only genuine field work is dispatched to a technician.

How are alarm floods handled?

Alarms follow ISA-18.2 prioritization: floods are suppressed, nuisance alarms are shelved, and related alarms are correlated into a single incident rather than a wall of notifications.

What does a technician get when a job is dispatched?

A qualification-checked assignment with the parts list, site-access details, safety requirements, and the full case history attached before anyone leaves the shop.

How does this connect to Fleet Management and the Installer Portal?

Diagnostics runs on the same telemetry as APM and Fleet Management, and dispatch checks the same live credential records the Installer Portal maintains.

Is diagnostic data secure and access-controlled?

Yes. Access is role-based, and diagnostic data lives on the asset's own record within the same platform that runs monitoring — not in a separate, unmanaged tool.

Next Step

Cut truck rolls, not corners.

See how remote diagnostics changes the economics of service.