I had to search this clarification since my initial thought was; not another "Mock" or Simulation of an issue that can potentially occur. I am all for discussing issues that we could potentially face and ways to solve those issues.
I have a hard time coming up with "Mock" instances to test a program . Now they added Mock Recall to 2.6.3.2 Investigation shall be undertaken to determine the root cause... that will take some inventiveness that I am not looking forward to for my simulation in February 2018. My team has little experience with actual recalls occurring,
thank goodness but with out that experience creating a fake root cause to a fake occurrence will take most of the time of our meeting.

Thanks Tony C. for the clarification 