Retail Petroleum Equipment

Fleet Management Bid Specification SP-7178 01/12 Gasboy│7300 W Friendly Ave│Greensboro, NC 27410 9 The software shall support multiple fleets and multiple departments. The software shall synchronize data with all sites. The software shall be used as a centralized issuing and programming facility for passive fuel rings, vehicle data modules and Mifare tags. The software shall be installed on the host computer running Windows operating system and SQL database that supports ODBC connectivity. The system shall be a centralized web server communicating with all sites to provide centralized data base and on-line network access for fleet managers, key personnel and remote maintenance entities. The software shall communicate with all sites to provide 24/7 on-line access through the network. The software shall create and control several fleets and departments and support different privilege levels for limited access for different users (for example, a specific Fleet manager shall only be able to manage only his fleet vehicles). The software shall provide advanced on-line services for multiple sites and multiple fleets in a region. The host software web interface shall use SSL security. The software shall provide secure log-in through the Web for each fleet manager, for monitoring & control and report generation including exception reports. The host software application can interface to other applications via Web Services, import and export of files to FTP and ODBC standard. The software shall allow Exporting data to different file formats (using a dropdown menu) such as CSV, TXT, and XML. The user interface for all software components shall be a web browser. Mifare tags, fuel ring and vehicle modules shall be defined and associated with unique numbers to the fleet vehicles. 11.2 Limits and Restrictions Host software shall allow limits and restrictions to be configured either by an authorized user or imported from a different external system (using the import/export). The rules shall be transferred to every site controller to enable off-line activity in case of communication failure; hence a fuel site will be able to refuel a vehicle within its set of limits and restrictions, when communication is down. The limits shall be ‘pushed’ into the site controller at a predefined time or for a predefined period of time. Site controllers can also use the limits in an off-line mode (in case of communication failure). There shall be a graceful period of time (parametric) for this off-line mode since the vehicle could refuel also in other sites (above its limits) while the sites are disconnected from the host computer. Customizable vehicle and driver limits and restrictions shall include:  Limit of daily, weekly and monthly refueling volume in gallons as well as in currency.  Enable or disable vehicle refueling on specific days (weekdays for example) and / or specific time slots within a day (night time for example)  Limit the maximum refueling sessions for a specific vehicle per transaction, per day, week or month.