Overview
When Witness generates events, such as alarms, or processes targets, it passes all this information to the Integration Manager. The Integration Manager is then able to use loaded plugins such as ICD-001 to convert this information into a suitable data format to send to external systems.
The data is transmitted as the events occur, leading to near-real time reporting.
Installing the ICD-001 Plugin
Witness supports integration with many different types of external systems through the use of plugins. These are stand-alone software libraries which are dynamically loaded by the Integration Manager and contain code which knows how to convert the Witness data into the required format for the external system. Navtech Radar can easily develop bespoke plugins to interface with a specific type of equipment or application, however ICD-001 has been developed to provide a comprehensive communication protocol which is based on open standards in order to make it as easy as possible to integrate with a large number of different systems.
The ICD-001 plugin file is entitled Tungsten.Integration.ICD001Highways.Plugin.dll and must be present in the Witness Plugin folder which is inside the main application folder.
| Tip |
|---|
The plugin can be selected during setup and will automatically be installed in the correct location. |
When installing Witness, in the Choose Components page of the Witness Setup wizard, open Integration Plugin options and select ICD001:
Configuring the ICD-001 Plugin
When the plugin is installed and licensed, a plugin configuration with default settings is automatically generated.The settings can be viewed and edited by enabling the Config Function, then selecting the plugin in Integration Configurations, within the Configuration Tree. Configuration settings will then be available in the Configuration Panel.
| Info |
|---|
Once you have made changes to the plugin configuration and committed the changes by saving, the plugin will automatically restart itself based on the new configuration. Note that any connections to 3rd party systems will be dropped during this restart. |
The setting options are as follows:
Enable Plugin: when not enabled, the plugin will not start up. If the plugin is already running, disabling the plugin will cause it to stop.
Plugin Name: name of the plugin within the Witness UI.
Track Output Mode:
None: No tracks reports are sent.
Broken Rule: Report all tracks which have broken rules, regardless of whether this resulted in an alarm.
Alarm Only: Report only tracks which have broken rules that results in an active alarm.
All: Reports all tracks.
Buffer Tracks: enable this for tracks to be buffered and sent in batches. This can optimise network load but has the drawback of not sending data in real time. The Track Buffer Time setting specifies how often the buffered tracks are sent.
Send Status: enable this for status reports to be sent at a regular interval based on the Status Report Time.
Send Alarm: enable this for Alarm reports to be sent.
Send Size Classification Report: enable this for Size Classification Reports to be sent.
Pump Timer (s): Default: 0.5 s.
Track Buffer Timer (s): period of time between each batch of tracks being sent of Buffer Tracks is enabled. Default: 1 s.
Heartbeat Timer (s): period of time between each heartbeat being sent to every connected client. Default: 10 s.
Status Report Timer (s): period between each status report being sent. Default: 10 s.
Monitor Client Health: enable for the plugin to monitor the health of client connections. If a client is either not connected or connected but not sending heartbeats, then an alarm will be raised in Witness.
Related information
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|