CC-03
UCL Not Configured
Control Chart
Default severity: medium
ProcessMetricsOutputRisk
What it detects
No Upper Control Limit is configured for this project — there is no defined out-of-control threshold.
Detection formula
IF config.ucl.sigma_multiplier IS NULL OR NOT SET THEN FLAG Recommend: UCL = avg + 3 * stddev (configurable multiplier)Examples in practice
- Control chart limits are not configured, so no UCL is available for outlier detection.
- The workspace never sets sigma multiplier for upper control limit calculation.
- Outlier rules cannot run because UCL configuration is missing.
Suggested response
Treat the metric as a control signal: confirm limits, windows, and cross-team spread before acting.
Coaching playbook
Symptom
No Upper Control Limit is configured for this project — there is no defined out-of-control threshold.
Why it matters
When "UCL Not Configured" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Treat the metric as a control signal: confirm limits, windows, and cross-team spread before acting.
Facilitation questions
- What system change would stop "UCL Not Configured" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.