Summary

The Honeywell ProWatch Access Control / Alarm Receiver Database integration is designed to seamlessly integrate with both Enterprise and SaaS environments. This document provides detailed information on the setup, configuration, and troubleshooting of this integration.

Information

• Manufacturer: Honeywell
• Product: ProWatch
• Type: Access Control / Alarm Receiver

Supported Features

• Output Control
• Get Config
• Sync

Prerequisites

• Sureview.Devices.dll Version 1.0.14

Setup

Configuration

The below values can be entered into the ExtraValue field in Sureview to provide further customisation. Each setting should be separated by a semi-colon (;)

Sureview Configuration

There are two different ways of adding ProWatch devices into Sureview

Site Sync

First add the Prowatch server details to the Sync System.

To add a ProWatch site to Sureview:

1. Create a Site Sync Entry for your Sureview site providing:

2. The sync will import all of the panels from the ProWatch site and events from those panels will be raised into the site.

Get Config

To add a single panel into Sureview:

1. Add a new device to your Sureview site providing:

2.Get Config will import all of the devices from the specified panel and all of the related events will be raised into the site.

Sync filtering options

The Honeywell ProWatch Database Integration has the following filtering options available for Sync and Get config. Multiple filters can be used together

Site Id

This will get all panels for the specified site
For example an identifer\Extra Value of Generic
Will sync for all panels, relays, and alarms with the site "Generic"

However, if any additional filters are being used then the site id must be specified in the following format siteid="Generic"

Panel Id

Instead of using a SiteID it is possible to get just a specified Panel
For example : panelid="Generic::010200"

Panel Filter

It is also possible to apply wildcard filtering for a panel's Description by specifying a contains, starts with, or ends with filter.

Contains filter

For example an identifer\Extra Value of panelfilter="*Panel 1*"
Will get all panels that contain a description of Panel 1

Starts With filter

For example : panelfilter="Panel*"
Will get all panels that start with Panel

Ends With filter

For example : panelfilter="*1"
Will get all panels that end with 1

Regex filter

When using a Regex Filter the pattern MUST start with ^ or it will fall back to the wildcard method.

For example : panelfilter="^Panel (1|2)"
Will get all panels with the description of Panel 1 or Panel 2

Door Filter

It is also possible to apply wildcard filtering for a Logical Device's Description by specifying a contains, starts with, or ends with filter.

Contains filter

For example an identifer\Extra Value of doorfilter ="*Entrance 1*"
Will get all the panels that contain the relays and alarms that use a Logical Device with a Description that contains Entrance 1

Starts With filter

For example : doorfilter="Entrance*"
Will get all the panels that contain the relays and alarms that use a Logical Device with a Description that starts with Entrance

Ends With filter

For example : doorfilter="*1"
Will get all the panels that contain the relays and alarms that use a Logical Device with a Description that ends with 1

Regex filter

For example : doorfilter="^Entrance (1|2)"
Will get all Logical Devices with the description of Entrance 1 or Entrance 2

Processes

Note all processes below require the IgnoreUnmatchedPanelAlarms setting to be enabled so that only ProWatch events that match a panel in Sureview are raised in Sureview.

Alarm Acknowledgements in ProWatch

The Sureview service can be set to acknowledge alarms that it receives and matches to an Sureview site so they are cleared from the ProWatch software. This removes the row in the UNACK_AL table and only occurs if the alarm matches a device (panel) in Sureview - any panels that are not in Sureview will not have their alarms acknowledged inside ProWatch (i.e. you can bring a few sites at a time over into Sureview, and only alarms from those sites will be removed from ProWatch).

NOTE: Due to a limitation of the ProWatch software, alarms that are cleared by Sureview will not be removed from already running ProWatch Alarm Monitor clients if the user has the site in their routing group, so the alarms will still show in the ProWatch software to those users.

To overcome this, when a site is live in Sureview you must:

1. Modify the ProWatch user alarm routing rules so that no ProWatch users see alarms from this site.
2. Clear out any existing alarms so there are no alarms left in ProWatch for the site.

Note: all the events in ProWatch will still be shown in the Event Log window of the ProWatch software so you can still watch all events being received regardless of Sureview clearing those that match sites it has from the alarm queue.

Adding a new site

1. Add the site and its Panels in ProWatch and perform all of your alarm tests in ProWatch
2. When the testing is complete, add the Sync Entry to the Sureview site which will cause the Panels to be imported and events to start being received.
3. Follow the steps in the "Alarm Clearing in ProWatch" above to stop alarms from being shown to ProWatch users

Adding a new panel to an existing site

1. Disable the sync entry in the Sureview site so panels are no longer imported for that site
2. Add the panel to ProWatch and perform all of your alarm tests in ProWatch
3. When the testing is complete, re-enable the Sync Entry in Sureview which will cause the new panel to be imported and events to start being received.
4. Follow the steps in the "Alarm Clearing in ProWatch" above to stop alarms from being shown to ProWatch users

Adding a new reader to an existing site

As the panel already exists in Sureview it will mean the test events are raised into Sureview and any alarms cleared out of the ProWatch alarm queue automatically.

In order to test the alarms for the new reader you will need to either set the site On Test in Sureview for the duration of the test period or disarm the alarm points in Sureview for the duration of the test period so the test events do not interfere with operators (note you can still watch the ProWatch Event Log to see the events coming in from the new reader regardless of any alarms being cleared as described in "Alarm Clearing in ProWatch" above).

Troubleshooting

Door Control Does Not Work

If your ProWatch server is 64-bit ensure that you have completed the steps explained in Honeywell's "64 bit Pro-Watch Servers" guide (attached to this page), including:

• Installing Microsoft's Visual C++ 2005 Runtime
• Installing Microsoft's "SQL 2005 Backwards Compatibility Pack"
• Adding the "CommServerName" registry entry to "HKLM\Software\Honeywell\ProWatch\Directories"
• Editing the C:\Program Files (x86)\ProWatch\Scripts\MICXP.sql file to point at the MICXP64.dll file instead of the MICXP.dll file and then
  running it against the ProWatch database.

Port 6000 in use by "system"

If you are attempting to start the HoneywellProwatchDBReceiver service and it starts and stops there are likely two causes:

• If you used the ProwatchDBTest.exe to test the connection to the ProWatch DB.
  In task manager:
  • Make sure the application for dbtest tool is closed.
  • Make sure the process is also closed.