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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

7. LESSONS LEARNED<br />

The HTDC project spanned a period of over three years; covered many facets of research and<br />

engineering; and involved many researchers, engineers, technicians, and industry professions; thus<br />

the lessons learned were varied. They include both positive and negative lessons. Some lessons<br />

learned were immediately incorporated into the testing protocols being employed at the time and<br />

allowed <strong>for</strong> more productive and efficient research and data collection. Other lessons learned were of<br />

a nature that did not allowed <strong>for</strong> more immediate or short-term adaption; however they may be of<br />

possible benefit <strong>for</strong> future research.<br />

For the purposes of this discussion, lessons learned will be discussed in two sections: Positive and<br />

Negative. The negative lessons learned have been separated into corrected/incorporated and unable<br />

to correct/incorporate.<br />

7.1 POSITIVE<br />

Many facets of the partnership development, testing, and data collection proved to be valuable to the<br />

overall program in ways that were not originally identified or fully appreciated. These are described<br />

in the following positive lessons learned.<br />

7.1.1 Lessons Learned from the Pilot Test<br />

Because of the ef<strong>for</strong>t put <strong>for</strong>th by Dana and ORNL in the Pilot Test and by ORNL in the Build-Up<br />

Phase, the DAS system functioned quite well during the FOT. There was very little down-time<br />

related to equipment internal to the test vehicle (VBox, eDAQ).<br />

Lesson Learned: In-situ testing of final equipment configurations, along with n appropriate burn-in<br />

period <strong>for</strong> all systems to be employed in the test is an effective way to insure longevity and robustness<br />

of equipment during a real-world FOT.<br />

7.1.2 Routine Data Collection Procedures<br />

Additional lessons learned in the pilot phase of this project were assimilated during the FOT resulting<br />

in a simplification of the task at hand, or an improvement in the quality of the results. Specifically,<br />

technical problems that were identified during the Pilot Test were corrected and incorporated in the<br />

software and procedures used in this phase. The data uploading and archiving procedures employed<br />

in this phase resulted in quick problem diagnosis and minimal data loss.<br />

Lesson Learned: Data should be downloaded frequently and basic statistics should be generated<br />

closely thereafter in order to determine that the sensors are working as expected.<br />

Lesson Learned: Data should be backed up often to prevent data losses from memory overflow.<br />

7.1.3 Fleet Selection<br />

Schrader is a <strong>for</strong>ward-looking, technology-savvy fleet. This facilitated good understanding and<br />

insightful communication between Schrader and ORNL regarding the HDTC goals and objectives as<br />

well as ORNL’s approach to conducting this research. This, in turn, allowed the integration of the<br />

data collection equipment within the test vehicles of the FOT to proceed efficiently.<br />

101

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

Saved successfully!

Ooh no, something went wrong!