Generated controls for a water utility appear with blank owners and nobody responds to failed tests. What accountability architecture is missing?
Select an answer to reveal the explanation.
Short Explanation
A broken hydrant with no crew assigned stays broken. Controls need owners—people or groups who own the testing and the fix. Blank ownership breaks the accountability architecture.
Full Explanation
Accountability architecture requires ownership on generated controls so testing, attestation, and issue response have clear assignees. Leaving owners blank creates orphaned work and silent failures. Ownership typically sits on the control instance (and related tasks), not solely on the distant authority document.