Skip to content

A Repository Storing the StuyPulse's Team Charter

Notifications You must be signed in to change notification settings

StuyPulse/charter.stuypulse.com

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

40 Commits
 
 
 
 

Repository files navigation

StuyPulse Team Charter

Table of Contents

Mission/Purpose:

This is a student led club designed to promote interest in the study of robotics and STEM through the teamwork of students, parents, mentors, and sponsors. We increase robotics and STEM awareness in our community and encourage education in engineering, computer science, web design, 3D animation, business, fundraising, and marketing. The club participates in robotics competitions, including ones organized by FIRST, an international robotics organization.

Description:

The Stuyvesant Robotics Team is an organization dedicated to the practical application of science, technology, and business in the field of robotics. We undergo an intensive, but enjoyable, six-week build season during which we build a robot for the FIRST Robotics Competition (FRC).

Our mechanical engineering department designs and builds the hardware of the robot, from each of the mechanical components to the electronic and pneumatic systems.

Our software engineering department develops the software used to control the robot as well as supporting software for the team.

Our business department provides real-world experience in non-profit fundraising and advertising as well as managing the logistics of a large team.

Our strategy team, comprised of members from all three departments, offers strategic assistance regarding robot design, gameplay, and alliance selections.

Our PulseLabs team is responsible for ensuring all research and development projects that the team undertakes are documented and assist EC in managing research as needed. Read more about PulseLabs here.

  • The validity period of PulseLabs, and related AC roles, will be of one year, and the team must vote to renew PulseLabs, or vote to solidify PulseLab's place within the team for perpetuity, unless removed by amendment, at the following (2025) charter amendment meeting.

Our media team, comprised of members from all three departments, is led by the business department and is in charge of all media related matters (e.g. videos, pictures, etc.).

Our Inspiration Team, comprised of members from all three departments, is led by the business department and is in charge of all matters related to the "Impact Award" (e.g. presentation, essay, speech, outreach ideas, video ideas, etc.).

We require no prior experience at all in mechanical engineering, software engineering, business, strategy, media, or presenting and will teach the skills members need to be able to participate in FRC.

Membership on StuyPulse is unrestricted. The club does not restrict membership on the basis of race, gender, ethnicity, commitment to other clubs, grade, or any other such factors. It is understood that those students who enjoy the club will attend and those who do not attend will not be considered members of the club.

Charter Amendments:

The amendment process will begin sometime after the last official competition of the school year. It is an open meeting, with the only requirement being that there must be at least two­-thirds of the Elected and Appointed Council present. All members who have paid their team dues, passed the safety test, and met a specific percentage of attendance may attend and vote. This percentage will be decided by the EC and faculty advisors. In the days leading up to the meeting, a list of eligible members shall be made public. Members who would like to propose charter amendments may submit proposals to the team in order to start discussion. Amendments not proposed prior to the meeting may be discussed at the end of the meeting if there is extra time.

The presidents of the team will preside over the charter meeting. They will decide on the order in which to address emailed proposals. Each proposal will be read and must be seconded to move to an initial vote to see where people stand. If the vote is unanimous, there will be no discussion or second vote. If there are conflicting views, members will be given time to discuss their thoughts on the issue. After discussion, the presidents will call for a final vote, where the majority decides the fate of the proposal. If the faculty advisor finds any issue with a part of the charter, there will be another charter meeting to revise the problematic parts. The Moderator(s) of the charter meeting shall appoint a minutes taker. The minutes will be made publicly available to all members of the team, present at the charter meeting or otherwise. The new Elected Council for the next school year will update the charter amendments in a timely manner and before the next charter meeting.

Elected Council (EC):

President of Mechanical Engineering (PoME): The President of Mechanical Engineering manages and oversees the construction and maintenance of the robot. They delegate the construction of the mechanisms of the robot. They are familiar with every mechanisms of the robot and able to explain the mechanisms to another team member or a judge. The PoE is also responsible for making administrative decisions for newbie education. Throughout the build season, they are a major contributor to the CAD and oversee the pits during competitions. They also communicate and work closely with the PoSE, Director of Electronics, and Director of Pneumatics to maintain the robot's systems.

President of Business (PoB): The President of Business holds final responsibility for all outreach, logistics, and award submissions for the team. They have full knowledge of all awards and shall present the Impact Award or assign the presentation to someone else deemed competent. The PoB also has adequate knowledge of the other two departments.

President of Software Engineering (PoSE): The President of Software Engineering balances the development and delegation for newbie education and member training, in-season robot coding / testing, team code libraries, and research projects. The President of Software Engineering should also uphold commendable coding practices and clean Git practices for team repositories (e.g. commented code, PR’s often, test before merge). The President is responsible for working with the Director of Newbie Relations to handle newbie training and engagement year-round. The PoSE also collaborates with the Strategy team to develop effective solutions for both the teleoperated and autonomous modes. During build season, the PoSE is responsible for scheduling code reviews to ensure team members are informed about the state of the robot code. Additionally, the President should bridge the gap with the Mechanical Engineering department during this time to build an interdepartmental understanding of prototypes, finalized mechanisms, and the robot as a whole. Furthermore, the President of Software Engineering, along with the President of Mechanical Engineering, should collaborate on testing time with the robot with the goal of making the robot as competition-ready as possible.

Vice President of Mechanical Engineering (VPoME): The Vice President of Mechanical Engineering is considered the second-in-command for the Mechanical Engineering department. They have knowledge of what the Presidents are currently doing and is able to direct the Mechanical Engineering division in the event of the PoME’s absence. The VPoME also has extensive knowledge of each part of the robot as well as basic knowledge of all awards submissions.

Vice President of Business (VPoB): The Vice President of Business is the second-in-command for the Business department. The VPoB should have knowledge of what the President of Business is currently doing and should be able to direct the Business department in the event of the PoB’s absence. They have extensive knowledge of all award submissions as well as basic knowledge of each part of the robot.

Vice President of Software Engineering (VPoSE): The Vice President of Software Engineering is the second-in-command for the Software Engineering department. They have knowledge of what the President of Software Engineering is currently doing and should be able to direct the Software Engineering department in the event of the PoSE’s absence, as well as collaborate with the President of Mechanical Engineering in managing the overall robot project.

It is the responsibility of the EC to create an annual Operations Plan. The Operations Plan includes the administrative process of the team to improve quality and increase efficiency in operation. It may include preliminary budgets and operational strategies for each department and a timeline for the pre­season, build season, and competition season. EC members are required to attend all competitions/regionals during the season, unless extenuating circumstances (health, family emergencies, etc.) which must be explained to Mr. Blay ASAP.

Appointed Council (AC):

Directors and assistant directors are responsible for seeing the completion of their respective jobs, but do not necessarily have to be the ones to complete the job. The role of the director and assistant director is to ensure the job is completed, and to organize/delegate the job(s) to members of the team who wish to help in their specific area.

Assistant directors must be appointed after directors. This is to ensure that directors have a say in who their assistants will be.

PulseLabs

The validity period of PulseLabs, and related AC roles, will be of one year, and the team must vote to renew PulseLabs, or vote to solidify PulseLab's place within the team for perpetuity, unless removed by amendment, at the following (2025) charter amendment meeting.

Director of PulseLabs (DoPLs): The Director of PulseLabs will assist the EC in organizing all research and development (R&D) efforts. They will maintain a system of documentation distribution, ensure documentation produced by PulseLabs members are up to standards outlined by authoritative documents, update said authoritative documents as needed. They should have a level of understanding of all ongoing and past research projects, maintain a clear line of communication with the EC to ensure research goes smoothly and subsequent knowledge is communicated and applied, ensure researched knowledge is transferred to the larger team, ensure research efforts are published in a timely manner, and publish an annual report as to the state of PulseLabs, which is to be completed by the end of the school year (see exception in the PulseLabs section for the 2025 season).

During the off-season, the DoPLs will be primarily responsible for assisting the EC in organizing, supporting, and understanding these research efforts. They will also be responsible for ensuring that the research efforts are documented and published in a timely manner and for ensuring that the research efforts are communicated to the rest of the team.

During the build season, the DoPLs will be responsible for assisting the EC in ensuring that the research efforts are communicated to the rest of the team, and that the knowledge gained from such research efforts are applied to the robot. The DoPLs will also be responsible for ensuring that the robot's design and features, especially those derived from research efforts, are documented, updated, and published as necessary.

Strategy

Director of Strategy (DoS): The Director of Strategy is responsible for all things strategy-related. The Director of Strategy is responsible for recruiting, structuring, running and ensuring the wellbeing of a team of strategists. From the start of the season, the Director of Strategy must ensure that all team members know game and robot rules. The Director of Strategy can suggest designs, features, and/or adjustments to the robot, as well as autonomous routines, to allow for possible gameplay strategies. In addition, the Director of Strategy assembles and trains match scouts that will gather data on other teams during competitions.

During competition, the Director of Strategy and their strategy team are responsible for creating match strategies and communicating with our drive team and those of other teams in our alliances. In addition, the Director of Strategy is responsible for heading and collaborating with their team of strategists in making a list of teams for alliance selections, the size of which should be at least one less than the number of teams moving into eliminations for the given competition.

The Director of Strategy is also responsible for the selection, training, and practice of all members of the drive team. Each member of the drive team is to be selected through tryouts organized by the Director of Strategy, with the exception of a continuing driver, operator, or coach. Conflicting responsibilities are to be taken into account for the final selection. The drive team must be approved by the faculty advisors.

Assistant Director of Strategy (ADoS): The Assistant Director of Strategy is responsible for collaborating with the Director of Strategy and the strategy team throughout the season. The Assistant Director of Strategy is to be familiar with all aspects of strategy and be ready to assume the jobs of Director of Strategy if necessary.

Business

Director of Finance (DoF): The Director of Finance is directly responsible for creating the yearly Financial Plan to indicate the fundraising goal for the year. In addition, the Director of Finance is also responsible for fundraising through applying for grants and contacting current or potentially new sponsors. The Director of Finance must also maintain stable relationships with sponsors and contact them on a regular basis.

Director of Impact (DoI): Part of business AC. Leads all Impact efforts including documentation, presentation, and scheduling practices. They are in charge of making sure presenters get tried out and may be a presenter.

Director of Operations (DoO): The Director of Operations will handle the day-­to-­day operations of the entire team. The Director of Operations is responsible for all paperwork, trip planning, managing deadlines and other logistics regarding the team. Their responsibilities may include collecting team dues, participant information like IDs, and attendance.

Director of Public Relations (DoPR): The Director of Public Relations will plan for outreach events and direct all outreach initiatives, such as Stuy Splash and public demonstrations. At the same time, the DoPR is responsible for creating a strong team media presence using blogs, photographs, videos, social media, and other media.

Director of Media (DoM): The Director of Media is responsible for the creation of all visual and media content for our social media platforms. They are also responsible for taking pictures and videos at all team events. They are to work alongside the Director of Public Relations to create necessary content. The DoM is also responsible for leading and educating the members of the media team, composed of members from all three departments and in charge of all media related matters (e.g. videos, pictures, etc.).

Mechanical Engineering

Director of Electronics (DoE): The Director of Electronics sets up and manages the electronic systems on the robot to FIRST regulations. They cooperate with both engineers and software engineers to ensure that the electronic systems are organised and able to be modified if needed. The DoE is also responsible for the education of other members in the electronics subdepartment. The Director of Electronics is also responsible for the creation and management of the pneumatic system on the robot according to FIRST regulations. The director is responsible for the upkeep and maintenance of all compressors, solenoids, and pistons.

Assistant Director of Electronics (ADoE): The Assistant Director of Electronics is familiar with all aspects of the electronic systems on the robot and be able to assume the jobs of Director of Electronics at any time.

Director of Lab Operations and Safety (DoLOS): The Director of Lab Operations and Safety, at the highest level, is responsible for the smooth running of the team’s workspaces. They are responsible for keeping a detailed inventory of the tools and construction materials in the laboratory as well as a record of materials used in the construction of the robot. The DoLOS is also responsible for ensuring that all necessary safety rules are observed in the lab during build season. The DoLOS will automatically be appointed Safety Captain at the competition and will be responsible for carrying out all duties therein.

Director of Mechanical Newbie Education (DoMNR): The Director of Mechanical Newbie Relations is responsible for the education of new members in mechanical engineering, engagining newbies in all efforts related to the robot or team, development of a curriculum, and ensuring the lessons are made in advance. The DoMNR is also responsible for ensuring the new members feel included, and have tasks during the off-season. The DoMNR is also responsible in making sure that all the veterans are well equipped andunderstand their task to help teach the newbies. They are also responsible for managing newbie education.

Director of Procurement (DoP): The Director of Procurement is responsible for overseeing and actualizing the procurement of goods necessary for the team’s operation. The DoP is similarly responsible for identifying adequate substitutes when a necessary resource cannot be obtained from the traditional supplier for a reasonable cost. All procurement requests must be approved by a faculty advisor. The DoP is also required to maintain a detailed, uptodate account of the team’s expenditures, available on request.

Director of Design (DoD): The Director of Design is responsible for the upkeep of the CAD model of the robot and all elements thereof with the aid of a CAD team. This CAD team is to be instructed in the use of CAD programs and led by the Director of Design.

Director of Machining (DoM): The Director of Machining is responsible for the maintaining the mill, lathe, and their parts. He/she must also make sure that there will be at least two members of the team that will be able to use the mill in the upcoming year, including the Director of Machining. If there are fewer than two such members, the Director of Machining is responsible for training new members.

Assistant Director of Machining (ADoM): The Assistant Director of Machining is familiar with the mill, lathe, and their parts, and be able to assume the jobs of Director of Machining at any time.

Director of Field Construction (DoFC): It is the job of the Director of Field Construction to construct the field of the released game with acceptable accuracy. For each function that the robot has to perform, it is this person’s responsibility to ensure that at least one set of the field elements involved in that task is procured and produced. However, the DoFC will also be responsible for all other fields, including FLL, FTC, and FRC fields. They are responsible for the upkeep of the shipping/robot crates and building new robot carts.

Software Engineering

Director of Software Newbie Relations (SE) (DoSNR): The Director of Software Newbie Relations is responsible for the education of new members in software engineering, engagining newbies in all efforts related to the robot or team, development of a curriculum, and ensuring the lessons are made in advance. The DoSNR is also responsible for ensuring the new members feel included, and have tasks during the off-season.

Assistant Director of Software Newbie Relations (SE) (ADoSNR): The Assistant Director of Software Newbie Relations should be primarily responsible for managing groups and communication and splitting up oldbie resources to most effectively promote group work. Beyond that, the ADoSNR should also be responsible for assisting the DoSNR with creating the curriculum, coming up with ideas, and lecturing. The Assistant Director of Software Newbie Relations is to be familiar with all aspects of newbie education and be ready to assume the jobs of Director of Software Newbie Relations if necessary.

Director of I/T (SE + Business) (DoIT): Responsible for creating new technology related to team logistics, continuous integration and development of existing technology, documenting existing tools, teaching members interested in I/T. The director ensures that I/T responsibilities are focused on the team website, the team manager, and important tools for attendance. The director of I/T will also have to communicate with business to ensure the team's website is up to date. The Director of I/T is also responsible for raising violations of the EC/AC attendence policy.

Assistant Director of I/T (SE + Business) (ADoIT): The Assistant Director of I/T should be familiar with the tools the I/T sub-department uses. The Assistant Director of I/T will be able to assume responsbility of Director of I/T whenever needed.

Elections:

Elections will take place after the charter meeting each year. This is done in order to give the newly elected officials a chance to become familiar with the position and with the handling of the team. After members have been elected to their positions, they will appoint members to the AC. There is no term limit for any position, but candidates must run for election every year, whether or not there is any opposition. A member of the team who will no longer be a Stuyvesant student the following year or who is not eligible to vote may not run for any elected position.

Rules for Elections:

  • Elections will begin with a call of attendance, after which nobody may leave the meeting without permission and without filing an absentee ballot, assuming that member is eligible to vote.
  • All members at or above a certain attendance percentage who have paid their team dues and have passed the safety test may attend and vote. This percentage will be decided by the EC and faculty advisors. Prior to the elections, a list of eligible members must be made available.
  • An absentee ballot is an official ballot on which the person leaving writes down the name of one person for every position for which they wish to cast a vote. The ballot will be given to the person in charge of elections. If the absentee does not choose a candidate for a position, they are abstaining from the vote for that position.
  • One team member, chosen by the Elected Council, will preside over elections as Moderator. They must uphold the rules, maintain order, and mediate any disputes that arise.

Order of Elections:

The Presidents of each department must be elected before The Vice Presidents. The order of The Vice Presidents may be the reverse order of The Presidents, but it is at the discretion of the Moderator.

Election Process:

The following election process will be followed for every position.

Candidacy Announcement:

  • Members must send out a candidacy email prior to elections in order to run for an elected position.
  • A person becoming a senior in the following year may not run for vice presidency.
  • A person may run for any position absentee if approved by two members of the current EC. The two members of the EC who approved the candidate will serve as one nomination for the candidate. This nomination must be seconded at the election by someone other than the two EC members who approved the absentee candidate.

Candidate Presentations:

At the start of a position being spoken about, the moderator will share the candidates' attendance rate.

Each candidate is given up to four minutes to present his or her qualifications for the position. The order of the presentation will be determined by the members running the election.

Discussion

A discussion will be held for each position following the presentations of those running for the position. The candidates are to be outside the main meeting during the discussion period.

Voting:

When the presentations are completed, all candidates will be asked to leave the main meeting and voting will commence. Voting for a department's candidate will only be done by the department if that department has 9 or more members. Otherwise, the entire team will vote on that candidate. The current EC may vote for all department elections. Awards, Outreach, and Fundraising may vote for Business elections. I/T may vote for both SE and Business elections. The moderator may vote.

  • Ballots will be counted by the Moderator and one official mentor. Vote totals will not be made public to the team.
  • Submitted ballots may only be viewed by the Moderator and the mentors. If another member of the team has intentionally viewed a ballot, that member will lose their right to vote for the remainder of the elections.
  • Students will rank their nominees in order of preference from 1 to however many they wish to put.
  • The votes are sorted based on who they ranked first.
  • If there is a clear majority, that individual wins the first nomination.
  • If there is not a clear majority, the nominee with the fewest votes will be removed, and their votes will then be sorted based on the second choice listed on the ballot.
  • This will keep occurring until one nominee has a clear majority.
  • After the first nominee is selected, the process is repeated with the same ballots to determine the second nominee.
  • A “NONE” candidate is included in every election If NONE wins the election, the position will become appointed.
  • A member may choose to abstain from voting during the election for any given position.
  • If a candidate is running unopposed, then the voting process will be expedited with a limited question and answer period.
  • In the case that no member is elected to any position, all present members of the current EC/AC will appoint the Presidents to represent the new EC/AC and follow the procedures of appointment.

Appointment:

Any appointed position will be decided by a majority vote of the elected officers after the conclusion of the election. The member chosen may decline the appointment, in which case another member must be appointed.

In the case that a majority vote cannot be reached by the elected officers, appointment of that position will be delayed. After all other positions are filled, the EC/AC will vote on the appointed position again.

In the event that any position is not filled by the EC/AC for any reason, the position shall remain vacant.

AC positions may be held by any team member, regardless of the department that the team member is part of.

Impeachment:

Any member of the EC/AC, Impact Team, or drive team may be impeached for reasons that include but aren’t limited to:

  • Dereliction of duty
  • Poor attendance, meaning missing 4 or more of last 10 meetings. (Enforced by Director of I/T)
  • Ignoring or disregarding the general will of the team
  • Performing actions that are legally or morally detrimental to the team, such as:
    • Embezzlement
    • Disregard for safety
    • Intimidation of members
    • Misappropriation of team resources

Impeachment proceedings for EC/AC are initiated through warnings given by a two-thirds majority of the EC/AC. The officer in question may defend himself/herself, and a two-thirds majority of the entire team will uphold the impeachment.

Any officers, unless suspended by the faculty advisor(s), may be reappointed at any time by a two-­thirds majority vote of the Elected Members. In the event of an impeachment or in the event that a member of the EC/AC resigns, the position will be filled by a two-thirds majority vote of the remaining EC/AC. When the position of President of Mechanical Engineering, President of Business, or President of Software Engineering is vacant, his/her Vice President may temporarily fill the position as President until the EC/AC has elected another member of the team to serve as President.

Impeachment proceedings for the Impact and drive team are initiated through warnings given by those responsible for each team.

Those responsible for the Impact Team include:

  • EC
  • Members of the Impact Team

Those responsible for the drive team include:

  • EC
  • DoS
  • ADoS
  • Members of drive team

The member in question may defend himself/herself, and the EC may uphold a decision to immediately remove the member under extreme circumstances.

Any Impact or drive team member, unless suspended by the faculty advisor(s), may be reappointed at any time by a simple majority of those responsible for each team. In the event of an impeachment or in the event that a member of the drive team or Impact Team resigns, the position will be filled by a simple majority vote of those responsible for each team.

Impeachment shall not be used to settle political or personal disputes.

Awards:

Impact Award:

Each department's EC members will select 2 delegates to contribute to the Impact Essay.

Woodie Flowers Award:

The nomination process will be moderated by the Presidents in attendance.

All veteran members of the team are allowed to take part in the Woodie Flowers Award nomination. The nomination process will be conducted without the presence of any mentors in the room.

The nomination process will begin with the moderator(s) asking for any nominations for the award, excluding any previous Woodie Flowers Award Finalists. Members will then be allowed to state their nominations, and their reasoning. The nominee must be seconded by another member to considered in the final vote.

Once all nominations are made, discussion will be allowed. The amount of time allowed for discussion is left to the moderator’s discretion. If you nominate a candidate, you are accepting the responbility to lead that submission if no one else steps up.

After the discussion period is over, all members will close their eyes.

Moderators will call out the name of each nominee, and count the number of votes they receive.

Each member is allowed to vote for only one nominee. If you cast an affirmative vote in favor for a candidate, you are require to contribute 1 sentence to the award submission.

The nominee with the most votes will be the mentor the team nominates for the Woodie Flowers Award.

In the case of a tie, another round of voting will be conducted with the only the tied nominees from the previous round.

Following this, a previous Woodie Flowers Award Finalist will be chosen to be nominated for the award at the World Championship. The moderators shall list the names of the previous winners. Afterwards, discussion will be allowed. The amount of time allowed for discussion is left to the moderator’s discretion.

After the discussion period is over, all members will close their eyes.

Moderators will call out the name of each previous winner, and count the number of votes they receive.

Each member is allowed to vote for only one individual.

The individual with the most votes will be the mentor the team nominates for a chance to win the Woodie Flowers Award at the World Championship.

Dean’s List Award:

The nomination process will be moderated by the highest ranking senior member(s) in attendance.

All veteran members are allowed to take part in the Dean’s List Award nomination excluding the juniors. All juniors must be outside of the room when the nominees for this award are being chosen.

The nomination process will begin with the moderator(s) asking for any nominations for the award. Only members in their junior year may be nominated for this award. Members will then be allowed to state their nominations, and their reasoning. The nominee must be seconded by another member to considered in the final vote.

Once all nominations are made, discussion will be allowed. The amount of time allowed for discussion is left to the moderator’s discretion. If you nominate a candidate, you are accepting the responbility to lead that submission if no one else steps up.

After the discussion period is over, all members will close their eyes.

Moderators will call out the name of each nominee, and count the number of votes they receive.

Each member is allowed to vote for two nominees. If you cast an affirmative vote in favor for a candidate, you are require to contribute 1 sentence to the award submission.

The nominee with the most votes will be selected as the first Dean’s List Award nominee.

In the event of a tie, a runoff vote will be held with those nominees.

Another round of voting will be held with the same nominees, excluding the already selected individual. The nomination process will follow the same procedure as it does for the first selection.

After selecting two students for the award, the moderators shall inform the head coaches about who was selected. After their selection is approved, the nominees may be informed.

PulseLabs:

The validity period of PulseLabs, and related AC roles, will be of one year, and the team must vote to renew PulseLabs, or vote to solidify PulseLab's place within the team for perpetuity, unless removed by amendment, at the following (2025) charter amendment meeting.

For the (2025) FRC season, the PulseLabs annual report must be completed at least approximately 1 week, or with enough time such that the performance and efficacy of PulseLabs may be reviewed by the team, prior to the annual Charter Amendment Meeting.

PulseLabs is an overseeing body within StuyPulse that is responsible for assisting EC in organizing and documenting all research and development projects within the team. Team members are encouraged to participate in efforts to further the team's knowledge within their respective departments, and PulseLabs will be responsible for ensuring that these efforts are documented. PulseLabs will be responsible for aiding the team in furthering and archiving the team's knowledge to gain a more competitive edge through advanced technology in FRC. Any effort towards advanced knowledge or technology will be within the purview of PulseLabs and its documentation requirements. Research in new technologies and techniques will become a key part of the team's success as we meld novel technologies with the tried and true methods of the past.

Leadership:

PulseLabs will be led by 2 Directors of PulseLabs (DoPLs), and their responsibilities are detailed here under the Appointed Council section. DoPLs should be chosen on the basis of interest in helping further the team's knowledge and performance through the application of novel technologies or techniques, along with managing the documentation process. There is no requirement for which department the DoPLs must come from, but they must have a strong understanding of the team's operations and a willingness to learn about new technologies and techniques.

Responsibilities:

  • Ensuring EC members of their respective departments are informed of these research efforts, the results of these efforts, and the applications of these efforts.
  • Ensure the transfer of knowledge from research efforts to the rest of the team.
  • Maintain a detailed and open record of all research and development projects undertaken with the support of the team.
  • Documenting the key components and results of any research effort.
  • Sustain and utilize a comprehensive and consistent system in publishing, for both internal and external usage, of research efforts, results, and applications.
  • Publish an annual report as to the state of PulseLabs, including ongoing and completed research, by the end of the school year.

Documentation:

All research and development projects undertaken by the team must be documented in a manner that is accessible to all members of the team. This documentation will also be made available to the public, unless designated otherwise by the DoPL and/or EC, using means such as but not limited to through the team's website and Chief Delphi. A system must be in place to ensure that all documentation produced by PulseLabs are distributed, stored, and archived in a manner that is accessible by any party at any point in the future.

The format and types of documentation will be standardized according to a series of authoritative documents, and all documentation must follow the guidelines set forth in these documents. These authoritative documents may undergo revision by the DoPL and the EC. All documents must be reviewed and approved by the DoPL before being published to ensure for the quality of the document. The DoPL may request for changes to be made to the document before approval.

All research efforts done in the team must have documentation attached to them, maintained throughout the research process, updated as necessary. This documentation may be in the form of a running document or a series of Technical Memorandums released at key points in a research effort. Documentation includes maintaining an accurate and complete list of references to all sources used in the research effort, including but not limited to books, articles, and websites. A Technical Article must be released at the conclusion of any research effort, regardless of the success of the effort, which should summarize findings, methodology, conclusions, further research, applications, etc.

Additional Amendments:

There will be an attendance requirement, as a percentage, to go on team trips. The exact number will be determined by the EC and faculty advisors.

The EC may call charter or team meetings throughout the year as needed

Attendance is required to be taken on a per meeting basis to easily track those who attend meetings and clear up arguments over attendance.

Reflections are required to attend offseason events. They are due the day trip forms are due for the first offseason event. If a reflection is not submitted by the deadline, a 250-word supplementary essay detailing why the reflection is late needs to accompany the late reflection and be submitted to the EC or mentors.

There will be an annual volunteer requirement. Team members, regardless of position, must complete at least one volunteering event. To prove they volunteered, they are required to take a picture of themselves at the volunteering venue and submit it to the Director of Public Relations. Members who fail to meet these requirements will be barred from all team trips until this requirement has been fulfilled. Volunteer hours are reset after the season (championships) is over.

About

A Repository Storing the StuyPulse's Team Charter

Resources

Stars

Watchers

Forks