search.noResults

search.searching

note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
business units, said Snyman, then the project would have merely replicated the current poor processes once more. At BNP Paribas, it was recognised that there would be a


need to shift from end-of-day to real-time risk management but it was still relatively early in the journey by late 2014. At least, unlike most banks, it had a risk platform that covered all lines of business and both counterparty and market risk. It was also the only part of the bank that had an IT development team within the group function, reflecting the fact that risk management was deemed to be a special case. It uses Monte Carlo models for calculating regulatory capital, with this coming to be seen as important for the management of the bank, not just a regulatory task. It had automatic monitoring of around 900,000 limits. It had multi- dimensional drill-down capabilities


for risk analysis and


reporting and stress testing for both market and counterparty risk. On the input side, it had a lot of source systems and siloes, market data, calibration, static data (‘absolutely crucial, you have to be a lot more attentive and there are more and more descriptive regulations about how you classify counterparties’, said the bank’s head of risk systems, Mikael Sorboen) and risk indicators (typically more than 100,000 feed files per day, 800 million rows per day, and more than ten source systems). The bank had a three-layer database (Sybase IQ) in its Paris


data centre, with three days of data in the first layer, 50 days in the second and five years of history in the third, amounting to around 40 terabytes of data. Input data was handled by a Java/Python-based in-house developed scripting engine,


then moved in file format into a reconciliation engine (around 90,000 jobs per day), and was then loaded into the three-day layer (it was only loaded into the second layer if there were any adjustments to be made). The bank had an event engine to trigger calculations as soon as possible, with data extracted, calculated and input back into the database. The platform supported 2000 users in 40 sites, generating around 50,000 requests per day. There was an internal business intelligence layer, dubbed MRflex, which was described by Sorboen as a bespoke Java-based wrapper.


In terms of what within this set-up needed to be real-time,


BNP Paribas had identified a number of areas, for compliance and control. These were pre-trade checks against counterparty limits; compliance with trading mandates; detection and prevention of abnormal trading patterns; incremental initial margin requirements from central counterparties (CCPs); and control of market risk exposures per counterparty, net of collateral. Moving towards that was a multi-year work in progress.


It should be noted there are often forces pulling in opposite


directions within institutions. The theory around enterprise risk and finance is now fairly well understood but ahead of the financial crisis, few institutions had made much headway. The need to turn theory into practice is now even clearer but many banks are in a mindset where they are not willing to consider big projects, however strong the rationale.


Risk Management Systems & Suppliers Report | www.ibsintelligence.com


179


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192