Fiori Approvals Implementation at Catlin

Company Overview

• Company name: Catlin Group

• Products/services: Specialist property/casualty insurer and

reinsurer

• Operating countries: Global - offices in more than 50 cities

• SAP Go-Live: Q2 2013

• SAP Modules: FI, CO & T&E

• SAP Version: ERP 6.0 EHP5

• SAP Users: 2000+

Project Drivers

• By accident rather than design the internal approvals capability of the pre-SAP GL Solution worked on many mobile devices

• Initial SAP implementation did identify mobile requirement but was understood to be low priority and de-scoped

• Due to webgui Java requirements the Internal SAP Approvals capability did not work on many mobile devices

• By end of August it was clear lack of mobile approvals was having an impact on agility of business operations

• Towards end of October Catlin board decided mobile solution was required and initiated a project to deliver mobile approvals functionality “in time for Christmas”

Solution Options• SAP Mobile Solution

• In-House Developed Solution

• SAP Fiori / UI5 Solution

Solution Options• SAP Mobile Solution

– High hardware and licensing costs

– In-consistent with target architecture and development standards

– High level of SAP expertise required to for on-going development and support

– High probability that solution could not be delivered in 2013

– SAP Standard Solution

• In-House Developed Solution

– Lowest hardware and licensing costs

– Consistent with target architecture

– SAP interface likely to require high level of SAP expertise for on-going development and support

– Medium probability that solution could not be delivered in 2013

– Higher risk of future changes impacting a Non-SAP Standard solution

• SAP Fiori / UI5 Solution

– Low hardware and licensing costs

– Consistent with target architecture

– Lowest level of SAP expertise required for on-going development and support

– Low probability that solution could not be delivered in 2013

– Although SAP standard solution Catlin would be a very early adopter

Vendor Selection Process

• Initial assessment indicated that 3rd party assistance would be

required

• Three competing vendors provided with seed funding and access to

Catlin systems and resources for two weeks

• Chosen vendor delivered a working proof of concept, other vendors

delivered written proposals

• Vendor agreed to placing all developers on site for the duration of

the project allowing for maximum interaction and knowledge transfer

Project Timeline

• 2 months from 1st contact to 1st delivery

• 29 working days from approval to start project to 1st production deployment

• Full project delivered in less than 4 months (including festive period)

• According to SAP account manager first production installation of SAP Fiori in UK

Success Drivers

• Commitment of senior management and their active sponsorship

• User requirements driven process. Use of wireframes for early feedback.

• Pilot Approach – getting functionality to users early and often then using the feedback to drive incremental improvements

• Collaboration between business, IT and delivery partner

• Team motivation and commitment to make it happen

• Agile methodology

Benefits Realised

• Project delivered full scope on time, on budget and with no post implementation issues reported

• System is being used globally 24 x 7

• Simpler and more usable user interface (both mobile and desktop) reduced average time to complete an approval by 2 minutes

• 2 minute reduction per approval equates to more than GBP 200,000 per annum saving at standard internal cost equates to payback on project of less than 12 months

• Platform can now be leveraged to easily install additional Fiori applications

• Intuitive enough training program was not required

• Well received by user-base “- I just used the new approval interface with SAP. Amazing difference! Really really good development. Makes things so much easier”

Challenges

• Prerequisites to support mobile solutions were not in place

• Single sign-on solution proved most difficult element of project

• Performance problems with inital remote access method forced a

redesign late in the process

• SAP Fiori product issues, particularly on Android

• Attachments proved more problematic than anticipated

Lessons Learnt

• Ensure the pre-requisites to support mobile capabilities are present

• Providing users with functionality early and often improves delivery

• Unexpected challenges (attachments, single sign on) proved more difficult to deliver than the software

• Don’t underestimate the value of even basic mobile capabilities

• Don’t underestimate the efficiency gains from improved usability

• Don’t be surprised how little feedback you’ll receive if it works well

Screenshots – Launch Pad

Screenshots – Approve Travel Expenses

Screenshots – Approve Travel Expenses

Screenshots – Approve Travel Expenses

Screenshots – Approve Travel Expenses

Screenshots – Approve Travel Expenses

Questions?