> For the complete documentation index, see [llms.txt](https://x.ancorasir.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://x.ancorasir.com/me303-311/2020-autumn/project-work/final-report-and-presentation.md). # Final Report & Presentation ### Overview The Final Report is a collection of documentation that summerizes all design activities of all members of the team, team roles and task roles. * A template is provided here, which should cover the sections explained the [guidelines](https://x.ancorasir.com/me303-311/2020-autumn/project-work/final-report-and-presentation#guidelines-on-final-report). * Refer to your Feishu shared folder to edit the password-protected version, accessible only by all members of your team. * The link to submission is here. * The deadline for submission is on [Wednesday noon on Week 15](https://maindl.ancorasir.com/?page_id=929). * The review will be released [after the Final Presentation on Week 15](https://x.ancorasir.com/me303-311/2020-autumn/weekly-teaching/syllabus#final-exam). ### Guidelines on Final Report A template is provided in your task force’s shared Feishu folder as a Feishu Doc, which can be simultaneously edited by all members on the browser as a collaborative effort. Don’t worry about making changes to the document, as you can access historical versions of the final while preparing it. * General: * Report Name: \[ME303] Final Report by \[Red/Green/Blue/Yellow] \[Apple/Banana/Cherry] * Submitted by: @ System Integrator * Reviewed by: All members of the team * Date & Version: YY-MM-DD-V1.0 * \[Proper use of document style is highly recommended to stay the file organized.] * \[Use the build-in Print function of Feishu Doc to save it as PDFs before making the submission.] * Project Overview \[System Integrator & Information Officer] * Motivation and Need * Design Challenge * Key Outcomes * Team Reflections * Team Roles \[System Integrator] * List of all members & roles * Team Roles * Task Roles for \[Red/Green/Blue/Yellow] \[Apple] on \[Machine Type] * Task Roles for \[Red/Green/Blue/Yellow] \[Banana] on \[Machine Type] * Task Roles for \[Red/Green/Blue/Yellow] \[Cherry] on \[Machine Type] * Teaching staff to your team * Budget & Codes \[Financial Officer] * Code of Ethics * Budget Report * Team Operation * Safety Measures & Risk Management \[Safety Officer] * Tool Management \[Tool Officer] * Site Management \[Team Site Master] * Team Communication \[Yoda Officer] * Task Force \[Red/Green/Blue/Yellow] \[Apple] on \[Machine Type] * (Updated) Design Need Report \[Design Engineer] * (Updated) Engineering Feasibility Report \[Feasibility Engineer] * (Updated) Fabrication & Assembly Report \[Fabrication Engineer & Assembly Engineer] * (Updated) Testing & Optimization Report \[Test Engineer] * Task Force \[Red/Green/Blue/Yellow] \[Banana] on \[Machine Type] * (Updated) Design Need Report \[Design Engineer] * (Updated) Engineering Feasibility Report \[Feasibility Engineer] * (Updated) Fabrication & Assembly Report \[Fabrication Engineer & Assembly Engineer] * (Updated) Testing & Optimization Report \[Test Engineer] * Task Force \[Red/Green/Blue/Yellow] \[Cherry] on \[Machine Type] * (Updated) Design Need Report \[Design Engineer] * (Updated) Engineering Feasibility Report \[Feasibility Engineer] * (Updated) Fabrication & Assembly Report \[Fabrication Engineer & Assembly Engineer] * (Updated) Testing & Optimization Report \[Test Engineer] * Final Remarks \[All members] * A full production line in DesignAIR simulation and an actual production line built as the alpha prototype. * Reflections of the production towards the wasteless project theme. * Discussion of the limitations of the production line * Suggestion to move forward on control and integration towards a working production line. * Reflections by each team member on the learning experience and recommendations to improve the learning experience. ### Guidelines on Final Presentation * Final Presentation \[Video Log Officer] * A 3-minute video presentation of their project learning experience and achievements. * A 10-min presentation, with the Video Log Officer taking the lead in the PowerPoint preparation, assisted by all members of the team. * A total of three members are to be elected by the team to present. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://x.ancorasir.com/me303-311/2020-autumn/project-work/final-report-and-presentation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.