Your PaperBike design document is a miniature version of the ME310 Fall Design Document. It intentionally contains many of the same sections and format. The point is to get used to the format, and the process of group creation of a design document, before December.
There is a ~15 min YouTube video from a recent year with advice on the PBike Documents: https://youtu.be/5EH4siXRuSQ -- (suggested viewing speed = 1.5x). The video mentions a Planning section at the end -- this is required for Fall Quarter reports but not for paper Bike documents this year.
Due dates:
Oct 14 for a draft version of the Requirements section (this is the section most teams struggle with). We'll provide quick feedback. Submit this as a Group (your team) on Canvas/Assignments.
Oct 19 for the completed report
Documentation
Your printed and bound final paper bike report is due in class with a PDF digital copy uploaded.
Please name the file with your TeamName and 'PBike' included in the file name!
Each team's report will be reviewed by two members of the teaching team (similar to the practice for many conferences and journals). They will follow a rubric: here are some sample scoring comments. In addition, there will generally be markups on the hardcopy. The point is to provide feedback to make the end-quarter documents as good as possible.
See the PBike Document template for details on the content and sections for this year. If you won't use Overleaf, just compile the template and download the PDF as a guide. There is an older MSWord/Googledoc template but most of the auto-numbering, auto-cross referencing, etc. does not work.
Outline and Sections
Executive Summary - a relatively short stand-alone summary of your bike and what makes it special. It's more than an abstract and it typically contains at least 1 action shot and one assembly view.
Auto-generated TOC. Also Glossary etc.
Context/Problem Statement (need statement, problem statement)
Design Requirements (or sometimes teams find it easier to put this after Development)
Design Development (usually starts with your Vision)
Design Description (or Specifications) - The big question is: could a smart person pretty much recreate your design from what is presented here and in the Appendices?
Resources used
Reflections
Bibliography and Appendices
Binding: We have a machine for this. Ask a TA how to use it.
Please review some of the many examples of previous Paper Bicycle final reports for ideas. Several examples have been attached below. There are also hard copies in the 310 loft. Whoever is doing proofreading, please check out the most common errors (e.g. axel).
These resources are useful for any documentation including the end-quarter reports. Some are from pointers to the old wiki. If prompted, login 'ME310Student', pwd 'PetersonLoft'.
Document Examples
Go to Past Projects and look in the Time Capsule. For each year, there is a folder with PDFs of paper bike documents from that year.
Direct links to some examples from a few years ago:
Tiger Beetle -- a good example from 2015 that introduced the drinking straws needle bearings