APPLICATION EFFICIENCY MEASUREMENT MODEL (AEMM)

1. APPLICATION EFFICIENCY MEASUREMENT MODEL (AEMM) using‘COPARIS framework’

2. PRESENTATION PATH 1 1 2 2 4 3 3 4

3. COPARIS Design Framework

4. What is COPARIS • PolarisFT believes that an effective IT Ecosystem has exactly 7 attributes: • Customer Experience – are the end users happy with their experience? • Operations – Is the Operation’s team comfortable maintaining the environment? • Performance – Is the ecosystem stable, performing and predictable? • Analytics – Does the IT landscape deliver relevant information to the decision makers? • Risk – Is risk management inbuilt into the IT stream? • Integration – Do individual components interface effectively with each other and other systems? • Security – Is our IT safe against external attacks and internal misuse? • PolarisFT has built a COPARIS framework centered on the above 7 attributes.

5. GARTNER EXP WORLDWIDE SURVEY WITH 1600 CIO’s O C P A C O A I C R S C

6. COPARIS Attributes  Design Thinking Targets • Design Objectives L0 were shaped from COPARIS attributes. These objectives aim to meet or exceed real world IT requirements. • This gives us a single, unified and complete starting point for ‘Design Thinking’ D2 D3 D4 D5 D6 D7 D1 Customer Experience Operations & support Performance & Scalability Analytics & Reports Risk Security Integration 1-Click Navigation Monitoring 200 msec STP D3 Reports 99.99 Availability Configurable User Identity & Role Management 1-Minute Data Entry Zero Manual Intervention 2 sec Screen Rendering D5 Dashboards 100% Reliability Seamless Integration Hack Proof Intuitive M180 30 min EOD Flexibility Data Integrity Non-Repudiation Rich UI Self Diagnostic Scalability Risk Management Stability

7. Targets  Design Thinking  Implementation Techniques D2 D3 D4 D5 D6 D7 D1 Customer Experience Operations & Support Performance & Scalability Analytics & Reports Risk Security Integration Caching Business Analytics Tool driven Authentication & Authorization Service SLAs Quick Navigation Cluster Deployment Tool Driven Interfaces Minimal Data Transfer Multi-dimensional drill-down Minimal Key Strokes ASOD Entitlements Event Monitoring Hot Deployment Standard Protocols & Data Formats Optimal Resource Usage V3 Data Operational Analytics Infra Security Instant Validations Guaranteed Processing Real Time / Single Txn Handling Infra / SQL Tuning Administration Bulk Processing Tool driven Concurrent Txn Updates Batch / Bulk Data handling Web Vulnerabilities Operational Data Store (ODS) Contextual IADT Workspaces Txn Atomicity Auto Scheduled Jobs Service Orientation Confidentiality Pro-active Risk Mitigation Domain Data Standards Message Integrity Background Processing Auto Event Handling Uniformity & Consistency Comprehensibility 1-Click Deployment Interface & Service Catalog Maker Checker Digital Signing Analytics Data Store Screen Ergonomics Auto-Maintenance Single Scan Batch Auditing & Compliance Interactivity No Recon Look Ahead Batch Personalization Automated Transaction Initiation Internationalization Point of Failure Re-processing Aesthetics Configurable Business Processes / Rules RIA Technology & Framework Based Design To Change Ease of Learning STP Traceability

8. COPARIS TREE COPARIS & BUSINESS

9. COPARIS INDEX to ‘Change The Bank’ CHANNEL BASED APPLICATIONS ( heavy on front end) C O P A R I S BACK OFFICE APPLICATIONS ( heavy on processing) C O P A R I S High Medium Low

10. What is AEMM

11. Design  Measure Attainment  AEMM • An application must satisfy requirements – including the ones that the customer did not state. • This completeness stems from attaining Design Objectives. • “Are these design objectives met” – are guided by a set of established implementation techniques (Design Techniques L0) • “Are these design objectives met” – must be measurable. • AEMM starts with a set of questions that verify and measure the completeness of objectives fulfillment. The questions are derived from PolarisFT Design Objectives L0. • This results in COPARIS Index (or AE Index) for the application • COPARIS Index must be viewed against requirements – It is a score card, not a report card. • This is later followed with finalization of key findings and ends with concrete action items as implementation roadmap

12. Sample Questions

13. APPLICATION EFFICIENCY MEASUREMENT MODEL (AEMM) Weighted average score arrived based on the aspects of COPARIS framework along with the purpose of the application like Channel based, back office.. Measurement arrived based on C,O,P,A,R,I,S eg: for C –> Intuitive –> Uniformity and Consistency Measurement arrived based on Usability, Hygiene, Flexibility at the lowest level

14. AEMM Interpretation

15. AEMM Context • To ‘Change the Bank’, there must be concrete action items. Complete Portfolio upgrade is tenuous at best; impractical in general. • People may not know or understand the entire IT. But they do know the applications they use. • Concrete action items can be identified at application level • Benefit – Pilot Approach: Verify Business Case by piloting AEMM on one application Retail Banking How to change the Bank? Action Item List Mobile Banking Internet Banking App 1 Retail Banking Corporate Banking …. App 2 Repeat the process

16. INFERENCE MATRIX (REFERENCE RANGE) CHANNEL BASED APPLICATION Outcome shows efficiency index of every aspect of the application BACK OFFICE APPLICATION

17. SAMPLE COPARIS SCORE CARD to ‘Change The Bank’ Methodology to arrive AE Index Customer satisfaction index is low

18. SAMPLE COPARIS SCORE CARD to ‘Change The Bank’ Methodology to arrive AE Index Ideal Operational efficiency

19. SAMPLE COPARIS SCORE CARD to ‘Change The Bank’ Methodology to arrive AE Index Performance Index needs improvement

20. SAMPLE COPARIS SCORE CARD to ‘Change The Bank’ Methodology to arrive AE Index Analytics view for customer is good

21. SAMPLE COPARIS SCORE CARD to ‘Change The Bank’ Methodology to arrive AE Index Risk management is ideal

22. SAMPLE COPARIS SCORE CARD to ‘Change The Bank’ Methodology to arrive AE Index Application Integration to be looked at

23. SAMPLE COPARIS SCORE CARD to ‘Change The Bank’ Methodology to arrive AE Index Security aspects to be evaluated

24. SAMPLE COPARIS SCORE CARD to ‘Change The Bank’ Methodology to arrive AE Index Internal customer satisfaction index is high

25. SAMPLE COPARIS SCORE CARD to ‘Change The Bank’ Methodology to arrive AE Index Analytics Index is very low

26. Who can Influence the score card? Solution Architects Application Main. team Central Processing Division Business Groups Technical Architects / Consultants Front desk group Risk team Relationship Managers

27. Benefits to the Bank • Benefits • Measurable and objective assessment as opposed to subjective judgments • Progressive addressing of pain points and improvement areas rather than a radical overhaul • Know where you stand based on AEMM Scores • Joint effort between us and you

28. AEMM Methodology The Implementation Approach

29. Assessment Approach

30. Assessment Methodology Optional Offering Preparation Phase Measurement Phase Recommendation Phase 1 6 7 • Understand Business Focus • Identify Current Applications • Capture Pain areas • Interview with Technical/Business stakeholders • AEMM scores should match pain areas • Highlight areas of improvement • Present Report 5 8 2 • Analyze AE scores • Map Business Process to Application • Map Pain Areas to Business Process • Map Business Focus to Applications • Divide Pain areas – Technology & Business • Propose approach & methodology 9 3 4 • Evaluate Applications in AEMM • Present the understanding • Obtain Concurrence • Plan & implementation approach

31. Assessment Team ** Discussion methodology, team members presence, timelines will differ based on the consulting requirement

32. Sample Report 1. Background 2. Objective 3. Scope 4. Audience 5. Systems studied _________________________________________ 1. Approach adopted 2. Steps to the <approach> 3. Why <Approach> 4. How suitable to the Bank _________________________________________ 1. Executive Summary 2. Application Efficiency Index 3. Our Key Findings L0 - Existing Process Pain Areas Business focus L0 - Process Recommendation L0 - Technical Recommendation

33. THANK YOU