Incident Prevention Centre in Service Collection

Prevention Center is an AI-native incident prevention command center within Service Collection Change Management. It brings together end-to-end change context, AI-assisted risk analysis, service dependencies, calendar collision checks, and actionable mitigation planning into a unified, human-reviewed workspace before changes are approved and deployed.

Overview of Prevention Center

When reviewing complex changes, key operational details are often fragmented across pull requests, deployment pipelines, related tickets, and knowledge bases. Prevention Center surfaces and synthesizes these data points directly on the change request while keeping standard Jira custom fields readily accessible below the AI-powered section.

Prevention Center provides the following core capabilities:

• Change Summary: Generates a concise summary of the change request from connected sources (change tickets, accessible linked resources, knowledge base articles, and attached PRs or deployments). It highlights the current state versus the proposed future state across all changing parameters.

• Change Pre-risk Assessment: Delivers an early risk indication by scanning high-level signals and historical risk patterns from previous changes.

• Activity Stream: Consolidates activities performed across the change description and audit logs, ensuring smooth hand-offs and clear operational visibility.

• Service Graph & Dependencies: Identifies all affected services, visualizes upstream and downstream dependencies, and highlights any active incidents on connected services.

• Calendar Conflicts: Cross-references deployment schedules and change calendars to flag concurrent changes or change freeze window violations.

Evaluate changes across 4 AI risk categories

Rovo evaluates risk using accessible change descriptions, comments, linked PRs, attachments, and organizational knowledge bases. Risk is evaluated across four dedicated dimensions:

1. Technical risk

Assesses factors that could increase the likelihood of incidents, deployment failures, or system instability:

• Related incidents and PIRs: Checks open incidents on affected services or assets and identifies patterns from past post-incident reviews (PIRs) matching the change.

• Change & deployment history: Flags historical deployment failures and rejected changes on the same service within the last 90 days.

• Implementation readiness: Evaluates the completeness of test plans, execution steps, and rollback plans.

• Data migration & compatibility: Highlights data layer changes, schema updates, or compatibility risks.

• Code quality & security: Performs basic static analysis on linked PRs/deployments to flag memory leaks, vulnerable dependencies, or security flaws.

2. Operational risk

Focuses on timing, cross-team coordination, and infrastructure impact:

• Scheduling conflicts: Highlights concurrent changes scheduled on overlapping services or assets.

• Stakeholder impact: Maps affected service roles (service owners, responders, stakeholders, incident managers, asset owners) to ensure appropriate notification.

• Infrastructure changes: Surfaces modifications to core infrastructure (such as authentication layers, CDNs, or network routing).

• Rollback complexity: Assesses the estimated time, dependencies, and operational difficulty required to revert the change.

3. Compliance & Security risk

Summarizes potential exposure across regulatory, security, and governance standards:

• Security risk: Identifies exposure from changes touching sensitive components, secrets, or identity boundaries.

• Privacy & regulatory compliance: Flags modifications involving personal data (PII), regulatory frameworks, data flows, and audit requirements.

• Accessibility risk: Evaluates UI modifications, interaction patterns, and assistive technology compatibility against accessibility standards.

4. Business risk

Evaluates direct financial, commercial, and customer brand impact:

• Financial risk: Assesses exposure to revenue streams, billing workflows, high transaction volumes, service downtime costs, or contractual SLA penalties.

• Reputational risk: Evaluates potential impact on customer trust, brand perception, user sentiment, and external communication requirements.

Work through mitigation steps and make approval decisions

Prevention Center keeps human decision-makers firmly in control:

• Actionable Mitigation Tasks: When risks are identified, Rovo suggests specific mitigation steps. Change managers and engineers can accept all or a subset of suggestions and instantly generate linked tasks on the change ticket.

• Reassess with Context: Approvers can add context (via fields, comments, or linked documentation) and rerun the risk assessment dynamically.

• Approve or Reject: Approvers evaluate the holistic pre-risk score, category breakdowns, and completed mitigations before granting approval or rejecting the change.

• Standard Field Retention: All standard Jira issue fields, forms, and custom attributes remain available directly below the AI-generated Prevention Center panel.

Configure Prevention Center and Risk Assessment settings

Project administrators can manage Prevention Center and risk evaluation preferences under project settings.

1. In your service project, go to Project settings > Operations > Change management.

2. Select the Risk assessment tab.

3. Configure the settings according to your operational model:

   • For new projects: Prevention Center and Rovo AI Risk Assessment are turned on by default.

   • For existing projects: Enable or disable Prevention Center using the main toggle.

   • When Prevention Center is enabled: Risk assessment can be configured to use Rovo-powered AI Risk Assessment or set to Disabled. There’s no option for using non-AI Risk assessment

   • When Prevention Center is disabled: Teams can choose between Rovo AI Risk Assessment or the Legacy (non-Rovo) Risk Assessment.

4. Under Knowledge base, link the Confluence spaces, SharePoint projects or knowledge base repositories that Rovo should reference when conducting risk evaluations.

5. Under Risk Management > More settings, toggle individual risk categories (Technical, Operational, Compliance & Security, Business) on or off as required (If Prevention Centre is enabled). Changes are saved automatically.