Documente Academic
Documente Profesional
Documente Cultură
MASTER PLAN
2018-2019 ROVER RUCKUS
1
Welcome to team Mythic 9459!
We are a team of students from Great River School, ranging from 7th through 10th Grade,
participating in a program called First Tech Challenge. Each year we engineer a new robot
and compete with other teams from Minnesota.
We are excited about your interest in the team! You will find the experiences rewarding,
educational, and enjoyable. This handbook is intended to give you an understanding of the
program and your responsibilities as a team member. In the following pages, you will find
lots of information that will guide you throughout your robotics journey.
This year will introduce the biggest change that has ever been implemented in our FTC
program - defined structure. The goal is to create a team which will keep on growing,
learning, and succeeding. We intend to achieve this by creating a detailed infrastructure that
will guide the team into the future.
Please review all the information carefully. If you have any questions that this handbook has
not covered or if there are questions regarding any topic, do not hesitate to ask a
Leadership member.
With appreciation,
Vasyl Shevtsov
Team Captain
CONTACT INFORMATION
SPONSORS
3
Section One - General Information and Schedule
General Information.......................................................................................1
Registration ..............................................................................................................1
Homework and Grades .............................................................................................2
Team Communication ...............................................................................................2
Transportation ..........................................................................................................3
Food ........................................................................................................................3
Rules ...............................................................................................................4
Behavior ...................................................................................................................4
General Safety .........................................................................................................5
Schedule .........................................................................................................7
Attendance ...............................................................................................................7
Calendar ..................................................................................................................7
Kickoff Schedule .......................................................................................................8
Important Days ..............................................................................................9
4
GENERAL INFORMATION
REGISTRATION
Team Signup: When you are ready to join the team, please fill out this form: eepurl.com/
dCzAoP . This is also our email list form, so every person who wants to receive email
updates needs to individually fill out this form. Each student needs to fill out this form. Each
parent also has to fill it out with their own information.
Student Contract: When you are ready to join the team, please sign the Student Contract
on the last page of this document. Hand to Vasyl or Heather.
Fee: When students commit to the team, we have a suggested cost for the year at $200 per
student. Actual cost should be decided by each family based on ability to pay, as long as
each family does contribute something. Families are also welcome to pay more to subsidize
other students. Please make checks payable to "GRS Foundation" along with "FTC" and
your child's name(s) in the memo field. Hand to Vasyl, Heather, or Toby.
FIRST Signup: In addition to the Team Signup and Fee, each family must register the
student with FIRST at firstinspires.org. At the top right of the page, there is a button
1
labeled "Register". It will take you to a signup page. Attention Parents: Register yourself
on this page for a new FIRST account, not your child. Enter your name, email address, and
birthdate, not your child's. You will be able to add your child and apply to a team under the
Parent/Guardian - Youth tab on your dashboard after your account has been created.
Read the Youth Protection Program Guide: The commitment to safety is a core value at
FTC and we strive to provide every team member with the safest possible experience as
they learn and grow through our program. We cannot do this alone, but working together
with you, we can help make your child’s experience with FTC a safe one. These Guidelines
for Parents provide you with important information to help us do this. firstinspires.org/
sites/default/files/uploads/about/FIRST-YPP-ProgramGuide.pdf
If you have any questions or need any help, email Toby at tobymcadams@gmail.com
Your academic performance and grades are your and everyone’s highest priority. If you have
assignments that you need to finish or are falling behind in class, have a Developing grade
or lower, or have a letter grade C or lower, you should not be at robotics. Do not use
robotics as an excuse for not turning in an assignment or turning in an assignment late. If
you need to miss a meeting or event to do school work, please let a captain or mentor know
as early as possible. Homework help is Tuesdays and Thursdays, which you should attend
instead of FTC. We will be doing grade checks at a certain point to see if you need any help.
Students who are traveling or competing with the team should notify their teachers early in
the semester so that teachers can try to avoid scheduling important dates (exhibitions, field
trips, project due dates, etc) at the same time as a competition.
We use email and Slack to communicate. All announcements will also be on the team
website.* Announcements are made by email to all members and parents, along with an
announcement in Slack in the #ftc-general Channel.
Email - Students are expected to have an email account that they check regularly. Students
should check their email at least once a day throughout the year since the team does
2
continue having events during the summer. Students should reply in a timely manner (within
24 hours) to let the sender know they have received the email.
Slack - When you fill out the team signup we automatically send an invite to students to join
the GRS FTC Slack workspace. You will receive an email being invited to join our workspace.
You are automatically added to the #ftc-general and #non-ftc channels. Parents are also
welcome to join the Slack workspace and can email FTC to request an invitation.
With Slack, you can always get to our workspace in a browser - grsftc.slack.com . There are
also Mac and Windows desktop and phone apps. These aren't required, but we suggest
getting them. They're highly customizable - you can set to get alerts by channel, time of day,
phone vs. computer, only when you're mentioned, only with specific keywords, etc.
When you create an account, use your full name. When choosing your display name, please
either use your first or full name. Don't make up a different display name. There are many
other channels you can join that are specific to subgroups. Anyone can join, but channel
discussion/content should be appropriate to the channel description.
*The team website is currently not functioning. We will notify when the website is working
and up to date.
TRANSPORTATION
It is always great to have organized carpooling for transport to and from robotics. When you
sign up to be on the team we ask you to share your address. We then see who lives close to
each other and recommend close families to get in contact with each other about transport.
When transporting to and from events far away from school, we suggest using Great River
School as a dropping point to transfer to another car.
Transporting materials to and from competitions can also be tricky, so when an event
approaches we send an email asking if anybody has a large car and is willing to help drive
materials to the competition.
We will always have a mentor wait until all students have left a practice or event.
FOOD
There are multiple ways that families can help support the GRS FTC teams. One of those
ways is by signing up to bring snacks! Please plan to have enough snacks for 20. We
3
recommend to send them to school with your student, but you can also drop off before 4:00
PM. Sign up here ahead of time: tinyurl.com/ftcsnacks . Thank you!
Fifteen minutes before meetings start snacks are rationed out to all members. Everyone is
expected to be finished eating their snack before the meeting starts. Everyone is also
welcome to bring their own snacks.
For meetings that go until 8:00, we will have dinner from 6:00 - 6:30. We ask that parents
volunteer to bring dinner. Please plan to have your meal ready at 6:00 PM and provide
enough food to feed 20. Feel free to drop off at 6:00, or earlier if it can be kept warm, like a
crockpot. We will not have kitchen space to use. Sign up here ahead of time: tinyurl.com/
ftcdinner . Thank you!
Allergy and food restrictions are provided in the signup link. Thank you so much for bringing
food, we really appreciate it!
RULES
While the team has its own rules and expectations, all school rules still do apply. For
example, if something is not covered in this Master Plan, but there is a school rule or policy
- the school rule or policy still applies.
B E H AV I O R
• Come to FTC to do robotics. This is not an afterschool daycare. If you're not here to do
robotics, please do not join the team.
• Students should conduct themselves in a professional manner at all times. This means
dressing appropriately for an event or meeting, using appropriate language, etc.
• As a member of our team, you will be treated respectfully, and you will treat others
respectfully.
• Students are expected to maintain a team-first attitude. Students should always be asking
themselves “What can I do to help my team succeed?”. In the end, people rarely
remember individual performances. What people always remember is what the team
accomplishes.
4
GENERAL SAFET Y
Illness - If you are sick, stay away from robotics. This is especially true during build season
when the team works in close quarters. Students who come to robotics sick can easily get
other students and mentors sick. Please be respectful of others and stay home. Any student
who comes to robotics and is sick will be signed out and sent home.
Dress Code - Always wear closed-toe shoes. Don't wear loose clothing or dangling jewelry.
Long hair should be tied back.
Glasses - Everyone must wear ANSI Z87.1 certified safety glasses whenever you're near a
work area. Prescription glasses with ANSI Z87.1 approved commercial off the shelf side
shields are also allowed. Our team provides safety glasses to wear, but you can also buy
your own certified safety glasses if you choose.
Hearing Protection - When near loud noises or using loud equipment, always use ANSI
S3.19 Certified hearing protection. Our team will provide hearing protection, but you can
also buy your own certified hearing protection if you choose.
Power Tools - Using power tools is encouraged (because power tools are cool), but you first
need to go through a safety course. First, read the operating manual of that power tool.
Then learn more about using that tool through online videos and tutorials. Once you have
done that, you need to be trained about how to safely use the tool by an adult mentor AND
documentation of this training must be completed before the student will be permitted to
use that tool.
When finished using a tool, it must be returned to its designated location in the workspace.
Electrical - Electrical devices of any kind must NEVER be powered by daisy-chaining cords
or power strips.
Unsafe Behavior - No horseplay and do not wander around. Always let a mentor or captain
know before leaving. Remember to use common sense whenever doing anything. Wear
additional safety gear whenever required. If you observe any unsafe behavior or interactions
please speak up and attempt to stop that behavior through conversation. If that doesn't
work, talk to a mentor or captain.
5
Accidents - Any accident, no matter how small, MUST be reported to an adult.
Safety Captain - This year we will also be introducing a new role of a Safety Captain. The
Safety Captain's job is to remind others to stay safe and remind students to follow these
rules!
Robot -
• Robot must be turned off and battery disconnected before repairing or adjusting.
• When lifting the robot, always hold the frame and not any moving or weak parts.
• When transporting the robot, always use the robot cart. Do not carry the robot.
• Do not drop the robot. If the robot was dropped, report to an adult immediately.
Batteries -
• If batteries are HOT (not just warm), unplug and report to an adult immediately.
• Never leave batteries charging unattended, always make sure batteries are
unplugged before leaving practice.
6
SCHEDULE
ATTENDANCE
This 2018-2019 robotics season Mythic is meeting on Tuesdays and Thursdays. Snacks will
be distributed at 3:45, and meetings will begin at 4:00. Thursday meetings extend to 8:00
with a dinner, but it is ok for students to leave at 6:00. Tuesday meetings are more focused
and are from 4:00 - 6:00, and only members with active projects should attend. Tuesdays will
be especially focused and members who are not contributing to the productive work
environment will be asked to leave.
As a full-time member of Mythic, you are required to attend a minimum of one practice a
week during build season.
All students are required to submit at least a week ahead which meetings they will attend.
On days when meetings go after 6:00, students are also required to submit a week ahead
whether they will be staying for dinner. This is so that we know how much food to provide
and plan for absences. tinyurl.com/grsftcattendance
All members are required to attend all events unless individually excused. Examples of
events include but are not limited to Kickoff, competitions, fundraising, and celebrations.
In the case of an unexpected absence, your parent or guardian needs to contact a mentor
and notify them of the absence as soon as possible.
CALENDAR
Summer Season: Officially starts the day school ends. Meetings are typically held weekly
and are optional. Anyone is allowed to come and participate. The focus of these meetings is
for individuals and sub-groups to focus on learning and doing fun projects in order to
prepare for the upcoming build season.
Build Season: Officially starts on the day of Kickoff, this year it is on September 8th. During
build season the team designs and builds a competitive robot. This is the most important,
most busy, and most stressful part of the robotics year.
7
Off-Season: This is the season between Build and Summer. It starts when the team can no
longer advance in competitions. During the off-season, meetings are weekly but optional.
The difference between Off-Season and Summer Season is that during Off-Season meetings
have a tendency to skip weeks because of school-related work and events. Meetings
typically don't happen towards the end of the year to allow students to prepare for exams.
Before Kickoff: It is very important to create anticipation before kickoff. Students need to
be ready and excited to build the robot. Kickoff is the most exciting part of the year!
September 8th: Attend the Kickoff event and breakout sessions at the U of M. After the
Kickoff event, hold a half hour discussion where all members shout out different ideas! It is
very important to let students be excited. DO NOT sit down and read the rules right away.
Have everyone get ideas out of their heads. Then have students individually read the
manual still at the meeting. Once everyone has read the rules, talk about all the different
things that the robot could do. Which actions do we want to do?
Next Meeting: Once those actions are picked, go and prototype examples of those actions.
Just small scale prototypes, nothing complicated. Once these simple prototypes are
experimented with, have a team discussion. Figure out what worked and what didn't.
Prioritize different mechanisms and talk about what we learned.
Next Meeting: Choose a couple prototypes to build/model with REV. Make prototypes all
meeting.
Next Meeting: Finish up prototypes. Once we have tested the possible solutions, hold a
team discussion and choose which ones you want to move forward with.
8
I M P O R TA N T D AYS
Workshop - These events can cover a variety of FIRST Tech Challenge and robotics-related
topics. They are often hosted by vendors, Affiliate Partners or teams.
Kickoff - Held each September, this event is when the new season’s game is revealed.
Kickoff offers the opportunity to see the game reveal live, network with other teams and
strategize about the new season.
Scrimmage - A small event run by volunteers, usually a team or Affiliate Partner, good for
practice and playing experience. These events can have anywhere from three to
twenty teams and may not include judging and awards. These events do not qualify teams
for championship tournaments. May also be called a Practice Day.
Qualifying Tournament - These events are held in areas with a large number of teams. In
these events, teams compete for positions at Championship Tournaments.
Qualifying Tournaments adhere to FIRST standards in format, judging, and awards.
Super-Qualifying Tournament - These events are held in regions with a large number of
teams and/or Leagues. In these regions, teams advance from either a League Championship
or Qualifying Tournament to a Super-Qualifying Tournament, and then to the regional or
State Championship. Super-Qualifying Tournaments adhere to FIRST standards in format,
judging, and awards.
9
Section Two - Specific Guide to Everything
Engineering Notebook..................................................................................11
10
ENGINEERING NOTEBOOK
One of the goals of FIRST and FIRST Tech Challenge is to recognize the engineering design
process and the journey that a team makes. This journey encompasses the phases of the
problem definition, concept design, system-level design, detailed design, test and
verification, and production of the robot.
Throughout the process of designing and building a Robot, teams will come across
obstacles, lessons learned, and the need to draw things out on paper. This is where teams
use an Engineering Notebook. These notebooks track a team from the beginning of the
season and throughout the Competition season. Judges review a team’s Engineering
Notebook to better understand the journey, design, and team as a whole.
The Engineering Notebook is a documentation of the team’s Robot design and records the
time spent doing research, outreach, team meetings, and plans for growth. This
documentation should include sketches, discussions and team meetings, design evolution,
software development, processes, obstacles, and each team member’s thoughts throughout
the journey for the entire season.
_____________
The Engineering Notebook is incredibly important. Three out of six teams advancing from
the League Qualifying Tournament this year will be doing so because of an award. And
every single award requires an Engineering Notebook submission. It is obvious that the
Engineering Notebook is crucial to increasing our chances of advancing to the MN State
Championship.
11
JOBS AND RESPONSIBILITIES
LEADERSHIP HIERARCHY
Big picture coordination and logistics of all teams in Mythical Robotics. In charge of
events, registration, and money. Does not have a role regarding the content of the robot.
The Teacher Liaison helps with navigating the administration and school related things.
Should always be a teacher.
The Coach is an adult that is responsible for day-to-day operations regarding executive
responsibilities. The Coach registers the team for season and competition events, keeps
track of the team budget, collects team fees, and keeps receipts on file for all purchases.
Regarding discipline, the Coach is in charge of handling student issues and communicating
with parents.
Mentors are adults that are responsible for guiding students with their projects.
Mentors don't have as many executive responsibilities as the Coach. It should be noted that
Mike Koch is the Coach for team Athena.
The Team Captain is in charge of overseeing and coordinating operations of the team
and sub-groups. The Captain keeps up morale and is the face of the team, setting high
standards and communicating team expectations. More responsibilities include giving
sponsorship presentations and speaking at informal presentations, applying for grants and
awards, keeping the Master Plan up to date, running opening and closing meetings at
practice, bringing discipline issues to the Coach's attention and mediating as appropriate,
communicating about the budget, giving input on setting the meeting times and dates,
teamwide communication and email updates, and setting the agenda for each practice. The
captain is responsible for knowing the Game Manual rules thoroughly.
12
MENTORS
Mentors do not pay the team fee. Mentors are not expected to bring meals (unless they are
also parents). Mentors receive a t-shirt each year, as well as food and lodging while traveling
with the team. Monetary contributions from mentors are not necessary (you’re giving your
time!) but are always welcome.
We encourage you to check with your work for matching donations. Some workplaces match
volunteer hours with monetary donations.
Obtain FIRST Youth Protection Clearance (YPC), before beginning regular involvement with
the team: firstinspires.org/sites/default/files/uploads/about/us-screening-steps.pdf
Undergo training in youth protection once regular involvement with a FIRST program starts
and at least every 36 months thereafter.
SUB GROUPS
Build - Engineering and solving design challenges to create the physical robot. Hands-on
work with parts and tools, solving problems through tough work and perseverance.
Computer Assisted Design (CAD) - Any CAD member must be an active Build member.
Members design the final robot design in CAD, along with parts to 3D print or manufacture.
Requires good visual imagination and creativity, perseverance, and good problem-solving.
Must have good computer skills. CAD members need to learn how to use the 3D printer
well.
13
Programming - Write code to make the robot move. Use the programming language Java
in Android Studio. Need to be good at computers and logical computations. Lots of
dedication and hard work required.
Social Media and Design (SMaD) - In charge of our team look. Includes website
development, social media, branding, and any designs for posters and logos. In charge of
taking pictures and managing the archive. Works with Captain and Awards/Engineering
Notebook on Team Judging Interviews.
JOBS
Build Captain - A veteran build team member that coordinates the build team. Has good
technical skills and knowledge. Works with the team captain to make sure that the build
team is doing their best. Has incredible drive and must push the build team hard.
CAD/3D Printing Captain - A veteran build team member that has very strong technical
skills in SolidWorks and 3D Printing. Works with the Build Captain to coordinate the CAD
team in designing the robot. In charge of operating and using the 3D printer, handles
technical issues and questions
Programming Captain - A veteran programmer that has very strong technical skills. Must
have the drive to push programming to the limits. Works with the team captain to make sure
the programming team is doing their best.
SMaD Captain - A veteran member that has good computer and social media skills. Pushes
SMaD team to the limits. In charge of creating and maintaining the Brand Standards
guidebook. Works with the team captain to make sure the SMaD team is doing their best.
Safety Captain - In charge of reminding everyone to stay safe. Can be from any sub team.
Cannot be a captain from another sub-group. Also in charge of keeping an inventory of all
safety equipment.
14
Website - Mythic needs to get a website up and running. Website responsibilities: Brief
summary updates from every meeting, team announcements, photos from events and
meetings.
Photography and Documentation - SMaD members are responsible for taking pictures and
archiving them. We don't have a team camera, so try to use a SMaD member's phone.
Upload pictures to the Google Drive Archive and make sure to organize in folders by date/
event. Then post to appropriate social media platforms.
Interview Session Observer: Takes notes on the Self-Reflection Sheet during the interview.
This person should be a keen, unbiased observer and a good note-taker. Jots notes on the
Self-Reflection Sheet immediately after the Judging Interview session. Takes notes during
team judging reflection session.
Master Plan - This is a document which needs constant updating. It is the job of the team
captain to respond to input/suggestions and always keep it updated and accurate. In the
future, our team will refine our handbooks. Take inspiration from other teams:
chiefdelphi.com/forums/showthread.php?t=165773
Reading the Game Manual - Every single member on the team Mythic needs to read both
Game Manual Part One and Game Manual Part Two. It is the job of the team captain to
know the manual very thoroughly and to know the rules better than anyone.
Cleanup - At the end of practices we have a 10 minute cleanup time. Along with putting
away all the materials you were using, individual team members also have specific jobs.
Team captain creates the jobs, and build team needs to create a job board (one doesn't
exist currently.) Jobs are not cycled, instead, every person has a permanent cleanup job.
Passwords - All passwords are to be stored in a Google Doc only accessible to team
Leadership. Only Leadership members are allowed to create and know passwords.
15
RESOURCES
TEAM RESOURCES
Master Plan: GRS FTC Google Drive < Mythic < Master Plan PDF
Attendance: tinyurl.com/grsftcattendance
Calendar: tinyurl.com/grsftccalendar
High Tech Kids is a Minnesota 501 (c)(3) nonprofit and is an affiliate partner of
FIRST charged with supporting FIRST LEGO League Jr, FIRST LEGO League, and FIRST Tech
Challenge teams in Minnesota by offering training, tournament opportunities, volunteer
coordination and community outreach. hightechkids.org
FIRST RESOURCES
The FIRST website is the main place for general information at firstinspires.org. The
First Tech Challenge Game and Season Info webpage contains quick links to everything at
firstinspires.org/robotics/ftc/game-and-season.
The MOST important FIRST resource is the Start a Team webpage. It has
everything you need to educate yourself and find information:
firstinspires.org/robotics/ftc/start-a-team
16
Youth Protection Program: firstinspires.org/resource-library/youth-protection-policy
17
Outreach and Marketing Resources: firstinspires.org/resource-library/ftc/team-outreach-
and-marketing-resources
Events: firstinspires.org/robotics/ftc/event-types
Awards: firstinspires.org/robotics/ftc/awards
FTCHELP
FTCHelp is a non-profit group in which multiple different FTC teams, mentors, and FTC
enthusiasts help post topics. The FTCHelp organization was created by the FTC team
Caffeinated Robots. Topics consist of help for all aspects of FTC. ftchelp.org
FTCHelp Docs: FTCHelp Docs is a collection of FTC help documents. Those documents are
aimed to help FTC teams with their questions about different aspects of FTC. These topics
are added and controlled by the FTCHelp moderators. docs.ftchelp.org
FTCHost: FTCHost's goal is to help FTC teams host their websites and domains for a low
cost. We are or have been on a team too, and we know that funding can be complicated
and hard to get. That is the reason we are creating FTCHost. Our servers are fast and have
the ability to scale to any need. SSL, weekly backups, and all other security measures are
provided for no extra cost. ftchost.org
18
YO U T U B E
An incredible platform with a gigantic amount of resources. There are many teams that
post how-to guides, robot reveals, and lots of other information. There are also videos from
companies like Servocity, and even FIRST with incredible tutorial videos. I also have a public
YouTube playlist with lots of random FTC videos. The FIRST Tech Challenge channel also has
a playlist collection that I recommend exploring.
AndyMark: youtube.com/user/AndyMarkTube
ServoCity: youtube.com/user/ServoCity
TETRIXrobotics: youtube.com/user/TETRIXbyPitsco
19
REDDIT
This is my favorite place online for FTC. You can find answers to almost any question
you have on the FTC subreddit! You will also find lots of robotics memes. It is a great
community to check out!
FTC: reddit.com/r/FTC
FRC: reddit.com/r/FRC
FLL: reddit.com/r/FLL
Robotics: reddit.com/r/robotics
DISCORD
The Orange Alliance is a project by REV Robotics to help make FTC match, event, and
team information more accessible. theorangealliance.org
PART SUPPLIERS
REV Robotics: REV Robotics was founded in August of 2014 by two friends; Greg Needel
and David Yanoshak. Combined, they have more than 20 years of experience in nearly every
level of the FIRST robotics program. Their collective experience makes the two of them
uniquely qualified to design and provide the highest-quality products to the FIRST robotics
community and beyond. revrobotics.com/about
20
McMaster-Carr: McMaster-Carr Supply Company is a private, family-owned supplier of
Maintenance, Repair and Operations materials and supplies. McMaster maintains over
570,000 products in a catalog offering a variety of mechanical, electrical, plumbing, and
utility hardware not usually located from a single source. mcmaster.com
VEX Robotics: VEX Robotics creates tools that educators and mentors will use to shape the
learners of today into the problem-solving leaders of tomorrow. vexrobotics.com .
FIRST Tech Challenge Products: vexrobotics.com/vexpro/ftc
Find Robot Parts: This website was made by members of FIRST Robotics Team 1735, The
Green Reapers, from Worcester, MA. findrobotparts.com
Adafruit: Adafruit was founded in 2005 by MIT hacker & engineer, Limor "Ladyada" Fried.
Her goal was to create the best place online for learning electronics and making the best-
designed products for makers of all ages and skill levels. adafruit.com
eBay: An American multinational e-commerce corporation based in San Jose, California that
facilitates consumer-to-consumer and business-to-consumer sales through its website.
ebay.com
PROGRAMMING
CodeCademy: CodeCademy is an online interactive platform that offers free coding classes.
codecademy.com
GitHub: GitHub is a development platform where you can host and review code, manage
projects, and build software alongside 20 million developers. github.com
21
Learn Git: try.github.io
OpenCV: Open Source Computer Vision Library is an open source computer vision and
machine learning software library. opencv.org
Android Studio: Android Studio is an integrated development tool that lets teams create
Java (text-based) programs for their competition robots. Android Studio offers great
flexibility when writing a program for a competition bot. developer.android.com/studio/
FTC Android Studio project to create the FTC Robot Controller app: github.com/
ftctechnh/ftc_app
SolidWorks Licenses: Our FTC team is sponsored by SolidWorks, and we have licenses to
give to our student members. Talk to a Leadership member to get a license key.
PTC Creo: Creo is a family or suite of Computer-aided design apps supporting product
design for discrete manufacturers and is developed by PTC. ptc.com/en/products/cad/creo
Fusion 360: A 3D CAD, CAM, and CAE tool that connects your entire product development
process in a single cloud-based platform that works on both Mac and PC.
autodesk.com/products/fusion-360/overview
OnShape: Onshape is a computer-aided design software system, delivered over the Internet
via a Software as a Service model. onshape.com
22
Prusa 3D YouTube: youtube.com/channel/UCLHAxAdvAKJY0niRJZRYMvg
The Holy Cows 2015 Brand Standards: Take inspiration from this document to create a
Mythic 9459 Brand Standards handbook.
team1538.com/site/assets/resource/2015BrandStandards.pdf
FTCHost: FTCHost's goal is to help FTC teams host their websites and domains for a low
cost. We are or have been on a team too, and we know that funding can be complicated
and hard to get. That is the reason we are creating FTCHost. Our servers are fast and have
the ability to scale to any need. SSL, weekly backups, and all other security measures are
provided for no extra cost. ftchost.org
Elementor: Elementor is the best WordPress Page Builder. Create beautiful websites using a
simple, intuitive drag and drop Interface. elementor.com
23
easy to use, offering developers the simplest path to getting their apps to market.
heroku.com/home
Wix: wix.com Ltd. is an Israeli cloud-based web development platform. The Mythic website
address is currently 9459mythic.xyz
Facebook: facebook.com is an American online social media and social networking service
company based in Menlo Park, California. Our current Mythic webpage is facebook.com/
mythica.grs.9
Twitter: Twitter is an online news and social networking service on which users post and
interact with messages known as "tweets". We currently do not have a Mythic twitter
account. twitter.com
Photos Archive: We use a Google Drive system to catalog our photos. If you have photos
to add, please email us the photos. The SMaD team has access to organize and edit the
archive. tinyurl.com/grsftcphotos
FUNDRAISING
Grants: There are many companies and foundations that offer grants for FTC teams.
FIRST: firstinspires.org/robotics/ftc/grants
24
High Tech Kids: hightechkids.org/programs/grants-and-scholarships/
25
STUDENT CONTRACT
By signing below I acknowledge and understand all points listed below:
I have read the Master Plan describing Robotics Team 9459 Mythic and agree to comply
with the policies outlined within.
Participation in the program requires attendance at meetings and I have received a tentative
schedule of those meetings.
The equipment used during construction of the robot can cause serious harm and injury if
used incorrectly. Students are not permitted to use any piece of equipment until they have
been instructed on its safe use and are not permitted to use any piece of power equipment
without adult supervision.
I understand that violation of any of the policies above is punishable by the leadership team
up to and including dismissal from the team.
26