Search Results

Commercial vehicles carry more than 10 billion tons of goods - approximately 70 percent of all freight shipped and travel over 450 billion miles each year in the United States. These vehicles are the exclusive mode of delivery in over 75 percent of U.S. communities. Such utilization and dependency demand commercial vehicles be reliable, durable, and cost effective. The heart of these commercial vehicles (Classes 3-8) is the diesel engine. The widespread use of the diesel engine can be attributed to its reliability, durability, and cost effectiveness. However, the 2007 and 2010 EPA emissions regulations are creating significant challenges for diesel-powered commercial vehicles. Engine and vehicle manufacturers must strike a balance between emissions, performance, and affordability. A consequence of the evolution of the diesel engine to meet the increasingly stringent emissions regulations is that more effort to accommodate the associated changes is driven to the vehicle manufacturers.

The successful development of new products is contingent on clearly understanding product requirements and defining appropriate design activities to deliver the right product. Even if one can clearly understand the abstract requirements implied by the voice-of-customer (VOC), engineers still work best to a set of specifications that define the product in objective measures. The task of extracting the systems specifications from text versions of product requirements is not trivial. Full order dynamic models of mass, springs and dampers provide understanding of vehicle performance; however, the engineer has to define the dynamic characteristics based on his understanding of requirements and translate them into technical specifications. The result can be too dependent on human assumptions and judgments at this point. This work was done to understand how to apply Object Oriented Design (OOD) methodology to trace requirements of a mechanical system to design parameters.

This paper describes how mind mapping software can help to visualize: System performance requirements Product attributes that satisfy performance requirements Mapping between performance requirements and product attributes An example is given using a partial model for vehicle performance developed by the International Truck and Engine Corporation. The mind map software used in this study is Mind Manager Pro version 6 by Mindjet. Anecdotal evidence is offered for the benefits and challenges of implementing a visual Mind Map scheme; however, the judgment of overall effectiveness is left to the reader.

In the present work computational fluid dynamics (CFD) simulations of the flow field around a generic tractor-trailer truck are presented and compared with corresponding experimental measurements. A generic truck model was considered which is a detailed 1/8th scale replica of a Class-8 tractor-trailer truck. It contained a number of details such as bumpers, underbody, tractor chassis, wheels, and axles. CFD simulations were conducted with wind incident on the vehicle at 0 and 6 degree yaw. Two different meshing strategies (tet-dominant and hex-dominant) and three different turbulence models (Realizable k-ε, RNG k-ε, and DES) are considered. In the first meshing strategy an unstructured tetrahedral mesh was created over a large region surrounding the vehicle and in its wake. In the second strategy the mesh was predominantly hexahedral except for a few narrow regions around the front end and the underbody which were meshed with tetrahedral cells owing to complex topology.

This paper discusses a practical use of the Systems Engineering Process as it is implemented in a Truck OEM. The process presented is focused on the Electrical and Electronics area, but can be applied to other systems on the vehicle and to the vehicle level requirements. Systems Engineering rationale is summarized based upon historical impacts and the application of Systems Engineering to address those impacts. Prior System Development Processes are reviewed in light of modern Systems Engineering approaches, leading to the synthesis of the Systems Engineering Documentation Set for the Vehicle and the Vehicle's Electrical and Electronic Systems. The analysis for this approach looks at the application of Systems Engineering Principles throughout the lifecycle of the vehicle, going beyond the boundaries of traditional requirements gathering and analysis.

This paper describes the electrical system development for the headlight feature in an International High Performance Vehicle. Systems engineers developed several iterations of functional requirements, functional block diagrams, state diagrams, and body controller software requirements early in the development cycle at considerable engineering expense. The hardware design team found the functional block diagrams useful, however the software design team did not find the other artifacts useful. The software design teams chose to implement a design that was very similar to a current product offering and did not map to the system proposed by the systems engineering team. This paper provides examples of the Systems Engineering artifacts and shows when they were developed in the project timeline.