Automated Vehicle Location System

The vendor required to provide automated vehicle location system (AVLS) are to give the highway maintenance contractors (HMCS) the capability to better manage their fleets in an efficient and productive manner and also give the department a tool to monitor and audit the HMCS’ work safely.
- Fleet tracking and management system (FTMS)
•    The asp shall track all vehicles that are designated by the department to be monitored by AVLS at all times. 
•    The asp shall maintain an online (internet-based) FTMS accessible by the HMC and department staff 24 hours a day, seven days a week throughout the calendar year.
•    The system’s mapping shall have modern mapping functionalities, and shall also include map layering capabilities such as satellite images and the department’s AVLS segment buffer map. 
•    This online FTMS shall be kept maintained technologically up-to-date as much as possible, in order to take advantage of possible new AVL equipment capabilities and online functionalities. 
•    The asp shall capture, store and archive all incoming raw data from the HMC vehicles in real time and provide reporting capabilities on current and historical data.
•    Requirements for the AVLS data collected from vehicles are listed below:
o    The minimum data required to be collected from all vehicles other than patrol vehicles includes the following: HMC name, operator id, type of vehicle, vehicle unit id, IP address, GPS coordinates in longitude and latitude, GPS data status, GPS ground speed, direction, date and timestamp, spreader type, spreader on/off, spreader pausing, spreader rate, material type, material set rate, material actual rate, material quantity, blast on/off, pre-wetting rates, pre-wetting on/off, pre-wet quantity, blade and plow and wing positions (up/down), billing switch status, ignition status, air temperature, road surface temperature, and other future input data fields.
o    For patrol vehicles, the minimum data required to be collected includes the following: HMC name, operator id, type of vehicle, vehicle unit id, IP address, GPS coordinates in longitude and latitude, GPS ground speed, direction, date and timestamp.
o    While receiving data from vehicles, the FTMS shall provide appropriate feedback responses to the AVL equipment vendor on whether the data received is acceptable. 
o    If there are issues with the data received, then a response shall be sent to the AVL equipment vendor that states the specific attributes that are generating errors and the reasons for them.
o    The FTMS shall provide reports with information on material usage and actual plow kilometers for each vehicle based on user-defined time periods.
o    The FTMS shall produce a detailed vehicle report showing a record of each vehicle. 
o    The user shall be able to select one vehicle, multiple vehicles, or all vehicles to report on.
•    The asp shall be responsible for ensuring that their application programming interface (API) is fully compatible with all current and future AVL equipment vendors.
•    Each vehicle’s AVL equipment is to have onboard non-volatile permanent memory capable of storing up to eight days’ worth of data points.
•    The asp shall use the department’s shapefile of AVLS segment buffers for AVLS tracking and billing, and make this buffer map one of the available map layers on the tracking system.
•    The system shall also include an additional map layer for winter performance assessment segments, which are different from the AVLS segments and are used for tracking HMC performance.
•    The FTMS shall display a different-colored icon for each HMC company, and when clicked upon, a pop-up window shall display the date and time, the vehicle id, asset type, HMC company, vehicle status, location address, GPS location Lat and long, CMA number, account, serial number, timestamp of last comms and last GPS, vehicle speed, heading, AVL equipment actions, rate of material application, operator id, ambient temperature, and road temperature.
•    The system should be capable of retrieving and displaying real time in-cab camera feeds, if and when the applicable hardware is made available by others and is producing images.
- Automated billing system (ABS)
•    The HMCS are under contract with the department to cooperate and provide the real time data to the department’s ABS through the asp’s systems, but the asp is responsible for coordinating with all the AVL equipment vendors employed by each HMC.
•    The asp shall obtain all the required raw data in real time from the AVL equipment in the HMC vehicles, and shall ensure all data attributes and formatting are compatible with the ABS and the asp’s systems at all times. 
•    Any costs associated with this effort shall be included in the proposed unit costs to the department
•    The asp shall maintain an online (internet-based) billing system accessible by the HMC 24 hours a day, seven days a week throughout the calendar year.
•    The overriding principle of the existing billing system is that the department will pay the HMC only when their vehicles are moving on billable AVLS segments, and all stop times shall not be considered billable.
•    Additional billing system requirements include the following:
o    Whenever the worksheet line contains an unknown segment, that line shall automatically become non-billable (regardless of the billing switch’s position) and become grey-highlighted in the worksheet. 
o    The ABS shall remove any Zero-Hour lines in the worksheets. 
o    The software shall be able to accept new data inputs coming through the AVL equipment or auxiliary weather equipment such as road weather sensors (e.g., air and surface temperatures, etc.). 
o    This may include a full suite of sensor outputs from a new type of mobile road weather information system (RWIS) hardware that may be installed into the vehicle. 
o    This shall also include the ability to capture anti-icing application and tow plow sensor inputs.
o    The HMC shall have the ability to edit the operator id on multiple lines at a time.