2024-08-01 Management New Cycle Meeting

Pickle status

• https://utexas.sharepoint.com/sites/ENGR-LonghornRacing/LHR%20General/Forms/AllItems.aspx?id=%2Fsites%2FENGR%2DLonghornRacing%2FLHR%20General%2FCommittees%2FFacilities%2F2024%20%2D%202025&viewid=d4bda28e%2Dc262%2D4729%2D9b96%2Dcd4fa714fabb

• https://utexas.sharepoint.com/:w:/r/sites/ENGR-LonghornRacing/_layouts/15/Doc.aspx?sourcedoc=%7B02989BF9-3A01-4696-84A4-FF780F98994A%7D&file=LHR%20Meeting%20Agenda%2007-30-2024.docx&action=default&mobileredirect=true

• We can enter and do small things, just no work

• Want to also clean up ETC garage, have solar be participating

• Will probably take everything out of pickle and powerwash

Status of onboarding materials

• Believe first workday, no work should get done. It should be about creating a bond

  • Idea from Sohan

    • first workday with new members: icebreaker, long lunch, social after

    • Second workday: sit new members in front of car and have them ask questions about it. After lunch open up CAD and do the same

• There should not be a long lecture at the start. People don’t learn shit and they just fall asleep

  • There is very little technical theory that we can teach better than a textbook or a youtube video. What we have to do is empower our members enough that they seek out these resources of their own volition

  • What we can teach them: engineering intuition, manufacturing principles, efficiency, curiosity, excitement

• IMO there should be two stages of starter projects:

  • First stage: communal practice and learning

    • EX: Everyone CADs the same thing

  • Second stage: individual exploration and work

    • EX: Each member gets assigned a part to design and they are responsible for it from start to finish

• People’s work should be basically what they will be working on on the car. Not something unrelated

  • Think giving new members projects on Daybreak is a good way to shorten the process for them. Don’t have to wait a year to make what they designed. They can design and then start manufacturing and then literally put it on the car

• Electrical onboarding

  • Move away from infodump lectures

  • Move towards solar specific stuff

  • Give them documentation they can read on their own

  • Starter projects:

    • Didn’t want to be anything super in depth

    • A couple small boards that will still challenge them to use good design principles

    • Tests and drivers that need to be written

    • Go more on the side of tangible stuff they will have to use

    • 1.5 workdays of onboarding before starter projects

• Onboarding for 3 or 4 weeks probably

Technical timelines

Questions to consider:

• To what extent are we going to modify daybreak for FSGP 2025?

• Is a one-year electrical cycle feasible?

  • Are we retrofitting a new electrical system onto daybreak? How modular does it need to be

• Are we comfortable doing design in one semester for mechanical?

• One semester of design, two semester and summer of manufacturing, one semester of testing

  • Finish the car by end of spring break

Want three phases of initial planning:

• Team Goals: a list of all

• Dependency Tree

• Timeline

• Want the car to be finished by end of spring break

  • By end of winter break is too aggressive

• Maybe plan an event for after spring break to force the deadline to be real

  • UT and A&M crossover

First leads meeting

Recruiting calendar

Aug 25, 2024: gone to Engineering
Aug 29, 2024: info session 1 @ 6:30 PM
Aug 30, 2024: open garage 1 @ 5:15 PM
Sep 3, 2024: info session 2 @ 6:30 PM
Aug 4, 2024: open garage 2 @5:15 PM + ops info session @ 4:30 PM (TBD)
Aug 5, 2024: apps due @ 5 PM
Sep 7, 2024: app decisions come out
Aug 9, 2024-Aug 13, 2024 : interviews
Sep 18, 2024: interview decisions
Sep 21, 2024: trial workdays
Sep 25, 2024: official decisions
Sep 28, 2024 : first official workday for everyone

• We have roughly a month from the start of school to the introduction of new members. Good - gives us time to plan for onboarding

  • But not that much time

• Questions we need to answer soon

  • How many members per system

  • What criteria are we looking for in the application process

  • What questions are we going to ask during interviews? How common do we want them to be?

    • Qualitative? Quantitative? Behavioral? Technical?

• Philip gerard kayla kenta should be at open garages

• Open garages 5:15-8:00

Daybreak Repairs

• Replace rod-ends / install new wishbones

• Replace steering pillow block, install second support

• Widen wheel cutouts

• Replace shell-to-frame attachment

• Replace canopy hinge

• Replace BPS enclosure (I think)

• Replace front array module (is this possible?)

The big question: How intact do we want daybreak to be during different parts of the year? Want it running for as long as possible ofc but for frame alterations for instance, it will have to be taken apart

• Perhaps take the frame out halfway thru the year - give electrical time to test and do some drive days

Housekeeping

• Reorganize Confluence

  • IMO put dates in () behind each title, easier to read

  • How are we going to manage additions to Daybreak made during this cycle? Put in this section or the other section

• Empty out clickup and start populating with new things

  • IMO wait until we have a timeline and list of action items

  • How should we separate Daybreak tasks and nextgen tasks?

• Do we want a new leads meeting format?

  • Feel like leads meetings weren’t super well-utilized in the past. A lot of people zoning out when it isn’t their turn, dragged on very long

• Want to have more varied socials this year

  • More socials without alcohol

  • Want powergen and data acq and ergo to come to more socials

• Detach the time from the car

• Separate clickup board for the two cars

• Differentiating between system updates and things that need to be brought up at leads meetings

• Leads meetings should be only stuff other leads should know about

• Division specific stuff should happen in division meetings

• Schedule division meetings before leads meetings

• Chief Engineer goes to division meetings, lead meetings, and two system meetings a week