Here are the steps required to install the vMDT app on an iPad or Android device. For a current list of Hudson Certified devices that will run the VMDT application: Mobile Device Certification
These are the steps required to add the device to your device configuration page of your VMDT site ResUtility page. These steps are required for the device to gain access to the VMDT site. You will need to know the URL of the resutil page of your VMDT site and you will need access to this site, setup from the Web tab of your local User Access configuration.
This step is required to give the driver access to any VMDT application from a device. It ensures that the driver has access to the VMDT application and also is used to define who the driver is, so that they see their Reservations and/or Trips.
This step is required in order for the drivers to receive their Messages, Reservations, and Trips from the Dispatcher. When using GPS on the VMDT, a unique Communication Device must be setup for each Vehicle/Driver. If GPS is not being utilized, one communication device labeled VMDT will suffice.
You can now run the VMDT application from this device.
If you will be tracking your vehicles using GPS, you will need to sync the devices to ensure that each coordinate is linked to the correct vehicle.
Now when you assign a driver to a vehicle using the Vehicle In/Out tool, the GPS device will be linked to that driver and vehicle and display on your map.
]]>If you will be connecting to your HWeb products (HWeb Agent, Dispatcher, Utilities, and Admin programs) via the internet, protecting your internet connection and internet access is crucial to being able to continue doing business. In the event you have a planned or scheduled internet outage make sure you prepare by printing out on paper all of the trips likely to occur during the service interruption so that you may continue to work. An alternative is to seek out another (temporary office) location to enter reservations from or to dispatch from so that you may continue to work without interruption.
You will be connecting to the Hudson Server via Remote Desktop Connection. This application is included in Microsoft Windows XP and later versions. You may use earlier versions of Microsoft Windows, but you must first download the free Remote Desktop Client from the Microsoft Website here.
This application is also included on the Windows XP install disk if you have it. This XP install disk may be used to install the Remote Desktop Client on earlier versions of MS Windows.
To see if your PC has the application:
Start—> All Programs—> Accessories—> Communications—>Remote Desktop
If you do have this application, it may be easiest to copy the shortcut to your windows Desktop. To do this, browse again to the Remote Desktop program. Right Click on it. Left click on Copy. Place the mouse cursor over the Windows Desktop. Right Click again and then select Paste. This should put an Icon on your Desktop named: Remote Desktop Connection.
(Ensure first that your workstation can connect to the internet.)
Double Click the Remote Desktop Connection program or shortcut, to bring up the connection window. In this window, enter the IP ADDRESS of the Hudson Server you will be connecting to:
Your Server IP Address is: (Contact Hudson Tech Support for this information)
Once the IP Address has been entered, click on CONNECT.
An internet connection to the Hudson Server will be initiated.
At the login screen, enter your Login Name and your password. Your login information is CaSe SenSItiVe. So check your caps lock key before entering.
Your Login Names and passwords are: (Contact Hudson Tech Support for this information)
Upon successful login, you will be presented with your customized Windows Server Desktop where you will see your normal HWeb Icons. From here, you login to and use your Hudson products in the normal manner.
When finished with your session, click the START button, then Log Off. When asked if you are sure you wish to log off, select YES.
At any time during your session, you may return to your own Windows Desktop by clicking on the minimize (-) button at the top of your Remote Desktop screen. The session will be minimized to your taskbar. To restore, simply double click on the “TSL02.HUDSONLTD.NET” task at the bottom of the screen.
While connected to the Hudson Server, you are welcome to use a web browser (Intenet Explorer, Mozilla, etc.) to retrieve helpful and useful work related information (Flight schedules, etc). You are not authorized to download applications of any sort to the Hudson Server, without express written consent of Hudson Technical Support department.
If you have trouble connecting to the Hudson Server, make sure first that you have internet access from the workstation. If in doubt, check this from more than a single workstation or PC. If you have internet access, but cannot connect to or login to the Hudson Server, call our Tech Support line or send and email to support@hudsonltd.com.
If connecting from a tablet, please reference this article:
http://hudsonltd.com/knowledge_base/Accessing_Hudson_Servers_from_a_Tablet
If you have connected to several remote computers in the past, using the RDP application, it is possible that you will end up with a drop down list of previous server names or IP addresses. If you want to remove or delete the computers from the list, try visiting this page on Microsofts website for a one-step fix-it link that will do this for you—> <a href=”>http://support.microsoft.com/kb/312169#FixItForMeAlways
]]>
This article contains information on how to add / configure one or two employees and assign them to a trip, within HWeb Dispatcher when these employees will serve as chaperone(s), monitor(s), tour guides, etc. These employees ARE NOT considered as drivers. Assigning employee(s) to a trip DOES allow you to track hours for payroll purposes.
These instructions assume you are already familiar with the basics of Hotkey configuration.
One or two
specific employees can be assigned to each trip. The status of the employees are not checked during assignment process, instead it is validated at ‘trip start’. An option has been added to allow the trip’s reservations be be updated with the employee information on assignment.
Note: Requires DB (database version) 135 or greater.
(Hweb 1.89e (3120))
To add an FAVICON to the reservation web site
1. Add the following lines to CSS_SKINFILE after <!—(!HTMLSkinName=HudsonFX,HTMLSkinVersion=100!)—>
<link rel=“icon” type=“image/ico” href=”/images/{sitekey}/favicon.ico” />
<link rel=“shortcut icon” href=”/images/{sitekey}/favicon.ico” />
The file name can be anything, but “favicon.ico” is typically used. The file is typically 16 or 16 or 32 x 32 pixels.
2. Create an icon file and upload it to the site subdirectory in the images directory.
The following link can be used to upload an image and convert it ot an ICON or to create an ICON.
http://www.degraeve.com/favicon/
Note: This icon is global for you entire site. It cannot be changed on portals
]]>
Many international travelers (from outside North America) are used to telling and writing time in a 24-hour format. Within the United States, this is sometimes referred to as military format. In this instance, 00:00 represents midnight, 12:00 represents noon, 13:00 represents 1:00 PM, 14:00 represents 2:00 PM, etc. In fact, if you were to ask a traveler from Europe to write their flight time as 2:30 AM or PM on web reservation site / form, they might be confused and select the incorrect designator.
Effective with Hudson Web version 2.72, you can opt to display your times in either AM/PM (12 hour format) or 24 hour format. To configure your site:
Login to your web based Reservation Utility page
Select the Configuration Tab
Select General Configuration
In the Time Settings section of the page, locate “Time Format.”
From the drop list, select either 12 hour or 24 hour
Scroll to the bottom of the page and click Submit.
Overview
Discount and gratuity exceptions are used with group profiles under the Payments and discounts tab in the HWebAgent profile configuration tool. These powerful exceptions can be used to adjust/override current discounts and or gratuities per profile.
Format: <type code>[:<discount|gratuity>][,<type code>[:<discount|gratuity>] ...
Type code
| Fn | Flight types (where n= D(Domestic), I(International, O (Other), R(Request) |
A,C,H, P | Location types (airport, corporate, hotel and place) |
Dn | Direction types (where n=A (Arrivals), D (Departures) etc.) |
Sn | Service types (alternate format) |
Mn | Meet & Greet option (MN, MW, MS, M2, M3) ** |
Other | Location key (either pickup or drop off) |
Discount or gratuity value (rate)
Numeric value | Use the default discount or gratuity calculation method, but change the value |
Fn | Force fixed rate calculation (when default is a percent), n is the fixed value |
n% | Force percent calculation (when default is fixed rate), n is the percentage value |
No value specified | Assume zero value |
Example 1.) P,C:10%,H:1.00,1:2.00
This indicates that places will have a value of 0, corporate locations will have a value of 10%, hotels will have a value of $1.00, service type 1 will have a value of $2:00. All non-matching criteria will use the default type and rate.
Example 2.) DA&S1:10,DD!S2:5
This indicates that arrivals AND service 1 will have a value of $10, departures OR service 2 will have a value of $5.
Example 3.) DH:8*%HOURS%
This indicates that hourly reservations have a value of $8 per billable hour.
** The letter codes presented correspond to the following Pickup Extra configuration options:
Below is a list of the most commonly asked questions about PCI Compliance and the Hudson system.
Any business that accepts credit cards will have an established relationship with a bank or credit card processor. As part of any agreement you signed with that processor, you have agreed to be contractually obligated to observe very specific security procedures in your business. This includes who has access to credit card information, how that information is recorded and stored, how you connect to the Internet and much more. Instead of each bank having their own requirements, most adhere to the standards put forth by the Payment Card Industry (PCI) Security Standards Council (SSC, aka PCI-SSC). This organization is comprised of the major credit card issuers (VISA, Master Card, AMEX, etc.). To be PCI compliant or PCI certified, you must 1) adhere to PCI standards in your business or obtain PCI certification, 2) use a PA-DSS accepted payment application in order to process credit cards. While Hudson delivers on item #2, you as a business must complete item #1. For complete information on PCI Compliance for Merchants, please visit: PCI for Merchants.
PA-DSS Acceptance is a process that software vendors undergo to ensure that the way they process and store credit card data falls within the PCI-SSC standards and guidelines. PCI Compliance is a process that merchants (Hudson clients) undergo to ensure that their business practices protect the security of their clients credit card data. The link below will allow you to watch a Quick Time movie that explains the differences in these two programs and how they both effect you and your business.
...or watch it right now on YouTube.
The HGTS suite uses a unique and very secure method of encryption (and always has). Credit card numbers are encrypted dynamically with a unique encryption key that changes for each and every record / reservation. HGTS generates a key that is a combination of the credit card number (which varies with most every reservation) the reservation ID (which is never duplicated) and other information from the reservation. This means that there is no single key to manage, protect or change and that a different encryption key is generated for each and every reservation / transaction in HGTS. Due to the robustness of this encryption process, which far exceeds the PA-DSS requirements, it is unnecessary to modify or change the Encryption Key in the Hudson system; this virtually eliminates the need for clients and users to have a key management policy in place.
Many layers of PCI compliant security have been built into Hudson systems. This begins with unique user access privileges in the HGTS local and web systems. A system administrator creates unique login accounts for their business. Each login account is protected with secure passwords. See Login Security for detailed information regarding the login security options. Each account is then reviewed and privileges are assigned based on that users function in the business. For example, only accounting staff should have the ability to generate invoices. The number of user access privileges is continuously evolving. When new features are added, a corresponding user privilege is often added and by default the privilege is disabled, unless later changed by a system administrator. Hudson clients have autonomous control over all levels of user access.
If you are a using Hudson’s Cloud Computing offering, then your entire reservation system is hosted on state of the art web servers that you access via the Internet from your office. To ensure the highest standards of security possible, Hudson neither owns nor has physical access to any of the web servers. Hudson employs the professional technical services of a hosting provider; INetU. This managed hosting provider has clients from the banking, finance, insurance and medical industries all of which have rigorous data processing and storage security requirements. To meet those requirements, INetU has to exceed the PCI standards outlined above. INetU servers and databases that Hudson clients are using and accessing are all PCI Certified. For more information on the PCI compliance of our managed hosting provider, please visit their site at http://www.inetu.net/Assurances.aspx
Well - sort of! This isn’t really the right question to ask. Only a business who accepts credit cards as a method of payment can be named “PCI Compliant” or “PCI Certified” therefore the Hudson system can never be called PCI-Compliant. We are however PA-DSS Accepted, which is actually even better. The Hudson Group has always observed the most stringent levels of security while developing its various systems. Each time Hudson integrates with a new credit card processor, we are checked and reviewed to insure that credit card security is observed at all times. As Hudson has grown and expanded and is being selected as the payment application of choice by larger transportation clients around the world it finally became appropriate to undergo the very stringent Payment Application-Data Security Standard (PA-DSS) evaluation process. Hudson has retained the services of Trustwave, an approved Qualified Security Assessor, to test andreview the HGTS product and how it processes credit cards. Begun in the spring of 2012, it took about 5 months for Hudson to meet all of the documentation requirements for PA-DSS acceptance. As of late December 2012, the HGTS application (version 1.94) has been named a PA-DSS Accepted payment application when installed and run on a Windows XP SP3 platform. Hudson is the first in the ground transportation software industry to achieve this designation according to the current (version 2.0) security standard. A list of accepted payment applications may be found at Validate Payment Applications. As 2013 continues, we will have our system evaluated for PA-DSS Acceptance on additional Windows Operating Systems. This will validate that the application performs in an equally secure manner on additional platforms. We will then be submitting additional systems and products to the same scrutiny and review process, including our Web reservation and mobile device systems.
The source for all official information and documentation regarding PCI requirements is found here: https://www.pcisecuritystandards.org. You can and should also consult with your current credit card processor(s) for their requirements which could be slightly different.
A quick reference guide for Merchants has also been added to the Hudson KB document: PCI Documents - Links.
If you are looking for broad based tips from a PCI security firm on how to reduce security vulnerability in your office and how to implement good security practices among your staff, consider visiting the Trustwave Security Resource Center.
Part of a merchant being PCI compliant involves establishing a Data Retention Policy. This is an internal program whereby you determine for what period of time you will keep sensitive client data in storage. PCI standards require that you keep information for the shortest period of time necessary for the normal operation of your business. While many don’t think about it, it really should not be necessary to retain credit card information on old or stale reservations, user accounts, etc. If a customer has not used your service in 3 years, it is likely that their credit card has expired anyway. This expired information should not be saved or stored indefinitely. Reservations that were completed and paid more than a few months ago will also contain credit card data that should no longer be needed. Your Data Retention Policy defines how long you will retain this kind of information as well as how often you will purge stale records and how that purging will be accomplished. To be PA-DSS compliant, Hudson provides the ability for a system administrator to purge sensitive data from reservations, user profiles and payment transaction records (NOTE: purging data only removes credit card details - the user profile, reservation and transaction histories are not lost). More information on how to purge this data may be found here: PCI Compliance - Credit Card Data Purging.
Hudson will enable all new systems with PA-DSS accepted settings. If you modify system security settings such that they fall below the minimum PCI defaults, you may be exposing your business to increased security threats and ‘breaking” the compliance of your system. For information on how to use your system so the PA-DSS acceptance remains, please obtain, read and adhere to the Hudson PA-DSS Client Implementation Guide. File:Hudson PA-DSS Implementation Guide.pdf
We already have and will continue to do so….by ensuring that our applications, products and services are PA-DSS Accepted. By delivering applications and services that meet these stringent guidelines and are inherently secure, your task of becoming PCI Compliant is greatly improved. Without a PA-DSS accepted application, your business cannot become PCI Compliant. You must however use the products as they were designed and as outlined in the Hudson PA-DSS Client Implementation Guide mentioned in the previous Question and Answer. There are many additional items you will need to evaluate and achieve, on your own and independent of Hudson, in order to achieve actual PCI Compliance. Think of it this way: Hudson has bult a very secure “safe” in which to store all cardholder data. You, as the end user, must ensure that the door to the safe is not left open, but is closed and locked - thereby ensuring true security. The process you go through, with or without the assistance of a licensed PCI approved Quality Security Assessor ensures that the door to that safe is always locked and sealed.
]]>***********THIS ARTICLE INCOMPLETE*************
Hudson considered integrating a 3rd party maintenance tracking module into its suite of products but could not find a program that was both simple enough for those clients who only need a simple and basic vehicle maintenance tracking system and simultaneously sophisticated enough to manage companies that have robust in-house body shops and repair facilities. Additionally, we wanted to be able to tie any maintenance program into existing technology, making it possible to page drivers from the Dispatcher grid when Dispatchers determine that vehicles on the road are in need of routine maintenance.
The result is that Hudson developers and engineers sought a way to create a custom system capable of being configured to meet the needs of each unique deployment. By using existing technology, we have built a system that is simple yet robust. As the clients needs to track and manage their maintenance grows and expands, the system will grow and expand with them.
The basic or default system outlined below can be used to track and manage all routine scheduled maintenance items along with tracking and managing services performed in line with Technical Service Bulletins (TSB’s) that are routinely issued by vehicle manufacturers.
There will be a shortcut created for you named Vehicle Maintenance, or similar,
The default Vehicle Maintenance desktop opens and displays 3 key grids:
The Vehicles List Grid contains 2 default tabs, Vehicles and Service Bulletins (TSB’s) colored green and yellow respectively.
The Vehicles tab (Green) contains a list of all vehicles in the fleet that have a status of: Clear, Available, Active, Holding, Deadhead, Airport Sweep or OOS (Out of Service). Vehicles that have a status of LTOOS (Long Term Out of Service) are hidden from view. The intent is to include on this list, all vehicles in the fleet that are capable of being put on the road and assigned work, including vehicles that may be temporarily out of service or unavailable due to maintenance issues. The list is defaulted to display vehicles in ascending order according to their name, as defined in the vehicle configuration tool. The most commonly used vehicle detail fields are displayed. The displayed fields may be adjusted to meet the specific needs and requests of the client. Using a mouse, click to select any vehicle in the fleet.
The Service Bulletin Tab (Yellow) is where new Technical Service Bulletin (TSB) work items can be entered and where previously entered TSB’s may be viewed. A TSB is a notice that is issued by a motor vehicle manufacturer and then provided to fleet managers, auto repair centers, certified technicians, rental services, etc. A TSB is often issued when a vehicle defect, which does not effect vehicle or passenger safety, is discovered by the manufacturer and where the defect does not warrant a recall. By sending TSB’s to vehicle mechanics and service centers, the goal is to have the repair facility adjust or repair those items the next time the vehicle is in for routine or preventative servicing.
How to go about getting Technical Service Bulletins: Manufacturers are required to submit TSB’s to the National Highway Traffic Safety Administration (NHTSA). While the NHTSA will provide requested TSB’s, they do not allow subscribing to all new TSB’s. If you wish to receive all new TSB’s automatically, you will need to contact the manufacturer directly. The best place to call is the Customer Service number listed in your vehicle Owners Manual. As an example, Ford issues TSB’s every 2 weeks for the vehicles they manufacture. One place to find “old” TSB’s and search by manufacturer is: SaferCar.gov.
The information located on these tabs (also colored green and yellow respectively) is designed to display more specific details, when an item has been highlighted or selected in the top grid. To view the
]]>The archiving of reservations and trips is a tool used to move completed reservations into a different table of the database. When reservations/trips are moved to the archive table, only those users with special permissions can access these reservations/trips. Archiving of reservations and trips helps keep reservation entry and system operation at peak efficiency. Most functions, including credit card processing and Invoicing may still be completed after reservations have been moved to the Archives.
Prerequisite:
In order to perform the archive function, it is necessary to have the proper system privileges enabled. Have your system Administrator go to: Configuration -> User Access. For each member who will be performing the archive process, locate and enable the following:
1.) RESERVATIONS:
2.) TRIPS:
To view or access a Reservation that has been archived:
To change back to the current records table, repeat the process but select Current records from the drop down menu.