Editing
Violation Management Settings
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
'''Location''' SETTINGS > Interfaces '''Purpose''' Violation Management Services (VMS) provides vehicle violation processing services to the auto rental industry. The services provided by VMS are designed to reduce the costs incurred by the rental company when their on rent vehicles incur traffic violations that are not reported by the renter. An integral part of the system involves the exchange of information between VMS and their clients. The process of obtaining renter information involves a two way conversation between the Client and VMS. Initially, VMS will send an information request to a designated FTP folder for the Client to retrieve. Subsequently, VMS will retrieve the requested data from a designated FTP folder where the Client has deposited the data and process it within the VMS system. The response file is encrypted using 256 bit encryption and also password protected for security purposes. Once the process has been defined for a Client, it should not require any further Client personnel involvement on a normal day to day basis. Please note that this is an add-on module, and you must enter into a contractual agreement directly with the VMS before this module can be implemented. There are also additional set-up requirements. Please see the VMS Setup Guide. '''Fields''' RentWorks Client ID β This is the code setup by VMS for the particular customer. The Client ID is EXACTLY the same as the data that will appear as the 6th entry in the VMS request file. Create location file - Check this box only once to generate location information for VMS. Only needs to be done ONCE (unless something at this location changes). The check box is cleared when the programs execute. Inbound Directory β This is the local directory for the in-bound request file from VMS. This information must be conveyed to VMS so they can FTP the requests to the correct location. Inbound Archive β This is the local directory to hold the in-bound requests once they are processed. Outbound Directory β This is the local directory for the out-bound data for VMS. This information must be conveyed to VMS so that they can retrieve the data files. Outbound Archive β This is the local directory to hold the out-bound data files once they have been retrieved. Column Headings to match in Request File - These must be entered as follows: :Date: DATE :Time: TIME :Plate Number: LICENSE_NO :Plate's Issuing State: LICENST_ST :Transaction ID: IDENTIFIER :BARS' Client ID: BLUEBRDID [[Category:Bluebird]]
Summary:
Please note that all contributions to KB may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
KB:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information