Running a CURWB of Private 5G network requires close monitoring to ensure you get the most from your investmentent.

 

For many ports, Wi‑Fi alone is no longer sufficient.

There are two key technologies which are highly suited to the automated vehicle use case - these are Cisco CURWB and Private 5G.

Both are highly suitable: Cisco CURWB is cheaper to deploy, but Private 5G has protected spectrum - but is much more expensive to deploy.

Cisco Private 5G provides deterministic performance, predictable latency, and stronger mobility management — but only if the network itself is continuously monitored and operationally visible.

This is where Splunk plays a critical role.

 

With the end users in mind, let's take a look at how what their use cases might be, in the next section below.

 

Modern automated vehicles are used to move containers around a port. The network needs monitoring, but the vehicle can send telemetry also. With no driver in the vehicle remote monitoring is critical in spotting issues early.

In automated port environments, operational teams are often alerted to a vehicle problem first:

- A container carrier slows unexpectedly
- A vehicle stops mid‑route
- Safety systems trigger failsafes

However, the root cause is frequently network‑related, not mechanical:

- Latency spikes impacting control commands
- Packet loss disrupting telemetry streams
- Weak radio conditions causing session instability

 

 Without unified visibility across vehicle telemetry and Private 5G performance, teams are left guessing — switching between operational systems, network dashboards, and vendor tools while production slows. 

 In this rendered dashboard below, we've drawn up an image showing the sort of monitoring that might be suitable for a port and the automated vehicles:

 

Rather than generic uptime indicators, the dashboard focuses on 5G KPIs that directly affect autonomous vehicle behaviour.

The reason Splunk works well in the Private 5G use case, is that it is often a mix of manufacturers in use. For example in the case of Cisco Private 5G, it uses Cisco servers and software, but a Radio Access Network (RAN) from a third party (eg Nokia and others).

Splunk can collate the sources of data and correlate across them, such as SNMP, syslog, telemetry (and this will be across multiple manufacturers).

The key metrics that we need to track for Private 5G are:

• • Network Latency
  • Packet Loss
  • Signal Strength and Radio Health 

Let's take a look at why each of these are important - then a sample dashboard that might be used.

Network Latency

Low network latency is critical for:

- Real‑time steering and movement commands
- Collision avoidance systems
- Remote supervision and exception handling 

The dashboard continuously tracks:

- Average latency across the Private 5G network
- Latency spikes tied to individual vehicles
- Threshold breaches that coincide with vehicle slowdowns

 

Packet loss

Packet loss can be more damaging than latency, especially for:

• Continuous telemetry streams
• Video or sensor data used by control systems
• Command acknowledgements

The Splunk view highlights:

• Real‑time packet loss percentage
• Deviation from normal operating thresholds
• Which vehicles are affected first

Signal strength and radio health

Private 5G environments still rely on radio conditions being healthy:

• Signal strength
• Uplink throughput
• Vehicle location

This allows teams to quickly identify whether issues stem from:

• Coverage gaps
• Temporary interference
• Mobility handover challenges as vehicles move through the port

The sample render below is just an example how we might pull these metrics into a dashboard and monitor the various aspects of the network:

   Sample Render of Splunk Glass Table View   

ASSOCIATED BLOGS:

• Discover Connected Devices with Splunk
• Warehouse Wi-Fi: Best Practice
•  Cisco DNA Spaces Applications 

---

The Splunk dashboards are about Operational insight, not just alarms, so the dashboard doesn’t simply indicate that something is wrong — it explains why.

In a busy port with lots of moving vehicles and devices any time there's an issue, there's a key question: Is this a vehicle issue, or a 5G network issue?

The key point of the Splunk dashboards is to answer this question as quickly as possible. The real ideal is to allow the shift from reactive troubleshooting to predictive operations.

With Splunk, we can offer:

• Real‑time visibility across vehicles and network performance
• Actionable intelligence aligned to operational outcomes
• A single source of truth for OT, network, and operations teams

If you’d like to chat over all things Splunk, or have any Splunk projects we could help you with, drop us a line at sales@iptel.com.au