- April 11, 2017
- Posted by: marlenedubois
- Category: CPR Training
A slight problem
The some other day our dispatch center called our computer office, saying “the network is actually slow”. For a large city police dispatch center, in which is actually not a Great thing. the idea wasn’t a busy day, although the dispatch people where still a bit annoyed at the problem. Jim, the dispatch super gave me the weird look.
“You know, in which is actually the same thing in which was happening last time, in addition to the idea was the network. the idea wasn’t a CAD problem”, Jim said.
“True, although I don’t see anything wrong. . .yet”. I said, a little worried although no panic yet.
I continued to look at the problem, thinking the idea was probably the server or database. Finally I began doing some more network tests.
“I think I found part of the problem. . .we are losing pings on the network. the idea’s network related, at least part of the idea, anyway.” I said. Suddenly the problem was mine in addition to my blood pressure went up.
I scrambled to find the problem. Using Ethereal, I captured some data on the CAD network vlan, nothing there. Then I captured data on the some other ports of the switch. Whoa, massive amounts of data flooding the network. Aha, in which must be what is actually slowing the idea down! although what was the idea, all in which UDP traffic? Soon the deluge of data stopped, although dispatch was not quite satisfied.
“What can we do to prevent in which next time?” the dispatch operator asked me.
“Well, we can discuss the idea, after I find out what the idea was. although there are some things we can do. One is actually to buy a dedicated network switch for CAD users, in addition to separate the CAD network.”
“How can we better isolate the problem next time? Jim asks, trying to find a resolution.
“Well, I can write up some things on how to better troubleshoot these issues. Well I suppose I could document some things to test next time you see in which.” I say, feeling a little better in which I actually know something about the problem today. What happened in which made in which incident different than any some other computer problem? The issue was the idea brought a metropolitan 911 dispatch center to a point where they could almost not dispatch calls. A bad thing!
People who understand technology realize there are many parts in which make up our complex machines in addition to systems we use. Look at a helicopter, for example in addition to compare the idea to a large the idea system. Both have many interconnected, single parts in which, if they fail, the system can be crippled, unable to perform the mission at hand. System engineers, technicians, in addition to the operators in which use the equipment all have various levels of knowledge on how the idea systems work. The question is actually, what level, or what training can give users in addition to operators enough information to help diagnose problems?
As a general rule, ignoring some theoretical discussion, technical training can be defined as risk = complexity divided by training. As a formula, R =C/T, meaning the more training, the less risk. in addition to the more complexity, the more exposed risk. Some engineers will argue in which they can build in complexity in addition to redundancy in which minimizes risk. I’d argue in which. The general tendency on many systems is actually to build the idea in which only incorporates a “red warning light” type signal in which works similar to a car warning engine light. Instead of having all 5 different gauges, the output is actually summed to one red light. by operational point of view, in which makes the idea easier for operators or technicians to be alerted in which something is actually wrong, meaning they have less complexity, less objects to keep track of. There is actually a downside though. in which makes the idea difficult to identify what exactly is actually causing the problem. As a manager of technology, you need to keep aware of dumbing-down your staff into just “red light watchers”.
The trend to simply complex technology is actually going to continue. In my humble opinion, such simplification does not mean you can skimp on training. Operational expenditures (opex) will climb if your staff does not understand how to troubleshoot complex systems. Saving money on theory of operation, in addition to diagnosis will end up costing you in downtime.
The take away lesson by in which: Make sure your staff can diagnose those “red lights” quickly in addition to effectively. Examine the downtime costs versus training costs to minimize service outages.