This company’s primary strength over time has been our ability to stay in the forefront of functionality and ease of use.  Since our first software release in 1993, some seven(7) years after the company’s origination, we have pursued an aggressive software development strategy.  At the present time, our software update/release cycle is approximately every 14 days as we race to refine Version 2.0.  This pace will slow to every 30 days, then every 90 days and eventually to every 180 days as the months go by and we begin to fulfill our most immediate development needs. 

The recent release of ExtraFleet Version 2.0 represents a major leap forward similar to the changes we made during the transition from Win 3.1 format to Win 9X.  Version 2.0 was designed to make the best use of Visual FoxPro Versions 8.0, Windows XP Professional, and Windows 2003 server.  MS Visual FoxPro™ is the core software development system we use as the basis for the single, LAN, TSE, and Global Access programs and the front end for the client server version of the program.

We are at the front end of a long term development cycle.  The recent introduction of the ShirtPocket WorkStations, the new user interface, and new tools like Report Designer are all avenues for further development.  Added features and functions like customer files, variable customer mark-ups, automatic sales tax, accounts with budgets and vendor contracts are other areas that will evolve with time.

One of the most fascinating areas is the ability to support multiple sites and multiple operating locations over a wide geographic area.  This is an area of high potential growth for both the software and the company.  So far we are scratching the surface on the opportunities this form and structure represent.  More than anything else, our goal is to provide a more efficient and effective work environment.

In addition to adding new programs for the ShirtPocket WorkStations, we will continue to pursue the entire concept of putting data entry as close as possible to the time and place of the activity.  This concept has served fleet maintenance very well ever since the days of the first electronic fuel interface that took driver entered fuel transactions from the service island and brought them directly into the fleet maintenance management system.  We will continue to be very interested in technologies that avoid duplication of data entry.