Have your cake and eat it: Build unique solutions on common platforms   Jonathan Vaughan Managing Partner [email_address] ...
Typical enterprise application architecture Computers Networks Applications Information Archetypal business process – the ...
Enterprise application issues <ul><li>Complexity burden </li></ul><ul><ul><li>Business models change faster than software ...
Wikipedia – SaaS: On Demand enterprise applications <ul><li>Network-based access to, and management of, commercially avail...
Enterprise application implementation barriers All characteristics of traditional systems  implementations Long Time Frame...
End user application adoption factors Easy to use Immediate benefits Organizational support Maintainable customization Bus...
On Demand  - a new enterprise application environment Nautilus: Expansion over time Cornucopia: The horn of plenty On Dema...
Traditional software adoption curve Time Pioneers Early Adopters Mainstream Late Adopters Product Development Market Devel...
Hidden costs of traditional on-site technology <ul><li>Integration </li></ul><ul><ul><li>Spaghetti architectures </li></ul...
On Demand software adoption curve Time Pioneers Early Adopters Mainstream Late Adopters Product Development Market Develop...
CRM - Public Sector starting point  <ul><li>Public Sector Traditional CRM Examples </li></ul><ul><ul><li>Marketing and Pub...
But needs go well beyond CRM <ul><li>Public Sector Beyond CRM Examples </li></ul><ul><ul><li>Customer Service </li></ul></...
Public Sector signs of success  <ul><li>Implementing On Demand solutions </li></ul><ul><ul><li>A strong foundation for bus...
Customization of On Demand applications <ul><li>Customization Pros </li></ul><ul><ul><li>Implementation politics </li></ul...
On Demand integration challenges <ul><li>Data Integration  – internal records </li></ul><ul><li>Transaction Integration  –...
On Demand accelerates innovation <ul><li>Architectural framework </li></ul><ul><ul><li>Standardized, scalable, tested </li...
On Demand considerations <ul><li>Review SaaS vendors / solutions </li></ul><ul><li>Leverage standard application meta-data...
Upcoming SlideShare
Loading in...5
×

Jonathan Vaughan - Have your cake and eat it

284

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
284
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Jonathan Vaughan - Have your cake and eat it

  1. 1. Have your cake and eat it: Build unique solutions on common platforms Jonathan Vaughan Managing Partner [email_address] Time and Tide wait for no man
  2. 2. Typical enterprise application architecture Computers Networks Applications Information Archetypal business process – the form
  3. 3. Enterprise application issues <ul><li>Complexity burden </li></ul><ul><ul><li>Business models change faster than software </li></ul></ul><ul><ul><li>Business applications need process and data integration </li></ul></ul><ul><ul><li>Legacy barnacle build up </li></ul></ul><ul><li>Internal application limitations </li></ul><ul><ul><li>One shot development process </li></ul></ul><ul><ul><li>Hand crafted customization </li></ul></ul><ul><li>ERP package limitations </li></ul><ul><ul><li>Mass customization costs </li></ul></ul><ul><ul><li>On-site platform integration and support requirements </li></ul></ul>
  4. 4. Wikipedia – SaaS: On Demand enterprise applications <ul><li>Network-based access to, and management of, commercially available (i.e., not custom) software </li></ul><ul><li>Activities that are managed from central locations rather than at each customer's site, enabling customers to access applications remotely via the Web </li></ul><ul><li>Application delivery that typically is closer to a one-to-many model (single instance, multi-tenant architecture) than to a one-to-one model, including architecture, pricing, partnering, and management characteristics </li></ul>Strengths: Location, Time, and Platform independence Concerns: Data access, Security, Performance, Support, Application fit Weaknesses: Browser interface, Real Time capabilities, Legacy integration
  5. 5. Enterprise application implementation barriers All characteristics of traditional systems implementations Long Time Frames Large Organizational Impact Major Process Changes High Up Front Costs The consumer web succeeds by reversing these factors (eBay, Google, etc.) Packaged ERP systems typically cost 3 - 4 times the license cost to implement The On Demand Service model also reverses these factors Historically major internal systems projects have greater than 50 % failure rates <3 month implementations Flexible data sharing Multi-phase delivery Predictable variable costs
  6. 6. End user application adoption factors Easy to use Immediate benefits Organizational support Maintainable customization Business driven roll out in accordance with organizational priorities Active information Dashboards show the value of information and track key metric Evolution Enhanced services support continued innovation Web GUI Consistent Graphical User Interface can be learned quickly
  7. 7. On Demand - a new enterprise application environment Nautilus: Expansion over time Cornucopia: The horn of plenty On Demand suppliers regularly: Upgrade infrastructure Increase capacity Improve functionality Extend partner networks On Demand solutions provide: Best practice building blocks High availability Ubiquitous access Business alignment: Integrated active information
  8. 8. Traditional software adoption curve Time Pioneers Early Adopters Mainstream Late Adopters Product Development Market Development Product Decline Cost Impact of obsolescence Function
  9. 9. Hidden costs of traditional on-site technology <ul><li>Integration </li></ul><ul><ul><li>Spaghetti architectures </li></ul></ul><ul><li>Deployment </li></ul><ul><ul><li>Vendor driven upgrade cycles </li></ul></ul><ul><li>Change management </li></ul><ul><ul><li>Y2K scenario </li></ul></ul><ul><li>Business process redesign </li></ul><ul><ul><li>Timeliness of systems delivery </li></ul></ul><ul><li>Infrastructure support </li></ul><ul><ul><li>Budget iceberg </li></ul></ul><ul><li>Technology availability </li></ul><ul><ul><li>Pioneer syndrome </li></ul></ul>
  10. 10. On Demand software adoption curve Time Pioneers Early Adopters Mainstream Late Adopters Product Development Market Development Product Evolution Cost Relative value continues to improve Function
  11. 11. CRM - Public Sector starting point <ul><li>Public Sector Traditional CRM Examples </li></ul><ul><ul><li>Marketing and Public Relations </li></ul></ul><ul><ul><li>Fundraising </li></ul></ul><ul><ul><li>Business Development </li></ul></ul><ul><ul><li>Public Opinion Surveys </li></ul></ul><ul><li>Small groups of specialized users </li></ul><ul><li>Limited systems integration </li></ul><ul><li>Automating semi-manual processes </li></ul><ul><li>High value information </li></ul><ul><li>Small to medium scope systems </li></ul><ul><li>Customer management characteristics </li></ul>Common CRM Characteristics
  12. 12. But needs go well beyond CRM <ul><li>Public Sector Beyond CRM Examples </li></ul><ul><ul><li>Customer Service </li></ul></ul><ul><ul><li>Quality Assurance </li></ul></ul><ul><ul><li>Incident Management </li></ul></ul><ul><ul><li>Campaign Management </li></ul></ul><ul><ul><li>Information Exchange </li></ul></ul><ul><ul><li>Regulatory Compliance </li></ul></ul><ul><li>Users frequently use multiple systems </li></ul><ul><li>Systems integration is required for success </li></ul><ul><li>Systems may be a component in a larger process </li></ul><ul><li>Emphasis on process controls and tracking </li></ul>Varied Non-CRM Characteristics
  13. 13. Public Sector signs of success <ul><li>Implementing On Demand solutions </li></ul><ul><ul><li>A strong foundation for business processing </li></ul></ul><ul><ul><ul><li>Well honed core applications </li></ul></ul></ul><ul><ul><ul><li>Wide application customization within a common shared platform </li></ul></ul></ul><ul><ul><ul><li>Partner ecosystem </li></ul></ul></ul><ul><li>On Demand results </li></ul><ul><ul><li>Revolution is followed by evolution - under business control </li></ul></ul><ul><ul><ul><li>Implementable prototyping changes the development process </li></ul></ul></ul><ul><ul><ul><li>IS legacy barriers to change are overcome </li></ul></ul></ul><ul><ul><li>Actionable information is visible throughout the organization </li></ul></ul><ul><ul><li>Low risk, high gain – excellent Return on Innovation </li></ul></ul>
  14. 14. Customization of On Demand applications <ul><li>Customization Pros </li></ul><ul><ul><li>Implementation politics </li></ul></ul><ul><ul><li>Enterprise Integration </li></ul></ul><ul><ul><li>End user productivity </li></ul></ul><ul><ul><li>Unique services </li></ul></ul><ul><li>Customization Cons </li></ul><ul><ul><li>Implementation time </li></ul></ul><ul><ul><li>Support cost </li></ul></ul><ul><ul><li>Maintenance complexity </li></ul></ul><ul><ul><li>Limit advantages of common solutions </li></ul></ul><ul><li>Key On Demand Customization Requirements </li></ul><ul><li>Meta Customization – upgrade transparency </li></ul><ul><li>Open API – well defined interface points </li></ul><ul><li>Easy to use administrator tools </li></ul>Not just enterprise integration any more
  15. 15. On Demand integration challenges <ul><li>Data Integration – internal records </li></ul><ul><li>Transaction Integration – internal users </li></ul><ul><li>Application Integration – internal/external users </li></ul><ul><li>Process Integration – external activity </li></ul><ul><li>Information Integration – external data </li></ul><ul><li>Knowledge Integration – context driven internal/external information and activity </li></ul>ETL / Data Warehouse SOAP / EAI Web Portals / Services Messaging / Mash Ups Service Providers Enhanced collaboration
  16. 16. On Demand accelerates innovation <ul><li>Architectural framework </li></ul><ul><ul><li>Standardized, scalable, tested </li></ul></ul><ul><ul><li>Supports rapid iterative deployments </li></ul></ul><ul><li>The benefits of new technology are shared with all subscribers </li></ul><ul><li>Vendors are tackling key inter / intra organization challenges </li></ul><ul><ul><li>Identity </li></ul></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>Change Management </li></ul></ul><ul><ul><li>Resource Management </li></ul></ul><ul><ul><li>Performance Management </li></ul></ul>
  17. 17. On Demand considerations <ul><li>Review SaaS vendors / solutions </li></ul><ul><li>Leverage standard application meta-data </li></ul><ul><li>Use a Service Oriented Architecture (SOA) - Loosely coupled data and process integration </li></ul><ul><li>Align cost models with business value </li></ul><ul><li>Recognize evolving customer expectations </li></ul><ul><li>Manage IT Transition </li></ul><ul><ul><li>Central data center vs distributed computing </li></ul></ul><ul><ul><li>Internal apps vs ERP </li></ul></ul><ul><ul><li>Internal staff vs Outsourcing </li></ul></ul>Simple Rapid Application Deployment
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×