Refine Your Search

Search Results

Viewing 1 to 3 of 3
Technical Paper

Compact Post-Aftertreatment Temperature Control Device for Exhaust Gas Cooling

2007-10-30
2007-01-4199
This paper presents a compact temperature control device to cool down hot exhaust gas coming out of an aftertreatment emission control system. Active DPF (Diesel Particulate Filter) regeneration is required for aftertreatment emission controls to meet the 2007 EPA (Environmental Protection Agency) PM(Particulate Matter) standard. However, regeneration of the DPF temporarily elevates temperatures in the filter to eliminate accumulated soot. This can increase the temperature of the exhaust gas. The temperature control device in this paper draws ambient air into the hot exhaust stream and mixes them together in such a fashion to maximize temperature drop and minimize back pressure for a limited space without any moving parts or supply of extra power. The simple and compact design of the device makes it a cost-effective candidate to retrofit to an existing aftertreatment system.
Technical Paper

Physical to Functional Mapping with Mindmap Software

2006-10-31
2006-01-3493
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.
Technical Paper

Systems Engineering Efforts - What, When and How Much?

2004-10-26
2004-01-2615
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.
X