If your bank, finance company or payments provider is supervised by the Saudi Central Bank, your IT incident and problem records will be read against the SAMA IT Governance Framework. Auditors do not only ask whether incidents were resolved. They ask whether the log was complete, whether SAMA was notified when the incident was notifiable, whether the detailed report went out on time, whether a root cause was found for major incidents, and whether lessons learned were recorded. Most teams keep this evidence scattered across the ITSM tool, email and spreadsheets, and they discover the gaps during the audit.
This workbook puts the evidence in one place and checks it for you.
WHAT IS INSIDE
Incident Register (SAMA ITGF 3.3.8). One row per incident: reference, opened time, service, owner informed, category, priority P1 to P4, classification, customer impact, SAMA notification time, resolution time, RCA, lessons learned, detailed report date and linked problem. The workbook calculates the target hours from your own policy, the elapsed hours, and a Met or Breach verdict on every row.
Problem and Known Error Register (SAMA ITGF 3.3.9). Impacted systems, priority, linked incidents, impact type, root cause, corrective action, owner, target date, closure date, known-error record and workaround.
Eleven automatic checks. Amber columns return 1 when a row has a gap an auditor is likely to raise: log fields missing, not resolved within the agreed level, notifiable but SAMA not notified, detailed report late or missing, P1 or P2 closed without RCA, P1 or P2 without lessons learned, impact not assessed, closed without root cause, root cause without corrective action, open past target date, and root cause known without a known-error record. The clause number sits above every check.
Evidence Summary. Counts rows and open gaps per check, with a grand total, ready to print as the cover page of your monthly evidence pack.
Settings. Your organisation name, review period, P1 to P4 resolution targets and the number of days allowed for the detailed incident report. The example values are illustrations, not regulatory requirements.
WHY IT IS DIFFERENT
It was built by a practitioner with more than ten years in enterprise IT operations inside a Saudi telecom group, who sits on the evidence side of audits. Every header is in English and Arabic. Every Y/N field that feeds a check is protected by a drop-down so the logic cannot be broken by free text. Each register holds up to 200 rows.
COMPATIBILITY
Microsoft Excel 2016 or later, or LibreOffice. No macros. Fictional sample rows are included so you can see every check working before you delete them and enter your own data.
Independent template. Not affiliated with, reviewed or endorsed by the Saudi Central Bank (SAMA). Not regulatory, legal or audit advice. Clause numbers refer to the SAMA IT Governance Framework; confirm them against the current official text.
Got a question about the product? Email us at support@flevy.com or ask the author directly by using the "Ask the Author a Question" form. If you cannot view the preview above this document description, go here to view the large preview instead.
Source: Best Practices in Incident Management, Arabic, Problem Management Excel: SAMA ITGF Incident & Problem Management Register Excel (XLSX) Spreadsheet, Elsadig Hamedelniel
|
Download our FREE Digital Transformation Templates
Download our free compilation of 50+ Digital Transformation slides and templates. DX concepts covered include Digital Leadership, Digital Maturity, Digital Value Chain, Customer Experience, Customer Journey, RPA, etc. |