AID System Description 20170420 EB

Traffic Management
& Video Processing

How FLIR ITS video detection solutions help you
manage and control road traffic
Contents
1 Scope ............................................................................................................. 4
2 Introduction: video detection for traffic control .............................................. 5
3 Product overview ........................................................................................... 8
VIP – Video Image Processor boards .................................................................................................. 8

TrafiBot HD – Box camera with integrated detection ......................................................................... 8
ITS series AID – Thermal camera with integrated detection ............................................................... 9
ITS series Dual AID – Dual vision camera with integrated detection................................................... 9
Detector overview ........................................................................................................................... 10
Flux – Management software .......................................................................................................... 12
4 Operation of the AID system .......................................................................... 13
System architecture overview .......................................................................................................... 13

Hardware components of the AID system ........................................................................................ 15
VIP detection and compression modules................................................................. 15
VIP housing............................................................................................................... 15
VIP-T optional expansion module ............................................................................ 17
AID functional description ............................................................................................................... 18
Automatic Incident Detection .................................................................................. 18
Traffic Monitoring and Traffic Data Collection......................................................... 18
Presence Detection .................................................................................................. 19
Technical monitoring ............................................................................................... 19
Input-output management ...................................................................................... 19
Video compression ................................................................................................... 20
Software components of the AID system ......................................................................................... 23
TCT – Traficon Configuration Tool............................................................................ 23
AID Management System: Flux ................................................................................ 26
5 System Redundancy....................................................................................... 33
Camera and detector unit level redundancy .................................................................................... 33
2
Redundancy based on detection zones ................................................................... 33
Detector redundancy ............................................................................................... 33
Power supply redundancy........................................................................................ 33
Flux scaling and redundancy ............................................................................................................ 34
Scaling ...................................................................................................................... 34
Redundancy ............................................................................................................. 34
6 Services ......................................................................................................... 35
7 Camera considerations .................................................................................. 36
Technical specifications of the camera ............................................................................................. 36

Position of the camera ..................................................................................................................... 37
Mounting of the camera .................................................................................................................. 39
Addendum: About Traficon - FLIR ITS ................................................................... 40
About 40
History 40
Company mission & objectives ........................................................................................................ 41
References ....................................................................................................................................... 41
Abbreviations and acronyms ................................................................................ 43
3
1 Scope
This document describes the different components, implementation and operation of FLIR Video Image Processing
solutions for road-, tunnel- and urban traffic applications. Specifically, this document describes the functioning and
deployment of Automatic Incident Detection (AID) systems.
FLIR Intelligent Transportation Systems tel +32 (0)56 37 22 00 VAT BE 0835 731 610
Hospitaalweg 1b fax +32 (0)56 37 21 96
B-8510 Marke, Belgium flir@flir.com
www.flir.com
2 Introduction: video detection for traffic
control
All over the world, major roads suffer from highly increasing traffic density. This leads to daily accidents, a larger risk
for secondary accidents and long traffic jams. Fast-developing urban regions have a need for information on traffic
patterns, to take well-founded decisions about new road infrastructure and improvements to the existing
infrastructure. Today, traffic managers worldwide have a need for state-of-the-art intelligent traffic solutions, both for
statistics purposes as well as for safety. Traffic managers are now looking for more optimized and improved Intelligent
Transportation Systems (ITS) technology.
Traditionally, basic detection systems (such as loops and radar) provide ample information to direct traffic flows and
assemble statistics but their information is limited. Nowadays, increasing traffic volume and complexity have created a
need for more optimized systems: video detection systems.
First of all, video detection handles both traffic data collection and automatic incident detection (AID). Further, video
incident detection shows a high detection rate, a short time to detect, fast visual incident verification and a low false
alarm rate. These characteristics make video extremely useful for a wide range of applications such as incident
management, congestion monitoring, ramp metering, hard shoulder monitoring, etc.
FLIR ITS video detection technology provides real-time data and image information for optimal traffic control and fast
accurate incident detection.
A key component in a FLIR ITS detection system is the smart FLIR ITS camera, or the VIP (= Video Image Processor), a
detector board on which several types of detection software is running simultaneously. The VIP modules and smart
cameras provide traffic monitoring, automatic incident detection and traffic data collection functionality for indoor
and outdoor applications.
The video detection system supports the operators in real-time by automatically generating a wide range of alarms,
data and visual information.
The video signal from any camera monitoring the traffic is used as an input for the detection module. VIP modules
analyze these video images of the cameras to generate traffic information useful for traffic control and management.
The Smart FLIR ITS camera is a high-end camera with built-in detection software. This further reduces overall system
complexity and wiring requirements.
The outcome of this video image processing process is a wide range of traffic data such as volume, speed, occupancy
… or an event notification in case an incident is detected. A clear definition of an incident is: “each event that lowers
the road capacity and/or each event that endangers the safety on the road and its direct environment disrupting the
normal traffic flow such as a stopped vehicle, wrong way driver, speed drop, queue, fallen objects …”
www.flir.com
Detection of stopped vehicle on Detection of fallen object in tunnel
highway at night in bad weather
Detection of wrong way driver

Detection of smoke in a tunnel
Detection of a pedestrian on a highway. Video Outdoor data collection on highway: speed,

detection can distinct vehicles, persons and occupancy, count, classification
objects (lost cargo, debris)
Thermal detection of stopped vehicles Thermal fire detection in tunnels

on bridges
On a dedicated server at the control centre, the FLIR ITS Management Software, called “Flux”, monitors the video
detection system.
Flux processes all Ethernet TCP/IP communication from the detectors and provides database storage of data, events,
images and incident video recordings. Additionally, Flux has options for use as video recorder, streaming video server
and video wall controller.
www.flir.com
Video detection system architecture
A typical video detection installation consists of a number of cameras installed along the (road/tunnel/bridge) section
that needs surveillance. FLIR ITS smart cameras or Video Image Processing (VIP) modules analyze the video signal.
These video signals can be either analogue (with VIP-T modules) or IP network camera streams (with VIP-IP) or
cameras with integrated detection software (TrafiBot HD/ITS-series AID).
The compressed images and video of each detector or smart camera, together with all traffic data and events are
transferred over Ethernet TCP/IP to the Flux server. Flux communicates with the overall traffic management server to
make sure that all traffic data, alarms and events are available within the control centre. The operator can now
retrieve specific video sequences, data or alarm information on his workstation.
Flux user interface
www.flir.com
3 Product overview
VIP – Video Image Processor boards
VIP boards are modular boards that take a standard camera signal as input, analyze the video in real-time and deliver
detection results in the form of alarms, data, video sequences, images and/or driving physical outputs.
For classic cameras, providing an analogue PAL or NTSC signal, the VIP-T and VIP-TX are available. The VIP-T provides
basic MPEG-4 video streaming while the VIP-TX has more advanced multi-codec triple encoding on board.
For IP cameras, the VIP-IP or VIP-HD product is available, processing an MPEG-4 or H.264 compressed video stream
over the network. All boards are multifunctional, serving a variety of traffic applications (automatic incident detection,
traffic data collection, presence detection)
VIP-T detector VIP-IP detector VIP-TX detector VIP-HD detector
8-channel VIP-T rack single channel VIP-IP or VIP-HD box
The VIP boards are placed in 19” rack-mountable enclosures or in a single channel stand-alone box to fit a broad range
of different deployment requirements.
All VIP boards interface over IP with a central management software that stores, visualizes and reports all events &
data to the operator or another third-party traffic management system.
TrafiBot HD – Box camera with integrated detection

The TrafiBot HD combines incident detection algorithms with advanced camera optics and powerful processing
technology in a single housing.
TrafiBot HD camera with integrated AID
This all-in-one solution is optimized and designed for traffic monitoring and incident detection from the bottom up. It
features very good low light performance and sufficient processing power to execute all AID detection algorithms
simultaneously. Its integrated nature allows for easy integration and lower network complexity.
www.flir.com
The TrafiBot HD exists in two versions: one with standard RJ45 Ethernet connection and one with Small Form-Factor
Pluggable (SFP) slot interface. The latter suits a range of SFP modules to support direct fibre optic interfacing for
various distances or an Ethernet over Coax (ECO) plug that allow the (re-)use of conventional coax cabling.
ITS series AID – Thermal camera with integrated detection

FLIR ITS-Series AID cameras combine best-in-class thermal imaging technology with advanced video analytics to
provide a complete solution for automatic incident detection, data collection and early fire detection.
ITS series AID camera with integrated AID
This all-in-one solution is optimized and designed for traffic monitoring and incident detection from the bottom up.
Its integrated nature allows for easy integration and lower network complexity.
The FLIR ITS-Series AID thermal camera can measure the temperature of any object in its field of view. This unique
capability allows detecting fires at an early stage over the full detection range.
Thermal cameras can penetrate smoke. This enhanced visibility can help guide emergency personnel to locate people
inside the tunnel and save lives in critical situations.
ITS series Dual AID – Dual vision camera with integrated detection
FLIR ITS-Series DUAL AID cameras combine best-in-class thermal imaging technology with advanced video analytics to
provide a complete solution for automatic incident detection, data collection and early fire detection.
ITS series Dual AID camera with integrated AID
This all-in-one solution is optimized and designed for traffic monitoring and incident detection from the bottom up.
Its integrated nature allows for easy integration and lower network complexity.
The FLIR ITS-Series Dual AID thermal camera can measure the temperature of any object in its field of view. This
unique capability allows detecting fires at an early stage over the full detection range.
Thermal cameras can penetrate smoke. This enhanced visibility can help guide emergency personnel to locate people
inside the tunnel and save lives in critical situations. All versions are equipped with a daylight/low light camera with a
motorized optical zoom. The video output of the thermal imaging and daylight/low light camera are simultaneously
available.
www.flir.com
Detector overview
The tables below summarizes and compares the different detector and smart camera solutions.
model VIP-T VIP-IP VIP-TX VIP- HD

description AID module for analogue AID module for IP encoder with embedded AID module for Full HD IP
cameras cameras AID cameras
video input analogue PAL / NTSC IP video: VGA, 4CIF or D1 analogue PAL / NTSC IP video: up to 1920 x
H.264 @ min 2 Mbps 1080
or MPEG-4 @ min 4 H.264 or MPEG-4
Mbps
encoding format MPEG-4 H.264, MPEG-4, MJPEG H.264, MPEG-4, MPEG-2, H.264, MPEG-4, MJPEG
MJPEG
max. resolution 4CIF @ 30 fps D1 @ 30 fps D1 @ 30 fps 1920 x 1080 @ 30fps
multi-streaming single single triple streaming: 1 x dual streaming
MPEG-4 H.264 or MPEG-4 or H.264 (BP) H.264 or MPEG-4 or
MJPEG + 2 x MJPEG or MPEG MJPEG
max streams 1 max 4 unicast or unicast and/or multicast, max 5 unicast or
multicast max 20 multicast
audio no no 2 full duplex stereo no
boards per rack 4 (1/2 19" rack) or 8 (19" 4 (1/2 19" rack) or 8 (19" 11 (19" rack) 8 (19" rack)
rack) rack)
power 4W < 4W < 5W < 8W
stand-alone box, 24V DC (+/- 15%) box, 24 V DC (+/- 15%) box, 11 to 19V DC box, 24 V DC (+/- 15%)
form
connector type 10/100 Mbps RJ45 10/100 Mbps RJ45 10/100 Mbps RJ45 10/100 Mbps RJ45
SFP for fibre or IP over
coax (ECO)
digital inputs 1 1 2 1
digital outputs 2 (+ optional 8) 2 2 2
data no no RS232 + RS422/485 No
PTZ control no no yes Yes
communication SNMP ONVIF profile S, NTCIP, ONVIF, SNMP
standards SNMP
operating temp -34 °C to +74 °C -34 °C to +74 °C -40 °C to +74 °C -34 °C to +74 °C
-29 °F to 165 °F -29 °F to 165 °F -40 °F to +165 °F -29 °F to 165 °F
MTBF 200.000 hrs 200.000 hrs > 200.000 hrs 200.000 hrs
other features AID overlay AID overlay AID + customizable AID overlay
overlay
vehicle presence video motion detection
detection
image monitor (quality
measurement)
www.flir.com
model Trafibot HD ITS series AID ITS series Dual AID
description full HD IP camera with Thermal imaging camera Dual imaging camera with
embedded AID with embedded AID embedded AID
video input 1/2.8" CMOS Uncooled Vox Uncooled Vox
microbolometer 7,5 to microbolometer 7,5 to
13,5 μm - IP and 13,5 μm - IP and
Analogue(PAL/NTSC Analogue(PAL/NTSC
video video + Full HD color 10x
zoom
encoding format H.264, MJPEG H.264, MJPEG H.264, MJPEG
max. resolution 1920 x 1080 @ 30fps D1: 720x576; Native: Full HD visual + D1 or
640x512 native thermal
multi-streaming dual streaming: dual streaming: Dual streaming per
H.264 (HP-MP) or MJPEG H.264 or MJPEG camera (4 in total) H.264
or MJPEG
max streams unicast and/or multicast, Unicast and/or multicast
max 20
audio 1 full duplex stereo No
boards per rack N/A N/A N/A
power 8W 24W
stand-alone 12V DC or 24V AC or 24V DC or 24V AC 12Vdc/24Vac/230Vac or
form 802.3af PoE PoE or PoE+
connector type 10/100 Mbps RJ45 10/100 Mbps RJ45 +
or SFP for fibre optional SFP slot
or IP over coax (ECO)
digital inputs 2 1 No
digital outputs 2 1 No
data RS232 or RS422/485 no No
PTZ control yes no No
communication ONVIF, NTCIP, SNMP ONVIF, SNMP ONVIF, NTCIP, SNMP
standards
operating temp -30 °C to +50 °C -50 °C to +70 °C -10 °C to +50 °C
-22 °F to +122 °F -58°F to +158 °F -14°F to +122 °F
XT model; XT model;
-40 °C to +75 °C -35 °C to +65 °C
-40°F to + 167°F -31°F to + 149°F
MTBF > 300.000 hrs > 100.000 hrs > 100.000 hrs
other features AID + customizable AID + customizable AID + customizable
overlay overlay overlay
Early fire detection
Early fire detection 10x optical zoom
www.flir.com
Flux – Management software
All traffic data, events, alarms and video images generated by the video detectors are collected and stored on the Flux
management server. The main goal of Flux is to manage and control all traffic information generated by these various
detectors and to make it useful, meaningful and relevant to the user. In its turn, Flux can communicate with the higher
level SCADA system or other software. All communications run over standard Ethernet.
Besides a pure server and storage function, Flux also provides extra functions such as data and event reporting, real-
time monitoring through an intuitive user interface, event filtering and scenario building ( = management of different
configurations subject to changes in the traffic situation).
Flux also has options to function as a streaming video server, a recording server and a video wall server by means of
plug-in modules.
Multiple servers can be deployed to provide scalability for large installations and/or critical redundancy.
Flux user interface
The client of Flux is a web-based application. This means users only need a web-browser installed on their PC that is
connected to the network of the video detection system to access the traffic management system.
www.flir.com
4 Operation of the AID system
System architecture overview
Below illustrates the typical system architecture of an AID implementation from camera to operator.
VIP system architecture
Third-party analogue or IP cameras of a controlled traffic theatre are connected to VIP detector boards.
For classic analogue CCTV cameras, this connection is a composite video link. The board first digitizes the analogue
video signal before sending it to the analysis algorithms. For IP cameras, this connection is streaming video over a
network link. The board decodes the compressed video stream before sending it to the analysis algorithms. For an
integrated system with edge analytics, the detection logic is embedded in the smart camera (TrafiBot-HD, ITS-series
AID or ITS-series Dual AID) itself.
The detection algorithms analyse the video content and generate events and/or data. In case of alarms, short
recordings (alarm videos) are generated for storage and review purposes. The detector or camera also encodes the
video stream for remote monitoring.
VIP boards are mounted together either in 19” racks or individually in a stand-alone box. The rugged nature of the VIP
boards allows these racks to be mounted in cabinets at the roadside and perform processing in harsh conditions along
the camera site. We refer to this method as a decentralised architecture. When all processing boards are installed in a
remote central equipment room, we refer to it as a centralized architecture. A system with TrafiBot-HD, ITS series AID
or ITS series Dual AID is decentralized per definition. This is also often referred to as “analytics on the edge”.
The detectors can be set up using standard TCP/IP protocol over Ethernet connection, either at the installed location
or remotely over a wide area network. To perform this basic configuration, a java-based application is provided with a
user-friendly interface that can operate on all common PC operating systems. This Traficon Configuration Tool (TCT) is
typically used at installation time, to do an initial setup such as configuring detection zones and verify correct
alignment of the camera on-site or for maintenance purposes.
The heart of an AID system is the Flux server. This system collects and stores all data, events and associated video
recordings from the different detectors in an SQL database structure. It has advanced intelligence capabilities that
www.flir.com
allows for complex filtering of events, even by combining the events from different sensors. It provides advanced
reporting and monitoring functionalities.
Flux can function as a fully stand-alone solution to a traffic management operator. Any operator with sufficient rights
can access the intuitive web-based interface of Flux, using standard browser software. The Flux client does not need
any additional or proprietary software at all. The operator can view events, clear them, add comments, generate
reports, see streaming video and configure the Flux system from this remote post.
In most installations, the Flux server also has its data, events and video sequences transferred to a larger SCADA
system over TCP/IP for further processing and visualization. The integrated open interface allows Flux to interact with
almost any third-party traffic management system.
In the following sections, this document will elaborate on the different components and their capabilities.
www.flir.com
Hardware components of the AID system
VIP detection and compression modules
VIP modules combine traffic monitoring, automatic incident detection and traffic data collection all in one board. VIP
detector boards can be used for indoor (tunnel) and outdoor applications, both for upcoming traffic or traffic driving
away from the camera.
VIP-T detector boards have analogue input and process composite video from classic analogue cameras. VIP-IP boards
can connect to IP cameras and process compressed video streams over Ethernet networks. VIP-TX detectors have
analogue input, provide advanced multi-stream & multi-codec video compression capabilities and have a serial
interface so potentially PTZ cameras can be used and controlled.
VIP-IP detector board VIP-T detector board VIP-TX detector board VIP-HD detector board
Different algorithms (detection algorithms, subroutines for shadow suppression, day/night transition checks, image
quality control, ...), run in parallel on the VIP detectors and deliver accurate traffic information in line with the specific
needs of the user. The user only needs to enable and configure the algorithm parameters that are needed for his
specific application.
Configuration of the VIP modules is done from the Flux server or via a PC that runs the setup software TCT (see
chapter ‘Traficon Configuration Tool’).
VIP housing
VIP detectors boards come mounted in standard 19” racks or as a stand-alone box.
VIP-T, VIP-IP and VIP-HD full 19” rack

The full 19” rack provides 8 slots for VIP-T or VIP-IP detection modules and one position for a power supply module.
The backplane of the rack is equipped with all required input and output connectors. The power supply module is
dimensioned to provide power for all 8 boards. Optionally, a redundant power supply can be connected as well to the
backplane for even higher reliability.
8 VIP-IP boards in a 19" rack and backplane
www.flir.com
VIP-TX 19” rack
The 19” rack for VIP-TX provides 11 slots for the detection modules and one position for a power supply module. All
connections are on one side and reversible handles make it possible to select this at the front or the back. A 24V DC
version exists with redundant power supplies.
.
19" VIP-TX rack
VIP-T box
The VIP-T box is a unit with a single VIP-T detection module. The VIP-T box is DIN rail mountable. Mounting
accessories and mating connectors are part of the deliverables. The VIP-T box requires a third-party 24V DC power
supply.
VIP-T box and DIN-rail mounting accessories
VIP-IP and VIP-HD box
The VIP-IP box is a unit with a single VIP-IP detection module. The VIP-IP box is DIN rail mountable. Mounting
accessories and mating connectors are part of the deliverables. The VIP-T box requires a third-party 24V DC power
supply.
VIP-IP box
VIP-TX box
The VIP-TX box is a stand-alone unit with a single VIP-TX detection module.
The VIP-TX box is delivered with a commercial 12V DC adaptor.
www.flir.com
VIP-TX stand-alone unit
VIP-T optional expansion module

Whenever more I/O is needed than the default on-board (1 input + 2 outputs), an I/O expansion can be added to VIP-T
systems. VIP-T communicates to the I/O expansion through a dedicated RS-485 line that links the 19” rack backplane
to the I/O expansion. This option is available for rack-mounted VIP-T solutions only.
VIP-T optional I/O expansion module
www.flir.com
AID functional description
VIP detection boards, TrafiBot HD and ITS series AID generate a wide range of traffic data and events. Below is an
enumeration of all traffic information available from the detectors and smart cameras. Depending on the application,
certain combinations of detection functions may not be advised. This is mostly due to physical limitations of the video
image and / or the positioning of the camera (viewing angle, viewing distance, etc…).
To keep configuration and calibration as easy as possible for the user, detector modules and smart cameras will be
configured and tuned on-site, in function of the exact requirements of each customer. As a result, unnecessary
complexity is avoided and non-useful information is discarded.
The functions are categorized as follows:
Automatic Incident Detection

Traffic incidents (= incidents directly linked to road traffic)
• Stopped vehicle detect stopped vehicles in up to 16 zones

• Inverse direction detect wrong way drivers in up to 8 zones
• Underspeed detect slow moving vehicles in up to 8 zones
• Levels of service define & distinguish 5 levels of service (normal, dense,
delayed, congested, stop & go) in up to 8 zones
5 levels of service in function of zone occupancy and flow speed
• Speed drop notice sudden drop of the flow speed by x% in up to 8 zones
Non-traffic incidents
• Pedestrian detect pedestrians in up to 16 zones

• Fallen object detect debris in up to 16 zones
• Smoke detect smoke in a tunnel
• Fire detect early fire in a tunnel
Traffic Monitoring and Traffic Data Collection

Detectors and smart cameras collect data per lane and per vehicle class. Note that for optimized data performance,
the camera should be mounted in a typical data-position (about 45° angle inclination to the road, looking at close
range), as both the gap between vehicles as well as the vehicle height must be distinguishable.
www.flir.com
Traffic flow data
• Traffic flow speed per lane

• Zone occupancy per lane
Individual vehicle traffic data
• Timestamp
• Lane number
• Individual speed
• Classification recognize 5 distinct vehicle classes during daytime,
based on length of vehicles;
recognize 2 classes during night-time,
based on headlight position of upcoming traffic
• Gap time
• Length
• Confidence level an indication of the reliability of the data
Integrated vehicle traffic data

= data integration into a single value for a configurable period of time
• Volume number of vehicles per vehicle class per lane

for up to 8 lanes
• Average speed per vehicle class per lane
• Headway
• Gap time per length class per lane
• Occupancy per lane
• Density number of vehicles per km per lane
• Average vehicle length per lane
Presence Detection
Detectors and smart cameras host presence detection algorithms for up to 8 zones. When presence detection is
activated, a detection module can be used to detect vehicle presence e.g. on the emergency lane of a road or in front
of traffic lights. These modules or cameras can be connected to any traffic controller using the physical outputs of the
detector board or camera.
Technical monitoring
Apart from traffic monitoring for incidents, data or presence, AID detectors and cameras also provides these alarms
and information for monitoring detector/camera health and detection operation:
• No video present
• Reboot of the detector
• Configuration change
• Camera movement
• Communication error
• Image quality monitoring
• Device temperature monitoring
Input-output management
www.flir.com
VIP-T boards can monitor up to 3 digital inputs (default 1, optional 2) and control up to 10 digital outputs (default 2,
optional 8).
VIP-IP and VIP-HD boards can monitor 1 digital input and control 2 digital outputs.
VIP-TX and TrafiBot HD detectors have 2 contact closure inputs and 2 contact closure outputs.
ITS-Series AID has 1 contact closure input and 1 contact closure output.
Inputs can be triggered by any external switch. Application example: in case the door of the cabinet is opened, this can
be alerted to the control room by connecting a door-switch to the input of a detector module.
Outputs can be activated upon any configurable combination of events and zones
Application example: Outputs can be used to trigger an alarm signal, a message sign or warning lamp.
I/O management is supervised by the Flux server when a network connection is established.
In case of temporary communication failure with the Flux server, or for decentralized applications, physical outputs
can be driven by the board itself.
Video compression
AID detectors and FLIR ITS smart cameras can generate compressed video sequences for all incident events. These AVI
formatted movies have a configurable pre- and post-event time, so that operators can review what happened before
and after an incident using any standard media player. The images are stored on the Flux server allowing review and
retrieval at any time.
AID detectors and FLIR ITS smart cameras have embedded video compression hardware and/or software that allow
generating streaming video out. VIP-T modules compress video in MPEG-4 format; VIP-IP, VIP-HD, VIPT-TX, TrafiBot
HD and ITS series AID have additionally H.264 and MJPEG compression capabilities on-board. Bit rate and frame rate
can be configured to optimize usage of the available network bandwidth.
All video streams are RTSP-compliant, allowing the use of standard player software such as Apple QuickTime and
VideoLAN VLC to connect to the detector and monitor video in real-time.
Multicast capability is available so that multiple workstations can view the video stream while the network bandwidth
is used in the most optimized way.
Besides the typical video streaming that contains overlay features (detection boxes, labels, etc…) VIP-IP and VIP-HD
also supports metadata mode. In this mode, the original input video is streamed back out without modification, but
with overlay information added next the stream, rather than embedded inside the image. This mode allows standard
media players to visualize the original camera stream without modification while specific metadata player software
can play the stream and visualize the additional detection information overlay. As a result, the visualization of overlay
information is an individual choice of each user.
Metadata stream in standard player Metadata stream in specific metadata player
www.flir.com
VIP-T VIP-IP VIP-HD VIP-TX TrafiBot ITS ITS
HD series Series
AID Dual AID
MPEG-4 encoding
      
MJPEG encoding
      
H.264 encoding
      
Metadata overlay
      
VIP and FLIR ITS smart cameras encoding capabilities
www.flir.com
Resolution PAL (up to 25 fps) NTSC (up to 30 fps)
Full D1
720 x 480
720 x 576
4CIF
704 x 576 704 x 480

2CIF
704 x 240
704 x 288
½ D1
352 x 480
352 x 576
CIF
352 x 240
352 x288
Common resolution options for compression
www.flir.com
Software components of the AID system
TCT – Traficon Configuration Tool
General
Traficon Configuration Tool is a fully graphical JAVA-based application for setting up detector modules. It allows to:
• Keep track of multiple detectors on multiple networks

• Modify generic parameters
• Define and enable detection zones and functionalities
• Modify detection function-specific parameters
• Define event recording and alarm generation
• Modify video compression parameters on VIP-T and VIP-IP
• Configure I/O functionality
• Save and recall multiple offline configurations
This fine-tuning of detectors or smart cameras can be done either on-site or remotely over the network. The system
can remain operational during the configuration and tuning or it can be done off-line on saved configurations to be
submitted to the board at a later time.
The TCT application operates on industry standard Microsoft Windows PCs.
TCT graphical user interface
www.flir.com
IP address assignment
VIP-T, VIP-IP and vIP-HD board IP addressing scheme is initiated from the TCT interface using an auto-assignment
principle. In this process, the administrator only provides a single base IP address for the whole AID system. The
address of all other boards is then automatically deducted, based on the rack number (set by a hardware DIP switch in
the rack) and the relative position inside the rack.
VIP-TX, TrafiBot HD and ITS Series AID addresses can be set individually over a web interface or from a device
management utility.
Calibration
For each camera position, the AID detector or smart camera is calibrated for the width of the road and the camera
height. By precise calibrating, the speed and the size of an object can be measured accurately. This allows the system
to properly distinct e.g. a person - to be detected as ‘pedestrian’ - and lost cargo – to be detected as ‘fallen object’-.
Setting up detection zones
For any image, TCT allows to define detection zones, as per the functionalities requested by the customer. One or
multiple zones are drawn on the image for detection functions that are activated. Each zone gets an ID and different
zones can be grouped for uniform reporting of events. Zones can be identified more intuitively by using the ability to
define ‘characteristics’. These characteristics assign user-configurable naming to zones, e.g. ‘left lane’, ‘km 34’ etc....
Reporting characteristics when alarms occur, rather than abstract zone numbers, makes the operator interface much
more intuitive to work with and to understand.
Pedestrian detection zones Stopped vehicle detection zone
www.flir.com
Speed alarm detection zones Fallen object detection zones
Underspeed detection zone Inverse direction detection zone
Different zones can get individually different parameters. As an example: an alarm gets flagged and reported to the
operator after an event occurs. Once the situation is cleared, the alarm remains raised for a certain amount of time,
called ‘time off’. This time can be set individually for every zone.
Settings like this allows to define a different behaviour for zones that are more or less critical than others; e.g.
emergency zones alongside the road.
If no detection is needed in certain areas of a zone, there is the possibility to create a masking zone (blanking zone).
This could be used to avoid false alarms e.g. from known fixed objects that are in the field of view of the camera and
obscuring part of the detection zone such as street lighting, billboards etc...
Masking light poles to avoid false alarms
www.flir.com
Certain zones can and some zones must be made direction sensitive, for example to detect wrong way drivers.
By moving the cursor over a detection zone, details of the zone are shown (length, width, etc...).
Zone details; the triangle indicates the zone direction
Display configuration settings define whether zones are shown as overlay on the image or not and where the alarm
messages should pop up. Certain zones could be visualised, while others are not.
TCT has build in copy/paste functionality for detection zones and their settings so that they can easily be copied e.g. to
use on another lane. A full configuration from a detector can also be copied to another detector. This is extremely
useful in tunnel applications, where most cameras have very similar views.
AID Management System: Flux

General
Flux is a stand-alone software platform for use with the AID video detection system. Its main task is to collect and
store traffic data and traffic events in its database. It can also function as an easy-to-use graphical user interface for
traffic operators, as a streaming video server, an interface to a networked video recorder (NVR) system, called T-Rec,
and as a video wall server.
Flux allows to:
• Receive data, alarms and images from each detector

• Store data and alarms in a relational database
• Store images on a hard disk as incident image sequences or recordings
• Continuously monitor the correct operation of the system
• Generate reports with traffic data charts and tables
• Communicate with other systems (matrix, other PC, …) via TCP/IP, or thanks to built-in Java plugins
• Inhibit alarms in certain traffic conditions (e.g. road works, heavy traffic, …)
• Build a customized user interface with maps, streaming video, alarm lists
• Send emails when incidents occur (email plug-in)
• Capture, re-encode and provide streaming video from detectors (IMUX plug-in)
• Drive a video wall display with customized layouts (Video wall plug-in)
• Control and interface to video storage (T-Rec)
www.flir.com
Flux management server and associated interfaces
Traffic data and events generated by the detectors or smart cameras are transferred to the Flux and stored in a
MySQL relational database. Real-time data is also available on a TCP/IP socket and can be used by client applications
or by a third-party management system to monitor and control the traffic.
This system is composed of a server and a client part. The server must run on a dedicated PC. The client application is
web compatible and can run in any web browser having the Adobe Flash Player plugin. It can run on the server PC or
on any PC in the network.
For example, clients can connect from the operator control room and at the police station.
Flux also creates video sequences of incidents. Therefore, the system collects the compressed video sequences from
detector modules and stores the files to disk. The video sequences can be replayed locally or with most common
third-party media players (Microsoft Windows Media Player, VideoLAN VLC player, etc…).
Flux is a backward-compatible product, meaning it can work with as well with older VIP products. Flux can replace
earlier TMS server software (Watts+, T-Port and T-Control) and connect to a combination of VIP-T, VIP-IP, VIP-TX,
TrafiBot, ITS-series and older VIP boards.
Build-in user management allows for different users to be created with different access levels. Different operators
can e.g. see a different part of the road and the related alarms.
www.flir.com
Flux real-time interface
Flux data reporting
For reporting purposes, data can be retrieved from one camera or a group of cameras and for certain time intervals.
One can e.g. ask for all stopped vehicle events for the cameras from a certain section for a specific period.
www.flir.com
Flux event reporting
Flux allows implementing a personalized Graphical User Interface
www.flir.com
Event recording
For all activated detection functionalities, Flux allows to store pre- and post incident video sequences. When an event
happens, the detector/smart camera on-board video buffer (size is related to the configurable pre-incident time e.g.
15 seconds) is sent to the management server and recorded together with the pre-defined post-incident sequence
after the event (e.g. another 30 seconds). This way pre- and post-alarm information is available at all times for
reviewing.
For each event, following information can be stored:

• Data only
• Data and a still picture (preview image)
• Data, preview image, pre- and post incident video sequence
The user may select to store data and/or a still picture after a change in the level of occupancy, while for a more
critical event such as stopped vehicle or smoke alarm, pre- and post incident video sequences can be stored as well.
At Flux, the pictures and video sequences can be easily replayed. These video sequences can be replayed with most
common third-party media players (Microsoft Windows Media Player, VideoLAN VLC player, etc…).
Flux build-in intelligence

Probably the most powerful function of Flux is to filter events, coming from the installed detectors/smart cameras, in
order to ensure that only relevant events generate alerts and only meaningful data gets collected. The filtering
functions prevent reporting of data that does not reflect the real-time traffic situation. The goal is to get a more user-
friendly system to the operators by providing only the wanted alarms. Some alarms might still be valid, but rather
unwanted at a given moment in time.
The filtering is typically defined in scenarios. A scenario defines a number of inhibitions (rules that filter a specified set
of events and alarms for one or more zones) that apply to a number of camera groups (a specified set of cameras).
The scenario can be triggered automatically by a defined set of physical digital inputs to any AID detector/camera, by
the internal task scheduler or can be started manually either from the Flux user interface or by remote command from
the higher level SCADA system. As a resulting action, a scenario can also upload a different configuration to the
detectors.
Consider this application example.

Flux does not need to report events from a road section that is closed due to maintenance works. For this situation, a
new scenario is created called ‘direction Y closed’. In this scenario, a camera group is created containing all cameras
monitoring the closed section. For this camera group, all alerts are inhibited as no traffic will be present on that
specific road segment. In fact, maintenance vehicles may even be on that segment causing false stop alarms to be
generated.
During this maintenance works, traffic gets diverted to the other side of the road, where a number of lanes now is
reserved to traffic from the opposite direction. We create a second camera group that contains all cameras
monitoring the open side of the road. Here we want to change the definition of the zones on all cameras to reflect
that traffic is going in the other direction on some lanes. This can be done by uploading an alternative configuration to
this second detection group.
Optionally, we may want to discard (inhibit) data collection for the time of the maintenance works as that data is not
representative for the normal traffic situation. We start this scenario on the day the road works are beginning.
A second method of filtering is available as ‘advanced filtering’. In this mode, we can:

• inhibit events that occur more than once on related cameras or zones
• ignore related events
• ignore event unless specific conditions apply
These methods allow for filtering out events under very specific conditions in a specific environment. The available
methods create a very powerful tool to create complex rules.
www.flir.com
As an example, in a bi-directional tunnel, cars may be surpassing one another in low traffic situations. To distinct a car
surpassing another from a car that is driving consequently on the wrong side of the road, we may ignore the ‘inverse
direction’ detection unless this occurs a number of times sequentially on the next cameras.
Flux interfacing
All alarm-, event- and configuration communication between AID detectors/smart cameras and Flux is based on
standard XML structured messages. Flux server collects these messages, analyzes them and translates them into data
for local storage in a standard MySQL database.
For this data to be accessible by third-party software, Flux provides an SDK (Software development kit) to
programmers or the possibility to add integrated Java plugins in the Flux server itself.
The SDK comes with an OCX ActiveX control that makes it easy to integrate this interface in Microsoft Windows
applications. Sample code is also provided to demonstrate the operation of the code, together with a reference
documentation that describes all functions and their parameters in detail.
With this SDK, it becomes easy to query the Flux data to either visualize in a common GUI application or to process it
and produce personalized reporting or analysis functionalities.
Email plug-in
An optional email plug-in allows Flux to send email alerts in case of incidents.
IMUX
IMUX is an option to Flux that retrieves streaming video with overlay from the detectors and can re-encode the
streams to lower bandwidth. This allows:
- a secure split between the video network and the data network segment on which the operators work
- save bandwidth for (remote) video monitoring capabilities
Video wall plug-in
An optional video wall plug-in allows defining multiple views and combinations of maps, video windows and alarm-
triggered display channels to drive a video wall display with a customized user interface.
Flux video wall
T-Rec
www.flir.com
T-Rec is a network video recorder (NVR) extension to Flux. It allows permanent recording of the AID system video
sources and other cameras.
Minimum Hardware requirement
Server:
• CPU model: Intel © Quad core @ 2 GHz
• RAM: 8 GB
• O/S: Windows 2008 server 64 bits, Windows 7 64bits, Centos 5.x, 6.x, 7.x 64bits, Red Hat Enterprise 5.x, 6.x,
7.x 64 bits; Linux required if redundancy needed
• Storage: 500 GB with a fast disk access (min 7200rpm)
• 1 Gb network connection to the detector network and data network
Note that his is the default advised configuration for one server and a maximum of 300 detectors connected.
Specification maybe adapted upon project requirements (very limited number of detectors, very important storage
depth) with FLIR ITS approval.
Client:
• 2 GHz CPU
• RAM: 1 GB ram
• Standard web browser, e.g. Microsoft Internet Explorer, Firefox with Adobe Flash plugin Version > 10.0
• Video card with graphic acceleration, minimum screen resolution 1024 x 768
• Network connection to the TMS Flux server
www.flir.com
5 System Redundancy
The automatic incident detection system is a safety & security system, so a high level of redundancy could be required
to make sure that the system remains operational in the event of a critical system component failure. In case of any
failure of a system component, the user must immediately be notified by an automatically generated system alarm.
Definition of a functional redundant system: if any single component fails, the system will keep on functioning and a
signal “component failure” will be transmitted immediately.
The AID system offers the possibility to implement redundancy capability on different levels:
• camera and detector level redundancy
• Flux server & database level redundancy
Camera and detector unit level redundancy

Redundancy based on detection zones
If a camera, the link between camera and detector board or detector board itself fails, the system will no longer
analyze the video from this camera. Flux will generate events to notify users and/or other systems. The only way to
have a redundancy on this side is by covering the same zones with different camera and detectors. This solution
requires more cameras and detectors. There are some limitations in terms of available detection types in redundant
zones.
C1 C2 C3 C4 C5 C6 C1 C2 C3 C4 C5 C6
120m 120m 120m 120m 120m 60m 60m 60m 60m 60m
120m 60m 60m
120m
Standard configuration Redundant configuration
C1 C2 C3 C4 C5 C6 C1 C2 C3 C4 C5 C6
120m 120m 120m 120m 120m 60m 60m 60m 60m 60m
120m 120m 60m 60m

120m
Camera/detector C3 fails in standard configuration C3 fails in redundant configuration
Redundant detector coverage
In normal function mode of all detection units, the filtering methods of the Flux server allow to avoid double event
reporting from overlapping areas.
Detector redundancy
For VIP-IP based detection, an option exists to add some detector boards to a so-called “spare pool”. These boards are
powered on at all time but not active in the AID event detection. When one of the active boards fail (either by
hardware or network connection failure), this is detected by the Flux management system that will then load the
configuration of the failing detector into one of the detector boards of the spare pool. This latter board will then take
over the functionality of the failing board until service intervention restores the functionality of the system.
Power supply redundancy

An optional external power supply module can be connected to the racks. This power supply can then serve as a
backup supply for keeping 3 racks operational.
www.flir.com
Flux scaling and redundancy
Scaling
In order to respond smoothly to an expanding video detection system, the administrator can upscale Flux by adding
extra servers. The total workload is then distributed over all servers (load balancing).
Redundancy
The administrator can configure Flux and the video detection system with duplicate components. If one component
fails, the duplicate component will take over.
System components and processes that can be scaled up or duplicated:

• Flux server
• Flux database - up to 2 online databases provide data redundancy
• Flux MMS server
• Flux streaming video server
Via these 4 components, the operation of Flux is fully covered.
Multiple Flux server configuration
To configure multiple servers for scalability or redundancy, Linux is required as the operating system. A multiple server
configuration also requires that the time is synchronized between all servers.
When the administrator sets up Flux as a scaled and redundant system, a minimum number of servers are required to
be operational in order to handle the workload.
Flux uses virtual IP addresses for network communication. A virtual IP address is an IP address that is not connected to
a specific PC or network card. The virtual IP address remains available when one PC fails. A second PC in the network
takes over the virtual IP address.
www.flir.com
6 Services
During a project preparation, a team of experienced field engineers are working with you in order to find the most
optimal solution for the position of the camera, in order to maximize the capabilities of the detection system.
Training can be offered on a project base. This can be towards the system integrator and/or the end-user.
FLIR ITS organizes dedicated training courses for ‘Certified Service Engineer’ to its partners. During these sessions, the
basic principles of video detection are taught, complemented by practical hands-on sessions in small groups. Each
function of the latest product and software enhancements is explained in detail.
Our AID products have a high MTBF (VIP MTBF = 200.000 hours) and a low MTTR (replacing a board, reloading
configuration en verification may take 30 minutes at most). On top of this, AID components are hot-swappable and
have a typical lifetime of 10 years. Note that the AID system also provides technical alarms in case of ‘unclear image’,
‘camera moved’ or communication problem. As a result, the detection system is a low maintenance system and
downtime is reduced to an absolute minimum.
The serviceability can be further increased by providing remote access via a password-protected VPN connection to
the Flux server. This allows FLIR ITS engineers to remotely diagnose and even correct failures or unexpected system
behaviour.
FLIR ITS can also offer customized maintenance contracts on different levels. Contact our service department or your
local sales contact for more information.
www.flir.com
7 Camera considerations
In case a third-party camera is chosen, as for any detection system, the sensor is a critical part to the performance of
the whole system. The camera, being ‘the eye of the system’, is a very important component in the chain of traffic
management. Not only good technical characteristics and performance of the camera system but also a correct
mounting will contribute to a better detection. FLIR ITS has many years of field experience in different traffic
application fields and will be pleased to advise you on proper sensor selection and positioning. FLIR ITS can test your
camera for its compatibility and performance in view of detection applications. Customers are guided from the very
beginning in project preparation up to the ultimate target of operational service.
Technical specifications of the camera

One can categorize different requirements for the camera as follows.
Optical performance
The sensor, lenses and image processing electronics are the elements of a camera that affect the quality the image
that it delivers. As a guideline, consider following minimal requirements. The requirements are identical for analogue
cameras as for IP cameras.
• sensor type: preferably CCD

• slow iris regulation
• AGC: 0 – 12 db max. (preferably switch off)
• no frame accumulation
• infra red filter (black & white camera)
• minimal blooming
• minimal smearing
Blooming Smearing
Signal integrity
Output signal specification, cabling, switches, convertors, etc… affect the quality of the video signal before it arrives at
the VIP detector board. The whole video transport and distribution system may influence the video quality and related
detection performance.
Consider these guidelines for analogue video:

• Analogue signal specification: CCIR/EIA 1V peak to peak (+/-20%)
• Analogue connection:
www.flir.com
o RG59 coax cable for distances up to 300m
o RG11 coax cable for distances up to 500m
Consider these guidelines for IP video
• Minimal Cat 6E cabling, maximum 100 meters, preferably shielded

• When using multicast, remember to select switches that support IGMP snooping.
• Manageable switches can avoid a lot of trouble.
Compression
When IP cameras are used or when the analogue signal gets converted to compressed IP video and optionally
decoded again, the whole compression conversion seriously affects video quality.
Consider these minimal requirements for IP video:
• Codec: MPEG-4 or H.264

• Resolution: VGA, 4CIF or D1
• Frame rate: 25 fps (PAL source camera) or 30 fps (NTSC source camera)
• Bit rate: MPEG-4 @ 4 Mbps or H.264 @ 2 Mbps
These requirements should be met simultaneously. Often, low quality cameras tend to sacrifice one of these
parameters in favour of another (e.g. lower frame rate at higher resolution), resulting in a degraded image.
Additionally, the camera or encoder should support RTSP streaming protocol, in order to facilitate connection to the
stream for viewing and / or detection purposes.
Position of the camera

Camera positions are affected by the application and have to be chosen with care. The expected performance of the
video detection system depends highly on correct positioning, height, angle and lens behaviour of the camera. A
poorly positioned camera may result in unwanted occlusion effects and inaccurate speed and length measurements.
Cameras should preferably be placed as high as possible and near the middle of the detection zone (road – tunnel
roof). If this is not possible, place the cameras to the left side of the road in order to avoid occlusion by heavy traffic.
www.flir.com
Occlusion by heavy traffic Occlusion in tunnel for Central and high mounting
side-fired camera position provides best
detection results
The detection range for detecting stopped vehicles depends on the height of the camera and on the objective of the
camera. As a general rule, we propose to limit the detection zone to 300m outdoors and to 20 times the camera
height indoors.
Always avoid having the horizon in the image. Direct sun into the image can make it impossible to see the traffic.
Direct sun from the horizon seriously affects detection capabilities
The ideal camera position and properties also depend on the main targeted functionality.
An AID system is only workable if the number of false and / or unwanted alarms is reduced to a minimum. For best
result, the lens of an AID camera is preferably a zoom lens with focal length between 8 and 25mm.
To detect different vehicles in view of classification, the detection system must be able to distinguish the gap between
different vehicles. This condition implies that a camera should be mounted at sufficient height (e.g. 12m) and under an
angle of typically 45° with a lens between 3.5 and 6 mm. The required camera height will be determined by the
number of lanes to be monitored and by the relative position of the camera to the monitored road surface.
Do not use detectors configured for data collection in tunnel applications because of the lack of height to mount the
camera. Experience has taught that the optimal video detection system for tunnels is a system with detectors
configured for incident detection inside the tunnel, while outside camera positions are used at the ends of the tubes
for data collection,.
In order to assist on camera positioning and mounting, FLIR ITS has developed the CamView software tool. With this
tool, any camera position can be simulated. CamView simulation can be made available free of charge upon simple
request of the customer.
www.flir.com
Camview simulation of 6 lane coverage from 5 to 50 meter distance
Mounting of the camera

It is preferable to mount the camera on a stable fixation to avoid image movement because of sweeping by the wind,
nearby fans in tunnels or any other cause of vibration.
For the connections of the camera follow the instructions of the camera supplier.
www.flir.com
Addendum: About Traficon - FLIR ITS
About
Based on technology developed by the University of Louvain in 1982, Traficon’s continuous research has resulted in
powerful solutions for traffic applications.
Today, FLIR ITS is the leading reference in traffic detection based on video image processing. Traffic managers all over
the world use our technology for vehicle detection, traffic data acquisition, automatic incident detection, and
intersection control and management in motorway, tunnel, bridge and urban applications.
As an ISO9001:2000 certified company, we strive to meet our customers' requirements and deliver reliable high
quality solutions. We guarantee tailor-made solutions and experienced project support.
FLIR ITS’s headquarter is based in Belgium. FLIR ITS has dedicated sales and support offices in the USA, France,
Germany, UK, China, India and Brazil.
History
History highlights:
1992: Foundation of Traficon n.v. by Mr. Jo Versavel. His mission is clear: to become the market leader in the field of
video detection for traffic applications.
1993: The VIP (Video Image Processing) board comes into the world. This modular single processor board has to
perform the basic tasks for handling the video, digitizing the video, analyzing the image and extracting the most
important traffic data. The basic idea of the VIP is to keep video detection for traffic as simple as possible. Therefore it
is designed to perform only the real needed tasks in standalone form. It can be programmed using only a simple
keyboard and monitor.
1994: At the East Coast of the U.S, our partner Control Technologies starts promoting Traficon products. Together
with our West Coast distributor ( Kar-Gor ), serious efforts are made to introduce the VIP detectors in the U.S.
intersection market. Kar-Gor (Gordon Dale) develops the first interface unit that permits VIP3 to be plugged into a 170
controller.
As of then, Traficon is ready to conquer the U.S. market
2000: New Traficon VIP Range: VIP/I, VIP/D, VIP/P.

These new boards include brand-new hardware with faster processors and more memory on board. This new VIP
range focuses on function and functionality with a more consistent grouping of functions within an application
domain. Ease of use also remains primordial.
2003: Launching TrafiCam®, an integrated sensor platform for vehicle presence detection and data collection.
2004: Traficon wins 'Olympic Games 2004' contract. The Flemish Ministry hands out the prestigious award 'Lion of
export 2003 ' to Traficon as best performer.
2008: Traficon always provides video detection technology with respect to Mother Earth. It extends its Traficam
sensor range with a solar powered environmental-friendly version.
2009: Traficon launches of a brand-new intelligent pedestrian detection concept: SafeWalk.
2010: Traficon launches VIP-IP, a powerful solution for AID using network cameras
www.flir.com
2012: Traficon announces integrated solutions VIP-TX (high-end video encoder with integrated incident detection
algorithms) and TrafiBot (box camera with integrated incident detection algorithms) at ITS world in Vienna
2012: In US, FLIR and Traficon had been working successfully together to improve vehicle presence detection in all
weather through the use of thermal imaging. In December, Traficon is acquired by FLIR and forms its transportation
centre of competence: FLIR ITS.
2013: FLIR ITS launches ThermiCam / TrafiSense, the world’s first intelligent thermal traffic sensor
2014: FLIR ITS launches TrafiBot-HD and VIP-HD, which brings the High Definition world to traffic
2016: FLIR ITS launches ITS series AID, a Smart AID camera which combines best-in-class thermal imaging technology
with advanced video analytics to provide a complete solution for automatic incident detection, data collection and
early fire detection.
2017: FLIR ITS launches ITS series Dual AID, a Smart Dual vision AID camera which combines best-in-class thermal
imaging technology with advanced video analytics to provide a complete solution for automatic incident detection,
data collection and early fire detection.
Company mission & objectives

TO BE THE WORLDWIDE MARKET LEADER IN
VIDEO IMAGE PROCESSING FOR TRAFFIC ANALYSIS
• FLIR ITS shall, with its experience in the field of image processing and traffic, contribute to a more fluent and
safer traffic.
• FLIR ITS believes that a correct and creative application of new technologies will improve the quality of life.
• FLIR ITS also believes that a good cooperation and creative effort of all FLIR ITS team members in full
confidence will result in the best possible human (social) and economic results.
• FLIR ITS wishes to conduct a policy of continual quality improvement
References
• FLIR ITS has more than 25 years of experience in the field of traffic vehicle detection.
• FLIR ITS has more than 75,000 detectors operational worldwide.
• FLIR ITS has installations in more than 400 tunnels.
• More than 600 km of tunnels worldwide are equipped with a FLIR ITS system.
Recent references include:
• Nefise-Akçelik tunnel on the Bolaman-Persembe Highway (Turkey): Automatic Incident Detection

• Fréjus Alpine Tunnel (France-Italy): automatic incident detection and digital recording
• Colorado Springs authorities (US): intersection management
• EMAS Arterial Roads (Singapore): Automatic incident detection & data collection
• Antwerp ring road: Automatic incident detection
www.flir.com
• Paris region: Automatic incident detection on more than 1400 cameras in 22 tunnels around the capital of
France
www.flir.com
Abbreviations and acronyms
A
AC Alternating Current
ADSL Asymmetric Digital Subscriber Line
AID Automatic Incident Detection
AVI Audio Video Interlaced
C
CCD Charge Coupled Device
CCIR Comité Consultatif International pour la Radio
CIF Common Intermediate Format
CPU Central Processing Unit
D
DC Direct Current
DIP Dual In-Line Packet
E
EIA Electronic Industries Association
G
GUI Graphical User Interface
H
HMI Human Machine Interface
I
I/O Input / Output
IGMP Internet Group Management Protocol
ISO International Organization for Standardization
ISDN Integrated Services Digital Network
L
LAN Local Area Network
LED Light Emitting Diode
N
N/A Not Applicable
M
Max maximum
Min minimum
MPEG Moving Picture Experts Group
MTBF Mean Time Between Failures
MTTR Mean Time To Repair
O
OCX OLE Control Extension
www.flir.com
OLE Object Linking & Embedding
O/S Operating System
P
PC Personal Computer
P/S Power Supply
R
Rpm rotations per minute
RTSP Real Time Streaming Protocol
S
SCADA Supervisory Control And Data Acquisition
SDK Software Development Kit
T
TCT Traficon Configuration Tool
TCSE FLIR ITS Certified Service Engineer
TMS FLIR ITS Management System
V
V Volts
VIP Video Image Processor
W
WAN Wide Area Network
X
XML Extensible Markup Language
Z
Zocc Zone occupancy
www.flir.com

AID System Description 20170420 EB

Uploaded by

Copyright:

Available Formats

AID System Description 20170420 EB

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AID System Description 20170420 EB

Uploaded by

Copyright:

Available Formats

Traffic Management

& Video Processing

2 Introduction: video detection for traffic control .............................................. 5

3 Product overview ........................................................................................... 8

VIP – Video Image Processor boards .................................................................................................. 8

4 Operation of the AID system .......................................................................... 13

System architecture overview .......................................................................................................... 13

Camera and detector unit level redundancy .................................................................................... 33

7 Camera considerations .................................................................................. 36

Technical specifications of the camera ............................................................................................. 36

Addendum: About Traficon - FLIR ITS ................................................................... 40

Abbreviations and acronyms ................................................................................ 43

Detection of wrong way driver

Detection of a pedestrian on a highway. Video Outdoor data collection on highway: speed,

Thermal detection of stopped vehicles Thermal fire detection in tunnels

Flux user interface

VIP-T detector VIP-IP detector VIP-TX detector VIP-HD detector

8-channel VIP-T rack single channel VIP-IP or VIP-HD box

TrafiBot HD – Box camera with integrated detection

TrafiBot HD camera with integrated AID

ITS series AID – Thermal camera with integrated detection

ITS series AID camera with integrated AID

ITS series Dual AID camera with integrated AID

model VIP-T VIP-IP VIP-TX VIP- HD

Flux user interface

VIP system architecture

VIP-T, VIP-IP and VIP-HD full 19” rack

8 VIP-IP boards in a 19" rack and backplane

VIP-T box and DIN-rail mounting accessories

VIP-IP and VIP-HD box

VIP-T optional expansion module

VIP-T optional I/O expansion module

The functions are categorized as follows:

Automatic Incident Detection

• Stopped vehicle detect stopped vehicles in up to 16 zones

5 levels of service in function of zone occupancy and flow speed

• Speed drop notice sudden drop of the flow speed by x% in up to 8 zones

• Pedestrian detect pedestrians in up to 16 zones

Traffic Monitoring and Traffic Data Collection

• Traffic flow speed per lane

Individual vehicle traffic data

Integrated vehicle traffic data

• Volume number of vehicles per vehicle class per lane

Metadata stream in standard player Metadata stream in specific metadata player

704 x 576 704 x 480

Common resolution options for compression

• Keep track of multiple detectors on multiple networks

The TCT application operates on industry standard Microsoft Windows PCs.

TCT graphical user interface

Setting up detection zones

Pedestrian detection zones Stopped vehicle detection zone

Underspeed detection zone Inverse direction detection zone

Masking light poles to avoid false alarms

Zone details; the triangle indicates the zone direction

AID Management System: Flux

Flux allows to:

• Receive data, alarms and images from each detector

Flux data reporting

Flux allows implementing a personalized Graphical User Interface