PlcConsoleChoose the time window that matches the question, identify the signal and inspect its detailed evidence.
Administrator summary cards are directional signals. Detailed records remain in the selected operational tab.
Changing the window recalculates both the summary and the detail query. Use a short window to understand what is happening now and a longer window to identify recurrence rather than comparing counts from different periods as though they represented the same workload.
Open Filter to add one or more criteria. Criteria use AND, the active count stays visible and Clear criteria restores the full result.
The compact row identifies the event. Expansion separates request details, result details and the fields changed by the operation.
Non-admin users do not receive the estate-wide administrator dashboard. Their overview is limited to PLCs visible to the signed-in user, effective capabilities and the previous 24 hours of attention or activity.
Role permissions are the baseline shown to the user. A PLC command policy may still narrow register families and ranges and the backend evaluates both boundaries for every command.
Dashboard cards summarize records in the selected time window. A count is a starting point, not a diagnosis.
| Signal | Question it answers | First detail to inspect |
|---|---|---|
| Unhealthy PLCs | Which visible devices currently have health evidence requiring attention? | PLC health, latest probe, site route and agent state. |
| Failed commands | Which allowed operations reached execution but did not complete successfully? | Failure class, PLC, site, duration and correlation evidence. |
| Denied commands | Which requested operations were stopped by visibility, permission or policy? | User, PLC, site, denial reason and request attributes. |
| Active users | Who generated activity during the selected period? | User identity and associated event volume. |
| Agent attention | Which site-agent conditions require connectivity or heartbeat review? | Agent state, last connection, heartbeat and last error. |
Check visibility, effective permission scope and the PLC's command policy. The request should be stopped before PLC traffic when authorization or policy does not allow it.
Check route availability, PLC reachability, timeout, queue and protocol result. The user may have been authorized even though execution failed.
Expand the change record to see request, result and changed values. Use it to determine whether an operational symptom followed an administrative edit.
Use onboarding issues to find resources that exist but are not yet usable, such as a site without its expected connectivity or a tenant awaiting setup completion.
Confirm that the same time window and detail tab are active, then clear filters. Pagination can place matching records on another page.
Verify the active tenant, user visibility and PLC lifecycle state. A command policy does not make a hidden PLC visible.
Open Agent connections and Agent failures together. Match the timestamps and inspect the current site-agent detail before changing credentials.
Use the table's horizontal scroll area or expand the row. Command, failure and correlation detail belongs in secondary detail rather than being inferred from clipped text.