Contents
Overview
IIS Integration Configuration
Reverse Commands Media Gateway Configuration
Event Codes and Event Mapping
Action Pattern
Overview
This document gives a look at the Manitou to Honeywell CLSS integration. The integration uses a web app called Integration. This will be the portal to pass information to and from Honeywell, CLSS integrated with setup in the Media Gateway via HTTP type Universal Connector. Operators can send a reverse command within an alarm that will trigger an event to be delivered to CLSS or a reverse command to dispatch to PSAP.
IIS Integration Configuration
The integration will be set up via Cloud Services. However, the customer will need to get and have available for setup the following:
- CLSS Contact Phone (Central Station PSAP would call back if needed)
- CLSS External ID
- CLSS API ID
- CLSS API Secret
- CLSS ClientID
- CLSS Client Secret
- The URL:Port for MGW
- What signal codes do they want to use
Reverse Commands
There will need to be two reverse commands created under the Monitoring Station record. One reverse command will be used to deliver the alarm to CLSS. The other reverse command will be used to dispatch the alarm through PSAP.
The reverse command to deliver the alarm to CLSS needs to look like this:
Details:
The reverse command to dispatch through PSAP needs to look like this:
Details:
The details are the same with the exception of the Fixed Value for SendToECC is set to "true".
Media Gateway Configuration
Data Packet
Create a Data Packet within the MG
- The address will be provided by the Cloud team based on their setup. The Packet name will need to match the Packet Value in the reverse command.
- The tenantID will be different for each Central Station.
- The username and password can be coordinated with BOLD to protect the message channel. The customer can select one and let us know or we can choose one for them.
Data Mapping
Create the following Data Mapping:
Return to Contents
Connectors
You will need to create two connectors. One for outgoing data and one for incoming data.
Create the following HTTP connector for outgoing data:
The outgoing HTTP connector will need to have an HTTP Header:
Create the following HTTP connector for incoming responses from CLSS:
Line Drivers
Two Line Drivers will need to be created. One for outgoing data and one for incoming.
Incoming Line Driver:
Outgoing Line Driver:
Event Codes and Event Mapping
A series of Event Codes will need to be created for each possible response sent by CLSS.
"REQUESTED": "HRQD",
"CHAT": "HCHT",
"DECLINED": "HDCD",
"ACCEPTED": "HACC",
"TIMEOUT": "HTOT",
"DIGITAL": "HDGT",
"SUPPLEMENTAL": "HSUP"
"NOTCOVERED": "HNCV",
"SENT": "HSNT"
The SIA codes in quotes are an example of what can be created as Event Codes. After the Event Codes are entered in Supervisor Workstation they also will need to be entered in Event Mapping for SIA. The decided-upon Event Codes will need to be noted and given to the Cloud team to update the appseting file for CLSS.
Action Pattern
This is an example of an Action Pattern that can be used to process a CLSS alarm.
- If the response is Sent, Digital, and/or Accepted the alarm can be handled and closed.
- If the response is that the customer is Supplemental or No Coverage, the Operator would need to contact the authority by phone.
- If the response was Declined or Timeout the original alarm can be closed and a new alarm escalated with an action pattern for manual processing, including contacting the Authority by phone.
