Team Goals - Melea

  • To uphold the FIRST Tech Challenge (FTC) Core Values and build the foundation for the next generation of engineers and scientists
    • We display Gracious Professionalism with everyone we engage with and in everything we do.
    • We act with integrity.
    • We have fun.
    • We are a welcoming community of students, Mentors, and Volunteers.
    • What we learn is more important than what we win.
    • We respect each other and celebrate our diversity.
    • Students and adults work together to find solutions to challenges.
    • We honor the spirit of friendly competition.
    • We behave with courtesy and compassion for others at all times.
    • We act as ambassadors for FIRST and FIRST Tech Challenge.
    • We inspire others to adopt these values.
  • Compete in the FTC World championship.

~Melea

Robot Design Leader – Wesley and Taylor

Goals
  • Responsible for overall design of the Robot.
  • Create a formal design process and build a robot based off of this process.
  • Create a subsystem envelope.
  • Create a a failure analysis process.
  • Work with team members and help them design their assembly.

Process:
  • Leads brainstorming sessions on possible ideas.
  • Ensure the robot is being built and tested safely and that the correct actions are taken to resolve any problems.
  • Test each sub-assembly thoroughly and discuss any failures and how to fix/prevent them from accruing again.
  • Approves all design changes to robot.


Wesley & Taylor

Software Leader - John Paul


Goals
  • Brainstorm and implement effective solutions to bring the robot to life
  • Communicate with drive team; tweak controls to fit their needs
  • Design multiple autonomous programs to be able to handle many situations
  • Keep one central updated program; others can do offshoots and elaborate, but changes must be finalized and added back to the main program
  • Design an autonomous playbook to be able to explain autonomous programs and communicate effectively to encourage coopertition.
  • Ensures program documented.
  • All changes to software are documented in the engineering notebook.
Process:
  • Assist team members with program designs.
  • Create a new backup of each week and send a copy to the coach. :

John Paul

Engineering Notebook Leader – Robert


Goals:
  • Create an Engineering notebook per the FTC handbook.
  • Ensure the proper notation and recording of all data created and collected within our team.
  • Keeping things orderly and timely

Process:
  • We have to keep the notebook on time. Entries need to happen before the next meeting so we don't forget what happened. Since we will be depending on the main whiteboard for our tasks list, we should be able to recall what happened every meeting with no problems. We have brought back the "you don't do anything else until you finish your posts" rule.
  • Entries look better when only a couple people make detailed posts rather than everyone making general posts without much information. We will be assigning topics for people to write up on rather than have an "everyone write something about this" every time.
  • Make sure everything is speeld correctly.
  • Ensures a team member takes several pictures each meeting. All pictures are saved to the team laptop. All pictures are routinely sent to the coach for backup.
  • Maintain the teams Wiki
    • Ensure a new Wiki page is started for each meeting.
    • Ensure each page has a task list, information about the task, how the team completed the task and reflection.
    • Ensure each team member enters information on the Wiki at each meeting.
Robert


Community Outreach Leader – Melea and Owen

Goals:
  • Do FTC demonstrations in at least 6 different events.
    • Look out for events that we can do demonstrations at.
    • Contact event coordinators in advance to see if they would allow us to do demonstrations at the events
    • Continue until at least 6 demonstrations have been scheduled. (Preferably closer to eight)
  • Mentor at least 6 existing FLL teams.
    • Contact (emails/letters followed up by phone calls if necessary) at least 7 existing FLL teams.
    • Continue on a monthly basis until at least 6 mentoring sessions have been scheduled.
  • Actively reach out to and mentor existing FTC teams.
    • Contact (emails/phone calls/whatever works for the other team) at least 20 existing FTCs team in MS at least once during the season.
    • Offer to schedule times where we can come to their workshop/school and help them. The goal is to meet with at least 15 teams before the season is over.
    • Inform other teams about our 80/20 Grant. Help interested teams manufacture their robot designs with 80/20.
  • Host an FLL qualifier to reach out to FLL teams in the area.
  • Host at least one FTC event to reach a large number of teams.
  • Reach out to school districts to introduce them to FTC and FIRST by inviting them to qualifiers and/or our shop.
  • Meet with at least half our sponsors to talk about their experience in the engineering world and show them our robot. Keep in touch with all sponsors through letters/emails.
  • Keep all social media up to date!
  • To have a handout for other teams and judges about the robot and community service.
  • A handout for community events about FTC in general
  • Create a Promote Video
  • Create a Compass Video
  • 80/20 - will find an effective method to distribute the 80/20 grant to Mississippi FTC Teams.
      • Decide on an efficient process to distribute 80/20 to teams
      • Evaluate grant forms to determine recipients of material
      • Successfully market/advertise 80/20 grants
      • Teach teams how to effectively use 80/20, and assist them with design
      • Supply 80/20 to around 6-12 Mississippi FTC teams
      • Document bill of materials, sketches, pictures and improvements that will be distributed to 80/20
      • Spread Gracious Professionalism, Coopertition, and friendly competition to promote learning and produce highly competitive Mississippi teams
Melea

Safety Officer - Joseph


Goals:
  • Ensure the safety of the team members and their but not limited to (arms, legs, head, shoulders, knees, and toes, and eyes and ears and mouth and nose and tail.) are intact and functioning without the aid of robotic appendages.
  • Ensure all participants wear safety glasses as required.
  • Setup a rotation and have one team member present a safety topic each meeting.
  • Setup a process for reporting unsafe acts.
Process:
  • Notify people of their safety topic the week before the next meeting.
  • Find safety pictures for each safety topic.
  • Assign a safety topic to the person to present at each meeting.
Joseph

Research/Scouting Leader – Joseph

Goals:
  • Create a team scouting sheet that the team can use at tournaments.
  • Research other teams designs and supply team with updates.
  • Research tournaments for any applicable information and update team.
  • Find several teams with blogs/online notebooks/etc. that are actively updated and check them at least every other week (we may monitor some closer than others depending on their performance/how often they update). Meet with and make the design team aware of potential changes that may be beneficial to robot performance weekly.
    • Start with the focus on teams from areas where we will be competing.
    • Next, check recent tournament results and research teams from there, focusing on teams who placed high in the rankings.
  • Research teams that have registered to be competing with us as soon as we are aware of it.
  • Make sure scouting sheets and scouts are prepared before each tournament.
  • Make sure scouting sheets are up to date.
    • Decide who will watch and fill out sheets on matches a few weeks before a tournament.
    • Ensure scouts know how to use scouting sheets properly.
    • Make sure that they have taken the scouting pledge.
Joseph

PTC Modeling Leader - Owen

Goals:
  • To complete a PTC model of the robot.
  • Ensure sketches of conceptual and actual designs are added to the Engineering notebook each week.
  • As new parts are added or created, they will be added to the Engineering notebook bill of materials and named within the models under the same name.
  • All new members are trained on PTC and contribute to the PTC modeling of the robot.
  • The PTC module will be fully articulated.
  • The model will not break any laws of physics.

Processes:
  • The PTC models will be adjusted the same day as the changes are made.
  • Ensure all parts created are copied to the team PC after each meeting and the files are backed-up weekly.
  • Members working on the PTC will consult with the design team to maintain accuracy.

Owen