Vehicle info/maintenance db

[maw230]

Does anyone know where to find a free access db that stores information on vehicles from general info to maintenance? I'm in the process of making one for myself, but wouldn't mind seeing what others have done.


Edit: this will be used at home to manage a few vehicles

 

[maw230]

Have look here for ideas. http://www.databaseanswers.org/data_models/

Their vehicle maintenance data model is pretty robust; probably too much so to manage only a few cars, but it's a good reference.

 

[wind20mph]

I created the same sometime in December 2013. I used 2 tables, 1 for Vehicle/Equipment List and the other table is vehicle/Equipment History.

What is recorded in the Vehicle table are the description of Vehicles, bodyno, serial, plateno, type, model, date acquired, purchase amount, and assignemnt/location.

In the history record are the, records of Preventive Maintenance/Corrective/Repair Details, Materials/Items Used, Cost, Date, Reference Code/Service Report, Remarks, Other info such as Back job. And has a recommendation. That concept was gathered from ISO procedures for Preventive Maintenance and Repair. that is to completely monitor, control and suggest if the service vehicle is for salvage value or for maintenance and will determine if the cost of maintenance vs the cost of new equipment for replacement and can justify status of every equipment/vehicle.

 

[maw230]

Currently, I have 4 primary tables:

1. VehicleMstr
2. MaintMstr
3. FinanceMstr
4. PartsMstr

VehicleMstr contains all of the basic car info i.e. Model Year, Make, Model, Owner, Purchase Mileage, MPG.
MaintMstr is used to record all maintenance items i.e. Maint Type, Desc, Hours, Cost, Mileage Performed, Mileage Recommended, Notes
FinanceMstr contains all the financial information.
PartsMstr contains the parts used or recommended for the MaintMstr records.

I may create an InsuranceMstr at a later date.
It started as a way to track performed and recommended maintenance, so that I could setup alerts when Maintenance was coming due. Since then it's become a general vehicle information db.

 

[maw230]

My only criticism so far is the spaces in your field names, and the use of Desc which is a Microsoft Access Reserved Word. If you have a screen shot of your relationship window, with all the fields shown that might be helpful.

Those aren't the actual field names. Wanted to describe them instead of list them and leave people confused. Desc is not used either.

 

[jdraw]

maw230,

Do you have a 4-5 line description in plain English of what your database is about? It may help you and others if you describe the things involved and how they are related in business terms.
My recommendation is to build a high level model of all the pieces. You can focus and provide more detail on the part you will do first, but because you have the high level model, you'll will know how the Insurance or other pieces to come in future will fit into the bigger picture.

Think of this high level model more as an artist's concept of a new building. You have an overall picture of the "building", but you can work on the foundation, first floor etc, without worrying about the penthouse interior decorating at the moment.