| Project Summary | Project Information |
|---|---|
|
The LiveAbility Lab is a configurable research and
development facility in Rochester dedicated to
assessing the efficacy of assistive devices. This
facility will provide a location for a wireless
movement and force analysis system to capture and
analyze contact forces and motions associated with
individuals with movement impairments. The facility
is currently unequipped, and there is no known
prototype for this specific force and motion
detection system desired for the customer. However,
there are existing systems that do portions of what
is desired.
The goal of this project is to design a sensor system that can be used by physicians to track the progress of their patients in their home environment. This system should not harm the individual, and will not affect their gait in any way. Attachment of all subsystems will not require any modification to shoes, garments, or walking assistance devices. The subsystem will be powered by a rechargeable battery that allows for 8 hours of operation before recharging, and it will be continuously monitored using a wireless beacon system. The resulting design must be portable, waterproof, and able to communicate wirelessly with a data logging system. For an updated project description, click on the following link for the Project Readiness Package. 
|
|
Team Members
Members of the team giving their best smile!
| Member | Discipline | Role | Contact |
|---|---|---|---|
| Hrishikesh Moholkar | Computer Engineering | Lead Systems Engineer | hnm6500@rit.edu |
| Martine Bosch | Mechanical Engineer | Communications Manager | mab7263@rit.edu |
| Nick Petreikis | Microelectronic Engineer | Purchasing Manager | njp2190@rit.edu |
| Erik Brown | Biomedical Engineer | Facilitator | eab5445@rit.edu |
| Patrick Mylott | Industrial and Systems Engineer | Project Manager | pfm9673@rit.edu |
| John LeBrun | Electrical Engineer, Power Focus | Lead Power Engineer | jjl3625@rit.edu |
| Matthew Devic | Electrical Engineer | Lead Communications Engineer | mjd5569@rit.edu |
Team Values and Norms
Below is a table of our team values and norms. Team members will be evaluated on a pass/fail basis for all team values and defined expectations.
| Value | Does Not Meet Expectation | Meets Expectation |
|---|---|---|
| Participation | Team member misses group meetings often, with no effort to make up work and take on additional responsibility. When they do attend meetings, they are often quiet and do not contribute many ideas or feedback. | Team member attends as many group meetings as possible and actively participates in group discussions and decision making activities. If they do miss a meeting, they contact other team members to get brought up to speed and still take on action items from the meeting if necessary. They are clearly committed to the team and the team goal. |
| Communication | Team member ignores GroupMe messages and does not provide other team members with updates on tasks or issues they discover. Other team members are consistently unaware of individual's progress or status. | Team member responds promptly and helpfully in the GroupMe and updates other team members regularly on status of tasks. If they come across issues, they promptly alert team members of the issue and plan of action. |
| Documentation | Team member does not save a copy of their work in a shared location for other team members to access. It is unclear what progress they have made on their tasks and other team members cannot provide constructive feedback. | Team member utilizes Google Drive as the main document managing and editing platform and uploads all completed information and documents to EDGE. |
| Promptness | Team member is consistently late posting their work to Google Drive and EDGE. Other team members do not have much of a chance, if any, to review and provide feedback on document before updating to EDGE. | Team member completes all action items two days before they're due and posts relevant documents on Google Drive to give other team members a chance to provide feedback before the due date. |
(REV 1-30-2019)
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. 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.
| Project Management | Design Tools | Design Documentation | Implementation | Validation | Presentation & Dissemination |
|---|---|---|---|---|---|
|
Schedule Cost Risk Management Problem Management |
Benchmarking 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.
- Viewing the latest revision
- Node updated 2019-06-10 23:37 by eab5445