Dr Aditya Khanna
Course overview
- Study period
- Semester 2, 2024 (22/07/2024 - 18/11/2024)
- Study level
- Undergraduate
- Location
- St Lucia
- Attendance mode
- In Person
- Units
- 2
- Administrative campus
- St Lucia
- Coordinating unit
- Mech & Mine Engineering School
Design of a powered machine using principles of systems engineering. Synthesis of machine frame, power transmission and controls. Risk and safety assessment. Model-based design using CAD. Basic design for manufacture and cost estimation.
The conceptualisation, design, validation, and operation of complex systems that efficiently and reliably perform their intended function are core to the engineering profession. This course is a capstone course in the ‘Design Stream’ of your curriculum and marks an important milestone in your journey of becoming a professional engineer.
ENGG1100 introduced you to the discipline of professional engineering and its principal fields. MECH2305 followed with an introduction to Engineering Design and Manufacturing. In MECH2100, you learned how to design key machine elements such as bolted connections, gears, and bearings. MECH3610 introduced you to the key concepts of systems engineering and principles of project management. In addition to the ‘Design Stream’ courses, you have also acquired a wealth of foundational knowledge through the other courses in the curriculum. This course will be your first opportunity to put all these learnings to practical use, cement previous learnings, and expand your discipline-specific understanding of systems engineering.
In this course, you are expected to work in teams using systems engineering principles to design, evaluate, build, assemble and test a substantive mechanical system. You will demonstrate the practice of mechanical system design as part of a project team. The course environment simulates the challenges facing a small manufacturing company designing a product for a competitive marketplace.
Course requirements
Assumed background
It is assumed that you have completed 2.5 years of study in mechanical engineering and have demonstrable ability to communicate effectively and work in a team to manage and deliver an engineering design project. Through your prior study, you should have a basic understanding of machine element design, materials selection, and manufacturing processes. You should be familiar with Computer Aided Design (CAD) and engineering drawings. Understanding of systems engineering principles is highly desirable.
Prerequisites
You'll need to complete the following courses before enrolling in this one:
ENGG1400 and MECH2100 and MECH2300
Course staff
Course coordinator
Lecturer
Dr Aditya Khanna
Dr Michael Heitzmann
Timetable
The timetable for this course is available on the UQ Public Timetable.
Aims and outcomes
The aim of the course is to provide you a practical opportunity to conceptualise, design, build, and test a mechanical system as part of a team and using systems engineering principles.
Learning outcomes
After successfully completing this course you should be able to:
LO1.
Identify and describe the key lifecycle steps in system engineering methodology
LO2.
Use the correct system engineering terminology to describe system engineering activities
LO3.
Employ system engineering principles to plan and execute an engineering project
LO4.
Employ system engineering tools and best practice in the appropriate sequence and lifecycle step
LO5.
Put in place appropriate review and reporting milestones for your engineering project and understand milestone requirements
LO6.
Use system engineering and concurrent engineering principles to coordinate multi-team members working one project
LO7.
Optimise the resources in an engineering team to design an innovative mechanical engineering product to a strict timeline and budget conditions
LO8.
Plan, monitor and control a mechanical system engineering project
LO9.
Work in teams to design, build and test a mechanical engineering system
LO10.
Employ engineering principles and science to evaluate design options and perform detailed design
LO11.
Proficiently employ state-of-the-art computer aided engineering tools (CAX) to design, build and validate complex engineering systems
Assessment
Assessment summary
| Category | Assessment task | Weight | Due date |
|---|---|---|---|
| Presentation, Portfolio |
Presentation Series
|
25% |
Conceptual Design Review (10%) 16/08/2024 1:00 pm Detailed Design Review (15%) 13/09/2024 1:00 pm |
| Product/ Design |
System Performance and Build Quality
|
50% |
Week 10 Mon - Week 12 Fri |
| Paper/ Report/ Annotation, Portfolio |
Technical Documentation Review
|
15% |
21/10/2024 1:00 pm |
| Practical/ Demonstration, Product/ Design |
System Disassembly
|
10% |
Exam week 1 Mon - Exam week 2 Fri
Disassembly workshop date TBA |
A hurdle is an assessment requirement that must be satisfied in order to receive a specific grade for the course. Check the assessment details for more information about hurdle requirements.
Assessment details
Presentation Series
- Team or group-based
- Online
- Mode
- Oral, Product/ Artefact/ Multimedia, Written
- Category
- Presentation, Portfolio
- Weight
- 25%
- Due date
Conceptual Design Review (10%) 16/08/2024 1:00 pm
Detailed Design Review (15%) 13/09/2024 1:00 pm
- Other conditions
- Peer assessment factor.
- Learning outcomes
- L01, L02, L03, L04, L05, L06, L07, L08, L09, L10, L11
Task description
Conceptual Design Review - 10%
The submission will be a slide deck in PowerPoint. The presentation will outline the functional baseline of the system and present a project management plan. Detailed requirements will be provided in the project brief document.
Detailed Design Review - 15%
The submission will be a slide deck in PowerPoint accompanied by supporting technical documents (calculations, engineering drawings, etc) in Teamcenter PLM. During class time in Week 8, each team will present their slides to the rest of the class via a live presentation or a prerecorded video. The presentation will be held online using Zoom since parallel streams of sessions are required to accommodate the large number of teams. Detailed requirements will be provided in the project brief document.
NOTE: You shouldn't need to make substantial design changes after submitting your detailed design review. However, in case you make design changes, these need to be reflected in the Teamcenter environment, i.e., you must maintain an accurate digital twin of your physical model.
Submission guidelines
PowerPoint slide decks to be submitted via Blackboard. Technical documents to be submitted via Teamcenter PLM.
Deferral or extension
You may be able to apply for an extension.
The maximum extension allowed is 7 days. Extensions are given in multiples of 24 hours.
This is a team exercise and extension requests will only be granted in exceptional circumstances as extensions impact other students in the team.
A Student Access Plan (SAP) can only be used for a first extension. Extensions based on an SAP may be granted for up to seven (7) days, or the maximum number of days specified in the Electronic Course Profile (ECP), if it is less than seven (7) days. Any further extensions will require additional supporting documentation, such as a medical certificate.
Late submission
You will receive a mark of 0 if this assessment is submitted late.
Oral presentations scheduled with multiple markers and are time limited.
System Performance and Build Quality
- Hurdle
- Team or group-based
- In-person
- Mode
- Activity/ Performance, Product/ Artefact/ Multimedia
- Category
- Product/ Design
- Weight
- 50%
- Due date
Week 10 Mon - Week 12 Fri
- Other conditions
- Peer assessment factor.
- Learning outcomes
- L06, L07, L08, L09, L10, L11
Task description
System Performance - 25%
The performance criteria are specified in the project brief document. Several testing days are scheduled in Week 10-12 for teams to demonstrate system performance against the scoring method outlined in the project brief document. A detailed testing schedule will be communicated to students via Blackboard.
NOTE: Teams can compare the performance of their prototype system against other teams in a tournament format during Week 13. Participation in the tournament is optional and a maximum of 3% bonus marks will be available to the winning team.
Build Quality - 25%
Teams must hand over their prototype system to the teaching staff upon achieving their final performance score unless participating in the optional tournament. Those participating in the optional tournament must deposit their prototype system to the teaching staff at the conclusion of the tournament. Teams must hand over the system as-is after testing, i.e. without modifications. Teams are not permitted to take away any part of the system. The build quality will be assessed by a panel of experts at a later date. Further details are provided in the project brief document.
Hurdle requirements
Teams must achieve a non-zero score during performance testing to pass the course.Submission guidelines
Physical products are submitted to the teaching team after performance testing.
Deferral or extension
You cannot defer or apply for an extension for this assessment.
Teams will be given multiple opportunities to complete performance testing between Weeks 10 and 12. No further testing opportunities will be provided after Week 12. Extensions impact on other students in the team.
Late submission
You will receive a mark of 0 if this assessment is submitted late.
Demonstration sessions are scheduled with multiple markers and is time limited.
Technical Documentation Review
- Team or group-based
- Online
- Mode
- Product/ Artefact/ Multimedia, Written
- Category
- Paper/ Report/ Annotation, Portfolio
- Weight
- 15%
- Due date
21/10/2024 1:00 pm
- Other conditions
- Peer assessment factor.
- Learning outcomes
- L01, L02, L03, L04, L05, L06, L07, L08, L09, L10, L11
Task description
The teaching team will assess the completeness of technical documents in the Teamcenter PLM environment. This assessment will evaluate your team's compliance with the model-based design approach, outcomes of system verification and validation undertaken in Weeks 9-12, and reflections on your engineering design decisions and project management. Detailed requirements will be provided in the project brief document.
Submission guidelines
Technical documents to be submitted via Teamcenter PLM.
Deferral or extension
You may be able to apply for an extension.
The maximum extension allowed is 7 days. Extensions are given in multiples of 24 hours.
This is a team exercise and extension requests will only be granted in exceptional circumstances as extensions impact other students in the team.
Late submission
A penalty of 10% of the maximum possible mark will be deducted per 24 hours from time submission is due for up to 7 days. After 7 days, you will receive a mark of 0.
System Disassembly
- Team or group-based
- In-person
- Mode
- Activity/ Performance
- Category
- Practical/ Demonstration, Product/ Design
- Weight
- 10%
- Due date
Exam week 1 Mon - Exam week 2 Fri
Disassembly workshop date TBA
- Other conditions
- Peer assessment factor.
- Learning outcomes
- L04, L06, L09
Task description
During the examination period, a disassembly workshop will be organised in which teams will use basic hand tools to disassemble their prototype system. A panel of experts will evaluate the ease of system disassembly and the reusability of sub-systems, components, and parts. Further details will be provided in the project brief document.
Submission guidelines
Teams to return in examination period to disassemble their prototype system under supervision and leave behind all disassembled materials.
Deferral or extension
You cannot defer or apply for an extension for this assessment.
Individuals who are unable to attend the disassembly workshop with an acceptable reason as defined on my.UQ will receive the average team mark.
Late submission
You will receive a mark of 0 if this assessment is submitted late.
The system disassembly workshop are scheduled with a panel of experts and are time limited.
Course grading
Full criteria for each grade is available in the Assessment Procedure.
| Grade | Cut off Percent | Description |
|---|---|---|
| 1 (Low Fail) | 0.00 - 29.99 |
Absence of evidence of achievement of course learning outcomes. Course grade description: Fail: Overall grade |
| 2 (Fail) | 30.00 - 44.99 |
Minimal evidence of achievement of course learning outcomes. Course grade description: Fail: Overall grade 30.0 to 44.99%. |
| 3 (Marginal Fail) | 45.00 - 49.99 |
Demonstrated evidence of developing achievement of course learning outcomes Course grade description: Fail: Falls short of satisfying basic requirements for a Pass. Overall grade: 45-49.99% or zero performance testing score. |
| 4 (Pass) | 50.00 - 64.99 |
Demonstrated evidence of functional achievement of course learning outcomes. Course grade description: Pass: Satisfies all of the basic learning requirements for the course, such as knowledge of fundamental concepts and performance of basic skills; demonstrates sufficient quality of performance to be considered satisfactory or adequate or competent or capable in the course. Overall grade 50-64.99% and a non-zero performance testing score. |
| 5 (Credit) | 65.00 - 74.99 |
Demonstrated evidence of proficient achievement of course learning outcomes. Course grade description: Credit: Demonstrates ability to use and apply fundamental concepts and skills of the course, going beyond mere replication of content knowledge or skill to show understanding of key ideas, awareness of their relevance, some use of analytical skills, and some originality or insight. Overall grade 65-74.99% and a non-zero performance testing score. |
| 6 (Distinction) | 75.00 - 84.99 |
Demonstrated evidence of advanced achievement of course learning outcomes. Course grade description: Distinction: Demonstrates awareness and understanding of deeper and subtler aspects of the course, such as ability to identify and debate critical issues or problems, ability to solve non-routine problems, ability to adapt and apply ideas to new situations, and ability to invent and evaluate new ideas. Overall grade 75- 84.99% and a non-zero performance testing score. |
| 7 (High Distinction) | 85.00 - 100.00 |
Demonstrated evidence of exceptional achievement of course learning outcomes. Course grade description: High Distinction: Demonstrates imagination, originality or flair, based on proficiency in all the learning objectives for the course; work is interesting or surprising or exciting or challenging or erudite. Overall grade 85 - 100% and a non-zero performance testing score. |
Additional course grading information
All the assessments in MECH3100 are team-based. Students must attend team meetings and meaningfully contribute to team assessment items to demonstrate the course learning outcomes. This will be captured via the ‘digital footprint’ in the PLM software, attendance records/meeting minutes at team meetings, and through peer assessment.
Peer Assessment (PAF multiplier)
Each team is responsible for establishing a mutually acceptable division of workload between team members early on in the semester. If the performance of individual members deviates from the agreed plan, the PAF multiplier offers teams a mechanism for grade redistribution within a team. In a balanced team, all team members should receive a PAF multiplier of 1.0, implying equal contribution. The PAF of any individual student is capped at 1.2 or one grade level above the total team mark, whichever is lower. There is no lower bound on the PAF, i.e., students that do not contribute to the team exercises can receive a mark as low as zero for the course.
Teams must submit Peer Assessments in week 6 and 13 via Blackboard. The two peer assessment factors will be averaged unless there is overwhelming compelling reason not to do so (at the discretion of the course coordinator). The results from the peer assessments will be used to scale the final course marks and can increase or decrease individual marks without changing the total marks obtained by the team. Attendance records and the digital footprint in Teamcenter will be used for dispute resolution. Further details will be provided in the project brief document.
Effective Team Membership - Attendance and Contribution
Team members must attend and actively contribute to team meetings. Attendance and contribution can be both in person or virtually via meeting platforms such as Zoom. Students who fail to attend and contribute to at least 50% of team meetings will not receive team marks towards team assessment activities. Attendance at team meetings (including the studio session) must be recorded.
All team members are responsible for establishing mutually agreed meeting times at the beginning of the project. Each team will decide their own meeting time, but one allocated meeting time is expected to be the studio contact session.
The team manager will collect meeting minutes and document attendance and contributions as well as action items for each team member. At the end of semester, the team manager will upload a summary of each team member's attendance (and contribution where relevant), as well as documented evidence, to Teamcenter PLM. The team meeting minutes must include a timesheet for all team members, a simple table will suffice. Each student is expected to contribute 10 hours per week to the course, the time spent should be evidenced by outputs and acknowledged by the team members.
All team members are required to keep regular records (updated weekly) of the tasks/activities that they have been completing towards the team exercises. These records can be kept in a physical logbook or as electronic records in Teamcenter PLM (preferred). Where possible, evidence of work should also be logged. Record keeping, especially Teamcenter activity, is important and may be used as evidence if there are disputes about the contribution of individuals to the team project.
Supplementary assessment
Supplementary assessment is not available for this course.
Additional assessment information
Students will not be given exemptions, or partial credit from any previous attempt of this course, for any piece of assessment. You must complete all of the learning activities and assessment items each time you take a course.
A failure to reference AI use may constitute student misconduct under the Student Code of Conduct.
Detailed task descriptions and marking criteria are available on Blackboard.
Learning resources
You'll need the following resources to successfully complete the course. We've indicated below if you need a personal copy of the reading materials or your own item.
Library resources
Find the required and recommended resources for this course on the UQ Library website.
Additional learning resources information
Other suggested learning resources will be posted to the Blackboard site, it is your responsibility to check Blackboard frequently.
Learning activities
The learning activities for this course are outlined below. Learn more about the learning outcomes that apply to this course.
Filter activity type by
Please select
| Learning period | Activity type | Topic |
|---|---|---|
Multiple weeks From Week 1 To Week 13 |
Studio |
Design Workshop Workshops on key system engineering principles and their use in your project. During the workshop you also have time to meet with your mentors and team members. Learning outcomes: L01, L02, L03, L04, L05, L06, L07, L08, L09, L10, L11 |
Team Based Learning |
System prototyping As a team, you will fabricate and assemble a physical prototype of your designed system using the resources in UQ Innovate. Learning outcomes: L03, L04, L07, L08, L09, L11 |
|
Multiple weeks From Week 10 To Week 13 |
Team Based Learning |
Performance testing You will perform testing to validate your physical system against the requirements provided in the project brief. Learning outcomes: L01, L02, L03, L04, L05, L06, L07, L08, L09 |
Policies and procedures
University policies and procedures apply to all aspects of student life. As a UQ student, you must comply with University-wide and program-specific requirements, including the:
- Student Code of Conduct Policy
- Student Integrity and Misconduct Policy and Procedure
- Assessment Procedure
- Examinations Procedure
- Reasonable Adjustments - Students Policy and Procedure
Learn more about UQ policies on my.UQ and the Policy and Procedure Library.