6 A session 6 A Modernization Strategy Is

6 A (session 6) A Modernization Strategy Is More Than Just About 'Technology' Lee Dare, Finzsoft Solutions Limited September 20, 2007 3 rd Annual Plex/2 E Worldwide Users Conference

Biography > Lee Dare > Finzsoft Solutions Limited > 15 years 2 e/Plex. Developing and managing teams. § Debt management § Application Processing § Core Banking. > Auckland, New Zealand. , lee. dare@finzsoft. com or leedare@talk 21. com > Other facts § Keen footy fan. 2 3/15/2018 *

Agenda > Overview of Finzsoft & Technical Evolution > Modernisation Scope and options for 2 e users > Organisational Impact > 2 e Model Management/Maintenance § ‘Model Tidy’ Project § Automated Development Standards > Customer Impact > Where from here? 3 3/15/2018 *

Overview of Finzsoft > Established in 1987 > Created ‘Sovereign’ in 1992 > Listed on NZX > 50+ staff, 45 Sites in 4 countries > Customers include § St George Bank § Nissan Finance § Volkswagen Financial Services 4 3/15/2018 *

Modernisation Drivers > Application looks old. > Fashion police and marketplace > Application size, higher maintenance costs > Reaction time > Less sales despite more marketing effort > Availability of skilled staff. System i (. NET? ) > Opportunity to redesign and rethink direction 5 3/15/2018 *

Client (5250 – AS 400) Inbound Interfaces (Batch) Conversion Real-time Interfaces Core Business Rules (RPG – AS 400) Legacy Reporting/Publishing Trend Analysis Loan Origination Credit Scoring Teller Memos Funding Lending Products Cash Management Sovereign Database (DB 2 – AS 400) Publishing 6 3/15/2018 * Imaging, Mail and EIS Conversion Real-time Interfaces

Inbound Interfaces (Batch) AUTHS Workflow Internet Banking IVR Global Rich Client Interface New. Look GUI Older Client (5250 – AS 400) Core Business Rules (RPG – AS 400) Legacy Reporting/Publishing Trend Analysis Loan Origination Real-time Interfaces Teller Memos Funding Conversion Credit Scoring Lending Products Cash Management Imaging, Mail and EIS Conversion Real-time Interfaces Sovereign Database (DB 2 – AS 400) Publishing PPSR 7 3/15/2018 * Credit Bureau Services Moto. Check/ REVS Other. GL etc Securitisation

Modernisation Scope > Determine Modernisation Scope/Goals § Architecture, Platform(s) and Software § Look ‘n’ Feel, Accessibility and localisation § Business goals § Timeline § Budget § Project resource § Phased or Big Bang 8 3/15/2018 *

Modernisation Scope > Investigate ALL technology options and candidly rate versus your modernisation goals > Up skill your development team > Involve your development team > No ‘Silver Bullet’ 9 3/15/2018 *

Modernisation Scope Just do it! 10 3/15/2018 *

Modernisation Options > 2 e to Plex utilising bridge > 2 e Backend – Own Java/. NET Client > RPG/RPGLE to 3 GL (Java/. NET) > Web Option/Quickstep > Screen Scrapper (i. e. New. Look) > Rewrite application and client logic > Create your own generator? > Any combination of the above or others 11 3/15/2018 *

MODERNISATION/MIGRATION PLATFORM NEUTRAL DEVELOPMENT SOVEREIGN TIDY NIGHTLY BUILDS AUTOMATED STANDARDS MODEL TIDY ** IDE SDLC DEVELOPMENT STANDARDS CHANGE MANAGEMENT FUNCTION PRIMITIVES BUSINESS OBJECT COMPONENTS DATABASE SCALABILITY ORGANISATION STRUCTURE (PODS) 12 3/15/2018 * TECHNOLOGY STRATEGY TARGET FRAMEWORK AUTOMATED TESTING

Hybrid Developers > 2 e/business experts > New technology expert § Framework and technical patterns § Standards > Identify appropriate developers § Technical and conceptual differences § Accept, then manage resistance to change > Avoid technology focused teams § Jealousy and division § Business expertise v technology 13 3/15/2018 *

P. O. D. S People Orientated Development Strategy > What are P. O. D. S. § Centralised development ownership – Design, development & quality assurance § Technology agnostic § Portability and scalability – Reusable building blocks (Lego) – Create and deprecate as priorities/projects dictate – Remote development teams § Business solutions focused § Organisation role awareness/appreciation 14 3/15/2018 *

2 e Model Management/Maintenance > Review current model § Easier to port/migrate a clean application § Easier to ‘Fix Up’ issues in current model § Rebuild entire application – Files & access paths – Functions § Tidy up your model 15 3/15/2018 *

MODEL TIDY NIGHTLY BUILDS TRIGGER REPLACEMENT PRIMITIVES *TEMPLATES SCOPING ENTITIES MODEL CORRUPTION ILE IMPACT YCHKMDL YCHKDTAMDL YCHKFUNACT FUNCTION TIDY (Iterative) RETRO FIT FUNCTION NAMING STDS SOURCE MODIFIERS SQL RPG UNUSED FILES & LOGICALS UNUSED INT/EXT FUNCTIONS FOOTPRINT CONSOLIDATION REVIEW SYNON 8. 1. 1. 1 or now 8. 1. 2 16 3/15/2018 * DEVELOPMENT STANDARDS USER SOURCE/PROGRAM DEPRECATION

Automated Development Standards > Review an entire model periodically > Common programming standards § Performance § Coding mistakes § Naming standards § Program interfaces § Style § Best practices > Allow for exceptions 17 3/15/2018 *

Customer Impact > Some customers don’t want a GUI § Training § Familiarity and trust with existing system § Hardware costs > Some may view as opportunity to review competitors offerings § Ensure your solution and roadmap has everything required to compete 18 3/15/2018 *

Internal Impact > Supporting a distributed platform § Staff Training (Product/Operations/Support) § Issue Tracking. Simplifying screen issues > Platform independent testing/compatibility § Balancing, Load and Functional Testing § More benchmarking > New technologies/databases. § DDL/DDS or CHAIN/SELECT § Target environment DBA’s § Environment management 19 3/15/2018 *

Where to from here? You > Review your processes > Automate standards > Shape your team > Complete ‘Model Tidy’ > Investigate all options > Nightly build > Complete modernisation project > Network and exchange ideas 20 Finzsoft Solutions > Network and exchange ideas 3/15/2018 *

Q&A ? 21 3/15/2018 *