Table 7 Description and examples of key fields in the constructed database.
No. | Key fields | Description | Example |
|---|---|---|---|
1 | Event ID | Unique identifier of the event | 1 (The first recorded in the database) |
2 | Start year | The year the operational risk event started | 2014 |
3 | Start month | The month the operational risk event started | 5 |
4 | End year | The year the operational risk event ended | 2018 |
5 | End month | The month the operational risk event ended | 7 |
6 | Loss amount | The actual amount of loss (Unit: 10,000 CNY) | 14,000 |
7 | Province occurred | Provinces, autonomous regions, municipalities and special administrative regions where the event occurred | Sichuan Province |
8 | City occurred | The city where the event occurred | Chengdu City |
9 | Bank involved code | The bank where the operational risk event occurs, represented by a code for privacy protection. | 1 |
10 | Causal factor | Causes giving rise to the event, including Internal processes, Personnel, Systems, and External events (according to the definition of operational risk). | Personnel |
11 | Event type | Seven event types classified by the Basel Committee on Banking Supervision, including Internal fraud, External fraud, Employment practices and workplace safety, Clients, products & business practices, Damage to physical assets, Business disruption and system failures, Execution, delivery & process management. | Internal Fraud |
12 | Business line | Eight business lines are classified by the Basel Committee on Banking Supervision, including Corporate finance, Trading & sales, Retail banking, Commercial banking, Payment and settlement, Agency services, Asset management, and Retail brokerage. | Commercial banking |
