06.08.2013 Views

Class-8 Heavy Truck Duty Cycle Project Final Report - Center for ...

Class-8 Heavy Truck Duty Cycle Project Final Report - Center for ...

Class-8 Heavy Truck Duty Cycle Project Final Report - Center for ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Lesson Learned: A technology progressive fleet helps to ensure the success of a vehicle-based<br />

research project.<br />

7.1.4 Equipment Access<br />

Schrader’s operations model involved the return of all fleet vehicles to their Jefferson City<br />

headquarters each weekend. This allowed ORNL personnel to have weekly access to the test vehicles<br />

and the DASs. The distance from ORNL to Schrader was approximately 45 miles, allowing <strong>for</strong><br />

relatively easy access to the test vehicles and DAS equipment.<br />

Lesson Learned: Periodic access is critical <strong>for</strong> collecting data and to conduct equipment health<br />

monitoring and repairs. Choosing a fleet that has a regular vehicle return schedule as well as one<br />

that has its entire fleet on the same return schedule saves valuable research time and ensures regular<br />

access to test vehicles and the DASs.<br />

Lesson Learned: Choosing a fleet within a reasonable driving distance reduces data collection and<br />

equipment monitoring/repair costs.<br />

7.2 NEGATIVE<br />

Just as with the positive lessons learned, there were arrangements, situations, and events that proved<br />

to be detrimental to the overall program in ways that were not originally identified or fully<br />

appreciated. These are described in the following negative lessons learned. First, the negative lesson<br />

learned that were corrected during the course of the program will be discussed, and lastly the negative<br />

lessons learned that were not corrected will be discussed. Knowledge of the latter may be beneficial<br />

<strong>for</strong> future ef<strong>for</strong>ts.<br />

7.2.1 Corrected Negative Lessons Learned<br />

7.2.1.1 Fleet procedures<br />

Schrader’s standard operating procedure (SOP) <strong>for</strong> its fleet called <strong>for</strong> regular (weekly in some cases),<br />

pressure washing of the tractors. It was determined that this pressure washing was leading to premature<br />

failure of the weather stations due to water infusion into the circuit boards of the devices.<br />

Once the cause was determined, ORNL requested that the weather stations be covered to prevent<br />

direct high pressure spraying. This protective measure corrected the water infusion problem with the<br />

weather stations.<br />

Lesson Learned: A thorough review of partner SOPs to glean possible practices that could be<br />

detrimental to equipment is recommended.<br />

Lesson Learned: Pressure washing of truck mounted sensors can cause premature failure.<br />

Lesson Learned: Effective work-arounds can be identified and implemented in the field.<br />

7.2.1.2 Additional duty-cycle data<br />

Just prior to the start of the FOT it was suggested that aerodynamics data relative to the Volvo VN<br />

660 tractors and the dry-box freight trailers would be of interest to collect during the FOT. At that<br />

point it was too late to plan <strong>for</strong> such data collection (the DAS was at capacity, no additional funding<br />

<strong>for</strong> sensors or additional DAS capacity was available, the MOU with Schrader did not identify this<br />

type of data collection, the suggested data collection method was not minimally invasive, and there<br />

was not sufficient time to instrument the vehicles or test the sensors prior to starting the FOT).<br />

102

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!