Informational Fresh jira_story: GOV-213

Lesson 4 of 4 — SLA and RACI automation and auto-recert

Data Platform Hardening · Source: Jira Story GOV-213 (5 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Automate SLA escalation and recurring recertification.

Why it matters

Manual SLA and recert tracking drifts; automation keeps obligations current.

Where this lives

Runs in the Customer AI Governance platform (components: workspace). SLA breaches trigger escalation; a recertification schedule is wired to RACI. Learn teaches this read-only.

Workflow

Given an SLA breach
When it occurs
Then escalation fires and the recert schedule is wired

Worked example

An SLA is breached. Beyond alerting, what recurring mechanism should this story wire up?

An escalation plus a recertification schedule so ownership is periodically re-confirmed.

Acceptance criteria (authoritative — GOV-213)

Given an SLA breach, when it occurs, then escalation fires and the recert schedule is wired.

Common pitfalls

Wiring escalation but forgetting the recurring recert schedule.

Knowledge check

Scenario: An SLA is breached. Beyond alerting, what recurring mechanism should this story wire up?
Look for: An escalation plus a recertification schedule so ownership is periodically re-confirmed.

Key concepts

SLA escalation
auto-recert
RACI automation

For the AI Tutor

Summary: Automate SLA escalation and recurring recertification.
When to use: teaching or answering questions about "sla and raci automation and auto-recert".
When NOT to use: assigning owners initially (that is GOV-117).
Key concepts: SLA escalation, auto-recert, RACI automation.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-213's acceptance criterion.

Module: LEARN-MOD-007 (Data Platform Hardening)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: (module complete)