When to loop back to configuration or methodology

Edit online
If a report looks off, it might be:
  • Configuration
  • Data quality
  • Real performance

You need to know when to pull in Configuration Guide or Data & Methodology Reference sections.

Escalate back to Configuration Guide when:
  • Whole Resource Towers or Cost Pools are blank when they should have cost.
  • You see obvious unit mix-ups (for example costs that imply 10x too many or too few servers).
  • Benchmark values change drastically after model changes in Costing.
Escalate back to Data & Methodology Reference when:
  • People question what exactly is included in a metric.
  • There is confusion about peer group or percentiles.
  • Someone asks if a comparison is valid given scope or accounting differences.

If you cannot explain a metric in plain language, treat that metric as advisory until you either fix configuration, refine scope, or get comfortable with the methodology.