Skip to content

Student Handbook

Student Contract

You can find the student contract here

About the Handbook

This handbook is intended to contain the information needed for all Team 2204 (Rambots) members to understand the administrative and logistical procedures for participating in the FIRST Robotics Competition. It is updated yearly by the Core Leadership team to accurately represent current standards and guidelines for the team.

Introduction to FIRST

FIRST Logo

FIRST is a non-profit organization founded in 1989 by inventor Dean Kamen. It aims to inspire young people to pursue careers in science, technology, engineering, and mathematics (STEM) through exciting and challenging robotics competitions. FIRST offers programs for students for all ages, promoting critical thinking, problem-solving, and teamwork. Its focus on hands-on learning and real-world problem-solving has made it a global phenomenon, with teams from all over the world participating in its competitions.

Participating in FIRST programs not only benefits students in the short term by developing their STEM skills and teamwork abilities, but also in the long term by providing access to a vast network of professionals and potential career opportunities. FIRST alumni have gone on to pursue successful careers in a variety of fields, including engineering, business, and medicine, and many credit FIRST for helping them achieve their goals. The focus on hands-on learning, problem-solving, and teamwork has helped students develop valuable skills that are in high demand in today's job market. Moreover, the FIRST community provides a valuable network of mentors, industry professionals, and peers who offer guidance, support, and inspiration to students as they navigate their future careers.

Introduction to the FIRST Robotics Competition (FRC)

The FIRST Robotics Competition (FRC) is an exciting program that challenges high school students to design, build, and program robots to compete in a game that changes every year. Founded in 1992, FRC combines the excitement of a varsity sport with the rigor of science and technology, promoting critical thinking, problem-solving, and teamwork.

Each year, FRC releases a new game that requires teams to build a robot that can perform specific tasks. Teams have six weeks to design, build, and program their robot before competing in regional events. The competitions are held in arenas where teams compete head-to-head to complete the game's objectives.

Through participation in FRC, students develop essential life skills such as leadership, communication, and problem-solving, which can benefit them both academically and professionally. FRC provides a unique and exciting opportunity for students to apply their knowledge in a real-world setting and develop valuable skills that will serve them well in the future.

Learn more about the FIRST and their other programs at firstinspires.org

About the Team

The Rambots, Team 2204 are a FIRST (For Inspiration and Recognition of Science and Technology) Robotics team located at the California Crosspoint Academy in Hayward, CA in the San Francisco Bay Area. They were established in 2007 in San Leandro, California. Since then, the school has moved to Hayward and provides students with a chance to pursue their interests in science, technology, engineering, and mathematics. The team is proud of its history and eager to contribute to the advancement of STEAM (science, technology, engineering, art, and mathematics) education.

Awards

  • 2023 Creativity Award for our flexible 3D Printed Robot Claw
  • 2020 Woodie Flowers Mentor Award for our mentor, Gary Gin

Mentors

Our team's mentors are industry professionals, teachers, parents, and community members who bring a wealth of knowledge and experience to our program. They work alongside students to teach, guide, and lead them throughout the season. With their technical expertise and real-world experience, our mentors help students develop their skills and achieve their goals. They are integral to the success of our team, providing valuable insight and guidance that helps us succeed both on and off the competition field.

Gary Gin is the most experienced mentor on our team, having been with us from when the team started. He is highly skilled in various areas, including mechanical engineering, design, and electrical systems. Gary has also been a competitor on the popular television show, BattleBots.

Earl Chen is our robotics team’s staff sponsor. He guides us in logistics, trip planning, finances, and well as offering advice to our build team. Thanks to his mentorship, our team is able to stay organized and on track.

Jason Hom has been a mentor and friend to our school since nearly the beginning of our team’s journey. Drawing from his industry experience, Mr. Hom assists with programming, fabrication, and design. Additionally, he provides valuable management insights to our business and leadership teams. His contributions have been instrumental in shaping our team’s growth and development.

Melissa Fong provides her mentorship and guidance the business and logistical aspects of our team. As a former student and now an alumni of our team, she also excels in guiding our leadership team, steering them with clarity and purpose.

Rodney Lim is a highly experienced mentor with expertise in electrical and electronics, as well as computer science. He has been with our team for five years and brings 44 years of industry experience.

Sam Cao has been mentoring our robotics team for three years, providing guidance in engineering problem solving, project management, CAD, rapid prototyping, and 3D printing. As a former student of our program, he has shared his experience and knowledge with our students, and has been a positive role model, demonstrating the principles of FIRST through Gracious Professionalism.

Teams Structure and Roles

Student Leadership

The core leadership team comprises the team captain, and subteam leads. For this year, that would be build lead, EECS lead, and business lead.

The captain of the team will be chosen from the previous year’s core leadership.

Team Captain: James Ding

  • Team captain serves as primary point of contact and liaison between team and others
  • Responsibilities include leading team meetings and facilitating decision-making processes
  • Works closely with other team leaders to coordinate and oversee team activities
  • Activities include CAD/programming work and project management
  • Leadership and communication skills of team captain are essential
  • Ensures team operates effectively and efficiently throughout the season

Build Lead: Ethan Wu

  • Lead design and prototyping, making critical decisions on robot's form and function.
  • Coordinate daily work of build team, ensuring timely completion of high-quality tasks.
  • Collaborate with programming team to integrate software and hardware components.

EECS Lead: Bryan Yu

  • Coordinate the team's electrical, electronics, and computer science work.
  • Work closely with the programming team to integrate software and hardware components.
  • Ensure that the team's electrical and electronics work is safe, reliable, and meets competition requirements.

Business Lead: Brian Ding and Aiden Lee

  • Manage team's finances, including accounting, purchasing, and record-keeping.
  • Plan and coordinate team events, including travel arrangements and logistics.
  • Establish and maintain relationships with sponsors, school officials, volunteers, and mentors
How are students selected for leadership positions?

After the season ends, all students are given the opportunity to apply for leadership positions. The application process to become apart of core leadership will often require you to submit an written statement of why you are fit for the position. Other leadership positions do not require a written statement, but are encouraged to do so. The current core leadership team will review the applications and select the the new core leadership team.

Next, the new core leadership team will choose the subteam leads from the previous year's subteam members.

Subteams

Design & Fabrication

The fabrication team utilizes part drawings and industrial machinery like mills, lathes, and routers to manufacture parts required for the robot.

Electrical

The electrical team is responsible for wiring the robot and installing any required pneumatic systems. They are tasked with ensuring that the mechanical systems, which were designed and built by the mechanical team, can be controlled effectively.

Programming

The programming team develops software in Java/Kotlin to control the robot's functions by integrating data from sensors such as encoders, limit switches, and vision systems. Their code ensures the robot performs effectively and safely in autonomous and teleoperated modes.

Business

The business team plays a critical role in managing the financial and public relations aspects of the project. They are responsible for budgeting, fundraising, and securing sponsorships to support the team's activities. They also handle social media and audiovisual tasks, as well as maintaining relationships to ensure the team’s success.

Expectations

Attendance Policy

Attendance is taken at every team meeting by each subteam lead. You are required to notify team leadership about late arrivals and absences. You should contact your subteam lead by email, Discord, or Teams as soon as possible, preferably at least 24 hours in advance. Longer absences should be communicated earlier. These are the following criteria for attendance:

  • Present
    • Being physically present is not enough—students must be attentive and productive during meeting time to be marked "present." Present markings will count positively towards your attendance percentage.
  • Absent Notified & Partial Notified
    • If you know ahead of time that you will miss a meeting, your subteam lead should be informed at least 24 hours prior to the meeting. If you do so, your absence will be marked as “notified” and you will have the ability to make up for your absence. All notified absences are still counted negatively towards your attendance percentage.
  • Absent Made Up & Partial Made Up
    • For notified absences ONLY, you have the ability to make up any work from the meeting, including homework and self-studying any material covered during training. If this action is taken, the absence will be counted positively towards your attendance percentage. It is YOUR responsibility to proactively ask the subteam lead for work to make up.
  • Absent Unnotified & Partial Unnotified
    • Unnotified absences cannot be made up and will count negatively towards your attendance percentage.
  • Unproductive
    • If you are not sufficiently productive or are distracting others during a meeting, the subteam lead may mark you “unproductive.” You will be given warnings when you are marked unproductive so you know what behavior was at fault and should not be repeated. Being marked “unproductive” will count negatively towards your attendance percentage and cannot be made up.

Attendance Evaluations

Members must be able to attend 70% of all meetings. To track your attendance, use the rambot Discord bot on our Discord server.

Regular attendance is essential for achieving success in any team or educational setting. It enables team members to stay informed, collaborate effectively, track progress, and allocate tasks efficiently. Moreover, attendance demonstrates a commitment to the team and its objectives, which helps build trust, respect, and team cohesion.

Monthly Member Evaluations

At the end of each month, the team roster will undergo a re-evaluation to ensure that only committed members remain on the team. Typically, students with an attendance rate below 75% will be subject to review. Those who fall below this threshold in the current month will be warned by a member of leadership, usually their subteam lead.

Apart from attendance, dismissal from the team may also be influenced by other factors. Reasons for dismissal may include, but is not limited to factors like behavior during team meetings, level of initiative, work ethic, and overall contribution to the team environment.

Subteam leads will engage with students who are not meeting the necessary requirements to stay on the team or are exhibiting behavior that puts them at risk of being dismissed. If it is determined that a student should be removed from the team, they and their parents will be informed.

Mental Health Days

We recognize that balancing the robotics season with school, family, and other responsibilities can become stressful and wear on a student’s mental and physical health. The health of a student is always our first priority, and thus we offer members the option of Mental Health Days. When needed, every student may make use of a Mental Health Day, where they can choose to either arrive late to a meeting, leave early, or not attend. There is no defined reason to use a Mental Health Day—mounting stress, family responsibilities, and other events are all equally valid. Unless your use of mental health days become excessive, there will be no questions asked. In the case of excessive usage, the subteam lead will speak with you about their circumstances and the best way for you to proceed. You must notify your subteam lead in advance when possible and the absence will be excused

Student Conduct

As members of our FIRST Robotics team, we uphold a high standard of behavior and conduct. We believe that a positive team atmosphere is essential for achieving our goals and fostering personal growth. All team members are expected to:

  • Respect Others: Treat teammates, mentors, volunteers, and competitors with respect and kindness. Differences in opinions and backgrounds should be celebrated.
  • Teamwork: Collaborate effectively and communicate openly. Share ideas, listen actively, and contribute positively to team discussions and projects.
  • Positive Attitude: Maintain a positive attitude, even in challenging situations. Encourage and support fellow team members to create a motivating and uplifting environment.
  • Safety First: Prioritize safety at all times. Follow safety guidelines and report any unsafe conditions immediately to mentors or team leaders.
  • Punctuality: Be punctual for team meetings, practices, and events. Respect your peers' time and commitment.

Gracious Professionalism

We embrace the concept of Gracious Professionalism – a FIRST core value that combines respect and cooperation. We strive to compete fiercely while maintaining empathy and respect for others. This means:

  • Helping Others: Offer assistance to other teams when possible. Share knowledge, tools, and resources to help everyone succeed.
  • Positive Competition: Compete to the best of your ability while respecting opponents. Win with humility and lose with grace.
  • Building Connections: Foster a sense of community within the larger FIRST Robotics family. Network and build relationships with teams from different backgrounds and regions.

Workspace Rules

To ensure a safe and productive environment, adhere to these workspace rules:

  • Safety Gear: Wear appropriate safety gear, such as safety glasses, closed-toe shoes, and any other protective equipment when working in the workshop.
  • Cleanliness: Keep the workspace organized and clean. Return tools and materials to their designated places after use.
  • Supervision: A adult mentor is required to supervise you in the workshop. Follow mentor guidance when using tools and equipment you're not familiar with.

Dress Code

When representing the team at events, presentations, and meetings:

  • Team Attire: Wear the official team attire, such as team shirts or uniforms, during competitions and outreach events.
  • Appropriateness: Dress in a manner that reflects positively on the team and its values.
  • Safety: Make sure your clothing is safe and does not cause any potential safety hazards. Talk to a member of the safety team for questions.
  • Hair: If using equipment, make sure to tie up long hair to ensure it does not interfere with the equipment or cause any safety hazards

Accountability

We hold ourselves accountable for our actions and commitments:

  • Commitment: Honor your commitments to the team. Be responsible for completing tasks and meeting deadlines.
  • Communication: If you're facing challenges that affect your involvement, communicate openly with mentors and team leaders to find solutions.
  • Quality Work: Strive for excellence in all team endeavors. Take pride in your contributions and ensure they meet the team's standards.

Reprecussions

Failure to adhere to the team's conduct and rules may result in consequences, which could include:

  • Verbal Warning: A mentor or team leader will discuss the issue with you and provide guidance on resolving it.
  • Probation: You might be placed on probation, during which your actions and behavior will be closely monitored.
  • Loss of Privileges: If the behavior continues, you might lose certain privileges, such as attending events or using the workshop.
  • Dismissal: In extreme cases, repeated or severe violations of conduct may lead to your removal from the team.

It is our belief that by following these guidelines, we can create a respectful, collaborative, and successful team environment that will benefit everyone involved.

Costs

The cost to join the team is $300, which covers the cost of team registration, materials, tools, and other expenses. Costs for trips to competitions are not included. However, we do not want the fee to be a barrier to entry, so we offer financial assistance to waive the fee for students who need it. If you need financial aid, please reach out to one of the mentors.

Parent Support

Donations

Approximately 25% of our team's income comes from parent donations, which help ensure that we can operate at our full potential. While donations are not mandatory, we greatly appreciate any support that we receive. Our team relies on the generosity of our community to provide valuable opportunities for our students in the areas of science, technology, engineering, and mathematics (STEM).

Volunteers

It's important to note that not all parents may be in a position to make monetary donations. However, there are other ways that parents can support the team. Parents play a significant role in supporting their children's involvement in this team.

Food

Parents are kindly requested to sign up for providing meals on either Wednesday dinner or Saturday lunch for the team. In cases where they are unable to bring food in person, alternative arrangements can be made by utilizing food delivery services such as DoorDash, Uber Eats, Postmates, and others. Your participation is greatly appreciated in ensuring the team's nourishment during these meals.

Events

During the competitions, parents can help facilitate students at the competitions.

Meetings Schedule

You can find the meeting schedule at rambots.org/schedule

Major Events

Chezy Champs

The Chezy Champs is an off season event hosted by Team 254: The Cheezy Poofs. It is held at Bellarmine College Preparatory School in San Jose, California.

Kickoff

Kickoff this year is on January 6, 2023

San Francisco Regional (CASF)

The San Francisco Regional is hosted at Saint Ignatius College Preparatory School. The event is held on March 16 to March 19. Our team has never been to the San Francisco Regional

Sacramento Regional (CADA)

The Sacramento Regional is hosted at the UC Davis Arc Pavilion. It is held on March 23 and goes to March 26. Our team has always gone to the Sacramento Regional and is considered a tradition.

Silicon Valley Regional (CASJ)

The Silicon Valley Regional is hosted at the event center at San Jose State University. The event is held on April 5-8. We have never competed at the Silicon Valley Regional.

Houston Championships

The Houston Championships is where the world championships are held. Our team has never competed in the world championships.

Credits

This handbook was inspired by Citrus Circuit’s handbook.

Contact Points

You may contact any of the student leadership team or mentors for any questions or concerns.

Visit our contact page for more information.