1. What remote diagnosis covers
When a device fails, operations can pull logs, read live data, and send diagnostic commands from the platform, without a site visit. Remote diagnosis (remote diagnosis) brings together log collection, real-time telemetry, and remote control, so the investigation happens in one place and fewer jobs need a truck roll. Several devices can be diagnosed at once, and a diagnostic session can be shared so an expert can help remotely. The same approach is already in use for industrial, energy, and connected-vehicle customers.
2. Diagnostic actions
Log pull
Ask for a log pull and the device uploads logs for the time range you set. The session is recorded, so more than one person can work the case and the steps can be kept.
Property read
Read the device’s current properties and real-time telemetry to see how it is running, and use that to locate the fault.
Diagnostic command
Send a test command, such as ping or a module reboot. Diagnostic rights can differ by role, and a sensitive action can require approval.
3. A typical diagnosis
4. How it works with fault diagnosis
| Remote diagnosis | Fault diagnosis | |
|---|---|---|
| Focus | The action: pull logs, read data, send commands | The analysis: combine several sources for an RCA |
| Together | Used together they shorten MTTR. Diagnostic records can be linked to a ticket, so the fault has a complete file. | |
| Session sharing | An expert can help the person on the front line remotely, and the steps can be kept in a knowledge base. | |
| On site | About 70% of common faults can be closed without a visit. When a visit is still required, logs and data are already collected for the person on site. | |
5. Where teams use it
Industrial, energy, and connected-vehicle customers use remote diagnosis so a fault can be worked without a site visit. The platform supports shared diagnostic sessions, permission control, and approval. SimtoLink can help design the remote-diagnosis approach, connect diagnostic features on the device, and standardize the diagnostic process. Contact us if you want that scoped to your fleet.
Appendix: running remote diagnosis in production
Remote diagnosis holds up in production when three habits are in place. Stress-test and run chaos drills on a pre-production or pilot batch that matches production, including connection storms, a full disk, certificate rotation, and a cross-region failure, and keep the results as an acceptance checklist. Put metrics, alert thresholds, on-call escalation, and audit retention into the change process so a parameter change can be traced and reversed, rather than living in one person’s head. Each quarter, engineering, operations, security, and data should ask whether the metrics still explain business risk, and tie the fixes to tickets and the release calendar. SimtoLink treats the console, open APIs, and exports as operating assets — observable, orchestrable, and auditable — not something you turn on once and abandon. If you want a joint review against your ITSM, IAM, data lake, or edge clusters, contact the SimtoLink solutions team for an implementation note and a risk checklist specific to remote diagnosis.