Lord of the Bricks FTC Team Handbook

Home / Activities and Awards / Lord of the Bricks Robotics Teams / Lord of the Bricks FTC Team Handbook

 

Purpose

This handbook is an informational guide book for the conduct of the Lord of the Bricks Robotics Team members.  All team members and their parents are expected to review this manual, and understand it.

Lord of the Bricks Robotics supports three levels of FIRST Robotics, resulting in a comprehensive Robotics program:

  • For six to nine-year-olds, we provide support for Junior FIRST Lego League (Jr. FLL). FLL is a hands-on program designed to capture young children’s inherent curiosity and direct it toward discovering the possibilities of improving the world around them.  This program features a real-world challenge, to be solved by research, critical thinking and imagination. Guided by adult coaches and the Jr.FLL Core Values, students work with LEGO elements and moving parts to build ideas and concepts and present them for review.

Team Members get to:

Design and build challenge solutions using LEGO elements
Apply real-world math and science concept
Research challenges facing today’s scientists
Learn team building and presentation skills
Develop Show Me poster

  • For nine to 14-yr-old, we offer FIRST Lego League (FLL). FLL Introduces younger students to real-world engineering challenges by building LEGO-based robots to complete tasks on a thematic playing surface. FLL teams, guided by their imaginations and adult coaches, discover exciting career possibilities and, through the process, learn to make positive contributions to society.

Elementary and middle-school students get to:

Design, build, test and program robots using LEGO MINDSTORMS® technology
Apply real-world math and science concepts
Research challenges facing today’s scientists
Learn critical thinking, team-building and presentation skills
Participate in tournaments and celebrations

What FLL teams accomplish is nothing short of amazing. It’s fun. It’s exciting. And the skills they learn will last a lifetime.

 

  • For middle- and high-schoolers, we participate in the FIRST Tech Challenge (FTC) annual competition. FTC is designed for students in grades 6-12 to compete head to head, using a sports model. Teams are responsible for designing, building, and programming their robots to compete in an alliance format against other teams. Teams, including coaches, mentors and volunteers, are required to develop strategy and build robots based on sound engineering principles. Awards are given for the competition as for well as for community outreach, design, and other real-world accomplishments.


Students get to:

Design, build, and program robots
Apply real-world math and science concepts
Develop problem-solving, organizational, and team-building skills
Compete and cooperate in alliances and tournaments
Earn a place in the World Championship
Qualify for millions of dollars in college scholarships

This handbook applies to the FTC middle/high school league.

Lord of the Bricks is not restricted to homeschoolers; so students in all schools and homeschools may participate.  All participating students, however, are subject to these rules of conduct, whether working with Lord of the Bricks, or at any event where the student represents the Lord of the Bricks Robotics team.

Goals

Our goal is to provide high school students with the opportunity to learn from mentors who have both technical and non-technical backgrounds, enabling them access to an unparalleled learning experience in all aspects of robot design, constructions, programming, and competition.  Through all our programs, we seek to instill FIRST’s ideal of Gracious Professionalism, which holds that even when in competition, every student will be courteous, and even help opponents to overcome technical issues and obstacles to competition.  This ideal includes participating in community outreach activities, helping to support other teams in our area, and “giving back” to our community.

To summarize, our goals are to:

  • Promote and maintain a safe working environment;
  • Challenge students and promote education in Science and Technology;
  • Promote Gracious Professionalism;
  • Provide the opportunity to build leadership and teamwork skills;
  • Use each student’s unique talents to their maximum effect;
  • Improve our community through outreach projects.

 

Team Organization

Lord of the Bricks Robotics is guided by volunteer mentors who have science and technology backgrounds, as well as non-technical mentors who help organize fundraising, pit decorations, and other important auxiliary functions.  In all cases, the purpose of the mentors is to teach, guide, make suggestions, and organize; but it is the students who design, build, program, and drive robots in competitions.

 

Safety

The responsibility of safety lies with each and every member of Lord of the Bricks Robotics.  Each team member is required to abide by safety rules at all times.

It should be understood that the student members of Lord of the Bricks are viewed by the mentors as young adults, acting much like employees of an organization.  It is important to maintain a positive image to our community, sponsors, and FIRST; and this begins with safety.  All Lord of the Bricks Robotics Team members must know and demonstrate safe and professional behavior wherever the Team conducts its business.

Important safety rules include (but are not limited to):

  • SAFETY GLASSES MUST BE WORN AT ALL TIMES DURING BUILD SESSIONS, EVEN BY STUDENTS WHO ARE NOT USING TOOLS. Clip on side guards are acceptable; regular glasses without side guards are NOT safety glasses.
  • No open-toe shoes, “Crocs,” etc. Shoes provide important protection in case of dropped tools or materials.
  • No loose fitting clothing dangling jewelry, or other items that present an entanglement hazard around equipment.
  • No “horsing around.” Work with tools and machines does not mix with practical joking or foolish behavior.
  • No personal electronics with earphones – you need to be able to hear warnings or instructions from the mentors and other students.
  • Always disable the robot’s “kill switch,” or remove the battery before undertaking repairs or modifications.
  • Use common sense; Be aware of what is going on around you.

tool usage

The use of power tools is a necessity for most members of the team.  Tools should always be used in a safe manner.  Only adequately trained members may use tools – no exceptions.  Always remember that tool usage is a privilege, and not a right; so use them responsibly.  Talking to a mentor before using a tool is required.  When using tools, a student is responsible to ensure everyone near them is wearing safety glasses, and is paying attention, that there is adequate space, an uncluttered work area, and other common sense precautions.  Team members must use tools in pairs; and prior to executing the tool maneuver, an adult must check that safety is observed.

Meeting Schedules

The schedule for robot team meetings is communicated via email by the coach/mentor.  Most meetings are 3 hours long; but near tournament time, build meetings may be longer than usual.  Students may bring homework with them for occupation during down times, when tasks may not be performed out of sequence.

Behavior

Lord of the Bricks treats each student member as a respected young adult.  Each student is expected to be respectful of all team members, mentors, and any other individuals with whom the team may come into contact.  Team members are expected to take direction from mentors and team leads, as needed. Gracious Professionalism is a must for all students.

Liability

Team members are responsible for their own behavior at all times, and are, thus, fully liable for any damages that occur as a result of their behavior.

Work product

All work created for and on behalf of Lord of the Bricks is owned by Lord of the Bricks, and shall not be removed from the team without prior consent.

Disciplinary actions

Violation of the Lord of the Bricks rules of conduct, safety violations, or other inappropriate activity may result in suspension or ejection from the Lord of the Bricks Robotics Team, at the discretion of the mentors.

Uniform for competition

Students will receive team shirts and gear, and are expected to wear them to all competitions, scrimmages, and outreach events.  Other aspects of dress for tournaments should be appropriate, neat, and modest, and should adhere to workshop rules (no open-toe shoes, no dangling jewelry, etc., as this is a safety issue in the pits).

Communication

It is important for both students and parents to be on the team’s communication registry to facilitate communication.  The mailing list is used to inform team members of build session schedules, competitions, scrimmages, and other important information.  Team member attendance statuses must also be registered on the communication registry so that mentors and team members can accommodate the scheduled activities. Emergency contact information should also be placed on the communication registry for easy access in the event of an emergency. The communication registry is located on TeamStuff.com; please set up an account if you have not already done so.

financial/fundraising

Each member if the team must pay an activity fee at the start of the season.  Lord of the Bricks offers participation scholarships as available from sponsorship funding; so please inquire if needed.  In addition, there may be nominal charges for participation in some tournaments and events.  Event travel shall be the responsibility of the team member’s family.  Team members are also expected to meet a sponsorship attainment goal of $1000 to offset the cost of each competition season.

Team members will, from time to time, be involved in fundraising activities.  This may include making presentations for potential sponsors, making phone calls, writing thank you letters to sponsors, or demonstrating robots to the community at large to generate interest.

Student involvement

Lord of the Bricks Robotics Team is a challenging activity.  There is a tremendous amount of information to learn, and many skills our team members must quickly acquire.  For this reason, significant commitment is required from our students.  Team members must strive to achieve real results at each meeting, and constantly explore ways to improve the robot and the team, itself, in a proactive manner.  Students will frequently not be told what to do; rather, they are expected to figure out what to do, themselves, perhaps with some guidance and teachings from the mentors.

Parent involvement

Lord of the Bricks Robotics Team values its parents as a support system for our team.  Parent support is crucial to the success of the Team, as the involvement of the team members relies heavily upon team parents.  Parents are encouraged to offer assistance, fill necessary Booster roles, provide team snacks, assist with fundraising and outreach, and offer mentorship opportunities in areas of expertise.  Team members, however, must take the lead

Publicity

Part of fundraising and community involvement is the placement of news articles in papers, on the internet, or in magazines from time to time.  Students may be interviewed by members of the press at events, and their words and likeness may be printed as a result.  FIRST requires a waiver signed by a parent or guardian giving permission for such press activity for each student.  This is a requirement to even set foot in the arena.  Lord of the Bricks may also release materials to the press that include photographs of the students involved with the team.  As such, Lord of the Bricks also requires a signed waiver from each team member.

Conclusion

Lord of the Bricks Robotics program offers a rich learning experience that is generally recognized by many colleges and universities.  Robotics requires a real commitment in time and energy from each student who participates; but the rewards, in terms of education, scholarship opportunity, national recognition, and the thrill of intense competition, will repay the students’ efforts many times over.


Fields marked with an * are required
Fields marked with an * are required