If you are writing in Perl, and it will be open-source, then I will help <img src="/forums/images/graemlins/lol.gif" alt="" />)
Other ideas could be:
- Gas milage information, with fields for approx. hwy k's (or miles <img src="/forums/images/graemlins/lol.gif" alt="" />) and city k's/offroad
- Upgrade statistics, how the changes affected fuel milage, speed, performance
- Cost analysis and storage for field trips (for searching, so that next year, you can plan ahead and know pretty well the costs
- Broken parts...over time, you could have a nice searchable index of common trends (especially if several people were to use this in a community environment)
- Picture storage facility for howto docs when performing jobs on a rig
- Someone else mentioned this, but a maintainance schedule, that will send out emails when something is due for maintenance
- A storage facility for scanned documents relating to repair (so when you resell, everything is electronic and easy to find)
- Info on new trails that one finds when they are just cruising around
- Info on trips...how long it took, little shortcuts, nice eateries etc on the way.
An automated purchasing system, so when the girlfriend goes and checks her bank account next time, we can just say "Sorry dear, my silly vehicle tracker program ordered that ARB locker by itself!...HONEST!"...of course, we could just call that a 'bug'

Seriously though. I did start a little web based app, that calculates my km/L to m/gal, and puts it into a db, but that was as far as I got. I just wanted to track trends for gas usage.
Steve