Ever wonder why this activity isn't scheduled where I think it should be? What exactly did PSO do to schedule it to a particular resource or not to the other one? It's a common challenge. You have this great software PSO, that's supposed to make complicated plans, but sometimes, SCHEDULING feels like a mystery. Totally. But what if I told you there's this feature that can actually explain those decisions? Oh, that's where the Explanations functionality comes in. Okay. So instead of just seeing the schedule and being confused, I can actually ask why did you do that? Exactly. The explanations page in PSO Workbench is your go-to for understanding not just what was decided, but why. So, it's all about transparency, helping users trust the system. Absolutely. You can see why an activity isn't scheduled or why it ends up being scheduled to a specific resource. Makes sense. But how does it actually work? Is it like some huge log file that's impossible to read? Yeah. No. Oh, not at all. The system shows all the places it tried to put an activity nicely grouped by resource and then by shift. So, if I'm scheduling a maintenance activity, I could see if it tried to put it on different resources or during different shifts. Exactly. And for each attempt, you can see if it worked or not and the reason why. Like, was the resource busy, or was there a shift conflict? Exactly. Maybe the Resource wasn't right for the job, or Something else is already scheduled, but you can go even deeper.