Huffman Trucking Service Request HT-03 Team D- Nikki Allen, Tom Philp, Brandon Rose, Michael Sandon and Tara Serna
DBM/380
April 9th, 2012
Paul Cooper

Huffman Trucking Service Request SR-HT-03
Huffman trucking is in need of a change that will help the company organize their data for maintenance and parts on their vehicles. The company has put in a service request for a database that will help the company improve efficiency and maintain records while also helping by increasing productivity. The service request includes several steps that need to be taken in order to complete this task. “The database development process consists of three major stages: requirements, design, and implementation” (Kroenke & Auer, 2012). One by one the request will be described in detail in what process are being taken to design the database that Huffman Trucking will use.
Service Request
The Huffman Fleet Maintenance database was created using Microsoft Access which is a database management system. Team D accessed the Huffman trucking Intranet site to gather all information required to create the database. Here is a look at the tables: One member created the database and in each table there are different columns that are to be filled in with the required information for the company. This is the start to a database that the company can utilize to improve workflow tremendously.
Entities and Attributes The Entities and Attributes for Fleet Truck Maintenance will be discussed. We will go into detail about how they would be used in the database, and how the information could be linked to another using a “Relationship”. We will begin by discussing the purpose of the database and what it will be used for.
The purpose of a database in regards to any company is to be able to keep track of a vast amount of information for a later purpose. In the database the requests for information are called queries. We can take the information from the different files listed above and insert them into a database, therefore being able to keep track of the information about several different things at any one time. We are able to look at this information and see that as time moves forward, the information will grow and records and columns, tables and keys will be created, making searching for several records from several tables as simple as calling upon the right conditions within the query
The database will go into more detail, but will also yield the right search parameters as well. We have the parts inventory and ordering sections, which are linked together to ensure that the correct amount of inventory is kept in the system and when an inventory part or parts are needed, that they are ordered. The database will also be linked to the parts catalogue, which will show all the parts that the company will use in the maintenance of the equipment. There are also vendors and parts purchasing history, which will all be linked together in the parts inventory and ordering sections. All of these things will all be linked together within the database themselves.
The next step of the database to look at, are the Maintenance records. The Vehicle Maintenance contains all the maintenance that was done on the vehicle including tire maintenance specific to maintenance done on each vehicle. The maintenance descriptions contain the description of the work that has been done to the vehicles. The Vehicles table and Work order table will be linked together in the way that the vehicle states what vehicles are being worked on. As well as the work order table, the table states the different work orders that were put into the system, and all of these things will work together as they are linked together within themselves. When a work order is placed, the parts needed are deducted from the system, and the inventory is adjusted accordingly. When orders need to be placed, vendors are selected and inventory is ordered from them and tracked using the system.
ERD
The service request for