Skills

ME capstone: design, build and test a machine

10 weeks · 2 milestones

Design, build and test a machine: requirements, CAD, analysis, a build or a full simulation, and a test report against the requirements, in a public repo; then a recorded 10-minute demo and talk. The final step of the Varsity Curriculum: Mechanical Engineering, read by a blind review for Honors.

Part of: Mechanical Eng. · Proves for: UG, Career

Milestone map

2 milestones

Design, build and test a machine

8–10 weeks (about 12 hrs/week)

Design, build and test a machine that does a real job: for example a hand-cranked winch, a small wind turbine, a mechanical clock escapement, a line-following cart, or a gripper. Write the requirements first (what it must do, with numbers). Then make the CAD model and drawings, analyse it (loads, stresses, power or motion, with hand calculations and a simulation where it helps), build it — or, if you cannot build it, run a full simulation — and test it against every requirement. Put it all in a public repo. Safety: hand tools and eye protection only. Never machine tools, welding, pressure vessels, combustion, or springs and flywheels that store dangerous energy, unless a trained supervisor is present in a proper workshop. Under 18? Build with an adult present, or simulate the same set-up instead.

Proof required

Link the public repo with the requirements, the CAD files and drawings, the analysis, build photos (or the full simulation), the test plan and a test report that gives each requirement a measured or simulated result and a pass or fail.

What gets checked

Every requirement has a number and a test, and the report gives a pass or fail for each.
The analysis is checked by hand and agrees with the test results, or the gap is explained.
Someone else can rebuild the CAD and rerun the analysis from the repo.

Common mistakes

A build with no requirements or test report.
Analysis that the test results never check.

Powstik Guide

A machine (built, or fully simulated) with its requirements, CAD, analysis and test report, in a public repo.

Steps

Write the requirements, each with a number.
Write the test plan: one test per requirement.
Model it in CAD and make the drawings.
Analyse it by hand, then in simulation where it helps.
Build it with hand tools (or run the full simulation).
Run every test and write the report.

Template

README
Machine:
Requirements (with numbers):
Test plan (test → expected number):
Analysis summary:
Results (measured or simulated → pass or fail):
How to rebuild and rerun it:
What I would change:
Safety: hand tools and eye protection only

What gets sent back

No requirements with numbers, or no test report.
Machine tools, welding, pressure vessels, combustion, or springs and flywheels storing dangerous energy without a trained supervisor.

Resources

Foundationstart here

What a verifier looks for

Do the drawings, analysis and test report describe the same machine?
Are the test numbers measured or simulated, with failed tests reported honestly?
Build photos show hand tools only and eye protection worn: no machine tools, welding, pressure vessels, combustion, or springs and flywheels storing dangerous energy (unless a trained supervisor and a proper workshop are shown).

You'll sign in first, then come straight back here.

Give a 10-minute demo and talk

1–2 weeks

Record a 10-minute demo and talk on your machine for people who know engineering: what it does, how you tested it against the requirements, and what you would change. Then take their questions.

Proof required

Link the recording and the slides, and say who the audience was (for example a study group, a maker club or a class).