LogoLogo
  • Welcome!
  • Mission Statement
  • Contributing Guidelines
    • Embed CADs in Wiki Articles
  • VEX Worlds Livestream Archive
    • VEX U
    • V5RC High School
    • V5RC Middle School
    • VIQRC Middle School
    • VIQRC Elementary School
    • JROTC
  • ⚙️Hardware
    • Design Fundamentals
      • Gear Ratios
      • Internal Forces (Stress)
      • Torque
      • RPM
      • Center of Mass
    • Introduction to VEX Parts
      • Structure
        • C-Channels and Angles
        • Fasteners
        • Retainers
        • Gussets and Brackets
        • Bearings
        • Plate Metal and Flat Bars
      • Motion
        • High Strength Components
        • Gears and Sprockets
        • Traction Wheels
        • Mecanum Wheels
        • Omnidirectional Wheels
        • Flex Wheels
    • Robot Decorations
      • Part Dyeing
      • Metal Coloring
      • License Plate Holders
    • Lifts
      • Double Reverse Four Bar (DR4B or RD4B)
      • Four Bar
      • Scissor Lift
      • Six Bar
      • Other Lifts
      • Best Practices
    • Shooting Mechanisms
      • Catapult
      • Flywheel
      • Linear Puncher
    • Drivetrains
      • Tank Drive
      • Mecanum Drive
      • Holonomic Drive
      • Designing a Drivetrain
      • Best Practices
    • Pivots & Joints
    • Pneumatics
      • Best Practices - Pneumatics
    • Intakes
    • Flip Out Mechanisms
    • Defensive Mechanisms
    • Misc. Building Techniques
    • VexU
      • Common Manufacturing Techniques
        • 3D Printing
        • Laser Cutting
      • Custom Manufactured Parts Library
      • Commercial Off The Shelf Parts Library
  • 👑Team Administration
    • New Team Resources
      • Creating The Team
      • Gaining Interest for Robotics Teams
      • Attending Competitions
        • Elimination Bracket
    • Team Dynamics
      • Organization Structure and Longevity
      • Member Allocation and Management
      • How *Not* To Run a Team
    • Team Finances
      • One-Year Team Financial Breakdown
      • Funding Your Teams
    • Hosting Competitions
      • Live Streaming
      • Tournament Manager
        • Competition Electronics
        • Creating a Tournament
        • Tools
          • Field Set Control
          • Connecting Mobile Devices
          • Connecting Raspberry Pis
        • Match Control
          • Inputting Match Scores
          • Inputting Skills Scores
          • Inputting Scores on TM Mobile
        • Displays
        • Alliance Selection
      • Additional Event Partner Resources
    • VexU Organization Management
      • Getting Started in VexU
      • Team / Personnel Management
      • Volunteering At Local Events
  • 📚The Judging Process
    • The Engineering Design Process
      • Test and Refine
    • The Engineering Notebook
      • Segments of the Notebook
      • BLRS2 '23-'24 Engineering Notebook
      • Integrating Inventor Models into Documentation
      • Engineering Notebook Rubric Breakdown
    • The Interview
      • Interview Rubric Breakdown
    • Using Notion for an Engineering Notebook
      • How to Setup a Notebook
      • How to Create Entries
      • How to Export a Notebook
      • Purdue SIGBots Notion Template
        • Game Analysis
        • Identify The Problem
        • Brainstorm Solution
        • Select Best Approach & Plan
        • Build Log
        • Programming Log
        • Testing Solution
        • Tournament Recap
        • Innovative Feature
  • 🖥️VEX CAD
    • CAD Programs
      • Inventor
      • Fusion 360
      • Solidworks
      • OnShape
      • Protobot
    • Making a Chassis
      • Inventor Chassis: The Basics
        • Installation
        • User Interface Overview
        • Dark Mode
        • Assemblies
        • Placing Parts
        • Navigating CAD
        • Changing Visual Style
        • Grounding
        • Connecting Two C-Channels
        • Modifying Existing Constraints
        • Toggling Visibility on Existing Parts
        • Completing Half of the Chassis
          • Inner Drive Channel
          • Bearing Flats
          • Motors
          • Wheels
          • Sprockets
          • Spacers, Washers and Standoffs
          • Spacers Cont.
        • Creating Mid-Plane
        • Mirroring
      • Inventor Chassis: Best Practices
        • File Structure
        • Subassemblies
        • Wheel Subassembly
        • Origin Planes
        • Cross Brace
        • Drive Channels
        • Simple Motor iMates
        • Replacing Simple Electronics
        • Completing Half of the Drive
          • Bearing Flats (Best Practice)
          • Wheels
          • Powered Gear
          • Spacer Boxing
          • Spacers, Washers and Standoffs (Best Practice)
        • Model Browser Folders
        • Mirroring (Best Practice)
        • Model Browser Folder (Right)
        • Main Assembly
      • Fusion 360 Chassis
      • Solidworks Chassis, Chain, and Custom Plastic
    • Remembering The Best
      • 62A Skyrise
      • 400X Nothing But Net
      • 2587Z Nothing But Net
      • 365X Starstruck
      • 62A In The Zone
      • 202Z In The Zone
      • 5225A In The Zone
      • 169A Turning Point
      • 929U Turning Point
      • 7K Tower Takeover
      • 5225A Tower Takeover
      • 62A Change Up
    • Scuff Controller
  • 💻Software
    • Odometry
    • Path Planning
    • Robotics Basics
      • Arcade Drive
      • Tank Drive
      • Joystick Deadzones
      • Curvature (Cheesy) Drive
      • Subsystem Toggling
    • Organizing Code
      • Code Style
      • Code Styling Guide
      • Writing Good Comments
      • Version Control
    • Control Algorithms
      • Bang Bang
      • PID Controller
      • Basic Pure Pursuit
      • Flywheel Velocity Control
      • Kalman Filter
      • Take Back Half (TBH) Controller
      • RAMSETE Controller
    • Competition Specific
      • Operator Control
      • Autonomous Control
    • C++ Basics for VEX Robotics
      • Basic Control Flow
      • Enumerations
      • Namespaces (::)
      • Multiple Files (C/C++)
    • VEX Programming Software
      • PROS
        • OkapiLib
      • vexide
      • Robot Mesh Studio (RMS)
      • EasyC
      • RobotC
      • VEXcode
      • Midnight C
    • General
      • Stall Detection
      • Register Programming
      • Sensors and Odometry in Autonomous
      • Embedded Programming Tips
      • Debugging
      • Bit Shift
      • Bit Mask
      • Autoformatting
      • Finite State Machine
      • Data Logging
    • Object Recognition
      • Red Green Buoy
      • AMS
      • OpenCV
      • OpenNI
    • 🤖AI in VRC: Pac-Man Pete
  • ⚡VEX Electronics
    • V5 ESD Protection Board
    • VEX Electronics
      • VEX V5 Brain
        • V5 Electronics Observations and Issues
      • VEX Controller
      • VEXnet and V5 Robot Radio
      • VEX Battery
      • VEX Motors
    • VEX Sensors
      • 3-Pin / ADI Sensors
        • Encoder
        • Potentiometer
        • Limit Switch
        • Bumper Switch
        • Accelerometer
        • Gyroscope
        • Ultrasonic
        • Line Tracker
        • LED Indicator
      • Smart Port Sensors
        • GPS Sensor
        • Rotation Sensor
        • Vision Sensor
        • Optical Sensor
        • Distance Sensor
        • Inertial Sensor (IMU)
        • 3-Wire Expander
    • V5 Brain Wiring Guide
    • Legacy
      • VEX Cortex
      • Power Expander
      • VEX Motor Controller
      • VEX Cortex Wiring Guide
  • General Electronics
    • General Topics
      • External Boards
        • ASUS Tinker Board S
        • Arduino
        • Beagleboard
        • Leaflabs Maple
        • LattePanda
        • Meadow F7 Micro
        • Netduino
        • ODROID-XU4
        • Pandaboard
        • Raspberry Pi
      • Analog-Digital Converter (ADC)
      • Bit-Bang
      • GPIO
      • I2C
      • Jitter
      • Line Noise
      • List of Tools
      • Output Drive
      • Power Consumption
      • Radius Array
      • Resettable Fuse (PTC)
      • SPI
      • Slew Rate
      • Stalling
      • USART
      • UART
      • 5 Volt Tolerant
      • DC Motor Basics
Powered by GitBook
LogoLogo

This work is licensed under a Attribution-ShareAlike 2.0 Generic License

On this page
  • Engineering Notebooks
  • In-House Resources
  • Interaction Between Teams
  • Teams Contributed to this Article:

Was this helpful?

Edit on GitHub
Export as PDF
  1. Team Administration
  2. Team Dynamics

Organization Structure and Longevity

PreviousTeam DynamicsNextMember Allocation and Management

Last updated 5 months ago

Was this helpful?

A successful robotics club is an investment that will teach members various important skills in engineering, as well as in many other fields. In addition to teams learning from external resources, being able to learn from other teams and members within the organization is a system that can help your organization successfully teach new members through generations of teams.

Engineering Notebooks

Not only do engineering notebooks provide documentation of your robot and design process for judges at competitions, they also serve as knowledge bases for future teams in your organization. Well-thought-out and thorough notebooks can serve as a database for building techniques, game strategies, and programming solutions for other teams in your organization long after you've graduated. On top of the content within the notebook, the notebook itself can act as an example of how to layout and format a notebook, to continue the cycle.

In-House Resources

The best In-House resource for a club's longevity is passionate students who will share everything they learned with new students. This is often fostered by working together across sister teams. Sharing design ideas throughout a season, asking for help, and giving help, as well as game strategies and more.

Another good way to develop resources is a shared drive folder (on a preferred platform). Teams take hundreds of photos and videos throughout a season. Compiling these will allow for new students to get a boot camp of what the process will look like. This is a great spot as well to compile build techniques or interesting mechanisms that have been developed in the club. Haverford (169) has employed this in the past where teams will compile their photos towards the end of the season to the drive and will share everything they have learned.

Code libraries are very helpful in organizations to assist in the start-up process for a new team, or new students. Commonly, this is done on Github. Compile all code that is created throughout the year, and in past seasons. BLRS has a GitHub with past seasons of code as well as PID, Odometry, and Pure Pursuit libraries (some of which are private for team use only right now).

Past robot libraries, displays, and notebook libraries are also helpful. Similar to the shared drive mentioned earlier, this is a great way to document designs, mechanisms, and build techniques. The easiest way to teach robotics is to show someone a past robot. If it is possible, displaying some past robots (ones that have done well for example) in the club meeting space helps to show a team close up how robots work. Some teams like have CAD models of their past robots as well. And notebook libraries can just be a shelf in a meeting space that show past notebooks that people can look through as needed.

At Purdue, the BLRS Wiki is in itself a form of an In-House Resource. Team members are asked to document knowledge that they have gained from VEX. This covers so much from organization creation, to build techniques. For BLRS, it is all published; however, this is not required. Resources like this are a great way to document learnings across an organization.

Interaction Between Teams

Mentorship between the more experienced teams in an organization and the less experienced teams is one of the most effective ways to ensure the long-term competitiveness of the club. If all of the knowledge on how to be a successful team rests in a single team in the organization, the organization will struggle when that team graduates. However, even after graduation, there are still plenty of opportunities for graduated members to continue to help their VRC organization. Staying in contact with teams using communication platforms such as group chats and Discord are great ways to continually receive build advice and programming help while alumni aren't able to help in person.

To take mentorship to the next level as a VRC team, working alongside other teams in your organization can help develop multiple competitive teams at the same time. This has many benefits, such as mutual improvement of each team, better drive practice (viable 1v1's and practice matches), and the ability to coordinate alliance selections. Many top-tier organizations have employed this strategy throughout many seasons with great success, such as and .

Another great thing to look into is communication with other teams across regions and the world. The for example has thousands of teams communicating daily and is a great place to ask questions and share knowledge. Similarly, YouTube has hundreds of VRC-related videos from reveals to tutorials. Many regions also have Discord servers. Talk to teams in different regions though to find out if there is a local Discord Server. With parent permission, these are a great way to get involved in the VEX community. The largest server is (formerly VEX Teams of the World AKA VTOW). This is an unofficial discord not affiliated with VEX which has teams from around the world.

Teams Contributed to this Article:

  • (Purdue SIGBots)

👑
here
SJTU
169
8059
VEX forum
VEX Robotics Competition
BLRS