SlideShare a Scribd company logo

IT Modernization For Process Modernization

•Download as PPT, PDF•
•
Dheeraj Remella
Dheeraj Remella

The slides from a recent webinar I had delivered regarding why IT Portfolio Modernization is important for a successful Business Process Transformation.

1 of 29
IT Modernization for Process Modernization
Introduction Dheeraj Remella, Solutions Architect @ Nexaweb Technologies Past Experience around Business Process Refinement: Call Center – A large call center business process outsourcer in Omaha, NE Insurance Industry – A multi LOB insurance company in Hartford, CT Healthcare Insurance – BCBSMA, Architect governing Health& Wellness Management and Claims Processing divisions LinkedIn Profile: http://www.linkedin.com/in/dremella
Business Innovation Meets Legacy Systems Nothing Happens Reasons: Legacy Systems are hard to change Scarcity of resources or high costs Don’t render themselves for modern capabilities Legacy technology obsolete and no support Initiative too costly. And it is working, let us not fix it. Let us modernize our legacy systems. Where do we start???
3Ps and 3Rs for safe and successful modernization 3P People Process Portfolio (Application and Data) 3R Risk Reduction Return on Investment Rapid Time To Market
3Ps – Understand your Organization
People First step to understand your business – know your people Identify divisions Identify divisional roles What do these roles do? Catalog current responsibilities
People
Process Next logical step from the catalog of responsibilities Sequence of things being done, highlights dependencies General rule of thumb, Fit on an A3 sheet (Lifted from The Toyota Way) Sub processes (again fit on an A3 sheet) Walk the floor to understand inefficiencies – useful to identify and measure wastes (metrics and critical success factors are useful) Redefine the process (the future state/vision) removing the wasteful activities
Process - Example
Portfolio List the applications and data sources that support every business sub process. Process and applications could highlight swivel-chair operations Good candidates for modernization Buy, Sell or Hold Hold is good for modernization – non commodity activities that differentiate you from your competition
Process to Applications mapping – Fictional Sample Pre Authorization Request Claims Adjudication Fax Server ClaimAdj (Mainframe) AuthReq (Mainframe) ClaimProc (Visual Basic) PaymentPolicy (Visual Basic) Axway (File transfer for batch processing) MedPol (PowerBuilder) ClaimDB (SQL Server – DB for ClaimProc)
3Rs – Guidelines for Modernization Methodology
Risks Scariest risk – loss of business logic that is embedded in the current systems How to manage concurrent changes? Is the new/modern application going to require retraining of the end users? Would the modernized code be maintainable? Can I find the resources to develop and maintain the new application
How to reduce risks Automated Code Analysis and Reverse Engineering Rapid development paradigm Application platform that supports the richness of experience of legacy (especially Client/Server) applications Target architecture that has a short on-ramping period Modernize to open standards
Return on Investment Current Expenses: Current operational cost to maintain the legacy application Cost of lost opportunity Cost of lost productivity Cost of missed new business Cost of modernization Time to break even
How to choose approach Predictable cost and schedule Target technology that could allow minimize retraining Phased enhancement implementation Technology that would decrease total cost of ownership over 5 years or beyond Technology that would be vendor supported
Rapid Time To Market How fast can I get there? How fast can I implement new business needs? How fast can I implement process changes? How fast can I patch any exceptions found? Can I deliver business enhancement requests in small batches quickly?
How to ensure rapid TTM Automated transformation Web target architecture Centralized availability instead of distribution mode as in Client/Server applications Easily scalable for high loads Readily available to migrate to Cloud infrastructure Rapid application development Prioritized business needs
Modernization with Nexaweb Technologies
Nexaweb: Application Transformation Mission To transform growth-limiting legacy applications into modern web solutions accessible to anyone from anywhere, enabling new business models fueling growth and expansion for our customers and partners How Cloud transformation software & services Repeatable approach Expert project leadership Fixed-price, fixed-time projects Market Status 200 satisfied customers 450 applications transformed Headquarters in Boston, with offices in Tokyo and Amsterdam
Nexaweb Makes Transformation Possible Over 450 applications transformed Repeatable approach Cloud transformation software & services Fixed-cost, Fixed-time projects
Repeatable Approach: Typical Nexaweb Engagement DEPLOY TRANSFORM CAPTURE TRANSFORMATION STRATEGY Duration: ~2-6 weeks Activities: App Portfolio Review Rationalize user adoption, value creation, transformation feasibility Deliverables: Roadmap-which apps to: Transform, Consolidate, Re-platform, Replace, End of Life, Leave As Is Prioritized Transformation Projects & Scopes Duration: 8-16 weeks Activities: Re-factor – Elminate bad/duplicate legacy code. Re-platform to Web w/ stable architecture Re-compose – Meet new requirements w/new workflows, UI content Deliverables: Working, tested, Cloud-based Java, Ajax, HTML application Duration: 3-6 weeks Activities: User Acceptance Testing Model Office set-up Tuning for different target platforms/ devices User training, adoption Seamless cutover with minimal downtime Deliverables: Multi-channel/multi-platform Cloud application Duration: 4-10 weeks Activities: Use automated tools to document legacy artifacts Deliverables: Reusable logic, UI, data mappings
Nexaweb Technology Transformation tools & pre-built software speed up the project and lower cost & risk Eclipse IDE & declarative XML simplify RIA/Web 2.0 development & maintenance Pre-built frameworks for Java, Ajax – integrate legacy business logic with modern Web 2.0 UI Internet messaging with guaranteed delivery – recreate client/server experience on the web Zero-install deployment to any browser/device Automatic client software change management for lower admin costs Nexaweb Platform Any Browser (.NET, JVM) Any Desktop (Win., Linux, Mac) Mobile (OCC) J2EE Application Server (Servlet) XML/JSON SOAP/WSDL JMS Spring iBatis ESB Application Stack #1 Internet messaging bus for client/server communication Integrated workflow and rules engine Pre-built navigation, security and page management Service consumption, scalability and security Nexaweb Studio Application Stack #2 Application Stack #3 Application Stack #4 Application Stack #5 Ajax & HTML dojo, dojo.E, jQuery Java & Desktop Nexaweb XML and Swing
Why Nexaweb? Technology skills SOA, Java and Java EE Ajax, HTML5 and Web 2.0 Real time, high availability Industry experience Finance and banking Manufacturing Health care Design partnership Include your team members Design, development, QA Lower cost, remove dependency Nexaweb technology Open standards and open source Eclipse based for future maintenance Ensures a clean architecture and design Full lifecycle Architecture Development, Quality Assurance Project Management Application experience Call Center Lab Management Trading, etc. Our services enable effective transformation Combining technology and services to ensure projects are completed fixed time and fixed price
Next Steps 1st meeting to discuss: Your legacy application portfolio Your cloud/business application strategy Your application technology platform(s) Nexaweb experiences in your domain(s) Nexaweb transformation process and technology in depth
Q & A
Linked product slides
Nexaweb Cloud Reference Framework Messaging Bus Asynchronous messaging High throughput, low latency Workflow Engine XML configured, configurable workflow and state engine Rules Engine On the fly rule compilation Uses JBoss Drools rule processor JavaScript library Messaging, UI Based on dojo and jQuery Apache Wicket Apache open source framework for web based user interface development Spring Open source framework that simplifies Java EE development and deployment CLIENT SERVER HTML Rendered HTML for the user interface Data Access Layer Leveraging Spring data access a easy to use data access layer Authorization Per component, action, screen Simple to integrate Data Databases, web services, repositories External Authorizations X.509, LDAP, CAS, SSO Hardware tokens Nexaweb reduced the # of lines of new code we needed by 65%, cutting 18 months off our original transformation schedule.” “ Custom code Nexaweb framework External systems Integrated open source Reporting Module with filters, exports, navigation (optional module) Application specific Administration Module that includes hierarchy, editing, navigation Application specific
Nexaweb Cloud Reference Framework Messaging Bus Asynchronous messaging High throughput, low latency Workflow Engine XML configured, configurable workflow and state engine Rules Engine On the fly rule compilation Uses JBoss Drools rule processor Nexaweb Java Client XML based user interface Messaging Spring Open source framework that simplifies Java EE development and deployment CLIENT SERVER Java VM Java Virtual Machine for multi platform application development Custom code Nexaweb framework External systems Integrated open source Data Access Layer Leveraging Spring data access a easy to use data access layer Authorization Per component, action, screen Simple to integrate Data Databases, web services, repositories External Authorizations X.509, LDAP, CAS, SSO Hardware tokens If I can dream it I can do it with Nexaweb.” “ Reporting Module with filters, exports, navigation (optional module) Application specific Administration Module that includes hierarchy, editing, navigation Application specific

More Related Content

IT Modernization For Process Modernization

  • 1. IT Modernization for Process Modernization
  • 2. Introduction Dheeraj Remella, Solutions Architect @ Nexaweb Technologies Past Experience around Business Process Refinement: Call Center – A large call center business process outsourcer in Omaha, NE Insurance Industry – A multi LOB insurance company in Hartford, CT Healthcare Insurance – BCBSMA, Architect governing Health& Wellness Management and Claims Processing divisions LinkedIn Profile: http://www.linkedin.com/in/dremella
  • 3. Business Innovation Meets Legacy Systems Nothing Happens Reasons: Legacy Systems are hard to change Scarcity of resources or high costs Don’t render themselves for modern capabilities Legacy technology obsolete and no support Initiative too costly. And it is working, let us not fix it. Let us modernize our legacy systems. Where do we start???
  • 4. 3Ps and 3Rs for safe and successful modernization 3P People Process Portfolio (Application and Data) 3R Risk Reduction Return on Investment Rapid Time To Market
  • 5. 3Ps – Understand your Organization
  • 6. People First step to understand your business – know your people Identify divisions Identify divisional roles What do these roles do? Catalog current responsibilities
  • 8. Process Next logical step from the catalog of responsibilities Sequence of things being done, highlights dependencies General rule of thumb, Fit on an A3 sheet (Lifted from The Toyota Way) Sub processes (again fit on an A3 sheet) Walk the floor to understand inefficiencies – useful to identify and measure wastes (metrics and critical success factors are useful) Redefine the process (the future state/vision) removing the wasteful activities
  • 10. Portfolio List the applications and data sources that support every business sub process. Process and applications could highlight swivel-chair operations Good candidates for modernization Buy, Sell or Hold Hold is good for modernization – non commodity activities that differentiate you from your competition
  • 11. Process to Applications mapping – Fictional Sample Pre Authorization Request Claims Adjudication Fax Server ClaimAdj (Mainframe) AuthReq (Mainframe) ClaimProc (Visual Basic) PaymentPolicy (Visual Basic) Axway (File transfer for batch processing) MedPol (PowerBuilder) ClaimDB (SQL Server – DB for ClaimProc)
  • 12. 3Rs – Guidelines for Modernization Methodology
  • 13. Risks Scariest risk – loss of business logic that is embedded in the current systems How to manage concurrent changes? Is the new/modern application going to require retraining of the end users? Would the modernized code be maintainable? Can I find the resources to develop and maintain the new application
  • 14. How to reduce risks Automated Code Analysis and Reverse Engineering Rapid development paradigm Application platform that supports the richness of experience of legacy (especially Client/Server) applications Target architecture that has a short on-ramping period Modernize to open standards
  • 15. Return on Investment Current Expenses: Current operational cost to maintain the legacy application Cost of lost opportunity Cost of lost productivity Cost of missed new business Cost of modernization Time to break even
  • 16. How to choose approach Predictable cost and schedule Target technology that could allow minimize retraining Phased enhancement implementation Technology that would decrease total cost of ownership over 5 years or beyond Technology that would be vendor supported
  • 17. Rapid Time To Market How fast can I get there? How fast can I implement new business needs? How fast can I implement process changes? How fast can I patch any exceptions found? Can I deliver business enhancement requests in small batches quickly?
  • 18. How to ensure rapid TTM Automated transformation Web target architecture Centralized availability instead of distribution mode as in Client/Server applications Easily scalable for high loads Readily available to migrate to Cloud infrastructure Rapid application development Prioritized business needs
  • 19. Modernization with Nexaweb Technologies
  • 20. Nexaweb: Application Transformation Mission To transform growth-limiting legacy applications into modern web solutions accessible to anyone from anywhere, enabling new business models fueling growth and expansion for our customers and partners How Cloud transformation software & services Repeatable approach Expert project leadership Fixed-price, fixed-time projects Market Status 200 satisfied customers 450 applications transformed Headquarters in Boston, with offices in Tokyo and Amsterdam
  • 21. Nexaweb Makes Transformation Possible Over 450 applications transformed Repeatable approach Cloud transformation software & services Fixed-cost, Fixed-time projects
  • 22. Repeatable Approach: Typical Nexaweb Engagement DEPLOY TRANSFORM CAPTURE TRANSFORMATION STRATEGY Duration: ~2-6 weeks Activities: App Portfolio Review Rationalize user adoption, value creation, transformation feasibility Deliverables: Roadmap-which apps to: Transform, Consolidate, Re-platform, Replace, End of Life, Leave As Is Prioritized Transformation Projects & Scopes Duration: 8-16 weeks Activities: Re-factor – Elminate bad/duplicate legacy code. Re-platform to Web w/ stable architecture Re-compose – Meet new requirements w/new workflows, UI content Deliverables: Working, tested, Cloud-based Java, Ajax, HTML application Duration: 3-6 weeks Activities: User Acceptance Testing Model Office set-up Tuning for different target platforms/ devices User training, adoption Seamless cutover with minimal downtime Deliverables: Multi-channel/multi-platform Cloud application Duration: 4-10 weeks Activities: Use automated tools to document legacy artifacts Deliverables: Reusable logic, UI, data mappings
  • 23. Nexaweb Technology Transformation tools & pre-built software speed up the project and lower cost & risk Eclipse IDE & declarative XML simplify RIA/Web 2.0 development & maintenance Pre-built frameworks for Java, Ajax – integrate legacy business logic with modern Web 2.0 UI Internet messaging with guaranteed delivery – recreate client/server experience on the web Zero-install deployment to any browser/device Automatic client software change management for lower admin costs Nexaweb Platform Any Browser (.NET, JVM) Any Desktop (Win., Linux, Mac) Mobile (OCC) J2EE Application Server (Servlet) XML/JSON SOAP/WSDL JMS Spring iBatis ESB Application Stack #1 Internet messaging bus for client/server communication Integrated workflow and rules engine Pre-built navigation, security and page management Service consumption, scalability and security Nexaweb Studio Application Stack #2 Application Stack #3 Application Stack #4 Application Stack #5 Ajax & HTML dojo, dojo.E, jQuery Java & Desktop Nexaweb XML and Swing
  • 24. Why Nexaweb? Technology skills SOA, Java and Java EE Ajax, HTML5 and Web 2.0 Real time, high availability Industry experience Finance and banking Manufacturing Health care Design partnership Include your team members Design, development, QA Lower cost, remove dependency Nexaweb technology Open standards and open source Eclipse based for future maintenance Ensures a clean architecture and design Full lifecycle Architecture Development, Quality Assurance Project Management Application experience Call Center Lab Management Trading, etc. Our services enable effective transformation Combining technology and services to ensure projects are completed fixed time and fixed price
  • 25. Next Steps 1st meeting to discuss: Your legacy application portfolio Your cloud/business application strategy Your application technology platform(s) Nexaweb experiences in your domain(s) Nexaweb transformation process and technology in depth
  • 26. Q & A
  • 28. Nexaweb Cloud Reference Framework Messaging Bus Asynchronous messaging High throughput, low latency Workflow Engine XML configured, configurable workflow and state engine Rules Engine On the fly rule compilation Uses JBoss Drools rule processor JavaScript library Messaging, UI Based on dojo and jQuery Apache Wicket Apache open source framework for web based user interface development Spring Open source framework that simplifies Java EE development and deployment CLIENT SERVER HTML Rendered HTML for the user interface Data Access Layer Leveraging Spring data access a easy to use data access layer Authorization Per component, action, screen Simple to integrate Data Databases, web services, repositories External Authorizations X.509, LDAP, CAS, SSO Hardware tokens Nexaweb reduced the # of lines of new code we needed by 65%, cutting 18 months off our original transformation schedule.” “ Custom code Nexaweb framework External systems Integrated open source Reporting Module with filters, exports, navigation (optional module) Application specific Administration Module that includes hierarchy, editing, navigation Application specific
  • 29. Nexaweb Cloud Reference Framework Messaging Bus Asynchronous messaging High throughput, low latency Workflow Engine XML configured, configurable workflow and state engine Rules Engine On the fly rule compilation Uses JBoss Drools rule processor Nexaweb Java Client XML based user interface Messaging Spring Open source framework that simplifies Java EE development and deployment CLIENT SERVER Java VM Java Virtual Machine for multi platform application development Custom code Nexaweb framework External systems Integrated open source Data Access Layer Leveraging Spring data access a easy to use data access layer Authorization Per component, action, screen Simple to integrate Data Databases, web services, repositories External Authorizations X.509, LDAP, CAS, SSO Hardware tokens If I can dream it I can do it with Nexaweb.” “ Reporting Module with filters, exports, navigation (optional module) Application specific Administration Module that includes hierarchy, editing, navigation Application specific