Native Integration
This integration requires a Class 3 License and an OpsLink Server (SaaS) or On-Premises Server (Enterprise). Please contact your account manager for more details.
Native Integration: Supported Features
- Alarms
- Health Alerts
- Get Config
Native Integration: Requirements
Version Requirements
The integration supports SecureBus as specified SecureBus Specification v3.
Specifically SB100 as the SecureBus controller and support for additional devices from the following list
- SB100 (configured as aux)
- SA2000 (FenceSecure)
- PS752 (PulseSecure) High and Low Voltage
- PS762 (PulseSecure) High Voltage Only
Hirsch has confirmed that future updates to the SecureBus compatible devices will remain backwards compatible to the existing integration.
Sureview has tested the integration against SecureBus Firmware Version 24856 (0x6118)
License Requirements
N/A - No manufacturer license required
Network Requirements
Include the default network requirements such as
| From | To | Port | Description |
| OpsLink Server / Sureview Device Server | SecureBus Controller (device 0) | 502 TCP | The Modbus Standard Port that the SB100 controller will be Listening on |
Note: the The Modbus Standard Port (502) is not configurable on the Securebus device
Important: SecureBus only supports one TCP connection at a time. When Sureview is connected the SecureBus Software will not be able to connect and any arming/disarming/configuring will need to be done using the on-site hardware panels.
You can force a sureview disconnection by invalidating the device details (such as changing the Port 502 in SureView device setup to 503)
Permission Requirements
N/A – The protocol has no built-in authentication, authorisation, or credential model. Any system with network access can communicate with Securebus. Security must therefore be enforced externally via network controls (e.g., segmentation, firewalls, IP whitelisting, and restricted routing) and physical access controls.
Native Integration: Device Setup
| Field | Value |
| Title | The user facing name of the system you are connecting to |
| Area | The Area/Site that the alarm points will be added to. |
| Type | Hatch Secure |
| OpsLink | The name of your connected OpsLink Server (SaaS only) |
| Host | The IP address of the SecureBus controller (device 0) - this will be an SB100 |
| Port |
502 The Modbus Standard Port that the SB100 controller will be Listening on |
| ExtraValue |
Recommended: leave blank
Optional: include "Control Master Events" alarms. This can cause a significant increase in alarm traffic. RaiseControl14Events=true; (default: false)
Optional: include all alarm technical detail. This can be useful for troubleshooting
(default: false) |
Important: After setting up a device for the first time, please wait at least 2 minutes before pressing "Get Configuration" for the internal device cache to refresh.
Native Integration: Alarm Setup
The Alarm points should be automatically populated by the Get Configuration feature with one alarm point per SecureBus Device connected to the connected SecureBus Controller
Once added the Sureview integration will immediately attempt to connect to the SecureBus system and will start receiving alarms. As long as the Securebus controller is accessible on the specified Host and Port then no additional device side configuration is necessary.
Sureview Alarm Point (Response) Fields
Note: Alarm Points are automatically populated by Get Configuration
| Field | Value |
| Title | Device [SecureBusDeviceID] ([DeviceType]) e..g. Device 0 (SB100 IO) Device 1 (SA2000) |
| Input1 | SecureBusDeviceID |
| Input2 | Not used, leave as "-1" |
| ExtraValue / ResponseCode | SecureBusDeviceID (automatically populated by Get Configuration) - used for matching the alarm |
Native Integration: Alarm Text
The alarm text in sureview follows this format:
Event Type - Device SecureBusDeviceID (DeviceType) - Type: Alarm Type [EventCode]
Examples
Zone A Pre-Alarm (Sounder) - Device 1 (SA2000) - Type: Alarm Acoustic Zone A Pre-Alarm [ZPAs]
Zone A Cut Alarm (Sounder) - Device 1 (SA2000) - Type: Alarm Acoustic Zone A Cut Alarm [ZCAs]
Enclosure Tamper (Sounder) - Device 1 (SA2000) - Type: Alarm Tamper [TAs]
Native Integration: Alarm Event Types
The SecureBus EventTypes are defined by the Securebus Event Log Structure "Log Event Table" EventLog/01.2016/V1
Important: The EventTypeCode and EventRestoreCode must not be changed as these are required to match exactly against the SecureBus specification.
Example of incoming alarms in SecureBus interface with the "Alarm Types" highlighted
Native Integration: Optional Alarm Event Types "Control Master Events"
If "RaiseControl14Events=true;" is added to the Device Setup ExtraValue the Securebus alarm receiver will include "Control Master Events" along with standard alarms. This can significantly increase the alarm trarffic received from SecureBus.
Comments
0 commentsPlease sign in to leave a comment.