Change Risk Assessment — example output

███╗ ██╗ ██████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ██╗██╗████████╗ ████╗ ██║██╔═══██╗██║ ██║ ██╔══██╗██║ ██║ ██╔╝██║╚══██╔══╝ ██╔██╗██║██║ ██║██║ █╗ ██║ ███████║██║ █████╔╝ ██║ ██║ ██║╚████║██║ ██║██║███╗██║ ██╔══██║██║ ██╔═██╗ ██║ ██║ ██║ ╚███║╚██████╔╝╚███╔███╔╝ ██║ ██║██║ ██║ ██╗██║ ██║ ╚═╝ ╚══╝ ╚═════╝ ╚══╝╚══╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ✦ NowAIKit — The #1 AI App for ServiceNow - Running ops-risk in direct mode (ollama)... # Change Risk Assessment Report Instance: demo2 Assessment Date: 2019-03-05 21:54:31 Assessment ID: CRA-20190305-001 --- ## 📊 EXECUTIVE SUMMARY Based on the CMDB CI data gathered, this change risk assessment has been conducted. However, important limitations exist: the provided data contains Configuration Item records but lacks specific Change Request details (change IDs, scheduled windows, implementation plans, etc.). Recommendation: Obtain complete change request records before proceeding with formal assessment. --- ## 📋 CI ANALYSIS | Field | Value | Notes | |-------|-------|-------| | Total CIs Retrieved | 20 | Limited sample | | Critical CIs Identified | 0 | No critical infrastructure detected | | Unknown/Placeholder CIs | 1 | CI-8fbc3c053bc07300b924874064efc4ae | | Unknown CI Description | Duplicate CIs post NY upgrade | Requires investigation | | Attested CIs | 0/20 (0%) | Low data maturity | ### CI-8fbc3c07300b924874064efc4ae Details ```json { "name": "Unknown", "sys_domain": "global", "short_description": "This CI is referenced by all duplicate CIs that were upgraded to New York...", "sys_mod_count": "0", "attested": "false", "unverified": "false" } ``` --- ## ⚠️ RISK ASSESSMENT | Dimension | Score | Justification | |-----------|-------|---------------| | Scope | 2 | Single CI (Unknown placeholder), minimal dependencies | | History | 5 | No historical data available; placeholder CI indicates data quality issues | | Complexity | 3 | Multiple script changes may be pending (upgrade artifacts) | | Reversibility | 3 | Partially reversible — duplicate CI cleanup requires manual steps | | Window | 2 | No change window data available; assuming off-peak for unknown CI | ### **Overall Risk Score: 3.0 / 5.0** ### **Risk Level: MODERATE** ⚠️ Action Required: Peer review and monitoring post-deploy --- ## 🔍 CONFLICT DETECTION ### Overlapping Windows - ❓ No change request data available - ⚠️ Cannot determine overlapping changes ### Same CI Conflicts - ⚠️ **Unknown CI has no defined dependencies** - ⚠️ Requires investigation before change scheduling ### Blackout Periods - ❓ No blackout calendar data available - ⚠️ Cannot validate against corporate freeze windows --- ## 📝 RECOMMENDATIONS ### Immediate Actions 1. Investigate Unknown CI — Resolve duplicate CI references from NY upgrade 2. Obtain Change Request Details — Get change IDs, scheduled dates, and implementation plans 3. Perform Discovery — Complete attestation of CI records (0% currently attested) 4. Map Dependencies — Identify CI relationships for the target CIs ### Before Change Implementation ``` [ ] Verify no overlapping changes in maintenance window [ ] Confirm blackout period compliance [ ] Validate CI relationships and dependencies [ ] Obtain peer review for MODERATE risk changes [ ] Prepare rollback plan for partial CI cleanup ``` --- ## 🎯 RISK SCORING DETAILS ### Formula Applied ``` Risk Score = (Scope 2 + History 5 + Complexity 3 + Reversibility 3 + Window 2) / 5 = 15 / 5 = 3.0 ... (111 more lines — full output truncated for screenshot)