COPS Monitoring/Alarmwatch Switchover Problems

What sort of issues are you having?

MD? What exactly the problem?

Alarmwatch was sold to COPS a few years ago, Alarmwatch worked off the Manitou platform and COPS has their own proprietary system. COPS just integrated all the accounts into its own proprietary system by "mapping" the information from one system to the other, and someone screwed up big time. 

-No one was getting open close reports 

-once they started to get them no names were associated with user number 

-supervised schedules were created for many of these accounts so everyone started getting calls at random times of day and night telling the customer either they weren't open or weren't closed. 

-Call lists were out of order and/or completely missing names 

-Still no control of our accounts online, everything must be manually sent to data entry 

-the line we use to monitor our land line based customers was completely down for a few day... Hundreds of accounts including some fire, with no monitoring. 

And I'm sure I'm forgetting a few things. 

Go to Rapid Response they assign a dedicated team when you switch over to them from another company. I was worried about the problems of switching a large number of accounts but it went very very smoothly. 

Very professionally run company with great technology and customer service

Conversions can be a nightmare when moving from one platform to another, event to the same platform because each CS can adapt to their own methods.

Reciever types, down to the handshake order cause missed signals, and the selection of the receiver output with SIA and Pulse Extended outputs.

Default types between the base signal information and the software that filter unknown events into actions.

Actions loaded into “notes” on one software become “instructions” in another.

It really takes the human touch and planning for it to go well, and “well” isn’t perfect.