| | 1 | Each year, the team engages in various activities and the students organize to ensure that one or more students assumes responsibility for each activity. These student roles may overlap and can vary with the time of season. For example, during the Fall/Training season, students must |
| | 2 | * Get students registered (collect forms, membership fees, etc.) |
| | 3 | * Train new students and mentors |
| | 4 | * Train returning students |
| | 5 | * Prepare for off-season activities |
| | 6 | * etc. |
| | 7 | |
| | 8 | == Fall/Training == |
| | 9 | |
| | 10 | * Recruiting (students, mentors, faculty) |
| | 11 | * RaiderTime (Spring) (students) |
| | 12 | * Back to School Night (students, mentors) |
| | 13 | * New Student Orientation (students, mentors) |
| | 14 | * Related [http://ahs.hcpss.org/clubs AHS clubs] and programs (women in engineering, PLTW, etc.) |
| | 15 | * Feeder middle-schools and community FTC teams (students) |
| | 16 | * Regular parent outreach (email, Facebook?) |
| | 17 | |
| | 18 | * Admin/Registrations |
| | 19 | * Take attendance each meeting |
| | 20 | * Collect AHS/HCPSS Release/Waiver, Emergency Contact forms |
| | 21 | * Register team with FIRST (work with Lead Mentor) |
| | 22 | * Work with IT/infrastructure lead to update tools access |
| | 23 | * FIRST Chesapeake registration (Roster) and online Consent and Release (Nov) |
| | 24 | |
| | 25 | * IT Infrastructure |
| | 26 | * Team website, facebook, twitter, etc. (not necessarily content) |
| | 27 | * Team Google account, drive, groups, |
| | 28 | * Maintain team cloud server (e.g. regular security updates) |
| | 29 | * Maintain team laptops (OS updates, software, hardware maintenance) |
| | 30 | * Update tools access: Canvas, Wiki, !TeamSnap, Slack, Google Drive, Git, (add new students, mentors, remove students no longer on team) |
| | 31 | * Update driver station software |
| | 32 | * Update firmware (radios, roboRIOs) |
| | 33 | |
| | 34 | * Off Season Competitions |
| | 35 | * Register team and pay for off season events (BoB, IROC) (work with Boosters/Faculty/Lead Mentors do this during the Summer) |
| | 36 | * Ask Boosters/Faculty Adviser to complete and submit [http://www.hcpss.org/f/aboutus/field-trip-packet-all-forms.pdf HCPSS Request for Student Field Trip form] |
| | 37 | * Reserve bus transportation (usually from Mellor's Bus Service for local events: 410-531-6033) |
| | 38 | * Inform students and mentors about dates, costs, rules, forms (September) |
| | 39 | * New students '''must''' and new mentors should attend at least one off season event |
| | 40 | * Students attending/participating in the field trip must ride the bus. |
| | 41 | * Students cannot drive themselves. |
| | 42 | * Students cannot ride with parents other than their own (or anyone else). |
| | 43 | * Students whose parents drive them are not on the field trip but are simply members of the public attending the event; parents must stay with the student for the entire competition (parent is fully responsible for student) and students cannot participate other than as member of the public (i.e. cannot work in pits, drive robot, represent the school, etc.) |
| | 44 | * Identify parent volunteers to chaperone (at least 1 per 20 students) (September) |
| | 45 | * Identify and make robot enhancements |
| | 46 | * Distribute, Nag, Collect, and Track [http://www.hcpss.org/f/aboutus/field-trip-packet-all-forms.pdf required HCPSS forms] from students (permission, release, health, emergency, etc.) (October) |
| | 47 | * Nag, Collect, and Track student fees (covers bus) (October) |
| | 48 | * Prepare checklists |
| | 49 | * Assemble and pack needed materials (work with quartermaster) |
| | 50 | * Reserve transportation for robot/driver station and pit/gear (e.g. rent a trailer, organize loading/unloading) |
| | 51 | * Train pit and safety leads |
| | 52 | * Brief students and mentors on the event (at meeting) |
| | 53 | * Ensure all materials returned to closet (work with quartermaster) |
| | 54 | * Charm school |
| | 55 | * Game/Strategy |
| | 56 | * Select, train students on scouting |
| | 57 | * Collect/crunch scouting data |
| | 58 | * Alliance selection/negotiation |
| | 59 | * Driver team |
| | 60 | * Pit/maintenance plan |
| | 61 | * Awards plan |
| | 62 | |
| | 63 | * Season Competitions |
| | 64 | * Select and register for 2 district events (the local events fill up quickly so Lead Mentor must do this as soon as registration opens) |
| | 65 | * Bethesda (Greater DC) at Walt Whitman HS |
| | 66 | * Edgewater (Central Maryland) at South River HS |
| | 67 | * Arrange buses (Mellor's or Dillon's depending on distance) |
| | 68 | * Arrange robot/pit transportation (rent trailer, organize loading/unloading) |
| | 69 | |
| | 70 | * Quartermaster |
| | 71 | * Closet/shed organization |
| | 72 | * Work with training lead(s) and Boosters to identify, budget, and purchase (through lead mentors) materials required for training and off-season competitions |
| | 73 | * Work with off-season competition lead(s) to prepare checklists and coordinate gathering/return of materials to/from off-season events |
| | 74 | * Work with outreach lead(s) to prepare checklists and coordinate gathering/return of materials for outreach events |
| | 75 | |
| | 76 | * Marketing |
| | 77 | * Outreach to existing sponsors |
| | 78 | * Outreach to parents/volunteers for company/individual sponsorship |
| | 79 | * Grant identification, applications |
| | 80 | * Outreach to new sponsors (local businesses, technology employers, etc.) |
| | 81 | * Prepare/update marketing materials (printed, video, web) |
| | 82 | * Sponsor logos on shirts, website, and robot |
| | 83 | * Press releases |
| | 84 | * Media outreach (e.g. local newspapers) |
| | 85 | * Graphic design |
| | 86 | * Videography |
| | 87 | * Social media updates |
| | 88 | * Website updates |
| | 89 | |
| | 90 | STEM outreach |
| | 91 | * Identify events (GirlPower, STEM Festival, Maple Lawn/Hackground, etc.) |
| | 92 | * Create events (e.g. outreach to feeder elementary and middle schools) |
| | 93 | * Organize and track volunteers (all students must and mentors should attend at least one event) |
| | 94 | * Materials development by age level (paper, programs, robots, etc.) |
| | 95 | |
| | 96 | * Team building |
| | 97 | * Big brothers/sisters for new students and mentors |
| | 98 | * Team-building events (laser tag, picnics, etc.) |
| | 99 | * Technology outings (ask parents/mentors to facilitate: NASA, Tech museum, industry events) |
| | 100 | * Yearbook? |
| | 101 | * Year end banquet |
| | 102 | |
| | 103 | * Awards |
| | 104 | * |
| | 105 | |
| | 106 | * Training |
| | 107 | * New Student/Mentor training (overview all topics) |
| | 108 | * Shop safety |
| | 109 | * Ongoing development and enhancement of training materials |
| | 110 | * Fabrication |
| | 111 | * Hand Tools, Fasteners, Adhesives, Materials |
| | 112 | * Power Tools, Polycarbonate Shaping |
| | 113 | * Physics: Torques, Moments, Strength/Forces, etc. |
| | 114 | * Actuators: DC motors, Servos, Solenoids, pneumatics |
| | 115 | * Transmissions: Gears, Chains, Belts, Shafts |
| | 116 | * Drive Systems: Wheels, Mecanum, Omni, Tank, Suspension, Differential |
| | 117 | * Advanced mechanisms: Shooters, Climbers, Manipulators, Precision Control |
| | 118 | * Design Automation: CAD/Solid Modeling,, CNC, 3D Printing |
| | 119 | * Sources: McMaster-Carr, Andymark, Vex, etc. |
| | 120 | * Control Systems Trainers |
| | 121 | * Programming, Java Basics |
| | 122 | * Electricity and Electronics |
| | 123 | * Electrical Safety and Rules |
| | 124 | * Power: Batteries, breakers, PDP, Fuses, VRs, wiring |
| | 125 | * Controllers: roboRIO, Raspberry Pi |
| | 126 | * Actuator control: DC motor control, Servo control, Relays, pneumatics |
| | 127 | * Sensors: switches, encoders, range finders, position/motion sensors |
| | 128 | * Driver Station: configuration, settings, cameras, targeting, testing, debug output, logging |
| | 129 | * WPILib |
| | 130 | * Advanced control: PID/control loops, smart motor controllers |
| | 131 | * Autonomous: vision systems, path navigation |
| | 132 | * Game/Strategy: BoB, IRoC |
| | 133 | * Driver Training |
| | 134 | * New driver identification (all students should try driving) |
| | 135 | * New driver training |
| | 136 | * Work with control systems on control enhancements |
| | 137 | * Scouting tool training |
| | 138 | * Planning/scheduling tool training |
| | 139 | * Test/Validation techniques |
| | 140 | * Create proforma schedule for season - fill in details after kickoff |
| | 141 | * Train students/mentors on and prepare communication tools |
| | 142 | |
| | 143 | == Kickoff == |
| | 144 | * Study other team’s successful processes (e.g. Chief Delphi) |
| | 145 | * Plan Kickoff |
| | 146 | * location (e.g. cafeteria) and backup location (snow) |
| | 147 | * food |
| | 148 | * design process and activities (e.g. game simulations) |
| | 149 | * gather materials (pens/notebooks/cards/cardboard/game pieces/dollys/chairs/etc.) |
| | 150 | * train design team leaders/mentors/facilitators |
| | 151 | * Prepare design guidelines, checklists, feedback forms |
| | 152 | |
| | 153 | |
| | 154 | == Build Season == |
| | 155 | * Project Management |
| | 156 | * Scheduling |
| | 157 | * Resource allocation |
| | 158 | * Calls and runs status meetings |
| | 159 | * Risk assessment and mitigation |
| | 160 | * Coordinates communication between teams (with Systems Eng.) |
| | 161 | * Focus on openness and accountability |
| | 162 | * Communicates status back to team |
| | 163 | * Strategy |
| | 164 | * Game analysis, pick strategy |
| | 165 | * Continuous strategy research and reporting (RiD, Ri3D, Chief Delphi, etc.) |
| | 166 | * Scouting app development |
| | 167 | * Scouting team training |
| | 168 | * Event Planning |
| | 169 | * Event management and reporting results |
| | 170 | * Game |
| | 171 | * Human Player Practice |
| | 172 | * Build practice field |
| | 173 | * Work w/CS on driveability/control |
| | 174 | * Systems |
| | 175 | * Checklists |
| | 176 | * Develop/maintain Space, Power,Weight, Cost Budgets |
| | 177 | * Coordinates between teams |
| | 178 | * Continuous technology research and reporting (RiD, Ri3D, CD, etc.) |
| | 179 | * Pit/Safety Planning, operational checklists |
| | 180 | * White-papers, documentation |
| | 181 | * Cost tracking (work with quartermaster) |
| | 182 | * Mechanical |
| | 183 | * Build 2 identical robots + spare parts |
| | 184 | * Drivetrain |
| | 185 | * Mechanisms 1..4 |
| | 186 | * Co-design w/CS |
| | 187 | * Fast design/build/test cycles |
| | 188 | * CAD/Documentation |
| | 189 | * Ordering/purchasing (coordinate with/cost tracking) |
| | 190 | * Control Systems |
| | 191 | * Build 2 electrical boards + vision systems + spare parts |
| | 192 | * Wiring power, actuators, sensors |
| | 193 | * Co-Design mechanisms and control/sensing w/Mech, Game |
| | 194 | * Low-Level Team: actuator and sensor programming and testing |
| | 195 | * Teleop/Drive (driver station, mechanisms, control) |
| | 196 | * Autonomous (vision, navigation, manipulation) |
| | 197 | * White-papers/documentation |
| | 198 | * Operations |
| | 199 | * Booth/Pit Planning (materials, give-aways, video, decoration) |
| | 200 | * Approach for team spirit |
| | 201 | * Sponsor logos (booth, robot) |
| | 202 | * Targeted awards pursuit |
| | 203 | * Sponsor updates and press releases |
| | 204 | * Business Plan |
| | 205 | * Charm School |
| | 206 | * Website updates |
| | 207 | * Social media updates |
| | 208 | |
| | 209 | == Game Season == |
| | 210 | The team will typically participate in 2 district competitions and if qualified, the district championship. If the team qualifies, it may also attend the World Championship. |
| | 211 | |
| | 212 | * Event Planning (see off-season event details) |
| | 213 | * Driver practice using 2nd robot |
| | 214 | * Organize practice scrimmages at STEMAction |
| | 215 | * Strategy: |
| | 216 | * study competitions and refine strategy |
| | 217 | * Refine strategy based on scouting feedback |
| | 218 | * Game: Build relationships, Negotiate alliances |
| | 219 | * Mech/CS |
| | 220 | * Maintain robot at competitions |
| | 221 | * Test/Fix/Enhance functionality (esp. CS) using 2nd robot |
| | 222 | * Systems: |
| | 223 | * Refine processes/checklists based on feedback from events |
| | 224 | * Plan/execute unbag maintenance windows |
| | 225 | |
| | 226 | == Post Season/Summer == |
| | 227 | * Surveys/gather student feedback |
| | 228 | * Sponsor thank yous |
| | 229 | * Banquet organization (May) |
| | 230 | * Closet/shed Clean-up |
| | 231 | * Capital purchases (based on funds remaining) |
| | 232 | * Add/refine/purchase training materials (based on feedback, experience) |
