banks, selling a solution for one area and then broadening from here. For instance, during 2011, it claimed many ALM clients had also bought liquidity management functionality. Some of the components have been rewritten, typically with a move to more modern platforms. There has been a standardisation on Microsoft, including at the database level with SQL, in part for reasons of cost of ownership. Sungard’s Ambit Risk & Performance MD for sales, Alwin Meyer, admitted in late 2011 that it was still a battle to persuade users that Sungard had a homogeneous platform. ‘It is the main thing we have to fight against, that we just have different components.’ In fact, he claimed not only a consistent look and feel but also emphasised that Sungard had started on integration earlier than some others. He pointed out that suppliers such as Algorithmics (IBM) and Oracle also had different pieces from different sources within their offerings. For credit risk, the Sungard solution is meant to cover
credit assessment, credit portfolio management and stress testing. This is more or less for commercial lending and not the type of pre-trade real-time credit risk of Adaptiv. For operational risk, the Sungard partnership for the Sword
product appears to have worked well and there has been a fairly good uptake. The area of greatest activity is ALM and market risk. ALM, as mentioned, is the origins of Almafin. Areas covered include earnings simulation, hedge management, funding optimisation and economic value of equity (EVE). The Adaptiv- derived market risk capability is still for smaller banks, with some of the facilities of the full Adaptiv offering basically turned off as they are not needed by the target segment. In this environment, Ambit Risk & Performance supports market risk management on a T+1 basis, with VaR and stress testing. The Adaptiv component has only been brought into the suite since Sungard went private, in 2005, at which point, as mentioned, the traditional divides between the different Sungard companies started to be dismantled. The fourth component is liquidity risk management, which has been built by the Sungard Risk & Performance team. There are pre-packaged stress test solutions and a scenario engine that can accommodate current and future stress testing needs, and supports countermeasure activities and measures their impact. There are also pre-defined extensible key risk indicators. To move data in and out of the platform – always a challenge within risk projects – there are migration tools within the offering for data validation, consolidation, enrichment, transformation and reconciliation. Above the credit, operational, market and liquidity risk components are layers for ‘risk mitigation’ centred on capital management, with both a regulatory and economic aspect to this (in line with Basel). It spans capital adequacy, performance stress-testing and risk aggregation. There is also an umbrella layer for risk adjusted performance
management, including profitability analysis and risk adjusted return on capital (RAROC) to a single transaction level. Sungard has added these capabilities within the last few years, through in-house development, with initial demand coming from the US. There is also a layer for budgeting and planning, including margin and payroll planning. The main development centres are New York, Boston,
London, Winterthur (where Almafin was based) and Melbourne. There are dedicated delivery teams as well in the Gulf, Zurich, Paris, Madrid, Pune, Johannesburg, Singapore, Beijing and Sao Paulo. Sungard largely handles the implementation of its suite
itself. For generic needs, such as project management, it can also draw on Sungard Consulting Services. The supplier claims a single code base for all customers. There has been cross-marketing into some of the core system user bases. This has happened with Apsys/Ambit Private Banking. It has not occurred with Symbols/Ambit Core Banking to date, with the main focus being selling treasury systems with this, although a push with the risk components was planned for 2012. There are also adaptors for third party applications, such as those of Avaloq, ERI (Olympic), Finnova and Temenos (T24). On the technology side, clearly Sungard inherited different systems of different ages and on different platforms but it made the decision, as noted, to standardise on Microsoft and Intel for Risk & Performance, including on SQL at the database level. The lower cost of ownership was deemed important for the target base. Meyer said he was aware of only two or three deals that had been lost over the years due to the platform (he cited China as particularly keen on Oracle rather than Microsoft) but felt this had been far outweighed by the speed of development that is feasible through the ability to focus on a single platform. As a potential alternative to the traditional licence software route, there has been little or no adoption of Sungard’s Software as a Service (SaaS) model (branded as Infinity) on the risk and performance side to date. It is worth noting that Sungard and SAP formed a partnership in mid-2007 whereby Sungard’s risk solutions were meant to be brought into the latter’s compliance suite. The first focus was on Bancware for ALM. SAP’s Business Process Platform (BPP) financial database was meant to integrate all transactions for operational risk, said the supplier’s Marc Derungs, VP of banking, with analytics on top. When the development started, there was huge pressure around Basel II and, in western Europe, IAS. However, ALM then started to become more prominent, he said. In traditional universal and retail banking, margin pressure had definitely increased in the last couple of years, he said. This had brought the need for more sophisticated ALM. ‘Before it was a risk control exercise – stay in limit and provide reports to the regulator.’ Now it was much more strategic, centred on taking interest rate risk as a revenue opportunity. SAP could have developed a solution to fill this gap, he said, but in the interests of time, it decided to
Risk Management Systems & Suppliers Report |
www.ibsintelligence.com 143
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