Running the checklist generator against these inputs. ═══════════════════════════════════════════════════════════ OPERATIONAL READINESS ASSESSMENT — FinanceHub Go-Live Target: not specified Platform: Hybrid — Windows Server 2022 (on-prem app nodes), SQL Server 2022 Always On AGs, on-prem AD synced to Entra ID, Azure integration service, Azure Monitor, SCOM, ServiceNow ═══════════════════════════════════════════════════════════ ## 1. EXECUTIVE READINESS SUMMARY Teams assessed: Infrastructure, Application Support, Database Team, Security Operations, Service Desk Domains applicable (11 of 20): 1. Monitoring & Alerting 2. Incident & Escalation Management 3. Identity, Access & Privileged Permissions 4. Knowledge Transfer & Documentation 5. Handoff & Cutover Mechanics 6. Backup & Restoration 7. Patch, Certificate & Secret Management 8. Support Model & Escalation Tiers 9. Data Migration & Reconciliation *(limited — see item)* 10. Cloud Governance 11. On-Premises Infrastructure & Network 12. Licensing & Vendor Support Entitlements Domains not applicable: - **Disaster Recovery & Failover** — merged into Backup & Restoration; no separate DR-site/region evidence exists beyond AG failover, not treated as distinct domain - **Capacity & Performance Thresholds** — no capacity/threshold evidence or RACI/scope reference found - **Integration, API & Scheduled-Job Support** — Azure integration service exists structurally, but no operational support detail found; folded into Cloud Governance REQUIRES VALIDATION items rather than a standalone domain, given thin evidence - **Change, Release & Rollback Management** — no evidence or RACI/scope reference - **Configuration Management (CMDB)** — no evidence or RACI/scope reference despite ServiceNow presence - **Business Continuity & Manual Workarounds** — no evidence or RACI/scope reference - **Hypercare Transition & Exit Criteria** — no hypercare terms, entry/exit criteria, or duration found in any input - **Compliance & Regulatory Obligations** — not named in any input Item counts by Readiness Status: READY: 3 | CONDITIONAL: 2 | REQUIRES VALIDATION: 11 | NOT READY: 5 | CONFLICTING: 0 | N/A: 8 Go-Live Blockers: 3 Most significant operational risks: - Database restore from backup has never been tested — only AG failover was demonstrated, which validates availability, not recoverability - Escalation contact list and vendor support contract are both unapproved/unfinalized, leaving Application Support's "A" for vendor escalation unsupported at go-live - On-prem server monitoring depends on SCOM, with no evidence SCOM alerting/coverage is configured for FIN-APP-01/02 Major evidence limitations: No CMDB/asset record, no change/rollback process, no defined hypercare period, no weekend Service Desk attendance confirmation, no capacity or performance baseline. **RECOMMENDED GO-LIVE POSITION:** **DO NOT PROCEED** Rationale: Three GO-LIVE BLOCKER items are NOT READY (database restore validation, escalation contact list, SCOM monitoring coverage confirmation) — untested recovery and an unapproved escalation path are disqualifying regardless of otherwise-passing smoke and node-failover tests. ## 2. EVIDENCE & SCOPE MAP | Source Tag | Document/Item | Type | Date/Version | Relevant Scope | Reliability/Limitation | |---|---|---|---|---|---| | {RACI} | RACI excerpt + matrix table | RACI | not dated | All teams | Two RACI representations given (prose + table); table used as authoritative, cross-checked against prose | | {IMPL-DESIGN} | Implementation design excerpt | Arch/Design | not dated | Platform architecture | Describes target design; not confirmation of current operating state | | {AS-BUILT} | As-built excerpt | As-Built | not dated | Server deployment, monitoring, backups | Most direct evidence of current state; explicitly flags SCOM dependency and missing restore test | | {WORKSHOP} | Support workshop notes | Workshop | not dated | Support model, escalation | States two items explicitly unresolved (vendor contract, escalation list) | | {TEST-RESULT} | Test results | Test-Result | 28 July 2026 | Smoke test, node failover, SQL failover | Recent and specific; explicitly excludes restore test | | {TRAINING-DOC} | Training record | Training | not dated | Service Desk readiness | Partial — weekend shift not confirmed | ## 3. TEAM & RACI ALIGNMENT | Team | Stated Scope | RACI Found | Confirmed Production Accountabilities | Ownership Gaps/Conflicts | Recommended Clarification | |---|---|---|---|---|---| | Infrastructure | Server availability, OS patching, network, DNS, backup-agent health, infra monitoring | R: Production hosting | Backup-agent installation confirmed (as-built) | DNS and infra-level monitoring named in scope but not evidenced anywhere in docs | Confirm DNS runbook and infra-monitoring configuration exist | | Application Support | App config, functional incident resolution, vendor escalation, release coordination, stakeholder comms | A: Production hosting, A/R: break-fix, A: user incident intake, A/R: vendor escalation | Smoke test pass supports functional readiness | Release coordination in TEAM_SCOPE has no matching RACI row — **OWNERSHIP GAP** | Add release coordination to RACI or confirm it sits elsewhere | | Database Team | SQL availability, backup execution, restore capability, performance, recovery support | A/R: database backup and recovery | AG failover demonstrated | Restore capability explicitly claimed in scope but restore test not evidenced — **RACI vs evidence gap, not a TEAM_SCOPE/RACI conflict** | Require restore test evidence before sign-off | | Security Operations | Privileged-access monitoring, security incident triage, escalation | A/R: security incident response | None confirmed — no privileged-access monitoring tooling or procedure evidenced | Scope claims privileged-access monitoring; no supporting evidence anywhere | Request evidence of privileged-access monitoring tool/process | | Service Desk | First-line intake, categorization, user comms, escalation to resolvers | R: user incident intake | Training delivered to 12 analysts | Weekend shift attendance not confirmed | Obtain weekend-shift training confirmation | ## 4. OPERATIONAL READINESS CHECKLIST | ID | Domain | Requirement | Team | RACI Role | Requirement Basis | Evidence State | Evidence Ref | Readiness Status | Criticality | Gap/Risk | Remediation | Proposed Owner | Target Timing | Dependency | |---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| | 01 | Backup & Restoration | Database restore from backup validated | Database Team | A/R | DOCUMENTED | CONFIRMED (as "not tested") | {AS-BUILT},{TEST-RESULT} | **NOT READY** | **GO-LIVE BLOCKER** | AG failover ≠ restore capability; no evidence data can be recovered from backup | Execute and document a full restore test | Database Team | Before go-live | None | | 02 | Support Model & Escalation Tiers | Final escalation contact list approved | Application Support | A/R | DOCUMENTED | CONFIRMED (as "not approved") | {WORKSHOP} | **NOT READY** | **GO-LIVE BLOCKER** | No approved path for P1 escalation at go-live | Finalize and approve escalation list | Application Support | Before go-live | Vendor contract (item 03) | | 03 | Licensing & Vendor Support Entitlements | Vendor support contract finalized | Application Support | A/R | DOCUMENTED | CONFIRMED (as "under review") | {WORKSHOP} | NOT READY | HIGH | Vendor escalation RACI role ("A/R") unsupported without active contract | Complete procurement | Application Support | Before go-live | None | | 04 | Monitoring & Alerting | On-prem server monitoring coverage confirmed for FIN-APP-01/02 (SCOM) | Infrastructure | R (Production hosting) | RACI-IMPLIED | PARTIAL | {AS-BUILT},{PLATFORM_CONTEXT} | **NOT READY** | **GO-LIVE BLOCKER** | As-built states dependency exists but doesn't confirm configuration/alerting is active on these two servers | Confirm SCOM monitoring + alerting rules are live for FIN-APP-01/02 | Infrastructure | Before go-live | None | | 05 | Monitoring & Alerting | Azure integration service metrics collection | — | — | DOCUMENTED | CONFIRMED | {AS-BUILT} | **READY** | MEDIUM | None — Azure Monitor collection confirmed | None | — | — | — | | 06 | Handoff & Cutover Mechanics | Application smoke test passed | Application Support | A/R | DOCUMENTED | CONFIRMED | {TEST-RESULT} | **READY** | HIGH | None | None | — | — | — | | 07 | Handoff & Cutover Mechanics | Application node failover tested | Infrastructure | R | DOCUMENTED | CONFIRMED | {TEST-RESULT} | **READY** | HIGH | None | None | — | — | — | | 08 | Handoff & Cutover Mechanics | SQL Server AG failover tested | Database Team | A/R | DOCUMENTED | CONFIRMED | {TEST-RESULT} | CONDITIONALLY READY | MEDIUM | Failover proven; restore not proven (see item 01) — availability ≠ recoverability | Pair with restore test before treating DB resilience as fully proven | Database Team | Before go-live | Item 01 | | 09 | Knowledge Transfer & Documentation | Service Desk training delivered | Service Desk | R | DOCUMENTED | CONFIRMED (weekday only) | {TRAINING-DOC} | CONDITIONALLY READY | MEDIUM | Weekend shift attendance not evidenced | Obtain weekend attendance record or schedule makeup session | Service Desk | Before go-live | None | | 10 | Backup & Restoration | Backup agents installed and healthy | Infrastructure | R | DOCUMENTED | CONFIRMED | {AS-BUILT} | READY | MEDIUM | None stated beyond installation — health/monitoring of agent status not evidenced | Confirm ongoing backup-agent health monitoring, not just installation | Infrastructure | Before hypercare exit | None | | 11 | Backup & Restoration | Database backup schedule configured | Database Team | A/R | DOCUMENTED | CONFIRMED | {AS-BUILT} | CONDITIONALLY READY | MEDIUM | Schedule exists but pairs with unproven restore (item 01) | Validate schedule against restore test outcome | Database Team | Before go-live | Item 01 | | 12 | Identity, Access & Privileged Permissions | Privileged-access monitoring operational | Security Operations | A/R | RACI-IMPLIED | MISSING | — | **REQUIRES VALIDATION** | HIGH | No tool, procedure, or evidence of any kind found for this accountability | Request evidence of privileged-access monitoring configuration | Security Operations | Before go-live | None | | 13 | Identity, Access & Privileged Permissions | AD/Entra ID sync health confirmed | Infrastructure | R (Production hosting, implied) | RACI-IMPLIED | MISSING | {IMPL-DESIGN} | REQUIRES VALIDATION | HIGH | Design states sync exists; no evidence of current sync health or monitoring | Confirm sync health monitoring in place | Infrastructure | Before go-live | None | | 14 | Incident & Escalation Management | Security incident escalation path defined | Security Operations | A/R | RACI-IMPLIED | MISSING | — | REQUIRES VALIDATION | HIGH | RACI assigns accountability; no procedure evidenced | Request security escalation runbook | Security Operations | Before go-live | None | | 15 | Incident & Escalation Management | 24/7 P1 escalation path (Infra/DB) operational | Infrastructure, Database Team | R / A-R | DOCUMENTED | PARTIAL | {WORKSHOP} | REQUIRES VALIDATION | GO-LIVE BLOCKER-adjacent* | 24/7 coverage stated as intent; not evidenced as staffed/tested, and depends on unapproved escalation list (item 02) | Confirm on-call staffing and test escalation path end-to-end | Infrastructure, Database Team | Before go-live | Item 02 | | 16 | On-Premises Infrastructure & Network | Network connectivity/DNS for app nodes confirmed | Infrastructure | R | RACI-IMPLIED | MISSING | — | REQUIRES VALIDATION | MEDIUM | Named in TEAM_SCOPE, no direct evidence | Confirm DNS records and network path documented/tested | Infrastructure | Before go-live | None | | 17 | Patch, Certificate & Secret Management | OS patching cadence for FIN-APP-01/02 | Infrastructure | R | RACI-IMPLIED | MISSING | — | REQUIRES VALIDATION | MEDIUM | RACI names patching accountability; no cadence/process evidenced | Confirm patch schedule and last-patched status | Infrastructure | Before hypercare exit | None | | 18 | Cloud Governance | Azure subscription/tenant governance for integration service | — | — | RECOMMENDED-CONTROL | MISSING | — | REQUIRES VALIDATION | MEDIUM | Not found in evidence or RACI; standard control for hybrid Azure workloads | Confirm subscription ownership, policy, and quota governance | To be assigned | Before go-live | None | | 19 | Data Migration & Reconciliation | Data migration/reconciliation evidence | — | — | RECOMMENDED-CONTROL | MISSING | — | REQUIRES VALIDATION | LOW | No evidence found; flagged only because "production" implies pre-existing or migrated data may exist — genuinely unclear from inputs | Confirm whether migration occurred and if reconciliation was performed | To be assigned | Before go-live | None | | 20 | Support Model & Escalation Tiers | Business-hours Application Support model confirmed operational | Application Support | A/R | DOCUMENTED | CONFIRMED (as intent) | {WORKSHOP} | REQUIRES VALIDATION | MEDIUM | Stated as the model, not evidenced as active/staffed | Confirm staffing roster in place | Application Support | Before go-live | None | *Item 15 marked REQUIRES VALIDATION rather than promoted to GO-LIVE BLOCKER on its own axis score, but it is flagged prominently because it structurally depends on Blocker item 02 — see Residual Risk Summary. ## 5. GO-LIVE BLOCKER REGISTER | Blocker ID | Blocker | Affected Capability | Evidence | Consequence | Required Resolution | Accountable Decision Owner | Closure Evidence Needed | |---|---|---|---|---|---|---|---| | B01 | Database restore not tested | Database recoverability | {AS-BUILT}, {TEST-RESULT}: restore "was not tested" | Data loss may be unrecoverable in a real incident despite AG failover working | Execute full restore-from-backup test | Database Team (A/R) | Documented restore test result with timestamp and outcome | | B02 | Escalation contact list not approved | P1 incident escalation, all teams | {WORKSHOP}: "final escalation contact list has not been approved" | No confirmed path to resolve a production P1 at go-live | Approve and distribute escalation list | Application Support (A/R, vendor escalation) | Signed-off escalation document | | B03 | On-prem monitoring (SCOM) coverage for FIN-APP-01/02 unconfirmed | Detection of on-prem app-node issues | {AS-BUILT}: monitoring "remains dependent on" SCOM, no configuration confirmation given | Issues on production nodes may go undetected until user-reported | Confirm and evidence SCOM alerting is active on both nodes | Infrastructure (R) | Screenshot/export of active SCOM monitoring rules for FIN-APP-01/02 | ## 6. CONDITIONAL READINESS & RISK ACCEPTANCE REGISTER | Item | Residual Risk | Impact | Temporary Control | Risk Owner | Formal Approval Required? | Review/Expiry Point | Permanent Resolution | |---|---|---|---|---|---|---|---| | SQL AG failover tested, restore not tested | Recovery from a full data-loss event unproven | High if realized | AG provides availability continuity in the interim | Database Team | Yes — not evidenced as approved in any input | Before go-live, tied to B01 | Completed restore test | | Service Desk weekend training unconfirmed | Weekend-shift analysts may be undertrained at go-live | Medium | None evidenced | Service Desk | Yes — not evidenced as approved | Before go-live | Confirmed attendance record | ## 7. VALIDATION & EVIDENCE REQUEST PLAN | Priority | Evidence/Validation Needed | Reason | Requested From | Acceptance Criteria | |---|---|---|---|---| | 1 | Database restore test result | Directly gates go-live recommendation (B01) | Database Team | Documented successful restore with timestamp | | 2 | Approved escalation contact list | Directly gates go-live recommendation (B02) | Application Support | Signed/approved document | | 3 | SCOM monitoring configuration evidence for FIN-APP-01/02 | Directly gates go-live recommendation (B03) | Infrastructure | Active alert rule export or screenshot | | 4 | Vendor support contract status | Blocks vendor escalation A/R role | Application Support / Procurement | Executed contract | | 5 | Privileged-access monitoring evidence | Security Operations RACI role currently unsupported by any evidence | Security Operations | Tool/process documentation | | 6 | AD/Entra ID sync health monitoring | Core identity dependency for hybrid auth | Infrastructure | Sync health dashboard or report | | 7 | Weekend Service Desk training attendance | Coverage gap for one shift | Service Desk | Attendance record | ## 8. HYPERCARE READINESS Not generated — no hypercare terms, entry/exit criteria, duration, or transition plan appear anywhere in DEPLOYMENT_DOCS, RACI_MATRIX, TEAM_SCOPE, or PLATFORM_CONTEXT. Flagging this as its own evidence gap rather than fabricating a standard hypercare structure. ## RESIDUAL RISK SUMMARY **Cross-team gaps requiring more than one team to close:** - B02 (escalation list) blocks Infrastructure and Database Team's 24/7 P1 capability (item 15) even though Application Support owns the approval - Database restore (B01) and backup schedule validity (item 11) are coupled — one team, but the checklist item can't close independently **OWNERSHIP GAPS (Step 0.2):** - Release coordination — named in Application Support's TEAM_SCOPE, no matching RACI row **RACI vs TEAM_SCOPE conflicts (Step 0.5):** - None found. Database Team's scope claims "restore capability" and RACI assigns A/R for "database backup and recovery" — these align on ownership; the gap is evidentiary (no test performed), not a Step 0.5 ownership conflict, and is scored that way in item 01. ## NOT INFERRED — deliberately excluded, no supporting evidence in any input - Whether ServiceNow is actually configured as the ticketing/escalation tool in use (named in PLATFORM_CONTEXT only, never referenced in workshop notes, RACI, or as-built) - Any capacity, performance threshold, or load-testing data - CMDB/asset accuracy status - Any change management or rollback procedure - Any named individual contacts, SLA figures, or approval signatures - Whether data migration into FinanceHub occurred, or from what source - Compliance/regulatory framework applicability - Go-live target date ═══════════════════════════════════════════════════════════ The recommendation is **DO NOT PROCEED** — driven strictly by the three GO-LIVE BLOCKER items, not by the overall pass/fail ratio (12 of 20 items are READY/CONDITIONAL/in-progress, which would look fine on a percentage basis, but the rule set explicitly forbids using that ratio to override an unresolved blocker). Items 01–03 are the fastest path to a status change if you want to re-run this once restore testing, the escalation list, and SCOM confirmation come back — those three alone would flip most of the downstream REQUIRES VALIDATION items in the Support & Monitoring domains too, since several are structurally coupled to them.