Skip to main content
OMNINET VISIONOmniNet Vision LLC — home

Illustrative sample — not a live client report.This uses a fictional manufacturing plant to show the shape of a recurring assurance report: what changed, what it cost operations, the evidence, assigned actions, and verified improvement. When the lab produces real data, this page will switch to lab-labelled output.

Sample report

Midwest Fabrication — Plant 3

Period: 2026-09-01 → 2026-09-30 · Timezone: America/Chicago · Calculation version: report-v0-illustrative

Engineer-reviewed summary for plant leadership and the network owner. Technical detail sits under each finding; the executive view is the same story without the packet-level evidence.

Executive view

  • Two material network changes this period; both have owners and verified follow-up.
  • Visibility gaps remain on the north warehouse aggregation path — called out explicitly, not hidden as zeros.
  • No after-hours engineer response is implied; alerting is automated around the clock, review is business hours.

Technical view — findings

Uplink utilisation crossed the planning threshold

Business impact
Intermittent queueing on the plant MES VLAN during shift change.
Evidence
Mirror-fed flow samples; LibreNMS interface counters; two linked change tickets.
Assigned action
Rebalance QoS for MES; schedule a second uplink before Q3 peak. · Owner: Plant network lead
Verified result
Peak utilisation back under threshold for five consecutive shifts.

STP reconvergence after an access-switch reboot

Business impact
Ninety seconds of loss on a packaging line camera VLAN.
Evidence
Syslog + SNMP traps; Zeek conn gap aligned to the reboot window.
Assigned action
Move cameras to a dedicated spanning-tree instance; document reboot procedure. · Owner: Controls engineering
Verified result
Controlled reboot drill completed with no camera VLAN loss.

Visibility gaps

  • No mirror session free on the north warehouse aggregation switch — wire visibility incomplete there.
  • Three access switches still not sending syslog copies to the edge node.

Missing data is listed here. It is never shown as a healthy zero.

Discuss a network assessmentRun the readiness checklist