1 / 30

The User Organized Enterprise

Ron Nunan Director of Connector Services Attachmate Corporation. The User Organized Enterprise. AGENDA. The Services Oriented Host Brief on SOA SOA beyond the ‘Service’ Requirements for existing systems Service Oriented Host Use Case Scenarios. WHY ARE WE TALKING ABOUT SOA?. “.

nedaa
Download Presentation

The User Organized Enterprise

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Ron Nunan Director of Connector Services Attachmate Corporation The User Organized Enterprise

  2. AGENDA The Services Oriented Host • Brief on SOA • SOA beyond the ‘Service’ • Requirements for existing systems • Service Oriented Host • Use Case Scenarios

  3. WHY ARE WE TALKING ABOUT SOA? “ A services-oriented architecture (SOA) approach to IT can bring agility and long-term savings to businesses. —PC Magazine, September 2004 ”

  4. SOA Is Part Of The Computing Cycle

  5. If a service is like a musical instrument... ...Then SOA is like an orchestra What Is A Service-Oriented Architecture?

  6. Let Services be Services and that’s all… …SOA takes care of all the things a services needs in order to be successful in the enterprise… Service Oriented Architecture ...and provides for the delivery of services to consumers. 2 Coordination Throughput Do Not Call List 3 Performance Monitoring Registry Security Messaging Operations 1 Workflow Identity SERVICE DELIVERY ENABLEMENT

  7. SOA: Layers of Value Services Reusable Business Process Foundation for the agility of 21st century demands Enablement Enterprise Agility Composition of services and business processes User Empowerment Composition of independent user views Delivery

  8. Value of Services Enablement Delivery Services Reusable Business Process Foundation for the 21st Century Demands Stand-alone Business Processes or Services Basic-business process context defined New services Business-use context unknown User-types context unknown Legacy “host” services often combined with user type context

  9. Value of Enablement Enablement Delivery Services Enterprise Agility Composition of Services and Processes Services Coordination, Services Enablement Business-use context defined Creates composite services Builds wrapped services Composes enterprise business processes User types context unknown

  10. Value of Delivery Enablement Delivery Services User Empowerment Composition of Independent User Experience Who? Employees, customers, partners/vendors What? Transactions, intelligence, collaboration, document and content management Purpose? General, vertical, horizontal How? Thick client, browser, wireless, PDA, e-mail

  11. What is this leading to? User Empowerment SOA Workgroup Experiences Host Application Integration (SOA) Host Presentation Integration (SOA) Web-to-Host Emulation User Productivity

  12. PRESENTATION Application Logic Application is or appears monolithic DATA Standard Access

  13. PRESENTATION Application Logic DATA “Transactional” Access OBJ OBJ OBJ

  14. PRESENTATION Application Logic DATA Use of “Transactional” Access Application Services Web Services OBJ OBJ OBJ

  15. Service-Oriented Host Services Applications Call Center Presentation Online Banking Host Logic Application Development Self-Service Data e-Commerce

  16. The Service Oriented Host • This is about taking advantage of the promise of SOA • It is not completely about the use of Web Services • Web services is an implementation • It is about correct use of existing applications within a services approach • Use a Services approach; transactionalize, add extensions, create services, allow tactical use of Host Applications within the push to SOA

  17. Use Case ScenarioKansas JobLink A Services Oriented Host

  18. The Issue Discerned a problem on the horizon • Economic climate change • Cyclical demand requirements • Currently approaching peak service requirement • Unemployment rising • Projected growth of claims processing in the double digits for the next several years • Inability to service the demand with current systems • Anticipated increase in claims to 250,000 per year • Call centers running at capacity of 110,000 claims per year

  19. Current System IVR Terminal Emulation CICS application Client Applications Call Center Mainframe

  20. Current Infrastructure • IS Staff • Internal IS staff developed legacy systems • Consultants developed VB app with Internal IS staff maintaining systems • Call Center Staff • Strong background using original "paper" system and CICS transactions • Trained in MS Office • Trained to use GUI-based system

  21. Business Objectives • Modify customer service delivery model (add channels) • Expand from phone to Web based self service • Redesign IVR script to provide self service • Extend hours of operation • Reduce the time an agent needs to spend with customer • Provide an agile platform to accelerate development times • Improve existing software performance throughput • Reuse code • Reduce delivery risk

  22. Looked At Two Options • A grant team reviewed the requirements • Two solutions were proposed to address the requirements out of the review • Mainframe service technology • Reengineer the legacy system to a client server environment Mainframe Service Technology Reengineer the legacy systemto a client server environment

  23. Requirements Re-evaluated • Combined critical path requirements • Business requirements • Staff skill-set capabilities • Re-use capabilities • Retention of existing systems Solution evolved out of ability of new open and market standards to access the critical legacy systems

  24. A Services Approach • Issue was how to work in KDHR preferred environments without throwing out Legacy Systems • Apply a Services Oriented Architecture to the legacy systems

  25. Services Architecture Pick appropriate access method Supply a services interface to the CICS applications Generate Host Interactions Publish as Service Tasks Screen Access XML Web services Direct CICS (DPL) Direct Bridge Exits Mainframe CICS .NET Service Provider Preferred Connectivity Java COM APPLICATIONS

  26. JobLink Phase 1 Web site BizTalk Web Service Tasks MSMQ Tasks XML-based messaging IVR Web Service AttachmateSmart Connector Tasks Tasks SNA, IP to mainframe CICS application Mainframe

  27. JobLink Phase 2 Web site BizTalk Web Service Tasks Tasks XML-based messaging IVR Web Service AttachmateSmart Connector Tasks Tasks Siebel app Web Service XML/ http CICS application Tasks Rules Higher Requirements Nativeschema Mainframe

  28. JobLink Phase 3 Web site BizTalk Web Service Tasks Tasks XML-based messaging IVR Web Service AttachmateSmart Connector Tasks Tasks Siebel app Web Service XML/ http CICS application Tasks Rules Nativeschema Web Service Mainframe Tasks Tasks Web Service Tasks Rules

  29. Benefits Applied • ROI in less than a year • The standard benefits used to bolster a services oriented architecture were realized • Simplified integration • Agility • Open standards made it a safe decision • Use of accepted standards facilitates use with future systems and technologies • These solutions will be accounted for…

  30. Thank You

More Related