Code of Conduct

1. Communication
   

   The group will primarily use the phone and texting. The secondary way of communicating would be email. Calling and texting should be kept to reasonable hours. 9am to 12am during the weekdays. Weekends will be 12pm to 8pm.

2. Roles
   

   Team Leader: George Heller - Arranging and organizing meetings, keeping things on track, scheduling;

   Assistant Team Leader: Parker Cook - Help with arranging and organizing meetings, keeping things on track, scheduling;

   Secretary: Brittney Theis - Taking notes at the meetings, keeping a calendar for the group, keeping the meeting logs up-to-date

   Treasurer: Josh Nguyen - Keeping track of money spent and being responsible for asking for purchase orders and follow up. Also budgeting and keeping things in perspective monetarily.

3. Conflict Resolution
   

   Problems with Scheduling and meeting:

   • If a group member can not make a single meeting for three weeks in a row: Team leader will approach personally to assess the situation. If there are more attendance problems approach Dr. Shih (Waryoba).
   • If a member blows off meetings, does not respond to communication, constant tardiness: Team leader approaches personally. If the member refuses to correct behavior, then approach Dr. Shih (Waryoba). Excused absences: tests or instances that member informs with group (within reason).

   Disagreements with Design:

   • All designs will be considered. When decisions are made there will be a point system established and it there is a tie or a design to close to call, the team members will vote and majority rules, 3:1. If there is a tie amongst the members (ie 2:2) there will be a secondary analysis. The customer gets vote nearer the end with the final ideas.

   Personal Disagreements:

   • If it is amongst two members, those to members will discuss it. If it can not be resolved, the two members should approach the team. If the problems goes beyond the mediation abilities of other members then the group should approach Dr. Shih (Waryoba).

   Customer Disagreements:

   • It will depend on the situation. The ideas and schedules will be moved around to the fit the customer above all else. Compromise will be used. If there are personal problems between the a member and the customer, all attempts will be made to remedy the situation and if the member and customer can’t get along at all, meetings will be held without the member.
   
   
4. Decision Making
   

   All designs will be considered. When decisions are made there will be a point system established and it there is a tie or a design to close to call, the team members will vote and majority rules, 3:1. If there is a tie amongst the members (ie 2:2) there will be a secondary analysis. The customer gets vote nearer the end with the final ideas.

5. Weekly Tasks
   

   The group will meet twice as a group a week and will attempt one contact with the customer a week, whether through email, phone, or in person.  The calendars and task lists will be refreshed weekly to keep things as accurate as possible. Each member will need to report weekly at one of the meetings on the progress of their overall tasks and the individual deliverable tasks.

6. Team Dynamics
   
   George Heller
   • Skills, personal abilities and preferences, and access to outside sources:  Machining, access to CAPS, some lab skills, know engineers in Tallahassee (contacts, references), xpc target, some Matlab, physical work, some Pro-E, some Solid Works, very familiar with metal work and welding, some drafting
   Parker Cook
   • Skills, personal abilities and preferences, and access to outside sources: prefers hands on tasks, enjoys building, ProE, some drawing skills, has some access to a website
   Brittney Theis
   • Skills, personal abilities and preferences, and access to outside sources: proficient in drawing by hand, proficient in Excel, good at technical communications, access to editors, some use of piping diagrams, access to some labs on campus
   Josh Nguyen
   • Skills, personal abilities and preferences, and access to outside sources: Some ProE, basic programming in Matlab
   
   
7. Integrity (Ethics)
   

   Follow FSU Student Code of Conduct. Also the group will follow the Code of Ethics and Standards established by engineering organizations used by professional engineers (American Society of Mechanical Engineering in particular). The group will not allow members to lie or to plagiarize, first and foremost.