VMS (Violation Management System)
Feature:
A feature of the VMS system is that evidence is acquired at source in the form of high quality video – from which still images are optionally extracted, formatted and encrypted to meet all the local compliance requirements for what constitutes legally binding evidence. Furthermore, GPS and “Automatic Number Plate Recognition” (ANPR) are utilized as standard features, thereby enabling real-time location-based notifications to be issued.
Core Object:
The core objective of Truvelo‘s Violation Management System (VMS) is to facilitate both the acquisition and subsequent processing of video-based evidence pertaining to traffic-related offences. This may include, but is not limited to:
- “Spot” speed offenses
- “Average” speed offenses over sections of roadway
- Traffic (red) light offenses
- Journey time
- Vehicles driving in unauthorized “zones”
- Illegal overtaking maneuvers and u-turns
Real Time Notification:
Additionally, VMS may be utilized to acquire real-time notification of vehicles bearing number plates that are currently under surveillance. This might include vehicles that:
- Have been reported as stolen
- Have may been cloned
- Are owned by individuals for whom there are outstanding Fines and/or Warrants of arrest.
- Are not legally roadworthy.
Driver Vehicle Licence (DVL) System
Centralized Server:
The DVL is a generic centralized server, designed to accommodate real-time communications between VMS subsystems and a variety of vehicle information sources. These include:
- The local authority responsible for the regional Vehicle Registration Database. In South Africa this takes the form of the eNaTIS system.
- Stolen vehicle databases.
- Cloned vehicle databases – possibly sourced from insurance companies.
Central Design Objective:
A central design objective of the DVL is to be as generic as possible – so that the systems run by local authorities can be integrated seamlessly with the VMS without the requirement for internal code changes.
VEX
VMS "Back Office"
The “Violation EXchange” (VEX) is a collective term for the VMS “Back Office” interfaces utilized by region-specific third party fine processing systems. The VEX systems can be configured to issue solicited and/or unsolicited HTTP POST violation updates and notifications to authorized (third party) back office systems.
