RIT will permanently shut down the RIT Wiki (Confluence wiki) on February 2, 2024. Review the Wiki Shut Down Overview for information on alternative tools, exporting content from the wiki, and other FAQs.
Intellectual Property Considerations
The ConcRIT 2 team has come to a preliminary agreement that we would like to not leave any IP generated in the public domain. However, we believe it is right that we do allow RIT and our customer, Sarah Brownwell, free ability to utilize the IP generated so long as it is used to fulfill student and humanitarian needs. All other uses must be approved by a majority vote of the team and any compensation associated with licensing of IP is to be shared equally among all team members.
Team Setup
| Name | Title |
|---|---|
| Meghan Britt | Project Manager |
| Derek Gagnon | System Engineer |
| Anthony Ambrose | Communicator |
| Tyler Swidler | Facilitator |
| Nicola Gnecca | Purchaser |
Team Values and Norms
At ConcRIT 2.0, we shape the future and improve the world through creativity and innovation. As an engaged, intellectually curious, and socially conscious community, we leverage the power of technology, the arts, and design for the greater good.
The values that we will work with are:
Innovation
Socially conscious community
Shape the future
Honesty
Create value-added work
To work towards these goals, we will get work done on time and complete it to the best of our ability. If needed, we will ask for help, and if we have any setbacks, we will communicate it with the team. We each will take personal responsibility for the success of the team and work to mitigate conflict by communicating early, often, and openly. To effectively communicate we will use the "what is in the way" portion of the daily stand ups. If someone is causing conflict, we will be direct with them and try to find out what resources they need.
Project Plans & Schedules
Our Fall semester schedule can be found here. Note that file must be downloaded in order to be viewed properly.
Risk Assessment
| Team #: | P21652 | Team Name: | ConcRIT 2 | ||||||
| Date: | 9/2/20 17:17 | Document Owner: | Derek Gagnon | ||||||
| Revision #: | 1 | ||||||||
| ID | Category | Risk Item | Effect | Cause | Likelihood | Severity | Importance | Action to Minimize Risk | Owner |
| What type of risk is this? | Describe the risk briefly | What is the effect on any or all of the project deliverables if the cause actually happens? | What are the possible cause(s) of this risk? | L | S | L*S | What action(s) will you take (and by when) to prevent, reduce the impact of, and/or transfer the risk of this occurring? | Who is responsible for following through on mitigation? | |
| 1 | Safety | COVID-19 | All work would go virtual and Students may have limited access to RIT facilities | Students not following safety guidelines | 1 | 1 | 1 | Follow CDC, NYS, and RIT Safety guidelines | Everyone |
| 2 | Safety | Electrical Fire from Power Supply | Damaged electrical requiring new purchase. Possible bodily harm | Poor storage, damage in travel | 1 | 9 | 9 | Verifying integrity of power supply | Derek |
| 3 | Resource | Concrete Additives pricing | Limit on available mixture testing | Current Demand and Economic state | 1 | 1 | 1 | Research additives and check pricing | Nicola |
| 4 | Technical | Flow setting in extruder | Loss of augur, extruder | Not cleaning extruder, larger extruder reservoir | 1 | 3 | 3 | Checking extrusion rate, looking for lack of flow | Tyler |
| 5 | Technical | Flow setting in reservoir | Cleaning of reservoir | Made concrete not being cleaned out | 1 | 3 | 3 | Cleaning out after every print | Tyler |
| 6 | Social | Unable to print desired structures | Lack of practicality of Printer | Unique designs, lack of ability | 3 | 1 | 3 | Checking print capability to current desired structures | Meghan |
| 7 | Resource | Concrete mixture gets clogged in extruder | The print would be interrupted and accelerated wear and stress might be put on the extruder causing components to fail | Concrete mixture too thick, too large of aggregate, additives cause too much friction | 3 | 3 | 9 | Study amount of force to push different concrete mixtures through a nozzle | Tyler |
| 9 | Environmental | Hopper system leaks concrete | This could cause concrete to end up spilling in the room the printer is located damaging the room and causing inconveniences to staff and students | Hopper failure, not tight enough seals between components, too thin of a concrete mixture | 1 | 3 | 3 | Ensure tight seals beteen parts, design platform so if leaks occur they are not on a permanent surface | Nicola |
| 10 | Resource | Concrete bottom layers deform too much once printed on top of | Accuracy requirement not met, vertical stucture may collapse | Concrete not left to cure enough, concrete mixture too thin | 2 | 2 | 4 | Test amounts of pressure that fresh concret can take when just printed and adjust print speed accordingly | Tyler |
| 11 | Social | Concrete printer makes significant amounts of noise while operating | Disturb other students and staff working in the vicinity of the printer, cause discomfort to the user | Steppers motors and extruder operating loudly | 1 | 1 | 1 | Insulate motors and ensure no undue strain is put on them | Nicola |
| 12 | Resource | Not enough funding | Can't complete the project due to the monetary restraints | Overspending or a budget that is too small | 1 | 3 | 3 | Spend our money wisely and design with the budgetary restraints in mind. | Nicola |
| 13 | Technical | Printer produces non-homogeneous printed material which can fail randomly | Final prints could fail randomly due to inconsistent material properties | An inconsistent extruder or non homogeneous cement mixture | 2 | 2 | 4 | Fine tune our cement mixture and nozzle design. Run materials testing on multiple samples of the printed concrete. | Nicola |
| 14 | Technical/Safety | Managing the elevated weight of the cement mixture (120 lbs) | Possible injury risk and destruction of the machine if the weight falls | Misuse of the printer by teams. A printer that doesn't account for the added weight of the cement mixture. | 2 | 3 | 6 | Design a weight management system that is safe and has a high factor of safety. | Derek |
| 15 | Technical | 3D printed auger could fail mid print or have a short life-cycle | Complete tear down of extruder, replacement of auger, and a failed print | Material used in auger | 2 | 2 | 4 | Use different material for the auger | Derek |
| 16 | Technical | Current design does not meet our requirements | Need to restart from the beginning and may need to replace parts | Current design doesn't hit our updated engineering requirements. | 1 | 2 | 2 | Design with the previous teams work in mind but also be critical of their work. | Everyone |
| 17 | Resource | No Chem-E to assist with creating a solution | May slow process for development and testing of the concrete | No Chemical Engineer on the team at this time | 3 | 1 | 3 | Team will be actively researching combinations, possibly recruit co-op students | Tyler |
| 18 | Technical | End product not being cleaned properly | May break the auger/extruder | Poor cleaning instruction | 2 | 3 | 6 | When writing User Guide include clear clean up instructions | Meghan |
| 19 | Resource | Subsystems are interdependent with timelines | May cause delays to each subsystem | Falling behind on any subsystem that others are dependent on | 2 | 2 | 4 | Stick to our schedule. If we fall behind we will increase hours that week towards the project. | Everyone |
| 20 | Environment | End user putting wet concrete down the drain | Would damage drain/pipes | Unclear clean up instructions | 2 | 1 | 2 | When writing User Guide include clear clean up instructions | Meghan |
| 21 | Technical/Safety | Reservoir leaks water onto rest of systems/motors | Electrical systems will be destroyed and will need to be replaced | Poor reservoir design | 1 | 3 | 3 | Put extra time into designing reservoir and fail-safes | Tyler |
| 23 | Technical | Not proper rated parts - overdrawing current from power supply | Fuse blown and possible damage to other circuitry | Not fully checking the specs of each electrical component included | 2 | 2 | 4 | Check with other electrical engineers on the design prior to building | Anthony |
| 24 | Technical | Electrical subsystems aren't compatible with software/other subsystems | The printer will not function | Poor electrical subsystem design/improper reviewing of design | 2 | 3 | 6 | Check with other electrical engineers on the design prior to building | Anthony |
| 25 | Resource | Writing and debugging code | May cause major delays | Only one member on the team knows coding well | 2 | 3 | 6 | Anthony will be a resource | Anthony |
Other Team Resources
- Planned meeting space - MSD Design Center, Zoom
- Planned build & test space - TBD
- Storage area for parts - Cubicle 2 in the MSD space
Meeting Minutes, Notes, & Actions
LINK to Meeting Minutes and Interview
Peer Reviews
Peer reviews will be conducted after each design review. The first one is to be completed before Tuesday September 8th, 2020 following the Problem Definition Phase Review.
Communication
- Customer Point of Contact: Anthony Ambrose (axa6841@rit.edu)
- Preferred method of communication: Email or Slack.
- Expected frequency of communication: A reply within 24 hours.
- Entire team should be cc on relevant customer emails (emails on Project Management page)
- Relevant documentation is shared with the customer through the Confluence wiki page, or through email.
Project Reviews
Preparation, notes and actions, etc. Refer to Gate Review page, as well.