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
wrong system was selected. Project management is a major cause of failures and delay; aspects such as data migration are consistently under-estimated; user resistance is another common cause (particularly if the users have not been adequately involved in the selection phase or where systems are being foisted on previously strong autonomous banks following a merger or acquisition). We carry lots of coverage of implementations – good, bad and everything in between – in our monthly IBS Journal as well as taking a closer look at the experiences, best practices and the lessons in our How to Select and Implement a Universal Banking System report. Where there are specialised system selection that need to be done, for example in the Islamic Banking systems, a 4D approach to selection has been explored in detail– including defining the needs, determining the short-list, deep-dive evaluation and delving into the contractual and commercial details.


A common question down the years has been, when are tier one and two banks going to address their core systems? The vast bulk of package sales are still to the tier three and tier four players, with this seen again in 2015. Where the bigger banks do buy packages, it tends to be for niche or overseas operations. Notably, when larger banks have set up direct banking offshoots, they have just about all gone for building brand new infrastructures, perhaps seeking a ‘bank in a box’ approach, rather than trying to tack the new entities onto their existing systems.


The reasons for the inability of the larger banks to address


their domestic cores are well known. Each bank has one of those sprawling systems diagrams showing the legacy and the ‘spaghetti’ that ties it together. An often home-grown set of core systems is surrounded by a mass of others, with point-to-point connections. The rallying cry for a few years now has been Service Oriented Architecture (SOA). Can the legacy be wrapped? Can functionality be provided as web services? Is this finally the way forward? Some banks, such as Wachovia (pre- crisis), have been taking an in-house build route with SOA; others, such as Credit Suisse, have been seeking over some time to put in an SOA framework ahead of what is meant to be a gradual replacement of their mainframe legacy.


The changing trends in the banking technology space are


best reflected in the topics of discussion in a typical conversation with the CIO or a CTO of a bank. While 10 years ago this used to be more focused on the core banking and back office systems that need to be overhauled, the shift became more towards service oriented architecture (SOA) and leveraging outsourcing models to drive cost structures down in the not so distant past. Talk to any technology head in the banking industry today, and it would be impossible to have missed the buzzwords of digital, cloud, analytics, mobility and


8


big-data.Banks have increasingly started to see the architecture driven by an 8 layer architecture : the channel layer that interfaces with the customer, the services / front-office, risk/middle-officeand core/back-office layers of the core systems, the analytics & reporting layer dealing with the business intelligence, the support layer that helps with the back-end functions, the external layer that includes inter-bank and payments and the inevitable middleware layer that stitches them all together In India, all of the large banks have set about overhauling their decent ralised domestic infrastructures in the last decade or so, with State Bank of India leading the way in terms of showing what can be achieved. The India Post experience has been more of a recent addition to the learnings. Deutsche Postbank in Germany also made strides for its large, albeit narrow, retail banking operations, as well as innovating in the area of payments, where it gained in sourcing mandates from three of the other large German banks. With Post bank’s acquisition by Deutsche Bank, the latter is seeking to adopt the former’s SAP set of systems.


A number of banks, such as Standard Bank in South Africa,


have been embroiled in ‘enterprise-widetransformation’ projects. During 2007 and 2008, two mid-tier UK banks came out with decisions for their core retail operations – Nationwide and Co-operative Financial Services, turning to SAP and Infosys respectively (Nationwide pressed on and had some cut-overs in 2012 and 2013 but the Co-op, for a variety of reasons, gave up, with a £151 million IT systems write-off ). In the Netherlands, F van Lanschot sought a fairly radical overhaul, so too KAS Bank (there was a major down-sizing as pectto this latter project). In Iceland, Kaup thing Bank had sought to transform its operations and Glitnir was seeking to do the same with its One- G project.


It looked as though in the new-look post-crisis financial


services market there would be are turn to traditional values and ways of competing, with the emphasis back on things like operational efficiency in transaction banking (payments has been a focus), customer service, rich and flexible channel delivery, time to market for products, ability to cross-sell, liquidity and risk management and control. To a degree, the experiences of the last few years should have emphasised this – for instance, those banks that could take savings over the internet benefited from the high degree of churn of funds as the crisis set in. The pressure to stand out from other banks will not go away and, indeed, should become more intense. There does seem to be a pick-up in urgency in at least the analysis being done by some of those banks that have been left intact, even if this isn’t equating to large numbers of strategic decisions at present.


The landscape of change, driven by the advent of digital and Market Dynamics Report 2017 | www.ibsintelligence.com


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  |  Page 193  |  Page 194  |  Page 195  |  Page 196  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203  |  Page 204  |  Page 205  |  Page 206  |  Page 207  |  Page 208  |  Page 209  |  Page 210  |  Page 211  |  Page 212  |  Page 213  |  Page 214  |  Page 215  |  Page 216  |  Page 217  |  Page 218  |  Page 219  |  Page 220  |  Page 221  |  Page 222  |  Page 223  |  Page 224