O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Software Systems & Application Rationalization

3.823 visualizações

Publicada em

Publicada em: Tecnologia, Negócios
  • Entre para ver os comentários

Software Systems & Application Rationalization

  1. 1. Pipeline Pilot Break Silos and Rationalize Applications with a common Platform
  2. 2. Agenda <ul><li>Application Rationalization </li></ul><ul><li>PP Competency Centers Overview </li></ul><ul><li>Pipeline Pilot PP Competency Centers Characteristics </li></ul><ul><li>Implementation Steps </li></ul><ul><li>Leveraging Pipeline Pilot’ s PP Competency Centers Functionality </li></ul><ul><li>Measuring ROI </li></ul><ul><li>Keys to Success </li></ul><ul><li>Professional Services Engagements </li></ul>
  3. 3. What’s driving Application Rationalization Organizations need to find ways to make their IT budgets go farther than ever.
  4. 4. Existing Situation <ul><li>Multiple non-integrated systems </li></ul><ul><li>Multiple disconnected applications </li></ul><ul><li>Lots of duplicate and redundant data </li></ul><ul><li>Business keen to see merger benefits </li></ul><ul><li>Organisations look to IT for solutions </li></ul>
  5. 5. <ul><li>Too much information </li></ul><ul><li>Too much complexity </li></ul><ul><li>Too many challenges </li></ul><ul><li>Too little time </li></ul><ul><li>Scientific Business Intelligence vs. Intelligent Science </li></ul>Information Indecisions
  6. 6. Hard wired systems lack agility Registration ERP Test Today’s architecture can be rigid, costly and difficult to operate <ul><li>Proprietary technologies and skill sets </li></ul><ul><li>Multiple communication infrastructures </li></ul><ul><li>High cost of license, consulting and operation </li></ul><ul><li>Lots of turf control and organizational issues </li></ul>Inventory Test
  7. 8. Adaptability and Flexibility is key Registration ERP PARTNER SYSTEMS Test Inventory <ul><li>Enterprises need business agility </li></ul><ul><ul><li>Ever-changing business requirements </li></ul></ul><ul><ul><li>Implement new programs to attract/retain customers </li></ul></ul><ul><li>Business processes </li></ul><ul><ul><li>Streamline, refine, and measure </li></ul></ul><ul><li>Underlying IT infrastructure </li></ul><ul><ul><li>Flexibility </li></ul></ul><ul><ul><li>Capable of adapting to change </li></ul></ul>
  8. 9. <ul><li>What is silo thinking? </li></ul><ul><ul><li>Silos are an unwanted outcome of decentralized Management </li></ul></ul><ul><ul><li>They occur when departments or teams within an organization stand alone and do not interact effectively with other departments or teams </li></ul></ul><ul><ul><li>Each silo may be operating quite effectively in their own Right </li></ul></ul><ul><ul><li>But they don’t work together to create an optimal performance for the organization </li></ul></ul>Continuing with Silos
  9. 10. The non-enterprise landscape <ul><li>Applications exist in Silos </li></ul><ul><ul><li>Teams follow different architectures inside their applications </li></ul></ul><ul><ul><ul><li>Mix of 2 tier and 3 tier, service and non-service </li></ul></ul></ul><ul><ul><ul><li>Integration at database level </li></ul></ul></ul><ul><ul><ul><li>Different platforms, patterns and frameworks </li></ul></ul></ul><ul><ul><ul><li>No pattern/no frameworks </li></ul></ul></ul><ul><ul><ul><li>Different technologies/tool sets </li></ul></ul></ul><ul><ul><ul><li>No consistent way to do anything </li></ul></ul></ul>
  10. 11. Problem with Silos <ul><li>Higher cost of ownership </li></ul><ul><ul><li>Higher cost during development </li></ul></ul><ul><ul><ul><li>Reinvent the wheels </li></ul></ul></ul><ul><ul><ul><li>Hard to reuse </li></ul></ul></ul><ul><ul><ul><li>Hard to integrate different applications </li></ul></ul></ul><ul><ul><li>Higher cost for production support </li></ul></ul><ul><ul><ul><li>Support needs different skill sets </li></ul></ul></ul><ul><ul><ul><li>Lack of consistency prevents having a common production strategy </li></ul></ul></ul><ul><ul><li>Higher cost to maintain/enhance the applications </li></ul></ul><ul><ul><ul><li>Harder to find and fix bugs </li></ul></ul></ul><ul><ul><ul><li>Harder to enhance the code for customer’s new requirements </li></ul></ul></ul><ul><li>Higher learning curve for developers to switch teams </li></ul>
  11. 12. <ul><li>What is silo thinking? </li></ul><ul><ul><li>Silos are an unwanted outcome of decentralized Management </li></ul></ul><ul><ul><li>They occur when departments or teams within an organization stand alone and do not interact effectively with other departments or teams </li></ul></ul><ul><ul><li>Each silo may be operating quite effectively in their own Right </li></ul></ul><ul><ul><li>But they don’t work together to create an optimal performance for the organization </li></ul></ul>Silos
  12. 13. The Existing Landscape <ul><li>Applications are developed in Silos </li></ul><ul><ul><li>Teams follow different architectures inside their applications </li></ul></ul><ul><ul><ul><li>Mix of 2 tier and 3 tier, service and non-service </li></ul></ul></ul><ul><ul><ul><li>Integration at database level </li></ul></ul></ul><ul><ul><ul><li>Different platforms, patterns and frameworks </li></ul></ul></ul><ul><ul><ul><li>No pattern/no frameworks </li></ul></ul></ul><ul><ul><ul><li>Different technologies/tool sets </li></ul></ul></ul><ul><ul><ul><li>No consistent way to do anything </li></ul></ul></ul>
  13. 14. Problem with Silos <ul><li>Higher cost of ownership </li></ul><ul><ul><li>Higher cost during development </li></ul></ul><ul><ul><ul><li>Reinvent the wheels </li></ul></ul></ul><ul><ul><ul><li>Hard to reuse </li></ul></ul></ul><ul><ul><ul><li>Hard to integrate different applications </li></ul></ul></ul><ul><ul><li>Higher cost for production support </li></ul></ul><ul><ul><ul><li>Support needs different skill sets </li></ul></ul></ul><ul><ul><ul><li>Lack of consistency prevents having a common production strategy </li></ul></ul></ul><ul><ul><li>Higher cost to maintain/enhance the applications </li></ul></ul><ul><ul><ul><li>Harder to find and fix bugs </li></ul></ul></ul><ul><ul><ul><li>Harder to enhance the code for customer’s new requirements </li></ul></ul></ul><ul><li>Higher learning curve for developers to switch teams </li></ul>
  14. 15. Minimize System Infrastructure Expenses <ul><li>Reduce TCO Through Rationalization </li></ul><ul><ul><li>Reduce hardware and infrastructure expense across applications </li></ul></ul><ul><ul><li>More efficient use of software licenses </li></ul></ul>EFFICIENT USE OF PP Inventory 0 1 2 3 4 12pm 6am 12am 6pm CPUs required Registration 0 1 2 3 4 12pm 6am 12am 6pm CPUs required Combined 0 1 2 3 4 12pm 6am 12am 6pm CPUs required 3-CPU peak use 2-CPU peak use 3-CPU peak use
  15. 16. Practice: Consolidation REDUCE IT COST THROUGH SOFTWARE AND HARDWARE CONSOLIDATION Storage HW HW HW HW HW HW HW HW HW HW “ If you won’t let 30% of your employees sit idle, why wouldn’t you do the same with your hardware & software”
  16. 17. Pipeline Pilot Web Services Architecture .NET Applications ASP VB component C# component C++ component J2EE Applications JSP Servlet Java object EJB SOAP SOAP Other Applications SOAP PP Server Perl/ ‘R’ Java PP Script
  17. 18. What Are PP Competency Centers? <ul><li>PP Competency Centers </li></ul><ul><ul><li>Unique organizational entities that contain a mix of task, process and “brain trust” personnel </li></ul></ul><ul><ul><li>Eliminate redundant resources across the Enterprise </li></ul></ul><ul><ul><li>Leverage economies of scale across R&D groups </li></ul></ul><ul><ul><li>Lower total cost of ownership </li></ul></ul><ul><ul><li>Organizationally located within IT Department </li></ul></ul><ul><ul><li>Sometimes also known as Shared Services Environment </li></ul></ul>
  18. 19. Pipeline Pilot PP Competency Centers Characteristics <ul><li>Centralize Operations for all Pipeline Pilot implementation projects </li></ul><ul><ul><li>Efficient and effective centralized operations vs. separate deployments </li></ul></ul><ul><ul><li>Charge Back Model based on usage </li></ul></ul><ul><li>Provides pool of resources for all Pipeline Pilot projects </li></ul><ul><ul><li>Resources include reusable infrastructure components, best practices guides </li></ul></ul><ul><li>Development Framework </li></ul><ul><ul><li>Help R&D groups in selecting appropriate Pipeline Pilot Component collections to meet R&D requirements </li></ul></ul><ul><ul><li>Easily integrate with other tools in Informatics solution delivery </li></ul></ul>
  19. 20. Pipeline Pilot PP Competency Centers Characteristics <ul><li>Provides Methodology for Rapid Application Development </li></ul><ul><ul><li>Methodology based on best practices </li></ul></ul><ul><li>Provides Interfaces for Efficient Deployment </li></ul><ul><ul><li>Security Integration </li></ul></ul><ul><ul><li>Portal, Web Site, Web Services </li></ul></ul><ul><li>Facilitates Release Management </li></ul><ul><ul><li>Coordinates release schedules across environments </li></ul></ul><ul><ul><li>Provides Change Control Mechanism </li></ul></ul><ul><li>Establishes charge back model for Services </li></ul><ul><ul><li>Utilizes usage tracking mechanism </li></ul></ul><ul><li>Liaison to Accelrys R&D </li></ul><ul><ul><li>Interface to Accelrys Support and Engineering </li></ul></ul><ul><ul><li>Participate in Beta Testing </li></ul></ul>
  20. 21. Pipeline Pilot PP Competency Centers Implementation <ul><ul><li>Identify key personnel and staff PP Competency Centers </li></ul></ul><ul><ul><li>Assign and execute tasks to close identified gaps </li></ul></ul><ul><ul><li>Identify and migrate/deploy target apps to PP Competency Centers Environment </li></ul></ul><ul><ul><li>Leverage Pipeline Pilot’ s PP Competency Centers Functionality </li></ul></ul>Implementation Plan <ul><ul><li>Identify gaps between the current state of resources and processes and the desired state required to support PP Competency Centers goals </li></ul></ul>Gap Analysis <ul><ul><li>Determine current state of resources </li></ul></ul><ul><ul><li>Inventory hardware, software, licenses, etc. </li></ul></ul><ul><ul><li>Conduct skills assessment </li></ul></ul><ul><ul><li>Review existing processes and methods for existing deployments </li></ul></ul>Inventory of Current State <ul><ul><li>Define measurable goals and services to be provided by Pipeline Pilot PP Competency Centers </li></ul></ul><ul><ul><li>Define roles and responsibilities </li></ul></ul><ul><ul><li>Establish reporting structure </li></ul></ul>Define Pipeline Pilot PP Competency Centers Goals and Services
  21. 22. <ul><li>Leveraging Pipeline Pilot </li></ul><ul><li>Competency Centers Functionality </li></ul>
  22. 23. Leveraging Shared Services Functionality <ul><li>One System that caters to all requirements throughout the enterprise </li></ul><ul><li>PP Clustering Functionality </li></ul><ul><li>Usage and Error Logging </li></ul><ul><li>Archiving and Retrieval </li></ul><ul><li>Extensible Security Architecture </li></ul><ul><li>Custom utilities </li></ul>
  23. 24. Pipeline Pilot Clustering Benefits <ul><li>Powerful out-of-the-box clustering features </li></ul><ul><li>High availability </li></ul><ul><ul><li>Remain on-line continuously using redundancy </li></ul></ul><ul><ul><li>Fail-over </li></ul></ul><ul><ul><li>Disaster Recovery </li></ul></ul><ul><li>Performance </li></ul><ul><ul><li>Multiple active machines sharing workload </li></ul></ul><ul><ul><li>Maximize resource utilization via load balancing </li></ul></ul>
  24. 25. Usage and Error Logging <ul><li>Charge Back – charge back business units based on actual PP cluster usage </li></ul><ul><li>Return on Pipeline Pilot Investment – how well is Pipeline Pilot helping me achieve corporate goals? </li></ul><ul><ul><li>User adoption </li></ul></ul><ul><ul><li>Collections used/not used </li></ul></ul><ul><li>Capacity Planning – capacity planning for future applications and hardware purchases </li></ul><ul><li>Guide Development Efforts – Identify the most/least frequently used components </li></ul><ul><li>Security Monitoring </li></ul>
  25. 26. <ul><li>Keys to Success </li></ul>
  26. 27. PP Competency Centers Best Practices <ul><li>Define process for bringing new applications on the PP Competency Centers </li></ul><ul><li>Publish rules of engagement and expected SLAs for customers </li></ul><ul><li>Establish matrix to identify best tools/component collection to meet broad range of Informatics requirements </li></ul><ul><li>Establish and publish reusable interfaces – security, portal, etc </li></ul><ul><li>Develop reusable load testing scripts to proactively identify and assess hot spots/bottlenecks in system </li></ul><ul><li>Define process to migrate application from the various environments </li></ul><ul><li>Automated alerting to track trouble tickets for efficient resolution </li></ul><ul><li>Publish and maintain Standard Operating Procedures for Pipeline Pilot administration activities </li></ul><ul><li>Establish Charge Back Model based on usage tracking </li></ul><ul><li>Create Capacity Planning Model for Pipeline Pilot PP Competency Centers to proactively assess resource requirements of applications </li></ul>
  27. 28. Measuring ROI <ul><li>Productivity of Resources </li></ul><ul><ul><li>Consolidation of Equipment and Personnel </li></ul></ul><ul><ul><li>Economies of Scale </li></ul></ul><ul><ul><ul><li>Reduced licensing costs </li></ul></ul></ul><ul><ul><ul><li>Volume discounts </li></ul></ul></ul><ul><li>Reduction in Time to Value </li></ul><ul><ul><li>Accelerated deployment times to meet R&D objectives </li></ul></ul><ul><li>Entry Costs for PP Competency Centers Applications </li></ul><ul><ul><li>Compare costs to “going it alone” </li></ul></ul><ul><li>Leverage Low Cost Resources </li></ul><ul><ul><li>Established Methodology and Processes </li></ul></ul><ul><ul><li>Farm out pieces of project lifecycle to low cost resource provider </li></ul></ul>
  28. 29. Professional Services PP Competency Centers Engagements <ul><ul><li>Roadmap, planning & strategy engagement </li></ul></ul><ul><ul><ul><li>Draft mission </li></ul></ul></ul><ul><ul><ul><li>Define structure </li></ul></ul></ul><ul><ul><ul><li>Develop ROI metrics </li></ul></ul></ul><ul><ul><ul><li>Create phased action plan </li></ul></ul></ul><ul><ul><li>Roadmap implementation engagement </li></ul></ul><ul><ul><ul><li>Technical audit and current inventory </li></ul></ul></ul><ul><ul><ul><li>Gap analysis </li></ul></ul></ul><ul><ul><ul><li>Execute detailed implementation plan </li></ul></ul></ul><ul><ul><li>Certification engagement </li></ul></ul><ul><ul><ul><li>Review development and deployment processes </li></ul></ul></ul><ul><ul><ul><li>Review operating procedures </li></ul></ul></ul><ul><ul><ul><li>Technical audit of current deployment </li></ul></ul></ul><ul><ul><ul><li>Training and certification for PP Competency Centers Staff </li></ul></ul></ul>

×