PROJ07026 2022 Polymer Project

General Details

Full Title
Polymer Project
Transcript Title
Polymer Project
Code
PROJ07026
Attendance
N/A %
Subject Area
PROJ - Project
Department
MECT - Mechatronics
Level
07 - Level 7
Credit
05 - 05 Credits
Duration
Semester
Fee
Start Term
2022 - Full Academic Year 2022-23
End Term
9999 - The End of Time
Author(s)
David Mulligan, Douglas Marques
Programme Membership
SG_EPOLP_J07 202200 Bachelor of Engineering in Polymer Process Engineering SG_EPOLZ_J07 202200 Bachelor of Engineering in Polymer Process Engineering SG_EPOLA_J07 202400 Bachelor of Engineering in Polymer Process Engineering SG_EPOLY_J07 202400 Bachelor of Engineering in Polymer Processing SG_EPOLB_J07 202500 Bachelor of Engineering in Polymer Process Engineering SG_EPLYP_J07 202400 Bachelor of Engineering in Polymer Processing
Description

The project aims to provide students with the opportunity to apply and integrate the skills and knowledge they have gained on the programme of study they are undertaking. 

The student should bring the learning from the modules covered in the course to conceive, define and agree a project which is relevant to the subject matter they are studying. A mentor will be assigned to each project, which may be individual or group projects. The mentor will act as a guide in agreeing the relevance and scope of the project, and monitor the progress on a regular basis. Updates will be sent to the mentor on an agreed basis.

Learning Outcomes

On completion of this module the learner will/should be able to;

1.

Identify a problem which needs to be addressed of importance to the organisation.

2.

Utilise an appropriate structured approach to manage the project with realistic, interim and overall project objectives.

3.

Prepare a written report which outlines in detail the background to the project, the methodology used, discussion, conclusions and recommendations.

4.

Present project results with Executive Summary, Conclusions and Recommendations and discuss the approach taken and results achieved.

Teaching and Learning Strategies

This module incorporates the principles of UDL (Universal Design for Learning) and takes a gradual approach from analysing the environment to putting a draft solution and assessment of that solution in place and on to implementation and testing. Findings are drawn from the case study or research and dissertation is documented. 

Module Assessment Strategies

 

The project will be assessed continuously through the academic year. The following structure of assessment is to be followed, regardless of the project nature:

CONTINUOUS ASSESSMENT - LOGBOOK: With three individual submissions along the academic year, the logbook aim to induce a culture of record keeping, rationale project evolution, and auto critical reflection. The submissions in three distinct stage of the academic year have for goal the assessment of: the original idea and its feasibility; the project evolution and progression; the project conclusion and readiness for presentation and delivery. Considering the logbook is not marked on its content, marks are given following individual live consultation. The logbook is used as tool of connection between the academic supervisor and the learner, and allows the supervisor a close accompanying of project evolution.

FORMATIVE ASSESSMENT - PROJECT MANAGEMENT TOOLS: with a single submission half way through the academic year, the assignment in Project Management Tools requires the learner to adapt their project to organisation tools taught in classroom. Work Breakdown Structure, Table of Dependencies, Critical Path Diagram, and Gantt Chart are requested, as each of the tools have their own merit on any type of project execution. The assignment is conceived to be delivered in the midway point of the module, given the learner time to stablish and plan the project, identify and inform stakeholders, and develop limitations and circumvention of initial ideas.

DISSERTATION AND FINAL PRESENTATION: at the end of the academic year, learners are required to write a short dissertation about the entire scope of the project. The dissertation structure is to be conceived following the text structure commonly encountered on engineering scientific articles. Along with the dissertation, learners are invited to a 10 minute long oral presentation, where the project execution is summarised and submitted to scrutiny and questioning. Below is detailed the demands for the written dissertation, as well as rubrics detailing marking criteria.

Students enrolled on this module were invited to write a short dissertation, describing the evolution of their project execution. Projects were allowed to be executed following one of two approaches: Research or Work based projects. Research-based projects follow scientific method to address hypothesis and aim overall contribution to knowledge generation. Work-based projects follow Six Sigma DMAIC approach and aim overall improvement on the companies where the project is executed. The rubrics below is set to be used as a basis of evaluation of all projects independently from its approach.

All dissertations must: be written in English and contain at least 3000 words, grammar is not a criterion included in the marking. The dissertation must contain at least 10 references, where only scientific articles and books count towards reference count. References must be expressed both on the text – format Author, Date – and on the Reference List at the end of the dissertation. The dissertation must include figures and tables, where subtitles are relevant to information being conveyed through the image/table. The mandatory textual structure to be followed by all delivered dissertations: Literature Review, Objectives, Methodology, Results & Discussion, Conclusions. Any section from the specified structure that is not included on the dissertation must be marked as Not Compliant.

CRITERIA Not Compliant (0) Poor (1-3) Average (4-6) Good (7-10)
Formatting – weight 10% 
Word count Does not contain 3000 words. - - Contains 3000 words
Reference count NO reference included on the reference list and included on the text. 1 to 4 references included on the reference list and included on the text. 5 to 9 references included on the reference list and included on the text. 10 or more references included on the reference list and included on the text.
Figures & Tables No Figures & Tables used Figures & Tables used have little to no relevance to the area of knowledge being addressed in the dissertation, have poor or irrelevant subtitles, and do not convey information clearly. Some Figures & Tables have relevance to area of knowledge being addressed in the dissertation, adequate subtitles, and clarity of information being conveyed.  All Figures & Tables are relevant to the area of knowledge being addressed in the dissertation, well written subtitles, and information being clearly and objectively delivered.
Area of Knowledge – weight 30%
Literature Review Literature is fragmented; no synthesis. Provides some synthesis of the literature; relationship between the literature and the research question(s) is present but not developed. Provides a modest synthesis of the literature; relationship between the literature and the research question(s) is present and is partially developed. Provides a focused synthesis of the literature; shows an excellent relationship between the literature and the research question(s)
Polymer related content Literature Review and Objectives do not approach polymer science. Literature Review and Objectives present a flawed and irrelevant polymer science perspective, a relationship between material properties and processing limitations is poorly constructed, and information presented is not sufficient to understand the hypothesis. Literature Review and Objectives partially approach polymer science, and building an incomplete relationship between the project hypothesis and the materials science perspective necessary to justify it.  Literature Review and Objectives approach polymer science on a complete manner, including material properties and processing limitations; build knowledge necessary to understand hypothesis from a materials science perspective
Objectives Objectives for the project are not included. Project objectives are unclear, do not address a relevant issue/question, are not aligned with polymer processing technology and are not achievable within the project timeline. Objectives are partially clear, but lacks depth of relevance, alignment with polymer processing technology, or feasibility within the project timeline. Project objectives are clearly stipulated, address a relevant issue within the company (work-based project) or address a relevant question within science (research-based project), encompass polymer processing technology, and were successfully completed within the project timeline.
Methodology – weight 20%
Experiment Design Does not address hypothesis; improper to achieve pre-established objectives. Omits important information; insufficient detail; inappropriate design; no controls. Methodology has little to no relationship with objectives. Appropriate procedures; described in minimal detail; insufficient for replication; missing some controls but data can still stand. Methodology’s relationship with the objectives is flawed or incomplete. Appropriate, clear; describes procedures in detail, precisely describing how data will be collected and handled; attention to relevant detail; has good controls; applies new methods or comes up with novel approach. Methodology presents a direct relationship with the objectives.
Data Handling & collection Does not identify groups; does not mention how data is collected from each methodology; does not organise or identify patterns. Shows little insight; data not organised; misses patterns in data; no connection to hypotheses. No analysis or use of inappropriate statistical tools. Identification of groups – treated and control – is improper. Consistently organises data, though not necessarily in patterns; data connected to hypotheses but rarely in patterns. Statistical tools used but with only limited understanding of statistical foundation. Identification of groups – treated and control - is satisfactory. Shows evidence of rigorous data collection; excellent data quality; done rigorously; strong statistical foundation for the analysis; creative analytical methods; demonstrates excellent understanding of statistical analysis. Identification of groups – treated and control – is outstanding
Results – weight 20%
Communication Does not present results of the data collection. Results are simply stated in an objective manner. Little depth given to relationship between method applied and data collected. Results are adequately stated in an objective manner. Depth of meaning is given to relationship between method applied and data collected. Results of the data collection use techniques that describe the data and reveal meaningful relationships that exist in the data. Creates a clear relationship between the method applied and the data collected.
Interpretation Does not interpret data obtained from methods of data collection. Cannot back up all interpretation with valid results; claims findings that are not evident from the data. Results are not relevant to the proposed work/research Can back up most interpretation with valid results but some interpretations are speculative; some findings claimed are not evident from the data. Not all results are relevant to the proposed work/research. Can back up all interpretation with valid results; does not claim findings that are not evident from the data. Results are relevant to the proposed work/research.
Discussion – weight 20%
Discussion of Findings Findings and implications not discussed, have no influence on the decision-making process, have no relationship to the objectives. Makes no attempt to discuss the implications of the findings. Makes an adequate attempt to discuss the implications of the findings. Provides a compelling discussion of the implications of the findings (positive and negative), placing their importance within the context of current knowledge.
For work-based projects: discussion does not stablish a direct relationship between the results obtained and the project goals, does not highlight results influence on decision making and project progression. Impact on the company is not commented. For work-based projects: discussion exposes the direct relationship between the results obtained and the project goals, but does not highlight results influence on decision making and project progression. Impact on the company is lacking. For work-based projects: discussion reinforces the direct relationship between the results obtained and the project goals, highlighting results influence on decision making and project progression. Impact on the company is detailed.
For research-based projects: discussion does not stablish a direct relationship between the results obtained and the initial hypothesis, does not highlight results relevance towards the knowledge generated. For research-based projects: discussion superficially approaches direct relationship between the results obtained and the initial hypothesis, and does not comment on results relevance towards the knowledge generated. For research-based projects: discussion exposes direct relationship between the results obtained and the initial hypothesis, highlighting results relevance towards the knowledge generated.
Conclusions No conclusion presented. Conclusion is not clear; not succinct; not complete. Conclusion does not clearly follow from the results, and does not create a connection to the initial goals (work-based) or hypothesis (research-based). Conclusion is mostly clear, succinct, and complete. Conclusion adequately follows from results and is explained in terms of the analysis of the data. Conclusion create a lacking relationship between the project achievements and limitations to the initial goals (work-based) or hypothesis (research-based) Conclusion is extremely clear, succinct, and complete. Conclusion clearly follows from results, is accurately described in detail in terms of data analysis, showing excellent methodological and conceptual rigour. Conclusion connects the project achievements and limitations to the initial goals (work-based) or hypothesis (research-based).

 

Repeat Assessments

Repeat submission of final dissertation with required amendments made. 

Indicative Syllabus

Syllabus Content

  • The student should bring the learning from the subjects covered in the course to conceive, define and agree a project which is relevant to the students course of study.
  • Various types of projects may be undertaken depending on whether the student is full time or part time and their course of study.  Examples of these are as follows:

Project Type A: Six Sigma DMAIC

The Six Sigma project will be undertaken by the student and should address a substantive issue in the workplace. The project will test the student's ability to define a real-life problem of concern to the organisation, design a strategy for addressing the problem, gather data, formulate and evaluate options and make recommendations. The project should follow the Six Sigma DMAIC methodology. While it is recommended that the problem is addressed as part of a cross-functional team, it is important that the student makes a significant contribution to the success of the project. A financial saving should be identified. The Green belt is normally expected to contribute annualised savings from €30,000 - €100,000. The amount of savings will depend on the size of the company, sales revenue, number of employees and opportunities for improvements.

The Six Sigma project will also cover the following areas:

1. Project management basics

•· Project charter and problem statement

•· Define and describe elements of a project charter and develop a problem statement, including baseline and improvement goals.

•· Project scope

•· Assist with the development of project definition/scope using Pareto charts, process maps, etc.

•· Assist with the development of primary and consequential metrics (e.g., quality, cycle time, cost) and establish key project metrics that relate to the voice of the customer.

•·  Use project tools such as Gantt charts, critical path method (CPM), and program evaluation and review technique (PERT) charts, etc.

•· Provide input and select the proper vehicle for presenting project documentation (e.g., spreadsheet output, storyboards, etc.) at phase reviews, management reviews and other presentations.

•· Describe the purpose and benefit of project risk analysis, including resources, financials, impact on customers and other stakeholders, etc.

  • Describe the objectives achieved and apply the lessons learned to identify additional opportunities.

 2. Team dynamics and performance

•·  Define and describe the stages of team evolution, including forming, storming, norming, performing, adjourning, and recognition. Identify and help resolve negative dynamics such as overbearing, dominant, or reluctant participants, the unquestioned acceptance of opinions as facts, groupthink, feuding, floundering, the rush to accomplishment, attribution, discounts, plops, digressions, tangents,

•· Describe and define the roles and responsibilities of participants on six sigma and other teams, including black belt, master black belt, green belt, champion, executive, coach, facilitator, team member, sponsor, process owner, etc.

•· Define and apply team tools such as brainstorming, nominal group technique, multi-voting, etc.

•· Use effective and appropriate communication techniques for different situations to overcome barriers to project success.

Project Type B: Research Project

 

 

Alternatively, a suitable research project may be undertaken by agreement with the project supervisor. Typical research projects often include, polymer material analyis or product design.  The principal difference between this type of project and Project Type A is that there will be minimal practical work and no requirement to show cost savings for the research project. There will also be a greater emphasis on the students background research and literature review of the chosen topic.

Note: The Research project type is NOT suitable for students wishing to pursue a Six Sigma Green Belt award.

Coursework & Assessment Breakdown

Coursework & Continuous Assessment
100 %

Coursework Assessment

Title Type Form Percent Week Learning Outcomes Assessed
1 Formative and Summative Assessment Log Book Coursework Assessment Written Report/Essay 15 % OnGoing 1,2
2 Project Management Tools Coursework Assessment Assignment 20 % Start of Year 4
3 Written Report Final Dissertation Coursework Assessment Written Report/Essay 50 % End of Term 1,2,3
4 Oral Presentation Final Report Coursework Assessment Interview 15 % End of Term 2,3

Part Time Mode Workload


Type Location Description Hours Frequency Avg Workload
Lecture Distance Learning Suite Theory 1 Monthly 0.25
Independent Learning UNKNOWN Project 4 Weekly 4.00
Directed Learning Not Specified Mentoring 0.25 Fortnightly 0.12
Total Part Time Average Weekly Learner Contact Time 0.25 Hours

Module Resources

Non ISBN Literary Resources

Recommended Reading 

Title

Authors

Publisher

Year

  Writing Winning Reports And Essays

Janeczko, Paul B.

 

New York : Scholastic Reference.

2003.

  Project Management : The Managerial Process

Gray, Clifford F.

 

Boston : McGraw-Hill/Irwin.

2006.

Business Research, Third Edition

Jill Collis & Rodger Hussey

 

Palgrave.

 

2009

 Six Sigma Demystified ISBN:0071445447

Paul A. Keller

 

McGraw-Hill Professional

 

2004

Other Resources

Moodle Site

Additional Information
None