Proposal: Sr-Ht-003 for Huffman Trucking

Proposal: SR-ht-003 for Huffman Trucking

Proposal: SR-ht-003 for Huffman Trucking

Huffman Trucking's central maintenance facility in Cleveland, Ohio and presently has hubs in Los Angeles, California, St. Louis, Missouri, and Bayonne, New Jersey. To effectively manage their business, it is critical that Huffman Trucking can share information regarding vehicles maintenance with each of its hubs, including parts inventory and vendor data.

Huffman Trucking needs a solution that would allow them to share information amongst their various locations. Smith Consulting was engaged to deliver an entity and attribute proposal to Huffman that outlines a database solution. The objective is to bring the proposed database to life and implement a shared database across Huffman's various locations. good intro.

Project Overview

Huffman Trucking needs to improve and ensure maintenance is performed for the complete fleet across all of their locations. Additionally, the project will minimize down time for vehicles in their fleet by ensuring parts are on hand to perform the maintenance. Having these needs met with minimize potential revenue lost due to unavailable vehicles. The goal of the project is to create the entity relationship diagrams that will support the creation of a shared database that can be accessed by all of Huffman Trucking various locations.

The project should take no longer then five weeks. estimate! If more time is needed, a request will be submitted within the first two weeks. good. The life cycle of the database depends on the growth and needs of Huffman Trucking Company. A yearly analysis will be preformed to determine necessary enhancements over the next three years and will be included in the support cost. Good precaution.

Assumptions

While the scope of the proposal attempts to be objective as possible, some assumptions are inherent. The team is assuming that Smith Consulting accurately interpreted all of the entities. Secondly, it is being assumed that Huffman has the necessary infrastructure or the means to put into operation the appropriate infrastructure, hardware, software, and licensing. Therefore, assuming these components will not limit or influence the ERD. good assumptions. In a real life situation, one always has some working assumptions that one needs to document and clarify with the client.

Requirements

In order to ensure a successful ERD, several tasks will need to be executed. The first requirement will be to define the business rules of Huffman's current maintenance program. This will be conveyed by drafting a Data Flow Diagram. One of the constraints we are presented with is the potential lack of documentation. One way to overcome this constraint will be to interview subject matter experts and the key players involved in the maintenance process. very important step.

The second requirement will be to draft an Entity-Relationship Diagram (ERD) based upon the business rules and the entities, which were captured by Smith Consulting. All of Huffman's hubs will use the database and with that, will need to be robust enough to handle the volume. In addition, data anomalies such as redundancies must be eliminated by normalizing the tables. One of the challenges will be to find a balance between normalization and performance. agreed, always a challenge is a high-performance transactional situation. For the case of Huffman, this may not be an issue.

The third requirement will be to construct a prototype of the ERD in Microsoft Access. The prototype will then be populated with a small sample of data. This will ensure the ERD will be robust and has in fact eliminated any data anomalies.

Impacts and Benefits

The cost of Huffman Trucking project includes, but is not limited to programmers, personnel for implementation, training personnel, project analysis, yearly analysis, and support personnel for a three-year period. Any enhancements during this period will be extra and determined at the time of request. The total cost shall not exceed $80,000. putting a dollar figure is good.

Benefits regarding this effort include but are not limited to the following:

* More efficient maintenance program.

* Reduced parts and labor overhead connected with inventory and ordering.

* Less likely to miss maintenance leading to reduced unscheduled maintenance.

* Allow data sharing across Huffman Trucking Corporation.

* Standardized record keeping across all of the companies locations

* Establishing an environment that will support a new record keeping front-end that can be made available through the intranet website great

There will also be several opportunities that will grow from this project. In the future, analysis of this data will lead to even more improvements in the maintenance program here at Huffman. Opportunities regarding this effort include but are not limited to the following:

* Automated parts ordering

* Automated settlement with parts vendors

* Automated maintenance schedule proposals based on historical trends.

* Enable maintenance to be performed in any of Huffman's hubs regardless of the vehicles home hub location very good.

If this project is not implemented, it will not be possible to automatically share data for each of the trucking hubs. Parts ordering and settlement will continue to be done in an inefficient and decentralized way. Parts inventory will not be able to be shared between hubs and maintenance schedules will be inconsistent between hubs.

Deliverables and Measurement

The required deliverables are Entity Relationship Diagram's for the Fleet Truck Maintenance. This project will accomplish that goal by leveraging the resources of this learning team to develop a concept database allowing for the validation of the data and entities, and will ultimately result in the creation of valid ERD's for the Fleet Truck Maintenance data systems.

Within the scope of this project, it will be very easy to measure the progress and eventual success of this project. Within the five-week timeframe of this project, we will design the data structure, implemented in a conceptual database,