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.
Document Owner: Jeffrey Seamon
Date Updated: 9/23/2020
Date
Wednesday 9/9/2020 - 12:00 to 12:45 pm - Zoom Meeting
Pre-Read
Team: 21363 Automated Player Piano V
The automated player piano is a continuation of a multi-year effort to retrofit an existing piano with a device which will allow the piano to be played completely autonomously or as a compliment to a human pianist. Ultimately, it could be used by people who have suffered hand injuries to (re)learn how to play the piano and as a practicing tool for people to learn new techniques. The piano's functionality must not be hindered such that the piano could still be played without interference from the device. Currently, there exists a device that is capable of playing the piano however this device is in a state of disrepair due to limitations caused by the COVID-19 pandemic.
The goals for this project are to realize the scope of the previous team's work, complete unfinished features, and continue with new features determined by the stakeholders. The aforementioned features that are set as the goals for production are to complete the unfinished construction of the device, develop a system to introduce a new layer of dynamics by automating the sustain pedal, and to continue development on a feedback system. The constraints that will effect the development of these desired features include working within the bounds of the previous team's scope, ensuring that the piano itself is not damaged or augmented in a way that normal operation will be hindered, enabling different modes of play (full autonomous, half autonomy-half player, and full player control), and the final constraint is to have a fully operational system of song selection and playback.
Over the course of this review we will be presenting the topics stated in the agenda directly from our teams wiki page and then subsequently addressing any questions you may have. Listed here is the link to the problem definition section of the wiki page for your reference:
https://wiki.rit.edu/display/P21363/Problem+Definition
Attendees
- Nick Besley
- David Anthony
- Josiah Martuscello
- Steven Petrick
- Jeffrey Seamon
- Jerry Adamski (Guide)
Ron Dufort (Customer)
Goals
- Inform Customer (Ron) and Guide (Jerry) of our understanding of the problem.
- Discuss Use Case Scenarios
- Lay out Customer and Engineering Requirements
- Show how CRs and ERs mesh for House of Quality
- Discuss potential issues and proposed solutions
- Show our tentative schedule
- Discuss next steps and answer and outstanding questions
Agenda and discussion notes
| Time | Item | Who | Notes |
|---|---|---|---|
| 3 min | Introduce Team and Project | Steven Petrick | N/A |
| 3 min | States of the Piano & Constraints | Steven Petrick | Physical constraints: At least 6 ft b/w people, if closer for more than 10 minutes face shields are required Keep these constraints in mind while scheduling Look for existing linear actuator components |
| 3 min | Goals & Deliverables | David Anthony | N/A |
3 min | Stakeholders | David Anthony | N/A |
| 4 min | Potential/Desired Use Scenarios | Jeffrey Seamon | N/A |
| 4 min | Customer Requirements | Jeffrey Seamon | Relax "Piano cannot be permanently altered" constraint (was High, now Medium) Gain Approval from Ron |
| 4 min | Engineering Requirements | Josiah Martuscelo | Gain input from Ron |
| 4 min | House of Quality | Josiah Martuscelo | N/A |
| 3 min | Issues and Solutions | Nick Besley | N/A |
| 4 min | Scheduling | Nick Besley | Make sure to involve time for testing: Will Test in Phase 3, Make plans in Phase 2 Make sure we're comfortable with what exists Testing earlier b/c its a mature project |
| 10 min | Thank You & Questions | Nick Besley | Follow up with all attendees after meeting We add value by designing and figuring out how to do it Provide items for customer approval before meeting if possible |
Presentation
The following link leads to the presentation given during the Problem Definition Review: Problem Definition Review Presentation. A PDF version is available here.
Issues Raised
- Physical constraints while in the lab
- Stagger work times, follow protocols
- Make sure time for testing is planned
- We'll keep that in mind, plan testing during Phase 2, actually test in Phase 3
- Provide items for customer approval before meeting if possible
- Will do so going forward
Decisions Made
- Conditional Approval is given by Customer to proceed to Phase 2: System Level Design
- Pending review of CRs, ERs, presentation by Ron
- "Piano cannot be permanently altered" constraint relaxed
Action items
- Team will complete peer evaluations.
- Ron will give approval on CRs, input on ERs and presentation by Friday 9/11.
Actions Taken (per customer feedback 9/23/20):
- Added CR 2 (others moved down)
- Updated ER 3 and 11
- Added ER 15 and 16