Table of Contents
MSD I Gate Review: Readiness to move to Build & Test
In MSD I our team was able to successfully improve upon the articulating toilet design presented by the P190011 team. Throughout the duration of MSD I, we worked to identify shortcomings in the presented design and improve upon them to deliver a solution that would successfully deliver on the needs of the customer. The results of this phase were a completed articulating toilet design that will be build through the duration of MSD 2.
In reflecting on MSD I, our team was able to successfully adhere to our intended schedule and accomplish all of our goals, with the exception of our intended donation request submission to the home depot. This unexpected issue did not delay project progress as the team was able to develop a plan to submit for extra funding. The other major change our project team faced was the removal of the tilt feature of our design during this phase. This project decision resulted in a simplified design and the ability for the team to focus their time on other prototype features.
Through this process our team has identified 75 + risks, and worked to mitigate and eliminate many threats that would pose risk to the team that may result in project delay.
During the team's detailed design review, there were a handful of concerns raised with the system design. They were as follows.
1. System base should be flat rather than raised to allow the user to approach the toilet closely. GREEN
2. The torso support bar may need to be secured using a ball joint. GREEN
3. The customer would like the system housed as there is concern of pinch hazards in the design. GREEN
It was discussed that these features would be fleshed out in the testing phase of the design, and the project team recognized that these may need to be extra budget planned to test these design features.
As a final step, the project team have each completed self critiques were we evaluated both our individual performance and the team performance.
Risk Assessment AnalysisThroughout the duration of MSD 1, our team was able to create a list potential risks that correspond to certain stages and aspects of our project. These risks were meant to reflect certain events that could have happened during this most recent semester. The main goal in mind was to think of the risks before they actually happened so that if one of them were to occur, we would already have a plan on how to handle it and on how to minimize the chance of it occurring in the first place. Each risk was also ranked/graded on likelihood and on severity using a "3, 6, 9" grading scale. This grading method was used in determining the overall importance of each risk.
We started coming up with risks right at the beginning of the semester during the Problem Definition Phase and continued to add onto the list all the way through the end of the Detailed Design Phase. The list itself went through several modifications throughout the semester. The end of each of the 4 phases corresponded to a certain "revision" of the actual risk spreadsheet, giving us a total of 4 revisions. Each of the risk spreadsheets can be seen below:
- Phase 1: Problem Definition: click here
- Phase 2: System Level Design: click here
- Phase 3: Preliminary Detailed Design: click here
- Phase 4: Detailed Design: click here
When comparing our risk total from the end of the Problem Definition Phase to the end of the Detailed Design Phase, the number increased from 15 risks to 75 risks. Of the 75 risks, we were able to close out about 15% of them (11/75). An example of a risk that we encountered was our donation request being denied by Home Depot. Although this risk wasn't one that was of high severity, we still experienced it nonetheless. We were able to deal with this risk by finding an alternate source for acquiring parts, whether it be purchasing items using our budget or using some of the materials that Marlon was able to acquire during his time on co-op. Another risk that we experienced firsthand was the Bill of Materials spreadsheet not being completed by the end of the Detailed Design Phase. Although we were able to come up with a reliable cost estimate for the majority of our parts/materials, we recognize that we are going to be adding on to the BoM throughout the duration of MSD 2. Certain hardware that will be needed for certain components (such as the hydraulic system) is still unknown, but will be determined eventually.
As for our most important risks (severity of 81), we had a total of 2 and we were successfully able to close out 1 of them. The one that we were able to close out involved the group members getting busier with other classes throughout the semester. This risk led to the team not being able to spend as much time on MSD as we did at the beginning of the semester. However, we dealt with this risk by communicating with each other and making sure that help was being offered where it needed to be. If a group member was getting too overwhelmed with work for other classes and could not put as much time into MSD as they would have liked to, they could ask for help by reaching out through the Slack group chat that we created.
Thankfully, none of our risks were able to manifest into actual problems. The team did an excellent job making sure that any conflict/setback was handled professionally and efficiently. Our risk list evolved during the semester. A lot of the risks reflect what phase the group was working through at that particular moment in time. We learned a lot about how certain project phases can correspond to certain risks and how to handle a risk if it presents itself to us. Overall, our risks assessment was highly effective and was handled very efficiently.
Bill Of Materials Budget Increase Request
Based on the anticipated materials needed it was determined that our team will require a budget increase. We are anticipating spending $489.44 of our $500 before shipping and contingency are in place. This estimated cost accounts for approximately 80% of our anticipated parts. After discussing with out guide, it has been determined our team will need to request a budget increase, however we are choosing to allow the project to progress before requesting a formal increase request. This will allow the team to better forecast the remaining costs they will need.
Since our Design Review (which was held on 12/05/19), we performed additional research on any remaining materials that may be needed during the construction of our prototype. In addition to this, estimates were made for the shipping costs. As of 12/10/19 it is anticipated that the extra budget will be used for:
- Building a contingency plan of ~10% the total budget: $48.94
- Building budget for rework which is expected to be 10-15% of the total purchasing costs: $73.42
- Purchasing the remaining 20 percent of project materials: $97.89
- Purchasing additional materials in the case that manufacturing does not go as expected (estimated 30% of purchasing costs): $146.83
- Shipping for raw steel material: $238.18 (from "mock purchase")
- Shipping costs for remaining "non-steel" materials (Expected 15% of the purchase costs): $32.14
Based on these estimates for the remaining cost of our prototype is approximately $1,130, therefore resulting in a budget increase of approximately $630.
The live document for the bill of materials list can be viewed here.
MSD II schedule
In preparation for MSD 2 our team has developed a scheduled based on the deliverables for each week outlined in the course syllabus on the MSD1 Edge page. Dates for these activities have been tentatively scheduled for the first two weeks of MSD 2. The remainder of the weeks will be scheduled tentative to the activities that are completed in these weeks.
Below is the Gantt chart with tentative dates for the first two weeks of project progress planned in MSD 2.
Vision for Imagine RITAs we move into MSD II the project team has begun to develop a plan for what we hope our imagine exhibit to look like.
Our team will have a toilet staged and have the prototype set as in reality. Ideally our location would have access to a water source such as a hose so that the prototype could be used functionally.
At least 3 of our team members will be present to demonstrate the lifting and lowering and adjustability properties of the toilet. Team members will explain how this toilet was designed and the workings of the toilet as well as the future vision for the project.
We will discuss the social impacts and show the design steps on our posted board
IF human testing goes well the team will have a liability waiver for participants at Imagine to try out the prototype and give feedback on the design
MSD II: Project close-out
- Use this space to organize information for your review. Key elements are listed here
- All team members present and prepared to report on team and individual status.
- All team MSD deliverables are complete and uploaded, and ready to be graded.
- Guide is present and prepared to evaluate all items included in the review.
- Review should take about an hour.
Status ReviewCurrent state of the project
- Summarize actual performance vs. requirements
(include snapshot of current requirements document here,
along with a link to the live document.).
- Which requirements were unmet, and why?
- How robust is your final design?
- We were able to stay within our project's budget. Of the $500 that we were initially given, we only used $310.20 of it, leaving $189.90 left over. Had the university not closed early, we might have been able to purchase a part for the back support sub-system. However, the remaining components, raw material, and necessary hardware were purchased prior to this occurring. To view our final Bill of Materials document, click here.
- What was your customer's assessment of the work you delivered to them? Were they satisfied?
- Compare your current project plan/schedule to your
- Did the scope of your project change during MSD II?
- How and why did your schedule change during MSD II?
- What have you learned from these changes that you can apply to future projects?
- Review individual team member status.
- Did you deliver on your personal responsibilities?
- Did you use your MSD II plan effectively? Was it realistic? If not already addressed above, what did you learn from this and how can you apply it to future projects?
- Review your current risk assessment and problem solving status.
During the entirety of MSD (both 1 and 2) we were able to develop a large list of potential risks that the team had a chance of encountering. All in all, we were able to come up with 75 risks during MSD 1 and 50 risks during MSD 2, therefore bringing our grant total to 125 for the entire academic year. To view our entire list of risks, click here.
of these 125 risks, only 17 of them actually manifested themselves as problems. Of these 17, 13 of them somewhat anticipated. This means that although we didn't necessarily expect any of them to actually occur, we always knew that there was always a chance that they could happen.
The other 4 problems that we encountered were not anticipated whatsoever. All of these problems are related to the COVID-19 pandemic, which caused the university to close in the middle of March. None of our team members could have predicted that something like this would actually occur, so they were very unexpected.
Given this, the team did an excellent job with approaching these problems with grace and efficiency. We were able to close out and solve all 17 problems that we encountered by the end of the academic year. Our problem solving process during the semester was very simple. We solved each problem one at a time. We didn't try to bite off more than we could chew. Once we solved the problem, the way way that we went about solving it was documented in our problem tracking document. To view that document, click here. (Problems 1 - 13 were anticipated and the remaining 4 were not anticipated).
Deliverables Checklist and Website Status
- All documents must be uploaded to your website in advance of the Gate Review.
- The team should not use gate review time to conduct a detailed examination of specific deliverables unless related to discussion items in the status review.
- Is prototype hand-off complete, is the team's workspace cleaned up, and have all tools been returned?
Lessons learned, etc.
- Does the team have any other lessons learned that were not addressed above?
- What advice would you give to future teams?