Proven approaches for Legacy Systems Modernization

Transcription

1 Proven approaches for Legacy Systems Modernization Dr. Setrag Khoshafian, Chief Evangelist

2 Agenda: Legacy Modernization Through BPM The Pain Points for Legacy Modernization BPM Suites For Modernizing The Enterprise Roadmap for Modernization 2

3 The Challenges and Problems of Legacy 3

4 Legacy and ERP Pain Points Extensive Manual Intervention Expensive & Error prone manual solutions to handle Exceptions: e.g. to handle suspended processes Millions of lines of custom code to handle sophisticated logic No Transparency Embedded & Ossified business policies and procedures No Auditing Difficult to maintain and change Infrastructure Service Service Service Service ERP 1 Legacy 1 ERP 2 Legacy 2 4

5 So why do we needed Legacy Modernization? Why is it so difficult for me to have complete visibility of my operations? How can we re-use our solutions? Why is there so much replication? Why do changes take such a long time? How can I align my systems to my customer or business goals? Why Can t I have a solution a case across multiple silos? 5

6 Agenda: Legacy Modernization Through Pega BPM The Pain Points for Legacy Modernization BPM Suites For Modernizing The Enterprise Roadmap for Modernization 6

7 BPM Suite: Continuous Improvement Cycle Directly Capture Objectives: Eliminate Execution Gaps & Efficiently Build Enterprise Solutions Monitor, Improve & Optimize Business Performance Change, reuse & Specialize Automate Work & Manage Dynamic Cases 7

8 Agile Business Applications Change, reuse & Specialize In-House Technology Solutions: Legacies BPM & Frameworks Packaged Applications 8

9 Service Consumer Connectors BPM Service Producer Services ESB 1 ESB 2 9

10 Manual Toggling Between Applications / Manuals / Experts 10

11 Example 1: As-Is State Claims workers switch & toggle multiple screens: IT and Operator Policies (business rules) need to be made in different systems: IT and Business Little visibility, governance and control of work: Operator and Business 11

12 Example 1 (cont.): BPM Suites Solution Changes made in one BPM Enterprise repository: IT and Business Business Empowered to make changes to the rules: Business and IT Workload Balance: Operations and Business Eliminate some of the incumbent systems: IT Manage the Service Levels: Operations and Business 12

13 Web Phone Mail Etc Dynamic Case Management Enterprise Repository Agility Layer Integration Plumbing HR Legacy Finance ERP ECM DBMSs Integration Plumbing Exceptions Case Management Enterprise Repository 13

14 Agenda: Legacy Modernization Through BPM The Pain Points for Legacy Modernization BPM Suites For Modernizing The Enterprise Roadmap for Modernization 14

15 Less Visibility Business Visibility High Visibility Think Big Start Small Impact/Risk Matrix: More Risk Complexity Less Risk 15

16 Selecting the Low Hanging Fruit Slivers for Modernization Business Value: How important will it be to the stakeholders Variability / Agility Measure: How frequently will policies and procedures change or how frequently are they changing (e.g., in an existing deployment) Maintainability Measure: How expensive is it to maintain the current legacy or custom code? Complexity Measure: For Wrap opportunities: How much effort will it be integrating with the ERP/Legacy Systems. Re-Use and Specialization Measure: How re-usable/specialize-able will the solution be? Automation Measure: How pervasive are the manual handoffs 16 Business Rules Measure: How pervasive are the sophisticated rules

17 BPM Iterative Methodology Slivers Direct Feedback Sticky Process Discovery Collaborative Feeds Application Process Discovery Profiler / Application Profiler Live Updates Unit Auto Test & Test Management Framework Project Management Framework Status Reporting and Governance Continuous Documentation Transition Reporting & BI Continuous Improvement 17

18 Enterprise Architecture: the Blueprint for the enterprise Business Architecture Information Architecture Application Architecture Infrastructure Architecture 18

19 Enterprise Architecture Frameworks and Methodologies The Zachman Framework Proliferation for Enterprise of Models and Artifacts The Federal Enterprise Architecture The Open Group Architectural Big Framework Bang. (TOGAF) Not agile OMG s Model Driven Architecture Difficult to achieve alignment with strategy. Many others 19

20 IT Infrastructure Security Static - Consistent System to System Increased Business Value Increased Agility Guided Human Interactions Business Agility In BPM Suite Layer 1. Directly Capture Objectives BPM COA 2. Dynamic Enterprise Repository 3. Automate Dynamic Cases ESB 1 ESB 2 Solution and Service Stack 1 Application Server Stack 2 Application Server Stack 3 20 HR Legacy Finance ERP ECM DBMS

21 From EA to BPM COA Multiple Layers Artifact Heavy: Many Models Mostly IT Focused Structured Core BPM Layer Executable Models Customer/Citizen Focused Dynamic and Adaptive 21

22 Mobile and Social Enterprise Collaboration HR Legacy Finance ERP ECM DBMS 1. Directly Capture Objectives Z/Os Enterprise, Private, or Public Cloud Deployment Business Performance BPM COA 2. Dynamic Enterprise Repository ESB EAI - MOM Application Server Clusters Windows Solaris AIX Linux 3. Automate Dynamic Cases HP UX Enterprise Applications and Content Integration 22

23 Controlled Migration Stay open for business while you build a new way of working Business Intent Driven Evolution Legacy Business componentes New components New business needs Add / Replace Functionality 23 New application