Engineering Notebook Team 8149: Panic in the Build Room.
-
Upload
reynold-mckenzie -
Category
Documents
-
view
221 -
download
0
Transcript of Engineering Notebook Team 8149: Panic in the Build Room.
Engineering NotebookTeam 8149: Panic in the Build Room
FormatsHandwritten: •Spiral-bound, laboratory, or
documentation notebooks, loose leaf paper in a binder
•Writing must be clear enough for anyone to read
Electronic:•May use an online program for
documentation•Printed version required in a binder 3” or
smaller for judging
Formats
•Entries in permanent ink- not pencil•Entries made by every team member•“X” or crosshatch unused space•Outline pictures taped into the book and
label picture with the corresponding page number
•When an error is made, cross it out with a single line #24
Organization•Everyone must be able to find anything
they may be looking for•A detailed index is recommended•Tab 8-10 important pages for the judges
to get a good idea of your designs•Number every page
Requirements
•Team Name and number on cover•Summary Page•Engineering Section•Team Section•Business Plan
Summary Page• Attached to front cover• 1 Page Long• Highlights the season• Direct judges to important
pages
Engineering Section
•Record all design processes•Start new page every meeting•Task Column- What your team does•Reflection Column- Thoughts on events and questions to be answered•Include a Bill of Materials
Tips and Tricks
•Calendar App•Do not get behind- You WILL regret it•Have 2-3 main writers/compilers•Make it neat and interesting: pictures
Team Section
•Introduces team members•Give bios including name, age, interests,
and reasons for joining FTC•Include pics for judges•Discuss outreach events and team
activities
Business Plan
•Contains schedules and plans for the season
•Includes future ambitions for the team•Any funding from outside sources and
fundraising events should be recorded
Scheduling
•Several formats to choose from•Do whatever is comfortable and makes
sense•Gant ChartMicrosoft Office ExcelSeries of lines to signify timeContains main sub teams/jobs (design,
build, programming, etc.) as main linesTasks of those sub teams follow
Awards
Any Questions?