MSD Project Risk Assessment Template s1
MSD Project Risk Assessment Template
ID # / Component / Functional Risk / Effect / Cause / Likelihood / Severity / Importance / Action to Minimize Risk / OwnerComponent / 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 / What action(s) will you take (and by when) to prevent, reduce the impact of, or transfer the risk of this occurring? / Who is responsible for following through on mitigation?
1 / Laser X-axis Motor / Does not move laser / Laser does not move to the next measurement cross section / Motor not strong enough / 1 / 3 / 3 / Perform analysis on the torque needed to move the gantry
Debris in track / 2 / 3 / 6 / Make a notification to alert that the cover is not on when not in use and in the instructions have a preventative maintenance plan
2 / Laser Y-axis Motors / Does not move laser / Cross section measurement not taken / Motor not strong enough or debris / 1 / 3 / 3 / View actions from ID #1
Do not move in-sync / Gantry jams & laser doesn’t measure cross section / Misalignment, bump to gantry / 2 / 3 / 6 / Instead of using 2 motors (one for either end of gantry) to move in the y-axis, use only one
Do not move in-sync / Laser point inaccurate / Misalignment, bump to gantry / 2 / 3 / 6 / Instead of using 2 motors (one for either end of gantry) to move in the y-axis, use only one
3 / Laser Z-axis Controller / Laser not at proper height / Laser inaccurate/does not take measurements / User / 1.5 / 2 / 3 / Have the system check to make sure proper height has been set
4 / Die Fixture / Not proper size or does not get to proper position / Inaccurate data points measured / Not in fixture / 1 / 3 / 3 / Make fixture so that the die can only fit one way and make operator move fixture on track by means of not pushing directly on the die, possible locking mechanism for the die
User selects wrong fixture / 1 / 3 / 3 / Training, possibly some kind of visual aid
Fixture Tracks Jam / 1 / 3 / 3 / Include preventative maintenance to the directions, make tracks go throw deeper underneat
ID # / Component / Functional Risk / Effect / Cause / Likelihood / Severity / Importance / Action to Minimize Risk / Owner
5 / Laser / Does not take measurements / No data collected / Software, interface, not turned on / 1 / 3 / 3 / In depth research of quality laser and have a preventative maintenance plan in place
Lens gets dirty / No data collected / Unit not covered / 2 / 3 / 6 / Research into proper air-curtains recommended for the environment and the laser, also preventative maintenance
6 / Frame / Does not hold together / Inoperable product / Not properly assembled, not torque / 1 / 3 / 3 / Detailed instructions with everything that is essential to how it should be assembled
7 / Directions /Manual / Does not accurately portray how to use system / Damage to system from misuse / Not written properly / 1 / 2 / 2 / Perform usability study and make sure that the directions make sense to a variety of users
System does not get used / Not written properly / 1 / 2 / 2 / Perform usability study and make sure that the directions make sense to a variety of users
8 / Housing / Fails to protect the unit from foreign objects / Damage / Projectiles, debris, etc / 1 / 1.5 / 1.5 / Make alert to make sure unit is covered when not in use
User sets dies on top / 3 / 2 / 6 / Label the protective case appropriately, make the surface not flat
10 / Fixture Tracks / Does not move fixture / Die cannot be moved into place / Debris or damage / 2 / 2 / 4 / Have a preventative maintenance plan and use durable materials
11 / Software / LabView VI fails / System cannot be controlled / Computer error, something missed in programming / 1 / 3 / 3 / Have backup files, make sure to perform extensive testing on a variety of scenarios
Database fails / System has no data recorded / Computer error, hard drive failure/full / 1 / 2 / 2 / Have backup files, set a system for how long to record data
Software compares wrong specifications / False positive or false negative / User error / 2 / 3 / 6 / Have a verification system for which die is being measured
12 / Motor Interface / Is not compatible or fails / Laser can’t be moved / Purchasing decision / 1 / 2 / 2 / Perform appropriate research on the motors before purchase
ID # / Component / Functional Risk / Effect / Cause / Likelihood / Severity / Importance / Action to Minimize Risk / Owner
13 / Laser Interface / Is not compatible or fails / Laser can’t take measurements / Shipping damage, operator damage / 1 / 3 / 3 / Perform appropriate research on the laser before purchase
14 / LEDs / Fail to display go or no go / User doesn’t know if die passes / User error, hardware error, LED burns out / 1 / 1 / 1 / Have a redundancy built in for go or no go result
15 / User Interface / Is to confusing or doesn’t include appropriate controls / Damage from misuse/ system can’t be used / Programming, human factors / 1 / 1 / 1 / Perform usability studies with a variety of subjects
16 / Parts / Arrive Late / Project is not delivered on time / Supplier, machining / 1 / 2 / 2 / Make sure to fully communicate with suppliers, if machining parts get the plans in before they are needed, possibility of using outside machine shop
17 / Team Members / Do not work well together / Project is stalled / Member conflict / 1 / 2 / 2 / Hold weekly meetings and make sure that everyone agrees with team values and norms.
Members unable to meet due / Project is stalled, lack of skill set in the other students / interviews/projects/etc / 1 / 2 / 2 / Making sure that all members are fully familiar with the system and how to perform the different functions will be able to minimize the risk of project stalling
18 / Air Curtain / Flow stops / Laser lens gets dirty / Clog or failure / 1 / 2 / 2 / Preventative maintenance
Likelihood scale / Severity scale
1 - This cause is unlikely to happen / 1 - The impact on the project is very minor. We will still meet deliverables on time and within budget, but it will cause extra work
2 - This cause could conceivably happen / 2 - The impact on the project is noticeable. We will deliver reduced functionality, go over budget, or fail to meet some of our Engineering Specifications.
3 - This cause is very likely to happen / 3 - The impact on the project is severe. We will not be able to deliver, or what we deliver will not meet the customer's needs.
“Importance Score” (Likelihood x Severity) – use this to guide your preference for a risk management strategy
Prevent / Action will be taken to prevent the cause(s) from occurring in the first place.
Reduce / Action will be taken to reduce the likelihood of the cause and/or the severity of the effect on the project, should the cause occur
Transfer / Action will be taken to transfer the risk to something else. Insurance is an example of this. You purchase an insurance policy that contractually binds an insurance company to pay for your loss in the event of accident. This transfers the financial consequences of the accident to someone else. Your car is still a wreck, of course.
Accept / Low importance risks may not justify any action at all. If they happen, you simply accept the consequences.