P13061: Periodontal Measurement Test System
/public/

Planning & Execution

Table of Contents

Project Summary

For an updated project description, click on the following link for the Project Readiness Package.

Periodontal disease affects over 50% of adults worldwide and is the leading cause of tooth loss. Currently, the presence and extent of periodontal disease are measured using an invasive, metal probe as seen in Figure 1 on the home page. This process is time consuming, inconsistent and painful. Therefore, Perio Alert is in the development stages as an attempt to make the sulcus measurement process more reliable, less painful and simpler. This idea uses an ultrasonic probe to perform the sulcus depth measurement required to determine the presence and extent of periodontal disease.

This project encompasses developing a method for testing an ultrasonic probe while performing the sulcus depth measurement. A test fixture must be developed to hold and maneuver the probe. The probe must be maneuvered accurately and repeatably to ensure the measurements are representative of the sulcus. A "phantom" tooth must also be developed to perform sulcus depth measurements on. This requires that a fixture be designed to hold and possibly maneuver the tooth being measured. This fixture should also move accurately and repeatably for the same reasoning of that associated with the probe fixture. Lastly, a system/program must be developed to serve as a user interface for the measurement technique. This system should be simple yet effective, leaving little room for user error. It should also provide meaningful feedback so the sulcus depth measurement can be easily interpreted and explained.

The importance of the phantom tooth lies in its ability to behave as a human tooth. The ultrasonic properties of materials used must be similar to those of a human tooth to facilitate meaningful results and prove out the process being tested; herein lies the difficulty of the project.

Customer Needs

The customer needs chart shown below was provided by customer. These needs will be evaluated to develop the specifications for the project. They will also be incorporated into the system design to ensure that the end product satisfies the deliverables the customer requested.

Customer Needs

Customer Needs

Specifications

Specs

Specs

Team Norms & Values

Code of Ethics

The Code of Ethics was developed by the team members at the initial team meeting. This document lays out the expectations team members hold for one another. It will help keep the team focused and on track while ensuring that everyone is pulling their weight and moving the team toward the end goal of delivering a solid, successful project. The Code of Ethics also discusses methods for communication, documentation, conflict management, etc. It is important to agree upon the techniques to be used early in the project so the expectations are set and all team members are on the same page.

Code of Ethics

Team Roles

Aside from the positions of Project Manager, Lead Engineer and Team Facilitator, roles were suggested based upon the requirements of the project. These roles include Electrical Engineers 1 & 2 and Mechanical Engineers 1-4. The project encompasses many different areas, as seen in the descriptions listed below. These role suggestions were provided by the team guide in order to help the team understand the scope of the project and assess the areas where technical skills will be necessary. The team chose to select a lead for each role, thus agreeing that the lead will be the technical "expert" responsible for tasks associated with their role. The role assignments are listed on the home page.

Electrical Engineer 1 & 2: Analysis of requirements and purchasing of motors. Implementation of motor control, Labview programming and DAQ to supply and measure user defined current or voltage profiles. (Core skills: motor control, instrumentation and advanced Labview programming and DAQ)

Mechanical Engineer 1: Analysis and lead physical design of fixture to hold ultrasound probe. CAD drawing. Material choices and parts. Machine work and taking the lead in assembly with other team members. (Core skills: 3D CAD and machining, mechanical design and materials)

Mechanical Engineer 2: Analysis and lead physical design of dental fixture to hold bone, tooth and gum proxies. CAD drawing. Material choices and parts. Machine work and taking the lead in assembly with other team members. (Core skills: 3D CAD and machining, mechanical design and materials)

Mechanical Engineer 3: Research non-biomaterials for use as gum, tooth and bone proxy within test fixture. Material choices. (Core skills: material properties with respect to wave propagation)

Mechanical Engineer 4: Assist with ME 1, ME 2 and ME 3

Work Breakdown Structure

The Work Breakdown Structure (WBS) is used to lay out the generic tasks that must be completed and any pertinent information related to each task. It serves as a basic representation of the scope of the project and the items that are necessary for completion of a successful project.

Work Breakdown Structure

Schedules

MSD I Schedule

The schedule shown below represents an aggressive approach to completing the system design by the end of MSD I. The tasks are listed, as well as start dates and durations. Dependencies are shown to indicate when beginning a task hinges upon the completion of a previous task. It is important to note these dependencies so the critical path can be determined. The critical path represents any tasks that are holding the project up, not allowing progress to be made until they are completed. It is the goal of each team member to remain off the critical path, as these tasks are road blocks that should be completed as soon as possible. The column entitled "Resource Names" represents the team member responsible for the task listed. This helps to ensure that everyone knows who is taking care of a certain task and allows team members to see when they are on the critical path.




MSD I Schedule - Microsoft Project 2010

MSD II Schedule




MSD II Schedule - Microsoft Project 2010


MSD II Schedule - Microsoft Project 2010

Risk Assessment

The risk assessment shown below provides details about the areas where the team recognizes risks. Each risk is assigned an ID for ease of reference. The cause of the risk is found as well as a predicted effect, should the risk materialize. A scale of 1-3 (1 being low, 3 being high) is then used to assess the likelihood and severity of each risk. The likelihood represents the probability that the risk will become a problem. The severity indicates the impact each risk would have on project timeline, budget and success. These two values are then multiplied and the resulting value is "importance". This importance allows the team to recognize the risks that will have the largest impact on the project. The range of the importance is 1-9 (1 being low, 9 being high). Risks with an importance of 5 or above appear in red to remind the team that it needs to actively work to mitigate these risks. The chart is organized to place the risks in descending order of importance. The column entitled "Risk Mitigation" contains ways in which the team can lower the possibility of a risk to occur or the effect of the risk. The column named "Plan B" is the action that will be taken if the risk materializes and proves to be detrimental to the project. The Plan B will be implemented if the trigger date passes and the risk has yet to be removed or has become too severe to allow for successful, timely completion of the project. The owner of each risk is responsible for heading up the risk mitigation efforts to ensure that the risk will not become a problem.

Risk items that are highlighted in green have been effectively dissolved, thus removing their bearing on the successful completion of the project.

Risk Management

MSD I Meeting Minutes

November 30, 2012

November 30, 2012

Topics

December 7, 2012

December 7, 2012

Topics

December 7, 2012 - Customer Call

December 7, 2012

Topics

December 10, 2012

December 10, 2012

Topics:

December 14, 2012

December 14, 2012

Topics:

December 18, 2012

December 18, 2012

Topics:

December 19, 2012

December 19, 2012

Topics:

December 21, 2013: Preliminary System Design Review

December 21, 2012

Notes & action items from Preliminary System Design Review

January 8, 2013

January 8, 2013

Topics:

January 10, 2013

January 10, 2013

Topics:

January 11, 2013: System Design Review

January 11, 2013

Notes & action items from System Design Review

January 15, 2013

January 15, 2013

Topics:

January 18, 2013

January 18, 2013

Topics:

January 18, 2013: Dr. Hopkins (RIT)

Dr. Hopkins, January 18, 2013

Topics:

January 22, 2013

January 22, 2013

Topics:

January 23, 2013: Dr. Phillips (RIT)

Dr. Phillips, January 23, 2013

Topics:

January 25, 2013

January 25, 2013

Topics:

January 30, 2013

January 30, 2013

Topics:

February 1, 2013: Preliminary Detailed Design Review

Preliminary Detailed Design Review

Team was supposed to have a preliminary detailed design review. The guide was not able to attend so the team held a conference call with the guide to review the presentation. Comments can be found in the meeting minutes above.

February 1, 2013: Dr. Caton (U of R)

Dr. Caton, February 1, 2013

Topics:

February 4, 2013: Dr. Helguera (RIT)

Dr. Helguera, February 4, 2013

Topics:

Note: Dr. Helguera cannot attend the detailed design review scheduled for Friday, 2/8. However, she would like a copy of the presentation and work being completed to provide further recommendations and insight. Dr. Helguera also loaned a coupling agent to the team.

February 6, 2013

February 6, 2013

Topics:

February 8, 2013: Detailed Design Review

Detailed Design Review

The detailed design review presentation can be found on the Detailed Design page. Overall, the detailed design review went rather well. The general design was accepted and attendees made recommendations based upon further questioning/analysis. The team met right after the review to discuss the suggestions made and their feasibility. Topics of discussion and the suggestions provided can be found in the meeting minutes above.

February 11, 2013

February 11, 2013

Topics:

February 15, 2013

February 15, 2013

Topics:

MSD II Meeting Minutes

March 6, 2013

March 6, 2013

Topics:

March 8, 2013

March 8, 2013

Topics:

March 14, 2013

March 14, 2013

Topics:

March 21, 2013

March 21, 2013

Topics:

March 24, 2013

March 24, 2013

Topics:

March 28, 2013

March 28, 2013

Topics:

April 1, 2013

April 1, 2013

Topics:

April 4, 2013

April 4, 2013

Topics:

April 11, 2013

April 11, 2013

Topics:

April 15, 2013

April 15, 2013

Topics:

April 18, 2013

April 18, 2013

Topics:

April 25, 2013

April 25, 2013

Topics:

April 29, 2013

April 29, 2013

Topics:

May 2, 2013

May 2, 2013

Topics:

May 3, 2013

May 3, 2013

Topics:

Home | Systems Design | Detailed Design | Build, Test, Document | Project Review | Photo Gallery