Huffman Trucking Case

This week, the team will continue to work on creating a vehicle maintenance database for Huffman Trucking. Now that the entities and attributes have been determined and the tables for the database have been created the team will now enter in fake realistic data into the tables so that the database can be tested.

This week for my participation in our team assignment I have entered in some of the data that is needed for the tables in the database. I added 10 different types of maintenance descriptions along with the other attributes of the maintenance description entity. I entered in the data for the vehicle maintenance and maintenance work orders entities. I also adjusted the vehicle type entity to comply with the types of vehicles that Huffman Trucking might have.

For my required participation this week for the learning team assignment, I entered three tables worth of data. I filled in items such as the information for the tables for: individual vehicle, parts history, and tire maintenance. All of these assets are quite important as each of these items need to be tracked quite frequently for the Huffman Trucking Database. It is important to know what each vehicle may have as far as required tire rotations, to ensure that safety expectations are met. Parts history is important as far as inventory is concerned so that the risk of audit is kept down low. Each individual vehicle must be tracked so that the communications department will know which vehicles should be tracked, and others that should not be.

I have added some tables also, especially in regards to tire pressure levels. I have also added some mechanic names, for accountability purposes. This will eliminate confusion with pay, especially if it is piece-rate work. It is also smart to have a record of who does what to each vehicle, so that the specific mechanic can properly be addressed if any issues come about.

This week we started with four tables and needed 11 tables total. I created the remaining tables with primary keys and attributes. In the database I have erased the previous relationships because referential integrity was not turned on. It seems there was a problem with auto number. I changed the auto number to text for some of the PK's and then turned on referential integrity. I also on and changed the name of some of the PK's so that they were not duplicated as PK's of another table. I wrote a brief document explaining the creation of the entity relationship diagram in Visio in APA format.