...
Heads are expected to contribute 15 hours of work per week.
This will typically consist of meetings, bay times, design reviews, design work, manufacturing, Slack messaging, etc.
It won’t make sense to do 15 hours every week. Sometimes there’s a huge push or deadline that requires a 22 hour week, and then you’ll need to do less than 15 hours the following week to catch up on homework. That is fine, as long as you are able to put in the work for the big push weeks and do not consistently do <15 hour weeks.
Weekly Responsibilities
The Head is responsible for doing weekly detailed checks of their system’s FinishLine projects.
The Head should notify Leads is they find any issues with one of their FinishLine projects/work packages. Issues include missed/concerningly close deadlines, missing information, and out of date information.
The Chief Electrical Engineer is in charge of checking over the Head’s FinishLine project(s) and work packages. This should have to happen minimally as the Head should have their FinishLine work well under control.
The Head must organize and run weekly meetings for their system.
Content for these meetings should involve updates from these projects and an informative presentation of some sort. Examples of this would be a presentation on a feature from a project, a tutorial on how to use a certain software, or a guest speaker from another subteam.
The Head can coordinate with a Lead or Leads for them to put together and present presentations.
The Head must make sure the meetings are announced well in advance and send reminders day of.
If the Head is absent, they must coordinate with either one of their system’s Leads or the Chief Electrical Engineer to fill in for them during the meeting.
The Leads are responsible for ensuring the bay, maker space, and other club spaces are cleaned up, but in the case where a Lead is not upholding this, the Head is responsible for ensuring the space is cleaned either by the Lead or themself.
In the case where a system is consistently not cleaning up, the Chief Electrical Engineer may require the system to schedule a 2 hour bay cleaning time where they must clean up and organize everything from their system and use additional time to help with additional chores around the bay.
The Head must provide bi-weekly updates to the Chief Electrical Engineer to share in the Leads channel.
Knowledge Base
...
The Head for each system should be comfortable enough with all software and manufacturing processes used within their system to train members with them. The Head should also have an understanding of how the limitations of these processes impact vehicle design.
The Chief Electrical Engineer is responsible for organizing trainings prior to the heads taking office.
Responsibilities for each system head:
Electrical Powertrain
Electronics
Firmware
These requirements are subject to change based on design decisions made for the car(s) being worked on when the Head takes office.
...
The Head must be consistently well informed on their system’s projects. They should be able to hop on a project in their system that is in crisis to help out, but should never be expected to take ownership over a large portion of the project unless discussed and agreed on with the Chief Electrical Engineer.
...
The Head must be knowledgeable on FinishLine fields and new features to ensure Leads and Members are using it correctly and effectively.
...
Support leads with training new members in software, manufacturing, and assembly skills
ask another member, ask the lead, then ask the head
...
communicate with chief EE when project(s) are behind and need additional help
explain reason is sometimes leads need to switch between projects, want to give more notice and be able to discuss more
...
attend all system design reviews
...
in charge of high level decision making for system
high level meaning decisions that impact multiple projects/systems
...
Responsibilities
From a higher-level, Heads own the success of their system and the welfare of its members, fighting fires where needed
Heads are responsible for:
Ensuring the completion of all projects in their system
Forming and communicating the vision and scope for the internals of the system
Effectively communicating system constraints and goals to relevant stakeholders
Integrating system projects with other electro/mechanical/software projects
Enhancing the workflow and vibe of the system
Meetings
Heads will run two weekly meetings at set times.
System Meetings
Who should be there
Head, leads, and relevant chief(s) should be present
What should happen
Check in with leads on project progress
Time for head and leads to work with members on projects
Bay Times
Who should be there
Head, leads should be present
What should happen
Time for head and leads to work with members on projects
Design Reviews (as needed)
Who should be there
Head, relevant leads and stakeholders
What should happen
Review the design
Finishline
Heads should ensure "Finishline-driven” development
The Head is responsible for
Doing weekly detailed checks of their system’s FinishLine projects.
Ensuring that project timelines are up to date
Creating and defining new projects
Maintaining accurate budget of projects