A utility's AI Center of Excellence has no intake. During storm week the loudest request gets an agent, and planned safety work waits. What should the CoE create?
Select an answer to reveal the explanation.
Short Explanation
A line with no tickets lets the loudest voice walk straight to the front. You create an intake path and ranking criteria so a storm-week request is ordered against the safety work already planned. A mailbox that still lets someone skip ahead is the queue you have now.
Full Explanation
Intake and ranking are how a Center of Excellence keeps urgent noise from erasing the plan. The utility has no intake, so storm week is won by whoever shouts, and the fix is an intake path plus criteria that place a storm request against the safety work already planned. A side channel where any team starts a build without being ranked is another way to skip the line. A status slide of last year's projects records history and does not order this week's requests. A shared mailbox that still lets the loudest request skip ahead collects paper and preserves the failure. The criteria should be written before storm week, using impact the sponsors already accept, such as safety and the cost of waiting. During the storm, new requests enter that same intake and receive a rank, and a shout in a channel is not a rank. Exam caveat: ranking criteria are not a ban on storm work. A storm request can rank first when the criteria say outage impact outranks ordinary projects. Operational check: submit one storm request and one planned safety request through the new intake and confirm both receive a rank before either build starts.