Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsGeneralRural LivingHome AutomationSecurity AlarmsConstructionRepairPlumbingCleaningPest ControlLawn and Garden

Homeowner Forum / Security Alarms / March 2006



Tip: Looking for answers? Try searching our database.

Average Response Time

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Joe Lucia - 09 Mar 2006 06:56 GMT
Does anyone here use COPS Monitoring?

We have been trying to figure out how they are calculating their
"Average Response Time" of 12.55 seconds.  They say "Our response time
is audited by an independent firm." (apparently on a yearly basis) but
doesn't say what Firm.  They did list the name of the auditor a while
ago but when we researched it we couldn't find that it acually existed
anywhere.

I'd like to contact that Firm to find out what the criteria is so I can
provide a fair and honest comparison to our own response time.  Wouldn't
you all like to see a comparison to know if 12.55 seconds is really an
acceptable "response" time or not?  Does "response" mean an actual
operator picking up the phone and calling to verify or dispatch on a
signal, or does it mean the operator simply "picked-up" the signal from
the pending alarm list?  Maybe you COPS dealers could request the name
of that firm from COPS for me?  I'd be VERY surprised if you can get a
straight answer from anyone, but there is no reason they shouldn't know
and tell you since they make such a big deal of it.  Even if you are Not
a COPS dealer, call them and ask.  Inquiring minds want to know.
Okitoki - 09 Mar 2006 08:47 GMT
Dear Lucia,

In Monitoring (whether it be COPS or someone else) there are two issues
that can give information on the performance of the CMS.

The first issue is the Responce time. This is the time it takes for the
opperator to just pick up the alarm. So when an alarm drops into the
window of the automation to the time that the opperator picks up the
the event is the responce time. Some people may consider that 12.55
seconds is too long... "What are they waiting for?". But considering
the fact that the opperator will have many more alarms (for example
late closing or early opening), this responce time (if it is true) is
actually good.

The second issue is the action time. This is the time it takes from
receiving the signal to the time the operator clicks on "save event".
This time gives you the idea of how long it takes for the operator to
complete all listed calls (or completing the "to do" list) and finally
click on save. So COPS must also inform of their action time. Because
just responding to an alarm and pending it does not give true values.

I have been trying to find a mathematical relation between these two
figures and have found some for some countries. Unfortunately the US is
not on my list as the service type differs from CMS to CMS.

I hope this gives you some idea on the situation. Good luck.
Joe Lucia - 09 Mar 2006 16:04 GMT
My thoughts exactly.  Obviously it must be the op-pickup-time to be a
12.55 second response, it does take humans a few more seconds to
comprehend what they are looking at before blindly dialing the customer.

I also wonder if the events are auto-assigned to the available operators
as they come in, which drastically reduces the "response" time but
doesn't mean the Operator has actually "responded", just his workstation
did.  I believe larger monitoring centers with a lot of operators
typically auto-assign events.  We don't, all operators see and hear the
pending alarms list as events hit.  It's up to the operators to
get-next-available signal.  We don't have enough operators to warrant
auto-assigning.  If I auto-assigned events it looks like it would
happen, on average, within about 5 seconds (it takes on average less
then 4 seconds from the time the receiver spits out the signal until it
hits an operators screen).

Most often, if I set my alarm off at home, by the time I walk to the
keypad to shut it off and head back to the phone to call the monitoring
center, it's too late, my phone is ringing, they are already calling
me.  That's an acceptable response time.  As mentioned, there is always
the exception when all operators are busy.  Our operators also try to
watch the pending alarms list while handling events, if a high-priority
event comes in (fire, medical, panic) they will typically stop calling
RP's on their current event and grab the high-priority event.  It's
amazing how efficiently the system works with a few seasoned operators.  
It doesn't matter how fast the system is if the operators are being lazy
or if the dealer puts a ton of special-instruction messages on the
account that the operator must read before they can actually respond to
it.  We try to eliminate these types of messages and script it into the
event actions for the operator so they just
"follow-the-yellow-brick-road" as we say.  Less interpretation is
required, hence, less mistakes.

>Dear Lucia,
>
[quoted text clipped - 24 lines]
>
>  
Mark Leuck - 10 Mar 2006 00:41 GMT
That is the time between getting the signal and calling out, and thats
pretty good

> Does anyone here use COPS Monitoring?
>
[quoted text clipped - 16 lines]
> and tell you since they make such a big deal of it.  Even if you are Not
> a COPS dealer, call them and ask.  Inquiring minds want to know.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2012 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.