| Risk ID | Risk | Type | Likelihood | Consequence | Risk Level | Mitigation Plan |
|---|---|---|---|---|---|---|
| R1 | Platform Breakdown | Cost Schedule | 4 | 3 | 12 | -Manufacture and/or order backup vehicle components - Perform extensive IP and durability testing on the electronics enclosure - Develop and implement a testing checklist |
| R2 | Controls are Infeasible | Schedule Technical | 2 | 4 | 8 | - Build in safety margin in motion planning - Separate controls computation |
| R3 | Vehicle Dynamics are Inaccurate | Schedule Technical | 4 | 3 | 12 | - Build custom model in Simulation - Use empirical data collected by platform to build models |
| R4 | Terrain Comprehension is Inaccurate | Schedule Technical | 3 | 4 | 12 | - Use multiple algorithms and sensors for redundancy - Create artificial distinctions between puddles and dry areas |
| R5 | Insufficient Time for Testing | Programmatic Schedule | 5 | 4 | 20 | - Split bulk testing into unit testing of each subsystem - Descope project to allow for more testing hours |
| R6 | No Suitable Demo Location | Programmatic Schedule | 2 | 5 | 10 | - Have backup test locations with qualities similar to ideal test location |
| R7 | Overbudget | Cost | 3 | 4 | 12 | - Exercise caution before purchasing items, and check MRSD inventory to save funds - Speak with advisors to discuss if they may possess any of the needed items |
| R8 | Real-time Computation Unachievable | Programmatic | 4 | 4 | 16 | - Purchase or source a more powerful unit for onboard computing - Perform bi-weekly code reviews to ensure software efficiency |
| R9 | Onboard Components Exceed Vehicle Capacity | Technical | 3 | 4 | 12 | - Optimize electronics enclosure and other manufactured components to minimize weight |
| R10 | Cannot Complete Full System | Programmatic | 1 | 4 | 4 | - Have consistent documentation and backup plans |
| R11 | Inability to Demo | Programmatic | 3 | 3 | 9 | - Use videos recorded from visits to demo location |
| R12 | Cannot Procure Plaftorm Components | Technical | 2 | 4 | 8 | - Source components early to allow for changes |
| R13 | Work Remains Remote | Schedule | 3 | 4 | 12 | - Note where we could show capabilities remotely |
| R14 | PDB Malfunctions | Technical | 2 | 4 | 8 | - Check connections on board regularly before supplying power |
