Alarm
Alarms are generated in the Witness software as a result of certain rules being broken or conditions being met. At the most simple level this may a target moving into a specific area but could also be a result of a set of more sophisticated inter-dependant rules being broken. Alarms are uniquely identified and can be associated directly with one or more tracks through the alarm information which is carried by each track.
Status
The primary status message is intended to provide health and status data for all the sensors. In addition status information can be provided about the software system which includes the tracking software.
Camera
A camera refers to a PTZ camera which is being used to track targets identified as threats by the software system. These cameras rely on the Navtech software telling them where to move. This can be done either directly or via a third party camera control application.
Subscriber
A subscriber is a system which connects to the Navtech software to receive data. Although the name suggests a formal method of subscription, at this stage this is not required. A subscriber is a device / system which simply connects to the relevant network point being used by the Navtech software to broadcast and receive data.
Report
A report is a XML document being transmitted or received by the Navtech software. This ICD will describe the various different reports that the software supports. Each report will support its own specification so a status report will take a different format to a track report.
Command
Commands are messages being passed into the Witness system. Commands offer the ability to request additional data or change the behaviour of the Witness software. Typically a command message would always elicit a response message, either containing the requested data or confirmation of whether the command action has been successfully received.
Messaging Transport
This document does not cover the specifics of the messaging transport mechanism. It is assumed that a suitable network link is available between the Navtech system and third-party. The network may implement security and encryption but these facilities remain independent of this ICD and therefore are not discussed. Further information should be sought from Navtech Radar concerning the various methods for communicating with the different software systems.
XSD Files
XML is plain text based data exchange protocol. It is widely supported in most modern development languages and tools. There are XSD files to support the protocol which can be used to validate incoming and outgoing messages. These can be found here. Navtech Radar recommends the use of the XSD in order to check the XML format. The Witness system uses the XSD and therefore will reject incorrectly formatted XML data.
Technical Skill Requirements
The use of this protocol will require a reasonable understanding of XML and some basic knowledge on developing a simple TCP or UDP client to decode the message structure and extract the XML. This is not difficult and there are plenty of examples online, however we would not recommend a non-software developer undertake this work.
Related information
-
ICD-001 Track Filter Command (Witness 4.0)
-
ICD-001 Acknowledge Alarm Command (Witness 4.0)
-
ICD-001 Request Status Command (Witness 4.0)
-
ICD-001 Detection Command (Witness 4.0)
-
ICD-001 Update Entity Command (Witness 4.0)
-
ICD-001 System Profile Command (Witness 4.0)
-
ICD-001 External Trigger Command (Witness 4.0)
-
ICD-001 Plugin (Witness 4.0)
-
ICD-001 Command Reply (Witness 4.0)
-
ICD-001 Camera Command (Witness 4.0)
-
ICD-001 Track Command (Witness 4.0)
-
ICD-001 Tracker Command (Witness 4.0)
-
ICD-001 Commands (Witness 4.0)
-
ICD-001 Change Log (Witness 4.0)
-
ICD-001 Classification Report (Witness 4.0)