Timetable of Sessions and Assessment 2013

ENGG1200 (LJK/CAR) Semester 2, 2013 1/16

ENGG1200 Timetable of Sessions for 2013

Week Workshop (1 h) Materials (2 h) Problem Solving (2 h) Online Module Assessment Due

1 22/07

W1. Course Intro – what do I want? –Template A

MW1. Reverse Engineering

PSS1. Engineering Problem Solving

OM1. Designing with Materials

1. PSS1 Sheet (in session)

2 29/07

W2. Reflecting –thinking like a design engineer –Template B

MW2. Tensile Testing (Metals)

PSS2. Data Analysis OM2. Elasticity 1. OM1 quiz (online, Mon 0900) 2. Reflection 1 (online, Wed 0900) 3. PSS2 Sheet (in session)

3 5/08

W3. The Prelim Memo –Template C

MW3. Dislocations (Bubble Rafts)

PSS3. Models and Systems

OM3. Plasticity 1. OM2 quiz (online, Mon 0900) 2. PSS3 Sheet (in session)

4 12/08

W4. Design – project specific concepts and issues-Template D

P/HOL (Wed) Platform primers – *online* – Matlab/ CREO

PSS4. Mathematical Models

OM4. Strengthening and Failure Mechanisms

1. OM3 quiz (online, Mon 0900) 2. Reflection 2 (online, Wed 0900) 3. Prelim Memo (H/copy + Turnitin) 4. PSS4 Sheet (in session)

5 19/08

W5. Matlab or Creo? –Template E

MW5. Tensile Testing (Polymers)

PSS5. Programming I OM5. Polymers – structure/ deformation

1. OM4 quiz (online, Mon 0900) 2. PSS5 Sheet (in session)

6 26/08

W6. Tracking the project I-Template F

MW6. Thermoforming PSS6. Programming II OM6. Polymers – time, temperature, & processing

1. OM5 quiz (online, Mon 0900) 2. Reflection 3 (online, Wed 0900) 3. PSS5 Sheet (in session)

7 2/09

W7. Exam preparation Structural Modelling I (Machine stream only)

Behavioural Modelling I (Model stream only)

1. Peer Assess (online) 2. OM6 quiz (online, Mon 0900)

8. 9/09

W8. Tracking the team –Template G

Structural Modelling II (Machine stream only)

Behavioural Modelling II (Model stream only)

1. Mid-semester Exam (Saturday)

9 16/9

W9. PAF Feedback (Compulsory)

Structural Modelling III (Machine stream only)

Behavioural Modelling III (Model stream only)

1. Reflection 4 (online, Wed 0900)

10 23/9

W10. Tracking the project II –Template H

Model Test (Compulsory)

1. Model Test (in session)

MID SEMESTER BREAK

11 7/10 P/HOL (Mon)

12 14/10

1. Final Report (H/copy + Turnitin) 2. Reflection 5 (online, Wed 0900)

13 21/10

Demonstration! (Compulsory)

Demonstration! (Compulsory)

1. Demonstration (in sessions) 2. Peer Assess (online)


ENGG1200 2012 - ASSESSMENT SUMMARY

All compulsory sessions must be attended. These are: Peer Assessment Feedback Session (Week 9); Model Test (Week 10), and Demonstration! (Week 13). If you fail to attend, you will have your PAF reduced and/ or receive zero (see table below for details). NB: It is recommended that all workshops and project sessions be attended. Attendance at Materials and Problem solving sessions will be monitored and used to justify PAFs.

Your team must achieve 50% or more for the Prelim Memo. If you do not, you will be allowed to resubmit to obtain a capped memo mark of 50%.

Templates will be submitted with the Prelim Memo (A-D), and final report (E-H) for an individual mark.

You must pass both module quizzes and mid-semester exam. To pass you must achieve 50% or more in total for each assessment. If you fail the quizzes and/or the mid-semester exam you will be given a chance to repeat them. Your mark will be capped at 50% for this second attempt.

Assessment Due date Submission details

1. Reflections (Individual, 15%) Wednesday 0900: Weeks 2, 4, 6, 9, and 12 Feedback: Monday 0900 Wks 3, 5, 7, 10 and 13

Electronic – via Blackboard Electronic – via Blackboard

2. Problem Solving Sheets (Team, 5%) Continuous: Weeks 1 through 6 inclusive at end of problem solving session

Mentor/ Tutor – End of session

3. Module Quizzes (Individual, 10%) Continuous, Monday 0900 in week following module: Weeks 2 through 7 inclusive

Electronic – access via Blackboard

4. Preliminary Memo (Team, 13%) + Templates (Individual, 2%)

Friday 16th August, 1600, Week 4 1. EAIT submission chute; 2. Turnitin (via Blackboard)

5. Peer Assessment (Individual, P/F) PAF1 (Week 7) – applied to Prelim memo, Problem sheets

Electronic – email sent to you with link

PAF 2 (Week 13) – applied to Final report, Testing/ Demonstration

Electronic – email sent to you with link

6. Mid-sem exam (Individual, 20%) TBC (Saturday, Week 7 or 8) Exam

7. Attendance (P/F) Peer Assessment Feedback (Week 9) Model Test! (Week 10, Problem Solving Session) Demonstration! (Wk 13, Problem Solving session)

Failure to attend: PAF1 is reduced by 0.1 (individual) Failure to attend: Test mark = 0 (for individual) Failure to attend: Demo mark = 0 (for individual)

8. Model Test (Team, 5%) Week 10 – Problem solving session Demonstration – Attendance compulsory.

9. Demonstration! (Team, 15%) Week 13 – Materials and Problem solving sessions Demonstration – Attendance compulsory.

10. Final report (Team, 13%) + Templates (Individual, 2%)

Friday 18th October 1600, Week 12 1. EAIT submission chute 2. Turnitin (via Blackboard)


ENGG1200 2013 – When and where are my sessions?

PROJECT MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY

A

W01 0800-1000 Mat – 47A 241

1000-1200 PSS – 47A 241

W02 1400-1600 PSS – 47A 241

0800-1000 Mat – 47A 241

W03 1000-1200 Mat – 47A 241

0800-1000 PSS – 47A 341

B

W04 1200-1400 Mat – 47A 241

1400-1600 PSS – 47A 241

W05 0800-1000 PSS – 47A 341

1000-1200 Mat – 47A 341

W06 1400-1600 PSS – ELCX

1200-1400 Mat – 47A 341

C

W07 1400-1600 Mat – 47A 341

1400-1600 PSS – ELCX

W08

1000-1200 Mat – 47A 241

0800-1000 PSS – 47A 241

W09 1200-1400 PSS – 47A 241

1000-1200 Mat – 47A 341

D

W10

0800-1000 Mat – 47A 241

1200-1400 PSS – ELCX

W11

1200-1400 Mat – 47A 241

1000-1200 PSS – 47A 241

? W12 1200-1400 PSS – 47A 341

1400-1600 Mat – 49-301

Mat= Materials lab/ session; PSS = Problem Solving session

ALL projects will require you to Design, Simulate, Build and Control. ALL projects are suitable for

students who are interested in electrical or software engineering.

Project A

W01, W02 or W03

In this project you will be required to design, simulate and build a payload

deployment-mechanism (mechanical arm assembly) that will be attached to a linear

rail. The objective of this project is to launch a projectile, using the launch arm you

have designed, to a known trajectory based on digital data that you will supply to

drive the motor.

Project B

W04, W05 or W06

Chemical Process Control System Select 4, 5, 6 In this project you will be required to

design, simulate and build a control system capable of accurately delivering a known

volume and temperature of liquid from an inlet supply of variable flow rates and

temperatures. This system of sensors and valves will be controlled via an Arduino.

The system is a model system for a food processing facility. Project C

W07, W08 or W09

Failure Aware Power Line Support Select 7, 8, 9 In this project you will be required

to design, simulate and build a power line support arm that can detect its own

structural failure. The support arm must be instrumented with sensors that detect

excessive loads or imminent collapse and send a signal down the line to alert a switch

that the power must be turned off before complete structural failure. Project D

W10 or W11

Core Drilling Strata Detection Select 10, 11 In this project you will be required to

design, simulate and build a cutting head and a torque measurement system to control

a scaled down mining drill rig as it drills a hole at the optimal penetration rate

through layers of unknown materials.


1. Reflections, Individual Mark (15%)

By reviewing our own work critically, we come to know it and improve it. (http://www.infed.org/thinkers/et-schon.htm - Donald Schon)

DUE: Reflection: By Wednesday 0900 Weeks 2, 4, 6, 9, and 12. Feedback: By Monday 0900 Weeks 3, 5, 7, 10, and 13 (i.e. 5 days later)

What do I need to do – how do I submit? There are two parts to each of the 5 reflections:

Reflection: Log on to the Blackboard reflection page and post your response to the trigger questions for that particular reflection.

Feedback: After the reflection submission time (0900 Wednesday) log on to the Blackboard reflection page and comment on the reflection assigned to you.

LENGTH: Anywhere from 150-200 words (one or two paragraphs) to 300 words.

STYLE: Relaxed, colloquial and personal. Write in a comfortable, conversational style in keeping with "reflections" on your learning. Give examples or evidence to show on which basis you believe your statements to be true.

MARKING: The reflections are worth 15% in total and there are 5 entries over the course of the semester. Each of your combined reflection and feedback postings is therefore worth a total of 3%.

You will receive an aggregated mark out of 4 and comments from a tutor. The aggregated mark will comprise 4 sections – all with equal weighting. A mark of 0 will be allocated if you do not demonstrate any ability with respect to the criteria. A mark of 1 will be given for an answer that perfectly responds to the criteria. 0.5 marks will be given for a passable attempt.

A. Insight - Demonstrates critical thinking and full understanding of task. Insightful content. Assumptions and feelings stated and explored. Exploration of possible reasons for feelings.

B. Depth - Skillfully analyses a significant issue as basis for reflection leading to new perspective or insights. Innovative connections made to self and beyond ENGG1200. Expectations stated and linked to past experience. Questions own biases, and stereotypes.

C. Logic/ Clarity of writing - Well written, fluid and original. Exceeds all requirements. Logical structure. Viewpoints and interpretations well supported.

D. Feedback - Both strengths and weaknesses identified objectively, communicated thoughtfully. Helpful suggestions for improvement. Sensitive approach.

LATE SUBMISSIONS: If you submit your reflection later than 0900 on the Wednesday that the reflection is due, you will forfeit the 3% associated with that particular reflection. If you miss the deadline due to illness or another valid reason, you will need to fill out an affirmation document1 and attach a medical certificate or other appropriate proof. Please submit this to Ms Lisa Deacon in the FYELC

1 The Affirmation document can be found on Blackboard under the Help tab, and it is also attached at the

end of this document.

http://www.infed.org/thinkers/et-schon.htm


2. Problem Solving Sessions, Team Mark (5% x PAF1)

DUE: At end of sessions in Weeks 1 through 6 inclusive. (There is no assessment associated with the sessions in Weeks 7 to 9 inclusive.)

Why 5%? This assessment is designed to ensure that you place value on the problem solving sessions and attend. There are a number of reasons to do so:

your team will be looking for your involvement and part of their peer assessment will be based on your attendance;

the project requires that you have this basic knowledge (as does being a professional engineer); and

the mid-semester exam will be partially based on the knowledge and skills that you learn in these sessions.

MARKING: Each session has an associated problem set which you and your team will solve. These solutions attract marks as shown in the session worksheet. Tutors and session leaders will mark your work either during the session or when you have completed. Each session is worth 1/6 x 5%.

Your first peer assessment factor (PAF1) will be applied to the team mark to generate your individual mark for these sessions.

SCHEDULE:

Weeks 1-6: Each week you will workshop with your team a number of modelling and problem solving exercises. At the end of each session (or during the session depending on your project leader’s preference), your team will submit a completed worksheet for assessment.

Weeks 7-9: Depending on which sub-group you find yourself in, you will undertake specialised training during EITHER your Materials or Problem Solving workshop session. Your team will divide into:

A machining sub-group who will learn how to program the CNC machine and who will be ultimately responsible for producing the item needed in your Build.

A programming sub-group who will learn about Simulink (and/ or alternatives) and who will be ultimately responsible for producing the model of your final Build.

ATTENDANCE: Although attendance will not be formally logged, your attendance at these sessions will be used to validate peer assessment scores and also to decide in cases of borderline grades.

If you are ill or miss a session due to a valid reason, you will need to fill out an affirmation document2 and submit to your tutor the following week.

2 The Affirmation document can be found on Blackboard under the Help tab, and it is also attached at the



3. Module Quizzes, Individual Mark (10%)

DUE: By Monday 0900 in Weeks 2 through 7 inclusive via Blackboard.

We have given you the weekend to complete the summative quiz3 at the end of each week’s module and therefore it is due by 0900 on the Monday following the week designated for that particular module (see Timetable, p1).

MARKING: At the end of each week’s online module on Materials, there is a small quiz that you need to complete online. It will be automatically assessed.

Each quiz is worth 1/6 x 10%.

What if I fail? You must pass the online modules to pass ENGG1200. Students achieving a mark of less than 50% for the modules in total, will have their quizzes reset and will be able to retake them. The deadline for re-taking the quizzes will be Monday 16th September at 0900.

LATE SUBMISSION: If you miss completing a quiz for a specific module through:

a valid reason including illness, you should submit an affirmation document4 with attached medical certificate or appropriate evidence to Ms Lisa Deacon ([email protected]) and complete the quiz. You will receive a mark as determined by your performance; or

an invalid reason, such as forgetfulness or distraction, you will still need to complete the missed quiz before Monday 2nd September at 0900, however you will receive a capped mark of 50% for the quiz (assuming that you pass).

3 Each week’s module is broken down into a number of sections. Each of these sections has a series of

formative questions at the end. Formative means that they don’t count towards your mark and that we have put them in for your feedback only. The questions at the end of these sections are the ones that contribute to your mark for this piece of assessment. 4 The Affirmation document can be found on Blackboard under the Help tab, and it is also attached at the


mailto:[email protected]


4. Preliminary Memo, Team Mark (13% x PAF1) + Individual (2% Templates)

DUE: 1600 Friday 16th August

SUBMISSION: 1. Hardcopy via EAIT chute; 2. Electronic version via Turnitin

Both the hardcopy and the Turnitin submission must be completed before the due date.

What is it? The Preliminary Memo is very much like the Preliminary Investigation Report for ENGG1100 in that it shows that you understand the brief that has been given to you, you have scoped the problem, and that you have some idea about where you need to go.

The Preliminary Memo is not to be set out as a report but instead will be much less formal and take the shape of a memo. The Purdue Online Writing Lab has some really good pointers about memos (http://owl.english.purdue.edu/owl/resource/590/1/) – make sure that you look at all the subsections under this introductory text.

You should address the memo to your project session mentor/ tutor, and begin with a one-paragraph introduction which clearly states what the memo includes – a sort of ‘Contents of Report’. Long memos often conclude with a ‘Summary’ or ‘Conclusions’ which restates the important parts of the memo.

What should be in it? We recommend that you section your memo as follows:

1. Scope of design project including any assumptions about what exists, what will be included etc. This is really a regurgitation of the brief with some extension in that you clearly outline what it is that you will be doing and what you are assuming is not part of your remit. (~2-3 pages)

2. SOLVEM overview – an outline of the problem using SOLVEM as per your first Problem solving session, (~2 pages)

3. Prior Art – what’s out there that you could use to help with your project. (~2 pages) 4. Project management package – go back to ENGG1100 and look at what you needed to do

for the PSP – you need to do this again for the Preliminary Memo. Include a Work Breakdown Structure (WBS), Gantt chart, overview of resource allocation, and a build risk assessment. (~4 pages include a 1-page Gantt chart and a 1-page risk assessment)

What’s the page length? The Purdue reference suggests that memos should only be 1-2 pages long. We appreciate that your memo will be substantially longer. Remember our reason for asking you to write a memo instead of a formal report, is to expedite the process for you.

You should be able to put the memo together in 12 pages or less. This isn’t a hard limit but if you run significantly over this number of pages due to repetition or irrelevant information, you will be penalised.

And the format? The use of a word processor is mandatory. USE:

1. Times New Roman or Arial 12 pt font; 2. all four margins 20mm; 3. A4 page size; and 4. single or 1.5 line spacing.

http://owl.english.purdue.edu/owl/resource/590/1/


As with ENGG1100, memos not in this format will not be accepted and you will need to resubmit with commensurate late penalty.

What’s with the individual mark for templates? We believe that the template sessions help you to plan your design, model, and build and have structured them so that many of the problems that your team might face are pre-empted.

For the Preliminary Memo, templates A, B, C, and D should be submitted.

How will templates be marked? Although we have not made templates compulsory or policed attendance at the sessions, we believe that those students who attend and participate should be rewarded as they will undoubtedly make a larger contribution to the team than those students who do not attend. Therefore each template is worth:

0.5% if it demonstrates effort and is fully completed;

0.25% if it is only partially complete; and

0% if it is missing or poorly completed.

How do we submit the templates? You should submit the templates as an appendix to the preliminary memo. They should not be typed up or rewritten but should be the original template that you completed during the template session. If you have stuck the original into a logbook, then a clear photocopy is acceptable.

It is recommended that you order the templates so that the work of individuals is grouped together.


ENGG1200 Preliminary Memo TEAM: MARKER:

SECTION (WEIGHT)

0 (MISSING) 1 (POOR) 2 (MIXED) 3 (AVERAGE) 4 (GOOD) 5 (EXCELLENT)

Presentation/ Spelling/ Grammar (10%)

No resemblance to professional report, illegible

Data presentation/ language/ format/ grammar not professional

Not pitched correctly, poor structure, some parts illegible

Acceptable - could be improved. Only minor spelling/ grammar errors. Mostly clear and legible.

Well structured, professional memo. Appropriately pitched. 1 or 2 errors if any.

Memo concise, good structure, completely professional. No errors. PERFECT!

Problem Definition and Scope: Aspects, goals, issues etc. (15%)

Not addressed Poorly defined and understood, unclear, missing the point, many issues not covered.

Limited understanding, patchy coverage, doesn’t match project reqs

Adequate – minor omissions only – mostly achievable. Sound coverage with varying depth across issues.

Good understanding. Full coverage – addresses issues well, assumptions clear and correct.

Insightful/ complete coverage – optimised scope and insightful assumptions. TBL may also be covered.

SOLVEM (25%) Not addressed SOLVEM poorly realised and understood: unworkable and detail poor.

Poor demo of SOLVEM process – patchy detail, mostly not applicable.

SOLVEM mostly correct, detail satisfactory. Easily understood. Applicable and useable.

SOLVEM sound with good detail. Concise, easily understood justification of approach.

SOLVEM innovative with extra details. Process used to best effect.

Prior Art (20%) None Limited research, 1-2 refs, single source, no critical thinking

Evaluation not complete, at least 3 refs, 2 sources

Sound evaluation, ≥ 5 refs, variety of sources, critical thinking evident

Fully researched and critiqued, ≥ 8 refs from variety of sources

Fully researched, including system requirements - ≥10 refs

Project Management: WBS, Gantt chart, Resource allocation, Risk management (25%)

None Incomplete and patchy coverage – missing aspect(s). PM principles clearly not understood.

Principles mostly understood. At least 3 parts passable but much doubt. Risks poorly addressed.

A workable project management package. Some aspects underdone/ misused but basically sound.

A good project management package. All aspects addressed and covered professionally. Minor omissions if any – major risks well covered.

WBS, Gantt chart, Resource allocation, and risk management complete, professional, and excellent processes proposed.

Diagrams (5%) None Diagrams inappropriate or poorly executed

Diagrams have some relevance but with major errors/ omissions

Sound diagrams, relevant, minor errors only. Engineering conventions used.

Diagrams correct and relevant, engineering conventions used.

Perfect diagrams used to enhance memo, highly professional


5. Peer Assessment (Applied to Team Marks, Weeks 7 and 13)

What is peer assessment? In Weeks 7 and 13, Peer Assessment will be opened in Blackboard. You will receive an email notification that the site is open. This is your opportunity to reward members of your team who worked hard and to give feedback to any non-performers. Your scores are confidential – only an aggregated mark will be given to each team member.

What do I have to do? You will be asked to evaluate the contributions of each person to the deliverable by distributing 100 points among them for the following criteria:

Week 7:

Materials Workshop Sessions = preparation, attendance and participation at the 5 sessions

Problem Solving Sessions = preparation, attendance and participation at the 6 sessions

Preliminary Memo Contribution = scoping, research, section development, reporting, editing, final submission production – how much work did the team member do?

Preliminary Memo Performance = the ability of the team member to meet agreed contribution times, and the standard and completeness of their work

Week 13:

Structural/ Behavioral Modeling Sessions (Week 7-9) = preparation, attendance and participation at the 3 sessions – this may be evidenced by the subsequent input to the project

Communication/ collaboration = attendance and participation at meetings, email/ SMS/ discussion board response, ability to work with team, ability to share findings with team

Contribution to final deliverables = modeling, building, reporting, coordination etc. – how much work did the team member do?

Performance = the ability of the team member to meet agreed contribution times, and the standard and completeness of their work

As a ready-reckoner of the Peer Assessment Factor (PAF) multiply the score that you are giving someone by the number of people in the team and divide by 100 ... now have a look at the scores in the table on the next page. Is this the PAF that you think they deserve?

For each score that is less than 0.95 you will need to include a comment to justify your scores. If you do not, your mark may be discounted.

What affect will this have? The PAF is calculated by the sum of all scores attributed to a student divided by the number of criteria multiplied by 100.

The Week 7 PAF will be applied to the team’s mark for the Preliminary memo and the Problem solving sessions to give you a mark for these items.

In Week 9, we will give your team their PAFs5 in a mentored session so that you can make adjustments to your team input in order to increase your PAF as necessary.

The Week 13 PAF will be applied to the team’s marks for the Final report and Model Test/ Demonstration! to give you your final marks.

5 The individual scores that you give to each student are confidential. Only the PAF and SAPA are disseminated.


What does the number mean? If you pull your own weight and undertake a similar amount of work to everyone else, you should get a PAF of 1.0. If you are leading the team and putting in extra work, you may get a PAF above 1.06. Note that for you to get above 1.0, another student will have to have lost some marks therefore PAFs slightly below 1.0 do not necessarily mean that you have not been pulling your weight. The following table shows the various levels of PAFs and possible interpretations.

PAF Interpretation Comments

>1.5 Alarm! Team failure.

Either someone is not participating at all or you are doing all the work by yourself. Either way, learning objectives are probably not being achieved by all the team.

1.15-1.5 Super Leader The team balance needs to be addressed as to achieve such a score other students are not participating or you are doing far too much.

1.05-1.15 Leader You are showing definite leadership qualities and/or have been putting in significant extra effort.

1.00-1.05 Good teamwork You are working well with the team and this has been recognised.

0.95-1.00 Acceptable teamwork

You have probably only been penalised because another team member has shown leadership and put in extra effort.

0.85-0.95 Social Loafer Any PAF below 0.95 is unacceptable. You need to talk to the team, find out what has gone wrong, and redress it immediately.

0.75-0.85 Super Social Loafer As above and below. You will need to talk to the team and get them to tell you what you need to do to bring your PAF to unity.

<0.75 Alarm! Individual failure!

You are in grave danger of failing the course. Much work is required for you to be accepted back into the team.

But couldn’t the system be manipulated: A minority of students use the peer assessment to give themselves a higher PAF than is warranted or to penalise other team members with whom they have disagreed. This is picked up by comparing your scores with the average of the other team members’ scores – and we do this check for all PAFS.

The SAPA (self assessment over peer assessment) is the score that you give yourself (ScoreSelf) over the average score that your teammates give you (∑ScoreOthers/(NTeam-1)).

( 1)

Self

Others Team

ScoreSAPA

Score N

A SAPA of over 1.0 indicates that you believe you do more in the team than your teammates think; a SAPA less than 1.0 indicates that you undervalue your contribution. The scores for individual students are also calculated as per the SAPA:

Assigned individual by student A

Individual over average

All other team members ( 1)Team

ScoreRatio

Score N

Again a ratio of over 1.0 indicates that Student A values the work of the individual more than their teammates think – this is common between friends; a ratio less than 1.0 indicates that student A may have personal conflict with the individual and undervalues their contribution. We will remove all scores that are over 15% above or below the team average where there is no justifying comment and/ or the mark appears to be unwarranted.

6 PAFs are capped at 1.1 which means you can potentially receive an additional 10% of the team marks. PAFs are

capped so that we are not overly rewarding effort in place of marks for other learning objectives.


6. Exam, Individual Mark (20%)

DUE: TBC (Most probably Saturday of Week 7 or 8)

What’s on it? The mid-semester exam will test concepts acquired through the online Materials modules, the Materials sessions/ laboratories, and the Problem solving sessions.

The Week 7 Workshop on Monday has been designed as a practice session for the exam. Attendance is strongly recommended.

What if I fail? You must achieve an overall mark of at least 50% in the mid-semester exam to pass ENGG1200. Students failing the exam will be able to re-sit it at a time and place to be nominated for a capped mark of 50% (assuming that a mark of at least 50% for the re-sit is achieved).

7. Attendance, Individual Mark (P/F)

DUE: Week 9 (Peer Assessment Feedback, Monday Workshop Session), Week 10 (Model Test, Problem Solving Session), Week 13 (Demonstration!, Materials and Problem Solving Sessions)

What do I have to do? Your attendance at the above three activities is compulsory. You must stay for the entire session - Do not leave unless you have been advised that this is acceptable by your session leader as early departure may result in you being marked absent for the session.

What’s the penalty for not showing up? There are consequences for missing one of these activities without a valid excuse as defined by UQ Policies.

Failure to attend the Peer Assessment Feedback Session (Week 9) will result in the Week 7 PAF being reduced by 0.1. For example, if your PAF is 1.02 it will be reduced to 1.02-0.10 = 0.92.

Failure to attend the Model Test (Week 10) will result in you receiving a mark of zero for this piece of assessment.

Failure to attend the Demonstration! (Week 13) will result in you receiving a mark of zero for this piece of assessment.

What if I have a good reason for not attending? If you know that you will be prevented from attending due to exceptional circumstances, then you must consult with the course coordinators (A/Prof Carl Reidsema or A/Prof Lydia Kavanagh) or your session leader to obtain signed approval. Approval will only be given for medical, compassionate reasons or exceptional circumstances. Exceptional circumstances could include, but are not limited to:

for a sporting or cultural commitment at state, national or international level; or for serious personal or emotional trauma.

If you are prevented from attending due to medical reasons, you must obtain a Doctor's certificate to substantiate your claim. University policy is clear on this practice: the medical certificate must be signed by a medical practitioner or registered nurse, and the medical practitioner cannot be a near relative or close associate. Examples of near relatives are partner, child, brother, sister, or parent. Examples of close associates are close friends, neighbours and partners or children of colleagues. Please arrange a time to talk to either the course coordinator or your session leader to submit your medical certificate.


8. Model Test, Team Mark (5% x PAF2) + 9. Demonstration!, Team Mark (15% x PAF2)

DUE: Week 10 Project Session (Testing!); Week 13 Project Session (Demonstration!)

What does this involve? Refer to your Project Design Brief for details on the Demonstration! Session. Testing details will be advised in your Problem solving sessions.

Do I have to go? Attendance is compulsory at both the Week 10 and Week 13 activities. You will not receive a mark for these sessions unless you are present. It is therefore important that you ensure your tutor marks you as present.

MARKING: Both Model Test and Demonstration! will be marked as per the template provided in your project design brief. Your Week 13 PAF2 will be applied to the both the Model Test and Demonstration! mark received by your team in order to calculate your individual mark.

10. Final Report, Team Mark (13% x PAF2) + Individual (2% Templates)

DUE: 1600 Friday 18th October (Week 12)

SUBMISSION: 1. Hardcopy via EAIT chute; 2. Electronic version via Turnitin (Both the hardcopy and the Turnitin submission must be completed before the due date.)

What is it? Each team will submit a comprehensive written report detailing your final design and model as well as a number of reflections on the process.

The report should be written as for a company director who wishes to know not only the details of the final design but also how your team are working and how the process of design can be improved within the company. It is up to you how you include both technical and process sections in your report.

What should be in it? Your report should include:

Virtual Model details: the model/ results, verification/ validation, expectations for Demonstration! (~3 pages)

Structural Model details: specifications, design drawings, materials, costs, expectations for Demonstration! (~3 pages)

Construction process: manufacturability, simplicity, prototypes, processes, costs (what did you do, where did you do it, who did what etc.), successes and difficulties encountered (~3 pages)

Team Reflection: If you did well, what do you think were the reasons for this (e.g. good planning, good teamwork, good luck etc.)? If you did poorly what could you have done better given the conditions? Negative external criticism will be marked down heavily. (~2 pages)

Key Lessons learned: 5 key lessons that your team learned as a result of this project. What skills (e.g. planning, team working, communication, estimating etc.) can you identify within these 5 key lessons? What are your recommendations for your next project based on this reflection? (~2 pages)

Effectiveness of Organisational Support: constructive criticism on the effectiveness of the support provided to complete your project (e.g. mentors, lab staff, lecturers, communication and online support tools, and learning activities). Negative criticism will be heavily penalised so match


criticisms with recommendations for improvement. For example, if mentors didn’t provide what you needed, what did you do to address it at the time and what will you do in future? (~2 pages)

Approximate page numbers these sections have been included ONLY to give you an idea of what we are expecting. This is not prescriptive and you will not be penalised for sections with different lengths.

Report sections: The report is to be set out professionally with at least the following sections:

o Transmittal letter o Title page o Executive summary o Table of contents o List of figures and tables o * Introduction (scope, objectives, contents of report) o * Body of report (refer to above and assessment sheet for potential section headings) o * Conclusions o * Recommendations o References (use a consistent and conventional referencing style such as Harvard or APA) o Appendices (including detailed data, calculations, data sheets etc.)

Report length: The body of the report (as denoted by all those sections marked with an asterisk * in the above list) must not exceed 15 pages. There are no extra marks for making the report longer than it needs to be – indeed concise reports that cover all the necessary points are likely to attract higher marks. There is no penalty for a report with less than 15 pages.

Your report should avoid any unnecessary 'dead-weight'. Don't include anything that is not directly related to your project; any research that proves to be fruitless or not relevant should not be included in the report.

Appendices, which are not included in the 15 page limit, are for supporting information and not a place to put any report overrun. The penalty for placing important information, that the reader must be aware of, only in the appendices will be a whole grade reduction in the ‘Presentation Quality’ section of the marking template. Appendices may be handwritten, but must be legible and logically structured.

Presentation: Try to improve on ENGG1100. Report presentation should be of the highest quality – the use of a word processor is mandatory. USE: 1. Times New Roman or Arial 12 pt font. 2. All four margins 20mm. 3. A4 page size. 4. Single or 1.5 line spacing is acceptable.

You are encouraged to present data in tabular format rather than prose. Diagrams, tables and figures are very useful ways to summarise information and should be included in the main report as appropriate. These should also be of excellent quality and should be numbered, have an appropriate title, and graph axes should be clearly labelled with appropriate units.

Templates?: Templates E, F, G, and H should be submitted as an appendix. See Page 8 for more detail.

Marking: The final report will be marked by tutors as per the following template. PAF2 will be applied to the report mark received by your team in order to calculate your individual mark.

All marks will be moderated; project group averages will be checked against each other and scaled if necessary. Coordinators’ decisions will be final.


ENGG1200 Final Report TEAM: MARKER:

Element (Weight) 0 None 1 Poor 2 Poor/ Mixed 3 Sound 4 Good 5 Excellent

Presentation Quality (10%) The look and structure of report: signposting, spelling, grammar, data presentation, executive summary

No resemblance to professional report

Not pitched correctly, poor structure/ exec sum, many errors

Slightly overlong or lacking in detail –could be improved but fair attempt

Professional – appropriately pitched – minor errors

Perfect – report succinct and professional – no mistakes

Behavioural Model (20%) [SIM] Design description of the system and it’s behaviour, results of simulations with prediction for final demonstration performance.

No model Poorly defined, parameters, diagrams, limited or incorrect results.

Incomplete description of system, poor use of diagrams, limited discussion

Has essential elements but doesn’t reflect good understanding of modelling to predict performance

Well thought out/ concise/ comprehensive description of system behaviour

Well thought out/ concise/ comprehensive description of system behaviour, insight/ initiative evidence (e.g. model extended to improve accuracy/ error analysis).

Structural Model (20%) [CAD] Design description of the physical configuration, selection/sizing/materials of components and assemblies.

No design details

Missing either structural model or design rationale.

Incomplete/faulty description of configuration and rationale for design decisions

Has essential elements but doesn’t reflect a good under-standing of use of design engineering equipment

Well thought out/concise/comprehensive description of structural design

Well thought out/ concise/ comprehensive description of structural design with evidence of insight/ initiative (e.g. extended use of software to improve model performance).

Construction Process (20%) Considerations on manufacturability, simplicity, fabrication processes, successes and difficulties encountered

Not addressed

Some coverage of processes

Some coverage of processes with attempt at flow chart and critical analysis

Reasonable coverage of processes including flow chart

Good coverage of processes including flow chart but lacking in completeness of critical analysis.

Concise and comprehensive coverage including a manufacturing process flow chart and critical analysis of performance against cost

Team Reflection (10%) Team roles/responsibilities and evaluation of performance in terms of success, recommendations for improvement

Fails to address reflection task.

Little thought given to planning (coordination, collaboration, communication and control)

Limited coverage of planning and/or critical review of performance.

Adequate description of the planning and execution of the project from a team performance perspective

Good description of planning and execution of project from team perspective missing one or two dimensions

Concise/Comprehensive description of the planning and execution of the project from a team performance perspective covering all dimensions and critical review

Key Lessons Learned (10%) Skill identification, recommendations for the next project

No lessons identified

Shallow attempt at task

Some lessons identified but lacking in critical appraisal.

Lessons identified but lacking in provisional planning

Lessons identified with good critical appraisal and provisional planning strategies discussed

Comprehensive coverage of the task with insightful reflection on learning extending beyond the course

Effectiveness of Organisational Support (10%) What worked, what didn’t, and recommendations for improvement

Not addressed

Shallow attempt at task, unproductive and/or negative feedback

Some attempt at task with variable quality of feedback

Some constructive recs for organisational improvement with limited ownership

Good review of organisational support structure/ critical review of ownership of learning

Insightful and valuable contribution to the improvement of the learning organisation with demonstrated ownership of learning.

ENGG1200: Engineering Modelling and Problem Solving

Affirmation of Non-Attendance/ Late Submission I, ______________________________, affirm that I did not :

attend the ENGG1200 session on _______________________, 2013.

submit/ complete the __________________________ by the due date.

The reason for this was:

Illness Details: __________________________________________

Emergency Details: __________________________________________

Other Details: __________________________________________

If ‘Other’, to ensure that this doesn’t happen again, I will:

________________________________________________________________________

Further to this I am seeking:

a PASS Details: __________________________________________

Other Details: __________________________________________

______________________ Signature ______________________ ______________________ Print Name Student Number Faculty of Engineering, Architecture & Information Technology

Timetable of Sessions and Assessment 2013

Documents

Transcript of Timetable of Sessions and Assessment 2013