Can someone help with deciphering these error messages?

I have read the definition but do not understand the cause or fix for the problem. I dont mean to sound stupid but a layman's terms for remediation would be nice.

When this rules fires it is due to an ESX server experiencing higher than expected latencies in performing I/O requests on the disks it is attached to. The latencies can happen in two areas:
Kernel: The time spent between the guest OS and the device.
Device: The time spent on the physical device. In VMware's words, "from the HBA to the platter."
The total latency that the rule assesses is the combined read and write latencies for both kernel and device.
In order to assess where the problem is taking place you should go to the vmExplorer dashboard for the ESX Host that triggered the rule. On this dashboard there is a tab for Storage information. In the table of physical disks you will need to look at the row for the disk that caused the rule to fire and then look at the values for Kernel and Device latency.

Hello Xafods,
If you are looking for additional help then my suggestion would be to create a support case rather than going back and forth here.
Regards

I have drilled down to when and where the latency happened. This is local disks on a single server. The information lists physical drive: naa...., Reads: 760.5, Read Rate: 354.6 KB/s, Writes: 981.6, Write Rate: 1.0 MB/s, Commands Issued 1.7 K, Command Aborts: 0.0, Bus Requests 0.0, Queue Latency: 600.0 us, Kernel Latency 646.8 us, Device Latency: 23.6

Full error message is: ESX Host xxx.xxx.xxx.xxx Total Command Latency (time taken during the collection interval to process a SCSI command issued by the Guest OS to the virtual machine. The sum of kernelLatency and deviceLatency) to extent: 48.00 have exceeded the threshold of 40 ms. Virtual machines on this ESX Host may be experiencing performance problems. Fires this rule when a VMWESXServerPhysicalDisk's Total Command Latency (time

Thank you for your help.