Planning & Execution
Table of Contents
Team SetupBased on our given backgrounds and various discussions we have developed the following team roles and responsibilities. These will continue to change as our roles develop throughout MSD I and II.
Robert Cybulski - Project Manager
- Create/assign tasks
- Organize group meetings
- Primary contact with customers
- Assist with engineering work
Mike Troise - EDGE and CAD Specialist
- EDGE Support
- CAD Designer
- Solid body mechanics specialist
Alison Wright - Fluids Engineer
- Lead fluid flow/hydraulic technical calculations and decisions
- Ensure ASTM standards are meets for hydraulics and human factors
- Create diagrams and drawings
John Stelmack - Facilitator/Statistics Lead
- Project planning/scheduling
- Ensure statistically sound tests are conducted
- Ensure product is designed for manufacturing
Robb Foote - Electrical Lead
- Design the electrical system to control the motor and valves
- Program PLC to control the valves and motor
- Assist with Hydraulic information
Team Values and Norms
Team ValuesThe following is a brief summary of the values that the team has agreed are important in successful team work.
- Punctuality - All members should consistently attend scheduled meetings and arrive on time. Any issues should be communicated within a reasonable time frame prior to the meeting. An absent member should confirm that the group has received their message.
- Thoroughness - Team members are expected to fully complete assigned action items by the given deadline. Work should be complete such that another team member does not need to re-do any work.
- Accuracy - Each team member completes their work accurately and in a way that can be easily checked for accuracy by peers and the faculty guide. All work is fully documented and easy to follow.
- Professionalism - Criticism of group member performance should be constructive, and team members should always be looking to improve their performance. Be respectful of other team members and immediately address any issues. Stay up to date on meeting minutes and completed tasks. Always be honest with our customers and with submitting work.
- Commitment - Team members should be actively engaged in the project both in and out of class, and making sure they are pulling their own weight.
If problems arise within the team, this escalation process will be used:
- Address the issue within the team at a group meeting. Avoid having altercations over text, email, or even a phone call.
- Bring issue to team guide.
- Bring issue to Dr. DeBartolo.
- If issue is still unresolved and all prior methods have been fully exhausted, bring issue to department coordinator of team member causing an issue.
Intellectual Property Considerations
Depending on the deliverable we end up with, we may end up being able to apply for a U.S. patent. We would most likely need a utility patent as it would better cover our cylinder concept and design. After discussing with our customers, the I.P. for this project will belong to us, however they would like the rights to use our technology developed at a cheaper rate than any other external companies.
Project Plans & Schedules
For those with access, our live action item document can be found here.
Problem Definition Phase Schedule
Systems Design Phase Schedule
Preliminary Detailed Design Phase Schedule
Detailed Design Phase Schedule
Preliminary MSD II Schedule (From end of MSDI)
MSD II Schedule
Throughout this phase the schedule has become more detailed. As final design decisions are made, the schedule will become even further detailed to track the progress of specific parts. Such details will include when to order stock material and parts, when to send drawings to the machine shop or ACM, and when the parts will be finished and ready fro assembly. Additionally, individual test plans will be tracked in the schedule. As our schedule has been greatly expanded, we will not be posting full screenshots moving forward. Our latest Microsoft Project schedule may be downloaded here.
Risk Assessment and Growth Curves
These are some preliminary risks identified at the start of the project. These will change throughout MSDI and MSDII.
Other Team ResourcesYour team may have other resource requirements. With your customer and guide, your team should identify:
- Planned meeting space:
- MSD Design Center
- Planned build & test space:
- MSD Design Center
- ME Machine Shop
- RIT safety training
- lab/studio safety - completed
- hazardous waste management
- gas cylinder training
- shop safety
Meeting Agendas & Minutes
|Week Number||Date||Meeting Agenda||Meeting Notes|
|Summer||6/19/18||Summer MECE Meeting Agenda||Summer MECE Meeting Minutes|
- Customer point of contact: Eric Wellington
- Primary contact method: Email for quick questions. Phone call for more in depth conversations.
- Expected frequency of communication: Once or twice a week depending on what the team is working on.
- Project review customer availability: Generally available during class time.
- Robert Cybulski will be the main point of contact
- Team should be cc'ed on technical emails and others pertinent to project success.
- Pre-read documentation should be shared with customer 48 hours before review via email/dropbox.
- Expectations for within-team communication:
- Preferred method of communication within group is GroupMe app.
- Guide should be cc'ed on all emails with the customer and included in important phone calls.
- All team members should be included on weekly recap emails.
- Professor Tim Landschoot would like to be invited to all project reviews.
Because our project review powerpoints contain sensitive info, we have opted to not include them on this page. For those with proper credentials, they can be found here.
Home | Planning & Execution | Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design MSD I | Detailed Design MSD II | Build & Test | Customer Handoff & Final Project Documentation | Gate Reviews