P20414: Indoor Dry Toilet Base
/public/

Gate Reviews

Table of Contents

Your team will hold a gate review with your guide at the end of each semester. This page should document any information needed for the review, as well as outcomes.

MSD I: Readiness to move to Build & Test

Team's Self Critique.

Expectations

Status Review

Current state of the project

The scope of the project has changed slightly since the beginning of the project. In the beginning of MSD 1, the team thought the focus was on improving the design of the toilet and the diverter. However the scope should actually have been on the process and manufacturing of the toilet while solving the critical issue of male clearance with the diverter.

Our schedule has changed due to cost infeasibility that occurred during the project. Once we were completing feasibility documents and started talking to experts about whether or not it was possible to use liquid rubber to create the interior and exterior molds of the life-sized toilet, it became clear to the team that the current team budget would not suffice if the team decided to continue in that direction. Our schedule also changed due to learning about risks and how projects actually run. The team was too ambitious at the start and had scheduled to finish a life size prototype by the end of the semester. However with more experience and actually working on the project, the scheduling was redone to take into consideration risks and more feasible actions that could be finished.

The team learned that it is very important to test for feasibility of a certain material or process before continuing and making a big decision that will largely affect the project. This big change could be pertaining to the budget or pertaining to a main process of how something will get done within the project. It is important that all team members are in the loop so they know why these big decisions are being made and how it will affect the outcome of the project.

All members of the team were too optimistic about their indiviudal responsibilities. No one expected for the risks to delay the schedule as much as it did. By this time, the team had hoped to be done with the life sized prototype. However, as the semester went on everyone on the team became more realistic and everyone was able to complete their responsibilities The difference between the first 3 week plans to the last is drastic.

The MSD 1 plan was not effectively used in the beginning. The plan was not realistic. The team and the PM had to take a step back and create a schedule that was realistic, allowed time for risk delays, and still complete the project goals. The MSD 2 plan has a lot more time for tasks, especially now that the project has become a lot more physical and hands on. This will lead to a more feasible schedule and less delays.

The team has not closed out on our more important risks. The most important risks can be closed out when the we are finalized with our prototype. They deal with the design and since we have not poured the concrete we are still not sure if we can go with the design. This will be figured out in the first 2 weeks of MSD2.

All risks have remediation plans and owners to take charge of if they occur.

One of a major risks that was not even predicted was not being able to access designable files from the previous team. The team was told that the files would be accessable and accessible since everything was done on Fusion 360. However when designing the toilet manufacturing process, this was not a case. Reaching out to graduated members of the previous project did not result in a response. The meant Patrick had to remake all the design files. This led to delays in creating the files that was not in the schedule.

Risks have been added and removed throughout the different phases. For example, all the rubber coating mix risks were removed when it was determined that this was not the direction the team was headed in. As a team we learned we really need to focus more on risks and risk management after the file delay occurred. This was a risk that no one on the team had even considered, just because the team was told that the files were there.

Review your team's MSD II schedule (if not done during DDR)

This is the general idea of what the team expects to accomplish in the next semester. The final step for this semester will be pouring the concrete. This will allow us to see what direction and what the first two weeks of MSD2 will look like.

General to do list for MSD2

General to do list for MSD2

Here is a Gantt chart for a possible schedule for next semester. This schedule starts with reviewing the results from this semester and then figuring out our next course of direction, pending pass/fail from current design.

Gantt File.

Deliverables Checklist and Website Status

MSD II: Project close-out

Expectations

Status Review

Current state of the project

We were unable to find out the actual performance of the toilet due to the campus closing down, leading us to unable to physically test our toilet. Here is a our Actual Performance vs. Requirements document that outlines all the team's ERs and CRs with explanations.

Design vs Requirements PDF

Most of our requirements will be met based on the testing that we were able to do. There were some requirements that were not able to be tested however, the team has high confidence that they would meet the requirements set.

Our final design is complete and ready for another team to physically start building and performing the test plans that we had set.

Yes. Our project budget was met. We initially had a budget of $1500 and our team spent around $250 on all materials for the design and for the future building of the toilet.

The customer was generally content with the work that was done over the course of the project. There was a lot of effort that went towards creating the prototype that did not go unrecognized by the customer.

The base scope of manufacturing a dry toilet did not change throughout MSD 2.

Our schedule changed due to us switching from a silicone mold to one more affordable. Then with the campus shutting down, the schedule changed completely.

We learned to always have a Plan-B in case things go wrong. We also learned there will be things that completely derail the project.

The team all delivered on their personal responsibilities. The roles were really set during MSD 2 where work was split up instead of collaborating with the entire group. All tasks were completed in the end.

Our plan was being followed effectively until the campus closed down. It was realistic with the toilet manufacturing being set and a realistic timeline being set for after spring break. This took some practice where the team was too ambitous during MSD 1 but improved in the second part of MSD.

Yes, all our risks were closed down for the this semester.

The biggest risk that we did not anticipate was the campus closing down to COVID-19. We did not think something this major could happen and were more concerned with the project risks.

Besides the campus closing down, we did not get to see if any of the project risks would have happened due to us starting the build after the spring break.

Our problem solving process improved. We had backup plans in case things would have went wrong and when problems occurred, we figured them out much quicker. For example, the toilet window was found out in less than a week after consulting with Mike.

Deliverables Checklist and Website Status

All the documentshave be handed off and uploaded on Edge as well as the materials we had. They were all listed for pickup in the MSD file. Lessons learned, etc.

If we had any advice to give to future teams, it would be to make sure to resolve any potential problems as early in the design process as you possibly can. Once a team begins to make progress towards creating a prototype, the momentum I already there and the team will not want to go back to the drawing board to redesign anything.


Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation