<aside>
<img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/a02c7a88-0b5b-40df-921e-d30b179c1f1a/empty.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/a02c7a88-0b5b-40df-921e-d30b179c1f1a/empty.png" width="40px" /> Challenges:
- The specified equipment at stage 3 is often changed later
- sometimes the equipment is not specified and there is chance that Single Phase Fan will become three phase - needing change in supply
</aside>
<aside>
<img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/8df95945-0479-497e-a150-8710961a5012/empty.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/8df95945-0479-497e-a150-8710961a5012/empty.png" width="40px" /> Successes:
- Preventative allocation of spare ways as default action
</aside>
Evidence:
<aside>
<img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/8df95945-0479-497e-a150-8710961a5012/empty.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/8df95945-0479-497e-a150-8710961a5012/empty.png" width="40px" /> Immediate causes:
- Analyze the collected data to identify the immediate causes of the problem. Look for factors such as errors, breakdowns, or deviations from established processes.
- Dig deeper: Use techniques like the "Five Whys" to dig deeper into each immediate cause. Ask "why" repeatedly to trace the causal chain until you reach the root cause.
</aside>
<aside>
<img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/d6831872-e8fb-4fc5-9536-50db7b9d9822/empty.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/d6831872-e8fb-4fc5-9536-50db7b9d9822/empty.png" width="40px" /> Recommended Actions for Implementation:
- allocate the supply to one of the three phases and immediately ‘block’ the other two as SPARE Later if the fan changes from single to three phase, you will have enough space in DB and will not need to move WAY - just update labelling
</aside>
- [ ] Seek feedback: Obtain feedback from project team members
- [ ] Consider unintended consequences: Examine if there have been any unintended consequences or side effects resulting from the implemented actions.
- [ ] Communicate the results: Share the evaluation results with the project team
