Reference no: EM132381224

Project - Interim Report Assessment

Title: THERMAL MANAGEMENT OF EV BATTERY PACKS

Objectives

• To analyse and quantify the thermal (Heat) management needs of Electric Vehicle battery packs and apply appropriate thermal management 'techniques.
• To develop an understanding of the relevant aspects that influence the thermal management needs of EV battery packs.
• To Identify and analyse current thermal management systems used in EV battery Packs.
• To establish and quantify key parameters. To identify and analyse current thermal management systems used in EV battery Packs and establish and quantify key parameters.
• To identify and analyse current thermal management systems used in EV battery Packs and effects on main grid.

Note - Need someone on electrical field who knows matlab. These need to be done on Matlab platform.

Final Project Report Format -

This should follow the format given below. However, note that by following this format you are not guaranteed a good mark! It is the content under each heading that will determine the mark you get.

1. Title Page

This must be on a separate page immediately following the cover of the report (maximum length 15 words). Also give your full name, number, course and submission date below the title.

2. Statement

At the bottom of the title page you should include the following statement: This report has been submitted for assessment towards a Bachelor of Engineering Degree in . . . . . . (subject). . . in the School of Engineering, London South Bank University. The report is written in the author's own words and all sources have been properly cited.

3. Abstract

The abstract should be a short summary (about 200 words) of the report and include the aims/objectives of your work, the methods used and your main results/achievements/conclusions. It should be written last, after the main report is finished. It can be distilled from the introduction, conclusions and recommendations of your report. Abstracts play a key role in engineering and scientific reporting. They tell the reader what your work is about and what has been achieved. If the reader is interested, they can continue reading the report. If not they will have wasted little time. It cannot be stressed how important it is to write an effective abstract. Any written work you do for a future employer will require an executive summary or abstract and must be done properly.

4. Contents Page

5. Introduction

This 'sets the scene' and gives the reader a brief background to the general area of your project. Describe in general terms what you are doing and why. The introduction should also guide the reader through your report e.g. what is addressed where. This section should be long enough to cover the essentials but short enough to maintain interest.

Final Year Project Module Guide

6. Aim and Objectives

• Aim - Give the main aim of your project. This is what you hope to achieve by the end of the project. Try to make this as specific as possible so that you and others can assess how successful you have been at the end of the project. Your aim must be realistic and achievable.
• Objectives - These are subsidiary aims whose completion will enable the main aim to be met. There can be several of these. Again try to make them specific and measurable wherever possible.

7. Deliverables

Deliverables are the main outputs of the project e.g. the final report, any hardware you will construct, software, user manuals etc. Deliverables are obviously related to the aims/objectives. List the key deliverables for your project.

8. Technical Background and Context

This sets the scene for your project work in more detail and gives a description of the field. It reviews and summarizes the existing knowledge (theoretical, practical, experimental) available in the 'literature' (text books, journals, patents, etc) i.e. the work other people have done in the area. You need to critically evaluate this work in the context of your project. Describe why you are doing the project and identify where it makes a contribution to the area e.g. is the work you are doing going to improve anything, make something more useful, add to the general understanding of the topic, etc. References must be given to any literature you cite in your report. Stick to the project theme. This section and the references to published work should bring the reader to the point where he/she is in a position to read and understand your report in detail. It is often the case that students do not do enough background reading and as a result cannot put their projects into context. Do not underestimate the importance of a proper literature search. Make full use of the Library and electronic resources at your disposal.

9. Technical Approach

This is the 'how you did it' part of the report. Describe exactly what you have done and the methods used. Generally topics like scope, design work, construction of equipment, procedures for testing and measurement, etc. are covered here. Any apparatus used to carry out experimental measurements should also be described here. It is difficult to give examples covering all the different types of projects students do because there are so many. If in any doubt discuss with your supervisor what should be covered. You can always do things in more than one way and this section should also describe other methods you have considered and the reasons for their rejection. You should also describe the technical problems you encountered and your attempts to solve them. Don't forget that experiments which go wrong can be important too! Don't whinge about resources and make excuses. Any special safety considerations relating to your work should also be mentioned here. Organise this section using different sub-headings as appropriate for your work.

10. Results and Discussion

In this section you need to present your main results and analyze them in a critical manner against expectations, predictions, models, assumptions etc. For example, if you have done software or a hardware project, the results of testing the software or hardware and a critical discussion of how it has performed must be given here. Present all your results carefully using diagrams, tables and graphs as appropriate. If the results are extensive, (e.g. lots of data tables, graphs/figures, program listings, etc), include the key ones in this section and the rest in appendices, referring to the latter as necessary. State how significant you think the work is and support your claims with evidence from your results, the literature, etc. You must also give a discussion of the experimental errors associated with your measurements if you have done an experimental/modelling project. This section can be divided into a separate results and a separate discussion section if you wish.

As you would expect most of the marks will be gained from how well you discuss your findings. Do not present results without analysis and discussion unless you want to fail!

11. Conclusions and Recommendations for Further Work

Summarize your key findings and results, successes and failures and problems encountered. Assess the work against the aims and objectives listed at the beginning of the report and the deliverables.

Have you met these? Try to put your work into the wider context of the area. Finish off with recommendations for further work where you identify areas that need completing or further research which needs to be done. The use of bullet points is a very effective way of listing the conclusions and is recommended. This section should be very brief. There must be nothing new in the conclusions. Your discussion must logically lead the reader to your conclusions.

12. Bibliography and References

A bibliography is a complete list of books and papers that you have consulted, whereas, references are those works to which you have made specific reference in the report. References are essential; you can include a separate bibliography if you wish. I would recommend that you aim for a reference list only, but it is ultimately up to you. You must give the complete details for every work and use a consistent format as described in.

13. Appendices

Only include items that are referred to in the report. Do not include published work - this should just be listed in the references. Inserts such as floppy disks must be securely attached to the inside-back cover of the report; they must be easily accessible and replaceable. If you have a large document as an appendix e.g. a user manual, this may be submitted separately if absolutely necessary. In this case it must be labelled clearly on the cover and spine to indicate the content.

14. Project Planning

Length of Report This final report should not be more than 35 pages long excluding reference and appendices. You will be penalised for doing so without permission.