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
Aimed at a bank’s CRO and other ‘super-users’ such as quants, the package had an obvious coherence for banks and was formed into what is now known as the SAS Risk Management for Banking solution. Although Credit Risk for Banking (running the RWA calculations) had to date been delivered as a standalone function, SAS started to merge it fully into the Risk Management for Banking solution, ultimately giving SAS ‘a single, integrated architecture’. Under this heading, SAS now offers a range of risk functionality. In operation, each function of this unified offering is intended to look to the user like an individual application, but together creating a series of analytical events that can be run, reported on, distributed, pushed into Excel and so on. As an example, Rogers explained that running a copula calculation (so divining the dependence between random variables) for joint market risk and credit risk was possible because the ‘white box’ technological environment (ie. nothing is closed off to users), treats each event as ‘just another project’, whether firm-wide or separately. Users can ‘break into the process’ to check where the data came from, how it has been modified prior to being loaded, and run further enquiries on the results via the optional SAS BI stack. With the same Base SAS framework across the board, core developments have been rolled out to each environment. In risk management, in-memory processing, for example, while not specific to the space, has nonetheless been particularly effective in decreasing the time it takes to run calculations. Beyond the core architecture, the whole SAS concept


remains essentially a toolset where developments can be made in each application according to need. But in many verticals, with firms increasingly looking at exploring an holistic approach to risk, the idea of governance, risk and compliance (GRC) as a means of standardising risk management processes has gained currency in recent years. SAS announced its own Enterprise GRC offering in June 2010. This is basically an ‘all under one roof’ repository of GRC components covering a range of operational risks, political risks, legal risks and market risks and is intended to give risk managers, compliance officers, auditors and other business owners an overview of these elements so they may see how they relate to each other and the overarching business risk strategy. Although in use already (Swedish energy company,


Vattenfall, Europe’s fifth largest generator of electricity, was live), Rogers described the work as ‘a long-term project’ that would see the measurement and fraud side of analysis, for example, ‘gravitating towards being reported through a GRC structure’. He added ‘traditionally SAS never sat that close to the operational environment’, and so the vendor was still forming the requirements, mainly in the audit space and


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


generalising operational risk. Using reporting tools, workflow tools and human interface technology that had not previously been a major part of the SAS offering, alongside aspects of the SAS BI stack, even ‘the non-quant or non-super user’ will be able to interact with the system. This, said Rogers, was all part of SAS’s plan to promote the concept of an enterprise-wide risk culture. In late 2011, SAS launched a real-time analytics solution specifically for large investment banks, targeted at traders as well as risk managers. Based on SAS’s own third generation complex event processing engine (CEP) – built over the previous 18 months – the vendor claimed it could collate and analyse more than one million market, position and risk data points per second and would deliver most large and complex trading institutions from the need to rely on over-night batch data and VaR models.


Duncan Ash, financial services marketing and strategy manager at SAS, explained at the press launch that knowing the level of exposure to certain events was vital (as shown by the Lehman Brothers experience) and if this cannot be seen with any degree of accuracy until the next day it may already be too late. Ash claimed that the mathematics behind position calculations was not complex in itself, but until the release of this solution ‘getting the data aggregated to that level, in real- time has been impossible’. SAS users would now be able to individually manipulate and respond to this data at the level of business line, asset class, currency and geography. By streaming huge volumes of data through the SAS


in-memory system, in addition to real-time stress testing and multiple scenario planning (so traders can make the appropriate trade as and when an event happens), Dale Stevens, head of capital markets for SAS UK, said the solution was also capable of running assumption tests (including macro- assumptions), modelling the correlation, price divergence and volatility of portfolios, and creating alerts when models need to be reviewed or ‘when they’re no long any good’. At the time of launch there were no confirmed takers.


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