Lloyds TSB International Private Banking manages content with Magnolia


Published on

Lloyds TSB International Private Banking offers personalized investment solutions directly from its headquarters located in Geneva, Switzerland to clients in more than 100 countries. Magnolia, the bank's open source content management system of choice, allows for content re-use within the bank's public website, Intranet and personalized client sites. For example, business analysts provide recommendations for investment products with background information on the bank's Intranet, while relationship managers use such information in client communication. Clients might also find some of those recommendation papers in their personalized website space once they bought one of the recommended products. Other recommendations might be of general interest and would thus be published on the public website. The open source CMS has been adopted by 700 employees, with 50 of them regularly creating content.

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Lloyds TSB International Private Banking manages content with Magnolia

  1. 1. Lloyds TSB IPB Uses Magnolia October 2008
  2. 2. Context <ul><li>This presentation was given at the “Open Source Meets Business” conference In January 2009 </li></ul><ul><li>It was written in October 2008 </li></ul><ul><li>This is a light version of the initial presentation. </li></ul>
  3. 3. London Gibraltar Luxembourg Switzerland (Geneva, Zurich) Monaco Dubai Miami Ecuador Uruguay Paraguay … Lloyds TSB International Private Banking operates on a global basis. Argentina Colombia Guatemala Lloyds TSB International Private Banking Brazil
  4. 4. Lloyds and Open Source <ul><li>Where a Lloyds TSB standard, strategic, approved product that meets an application’s requirements already exists, it must be used - whether open source or proprietary </li></ul><ul><li>The selection process for OSS is similar to that for any third party offering, but with some additional considerations to accommodate criteria specific to OSS. </li></ul><ul><li>Lloyds TSB Group IT will not normally undertake to participate in Open Source developer communities, or commit to contribute to open source projects. </li></ul><ul><li>To avoid complicating both environments and licensing responsibilities, LTSB users will not ordinarily make direct changes to any Open Source code acquired. </li></ul>
  5. 5. Why having chosen Magnolia? <ul><li>We needed to re-factor our Intranet for the following reasons: </li></ul><ul><li>It had grown faster than expected </li></ul><ul><ul><li>It had become very uneasy to maintain </li></ul></ul><ul><ul><li>It had become very uneasy to manage </li></ul></ul><ul><li>We had very labour intensive publishing processes </li></ul><ul><ul><li>Users prepared documents/information (content) </li></ul></ul><ul><ul><li>Web master took the content, developed pages and deployed it on test </li></ul></ul><ul><ul><li>Users had to validate it in the test environment </li></ul></ul><ul><ul><li>Web master had to deploy it in production </li></ul></ul><ul><li>We had multiple publishing processes and they were error prone </li></ul><ul><li>We had a lot of duplicates between the Internet site and the Intranet site </li></ul><ul><li>Business people did not really own the content. IT did </li></ul><ul><li>We had to start a very expensive re-branding project </li></ul>
  6. 6. Why having chosen Magnolia? <ul><li>We then defined the following targets: </li></ul><ul><li>Chose a tool that will let us </li></ul><ul><ul><li>Simplify the publishing processes </li></ul></ul><ul><ul><li>Give to business people the ownership of the Intranet/Internet content </li></ul></ul><ul><ul><li>Publish the same information on different sites </li></ul></ul><ul><ul><li>Define different look and feels (e.g. Intranet different that Internet) </li></ul></ul><ul><ul><li>Easily manage and publish documents </li></ul></ul><ul><ul><li>Easily validate the content </li></ul></ul>
  7. 7. Why having chosen Magnolia <ul><li>The choice was made in 2005 </li></ul><ul><li>With the following main constraints </li></ul><ul><ul><li>Very limited budget -> Focused on Open Source solutions </li></ul></ul><ul><ul><li>Had to integrate well with our J2EE based environment </li></ul></ul><ul><ul><li>Support Multi-site publication </li></ul></ul><ul><li>I have rejected all the XML/XSL based CMS </li></ul><ul><li>Based on standards </li></ul><ul><ul><li>JCR170 </li></ul></ul><ul><ul><li>J2EE </li></ul></ul><ul><li>Ease of use. More intuitive than other tools </li></ul><ul><li>Ease of installation </li></ul><ul><li>Very flexible programming model </li></ul><ul><ul><li>This eased the integration with our existing applications </li></ul></ul>
  8. 8. Why having chosen Magnolia? <ul><li>Offered professional support </li></ul><ul><li>Swiss based product </li></ul><ul><ul><li>Why not encouraging a local Open Source product? </li></ul></ul><ul><ul><li>Ease of contact </li></ul></ul><ul><ul><li>Operating within the same business hours than us </li></ul></ul><ul><ul><li>They were able to immediately provide a Senior developer to help us </li></ul></ul><ul><li>We finally choosed their professional offer. </li></ul>
  9. 9. Magnolia Usage <ul><li>Intranet </li></ul><ul><ul><li>100% managed by Magnolia </li></ul></ul><ul><ul><li>2000 pages </li></ul></ul><ul><ul><li>3000 documents </li></ul></ul><ul><ul><li>35 contributors </li></ul></ul><ul><ul><li>4 content validators </li></ul></ul><ul><ul><li>Including </li></ul></ul><ul><ul><ul><li>“ Blog like” news system </li></ul></ul></ul><ul><ul><ul><li>Help desk web site </li></ul></ul></ul><ul><ul><ul><li>Financial Markets Web Site </li></ul></ul></ul><ul><ul><ul><ul><li>Containing all the investment advices, analysis, performance reports, ... </li></ul></ul></ul></ul><ul><ul><ul><li>Internal control web site </li></ul></ul></ul><ul><ul><ul><li>Shared information/documents with Internet </li></ul></ul></ul><ul><ul><ul><li>“ Wiki like”. Simple pages/site management using Magnolia </li></ul></ul></ul><ul><ul><ul><li>Image galleries </li></ul></ul></ul>
  10. 10. Magnolia Usage <ul><li>Public Internet Web site (http://www.lloydstsb-ipb.com/w3/en/home) </li></ul><ul><ul><li>100% managed with Magnolia </li></ul></ul><ul><ul><li>Multi-languages </li></ul></ul><ul><ul><li>Products & Offers </li></ul></ul><ul><ul><li>Contacts </li></ul></ul><ul><ul><li>Branches </li></ul></ul><ul><li>Private Internet Web site </li></ul><ul><ul><li>Web content and documents are managed with Magnolia </li></ul></ul><ul><ul><li>News </li></ul></ul><ul><ul><li>Special product offers </li></ul></ul><ul><ul><li>Product factsheets </li></ul></ul><ul><ul><li>Financial information </li></ul></ul><ul><ul><li>Results </li></ul></ul><ul><ul><li>Investment policies </li></ul></ul>
  11. 11. Publishing to multiple web sites <ul><li>Using Magnolia publishing mechanism we can publish the different information to different sites at the same time. </li></ul><ul><li>This is true for documents/content that has to be published both </li></ul><ul><ul><li>To the Intranet </li></ul></ul><ul><ul><li>To the public Web site </li></ul></ul><ul><ul><li>To the private Web site </li></ul></ul><ul><li>This is also true for recommendations given to the clients via the private Web site. The same information is published both: </li></ul><ul><ul><li>To the Intranet </li></ul></ul><ul><ul><li>To the Private Web site </li></ul></ul><ul><li>Our product offers are published both: </li></ul><ul><ul><li>To the Intranet </li></ul></ul><ul><ul><li>To the Private Web site </li></ul></ul>
  12. 12. Multi-languages Internet web site
  13. 13. Reusing/Sharing the information <ul><li>Using Magnolia we can centralize the access to the most meaningful information </li></ul><ul><li>Relationship managers now have a direct access to </li></ul><ul><ul><li>Product information </li></ul></ul><ul><ul><li>Analysis </li></ul></ul><ul><ul><li>Recommended products </li></ul></ul><ul><ul><li>Investment policies </li></ul></ul><ul><ul><li>News </li></ul></ul><ul><li>These documents are managed by Magnolia and easily made available </li></ul><ul><ul><li>Full integration (documents or services) </li></ul></ul><ul><li>Contributors regularly update the information </li></ul><ul><li>This information is used to provide better information/recommendations to the clients </li></ul>
  14. 14. Benefits of using Magnolia <ul><li>Simplification of the publication processes </li></ul><ul><li>One single repository of information </li></ul><ul><li>Shared documents: Intranet/Internet/Private Internet </li></ul><ul><li>Users now own the business content </li></ul><ul><li>Business people can now update the business content without the help of the IT department </li></ul><ul><li>Because of Magnolia’s flexibility we have been able to provide different kind of support to the users </li></ul><ul><ul><li>Web pages / Portal </li></ul></ul><ul><ul><li>Document management </li></ul></ul><ul><ul><li>News </li></ul></ul><ul><ul><li>Wiki </li></ul></ul><ul><li>Easy to use </li></ul>
  15. 15. Challenges <ul><li>Mainly on the IT side </li></ul><ul><li>Need very good IT skills (Java, Web) </li></ul><ul><li>Need for more documentation </li></ul><ul><li>Product evolving quickly </li></ul><ul><ul><li>Need to adapt to the changes. Not always easy to change too often in a big company </li></ul></ul><ul><li>More infrastructure management than expected </li></ul><ul><ul><li>This is getting much better with the latest releases </li></ul></ul><ul><ul><li>We are a big company with specialized departments (IT infrastructure, IT Development, …). IT Infrastructure had to understand how to manage Magnolia. </li></ul></ul><ul><li>Users now own the content and are fully involved in the publishing process. </li></ul><ul><ul><li>The challenge is not to use Magnolia, but to understand the process. </li></ul></ul>
  16. 16. Best practices <ul><li>Focusing on users </li></ul><ul><ul><li>By making sure they have a good understanding of what “Web” or “web content management” really means </li></ul></ul><ul><ul><li>By training them to Magnolia and Web Content Management </li></ul></ul><ul><ul><ul><li>Use of Magnolia must be made easy </li></ul></ul></ul><ul><ul><ul><ul><li>By providing trainings and documentation </li></ul></ul></ul></ul><ul><ul><ul><ul><li>By providing appropriate templates </li></ul></ul></ul></ul><ul><ul><li>By getting feedbacks and assessing the way they work </li></ul></ul><ul><ul><ul><li>Avoid misuses or misunderstandings (e.g. html formatting is not MSWord formatting) </li></ul></ul></ul><ul><ul><ul><li>Make them understand what they are responsible for (content) and what the Webmaster is responsible for (pages, navigation, templates, layouts, …) </li></ul></ul></ul><ul><li>Monitoring site evolution </li></ul><ul><ul><li>Users don’t understand the impacts of their activity on the overall system. Don’t let sites grow without management. </li></ul></ul><ul><li>Being proactive with users </li></ul><ul><ul><li>Magnolia provides the flexibility to adapt to user needs and offer very rich information. </li></ul></ul>
  17. 17. Best practices <ul><li>Defining new business processes </li></ul><ul><ul><li>New actors (not Web master centric as it was before) </li></ul></ul><ul><ul><li>User’s part of the process becomes more important, IT part becomes less important </li></ul></ul><ul><li>Defining a scalable architecture </li></ul><ul><ul><li>Support site growth (number of pages, number of documents, number of users) and new needs </li></ul></ul><ul><ul><li>It is going to grow faster than expected </li></ul></ul><ul><li>Integrating with Magnolia </li></ul><ul><ul><li>Magnolia to be used for Web Content Management </li></ul></ul><ul><ul><li>Other applications must reuse Magnolia but don’t have to be based on Magnolia </li></ul></ul><ul><li>Carefully planning the migration to new Magnolia releases </li></ul><ul><ul><li>This can be a very lengthy process (especially with a huge amount of pages and a big number of users to be migrated). You may should consider being helped by Magnolia people to do that. </li></ul></ul><ul><li>Letting the Webmaster be free to innovate </li></ul><ul><ul><li>To benefit from flexibility </li></ul></ul>
  18. 18. Best practices <ul><li>Do not under estimate the infrastructure workload </li></ul><ul><ul><li>Machines availability, backup, number of sites, security aspects </li></ul></ul><ul><li>Monitoring the changes </li></ul><ul><ul><li>Keep informed of the releases </li></ul></ul><ul><ul><li>Keep informed of the new features </li></ul></ul><ul><ul><li>Implement the most important releases (but not all) </li></ul></ul><ul><li>Keeping it simple </li></ul>
  19. 19. Best practices – For Open Source solution providers <ul><li>When wanting to be used by big companies </li></ul><ul><li>Sticking to the standards (J2EE standards in this case) </li></ul><ul><ul><li>E.g: JSR 170 </li></ul></ul><ul><li>Your products must run on the industry standard platforms </li></ul><ul><ul><li>E.g: Running on IBM Websphere, with an Oracle database </li></ul></ul><ul><li>Offering professional support </li></ul><ul><li>Must be easy to use </li></ul><ul><li>Must be easy to install </li></ul><ul><li>Keep in mind that your product will be subject to a stronger validation process than a non open source product </li></ul><ul><ul><li>Sticking to the standard and running on standard platform becomes a real plus </li></ul></ul><ul><li>Making a real effort on documentation </li></ul>
  20. 20. Questions and Answers