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.
All spaces are private by default. Please update the two following items so that we know how to handle your team's work after you leave campus:
| The contents of this wiki space may/may not be shared with the general public | This wiki space may/may not be shared with future RIT students and faculty working on follow-on projects |
|---|
Project Summary | Project Information |
|---|---|
Laundry Alert is a system that allows the user to check the status of washing machines and dryers at any time. This system will eliminate the need to monitor the washer and dryer in a home while waiting for the cycle to complete, which will effectively save the user’s time. Washing machines and dryers are appliances found in most homes and have become essential to our day-to-day life. Many modern washers and dryers have a notification system to let the user know when their laundry is done. However, these audible notifications are insufficient in situations where the user is not within earshot of the washer or dryer. The key goals for this project are to notify the user of an end-of-cycle state remotely so that there is no need to constantly monitor the machines. The result will be an easy-to-use device which can be installed easily on any washer or dryer without the help of an electrician and without altering the original machine wiring. The device must have a cost-effective price less than $50, and it must be compliant with all industry standards. The intellectual property of the final prototype will be assigned to the customer, Dean Eaton of Rochester Appliance, for the design to be used commercially. | Project Title: Laundry Alert Project Number: P21301 Project Family (if relevant): Start Term: Spring 2021 End Term: Fall 2021 Faculty Guide: Jennifer Indovina Primary Customer(s): Dean Eaton, Rochester Appliance Sponsor (financial support): Dean Eaton, Rochester Appliance Don't include people's email/phone # without their consent |
Team Members
(this is a good place to put a team photo if you have one)
| Member | Major | Role | Contact |
|---|---|---|---|
| Zachary O'Brien | Electrical Engineering | System Engineer | zjo5244@rit.edu |
| Marissa Shaw | Electrical Engineering | Communication, Purchasing | mls6002@rit.edu |
| Adam Palumbieri | Electrical Engineering | Facilitator | ahp4086@rit.edu |
| Joshua Nagy | Electrical Engineering | Project Manager, (Clamp) | 585-730-9998 |
| Thomas Endress | Electrical Engineering | System Engineer | tae6635@rit.edu |
| Jonathan Kabamba | Electrical Engineering | Project Manager, (In-line) | jik8347@rit.edu |
Information
Content Guidelines: Use these links below to guide you in populating your website. A few points to consider:
- Be aware of any information that your sponsor might not want publicly available. If you post this information to your wiki, you should keep your site private.
- Do not post any files on your site that are not yours, unless you are certain that they are in the public domain or you have received permission to post them. Examples of files that you should avoid posting are copies of published papers, standards documents, textbook chapters/excerpts, or copyrighted images. If you have received a .pdf of a paper through Interlibrary Loan, or purchased an ASTM or ISO standard, you may post it in the private directory, where only your team and guide will have access to it.
- If you are including contact information for people that would otherwise not be publicly available, make sure you have their permission. For example, your faculty advisor's email address and office phone number are already publicly available on the KGCOE website, and is fine to post. However, if he or she has provided a cell phone number to the team, that is most likely not public information and should not be posted without explicit permission.
- Remove all template text once you've read it and taken the appropriate action.
Work Breakdown: By Phase
MSD I & II | MSD I | MSD II |
|---|---|---|
Integrated System Build & Test Customer Handoff & Final Project Documentation (Verification & Validation) |
Work Breakdown: By Topic
Use this space to link to live/final documents throughout the project - this can be a convenient way to find individual documents without having to navigate the phase-by-phase pages. Your team should customize this as-needed, with input from your guide and customer. The example below will address most of what most teams need to capture. If you opt not to link to these items on your homepage, delete this block and the corresponding pages.
Project Management | Design Tools | Design Documentation | Implementation | Validation | Presentation & Dissemination |
|---|---|---|---|---|---|
Cost Problem Management Communication | Functional Decomposition Morphological Chart Pugh Concept Selection | BOM Mechanical Drawings Electrical Schematics Software Diagrams Facility Layout Manuals | Mockups Test Fixtures Prototyping Test Plans | Analysis Results Simulations Test Results | Design Review Documents Technical Paper Poster Imagine RIT Exhibit |
Acknowledgements
- Be sure to include any relevant sponsor acknowledgement throughout your site.
- Acknowledge any other support you have received from people at RIT or elsewhere.
Ajouter un commentaire