Visual Maps 09–12
Map 9 — Operations Control Loop
RULES → MEASURE → THRESHOLD → ISSUE → ASSIGN / ESCALATE → DIAGNOSE → REMEDIATE → MONITOR
Overlay SLA commitments on notification, response, remediation, and escalation.
Answer check: the loop returns to monitoring and preserves rule/issue history.
Source: pp. 445–450.
Map 10 — Tool Pipeline
PROFILE → PARSE → STANDARDIZE / TRANSFORM → ENRICH → MONITOR / INCIDENT
Interpretation: discovery, decomposition, normalization, augmentation, and operational management are different functions.
Name/address example: profile patterns → split name → normalize state/address → add geocode → monitor exceptions.
Answer check: parsing is not enrichment; standardization does not prove accuracy.
Source: pp. 450–453.
Map 11 — Prevention / RCA / Correction Triangle
- PREVENT — stops future defect entry/propagation.
- RCA — explains/removes the underlying cause.
- CORRECT — repairs existing bad records.
Examples: UI validation = prevention; Five Whys = RCA; cleansing = correction.
Answer check: “best long-term” usually points toward cause/prevention unless facts justify controlled ongoing correction.
Source: pp. 455–459.
Map 12 — Evidence & Governance Stack
RULE-LEVEL RESULTS → SCORECARD / TRENDS → SLA & ISSUE REPORTS → BUSINESS IMPACT → GOVERNANCE ACTION
Interpretation: measurement creates value only when ownership and governance turn evidence into decisions and action.
Place Data Owner / Steward / Governance beside the action layers.
Answer check: measurement without ownership/action is not a mature DQ function.
Source: pp. 446–450, 462–464.
Final visual test
Rebuild Maps 1, 3, 4, 5, 6, 7, 9, and 11 without looking. For each, state the single clue that would change an exam answer.